Databricks says the new Azure Databricks on Azure Government is now in Beta, and the detail that matters is the default: every workspace ships with Compliance Security Profile enabled and Azure Private Link required on the front end and back end.
That is the break from legacy.
Unlike the old government environment, this one runs on the same architecture as commercial Azure Databricks, the company said. Customer content stays in US Gov Virginia and US Gov Arizona, access runs through Microsoft Entra ID, and the service is managed in the Azure portal and counts toward existing Azure commitments. For teams stuck on a build that lagged commercial by years, that parity is the news.
Unity Catalog arrives on Azure Government for the first time in this Beta, so admins can set access once, track lineage and audit who touched what. Databricks SQL runs with classic clusters or serverless compute per workload, which cuts cluster sizing and patching for analysts who just need fast queries.
You have used this pattern before: governance first, then speed. System tables give you audit logs, billing, compute, query history and storage in one queryable view. Nodes talk over encrypted traffic, compute uses a hardened image with automatic updates, and nothing routes over the public internet when both Private Links are set.
AI is not in Beta. It is the next step, and all of it inherits Unity Catalog controls, the company said. The list is Genie for plain language analytics, AI help for writing code, Agent Bricks for agents over private documents, Model Serving and Foundation Model APIs, plus Vector Search, AI Functions, Databricks Apps and Lakebase. When serving lands, Microsoft Learn notes you can declare a model service in a bundle as a governed AI Gateway endpoint that routes to foundation models or other destinations, which is how Gov teams will likely ship it as code.
That roadmap explains the compliance wait. Databricks is pursuing FedRAMP Class D, formerly High, and DoD Impact Level 5, expected by early 2027 according to the company. Once authorized, the environment can run CUI and mission-critical defense workloads that cannot run on Azure Commercial. During Beta it is for non-production only.
Here is the friction most guides will skip. You need a dedicated Azure Government subscription that has never been used for Azure Databricks, then you register the preview feature and every new workspace lands in the new environment. Legacy workspaces keep running side by side, so start the migration homework now: design Unity Catalog, get security to review serverless, switch cluster configs and Terraform and ARM templates to instance types that support Azure Virtual Network encryption, and update ATO paperwork. Workspaces you build now carry forward to General Availability, so the teams that fix networking and governance during Beta will be ready for CUI when the stamp arrives.





