An Apache Spark-based analytics platform optimized for Azure.
Hi ,
Thanks for reaching out to Microsoft Q&A.
The behavior you're seeing is expected because Entra Global Administrator and Databricks Account Administrator are different roles.
A user can be a Global Administrator in Microsoft Entra ID and still only be a Workspace Admin in Azure Databricks. Azure Databricks has separate administration scopes:
- Account Admin: Manages the Databricks account, Unity Catalog enablement, identity administration, and account-level settings.
- Workspace Admin: Manages users, groups, and settings within a specific workspace
When a user with appropriate Azure permissions (such as Subscription Owner or Contributor) launches a Databricks workspace, Databricks can automatically grant the Workspace Admin role. However, this does not automatically make that user an Account Admin.
The error you're receiving when accessing https://accounts.azuredatabricks.net:
Selected user account does not exist in tenant 'Microsoft Services'...
suggests an identity or tenant sign-in issue with the databricks Account Console, rather than a direct permission issue on the system.serving catalog.
- Verify that you're signing in with the same AAD that owns the databricks workspace.
- In Microsoft Entra ID, check whether the account is a Guest (B2B) user and review its User Principal Name (UPN).
- Try accessing the Databricks Account Console using an InPrivate/Incognito browser session to avoid cached credentials.
- Confirm whether an existing Databricks Account Admin can see your user in the account and explicitly assign the Account Admin role if needed. Account Admins are the only users who can delegate the Account Admin role.
Also, regarding access to system.serving, becoming an Account Admin may not by itself resolve the issue. Unity Catalog access is governed by catalog ownership, metastore administration, and granted privileges. Depending on the object being accessed, you may also need the appropriate Unity Catalog permissions or Metastore Admin privileges.
In summary, the immediate issue appears to be that the user is Workspace Admin only and is unable to access the Databricks Account Console due to an identity/tenant mismatch. I would resolve the Account Console sign-in issue first, then verify whether the required UC permissions exist for system.serving.
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.