Databricks supports SCIM provisioning. Stepwork automates Databricks provisioning with 98% accuracy — no API required.
SCIM Support & Constraint: Databricks supports SCIM for identity sync but not for full workspace or data-layer permissions. Complexity Vector → Stepwork: Permissions span workspace, compute, and data layers across multiple UIs, so automation breaks due to multi-layer complexity; therefore Stepwork is required to automate these admin workflows end-to-end.
Databricks permissions directly affect data custody and audit scope. SCIM does not govern workspace or catalog access, which is why teams use Stepwork to automate Databricks flows with 98% accuracy without needing an API.
Databricks supports SAML sign-on. Stepwork authenticates through your existing identity provider — the same way your employees do.
Stepwork automates Databricks provisioning through interface automation — the same way a human would, but with 98% accuracy and no API required. Record the flow once, and Stepwork runs it on demand or on a schedule.
Yes. Stepwork authenticates to Databricks through your existing identity provider (Okta, Microsoft Entra ID, 1Password, etc.) and completes MFA natively — including OTP, passkeys, and push notifications. No separate credentials or service accounts are needed.
The primary risk is scim does not manage data permissions.. Additional risks include workspace drift, cluster/job access manual, catalog overexposure. Stepwork eliminates these risks by automating the entire provisioning workflow.
No. Stepwork completes MFA exactly like a human user — supporting OTP, passkeys, push notifications, and other methods. It signs in through your existing identity provider via SAML, mirroring your organization's security posture.
See how Stepwork provisions users in Databricks with 98% accuracy — in a 15-minute demo.
Book a Demo