Azure Sponsorship on a Marketplace Deal: The Rules

Grow Azure sponsorship is a Frontier Accelerate for Marketplace benefit that lets a software company in the program’s Grow stage give a customer on a Microsoft Marketplace deal 100% discounted first-party Azure usage for a fixed period, drawn from an allowance that increases with its Marketplace performance. A separate allowance offsets the company’s own free-trial costs. This post covers the deal use, as Microsoft’s policy stands on September 29, 2026.

---

Late in the negotiation, Globex’s cloud architect asks whether Microsoft will help with the Azure costs of the rollout. Acme’s account executive has heard that Frontier Accelerate for Marketplace includes Azure sponsorship and wants to put a number in the proposal. Before anyone does, the deal desk needs four answers: does the deal qualify, how much can it carry, when does the request go in, and what will surprise the customer later?

Microsoft answers almost all of it on one policy page, dated September 16, 2026, and warns that its “policies are subject to change at any time at Microsoft’s discretion.” It doesn’t publish the size of your allowance, so this post states none. Microsoft announced the program as “now available to eligible partners” on September 28, 2026; for how it works, from enrollment to Premium, start with our guide to Frontier Accelerate for Marketplace.

What is Grow Azure sponsorship?

Grow Azure sponsorship is a set of Azure sponsorship allowances in Frontier Accelerate for Marketplace that, in Microsoft’s words, “increases with your Marketplace performance and is designed to help you grow pipeline and sales through Marketplace.” You draw on an allowance in increments Microsoft calls grants, and each grant “provides 100% discounted Azure usage of first-party Azure workloads for a specific duration.”

Microsoft approves two uses and gives you a separate allowance for each, so a trial grant never eats into what you can offer a customer:

Use	Who receives the grant	What it covers
Accelerate Marketplace adoption	A customer tied to a Microsoft Marketplace deal	The customer’s own Azure usage
Offset costs from free trials	Your own tenant	The infrastructure cost of the free trials you offer

Microsoft’s Grow page sums the benefit up as sponsorship “for customer deployment, no-cost trials, and deal-closure assistance.” This post calls the first allowance your adoption allowance.

Who has an allowance, and how large is it?

You have one when three things are true:

• An active enrollment, which Microsoft requires for every Frontier Accelerate for Marketplace benefit.
• The Grow stage, which starts once a published, transactable offer generates Marketplace Billed Sales.
• A milestone: sponsorship is “unlocked as performance milestones are reached.”

You don’t need Premium. Microsoft’s benefits page includes “Azure sponsorship (Grow, milestone-based)” on both the no-cost path and Premium.

Keep one figure apart. Microsoft’s September 28 announcement credits Premium with “up to 30,000 USD in Azure sponsorships,” but the only $30,000 on its benefits page is Azure dev/test credits for new Premium partners, a Build and Publish internal-use benefit, and the sponsorship policy never mentions Premium. Don’t size a customer grant against it.

Microsoft doesn’t publish allowance sizes. Yours grows with your Marketplace performance, and Microsoft’s FAQ puts “exact thresholds and per-tier benefits” in a Tiers & Benefits Matrix that isn’t on its public Learn pages. Grow tiers track trailing 12-month Marketplace Billed Sales and reset at renewal, and the allowance “refreshes yearly if you maintain your Marketplace performance.” Microsoft’s process has you get your total allowance, remaining allowance and anniversary date from your Engagement Manager, and the unified dashboard in Partner Center shows whether each benefit is available or locked. Confirm your remaining allowance before you promise a grant.

Which Marketplace deals qualify?

A deal qualifies when it transacts through Microsoft Marketplace, the sponsorship was part of the negotiation, and the customer’s Azure can receive it. Run each deal through this checklist before sponsorship goes into a proposal:

