Azuredevops subscription Transfer

Question

Azuredevops subscription Transfer

Srihari Papanaboyina 20

we want to move Azuredevops Subscription Transfer from one company to another , what are the challenges will may get post subscription Transfer.

Srihari Papanaboyina 20 Reputation points

2026-07-17T06:12:21.0266667+00:00
we need insights on below two

Transferring only the Azure subscription,

Moving the subscription to a different Microsoft Entra tenant
Srihari Papanaboyina 20 Reputation points

2026-07-17T06:18:49.5366667+00:00

When carrying out a company merger, what’s the best approach for taking control of Azure DevOps(Saas) to the target company?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-17T22:13:30.12+00:00
Hello Srihari Papanaboyina,

For a company merger, the best approach depends on how you plan to manage Azure DevOps after the merger.

If you want to continue using the existing Azure DevOps organization, you can connect it to the target company's Microsoft Entra tenant. Before making this change, ensure there is at least one Project Collection Administrator (PCA) or Organization Owner in the target tenant to avoid losing administrative access.

If the intention is to consolidate into an existing Azure DevOps organization in the target company, there is no supported method to transfer or merge Azure DevOps organizations. In this case, Azure DevOps assets (such as repositories, pipelines, boards, and test artifacts) would need to be migrated separately using the appropriate migration tools or APIs.

Could you let us know which approach you're planning to take? That will help us provide guidance specific to your scenario.

References:

https://learn.microsoft.com/azure/devops/organizations/accounts/connect-organization-to-azure-ad

https://learn.microsoft.com/azure/devops/migrate/
Srihari Papanaboyina 20 Reputation points

2026-07-18T07:26:11.7033333+00:00
We need clear insights on the two items below:

Transferring only the Azure subscription,

Moving the subscription to a different Microsoft Entra tenant

Please share the pros and consequences after the transfer, with no assumptions—just clear information. I’d recommend your first approach. Since it’s the same organization, we need to move the entire organization toward the target.
Srihari Papanaboyina 20 Reputation points

2026-07-19T09:05:36.41+00:00

moving the Azure DevOps organization to the target company's Microsoft Entra tenant, please let us know. We need guidance specific to this scenario?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-19T16:15:03.6+00:00
Hello Srihari Papanaboyina,

Thank you for confirming.

When moving an existing Azure DevOps organization to the target company's Microsoft Entra tenant during a merger, here are the key considerations:

Existing users from the original tenant are removed from the organization unless they also exist in the target tenant or are re-added afterward.

Azure DevOps permissions are retained, but user identities must exist in the target tenant for those permissions to apply.

Any service connections that rely on Microsoft Entra ID should be reviewed and reauthorized if they reference resources or identities from the original tenant.

Review applications, service principals, and managed identities used by your pipelines, as they may need to be recreated or updated after the tenant change.

Validate integrations with Azure resources, such as Azure subscriptions and Key Vault, to ensure authentication and access continue to work as expected.

It is recommended to perform the tenant connection during a maintenance window and verify user access, pipelines, and integrations before resuming normal operations.

For detailed prerequisites and post-migration considerations, please refer to:

https://learn.microsoft.com/azure/devops/organizations/accounts/connect-organization-to-azure-ad
Srihari Papanaboyina 20 Reputation points

2026-07-19T16:20:10.35+00:00

So , what is the plan from starting onwards, we need to raise any request with Microsoft for this?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-19T16:24:51.6366667+00:00
Hello Srihari Papanaboyina,

Thank you for your question.

Connecting an existing Azure DevOps organization to a different Microsoft Entra tenant is typically a self-service process. In most cases, you do not need to raise a Microsoft support request, provided you meet the documented prerequisites and have the required administrative permissions.

At a high level, the process is:

Review the current environment

Identify the Azure DevOps organization that will be retained.

Review users, groups, service connections, pipelines, and any integrations that rely on Microsoft Entra ID.

