Databricks Asset Bundles · OAuth Scopes
Databricks Asset Bundles OAuth Scopes
OAuth 2.0
probed
Databricks Asset Bundles uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CI/CDData EngineeringDatabricksDeploymentInfrastructure as CodeJobMachine-LearningMLOpsPipelinesWorkflows
Scopes: 0
Flows:
Method: probed
Scopes (0)
Databricks Asset Bundles implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
The baseline scope list is read verbatim from the RFC 8414 authorization server metadata document Databricks serves anonymously on the account console host — not from prose. The managed-MCP scopes below are read from the managed MCP documentation and are not present in scopes_supported.
The baseline scope list is read verbatim from the RFC 8414 authorization server metadata document Databricks serves anonymously on the account console host — not from prose. The managed-MCP scopes below are read from the managed MCP documentation and are not present in scopes_supported.
📄 Provider scope reference: https://docs.databricks.com/aws/en/dev-tools/auth/oauth-m2m
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.