Jobs API 2.2 No Longer Enabled for Azure Government

fpmsi
New Contributor II

‎03-31-2025 01:01 PM

Hello,

My team deploys job in the Azure Government environment. We have been using the updated cli (> .205) to do so. Sometime within the last month and a half, our azure us gov environment stopped working with the jobs api 2.2. It was working before but now we get this message: "API 2.2 is not enabled. Please use API 2.1". Our other environments work well with deploying jobs using the new cli. This includes Azure dev and AWS prod. We tried looking to see if there was something we could enable in our workspace to make Jobs API 2.2 work but there isn't a corresponding setting.

Can someone from Databricks talk about this issue? We believe that there is some issue with updated cli and azure us government.

Preview file
53 KB

Louis_Frolio
Databricks Employee
Databricks Employee

‎11-03-2025 01:11 PM

Hey @fpmsi , thanks for raising this — I can clarify what’s going on and how to work around it.
 

What’s happening

  • Jobs API 2.2 is not enabled on the Azure Government (Govcloud/FedRAMP/PVC) shards today, by design. In those regions, the service responds with the exact error you’re seeing: “API 2.2 is not enabled. Switch to API 2.1.”
  • Azure commercial and AWS shards do have Jobs API 2.2 available since the public launch, which is why your other environments continue to work with the newer CLI that prefers 2.2-capable endpoints.
  • There is no workspace-level toggle to enable Jobs API 2.2 in Govcloud; enablement is controlled centrally and currently disabled on these shards.

Why this started surfacing recently

  • When Jobs API 2.2 was publicly released, tooling began preferring 2.2 where supported; on Govcloud, the platform correctly rejects 2.2 calls with the “not enabled” message, so any CLI or script that doesn’t fall back automatically will fail until it targets 2.1 explicitly.

Workarounds you can use now (Govcloud)

  • Target Jobs API 2.1 for all job operations against Azure Government workspaces until 2.2 becomes available on those shards.
  • Use direct REST calls to 2.1 endpoints. For example: ```bash # Create a job (API 2.1) curl --location '<host>/api/2.1/jobs/create' \ -H 'Authorization: Bearer <token>' \ -H 'Content-Type: application/json' \ --data @job.json
    # Submit a run (API 2.1) curl --location '<host>/api/2.1/jobs/runs/submit' \ -H 'Authorization: Bearer <token>' \ -H 'Content-Type: application/json' \ --data @run.json ```
  • If you use Databricks Asset Bundles to deploy jobs, the job resource mappings align to the Jobs API 2.1 create payload; keep those targets on Govcloud pointing to 2.1 until 2.2 is enabled there.

Operational note

  • Some behaviors introduced with Jobs API 2.2—for example, queueing enabled by default for new or updated jobs—won’t apply on Govcloud while you’re on 2.1. Review any automation that assumes 2.2 defaults and set concurrency/queueing explicitly in 2.1 as needed.

Summary

  • The error isn’t a workspace misconfiguration; it reflects the current platform-level non-availability of Jobs API 2.2 on Azure Government. Use Jobs API 2.1 for Govcloud workloads for now, and keep using 2.2 in Azure commercial and AWS where it’s supported.
Hope this helps, Louis.
0 Kudos