Hi ,
Thanks for reaching out to Microsoft Q&A.
Please try the following common fixes for your issue.
Confirm Workspace Admin Role at the Platform Level
- Go to Admin Console > Workspace Settings.
- Ensure that
******@trubrixai.com
is:- Workspace Admin in Databricks (not just RBAC). Also listed under Admin Users in the Access Control section.
Check Cluster Policy Scopes
Go to Compute > Cluster Policies.
Open the "Personal Compute" policy.
- Verify the policy definition does not contain scope-limiting conditions like:
"allowed_users": ["specific-user@example.com"]
If it does, remove or update to include your user.
Add Full Cluster Permissions
Go to Compute > Permissions (on any cluster).
Add your user (azure-admin@...
) with:
Can Manage or Can Attach To / Restart / Use as needed.
Apply same permission on the Cluster Policy as well.
Reassign Entitlements
Go to Admin Console > Users.
- For your user:
Toggle off "Unrestricted Cluster Creation".
Save.
Toggle it back on and save again.
- This forces a resync of the entitlement.
Confirm Azure RBAC at Subscription / Resource Level
- In Azure Portal:
- Navigate to the RG and databricks workspace.
- Higher roles like owner or user access administrator may be needed if policies are enforced at the management group level.
Clear Cached Access Tokens
- Log out of the databricks workspace.
Clear browser cache or use an incognito window.
Log back in and retry cluster creation.
Test with a New Cluster Policy
Create a new cluster policy without restrictions.
- Assign it to your user or group with can use permission.
- Attempt to create a cluster using this new policy.
Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.