All VMs - Unable to stop/deallocate/start/resize

Luis Fuentes 0 Reputation points
2026-08-20T21:12:26.7133333+00:00

As usual, something in Azure was working and all of a sudden services just crapped out. We have AVD session hosts and a few VMs on US West 3. Working fine 2 months. Today we are unable to stop/start or even resize any VMs. Every single VM is returning what you see below. We verified no changes in RBAC, no resource locks, no Azure outages, and no quota related problems. Any thoughts? Azure support is atrocious and we seem to just get AI generated responses. Tracking ID#2608200010001386

The Azure Compute API is returning:

  • HTTP 500 – InternalServerError
  • InternalOperationError
  • x-ms-failure-cause: service VERBOSE: Authenticating to Azure ... PS /home/user> az vm start --subscription [REDACTED] --resource-group [REDACTED] --name [REDACTED] --debug cli.knack.cli: Command arguments: ['vm', 'start', '--subscription', '[REDACTED]', '--resource-group', '[REDACTED]', '--name', '[REDACTED]', '--debug'] cli.azure.cli.core: Using packaged command index for profile 'latest'. cli.azure.cli.core: Loading command modules... cli.azure.cli.core: Found a match in the command table. cli.azure.cli.core: Raw command: vm start cli.azure.cli.core: Command table: vm start az_command_data_logger: command args: vm start --subscription {} --resource-group {} --name {} --debug cli.azure.cli.core.sdk.policies: Request URL: https://management.azure.com/subscriptions/[REDACTED]/resourceGroups/[REDACTED]/providers/Microsoft.Compute/virtualMachines/[REDACTED]/start?api-version=2022-11-01 Request method: 'POST' Request headers:
    'CommandName': 'vm start'
    
    'ParameterSetName': '--subscription --resource-group --name --debug'
    
    'User-Agent': 'AZURECLI/[VERSION] (...) cloud-shell/[VERSION]'
    
    'Authorization': '*****'
    
    Request body: This request has no body urllib3.connectionpool: https://management.azure.com:443 "POST /subscriptions/[REDACTED]/resourceGroups/[REDACTED]/providers/Microsoft.Compute/virtualMachines/[REDACTED]/start?api-version=2022-11-01 HTTP/1.1" 500 125 cli.azure.cli.core.sdk.policies: Response status: 500 Response headers:
    'Cache-Control': 'no-cache'
    
    'Content-Type': 'application/json; charset=utf-8'
    
    'Retry-After': '180'
    
    'x-ms-failure-cause': 'service'
    
    'x-ms-ratelimit-remaining-subscription-writes': '199'
    
    'x-ms-ratelimit-remaining-subscription-global-writes': '2999'
    
    'x-ms-routing-request-id': 'WESTUS3:[REDACTED]'
    
    'Date': 'Thu, 20 Aug 2026 [REDACTED] GMT'
    
    Response content: { "error": {
    "code": "InternalOperationError",
    
    "message": "An internal error occurred in the operation."
    
    } }
Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments No comments

2 answers

Sort by: Most helpful
  1. SUNOJ KUMAR YELURU 18,656 Reputation points MVP Volunteer Moderator
    2026-08-23T06:20:21.5933333+00:00

    Hello @Luis Fuentes

    That's an Azure platform outage in West US 3 - not your RBAC/locks/quota.

    500 InternalOperationError + x-ms-failure-cause: service + x-ms-routing-request-id: WESTUS3 = fabric controller in that stamp is down.

    Microsoft won't show it on status page until enough customers complain. Your tracking ID 2608200010001386 proves it's their side - all start/stop/resize calls go through same Compute RP in that scale unit.

    What to do:

    1. Check Resource Health for VMs - it will say Platform-initiated issue even if Service Health is green.
    2. Don't keep retrying - you'll get throttled (Retry-After: 180).
    3. Open Sev B ticket with that correlation ID + x-ms-routing-request-id: WESTUS3:... - ask them to failover your VMs to another cluster.
    4. If AVD is down for business, redeploy critical hosts to West US 2 temporarily.

    If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

    Was this answer helpful?

    0 comments No comments

  2. Luis Fuentes 0 Reputation points
    2026-08-20T23:07:08.21+00:00

    Can anyone help escalate this? It's set to Severity A. Over 2 hours without an engineer response.

    Support request ID 2608200010002223

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.