To continue using your Azure portal and the resources hosted there after moving your domain to another Office 365 tenant, you will need to ensure that your Azure resources are not tied to the original Office 365 tenant. Here are some steps you can take:
- Separate Azure Subscription: Make sure that your Azure resources (web apps, SQL projects) are under a separate Azure subscription that is not linked to the Office 365 tenant from which you are transferring the domain. This way, the Azure resources can remain operational even after the domain transfer.
- Access Management: Ensure that the users who need to manage the Azure resources have the appropriate permissions in the Azure portal. You may need to add users from the new Office 365 tenant to the Azure subscription and assign them roles that allow them to manage the resources.
- Domain Configuration: After transferring the domain, you may need to update any configurations that rely on the domain name, such as connection strings in your web apps or SQL databases. Ensure that these configurations reflect the new domain settings.
- Tenant-to-Tenant Migration: If you are migrating resources between tenants, consider using Microsoft Consulting Services or third-party tools that can assist in tenant-to-tenant migrations, especially if you have complex dependencies between your Azure resources and Office 365 services.
- Documentation and Planning: Review Microsoft's documentation on tenant-to-tenant migrations and ensure that you have a clear plan for how the transition will affect your Azure resources.
By following these steps, you can help ensure that your ongoing projects in Azure remain unaffected by the domain transfer to another Office 365 tenant.