Check	Microsoft’s rule
The deal goes through Microsoft Marketplace	”Deal must be through Microsoft Marketplace.”
Sponsorship is part of the negotiation	It “must be offered as part of deal negotiation (deal is contingent on sponsorship)” and “may not be given to customer reactively if it was not part of the deal.”
The customer’s billing account is pay-as-you-go, EA or MCA	Sponsorship applies only to pay-as-you-go (PAYG), Enterprise Agreement (EA) and Microsoft Customer Agreement (MCA) billing accounts. “It’s not available on CSP billing accounts.”
The tenant is on Microsoft’s commercial cloud	Commercial (Public and Global) cloud only, not Azure Government, Azure China or other sovereign clouds.
The billing account has no active sponsorship	Sponsorships can’t be stacked on billing accounts with the same owner. The existing one has to expire or be used up, or the grant goes to an account with a different owner.
The customer isn’t public sector	Adoption grants “cannot be awarded to public sector companies, state-owned entities, or government customers without specific controls.” Microsoft doesn’t define those controls, so ask before offering.
No other grant on the deal	”Only 1 grant per deal,” and it can’t be split into several grants or given at separate times.

On a resale deal, agree who files before anyone offers it: the request form asks whether the requester is the ISV or a channel partner reselling the ISV’s solution, and the deal still gets one grant.

How much sponsorship can one deal carry?

The lowest of three limits: Microsoft’s cap for the deal’s term, its $200K maximum per request, and what remains of your adoption allowance. A deal gets one grant, so that is the whole of it.

Deal	Cap on the grant
Three years or more	10% of annual contract value (ACV). Where ACV differs by year, use the average
One to two years	3% of total contract value (TCV)
Usage-based pricing	The same caps, on an estimate of ACV or TCV, which Microsoft accepts
Any term	No more than $200K per request

Microsoft doesn’t say how a term under one year, or between two and three, is treated. Ask before offering sponsorship on one.

The amount sets the validity period and whether the customer’s Microsoft account team must approve:

Grant amount	Validity period	Account team approval
Under $35K	90 days	Not required
$35K to under $100K	90 days	Required
$100K to $200K	180 days	Required

Four illustrative deals, with fictional customers:

Deal	Arithmetic	Largest grant	Validity	Approval
Globex: three years at $300K a year	10% of $300K ACV	$30,000	90 days	Not required
Initech: three years at $400K, $500K and $600K	10% of the $500K average ACV	$50,000	90 days	Required
Umbrella: two years at $750K a year	3% of $1.5M TCV	$45,000	90 days	Required
Five years at $2.5M a year	10% of ACV is $250K, above the $200K maximum	$200,000	180 days	Required

Each figure is a ceiling, not an entitlement: the grant can’t exceed your remaining allowance, and requests go in $100 increments, with a $100 minimum.

Term matters as much as price. With equal years, the cap is 3% of one year’s value on a one-year deal, 6% on a two-year deal and 10% from three years on, by our arithmetic from Microsoft’s rules.

When do you offer it, and when do you request it?

Offer it during the negotiation, and request it after the deal closes, within 60 days of the close date. Microsoft requires both: the sponsorship has to be part of the deal, and it “must only be requested after the deal has closed.” Five more rules set the timing:

1. Submit before your anniversary date. You can request up to your allowance “before your Anniversary Date,” and the balance then expires and “does not roll over.” A deal that closes three weeks before your anniversary has three weeks, not 60 days, to draw on this term’s allowance.
2. Choose a start date 14 to 30 days out. The validity period “must start within 30 days of request date,” and the request form says to “select a date between 14-30 days from today due to processing time.”
3. Allow about seven business days. Microsoft provisions the sponsorship “within approximately seven business days of receiving the correct information,” and contacts you or the recipient if anything is wrong.
4. The customer activates it. The recipient “must take action to activate the sponsorship”: in the Azure Sponsorships portal on an EA or pay-as-you-go account, or from Microsoft’s email on an MCA. On pay-as-you-go, Microsoft “doesn’t reverse charges for Azure consumption before or after the sponsorship is activated.” Problems applying it go to Azure support.
5. The clock runs once. The only extension Microsoft lists is a one-time 30 days for “issues with applying the sponsorship requiring an Azure support ticket or entitlement transfer.” Microsoft wants customers “ready to use sponsorship right away,” so set the start date around the customer’s deployment plan.

Offering before close and requesting after it leaves a gap. A request has to meet policy “to avoid rejection,” and a grant of $35K or more needs the account team’s approval, so qualify the deal against every rule before sponsorship goes into the proposal, find the account team contact early, and have your legal team word the commitment.

An example timeline

An illustrative example with fictional companies: Acme’s Frontier Accelerate anniversary is November 30, 2026. Its three-year deal with Globex carries a $30,000 sponsorship, below the $35K approval line.

