Troubleshooting

Having trouble using the module and unable to find a solution in the Wiki?

If it isn't listed below, let us know about it in our Issues log. We'll do our best to help and you may find your issue documented here in the future!

Errors creating Role Definitions and Role Assignments

Error: authorization.RoleDefinitionsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="RoleDefinitionDoesNotExist" Message="The specified role definition with ID '<redacted>' does not exist."

Description:

This error is a transient error which may occur when the Resource Provider in ARM is yet to complete replication of the newly created Role Definition.

Solution:

If the Role Definition has been successfully created in Azure but has not been committed to the terraform state you will need to run terraform import to add the Resource to the state file. Due to caching in ARM, it could take up to 10 minutes before you can successfully import the Resource.

This problem has been identified and logged on GitHub against the AzureRM Provider: #10442

Error: authorization.RoleAssignmentsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="RoleAssignmentNotFound" Message="The role assignment '<redacted>' is not found."

Description:

Coming soon