Government partners can now build on Unity Catalog, Databricks SQL and serverless compute in Azure Government, delivered as a first-party Azure service.
Closing the gap between innovation and compliance
For years, public sector leaders have faced a difficult choice: adopt the latest data and AI capabilities or meet the strict security and compliance requirements of their mission. As a result, many agencies and their partners have not had access to the full set of Azure Databricks capabilities available in the global Azure cloud.
On Azure Databricks, we believe the public sector should not have to make that trade-off. Today, we're announcing the Beta release of Azure Databricks on Microsoft Azure Government. Agencies and the organizations that serve them can now build on the same modern data foundation available in global Azure, including Unity Catalog, Databricks SQL, and serverless compute. For details on Azure Databricks release types, see Azure Databricks preview releases - Azure Databricks | Microsoft Learn.
One platform across global Azure and Azure Government
On global Azure, Azure Databricks has already achieved FedRAMP Class D authorization. With this Beta, the same modern platform arrives in Microsoft Azure Government, giving U.S. public sector customers a modern Azure Databricks option in both Azure clouds.
Azure Government is Microsoft's dedicated Azure cloud for U.S. government agencies and their partners. It is physically isolated from the global Azure cloud, and screened U.S. persons operate it to meet the compliance requirements of federal, state, local and tribal governments.
Choosing between the two comes down to the workload. Azure Databricks is available today for federal civilian agencies, state and local governments, and partners whose workloads fit FedRAMP Class D in global Azure regions. The new Azure Government environment, now open in Beta, is for organizations that need a dedicated government cloud.
In both clouds, Azure Databricks is a first-party Azure service. Agencies manage it in the Azure portal, rely on its native integration with Microsoft Entra ID and apply usage toward their existing Azure commitments, so adoption happens within the cloud, contracts and identity systems they already trust. Under the hood, the new environment shares the architecture of Azure Databricks in global Azure and is built to take in the full Databricks platform, with every feature released in global Azure reaching Azure Government through the same ongoing releases.
Authorization path
FedRAMP Class D (formerly FedRAMP High) and DoD Impact Level 5 (IL5) authorizations for the new Azure Databricks on Azure Government environment are pending. Once they are in place, agencies and defense partners will be able to bring Controlled Unclassified Information (CUI) and mission-critical workloads to the modern Azure Databricks platform.
Until then, the Beta environment must not be used to process CUI or any other data regulated by these standards, and General Availability depends on completing the applicable government authorization process.
What's available in Beta
Beta is the first step toward the full platform, and it already delivers the core capabilities that data teams depend on. It is intended for non-production workloads, and feature availability might differ from the generally available Azure Databricks service.
- Unified governance across data and AI: Unity Catalog comes to Azure Government for the first time. Teams can control access, trace lineage and audit usage for every data and AI asset from one place: write a policy once, enforce it everywhere and answer who accessed what, when and why.
- Analytics that scale without the overhead: Databricks SQL provides fast analytics at high concurrency. For each workload, engineers and data scientists pick classic clusters or serverless compute, spending less time sizing and patching infrastructure and more time on the mission.
- Security controls on from day one: The Compliance Security Profile is enabled by default in every workspace. It adds enhanced security monitoring, automatic cluster updates and a hardened compute image, and it enforces VM instance types that support Azure Virtual Network encryption for hardware-implemented encryption between cluster nodes. Front-end and back-end connections both require Azure Private Link, which keeps all traffic on the Microsoft backbone network.
- Visibility into usage and cost: Administrators can query system tables for audit logs, billing, compute, jobs and pipelines, ML experiments, query history and storage in one place, so responding to audit requests and managing spend uses tools they already know.
- Data that stays in government regions: Data residency is always enforced: customer content is stored and processed only in the U.S. government Azure regions US Gov Virginia and US Gov Arizona. Cross-Geo processing does not apply to Azure Government workspaces and cannot be used to process data outside those regions.
Take the next step
Starting fresh in the new environment
During Beta, access is enabled per subscription. Register a dedicated Azure Government subscription that has never been used to create an Azure Databricks workspace. In the Azure Government portal, open that subscription's Preview features, find the Azure Databricks new GovCloud environment feature and register it (this requires permission to register subscription features). Once the status reads Registered, each new workspace created in that subscription lands in the new environment. Plan Beta workloads for non-production and non-CUI scenarios.
Moving from the existing Azure Government environment
Because the new environment is separate, registering for Beta leaves your existing workspaces, notebooks, data and configurations untouched, and you can evaluate the new environment alongside them. Use a different subscription from the one that hosts your existing workspaces, since a subscription cannot be registered for both environments at the same time. Four areas deserve early attention:
- Unity Catalog: Begin now so your teams have time to design and roll out unified governance.
- Serverless compute: Serverless is new to government environments, so open your internal security and compliance review early.
- Network encryption: Because the Compliance Security Profile is enabled on every workspace, clusters need instance types that support Azure Virtual Network encryption. Align your cluster configurations and Terraform/ARM templates accordingly.
- Your ATO: Engage your security and authorizing officials now about adding Azure Databricks on Azure Government to your system's Authorization to Operate (ATO). Updating system security plans, data flows and boundary documentation during Beta positions you to run CUI production workloads at General Availability.
Getting started
To get started, visit Azure Databricks on Microsoft Azure Government. For questions or feedback during Beta, contact your Microsoft account team.
Learn More