Azure Marketplace Offer Development for Agencies
White-label SaaS listing and transactable offer delivery across AU, UK, and SG. We build the Azure Marketplace offer — your clients go live on the Microsoft commercial marketplace.
From SaaS Fulfillment API integration and managed application packaging to Partner Center listing, metered billing setup, and co-sell eligibility activation. End-to-end marketplace publishing delivered under your agency brand.
Azure Marketplace Publishing: The Technical Groundwork Most ISVs Underestimate
Publishing on Azure Marketplace isn’t uploading a product listing. The transactable SaaS path requires implementing the SaaS Fulfillment API v2 — a landing page that correctly exchanges the x-ms-marketplace-token query parameter for subscription metadata, a webhook endpoint that acknowledges Microsoft’s provisioning and lifecycle events within a ten-second timeout window, and an activation flow that calls back to confirm the subscription before your tenant can access the product. Get that sequence wrong and certification flags it — sometimes with a clear error, sometimes with a vague test failure that takes two revision cycles to diagnose.
The certification queue is automated for most technical checks and manual for security and functionality reviews. First submissions rarely clear without at least one revision request when the SaaS API integration hasn’t been built by someone who’s done it before. We’ve scoped enough Azure Marketplace projects to know where the friction points are and to build offers that pass certification with minimal revision cycles. You can see how that translates in practice across our case studies.
Azure Marketplace Offer Services
Six specialist capabilities. One engineering team building and publishing your Microsoft Azure Marketplace offer end to end.
SaaS Fulfillment API Integration
We build the full SaaS Fulfillment API v2 integration — landing page with x-ms-marketplace-token exchange, subscription activation callback, webhook endpoint handling subscription provisioning, plan change, cancellation, suspend, and reinstate events within Microsoft’s ten-second acknowledgement window. The Azure Marketplace SaaS offer documentation defines the full lifecycle — we implement and test it against the Microsoft certification checklist before first submission.
Managed Application Offer Packaging
We package managed application offers with ARM or Bicep deployment templates, define the createUiDefinition.json for the Azure portal deployment experience, and configure managed resource group permissions and deny assignment policies. For publishers deploying infrastructure-heavy solutions where customers should receive a fully managed resource group rather than a SaaS subscription, the managed application offer type is the correct path — and the packaging requirements are significantly more involved than SaaS.
Partner Center Listing and Plan Configuration
We set up the Partner Center commercial marketplace account, configure offer properties and categories, write listing copy for AppSource and Azure Marketplace storefronts, define plan tiers with pricing models — flat rate, per-user, or metered — and configure preview audiences for staging validation before publishing. Offer properties, listing quality, and plan structure all affect discoverability and co-sell eligibility, so we treat the listing configuration as a GTM asset, not an afterthought.
Marketplace Metered Billing
We integrate the Marketplace Metering Service API to emit usage events against custom dimensions defined in your offer plan — API calls, data volume, active seats, processing minutes. Metered dimensions are defined in Partner Center and referenced in emitted events using the resourceId and quantity payload format. We build the usage aggregation logic, the retry strategy for failed emission calls, and the reconciliation dashboard your clients use to validate billed consumption against actual usage records.
Private Offer Configuration
Private offers let publishers extend customised pricing, discounted terms, or non-standard plan configurations to specific customer tenants outside the public marketplace listing. We configure private offers in Partner Center against a target customer tenant ID, set expiry windows, and validate acceptance flows in staging before the offer goes to the target customer. For agencies managing enterprise ISV clients with negotiated deals, private offers remove the need to publish special-case pricing publicly in the standard plan catalogue.
Co-Sell and GTM Activation
Co-sell eligibility unlocks access to Microsoft’s field sales team as a referral channel. We configure the Partner Center co-sell section — solution overview, customer pitch deck, reference customers, and solution intent documentation — to meet the IP co-sell ready and Azure IP co-sell incentivised tiers. We also set up the Marketplace Rewards benefit tracking and walk your client through the Microsoft Business Applications ISV Connect programme requirements if Dynamics 365 integration is part of the offer scope.
Our Offer-Architecture-First Approach to Azure Marketplace
We don’t start by writing SaaS API code. Every Azure Marketplace engagement begins with offer architecture — mapping the subscription lifecycle events your application must handle, selecting the right offer type for your client’s product and customer acquisition model, defining plan tiers and pricing dimensions before any Partner Center configuration is touched, and designing the Azure AD application registration structure that underpins the landing page token exchange and webhook authentication.
The decisions made in this phase — offer type selection, plan model, metered dimension design, tenant isolation approach for multi-tenant SaaS — determine the complexity of every subsequent build step. Getting them wrong means revisiting Partner Center configuration after the API integration is already built. We document the offer architecture and get sign-off before writing a line of fulfillment code. To discuss your client’s marketplace project, book a discovery call — we return a preliminary scope within a week.
Technical Capabilities We Bring to Every Azure Marketplace Project
Certification-ready builds, identity-secure API integrations, and metered billing architecture — delivered from day one of the engagement.
Offer Certification and Validation
We build against the Microsoft certification test cases before submission — SaaS landing page token validation, webhook acknowledgement timing, subscription lifecycle coverage, security vulnerability scans, and listing quality requirements. Certification failures caught during build are cheaper than revision cycles inside the Partner Center review queue, so we run the Microsoft Certification Test Tool against every offer before first submission.
Landing Page and Webhook Engineering
The marketplace landing page correctly processes the x-ms-marketplace-token via the SaaS Fulfillment API resolve endpoint, persists subscription metadata, and initiates your tenant provisioning flow before calling activate. The webhook endpoint is secured with Azure AD bearer token validation, returns HTTP 200 within the ten-second window for all event types, and processes each lifecycle event — provisioning, plan change, cancellation, suspend, reinstate — without producing duplicate records on redelivery.
Metered Billing Architecture
Custom dimension design in Partner Center aligned to how your client’s product actually generates value — API calls, compute minutes, active users, records processed. Usage aggregation with scheduled emission jobs, retry logic for failed Metering Service API calls using exponential backoff, idempotent emission using the resourceId correlation key, and a reconciliation view comparing emitted usage against Azure billing records to catch discrepancies before invoice generation.
Marketplace Identity and Security
Azure AD multi-tenant application registration for the SaaS offer, admin consent grant flow for the landing page, webhook endpoint authentication using Microsoft identity platform bearer tokens validated against the well-known JWKS endpoint, and tenant isolation patterns preventing cross-tenant data access in multi-tenant SaaS architectures. Security is a first-class certification requirement — it’s not a final review step we address after the API integration is already built.
Azure Marketplace Offer Development Under Your Agency Brand
We work as the invisible engineering layer behind your agency’s Azure Marketplace delivery. Our engineers handle the SaaS Fulfillment API integration, Partner Center configuration, and certification submission — while your account managers own the client relationship. Your clients receive architecture documentation, testing reports, and go-live runbooks in your agency’s format. We’re the technical team they don’t see, and that’s exactly how the engagement is designed.
Our white-label development model is built for agencies managing ISV clients who need Azure Marketplace presence at scale. You scope confidently knowing the certification-grade technical delivery is handled. For agencies managing multiple marketplace projects simultaneously, our agency partner programme provides priority access to our marketplace engineering team, preferred rates, and a dedicated account contact across all active ISV publishing engagements.
Why Azure Marketplace Offers Fail Certification — And What We Do Differently
The two most common certification failure patterns we see on inherited projects: first, the landing page doesn’t correctly process the marketplace token — it stores the raw x-ms-marketplace-token instead of resolving it against the SaaS Fulfillment API to retrieve the actual subscription and plan metadata. Microsoft’s automated certification tests catch this, but the error message doesn’t always make the root cause obvious, and development teams without prior Azure Marketplace experience spend days diagnosing what is actually a three-line API call issue.
Second, the webhook endpoint either doesn’t respond within the ten-second acknowledgement window under load, or it doesn’t handle all required lifecycle event types — particularly the Suspend and Reinstate events that fire when a customer’s payment fails and then recovers. Our Microsoft Azure development services practice builds against the full certification checklist from the start — not as a final-stage review before submission.
Engagement Models for Azure Marketplace Projects
Structured for agency delivery workflows. Scalable across your full ISV client portfolio.
Marketplace Offer Sprint
A defined 4-to-8-week sprint covering offer architecture, Azure AD registration, SaaS Fulfillment API integration, Partner Center listing configuration, and certification submission. Best for agencies that need a fixed deliverable scope and a published, transactable Azure Marketplace offer at the end — not a work-in-progress handed over before certification completes.
Dedicated Marketplace Engineer
A senior marketplace engineer embedded in your ISV client project — owning the SaaS API integration, Partner Center configuration, metered billing build, and certification submission process. Operating in your project tools and producing documentation in your format. Available full-time or part-time depending on the project phase and concurrent Azure Marketplace offer count.
ISV Publishing Retainer
A monthly retainer for agencies managing multiple ISV clients publishing on Azure Marketplace simultaneously. Covers new offer type development, plan additions, metered dimension changes, co-sell documentation updates, and certification resubmissions — without spinning up a separate engagement for each change. Predictable monthly cost across your active publisher portfolio.
Multi-Offer Portfolio Delivery
Two to three marketplace engineers delivering across multiple concurrent Azure Marketplace offers for a single ISV client — SaaS offer plus managed application plus virtual machine image, or separate offers targeting different customer segments with distinct plans. Reach us via our contact page to discuss portfolio scope and team structure.
Our Azure Marketplace Offer Delivery Process
Six phases from offer architecture to go-live, with sign-off gates before each build stage begins.
Phase 1 — Offer Architecture and Subscription Model Design
We select the right offer type for your client’s product — SaaS, managed application, virtual machine image, or container — define the subscription lifecycle event map, design plan tiers and pricing models, and scope metered billing dimensions before any Partner Center configuration is touched. Offer architecture decisions reviewed and signed off before the build phase begins.
Phase 2 — Azure AD Setup and Application Registration
Multi-tenant Azure AD application registration for the SaaS offer, admin consent grant configuration for the landing page, reply URL setup for the OAuth flow, and API permission scopes defined for the fulfillment and metering service calls. The identity layer underpins every subsequent API integration — we configure it correctly before writing the first line of fulfillment code.
Phase 3 — SaaS Fulfillment API and Landing Page Build
Landing page implementation with x-ms-marketplace-token resolution, subscription activation callback, and tenant provisioning trigger. Webhook endpoint built with Azure AD bearer token validation, HTTP 200 acknowledgement within ten seconds, and idempotent event handling for all lifecycle types. Metered billing emission jobs built and tested against sandbox Metering Service API endpoints before Partner Center configuration begins.
Phase 4 — Partner Center Listing and Offer Configuration
Offer property configuration, storefront listing copy for both AppSource and Azure Marketplace, plan creation with pricing and trial period setup, preview audience configuration for staging validation, and technical configuration linking the landing page URL and webhook endpoint. Listing quality reviewed against Microsoft’s certification requirements before submission is initiated.
Phase 5 — Certification Submission and Validation
We submit the offer to certification, monitor the automated and manual review queues, respond to certification feedback with targeted fixes, and re-submit until the offer reaches the published state in both preview and live environments. Common failure reasons are addressed proactively during build — webhook timing, landing page token handling, and security scan findings — to minimise revision cycles inside the review queue.
Phase 6 — Go-Live, Co-Sell Activation, and Revenue Monitoring
Go-live checklist covering live environment validation, customer subscription purchase test, metered billing emission verification against published dimensions, and co-sell documentation submission in Partner Center. Post-launch, we configure Marketplace Rewards benefit tracking and set up the Azure Cost Management view your client uses to reconcile metered billing revenue. Learn more about how we structure all engineering delivery on the NextEnvision Digital homepage.
Azure Marketplace — Frequently Asked Questions
Honest answers to the questions agencies ask us before taking on an ISV marketplace publishing project.
What security requirements should Android Kotlin development address?
The SaaS Fulfillment API v2 is the integration layer Microsoft requires between your SaaS application and the commercial marketplace subscription lifecycle. It handles the token exchange on your landing page, the activation call that confirms a customer’s subscription, and the webhook events that fire when a customer changes plan, cancels, or gets suspended for non-payment. Without a correctly implemented fulfillment integration, your offer won’t pass transactable SaaS certification — and a listing without transactability means customers can’t purchase through the marketplace checkout flow.
How is WCAG 2.1 accessibility implemented in Android Kotlin development?
A SaaS offer means the publisher hosts the application in their own infrastructure and the customer pays through the marketplace. A managed application offer deploys a publisher-defined Azure resource group into the customer’s own subscription — think infrastructure-heavy solutions like pre-configured virtual machine clusters, data platforms, or networking appliances. SaaS is the right choice when you control the hosting environment. Managed application is correct when the customer needs the solution running inside their own Azure tenant with their own resource governance.
How does Hilt dependency injection work in Android Kotlin development?
Microsoft’s automated certification checks run within a few hours. Manual security and functionality reviews currently run two to five business days for first submissions. If certification returns revision requests — which it will for most first-time publishers on the transactable SaaS path — each resubmission restarts the review queue. We build against the certification checklist before first submission specifically to avoid revision cycles. For a well-prepared offer, plan for three to four weeks from first submission to live status on the marketplace.
What is ProGuard/R8 and why does Android Kotlin development need it?
Metered billing lets you charge customers based on actual consumption beyond a base subscription fee — API calls, compute minutes, records processed, active seats. You define custom dimensions in Partner Center, then emit usage events against the Marketplace Metering Service API as customers consume. It’s the right choice when your product’s value delivered varies significantly between customers and a fixed monthly plan would either underprice heavy users or overprice light ones. The metering integration requires careful implementation — failed emission calls mean unbilled consumption.
How does Android Kotlin development handle errors and offline states?
A private offer lets you extend customised pricing, discounted terms, or non-standard plan configurations to a specific customer tenant without publishing those terms publicly in your standard plan catalogue. It’s the right mechanism for negotiated enterprise deals where the commercial terms differ from your public listing — annual commitments, volume discounts, custom SLA terms. The customer receives a unique offer URL that maps to your private configuration in Partner Center, and acceptance triggers the standard subscription purchase flow.
How do you evaluate and select third-party libraries for Android Kotlin development?
That’s our standard delivery model. The Partner Center publisher account belongs to your client — we configure it, build the SaaS integration, and manage the certification process operating entirely within your agency engagement. Architecture documents, certification reports, and go-live runbooks are produced in your format. Agencies managing multiple ISV clients publishing on Azure Marketplace through us typically move to our agency partner programme for priority team access and consolidated commercial terms.