I cannot move Foundry to a new subscription

Hi VNJoe,

Thanks for raising this. Based on the current behavior and existing guidance around Azure AI Foundry and AI Services, moving a Foundry (or Foundry‑backed AI Services) resource directly between subscriptions is not supported today. Even when permissions are correct, these resources are tightly bound to the original subscription for billing, quota, and internal identity reasons, which is why the move operation fails at the platform level.

At the moment:

• Azure Support cannot manually move an existing Foundry resource to another subscription.
• The supported path is to recreate the Foundry hub/project and associated AI resources in the target subscription and then reconfigure them there.
• This is consistent with other Azure AI resource limitations where cross‑subscription moves aren’t allowed due to commercial and backend constraints.

Recommended approach

1. Document your existing Foundry setup (projects, connected resources, model deployments, quotas, and configurations).
2. Create a new Foundry instance in the destination subscription.
3. Recreate the required AI Services and redeploy models/configurations as needed.

I understand this isn’t ideal, especially for mature environments, but at this time recreation is the only supported option. If Microsoft introduces subscription‑move support in the future, it would be reflected in Foundry documentation or release notes.

Hope this helps clarify the current limitation. if the issue persists after these checks. If you have any remaining questions or need additional details, I’ll be glad to provide further clarification or guidance.

If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

Thankyou!