Training: Instruction to develop new skills.
No. Once the Visual Studio subscriber Azure credit has been activated on a specific Azure account/identity, it can’t be “unassigned” and moved to another existing Azure account.
However, if the Visual Studio subscription itself was associated with the same credentials as an Azure Enterprise Agreement (EA) or other enrollment and that caused the loss of the individual Visual Studio Azure benefit, there is a supported way to recover the benefit by changing which identity holds the Visual Studio subscription:
- Remove or move any Azure subscriptions that are currently associated with that account from the EA/billing enrollment, and then remove that account as an EA Account Owner in the Azure portal.
- Then sign up again for the individual Visual Studio Azure benefits using the Visual Studio subscription identity.
Or, alternatively:
- Delete the Visual Studio subscriber from the administration site in VLSC.
- Reassign the Visual Studio subscription to a different identity (for example, a personal account with different credentials).
- Activate the Visual Studio Azure credits again under that new identity.
Also note:
- Visual Studio subscriptions support adding an alternate identity (for example, a work or school account) that can be used to access Azure, Azure DevOps, and Visual Studio IDE benefits. This does not duplicate the subscription; it only allows that alternate identity to use the benefits.
- Monthly Azure credits for Visual Studio subscribers are for personal use and cannot be pooled or shared.
To change which identity uses the Visual Studio Azure benefit, the Visual Studio subscription itself must be reassigned to that identity and the Azure benefit reactivated under it.
References: