Move Azure subscription to another tenant
We want to move Azure subscription resources, which are already hosting production system to another Azure AD tenant (using "Change Directory" feature).
I would like to know:
- If resources will continue to work will this this move is being made?
- We have locally defined users and groups in tenant from which subscription is moved. Do I understand correctly that these users will need to be recreated?
- Documentation says that RBAC permissions will be lost. Does this affect only the subscription being moved? Like Owner, Reader, Contributor permissions to subscription?
Any help is much appreciated. Thanks!
azure azure-active-directory
add a comment |
We want to move Azure subscription resources, which are already hosting production system to another Azure AD tenant (using "Change Directory" feature).
I would like to know:
- If resources will continue to work will this this move is being made?
- We have locally defined users and groups in tenant from which subscription is moved. Do I understand correctly that these users will need to be recreated?
- Documentation says that RBAC permissions will be lost. Does this affect only the subscription being moved? Like Owner, Reader, Contributor permissions to subscription?
Any help is much appreciated. Thanks!
azure azure-active-directory
The move affects rbac roles across all resources in the sub. They refer to user ids that are unique to the tenant so can't be moved.
– juunas
Nov 12 '18 at 14:38
Users need to be able to login to the new tenant access the subscription. Whether you create new users for them or add them as guests from another tenant is up to you.
– juunas
Nov 12 '18 at 14:39
add a comment |
We want to move Azure subscription resources, which are already hosting production system to another Azure AD tenant (using "Change Directory" feature).
I would like to know:
- If resources will continue to work will this this move is being made?
- We have locally defined users and groups in tenant from which subscription is moved. Do I understand correctly that these users will need to be recreated?
- Documentation says that RBAC permissions will be lost. Does this affect only the subscription being moved? Like Owner, Reader, Contributor permissions to subscription?
Any help is much appreciated. Thanks!
azure azure-active-directory
We want to move Azure subscription resources, which are already hosting production system to another Azure AD tenant (using "Change Directory" feature).
I would like to know:
- If resources will continue to work will this this move is being made?
- We have locally defined users and groups in tenant from which subscription is moved. Do I understand correctly that these users will need to be recreated?
- Documentation says that RBAC permissions will be lost. Does this affect only the subscription being moved? Like Owner, Reader, Contributor permissions to subscription?
Any help is much appreciated. Thanks!
azure azure-active-directory
azure azure-active-directory
edited Nov 12 '18 at 15:10
Gaurav Mantri
71.8k8108134
71.8k8108134
asked Nov 12 '18 at 14:29
Peteris
31
31
The move affects rbac roles across all resources in the sub. They refer to user ids that are unique to the tenant so can't be moved.
– juunas
Nov 12 '18 at 14:38
Users need to be able to login to the new tenant access the subscription. Whether you create new users for them or add them as guests from another tenant is up to you.
– juunas
Nov 12 '18 at 14:39
add a comment |
The move affects rbac roles across all resources in the sub. They refer to user ids that are unique to the tenant so can't be moved.
– juunas
Nov 12 '18 at 14:38
Users need to be able to login to the new tenant access the subscription. Whether you create new users for them or add them as guests from another tenant is up to you.
– juunas
Nov 12 '18 at 14:39
The move affects rbac roles across all resources in the sub. They refer to user ids that are unique to the tenant so can't be moved.
– juunas
Nov 12 '18 at 14:38
The move affects rbac roles across all resources in the sub. They refer to user ids that are unique to the tenant so can't be moved.
– juunas
Nov 12 '18 at 14:38
Users need to be able to login to the new tenant access the subscription. Whether you create new users for them or add them as guests from another tenant is up to you.
– juunas
Nov 12 '18 at 14:39
Users need to be able to login to the new tenant access the subscription. Whether you create new users for them or add them as guests from another tenant is up to you.
– juunas
Nov 12 '18 at 14:39
add a comment |
1 Answer
1
active
oldest
votes
- So long as all your resource support being moved then yes they should continue to work.
- These users will remain in your existing tenant, they will not exist in your new tenant, you will need to create them
- All RBAC roles on the subscription being moved will need to be recreated. Other subscriptions that are not being moved will not be affected
1. Are there really resources that are not supported? This article does not mention that docs.microsoft.com/en-us/azure/active-directory/fundamentals/… 2. Clear 3. Clear
– Peteris
Nov 12 '18 at 19:37
No I believe your correct, for a Tennant move you should be good for any resource. There are some restrictions on resources that can be moved between subs.
– Sam Cogan
Nov 12 '18 at 19:38
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264291%2fmove-azure-subscription-to-another-tenant%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
- So long as all your resource support being moved then yes they should continue to work.
- These users will remain in your existing tenant, they will not exist in your new tenant, you will need to create them
- All RBAC roles on the subscription being moved will need to be recreated. Other subscriptions that are not being moved will not be affected
1. Are there really resources that are not supported? This article does not mention that docs.microsoft.com/en-us/azure/active-directory/fundamentals/… 2. Clear 3. Clear
– Peteris
Nov 12 '18 at 19:37
No I believe your correct, for a Tennant move you should be good for any resource. There are some restrictions on resources that can be moved between subs.
– Sam Cogan
Nov 12 '18 at 19:38
add a comment |
- So long as all your resource support being moved then yes they should continue to work.
- These users will remain in your existing tenant, they will not exist in your new tenant, you will need to create them
- All RBAC roles on the subscription being moved will need to be recreated. Other subscriptions that are not being moved will not be affected
1. Are there really resources that are not supported? This article does not mention that docs.microsoft.com/en-us/azure/active-directory/fundamentals/… 2. Clear 3. Clear
– Peteris
Nov 12 '18 at 19:37
No I believe your correct, for a Tennant move you should be good for any resource. There are some restrictions on resources that can be moved between subs.
– Sam Cogan
Nov 12 '18 at 19:38
add a comment |
- So long as all your resource support being moved then yes they should continue to work.
- These users will remain in your existing tenant, they will not exist in your new tenant, you will need to create them
- All RBAC roles on the subscription being moved will need to be recreated. Other subscriptions that are not being moved will not be affected
- So long as all your resource support being moved then yes they should continue to work.
- These users will remain in your existing tenant, they will not exist in your new tenant, you will need to create them
- All RBAC roles on the subscription being moved will need to be recreated. Other subscriptions that are not being moved will not be affected
answered Nov 12 '18 at 16:43
Sam Cogan
1,74762763
1,74762763
1. Are there really resources that are not supported? This article does not mention that docs.microsoft.com/en-us/azure/active-directory/fundamentals/… 2. Clear 3. Clear
– Peteris
Nov 12 '18 at 19:37
No I believe your correct, for a Tennant move you should be good for any resource. There are some restrictions on resources that can be moved between subs.
– Sam Cogan
Nov 12 '18 at 19:38
add a comment |
1. Are there really resources that are not supported? This article does not mention that docs.microsoft.com/en-us/azure/active-directory/fundamentals/… 2. Clear 3. Clear
– Peteris
Nov 12 '18 at 19:37
No I believe your correct, for a Tennant move you should be good for any resource. There are some restrictions on resources that can be moved between subs.
– Sam Cogan
Nov 12 '18 at 19:38
1. Are there really resources that are not supported? This article does not mention that docs.microsoft.com/en-us/azure/active-directory/fundamentals/… 2. Clear 3. Clear
– Peteris
Nov 12 '18 at 19:37
1. Are there really resources that are not supported? This article does not mention that docs.microsoft.com/en-us/azure/active-directory/fundamentals/… 2. Clear 3. Clear
– Peteris
Nov 12 '18 at 19:37
No I believe your correct, for a Tennant move you should be good for any resource. There are some restrictions on resources that can be moved between subs.
– Sam Cogan
Nov 12 '18 at 19:38
No I believe your correct, for a Tennant move you should be good for any resource. There are some restrictions on resources that can be moved between subs.
– Sam Cogan
Nov 12 '18 at 19:38
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264291%2fmove-azure-subscription-to-another-tenant%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The move affects rbac roles across all resources in the sub. They refer to user ids that are unique to the tenant so can't be moved.
– juunas
Nov 12 '18 at 14:38
Users need to be able to login to the new tenant access the subscription. Whether you create new users for them or add them as guests from another tenant is up to you.
– juunas
Nov 12 '18 at 14:39