Home > Docs > Gov Service Matrix

Azure Government Service Availability Matrix¶

Quick Summary: Comprehensive matrix of Azure service availability across Commercial vs Government regions (FedRAMP High, IL4, IL5, IL6), including endpoint URL differences, API version caveats, Bicep configuration for Gov, compliance requirements by vertical, and open-source alternatives for Government gaps.

Impact Level 6 (Classified / SIPR) — CSA-0086. IL6 workloads run on Azure Government Secret — a separate physically-isolated cloud with its own Authority to Operate. It is not reachable from Azure Government (IL4/IL5) and none of the Bicep, dbt, or portal deployments in this repo have been authorized for IL6. DoD SIPR/TS customers should treat this matrix as IL4/IL5-scoped and engage their sponsor for the Azure Government Secret onboarding process. The column below therefore reads N/A — Azure Government Secret (separate ATO) uniformly. Honesty over silence.

This document tracks the availability of every Azure service used by CSA-in-a-Box across Azure Commercial and Azure Government regions, including FedRAMP authorization levels and impact level (IL) support.

Last verified: April 2026. Check Azure Government Services by Region for the latest status.

📑 Table of Contents¶

• ☁️ Core Services
• 💻 Compute & Hosting
• 🤖 AI & ML
• 🗄️ Databases
• 🔒 Identity & Security
• 📊 Monitoring & Management
• 🌐 Endpoint URL Differences
• ⚙️ API Version Differences
• 📦 Bicep Configuration for Government
• 🏛️ Compliance Requirements by Vertical
• 🔓 Open-Source Alternatives for Government Gaps
• 📚 References

☁️ Core Services¶

"N/A (Secret)" means the service exists in Azure Government Secret but csa-inabox has not been authorized against that cloud. Customers requiring IL6 must engage their sponsor for the Azure Government Secret onboarding process.

💻 Compute & Hosting¶

🤖 AI & ML¶

🗄️ Databases¶

🔒 Identity & Security¶

📊 Monitoring & Management¶

🌐 Endpoint URL Differences¶

When deploying to Azure Government, all service endpoints use different domains:

⚙️ API Version Differences¶

Most Azure Resource Manager API versions are identical between Commercial and Government. However, verify these known cases:

📦 Bicep Configuration for Government¶

// In your Bicep parameters file for Gov:
param environment string = 'AzureUSGovernment'
param location string = 'usgovvirginia'  // or 'usgovarizona', 'usdodeast', 'usdodcentral'

// Endpoint overrides
param storageEndpointSuffix string = 'core.usgovcloudapi.net'
param sqlEndpointSuffix string = 'database.usgovcloudapi.net'
param kvEndpointSuffix string = 'vault.usgovcloudapi.net'

// Compliance tags applied automatically
param complianceTags object = {
  FedRAMP_Level: 'High'
  FISMA_Impact: 'High'
  Data_Classification: 'CUI'
  Compliance_Framework: 'NIST-800-53-Rev5'
}

🏛️ Compliance Requirements by Vertical¶

🔓 Open-Source Alternatives for Government Gaps¶

For the rare cases where a service is unavailable in Government at a required impact level, CSA-in-a-Box provides containerized open-source alternatives deployable on AKS:

📚 References¶

• Azure Government Documentation
• Azure Government Services by Region
• FedRAMP Authorized Services
• DoD IL Guidance

See also:

• ← Previous: Environment Protection
• → Next: Documentation home
• ⌂ Index: Documentation home