Thank you for your detailed post!
Error: Authorization Failed
The client '....1426' with object id '....1426' does not have authorization to perform action 'Microsoft.KeyVault/vaults/read' over scope '.../Connector/providers/Microsoft.KeyVault' or the scope is invalid.
Based off your error message, it looks like you're running into an HTTP 403: Insufficient Permissions issue.
HTTP 403 means that the request was authenticated but the identity (
..1426
) does not have permission (../vaults/read) to access the requested resource (../Microsoft.KeyVault/vaults
). There are two causes:> - There is no access policy for the identity.
- The IP address of the requesting resource is not approved in the key vault's firewall settings.
To hopefully help point you in the right direction or resolve your issue, I'll share some troubleshooting steps below.
-
Navigate to your desired scope
(i.e. resource group). Based off your error message, it looks like your resource group would be "Connector" -/resourceGroups/Connector.
- From your error message, you'll need the
Microsoft.KeyVault/vaults/read
RBAC permission. For more info - Microsoft.KeyVault RBAC Permissions. - Within your "Connector" Resource Group, assign the appropriate Key Vault built-in role to your application or object ending in (
..1426
).
For more info Resource group scope role assignment
- Go to the Resource Group that contains your key vault.
- Select Access control (IAM).
- Select **Add
- Add role assignment** to open the Add role assignment page.
- Assign the appropriate role.
Note: These roles all have the /read permission.
Additional Links:
- Azure Key Vault REST API Error Codes
- Recommended troubleshooting Steps for following error types
- Common error codes for Azure Key Vault
- Azure built-in roles for Security
I hope this helps!
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.