Date	What happens	The rule behind it
October 2026	Acme includes the sponsorship in its proposal. Globex confirms an EA billing account on the commercial cloud with no active sponsorship, and sends the form’s EA details	Part of the negotiation; an eligible account
November 2	Globex accepts and purchases the private offer, closing the deal	Request only after close
November 4	Acme submits the request with a November 20 start date	Within 60 days of close (by January 1, 2027) and before its anniversary; a start 16 days out
About seven business days later	Microsoft provisions the sponsorship to Globex	The stated processing time
Before November 20	Globex’s EA administrator accepts the terms, and its account owner converts the subscription	The recipient activates
November 20	The 90-day validity period starts	Under $100K
November 30	Acme’s anniversary: its unrequested adoption allowance expires	No rollover
Mid-February 2027	The sponsorship ends, and Globex’s usage reverts to its EA rates	Expiry or the amount used, whichever comes first

Had Globex closed on November 25, Acme would have had less than a week, not 60 days, to request against this term’s allowance.

What can’t Azure sponsorship pay for?

It can’t pay for your offer, reduce a bill the customer already has, or retire the customer’s MACC. Microsoft says partners and customers “are responsible for understanding whether Azure sponsorship works for them,” so put these in front of the customer before the proposal goes out:

Limit	What Microsoft says	What the customer should hear
First-party Azure only	Usage “of first-party Azure workloads,” not “third-party marketplace purchases, services, or support”	It covers Azure usage, not the Marketplace charge for our product
Retail rates	Discounted “off published pay-as-you-go retail rates, not contracted pricing rates”	Usage is valued at list pay-as-you-go prices, not your negotiated rates
No reservations	Not on billing profiles or subscriptions with Reserved Instances or Reserved Capacity	Use a subscription and billing profile without reservations
Future usage only	”Not a direct bill credit,” and it “can’t be applied retroactively to past charges”	It won’t reduce an invoice you already have
No MACC or ACR credit	It “doesn’t count towards ACR milestones or retiring a Microsoft Azure Consumption Commitment (MACC)“	Sponsored usage doesn’t draw down your MACC
Automatic switch	Pay-as-you-go or EA rates resume when the amount is used or the sponsorship expires, “whichever comes first”	Usage after that is billed to you as normal

The Marketplace purchase itself still counts. When a customer buys an Azure benefit-eligible offer through Marketplace in the Azure portal, on a subscription tied to its agreement, Microsoft counts 100% of the pretax purchase amount toward its MACC. See what a MACC is and how Marketplace purchases draw it down for the conditions.

Microsoft adds that “sponsorship usage and sponsorship impact cannot be amortized beyond the validity period.” How your finance team, or the customer’s, records a sponsorship is a question for them; nothing here is tax or accounting advice.

What does Microsoft’s request form ask for?

Details about you, the deal and the customer’s billing account. You’ll usually need the customer to confirm the billing-account identifiers, so collect or validate them before you submit. The policy page doesn’t link the form itself; Microsoft’s FAQ points to your Engagement Manager for the full submission checklist.

• You: your company name and Global Partner ID, and whether you’re the ISV or a channel partner reselling the ISV’s solution.
• The grant: the amount, the start date, and whether it goes to your own tenant or a customer.
• The deal: the recipient company, the offers transacted and their URLs, TCV and ACV in USD, the term, the close date and the co-sell deal ID, plus a contact on the customer’s Microsoft account team for a larger grant’s approval.
• The recipient: its region, Azure subscription type, an extra email for notices, and its billing-account identifiers:

Billing account	Identifiers the form needs
Enterprise Agreement	Enrollment number, account owner email and EA administrator email. The administrator accepts the terms and must be registered under the same Enterprise Agreement as the subscriptions
Pay-as-you-go	The Azure account ID email
Microsoft Customer Agreement	Billing account owner email, account ID, billing profile ID and enrollment number

One field depends on co-sell: the “deal ID or opportunity ID from co-sell deal registration.” Microsoft’s deal registration page treats a deal’s ID as its referral ID, and registration starts from the deal in Partner Center’s Co-sell opportunities tab. Microsoft doesn’t say whether a Marketplace deal never shared with Microsoft can still get a grant. If yours wasn’t shared, ask before you offer sponsorship.

How is the free-trial grant different?

