AzureMid

Azure AuthorizationFailed: the client does not have authorization

AuthorizationFailed means your identity lacks permission for the action at that scope. Check the role assignment, the scope and any ABAC condition.

What you see

  • The client with object id does not have authorization to perform action over scope (code: AuthorizationFailed)
  • The client '<client>' with object id '<objectId>' does not have authorization to perform action '<action>' over scope '<scope>' or the scope is invalid.

What it means

Azure checks your role assignments at the scope of the resource and its parents. The message names the action and the scope that failed.

How to confirm the cause

  1. 1
    List your role assignments
    az role assignment list --assignee USER_OR_APP_ID --all

    Check the role and the scope on each assignment.

Causes and fixes

  • No write role at the scope

    HOW TO TELL
    You are signed in as a user without write permission on that resource at that scope.
    FIX
    Sign in as a user with a suitable role, for example Virtual Machine Contributor on the resource group (or a parent scope) to manage virtual machines.
  • Guest user without a role

    HOW TO TELL
    A guest user gets the same message.
    FIX
    Assign the guest a role with the least permissions needed at the scope.
  • ABAC condition conflicts with a storage data action

    HOW TO TELL
    The role includes a Microsoft.Storage data action and the assignment condition uses a GUID comparison operator.
    FIX
    That combination is not supported. For a custom role, remove Microsoft.Storage data actions, or change the condition so it does not use GUID comparison operators.

How to stop it coming back

  • Assign roles to groups at the narrowest scope that works.
  • Review role assignments when people change teams.

Keep going

Sources

Microsoft Learn (learn.microsoft.com), read 18 Nov 2026. The page's own metadata shows it was last updated 5 Nov 2026.

Search

Search cheat sheets and projects