@pranav5
This issue usually occurs because of how Databricks handles group provisioning via SCIM, especially with external groups from Azure AD.
SCIM 404 Error: This generally means Databricks cannot find a matching SCIM identity for the Azure AD group โ usually because Databricks didnโt provision the group itself via SCIM.
Azure AD security groups may appear in the Databricks UI (via entitlement sync), but unless they are SCIM-provisioned, Databricks canโt manage or nest them internally.
To Fix This:
Here are some steps to verify and resolve:
1. Confirm SCIM Provisioning
Make sure SCIM provisioning from Azure AD to Databricks is fully configured:
In Azure AD > Enterprise Applications > [Your Databricks app] > Provisioning:
- Confirm it's On and working without errors.
- Check that group provisioning is enabled (not just users).
-Look for this group in the provisioning logs โ it should be successfully pushed.
2. Group Assignment in Azure AD
Ensure that:
- The group is assigned to the Databricks app in Azure AD.
- Itโs not just visible โ it must be assigned for SCIM to provision it properly.
3. Group Must Be SCIM-Managed to Nest in Databricks
Databricks only supports nesting SCIM-managed groups. If your group is external (from Azure AD but not SCIM-provisioned), you cannot nest it under admins or any other group.
Workaround: If nesting is required:
- Create a new group in Azure AD.
- Assign users and the group to the Databricks SCIM app.
- Allow Azure AD to provision it into Databricks.
- Then you can nest this new SCIM group under the admins group in Databricks.
LR