Prepare the target Microsoft Entra tenant

Ensure the required administrators and users exist in the target tenant.

Verify that you have the necessary administrative permissions before starting the tenant connection.

Connect the Azure DevOps organization

Connect the existing Azure DevOps organization to the target Microsoft Entra tenant by following the documented procedure.

Validate the organization

Verify that users can sign in and access projects.

Review service connections and validate access to Azure resources.

Validate pipelines, deployments, and other Microsoft Entra ID-based integrations.

Update any identity-based configurations if required.

If you encounter issues during the tenant connection or are unable to complete the process, you can then raise a Microsoft support request for further assistance.

For the detailed prerequisites and step-by-step guidance, please refer to:

https://learn.microsoft.com/azure/devops/organizations/accounts/connect-organization-to-azure-ad
Srihari Papanaboyina 20 Reputation points

2026-07-19T16:29:20.7033333+00:00

If I do Microsoft tenant transfer or Azure subscription transfer,can I raise request to Microsoft on this ?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-19T16:31:23.98+00:00
Hello Srihari Papanaboyina,

Yes, you can raise a Microsoft support request if you need assistance with either scenario.

Azure subscription transfer: If you have questions about the transfer process or encounter issues during the transfer, you can create an Azure support request through the Azure portal.

Connecting an Azure DevOps organization to a different Microsoft Entra tenant: This is a self-service operation. Microsoft does not perform the tenant connection on your behalf. However, if you encounter issues while following the documented procedure, you can raise a Microsoft support request for assistance.

For guidance, please refer to the following documentation:

Azure subscription transfer: https://learn.microsoft.com/azure/cost-management-billing/manage/billing-subscription-transfer

Connect an Azure DevOps organization to Microsoft Entra ID: https://learn.microsoft.com/azure/devops/organizations/accounts/connect-organization-to-azure-ad
Srihari Papanaboyina 20 Reputation points

2026-07-19T16:34:19.1433333+00:00

I want to expect here zero downtime , what is the best strategy to follow?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-19T16:36:28.46+00:00

Hello Srihari Papanaboyina,

A zero-downtime transition cannot be guaranteed because changing the Microsoft Entra tenant affects authentication and identity-based access.

To minimize the impact, the recommended approach is to perform the change in phases rather than all at once. For example, complete the Azure subscription transfer first, verify that all Azure resources are functioning as expected, and then connect the Azure DevOps organization to the target Microsoft Entra tenant. This allows each step to be validated independently and reduces the overall risk.

Planning the change during a maintenance window is the recommended approach, as it provides time to address any unexpected issues before users resume normal operations.
Srihari Papanaboyina 20 Reputation points

2026-07-19T16:54:53.86+00:00

Do you have any plan step by step to follow?

Answer accepted by question author

Christos Panagiotidis 3,551

Treat these as separate changes. Moving billing ownership alone does not change the Entra directory or Azure DevOps organization, so repositories and Boards remain. Changing the subscription directory removes Azure RBAC assignments and custom roles; service principals, managed identities, Key Vault access, and pipeline service connections can break.

For the merger, keep the existing Azure DevOps organization and connect it to the target company’s Entra tenant; there is no supported organization merge. Before switching, ensure a target-tenant member is a Project Collection Administrator, export users, map identities, invite required guests, and request SSH-key cleanup through Support. Microsoft recommends Support when more than 100 users must be remapped.

Freeze deployments during the change. Export RBAC and service-connection inventories, then validate sign-in, groups, licenses, pipelines, agent pools, feeds, extensions, and federated credentials. If transferring billing only, leave the directory unchanged. If changing directory, re-create Azure roles and identities before production deployments resume.

Srihari Papanaboyina 20 Reputation points

2026-07-18T07:46:06.0366667+00:00
Do you have any Detailed plan on these two?

Transferring only the Azure subscription,

Moving the subscription to a different Microsoft Entra tenant

1 additional answer

Your answer

