Container Apps: Stuck in registrationState Registering — Troubleshooting Azure provider registration

Question

Container Apps: Stuck in registrationState Registering — Troubleshooting Azure provider registration

JimOlness-6423 0

Problem description

I am experiencing an issue where my Microsoft.App resource remains in the registrationState 'Registering' on my subscription. Despite multiple attempts to register the provider using the 'az provider register' command and waiting for 30 minutes between retries, the registration status does not change to 'Registered'. I am seeking guidance on how to resolve this persistent registration state and successfully register the provider to proceed with my Container Apps environment creation.

Environment

Azure Container Apps, subscription scope, located in westus2 region

What I've already tried

I tried running the 'az provider register --namespace Microsoft.App' command three times, waiting 30 minutes each time, but the registration status remained 'Registering'. I also checked the provider registration status using 'az provider show --namespace Microsoft.App -o json' and reviewed the JSON output, which indicated the same ongoing 'Registering' state.

Current status

I am currently unable to proceed with Container Apps environment provisioning due to the provider registration being stuck. I am seeking assistance to troubleshoot and resolve the registration issue, including verifying the subscription's provider state, checking activity logs for registration attempts, and ensuring there are no governance or permission blocks preventing registration.

JimOlness-6423 0 Reputation points

2026-10-13T00:23:48.18+00:00

Request for escalation to Microsoft Azure Support Engineering

The Microsoft.App resource provider is stuck in the Registering state on our Azure subscription (iec-subscription), preventing us from creating an Azure Container Apps environment in westus2.

The Azure Activity Log confirms that both operations completed successfully:

Unregister Microsoft.App resource provider — Succeeded

Register Microsoft.App resource provider — Succeeded

However, the resource provider continues to report Registering, including when queried using the Azure CLI:

az provider show --namespace Microsoft.App --query registrationState -o tsv

Attempting to create the Container Apps environment fails with:

Timed out while waiting for the Microsoft.App resource provider to be registered.

I have already attempted to unregister and re-register the provider without success.

I am requesting escalation to a Microsoft Azure support engineer to investigate the resource provider's registration state on the Azure backend. The successful Activity Log events conflict with the persistent registration state reported by Azure Resource Manager.

Please advise how this issue can be escalated for investigation by Microsoft engineering. I would appreciate an acknowledgment from a Microsoft support representative.

Original Azure support request: 2610100010000984
Likhitha Sulake 105 Reputation points Microsoft External Staff Moderator

2026-10-13T18:21:12.3933333+00:00
Hi @JimOlness-6423 ,
Hi,

Thank you for sharing the details.

Since the Microsoft.App resource provider remains in Registering state, please perform the following checks:

Confirm the current status:
az provider show --namespace Microsoft.App --query registrationState -o tsv
Microsoft documents using Azure CLI to review resource provider registration status.

In Azure Portal, open Subscription > Activity log and check the provider registration attempts for any failed Register Subscription/provider registration operations. Please share the error details/JSON if a failure is shown.

Under the subscription, review Policy > Assignments and verify that no Azure Policy is preventing resource provider registration or restricting the required provider/region.

Verify that the account performing the registration has the required Microsoft.Resources/subscriptions/providers/register/action permission. The Q&A guidance recommends confirming appropriate subscription permissions such as Owner or Contributor.

Please share the output of:Microsoft documents using Azure CLI to review resource provider registration status.

In Azure Portal, open Subscription > Activity log and check the provider registration attempts for any failed Register Subscription/provider registration operations. Please share the error details/JSON if a failure is shown.

Under the subscription, review Policy > Assignments and verify that no Azure Policy is preventing resource provider registration or restricting the required provider/region.

Verify that the account performing the registration has the required Microsoft.Resources/subscriptions/providers/register/action permission. The Q&A guidance recommends confirming appropriate subscription permissions such as Owner or Contributor.

Please share the output of:
az provider show --namespace Microsoft.App -o json
Also share the Subscription ID and the relevant Activity Log error/correlation details, with any sensitive information removed.

Once we receive these details, we can review whether the issue is being caused by a permission/governance restriction or requires further backend investigation.

1 answer

Your answer

JimOlness-6423 0 Reputation points

2026-10-13T00:23:48.18+00:00

Request for escalation to Microsoft Azure Support Engineering

The Microsoft.App resource provider is stuck in the Registering state on our Azure subscription (iec-subscription), preventing us from creating an Azure Container Apps environment in westus2.

The Azure Activity Log confirms that both operations completed successfully:

Unregister Microsoft.App resource provider — Succeeded

Register Microsoft.App resource provider — Succeeded

However, the resource provider continues to report Registering, including when queried using the Azure CLI:

az provider show --namespace Microsoft.App --query registrationState -o tsv

Attempting to create the Container Apps environment fails with:

Timed out while waiting for the Microsoft.App resource provider to be registered.

I have already attempted to unregister and re-register the provider without success.

I am requesting escalation to a Microsoft Azure support engineer to investigate the resource provider's registration state on the Azure backend. The successful Activity Log events conflict with the persistent registration state reported by Azure Resource Manager.

Please advise how this issue can be escalated for investigation by Microsoft engineering. I would appreciate an acknowledgment from a Microsoft support representative.

Original Azure support request: 2610100010000984

Answer 1

Hi @JimOlness-6423

Microsoft.App usually finishes registering within a few minutes, so 90 minutes stuck at "Registering" means something is blocking it in the background. Running the register command again won't move it along, so it's better to find out why it's stuck.

In the portal, open your subscription > Activity log, filter on the last few hours and look for a "Register Subscription" or provider registration event that failed. Open it and check the error in the JSON tab.
Under the subscription's Policy > Assignments, check whether any policy denies resource provider registration or restricts which providers or regions can be used. An org-level policy can quietly block this.
Make sure the account running the command has Owner or Contributor on the subscription, since registering needs the resourceproviders/register/action permission.
If the Activity log shows nothing useful, open a support request. Provider registration falls under subscription management, which doesn't need a paid support plan. Include the namespace (Microsoft.App) and the times of your attempts.

Is this a new subscription, or one that's part of a company or school tenant with policies applied?

If this resolved your issue, please consider accepting it as the answer. If the Activity log shows an error you're not sure about, let me know and I'll be happy to keep helping.

Reference: