Issue moving Azure Open AI resource to a target subscription

Question

Issue moving Azure Open AI resource to a target subscription

Shauktik Kumar 20 Microsoft Employee

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 29ec82a5-b0c2-41d9-a056-b40f784250f4 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).

Karnam Venkata Rajeswari 2,390 Reputation points Microsoft External Staff Moderator

2026-05-01T19:41:49.0766667+00:00
Hello @Shauktik Kumar ,

Welcome to Microsoft Q&A .Thank you for reaching out to us.

Based on the validation output, the resource move is failing due to a quota limitation in the target subscription, which is preventing the move from proceeding.

The validation step checks whether the destination subscription can fully support the existing resource configuration before allowing the move. In this case:

The deployed model OpenAI.Standard.gpt-4o requires 230 quota units

The target subscription currently has only 150 quota units available

Because the available quota does not meet the required capacity, the validation fails with the error TargetMoveSubscriptionNotEligible, and the move operation is blocked. This is expected behavior, as resource moves only proceed when all provider-level checks (including quota and supportability) are satisfied.

Alternative options if quota cannot be increased.In some cases, quota requests may not be approved due to regional or capacity constraints. If that occurs, the following options can be considered:

Using a different target subscription - Select a subscription where sufficient quota can be allocated for the required model

Reduce required capacity if applicable - Lower the deployed quota or capacity in the source resource to align with available quota in the target subscription before retrying the move

Recreate the resource in the destination subscription - Provision a new Azure OpenAI resource in a subscription/region with sufficient quota.Then , redeploy required models and update application configurations to point to the new resource

The following references might be helpful , please check them out

Move Azure resources to a new resource group or subscription - Azure Resource Manager | Microsoft Learn

Thank you

2 answers

Your answer

Karnam Venkata Rajeswari 2,390 Reputation points Microsoft External Staff Moderator

2026-05-01T19:41:49.0766667+00:00

Hello @Shauktik Kumar ,

Welcome to Microsoft Q&A .Thank you for reaching out to us.

Based on the validation output, the resource move is failing due to a quota limitation in the target subscription, which is preventing the move from proceeding.

The validation step checks whether the destination subscription can fully support the existing resource configuration before allowing the move. In this case:

The deployed model OpenAI.Standard.gpt-4o requires 230 quota units

The target subscription currently has only 150 quota units available

Because the available quota does not meet the required capacity, the validation fails with the error TargetMoveSubscriptionNotEligible, and the move operation is blocked. This is expected behavior, as resource moves only proceed when all provider-level checks (including quota and supportability) are satisfied.

Alternative options if quota cannot be increased.In some cases, quota requests may not be approved due to regional or capacity constraints. If that occurs, the following options can be considered:

Using a different target subscription - Select a subscription where sufficient quota can be allocated for the required model

Reduce required capacity if applicable - Lower the deployed quota or capacity in the source resource to align with available quota in the target subscription before retrying the move

Recreate the resource in the destination subscription - Provision a new Azure OpenAI resource in a subscription/region with sufficient quota.Then , redeploy required models and update application configurations to point to the new resource

The following references might be helpful , please check them out

Move Azure resources to a new resource group or subscription - Azure Resource Manager | Microsoft Learn

Thank you

Answer 1

kagiyama yutaka 1,990

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.

0 comments

Answer 2

The move validation is failing because the target subscription does not have enough Azure OpenAI quota for OpenAI.Standard.gpt-4o. The move operation requires quota 230, but only 150 is available in the target subscription, so the provider validation fails with TargetMoveSubscriptionNotEligible.

To make the move succeed, the target subscription must first have sufficient quota for the same model and SKU as the source resource. The supported remediation, based on the move framework in Azure, is:

Ensure the target subscription is correctly registered for the Azure OpenAI resource provider and model SKU (this is already implied by having some quota, but must remain in place during the move).
Request a quota increase for OpenAI.Standard.gpt-4o in the target subscription from 150 to at least 230 (or higher) through the standard Azure quota increase process for that service/region.
After the quota increase request is approved and the new quota is visible on the target subscription, rerun the move validation and then the move operation.

If the quota cannot be increased to the required level in that subscription/region (for example, due to capacity constraints), the move will remain blocked. In that case, the only supported options are to:

Use a different target subscription where sufficient quota can be granted, or
Recreate the Azure OpenAI resource in a subscription/region that can accommodate the required quota and then reconfigure dependent applications to use the new endpoint, instead of using a move operation.

The error code ResourceMoveProviderValidationFailed is expected in this scenario: provider-level checks (quota, supportability, state) must all pass before a move is allowed.

References:

Share via

Issue moving Azure Open AI resource to a target subscription

2 answers

Your answer