STEP 1
Connect Databricks and Microsoft Entra ID
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Databricks and Microsoft Entra ID Integration
Connect Databricks and Microsoft Entra ID to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Databricks and Microsoft Entra ID
Detailed info you need to know about Databricks and Microsoft Entra ID integrations in WEXTL. Explore which modules apps support and how you connect them.
Databricks
Run Databricks jobs, clusters, SQL, files, Unity Catalog, and model serving from a workspace. [5]
Microsoft Entra ID
Manage Microsoft Entra ID users, groups, and directory objects via Graph. [6]
How to connect Databricks to Microsoft Entra ID
Set up your Databricks and Microsoft Entra ID integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Databricks and Microsoft Entra ID nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Databricks and Microsoft Entra ID. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Databricks and Microsoft Entra ID work in WEXTL?
WEXTL exposes actions and triggers for Databricks and Microsoft Entra ID that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Databricks triggersMicrosoft Entra ID actions
Databricks modules
- Watch Job RunsTriggers when a Databricks job run starts.
- Cancel All RunsCancels all runs of a job.
- Cancel RunCancels a job run.
- Cancel SQL StatementCancels a SQL statement.
- Change Cluster OwnerChanges the owner of a cluster.
- Create CatalogCreates a catalog.
- Create ClusterCreates a new cluster.
- Create Conversation MessageSends a message in a Genie conversation.
- Create DirectoryCreates a volume directory.
- Create FunctionCreates a function.
- Create JobCreates a new job.
- Create RepoCreates a new repo.
- Create SchemaCreates a schema.
- Create Secret ScopeCreates a secret scope.
- Create Serving EndpointCreates a serving endpoint.
- Create SQL WarehouseCreates a SQL warehouse.
- Create Vector Search IndexCreates a vector search index.
- Create VolumeCreates a volume.
- Create Workspace DirectoryCreates a workspace directory.
- Delete CatalogDeletes a catalog.
- Delete Cluster PermanentlyPermanently deletes a cluster.
- Delete DirectoryDeletes an empty volume directory.
- Delete FileDeletes a file from a Unity Catalog volume.
- Delete FunctionDeletes a function.
- Delete JobDeletes a job.
- Delete RepoDeletes a repo.
- Delete RunDeletes a job run.
- Delete SchemaDeletes a schema.
- Delete SecretDeletes a secret.
- Delete Secret ACLDeletes a secret ACL.
- Delete Secret ScopeDeletes a secret scope.
- Delete Serving EndpointDeletes a serving endpoint.
- Delete SQL WarehouseDeletes a SQL warehouse.
- Delete VolumeDeletes a volume.
- Delete Workspace ObjectDeletes a workspace object.
- Download FileDownloads a file from a Unity Catalog volume.
- Edit ClusterEdits an existing cluster.
- Edit SQL WarehouseEdits a SQL warehouse.
- Execute Message SQL QueryExecutes the SQL query on a Genie message attachment.
- Execute SQL StatementExecutes a SQL statement on a warehouse.
- Export RunExports a job run.
- Export Workspace ObjectExports a workspace object.
- Get CatalogReturns a catalog.
- Get ClusterReturns a single cluster.
- Get Conversation MessageReturns a Genie conversation message.
- Get File MetadataReturns metadata for a volume file.
- Get FunctionReturns a function.
- Get Genie SpaceReturns a Genie space.
- Get JobReturns a single job.
- Get Job RunReturns a single job run.
Microsoft Entra ID modules
- Change a User PasswordExecutes “Change a User Password” against the connected service API.
- Create a GroupCreates a new Group.
- Create a UserCreates a new User.
- Create an ApplicationCreates a new Application.
- Delete a GroupDeletes the selected Group.
- Delete a UserDeletes the selected User.
- Delete an ApplicationDeletes the selected Application.
- List ApplicationsRetrieves a list of applications.
- List GroupsRetrieves a list of groups.
- List UsersRetrieves a list of users.
- Make an API CallPerforms an arbitrary authorized API call.
- Retrieve a GroupRetrieves a Group.
- Retrieve a UserRetrieves a User.
- Retrieve an ApplicationRetrieves an Application.
- Update a GroupUpdates an existing Group.
- Update a UserUpdates an existing User.
- Update an ApplicationUpdates an existing Application.
- Watch ApplicationsTriggers when new applications are created.
- Watch GroupsTriggers when new groups are created.
- Watch UsersTriggers when new users are created.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Databricks and Microsoft Entra ID integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Databricks and Microsoft Entra ID.
Connect your Databricks and Microsoft Entra ID accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Databricks's "Watch Job Runs" fires, WEXTL can "Change a User Password" in Microsoft Entra ID. Databricks has 1 trigger (including Watch Job Runs); Microsoft Entra ID has 17 actions (including Change a User Password, Create a Group, and Create a User). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Databricks-to-Microsoft Entra ID automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Databricks (or Microsoft Entra ID) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Databricks + Microsoft Entra ID automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Databricks and Microsoft Entra ID integration.
- Databricks and Microsoft Entra ID integration source code, module specs and credentials implementation.
- Our Databricks and Microsoft Entra ID integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Databricks and Microsoft Entra ID — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Databricks integration information
- Microsoft Entra ID integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library