Contents
Why do I get an error message when I remove a role assignment?
In PowerShell, if you try to remove the role assignments using the object ID and role definition name, and more than one role assignment matches your parameters, you will get the error message: “The provided information does not map to a role assignment”. The following output shows an example of the error message:
Do you have to re-create role assignment after move?
After the move, you must re-create the role assignment. Eventually, the orphaned role assignment will be automatically removed, but it is a best practice to remove the role assignment before moving the resource. For information about how to move resources, see Move resources to a new resource group or subscription.
How can I reduce the number of role assignments?
The 2000 role assignments limit per subscription is fixed and cannot be increased. If you are getting close to this limit, here are some ways that you can reduce the number of role assignments: Add users to groups and assign roles to the groups instead. Combine multiple built-in roles with a custom role.
What happens if I delete a custom role in azure?
If you are unable to delete a custom role and get the error message “There are existing role assignments referencing role (code: RoleDefinitionHasAssignments)”, then there are role assignments still using the custom role. Remove those role assignments and try to delete the custom role again.
Can a custom role be assigned to a management group?
Custom roles with DataActions cannot be assigned at the management group scope. Azure Resource Manager doesn’t validate the management group’s existence in the role definition’s assignable scope. For more information about custom roles and management groups, see Organize your resources with Azure management groups.
How to enable user login on web service?
Click on the User Mapping link on the left of the screen and select the DB you’d like your web service to be able to reach. Click on the Status link on the left and ensure that the settings are set to Grant for permission to connect to the DB and Enabled for the login.
How to troubleshoot IAM roles in AWS service?
ClientError: An error occurred (AccessDenied) when calling the PutLifecycleHook operation: User: arn:aws:sts::111122223333:assumed-role/Testrole/Diego is not authorized to perform: iam:PassRole on resource: arn:aws:iam::111122223333:role/aws-service-role/autoscaling.amazonaws.com/AWSServiceRoleForAutoScaling