Unable to create resources

santner m 20 Reputation points
2026-03-18T13:40:25.7866667+00:00

Unable to create resources, error message in deployment shows "Authorization failed"

Cost Management
Cost Management

A Microsoft offering that enables tracking of cloud usage and expenditures for Azure and other cloud providers.

0 comments
Answer accepted by question author
Anonymous
2026-03-18T13:47:50.7166667+00:00

Hi santner m
Based on the error message "Authorization failed" observed during the deployment, the issue is related to insufficient permissions to create resources in the Azure subscription or resource group.

To resolve this, we recommend the following steps:

  1. Verify that your user account or service principal has the appropriate role assigned.
  2. Ensure you have at least Contributor access at the subscription or resource group level.
  3. If the required access is not assigned, please contact your Azure administrator to grant the necessary permissions via Access Control (IAM).
  4. After the role assignment is updated, kindly wait a few minutes for the changes to propagate and then retry the deployment.

Please let me know if you face any challenge here, I can help you to resolve this issue further

Provide your valuable Comments.

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Was this answer helpful?

0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-03-18T13:40:38.4533333+00:00

    The error "Authorization failed" during deployment indicates that the signed-in identity doesn't have sufficient permissions (role assignments) at the scope where resources are being created.

    To resolve this:

    1. Identify the exact error details
      • In the Azure portal, go to Resource group (or subscription) → Deployments.
      • Open the failed deployment and check the Error details.
      • Note the client/object ID, the action (for example, Microsoft.Compute/virtualMachines/write), and the scope (subscription, resource group, or resource) mentioned in the message.
    2. Verify current role assignments
      • Navigate to the scope from the error (for example, the subscription or resource group).
      • Select Access control (IAM) → Role assignments.
      • Confirm that the identity in the error (user, service principal, or managed identity) has a role that includes the required action.
      • If the identity is a guest user, ensure it has an appropriate role at that scope.
    3. Assign an appropriate role
      • If no suitable role is assigned, select Add → Add role assignment.
      • Choose a built-in role that includes the required permissions (for example, Contributor or a more specific role such as Virtual Machine Contributor, depending on what is being deployed).
      • Assign the role to the identity from the error at the correct scope (subscription or resource group).
    4. Wait for propagation and retry
      • Wait a few minutes for the new role assignment to propagate.
      • Retry the deployment.

    If the error persists, confirm that:

    • The correct account is signed in (no mix of multiple tenants/accounts).
    • There is no conflicting role assignment with unsupported ABAC conditions (for example, a role that includes Microsoft.Storage data actions combined with GUID comparison operators), which can also cause AuthorizationFailed.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.