• Automatic Identity Management (AIM) for Entra ID on Azure Databricks is now Generally Available, removing the need for manual provisioning or complex SCIM-only workflows.
• With AIM, users, groups, and service principals are automatically available within Azure Databricks, with support for nested groups and dashboards.
• The GA release makes AIM on by default for new accounts, offers a simple opt-in for existing ones, and adds API support for automation at scale.
Automatic Identity Management (AIM) for Entra ID on Azure Databricks is now Generally Available.
As customers scale their use of Databricks, managing thousands of users, groups, and service principals across teams becomes complex. Traditionally, admins have relied on SCIM, custom scripts, or manual setup to provision access and keep identities in sync. While these approaches work, they add overhead and make it harder to keep up with fast-growing identity environments.
AIM changes this. Users, groups, and service principals from Entra ID are now connected automatically, so you no longer need to pre-provision identities. This means faster onboarding, less manual work, and smoother collaboration. For example, you can now share an AI/BI dashboard with anyone in your Entra ID directory, even if they’ve never logged into Databricks before.
In this post, we’ll discuss the GA release's features and how AIM works in practice.
With this GA release, Automatic Identity Management (AIM) for Entra ID brings several important updates for Azure Databricks customers to help with adoption and scalability:
"Automatic Identity Management creates a seamless identity management experience in Azure Databricks. It delivers the enterprise-grade user and group management our teams need and adds meaningful maturity to the platform, especially important at our scale, with over 43,000 groups."- Yev Eydelman, Analytics & AI Lead, CARIAD (Volkswagen Group Company)
With AIM, Entra users, service principals, and groups are available in Azure Databricks as soon as they’re granted permissions. Group memberships, including nested groups, flow directly from Entra ID, so permissions always reflect the latest updates.
Under the hood, AIM uses the Entra ID Graph API to keep the Databricks identity directory in sync. It works seamlessly with SCIM, supports service principals (even inside groups), and treats all identities consistently across workspaces.
"Automatic Identity Management will allow us to sunset a large, bespoke integration we had to build ourselves, including a self-service API, and shift identity management directly to our Databricks users. That’s a huge step forward in scaling access securely and efficiently across our organization." - Gerco Grandia, Lead Solutions Architect, E.ON
For collaboration, this means:
See how it works in our demo, and consult the documentation for full details, as well as our blog on the Microsoft Tech Community.