Srihari Papanaboyina 20 Reputation points

2026-07-17T06:12:21.0266667+00:00

we need insights on below two

Transferring only the Azure subscription,

Moving the subscription to a different Microsoft Entra tenant
Srihari Papanaboyina 20 Reputation points

2026-07-17T06:18:49.5366667+00:00

When carrying out a company merger, what’s the best approach for taking control of Azure DevOps(Saas) to the target company?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-17T22:13:30.12+00:00

Hello Srihari Papanaboyina,

For a company merger, the best approach depends on how you plan to manage Azure DevOps after the merger.

If you want to continue using the existing Azure DevOps organization, you can connect it to the target company's Microsoft Entra tenant. Before making this change, ensure there is at least one Project Collection Administrator (PCA) or Organization Owner in the target tenant to avoid losing administrative access.

If the intention is to consolidate into an existing Azure DevOps organization in the target company, there is no supported method to transfer or merge Azure DevOps organizations. In this case, Azure DevOps assets (such as repositories, pipelines, boards, and test artifacts) would need to be migrated separately using the appropriate migration tools or APIs.

Could you let us know which approach you're planning to take? That will help us provide guidance specific to your scenario.

References:

https://learn.microsoft.com/azure/devops/organizations/accounts/connect-organization-to-azure-ad

https://learn.microsoft.com/azure/devops/migrate/
Srihari Papanaboyina 20 Reputation points

2026-07-18T07:26:11.7033333+00:00

We need clear insights on the two items below:

Transferring only the Azure subscription,

Moving the subscription to a different Microsoft Entra tenant

Please share the pros and consequences after the transfer, with no assumptions—just clear information. I’d recommend your first approach. Since it’s the same organization, we need to move the entire organization toward the target.
Srihari Papanaboyina 20 Reputation points

2026-07-19T09:05:36.41+00:00

moving the Azure DevOps organization to the target company's Microsoft Entra tenant, please let us know. We need guidance specific to this scenario?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-19T16:15:03.6+00:00

Hello Srihari Papanaboyina,

Thank you for confirming.

When moving an existing Azure DevOps organization to the target company's Microsoft Entra tenant during a merger, here are the key considerations:

Existing users from the original tenant are removed from the organization unless they also exist in the target tenant or are re-added afterward.

Azure DevOps permissions are retained, but user identities must exist in the target tenant for those permissions to apply.

Any service connections that rely on Microsoft Entra ID should be reviewed and reauthorized if they reference resources or identities from the original tenant.

Review applications, service principals, and managed identities used by your pipelines, as they may need to be recreated or updated after the tenant change.

Validate integrations with Azure resources, such as Azure subscriptions and Key Vault, to ensure authentication and access continue to work as expected.

It is recommended to perform the tenant connection during a maintenance window and verify user access, pipelines, and integrations before resuming normal operations.

For detailed prerequisites and post-migration considerations, please refer to:

https://learn.microsoft.com/azure/devops/organizations/accounts/connect-organization-to-azure-ad
Srihari Papanaboyina 20 Reputation points

2026-07-19T16:20:10.35+00:00

So , what is the plan from starting onwards, we need to raise any request with Microsoft for this?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-19T16:24:51.6366667+00:00

Hello Srihari Papanaboyina,

Thank you for your question.

Connecting an existing Azure DevOps organization to a different Microsoft Entra tenant is typically a self-service process. In most cases, you do not need to raise a Microsoft support request, provided you meet the documented prerequisites and have the required administrative permissions.

At a high level, the process is:

Review the current environment

Identify the Azure DevOps organization that will be retained.

Review users, groups, service connections, pipelines, and any integrations that rely on Microsoft Entra ID.

Prepare the target Microsoft Entra tenant

Ensure the required administrators and users exist in the target tenant.

Verify that you have the necessary administrative permissions before starting the tenant connection.

Connect the Azure DevOps organization

Connect the existing Azure DevOps organization to the target Microsoft Entra tenant by following the documented procedure.

Validate the organization

Verify that users can sign in and access projects.

Review service connections and validate access to Azure resources.

Validate pipelines, deployments, and other Microsoft Entra ID-based integrations.

Update any identity-based configurations if required.

If you encounter issues during the tenant connection or are unable to complete the process, you can then raise a Microsoft support request for further assistance.

For the detailed prerequisites and step-by-step guidance, please refer to:

https://learn.microsoft.com/azure/devops/organizations/accounts/connect-organization-to-azure-ad
Srihari Papanaboyina 20 Reputation points

2026-07-19T16:29:20.7033333+00:00

If I do Microsoft tenant transfer or Azure subscription transfer,can I raise request to Microsoft on this ?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-19T16:31:23.98+00:00

Hello Srihari Papanaboyina,

Yes, you can raise a Microsoft support request if you need assistance with either scenario.

Azure subscription transfer: If you have questions about the transfer process or encounter issues during the transfer, you can create an Azure support request through the Azure portal.

Connecting an Azure DevOps organization to a different Microsoft Entra tenant: This is a self-service operation. Microsoft does not perform the tenant connection on your behalf. However, if you encounter issues while following the documented procedure, you can raise a Microsoft support request for assistance.

For guidance, please refer to the following documentation:

Azure subscription transfer: https://learn.microsoft.com/azure/cost-management-billing/manage/billing-subscription-transfer

Connect an Azure DevOps organization to Microsoft Entra ID: https://learn.microsoft.com/azure/devops/organizations/accounts/connect-organization-to-azure-ad
Srihari Papanaboyina 20 Reputation points

2026-07-19T16:34:19.1433333+00:00

I want to expect here zero downtime , what is the best strategy to follow?
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-07-19T16:36:28.46+00:00

Hello Srihari Papanaboyina,

A zero-downtime transition cannot be guaranteed because changing the Microsoft Entra tenant affects authentication and identity-based access.

To minimize the impact, the recommended approach is to perform the change in phases rather than all at once. For example, complete the Azure subscription transfer first, verify that all Azure resources are functioning as expected, and then connect the Azure DevOps organization to the target Microsoft Entra tenant. This allows each step to be validated independently and reduces the overall risk.

Planning the change during a maintenance window is the recommended approach, as it provides time to address any unexpected issues before users resume normal operations.
Srihari Papanaboyina 20 Reputation points

2026-07-19T16:54:53.86+00:00

Do you have any plan step by step to follow?
Srihari Papanaboyina 20 Reputation points

2026-07-18T07:46:06.0366667+00:00

Do you have any Detailed plan on these two?

Transferring only the Azure subscription,

Moving the subscription to a different Microsoft Entra tenant

Answer 1

Hello Srihari Papanaboyina,

Thank you for the clarification.

Please find a comparison of the two scenarios below:

Scenario	Impact
Transfer only the Azure subscription	The Azure DevOps organization and its data (Repos, Boards, Pipelines, Test Plans, and work items) remain unchanged. After the transfer, verify that your service connections still have the required permissions to access the Azure subscription and validate any pipelines that deploy to Azure resources.
Move the subscription to a different Microsoft Entra tenant	The Azure DevOps organization and its data remain unchanged, but identity-based integrations require updates. Service principals and managed identities typically need to be recreated, service connections reauthorized or recreated, and RBAC permissions reassigned in the destination tenant. Pipelines and applications that authenticate with Microsoft Entra ID should also be validated after the move.

For a company merger, if the Azure DevOps organization will continue to be used and only the Azure subscription ownership is changing, the impact on Azure DevOps is generally limited to validating access and Azure integrations. If the subscription is also being moved to a different Microsoft Entra tenant, plan for the additional work required to reconfigure identity-based authentication and permissions.

If your merger plan also includes moving the Azure DevOps organization to the target company's Microsoft Entra tenant, please let us know. We can provide guidance specific to that scenario.

References