Skip to content

az provider register -n Microsoft.App stuck in "Registering" for 2+ days #34214

Open

Description

@PawelSienko

Describe the bug

The Microsoft.App resource provider has been stuck in "Registering" state on
my pay-as-you-go subscription for more than 2 days. It never reaches
"Registered". Other providers (Microsoft.ResourceHealth,
Microsoft.OperationalInsights, Microsoft.Insights) register fine on the same
subscription. Portal shows: "'Register' operation check timed out on Resource
Provider 'microsoft.app'". This blocks Azure Container Apps / Flex Consumption
VNet deployments. I have a Basic support plan, so I cannot open a technical
support ticket (billing case 2610120050002174 was closed). This looks like a
backend issue that needs a registration reset. Could you route it to the right
team?

Related command

az provider register -n Microsoft.App
az provider show -n Microsoft.App --query registrationState -o tsv

Errors

$ az provider show -n Microsoft.App --query registrationState -o tsv
Registering

Portal: Subscription Registering Resource Provider
'Register' operation check timed out on Resource Provider 'microsoft.app',
please refresh resource providers list to check for registration status

Issue script & Debug output

az provider register -n Microsoft.App --debug

Expected behavior

Provider moves to "Registered" within a few minutes.

Environment Summary

azure-cli 2.90.0 *

core 2.90.0 *
telemetry 1.1.0

Extensions:
ml 2.45.0
ssh 2.0.9

Dependencies:
msal 1.36.0
azure-mgmt-resource 24.0.0

Python location '/usr/bin/python3.12'
Config directory '/home/pawel/.azure'
Extensions directory '/home/pawel/.azure/cliextensions'
Extensions system directory '/usr/lib/python3.12/site-packages/azure-cli-extensions'

Python (Linux) 3.12.14 (main, Aug 18 2026, 15:00:50) [GCC 13.2.0]

Legal docs and information: aka.ms/AzureCliLegal

You have 2 update(s) available. They will be updated with the next build of Cloud Shell.

Additional context

Region: West Europe. Subscription state: Enabled. Portal subscription
diagnostics: no issues. Service Health: no events. Subscription ID available
privately on request.

Activity

  1. added
    bugThis issue requires a change to an existing behavior in the product in order to be resolved.
    on Oct 12, 2026
  2. yonzhan commented on Oct 12, 2026

    @yonzhan
    Collaborator

    Thank you for opening this issue, we will look into it.

  3. added
    customer-reportedIssues that are reported by GitHub users external to the Azure organization.
    ARMaz resource/group/lock/tag/deployment/policy/managementapp/account management-group
    Azure CLI TeamThe command of the issue is owned by Azure CLI team
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    on Oct 12, 2026
  4. x-engineering-agent commented on Oct 12, 2026

    @x-engineering-agent
    Contributor

    Bug Analysis

    The reported two-day Registering state and matching Portal timeout point to ARM/Microsoft.App service-side registration, rather than an established CLI defect. This is based on the report and source review; I have not reproduced the issue or diagnosed the backend root cause.

    The command mapping routes show to the provider GET operation. The registration implementation submits registration to ARM and reads the service-returned state. --wait only polls that state every 10 seconds; it cannot repair or reset a stuck registration.

    Next action: the existing ARM/component owners should route this to the Microsoft.App registration/service owners to inspect the affected subscription through an approved private channel. Please keep subscription identifiers, authorization credentials, and debug secrets out of public comments. This evidence does not establish a CLI change or promise a backend reset.

    Posted by x-engineering-agent (Fixer)

  5. added this to the Backlog milestone on Oct 12, 2026
  6. removed
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    on Oct 12, 2026
  7. microsoft-github-policy-service commented on Oct 13, 2026

    @microsoft-github-policy-service
    Contributor

    Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc antcp, AzureAppServiceCLI (@AzureAppServiceCLI), @Azure/act-observability-squad.

  8. microsoft-github-policy-service commented on Oct 13, 2026

    @microsoft-github-policy-service
    Contributor

    Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc Joseph Chan (@josephkwchan), Jenny Hunter (@jennyhunter-msft), @Azure/act-identity-squad.

  9. microsoft-github-policy-service commented on Oct 13, 2026

    @microsoft-github-policy-service
    Contributor

    Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc antcp, AzureAppServiceCLI (@AzureAppServiceCLI), @Azure/act-observability-squad.

  10. microsoft-github-policy-service commented on Oct 13, 2026

    @microsoft-github-policy-service
    Contributor

    Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc Joseph Chan (@josephkwchan), Jenny Hunter (@jennyhunter-msft), @Azure/act-identity-squad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

ARMaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupApp Servicesaz appserviceAuto-AssignAuto assign by botService AttentionThis issue is responsible by Azure service team.bugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions