Hello Chinnaraja V
When planning a tenant‑to‑tenant migration, the key point is whether you are moving the Azure subscription or only moving workloads.
- If the Azure subscription is transferred to another Microsoft Entra tenant:
If the Azure subscription is transferred to another Microsoft Entra tenant The ExpressRoute circuit moves automatically with the subscription. ExpressRoute is not listed as an impacted or unsupported service during a directory (tenant) transfer. The only required follow‑up action is to re‑create Azure RBAC role assignments, because all RBAC assignments are removed by design when a subscription changes tenants.
To get a list of some of the Azure resources that are impacted when you transfer a subscription, you can also run a query in Azure Resource Graph. For a sample query, see List impacted resources when transferring an Azure subscription.
- If the subscription is not transferred:
The ExpressRoute circuit remains in the original tenant (Tenant A). Microsoft allows workloads in another tenant (Tenant B) to use the same circuit by using ExpressRoute authorizations, which can span subscriptions, tenants, and enrollments. No circuit recreation is required.
ExpressRoute authorizations can span subscription, tenant, and enrollment boundaries with no extra configuration required. Connectivity and bandwidth charges for the dedicated circuit gets applied to the ExpressRoute circuit owner and all virtual networks share the same bandwidth.
For more information, see sharing an ExpressRoute circuit across multiple subscriptions.
Reference: https://learn.microsoft.com/en-us/azure/expressroute/expressroute-howto-linkvnet-arm?tabs=maximum
ExpressRoute has no Entra ID dependency for network traffic, but it does rely on Entra ID for RBAC‑based management. This is why ExpressRoute is unaffected during tenant transfer from a connectivity perspective, while access permissions must be reconfigured afterward.
If you have any other queries, please do let us know.
Thanks,
Suchitra.