An Apache Spark-based analytics platform optimized for Azure.
Hi @Veera-3402 ,
Thank you for contacting Microsoft Support Q&A. My name is Siva, and I will be assisting you with this support request.
Thank you for providing the detailed information regarding the Azure Databricks Supervisor Agent issue.
I understand that the Supervisor API (Beta) is shown as enabled/effective in your East US workspace, Unity Catalog and serverless capabilities are enabled, but attempting to save a Supervisor Agent returns:
“Failed to save agent. Supervisor Agent is not available. To access this feature, please contact sales for assistance.”
Technical Assessment
Based on the current Azure Databricks documentation, there is an important distinction between the Supervisor API and Agent Bricks Supervisor Agent.
The Supervisor API has been deprecated and reached end of life on September 30, 2026. Therefore, enabling the Supervisor API preview should not be considered confirmation that Supervisor Agent creation is enabled for the workspace.
Supervisor Agent is a separate Beta capability. Access to Beta functionality can be controlled at the Databricks account/preview level.
Since you have already confirmed the standard workspace configuration and the operation reaches Supervisor Agent creation but returns an explicit “feature not available/contact sales” message, I do not recommend repeatedly enabling/disabling the Supervisor API or making unrelated Unity Catalog/serverless configuration changes.
Recommended Next Steps
Please perform the following validation:
Have an Azure Databricks account administrator review the available previews and confirm that the Supervisor Agent Beta capability is available/enabled for the affected account/workspace.
If Supervisor Agent is already enabled but the Save operation continues to return the same error, please provide:
- Azure Databricks Workspace ID
- Databricks Account ID
- Exact failed-attempt timestamp in UTC
- Screenshot of the complete error
- Request/correlation ID, if one is exposed by the failed request
- Screenshot of the complete error
- Exact failed-attempt timestamp in UTC
- Databricks Account ID
At this stage, I do not want to attribute the failure to East US, Unity Catalog, serverless configuration, permissions, or another workspace setting without supporting service-side evidence.
Supervisor API Clarification
If your objective is to develop a custom programmatic agent using the Supervisor API, please note that the Supervisor API reached end of life on September 30, 2026. Azure Databricks now recommends custom agents on Databricks Apps instead.
If your requirement is specifically the Agent Bricks Supervisor Agent experience, we should continue by validating the Supervisor Agent Beta availability for the affected Databricks account/workspace.
Root Cause Status: Under Investigation
The currently available evidence indicates that further account/workspace feature-availability validation is required before we can establish the final cause.
Refer: -
https://learn.microsoft.com/en-us/azure/databricks/agents/agent-bricks/multi-agent-supervisor