The stuck InProgress provisioning state on the named value is a control-plane issue that cannot be fixed from the client side when all management operations (update policy, delete named value, etc.) are blocked.

The available documentation and tooling only support normal CRUD flows for named values:

• Creating, updating, listing, and deleting named values via Azure CLI (az apim nv create, az apim nv update, az apim nv list, az apim nv show, az apim nv delete, az apim nv show-secret).
• Using named values in policies, with the constraint that a named value cannot be deleted while it is referenced by any policy.

There is no supported command or API to force-clear or override the provisioningState of an individual named value. The provisioningState field on the NamedValueContract is explicitly documented as server-populated and not client-serializable:

provisioningState?: string // NOTE: This property will not be serialized. It can only be populated by the server.

Given that:

1. The APIM service itself is in Succeeded state.
2. The named value is stuck in InProgress and is referenced by a policy.
3. Any attempt to change the policy or the named value fails with 5xx/validation errors because the management plane is effectively locked.

This is a backend/platform issue that requires intervention from Azure Support. Client-side retries, re-PUTs, or delete attempts cannot override the server-managed provisioning state.

The only viable resolution path is:

1. Open an Azure Support ticket for the APIM resource.
2. Provide the APIM service name, resource group, region, named value ID (maintenance-mode), and timestamps of failed operations.
3. Request backend remediation to:
   • Either complete or roll back the stuck provisioning operation on the named value, or
   • Remove the named value and/or its references at the control-plane level.

Similar stuck-provisioning situations in other Azure services (for example, Redis Cache or AI deployments) have been resolved only after the resource transitioned to a failed state or after deletion/recreation, sometimes with support assistance. In this case, because the named value cannot be independently deleted and the management plane is blocked, support escalation is required to unblock the APIM instance.

Until support clears the stuck state, there is no documented or supported way to force-reset the provisioningState of the named value from CLI, REST, or Portal.

References:

• Use named values in Azure API Management policies
• NamedValueContract interface
• Stuck in Creating / Failed provisioning Redis Cache - Microsoft Q&A
• Deployed Claude and getting API deployment resource is not ready even though it has been an hour - Microsoft Q&A
• Azure Deployment Takes 70 Minutes to Fail with Obscure Error - Microsoft Q&A