Migration of Outlook and Teams Multi tenant applications

Question

Hello, Following our recent acquisition, we're seeking guidance on migrating our existing in house developed Microsoft Teams and Outlook App Source integrations to their tenant. Our primary concern is maintaining a seamless experience for our extensive external client base. We want to avoid any disruption caused by re-installation or a new app store review process. We would appreciate your insights and support in developing a migration strategy that achieves the following objectives: Transfer of integrations to the parent organization's tenant. Transfer of existing domain which these integration use to the new tenant. Continued functionality and access for our external clients without requiring them to re-install the app. Thank you, Chris

Answer 1

1. Transfer Integrations to the Parent Organization's Tenant:

To transfer your existing integrations to the new tenant, you can use the Teams Developer Portal or the Teams Admin Center to upload and publish your app for the new organization. This process requires approval from your IT admin. By uploading and publishing the app in the new tenant, you ensure that the app is available for all users in the new organization without the need for re-installation.

2. Transfer Existing Domain Used by Integrations to the New Tenant:

If your existing integrations rely on specific domains for functionality, ensure that these domains are updated to point to the new tenant after the migration. This may involve updating configurations within your app manifest or backend services to reflect the new domain settings in the new tenant.

3. Continued Functionality and Access for External Clients:

To ensure continued functionality and access for your external clients without requiring them to re-install the app, you can leverage the multitenant hosting capabilities of the Teams platform. By hosting your app as a multitenant app, you can make it scalable and easily distributable across different organizations.