Issue moving Azure Open AI resource to a target subscription

Shauktik Kumar 40 Reputation points Microsoft Employee
2026-05-01T18:37:19.4733333+00:00

I am getting the following failure while trying to move Azure Open AI resource to another subscription. Please investigate and recommend the best solution to make the move happen Resource move validation failed. Please see details. Diagnostic information: timestamp '20260501T034625Z', subscription id [SUBSCRIPTION_ID_REMOVED], tracking id [TRACKING_ID_REMOVED], request correlation id[CORRELATION_ID_REMOVED]. (Code: ResourceMoveProviderValidationFailed) The target subscription [SUBSCRIPTION_ID] is missing quota to perform the resource move: The target subscription [SUBSCRIPTION_ID_REMOVED], does not have enough quota for OpenAI.Standard.gpt-4o, required quota: 230 remaining quota: 150 (Code: TargetMoveSubscriptionNotEligible, Target: Microsoft.CognitiveServices/accounts) (Code: ResourceMoveProviderValidationFailed). Note: PII redacted at support side for customer's confidentiality

Azure OpenAI in Foundry Models

Answer accepted by question author
Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator
2026-05-15T13:02:29.5666667+00:00

Hi Shauktik Kumar,

As discussed, the issue is due to insufficient quota in the target subscription, which is preventing the resource move. A request has already been raised to increase the quota, and I have also checked with the team. They will reach out to you shortly.

If this helps, please take a moment to accept the answer, as it helps increase the visibility of this question for other members of the Microsoft Q and A community.

Please let me know if the issue persists or if you have any further questions.

Thankyou!

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

1 additional answer

Sort by: Most helpful
  1. kagiyama yutaka 5,570 Reputation points
    2026-05-06T04:55:05.34+00:00

    I think the move fails because ARM won’t downsize the pinned gpt‑4o capacity, so raising the dest‑sub’s gpt‑4o quota to at least 230 is the only way to make the move succeed.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.