Tag not monitored by Microsoft.
Renewing the Microsoft AI Cloud Partner Program with a Partner Success Core Benefits package does not automatically extend or convert an existing individual Azure subscription that was using monthly partner credits.
Key points based on the current benefits model:
- Azure credits are now pooled at the organization level
Partner Program developer benefits have been updated so that Azure value is delivered through Partner Program benefit packages, not as per-user monthly credits tied directly to an individual Azure subscription.
This means the new Partner Success Core Benefits package gives the organization a pool of Azure credits, which must be redeemed/used via eligible Azure subscriptions. It does not automatically attach to an existing dev/test or sponsorship subscription.“Azure value shifts from per-user monthly credits to Partner Program benefit packages. This change enables pooled usage and improved utilization across teams.”
- Existing subscriptions tied to expiring monthly credits will not continue automatically
When a Visual Studio or partner-based monthly credit expires, the associated Azure subscription loses that benefit. To keep resources running, one of the following must be done before the subscription is disabled:- Transfer resources to another Azure subscription that has valid credits or
- Convert the current subscription to pay-as-you-go by removing the spending limit.
“If your Visual Studio subscription expires or is removed, subscription benefits including the monthly Azure dev/test individual credit are no longer available… You must transfer your resources to another Azure subscription before your current Azure subscription is disabled or you'll lose access to your data.”
- What to do with the new Partner Success Core Benefits credits
With the new benefits package:- Redeem the Azure credits provided by the Partner Program benefit package into an eligible Azure subscription (this may create a new Azure subscription depending on how the credits are redeemed).
- Move existing resources from the old, expiring-credit subscription into the new credit-backed subscription before the old one is disabled.
- Option 1: Redeploy/move resources using the partner benefits package Azure credits.
- Option 2: Keep resources running under pay-as-you-go by removing the spending limit.
- Option 3: Move resources to another subscription or resource group that aligns with the organization’s Azure credit use.
- Risk of doing nothing
If no action is taken and the old partner-credit subscription reaches its disable date:- The subscription will be disabled.
- Access to resources and data can be lost unless the subscription is later re-enabled as pay-as-you-go, and even then, credits from the new benefits package will not retroactively apply to that disabled period.
- Recommended path for this scenario
- In Partner Center, confirm that the Partner Success Core Benefits package is active and identify the Azure credits included.
- Redeem those credits into an Azure subscription (this may be a new subscription depending on the benefit type).
- In the Azure portal, move your existing resources from the old partner-credit subscription to the new credit-backed subscription using the documented move process: Move Azure resources to a new resource group or subscription.
- Only if you explicitly want pay-as-you-go on the old subscription, remove the spending limit there; otherwise, keep usage on the new credit-backed subscription.
This approach avoids unplanned pay-as-you-go charges on the old subscription and ensures resources are protected under the new Partner Success Core Benefits Azure credits rather than assuming automatic renewal on the existing subscription.
References: