How to transfer App Registration between two Microsoft Entra IDs (formerly Azure Directory)

Question

How to transfer App Registration between two Microsoft Entra IDs (formerly Azure Directory)

Valentin Kirilov 20

tl;dr I need assistance in transferring my App Registrations from one Microsoft Entra ID to another without downtime, because they need domain verification, and currently, we can't have a single domain associated with more than one Azure Directory.

I've been developing Microsoft Teams applications for almost 2 years already, and so far, I have used a "Microsoft 365 developer subscription" to serve that process. It was all good until this week, when I noticed my subscription was not auto-renewed (as it usually happens every 3 months), and was disabled (meaning, it will be deleted in a month).

Automatically associated with this developer subscription, there is a Microsoft Entra ID/Azure Directory in Microsoft Azure, where my App Registrations live. I'm using Agents Toolkit (formerly known as Microsoft Teams Toolkit), which provisions my app into this Azure account. And the app is distributed globally and already published on Microsoft AppSource, so many teams are using it already.

Now, when I saw that my "Microsoft 365 developer subscription" was disabled and will be deleted soon, I'm afraid that the associated Azure account will follow and will be deleted as well. Meaning, my app will also follow the same destiny. and go into the trash. So, I need to transfer it to another Azure Directory before that.

My plan was the following:

Create new App Registrations in a new Azure directory (I already have such where I pay for Azure services), and use the manifest from the developer Azure directory, to replicate the same config for the app
Ensure the app is working fine, with the new App Registration
Submit my app in Partner Center, as a version update (and point the IDs to the new App Registrations)

And hope that the process will be smooth, and won't cause any downtime and loss of users.

However... I experience issues on the first step already. I can't transfer the App Registrations between the Azure directories, because my app requires custom domain verification, which is currently failing.

Turns out, that a custom domain can be associated with a single Azure directory at a moment, meaning that I should delete the custom domain from my Developer tenant, associate it with the new Azure directory, verify that everything works, and submit the app for a review (which might take more than a month, compared to my experience so far).

And my current application will stop working during this period, when I delete the custom domain associated with the developer Azure directory.

So, I'm searching for suggestions or ideas on how to perform this process properly.

I would be happy if you could tell me that my Azure Directory won't be automatically deleted alongside the Microsoft 365 Developer subscription that is already disabled (but I doubt that)
Is it possible to ask Azure support to perform the transfer of the Azure Directory from the disabled Microsoft 365 Developer tenant to another one (and have everything working as expected). I need the App Registrations + Custom Domain to saved.
Can I perform the operation safely, if I buy one more domain and use it temporarily? Or it will only overcomplicate the process, and require creating a new App Registration one more time, when I have performed the transfer safely, and I delete the original domain from the old tenant, and try to create it in the new one.

Or any other ideas on how to perform this on my own, without huge downtime, will be highly appreciated.

Answer accepted by question author

1 additional answer

Your answer

Answer 1

Praveen Chivarla 2,005 Microsoft External Staff Moderator

Hi Valentin,

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

Transferring App Registrations between two Microsoft Entra ID (Azure AD) tenants requires careful planning because this operation is not directly supported. Each App Registration is bound to the tenant where it was originally created, and app configurations cannot simply be moved or transferred with their custom domain attached.

Please note the following important points:

App Registrations Are Tenant-Specific: App Registrations belong to the specific Azure AD tenant and cannot be transferred directly between tenants. You need to recreate the App Registration manually in the new tenant.
Custom Domain Limitations: A custom domain can only be verified in one tenant at a time. So before associating it with a new tenant, you must remove it from the old tenant. This can cause downtime during the transition because the domain verification process takes time.
Use a Temporary Domain to Minimize Downtime: To avoid downtime while moving your app registrations, you can use a temporary domain in the new tenant. You create and configure your apps using this temporary domain, verify functionality, and after successful testing, switch to the original domain when it’s free.
Directory Deletion and Subscription Expiry: Deactivating or disabling a Microsoft 365 Developer subscription does not automatically delete your Azure AD tenant. However, it is best to check with Microsoft support about your specific tenant’s lifecycle to avoid accidental data loss.
Minimize Downtime with Careful Planning: Replicate your app registration settings precisely in the new tenant. Double-check redirect URIs, permissions, and API settings. This can help ensure a smooth migration with minimal impact on your users.

Useful References:

I hope this information is helpful. Please feel free to reach out if you have any further questions. If the answer is helpful, please click "Accept Answer" and kindly Upvote it.

Valentin Kirilov 20 Reputation points

2025-11-10T18:49:57.9066667+00:00
Thanks for your precise answer and the provided information!

I was afraid that such migration won't be possible because of having the App Registrations bound to the Tenant ID, but I was hoping that the Azure Support team might be able to transfer them. And as you said, the only way to achieve this goal is via a temporary second domain, so I can avoid the downtime (which is very important).

If this is the only way to achieve that, I have a few more follow-up questions regarding the way the users will feel the migration.

My app is a Microsoft Teams application with a Bot and Tab. Considering the scenario that I recreate the App Registrations in the new tenant, following exactly the same configurations as the old apps, and I do verify they work as expected.

As a next step, I should resubmit the app into the AppSource marketplace, referencing the IDs of the new Tab app and Bot app (they're part of the manifest).

Will this affect the existing users in any way?

Should they reinstall the app, or will it be done automatically, updating to the latest version of the manifest and not requiring any changes on their end?

Should the users need to reclaim the consent modal, providing permission for the app to work as expected (SSO/etc)?

Will the Bot instance for the app remain the same, or a new conversation will be started (because of the new ID)?

Will the Tab application added to group chats/channels remain operational, or should users have to re-add the app to every chat/channel?

Will the Bot that was invited to group chats/channels remain operational, or should it be re-invited (because of the new Bot ID)?

Your previous answer was very helpful, so I'll need to plan the migration very carefully, and I need to collect as much information as possible. Any further guidance on the topic will be highly appreciated, thank you!

And again, all this effort might not be necessary if I know for sure that the Azure Directory associated with the disabled Developer Subscription doesn't get automatically deleted, and remain operational.
Praveen Chivarla 2,005 Reputation points Microsoft External Staff Moderator

2025-11-11T08:19:22.8333333+00:00
Hi Valentin,

Thank you for sharing the additional information.

As per our understanding, you are planning to transfer your Microsoft Teams application’s App Registrations (including Bot and Tab apps) from one Microsoft Entra ID tenant to another because your current Microsoft 365 Developer subscription is disabled. You want to understand the impact of this migration on your users and confirm if the Azure Directory will remain operational after the subscription is disabled.

Important points based on the latest Microsoft documentation and scenarios:

App Registrations Are Tenant Bound and Cannot Be Transferred Directly: App Registrations belong exclusively to their original Azure AD tenant and cannot be migrated directly to another tenant. You must recreate your app registrations manually in the new tenant and replicate their configuration.

Custom Domains Can Be Verified in Only One Tenant: To verify your custom domain in the new tenant, you must first remove it from the old tenant. This may cause downtime, which can be mitigated by using a temporary domain temporarily in the new tenant for testing and validation.

Azure Directory and Subscription Relationship: The Azure AD/Entra ID tenant usually does not get automatically deleted immediately when a Microsoft 365 Developer subscription is disabled but it’s recommended to confirm the exact retention policies with Microsoft Support to avoid surprises.

Impact on Users Post Migration and App Submission:

Will users need to reinstall the app? Yes, depending on the app deployment mode, users might have to reinstall or update the app to get the new version reflecting the new App Registration IDs, especially if the manifests change.

Will consent need to be re-granted? Yes, since the new App Registrations have different IDs, users or admins will likely need to re-consent to permissions required by the app.

Will ongoing Bot conversations persist? No, Bot instances are tied to the Bot ID. New IDs mean new Bot instances, so existing conversations typically will not carry over.

Will Tabs remain in group chats/channels without re-adding? No, users usually need to re-add Tabs linked to the new app registration since IDs and contexts change.

Will Bot presence in teams/chat persist or will it require re-inviting? The Bot will need to be re-invited due to new identity in the new tenant.

Recommended Approach for Minimal Customer Impact:

Conduct thorough testing using a temporary domain.

Communicate migration plans and user actions clearly to your end users.

Prepare for re-consent flows and possible app reinstallation or re-invitation processes.

References for Further Reading and Planning:

Register an application in Microsoft Entra ID

Migrating applications between Azure AD tenants

Microsoft Teams app submission

If you need any further assistance or have additional questions, please feel free to ask. If this answer helps, kindly click Accept Answer and Upvote it.
Valentin Kirilov 20 Reputation points

2025-11-11T18:26:34.6133333+00:00

Thank you very much Praveen, for your time and the detailed answer!

So basically, it sounds like I'll start with entirely new app, no matter what I do. I don't like it, but i's good to know all this information and try to plan it ahead of the migration.

My last hope is that Azure Directory shouldn’t be deleted automatically alongside the Developer Subscription, as you said, but I’ll need to check this with the support team. I’m a bit afraid they won’t provide me with accurate information, as they weren’t able to explain why the subscription wasn’t renewed initially, nor could they renew it themselves. However, this is my only hope, so I’ll try to contact them again.

Otherwise, I need to start the transfer of the apps, and resubmit the new manifest to the Partner Center, so my app get a review in time (because usually it takes time).

Again, thank you very much for all the information you provided! Much appreciated!
Valentin Kirilov 20 Reputation points

2025-11-14T19:23:53.02+00:00
I have a statement from the support team, it seems like the Azure Directory that comes with the Developer Subscription, will be also deleted alongside it. Very unfortunate.

What happens to the associated Azure Directory (Microsoft Entra ID)? The Azure AD tenant linked to your developer subscription follows the same lifecycle:

Day 0: Subscription expires.

Next 30 days: Admin access remains for backup or migration.

Day 60: The subscription and all associated data—including the Azure AD tenant—are permanently deleted. This includes users, app registrations, and configurations.
Praveen Chivarla 2,005 Reputation points Microsoft External Staff Moderator

2025-11-18T10:09:57.2366667+00:00

Hi Valentin,

Transferring App Registrations between Microsoft Entra ID tenants is not directly supported because each registration is bound to its original tenant and linked to custom domains that can be verified in only one tenant at a time. To avoid downtime, you’ll need to recreate app registrations manually in the new tenant and may use a temporary domain during the transition. This process requires careful replication of app settings, redirect URIs, and permissions.

After migration, users might need to reinstall apps, re-consent to permissions, and re-invite bots due to new app IDs. While the Azure Directory tied to a disabled Microsoft 365 Developer subscription usually isn’t deleted immediately, confirming tenant retention policies with Microsoft Support is recommended. Thorough planning and communication with users are key to minimizing impact during the migration.

Answer 2

Transferring App Registrations between Microsoft Entra IDs (formerly Azure Active Directory) can be challenging, especially when dealing with custom domain verification and the potential for downtime. Here are some insights based on your situation:

Azure Directory Deletion: If your Microsoft 365 Developer subscription is disabled, it does not automatically mean that the associated Azure Directory will be deleted. However, it is important to check the specific policies regarding the retention of Azure Directories linked to subscriptions, as these can vary.
Azure Support for Transfers: You can reach out to Azure Support to inquire about the possibility of transferring your App Registrations and custom domain from the disabled Microsoft 365 Developer tenant to another Azure Directory. They may provide options or processes that are not publicly documented.
Using a Temporary Domain: Acquiring a temporary domain could be a viable workaround. You can associate this new domain with your new Azure Directory, verify it, and then replicate your App Registrations. Once everything is functioning correctly, you can switch back to your original domain after you have removed it from the developer tenant. This approach may help avoid downtime, but it requires careful management to ensure that the transition is seamless.
Alternative Approaches: If the custom domain verification is a significant hurdle, consider adopting a multi-directory architecture using Azure Lighthouse. This allows you to manage resources across directories without needing to transfer them directly.

Overall, careful planning and possibly engaging with Azure Support will be crucial in executing this transfer without significant downtime or loss of functionality for your applications.

Share via

How to transfer App Registration between two Microsoft Entra IDs (formerly Azure Directory)

1 additional answer

Your answer