Associate or add an Azure subscription to your Azure Active Directory tenant
An Azure subscription has a trust relationship with Azure Active Directory (Azure AD). A subscription trusts Azure AD to authenticate users, services, and devices.
Multiple subscriptions can trust the same Azure AD directory. Each subscription can only trust a single directory.
One or more Azure subscriptions can establish a trust relationship with an instance of Azure Active Directory (Azure AD) in order to authenticate and authorize security principals and devices against Azure services. When a subscription expires, the trusted instance of the Azure AD service remains, but the security principals lose access to Azure resources.
When a user signs up for a Microsoft cloud service, a new Azure AD tenant is created and the user is made a member of the Global Administrator role. However, when an owner of a subscription joins their subscription to an existing tenant, the owner isn't assigned to the Global Administrator role.
All of your users have a single home directory for authentication. Your users can also be guests in other directories. You can see both the home and guest directories for each user in Azure AD.
When you associate a subscription with a different directory, users that have roles assigned using Azure role-based access control lose their access. Classic subscription administrators, including Service Administrator and Co-Administrators, also lose access.
Moving your Azure Kubernetes Service (AKS) cluster to a different subscription, or moving the cluster-owning subscription to a new tenant, causes the cluster to lose functionality due to lost role assignments and service principal's rights. For more information about AKS, see Azure Kubernetes Service (AKS).
Before you begin
Before you can associate or add your subscription, do the following tasks:
Review the following list of changes that will occur after you associate or add your subscription, and how you might be affected:
- Users that have been assigned roles using Azure RBAC will lose their access.
- Service Administrator and Co-Administrators will lose access.
- If you have any key vaults, they'll be inaccessible, and you'll have to fix them after association.
- If you have any managed identities for resources such as Virtual Machines or Logic Apps, you must re-enable or recreate them after the association.
- If you have a registered Azure Stack, you'll have to re-register it after association.
- For more information, see Transfer an Azure subscription to a different Azure AD directory.
Sign in using an account that:
- Has an Owner role assignment for the subscription. For information about how to assign the Owner role, see Assign Azure roles using the Azure portal.
- Exists in both the current directory and in the new directory. The current directory is associated with the subscription. You'll associate the new directory with the subscription. For more information about getting access to another directory, see Add Azure Active Directory B2B collaboration users in the Azure portal.
Make sure that you're not using an Azure Cloud Service Providers (CSP) subscription (MS-AZR-0145P, MS-AZR-0146P, MS-AZR-159P), a Microsoft Internal subscription (MS-AZR-0015P), or a Microsoft Azure for Students Starter subscription (MS-AZR-0144P).
To associate an existing subscription to your Azure AD directory, follow these steps:
Sign in and select the subscription you want to use from the Subscriptions page in Azure portal.
Select Change directory.
Review any warnings that appear, and then select Change.
After the directory is changed for the subscription, you'll get a success message.
Select Switch directories on the subscription page to go to your new directory.
It can take several hours for everything to show up properly. If it seems to be taking too long, check the Global subscription filter. Make sure the moved subscription isn't hidden. You may need to sign out of the Azure portal and sign back in to see the new directory.
Changing the subscription directory is a service-level operation, so it doesn't affect subscription billing ownership. To delete the original directory, you must transfer the subscription billing ownership to a new Account Admin. To learn more about transferring billing ownership, see Transfer ownership of an Azure subscription to another account.
After you associate a subscription to a different directory, you might need to do the following tasks to resume operations:
If you have any key vaults, you must change the key vault tenant ID. For more information, see Change a key vault tenant ID after a subscription move.
If you used system-assigned Managed Identities for resources, you must re-enable these identities. If you used user-assigned Managed Identities, you must re-create these identities. After re-enabling or recreating the Managed Identities, you must re-establish the permissions assigned to those identities. For more information, see What are managed identities for Azure resources?.
If you've registered an Azure Stack using this subscription, you must re-register. For more information, see Register Azure Stack Hub with Azure.
For more information, see Transfer an Azure subscription to a different Azure AD directory.
To create a new Azure AD tenant, see Quickstart: Create a new tenant in Azure Active Directory.
To learn more about how Microsoft Azure controls resource access, see Classic subscription administrator roles, Azure roles, and Azure AD administrator roles.
To learn more about how to assign roles in Azure AD, see Assign administrator and non-administrator roles to users with Azure Active Directory.
Submit and view feedback for