Two Azure subscriptions under the same Visual Studio Professional account

Question

I have two Azure subscriptions under the same Visual Studio Professional account:

<PII Removed>
My resources are running in the first subscription, but the monthly Visual Studio Azure credit is being applied to the second subscription. Is it possible to associate the Visual Studio subscriber credit with the existing subscription instead?

Answer 1

Hello Tony Arslan,

Thank you for posting your query on Microsoft Q&A platform.

No, the Visual Studio monthly Azure credit can't be detached from the subscription it created and "re-attached" to another existing Azure subscription. The credit is permanently bound to the Azure subscription that was provisioned when you activated the Monthly Azure credit benefit on my.visualstudio.com (in your case, the subscription <PII Removed> bdc554d3f2a2). That subscription is on a special Visual Studio Professional offer (MS‑AZR‑0059P), which is what makes the $50/month credit apply. A regular subscription (like your c3906033-… one) is on a different offer (e.g., Pay‑As‑You‑Go), so the credit can't be reassigned to it.

When you click Activate on the Azure monthly credit benefit, Microsoft creates a new Azure subscription using the Visual Studio Professional offer (MS‑AZR‑0059P). The credit is a property of that offer, not of your Visual Studio account, so:

• You can't "move" the credit to your other subscription.
• You can't convert your existing pay-as-you-go subscription so it starts receiving the VS credit.
• You can only have one active VS credit subscription per Visual Studio license at a time.

This is documented here:

• Monthly Azure credit for Visual Studio subscribers
• Azure Dev/Test eligible credits in subscriptions
• Maintain a Visual Studio subscription for Azure credit access

You have two practical paths, depending on which subscription you want to keep long‑term:

Option 1 : Move your resources into the credit‑backed subscription (recommended)

Since the credit lives on <PII Removed>, the simplest fix is to migrate the resources from your first subscription into this one so the credit actually offsets your spend.

• Use Move resources to a new resource group or subscription in the Azure portal.
• Both subscriptions need to be in the same Microsoft Entra tenant (or you must transfer first), and not all resource types support cross‑subscription move, verify with the https://learn.microsoft.com/azure/azure-resource-manager/management/move-support-resources.
• Reference: https://learn.microsoft.com/azure/azure-resource-manager/management/move-resource-group-and-subscription.

Option 2 : Keep using the first subscription and stop relying on the credit

If your resources can't be moved easily (or you're running production-style workloads, which the VS credit isn't intended for anyway — it's Dev/Test only), then:

• Leave c3906033-… on Pay‑As‑You‑Go and pay normally for it.
• Let the credit on d2ecb78c-… be used for dev/test workloads, or stop activating it.

The VS monthly credit subscription is explicitly intended for development and testing, not production, and has no SLA, which is another reason Microsoft doesn't allow attaching it to an arbitrary existing production subscription.

Option 3 : Transfer billing ownership (only if you also want to change who pays)

If your real goal is to consolidate billing under one account, you can use Transfer billing ownership. But note: when a VS credit subscription is transferred, the credit doesn't carry over it starts using the credit available in the destination account. So this doesn't solve "merge credit into my other subscription" either.

Reference: Transfer billing ownership of an MOSP Azure subscription and Azure product transfer hub.

The Visual Studio monthly credit is locked to the Azure subscription that was created when you activated the benefit (your d2ecb78c-… subscription). Microsoft doesn't provide a way to re‑associate that credit with an already‑existing Azure subscription that's on a different offer. The supported path is to move your resources into the credit‑backed subscription, rather than moving the credit. If the resources need to stay where they are (e.g., they're production), continue running them on the pay‑as‑you‑go subscription and treat the VS credit subscription as your separate dev/test sandbox.

Thanks,

Suchitra.

Answer 2

Hello Tony Arslan,

Welcome to Microsoft Q&A,

The monthly Visual Studio Azure credit is permanently tied to the specific Azure subscription that was created at the time you activated it. There's no setting to re-point an already-activated credit benefit to a different existing subscription, each activation creates its own subscription.

You could move your resources into the credit subscription. Since the credit is already landing on the second subscription, move your existing resources from the first one into it.

https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli

Note: not all resource types support subscription moves, check the supported resources list on that page first

Please upvote and accept the answer if it helps!!