Microsoft.App resource provider stuck in "Registering" for 2+ days (Basic support plan, no technical ticket possible)

Hello Paweł Sieńko,

Greetings! Thanks for raising this question in the Q&A forum.

Thanks for the detailed write-up. A resource provider that stays in "Registering" while others on the same subscription register fine usually means the registration request was accepted by Azure Resource Manager but the provider-side or backend notification never completed. This is not something you can reset from the portal or CLI, and I can't confirm the exact backend cause from here. A mix of client-side retries and a free support route usually resolves it, so please try the following in order.

1. Retry registration and wait on the result. Run these in Azure Cloud Shell, which avoids local CLI or token problems:

az provider register --namespace Microsoft.App --wait

az provider show --namespace Microsoft.App --query "{state:registrationState, id:id}" -o json

1. Re-send the registration through the REST API. This replays the registration directly against Azure Resource Manager:

az rest --method post --url "https://management.azure.com/subscriptions/<subscription-id>/providers/Microsoft.App/register?api-version=2021-04-01"

Then check the state again with az rest --method get --url "https://management.azure.com/subscriptions/<subscription-id>/providers/Microsoft.App?api-version=2021-04-01" --query registrationState

Make sure the dependencies and permissions are in place. You already confirmed Microsoft.OperationalInsights is Registered, which Container Apps needs for logging. Also confirm you have the Contributor or Owner role at subscription scope, since registration requires the */register/action permission. Check with az role assignment list --assignee <your-user-or-object-id> --scope /subscriptions/<subscription-id> -o table.

Trigger registration through a real deployment. Try creating a small Container Apps environment from the portal (Container Apps, then Create) or with az containerapp env create --name <env-name> --resource-group <rg-name> --location <region>. Creating a resource sometimes forces the provider registration to complete. Also try creating and deleting a temporary resource group first, since several users have reported that this nudged a stuck registration. This is anecdotal, so treat it as a low-cost attempt only.

Raise a free Subscription management support request. The Basic plan does not include technical support, but it does include subscription management and billing support at no cost. Your earlier case was closed because it was filed as a technical case. In the Azure portal, go to Help + support, then Create a support request, and choose Issue type "Subscription management" (or "Billing" if that is the only one offered) and select your subscription. Explain that Microsoft.App is stuck in the Registering state for more than 2 days, and include the subscription ID, the provider namespace, the portal timeout message, and the earlier case number 2610120050002174. I can't promise that this category will accept the request, but it is the correct free route to reach the team that can look at subscription-level provider state.

Other ways to get help without a paid plan. You can post on Azure Feedback or ask through the Azure support X account (@AzureSupport), which can open an internal engagement for subscription-level problems. If a paid technical plan is not an option and the project is blocked, a Developer support plan is the lowest-cost paid tier and can be cancelled afterwards.

1. Use a workaround while waiting. If you need to keep moving, deploy to a different Azure subscription, for example a new pay-as-you-go one, where Microsoft.App registers normally, and keep the original subscription for the support case.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,
Jerald Felix