Status as of
Azure Databricks
Azuredatabricks.net is the domain used by Azure Databricks, a first-party Microsoft Azure service built in partnership with Databricks. It hosts customer workspaces where data engineers, data scientists and analysts use Apache Spark-based analytics, notebooks, SQL warehouses, Delta Lake, Unity Catalog and machine learning tools. Azure Databricks integrates with Azure Data Lake Storage, Microsoft Entra ID, Power BI and other Azure services. Organisations use it to process big data, build AI models and power analytics on Azure.
I have a problem with Azure Databricks
Select the type of problem you're facing to help us and other users.
Recent User Report Trends for Azure Databricks
Aggregated reports in the last 48 hours.
Official Status Unavailable
We couldn't load live incident data from the official status page for azuredatabricks.net at this time. Please try again later.
User Reports for Azure Databricks
Recent issues reported by users from around the world.
Experiencing an issue? Add your report:
Stop refreshing this page
We'll email you the moment Azure Databricks goes down — and again when it's back.
How to fix Azure Databricks not working
Azure Databricks is a Microsoft Azure service, built with Databricks, for data engineering, data science and analytics. Teams use its workspaces for notebooks, clusters, SQL warehouses, jobs and machine learning, connected to Azure data and identity services. Find your symptom below. Most problems come from a sign-in, a cluster or compute setting, a permission on the data, or an incident on the service. Check the status page before you stop or change a job that is running in production.
Jump to what you are seeing
- Workspace Unavailable
- Login Failed
- Cluster Startup Failed
- Notebook Execution Error
- Job Failure
- SQL Warehouse Down
- API Error
- Slow Performance
Login Failed
Sign-in is refused.
- Sign in with the work account your organisation uses for Microsoft Entra ID.
- Check your account has access to that workspace.
- Try a private window to rule out an old session.
Cluster Startup Failed
A compute cluster does not start, or it stops during start-up.
- Read the cluster event log, which usually names the quota, the node type or the setting that failed.
- Check the region has capacity for the node type you picked, and try another node type if your team allows it.
- Check status.azuredatabricks.net, then start the cluster once more.
Notebook Execution Error
A notebook cell fails, or it stops partway through a run.
- Read the first error in the cell output, and the line it names.
- Check the data path and the permission for the data the cell reads.
- Run the notebook on a small sample of the data to find the problem.
Job Failure
A scheduled job fails, or it does not run at its time.
- Read the job run log for the first error.
- Check the job's cluster, its schedule and its permissions have not changed.
- Check status.azuredatabricks.net, then rerun the job once. Check for duplicate output before rerunning.
SQL Warehouse Down
A SQL warehouse does not start, or queries against it fail.
- Check the warehouse is started, and that the user has access to it.
- Check the query runs in a smaller form, to rule out a large or slow query.
- Check status.azuredatabricks.net, and report the warehouse name and the time if it stays down.
API Error
Calls to the Databricks API fail or return an error.
- Check the status code. An access error usually means the token is wrong or lacks permission, too many calls means you should slow down, and a server error means a service-side problem.
- Confirm the token has not expired and is for the right workspace.
- Retry with a growing delay, and check status.azuredatabricks.net if several calls fail together.
Slow Performance
Notebooks, queries or jobs take much longer than usual.
- Check the size of the data and the cluster's size, since a small cluster slows large jobs.
- Check whether other large jobs are running on the same cluster or warehouse.
- Check status.azuredatabricks.net, and report the job name and the time if it is slow for everyone.
Still not working?
Contact your organisation's Azure administrator or your data platform team first, since they manage subscriptions, workspaces and permissions. For a platform-wide problem, contact Microsoft Azure support through the Azure portal, and use the help route in your Azure agreement. Have your subscription and workspace name, the cluster, job or warehouse name, the exact error text, and the time with your time zone. Never send passwords, access tokens or customer data in a support message. Live incident updates are on status.azuredatabricks.net.
Most data-platform problems come from a cluster setting, a permission or a job input, and they usually clear once that is checked. The status page shows live incidents, so you can see whether the problem is on the service's side.
Frequently asked questions about Azure Databricks
Is Azure Databricks down right now?
We cannot confirm an outage for Azure Databricks (azuredatabricks.net) at the moment, and we have no live automated check result to show for it. This page relies on incident updates and reports from users.
What should I do if Azure Databricks is not working for me?
First rule out your side: reload the page, try another browser or device, clear the cache and cookies for azuredatabricks.net, flush your DNS cache and turn off any VPN or proxy. Then compare with this page: if the status shows an incident, or many users reported problems in the last 48 hours, the issue is on the service's end and usually clears up without any action from you. The troubleshooting steps on this page go through each check in order.
How do I report a problem with Azure Databricks?
Use the report buttons at the top of this page, or describe the problem in the user reports section. Every report is counted in the 48-hour trend chart and helps other people see whether the problem is widespread.
Where is the official Azure Databricks status page?
The official status page for Azure Databricks is status.azuredatabricks.net.
Advanced Domain Info Unavailable
We couldn't load advanced domain and security information for azuredatabricks.net at this time. Please try again later.