Azure Network Connectivity Configurations API failing

[sebastiandz]

It seems like since yesterday evening (Europe time) there's a platform-side issue with Network Connectivity Configurations API on Azure Databricks Accounts.

API calls are being redirected to a login page, causing multiple different tools, such as Terraform, SDK, CLI, to fail. Other Account APIs are working just fine with the same credentials, so it doesn't seem to be a valid authentication error.

It was raised on Terraform provider Github by multiple users, as this is what its error message suggests: [ISSUE] mws network connectivity config issue : invalid character '<' looking for beginning of value...

I know posting here is not ideal way of reporting technical issues, but I hope this comes to attention of Databricks personnel as I don't have a better comms channel handy.

[stbjelcevic]

I can't speak to this specific incident as it was over a year ago, but for future reference:

Monitoring Databricks service health

• Please subscribe to the Azure Databricks Status Page for your region(s) and the specific components you use. You can opt into notifications via email, webhook, or Slack so your team gets real‑time updates only for relevant services.
• The status page also shows Azure-wide service health so you can identify when upstream Microsoft incidents may be contributing to impact.
• https://status.azuredatabricks.net/

How to raise issues with Databricks Support:

• File a case in the Databricks Help Center. Only authorized support contacts under your company’s Databricks Support contract can open and manage tickets; if you’re not listed, ask your admin to add you as an authorized contact.
• If an authorized user cannot submit via the portal, they can email help@databricks.com to create a case. Emails from non‑authorized contacts are rejected by the system.
• Set the case priority to match impact (for example, Urgent for production‑blocking events). Databricks Support will respond per the SLA in your plan.

https://www.databricks.com/support

https://docs.databricks.com/aws/en/resources/support

What to include for faster triage (especially for API issues):

• The full endpoint URL and method, your Azure region(s), and the UTC timestamp(s) of the failures.
• Failing response headers (especially X‑Request‑Id and Traceparent) and a note if the payload was HTML instead of JSON.
• Your authentication context (service principal or managed identity, tenant, and token audience/resource).
• Whether the same action worked in the Account Console UI for your account/region.

Optional: open‑source tooling:
If the issue appears tied to an open‑source tool (Terraform provider, CLI, SDK), also raise a GitHub issue in the relevant repository to inform maintainers. Still open a Help Center case for production impact to ensure SLA‑backed support.

You can also reach out directly to your Databricks account team and they should be able to provide you with up-to-date information.