It goes to your own tenant, from its own allowance, and only for SaaS or Azure Application offers “which generate consumption on partner’s tenant, and have free-trial capability enabled or a $0 SKU.” You state the trials you expect in the next three months and the expected conversion to paid, and attest to appropriate usage. The public-sector rule is stricter, with no “without specific controls” qualifier: trial sponsorship “cannot be awarded to public sector companies, state-owned entities, or government customers.”

How Suger fits

Suger’s documented funding workflow is AWS-specific; for Azure sponsorship, Microsoft’s request process remains separate. What Suger’s docs cover is the Marketplace offer the grant attaches to and, where the deal is co-sold, the referral behind the ID Microsoft’s form asks for.

• The Marketplace offer. Suger creates Azure private offers from Salesforce opportunities, HubSpot deals, the Suger Console or the API, so the offer the customer accepts is the Marketplace transaction the grant is tied to.
• The co-sell referral. Through Suger, your reps share and accept Azure co-sell referrals from Salesforce, HubSpot or Dynamics 365. When your team shares a deal with Microsoft from Salesforce, the Microsoft Referral ID syncs back to Suger’s referral record there, beside a flag showing whether the referral is eligible for Azure deal registration. The Azure fields on Suger’s Salesforce referral record lists both.

Frequently asked questions

Can you offer Azure sponsorship to win a Microsoft Marketplace deal?

Yes, if you’re in Frontier Accelerate for Marketplace’s Grow stage with an adoption allowance. The deal must go through Microsoft Marketplace, and the sponsorship must be part of the negotiation. You request it only after the deal closes, within 60 days of the close date.

How much Azure sponsorship can one Marketplace deal get?

One grant: up to 10% of average annual contract value on deals of three years or more, or 3% of total contract value on one-to-two-year deals. It’s capped at $200K per request and by your remaining allowance, and $35K or more needs Microsoft account-team approval.

Does Azure sponsorship count toward a customer’s MACC?

No. Microsoft says sponsorship offsets Azure consumption, so it doesn’t count toward ACR milestones or retiring a Microsoft Azure Consumption Commitment. An eligible Marketplace purchase of your offer still counts toward the MACC; the sponsored Azure usage doesn’t.

Can a customer use Azure sponsorship to pay for your Marketplace offer?

No. Microsoft excludes third-party Marketplace purchases, services and support. Sponsorship covers first-party Azure usage, priced at published pay-as-you-go retail rates, and only future consumption: it isn’t a bill credit and can’t be applied to past charges.

How long does an Azure sponsorship grant last?

90 days for grants under $100K and 180 days for $100K or more. The validity period must start within 30 days of the request, and Microsoft suggests a start 14 to 30 days out. Usage after expiry, or beyond the amount, is billed to the customer.

Which customers can’t receive Azure sponsorship?

Customers on CSP billing accounts, tenants outside Microsoft’s commercial cloud, such as Azure Government or Azure China, and, without specific controls, public sector companies, state-owned entities and government customers. Sponsorships also can’t be stacked on billing accounts with the same owner.

Takeaways

• Grow Azure sponsorship gives a Marketplace customer 100% discounted first-party Azure usage for 90 or 180 days, from an allowance whose size Microsoft doesn’t publish.
• Offer it in the negotiation; request it after close, within 60 days and before your anniversary date, starting 14 to 30 days out.
• One grant per deal: up to 10% of average ACV on deals of three years or more, or 3% of TCV on one-to-two-year deals, never over $200K, with account-team approval from $35K.
• The customer needs a pay-as-you-go, EA or MCA billing account on the commercial cloud and must activate the grant. Tell them up front that it doesn’t pay for your offer, isn’t a bill credit and doesn’t retire their MACC.
• The policy can change at Microsoft’s discretion, so re-read it before a number goes into a proposal.

Sponsorship rides on a Microsoft Marketplace deal, and Microsoft’s request asks for a co-sell deal or opportunity ID, so if the deal hasn’t been shared with Microsoft, confirm eligibility before promising sponsorship. Suger connects the Marketplace deal and the co-sell workflow: Azure private offers from Salesforce opportunities, HubSpot deals, the Suger Console or the API, and Azure co-sell referrals from Salesforce, HubSpot or Dynamics 365. See how in Suger’s Microsoft Marketplace solution.