Startups: Companies that are in their initial stages of business and typically developing a business model and seeking financing.
Transferring Azure sponsorship credits between subscriptions is constrained by billing-account and offer rules and doesn’t behave like a simple “retarget” of credits onto any existing subscription.
From the provided information:
- Azure credits are bound to the purchase Billing Account and can’t be moved or transferred outside that Billing Account boundary. If subscriptions A, B, and C are not under the same Billing Account, the credits can’t be moved to B or C at all.
- When credits are deposited on a Billing Profile (modernized experience), subscriptions under that Billing Profile can’t be moved to a different Billing Profile until the credits are fully consumed.
- In the legacy experience, redeeming Azure credits always creates a new Azure subscription; credits can’t be applied to an existing pay-as-you-go subscription. After redemption, resources must be moved to that new subscription to use the sponsorship credits.
- Credits associated with specific offers (for example, Microsoft AI Cloud Partner Program, Visual Studio, or sponsorship offers) are tied to the subscription/offer type and don’t combine with other offers.
- For supported subscription types, any credit available on the subscription won’t be available in the new account after a billing-ownership transfer.
Given these rules, when Microsoft “moves” or “reassigns” sponsorship credits, the normal pattern is:
- Credits remain tied to the Billing Account and Billing Profile where they were purchased/deposited.
- In legacy/benefit scenarios, applying sponsorship credits typically creates a new subscription rather than attaching them to an existing one.
Therefore, when requesting Microsoft to transfer sponsorship credits from subscription A to an identity that already has subscriptions B or C, the expected behavior based on the documentation is that the sponsorship is associated with a new subscription under that billing context, not retroactively attached to an existing subscription B or C.
To use the credits for workloads currently in B or C, the supported path in the documentation is to move the resources from B or C into the sponsorship-backed subscription (the one with the credits) rather than expecting the credits to be layered onto B or C.
References: