Migrating resources/resource groups from one subscription to another

%3CLINGO-SUB%20id%3D%22lingo-sub-2306402%22%20slang%3D%22en-US%22%3EMigrating%20resources%2Fresource%20groups%20from%20one%20subscription%20to%20another%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2306402%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20been%20asked%20by%20a%20client%20of%20mine%20to%20migration%20resources%2Fresource%20groups%20from%20a%20current%20CSP%20subscription%20to%20their%20MCA%20subscription.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20migrating%20the%20entire%20resource%20group%2C%20can%20I%20keep%20the%20same%20name%20in%20the%20new%20Subscription%20or%20will%20this%20require%20a%20new%20name%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2308415%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20resources%2Fresource%20groups%20from%20one%20subscription%20to%20another%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2308415%22%20slang%3D%22en-US%22%3EIn%20general%2C%20each%20resource%20has%20a%20ResourceId%20and%20subscriptionId%20is%20part%20of%20that%20ID.%20Since%20there%20can't%20be%20two%20subscriptions%20in%20Azure%2C%20you%20can%20retain%20your%20original%20name.%20The%20issue%20can%20be%20with%20some%20resources%20that%20must%20have%20globally-unique%20names%20(like%20Azure%20Storage%20accounts)%20and%20the%20way%20you%20are%20planning%20to%20perform%20this%20migration.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2311762%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20resources%2Fresource%20groups%20from%20one%20subscription%20to%20another%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2311762%22%20slang%3D%22en-US%22%3EHi%3CBR%20%2F%3ENo%20it%20will%20not%20require%20a%20new%20name%20ine%20case%20of%20just%20moving%20the%20resource%20.%3CBR%20%2F%3EBut%20you%20may%20know%20that%20all%20resources%20doesn't%20support%20move%20.%3CBR%20%2F%3EYou%20can%20see%20the%20full%20list%20below%20%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-resource-manager%2Fmanagement%2Fmove-support-resources%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-resource-manager%2Fmanagement%2Fmove-support-resources%3C%2FA%3E%3CBR%20%2F%3EIf%20the%20move%20is%20not%20supported%20you%20will%20need%20to%20create%20it%20directly%20in%20the%20new%20subscribtion%20.%3CBR%20%2F%3EWhen%20it%20comes%20to%20create%20resources%20for%20the%20new%20subscription%20you%20need%20to%20consider%20the%20scope%20for%20the%20resource%20names.%3CBR%20%2F%3EGlobal%20%3D%20Unique%20across%20All%20of%20Azure%20(Name%20of%20Paas%20resources%20with%20public%20ip%20endpoints%20accross%20all%20Azure%20.%3CBR%20%2F%3EResource%20Group%20%3D%20Unique%20within%20the%20resource%20group%20(%20Virtual%20Networks%20should%20have%20unique%20name%20when%20they%20shared%20the%20same%20resource%20group%20but%20the%20same%20name%20can%20be%20used%20within%20another%20resource%20group%20and%20in%20your%20case%20another%20subscription%20)%3CBR%20%2F%3EResource%20Attribute%20%3D%20Unique%20within%20the%20parent%20resource(%20Subnets%20need%20to%20be%20unique%20within%20a%20vnet%20but%20can%20have%20duplicate%20name%20when%20related%20to%20different%20vnet%20.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi 

 

I have been asked by a client of mine to migration resources/resource groups from a current CSP subscription to their MCA subscription.  

 

When migrating the entire resource group, can I keep the same name in the new Subscription or will this require a new name?

2 Replies
In general, each resource has a ResourceId and subscriptionId is part of that ID. Since there can't be two subscriptions in Azure, you can retain your original name. The issue can be with some resources that must have globally-unique names (like Azure Storage accounts) and the way you are planning to perform this migration.
Hi
No it will not require a new name ine case of just moving the resource .
But you may know that all resources doesn't support move .
You can see the full list below :
https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/move-support-resources
If the move is not supported you will need to create it directly in the new subscribtion .
When it comes to create resources for the new subscription you need to consider the scope for the resource names.
Global = Unique across All of Azure (Name of Paas resources with public ip endpoints accross all Azure .
Resource Group = Unique within the resource group ( Virtual Networks should have unique name when they shared the same resource group but the same name can be used within another resource group and in your case another subscription )
Resource Attribute = Unique within the parent resource( Subnets need to be unique within a vnet but can have duplicate name when related to different vnet .