IdP Configuration - Azure
On this page
SingleStore SCIM supports Azure with the SCIM 2.
Prerequisites
-
RBAC authorization for the Organization Team feature is enabled.
-
RBAC user sync should be enabled for the Engine RBAC at SingleStore database level.
SCIM Provisioning in the SingleStore Helios Portal
Follow the instructions specified in SCIM User Provisioning.
Note: SingleStore recommends that you check out the logAllRequests attribute to facilitate debugging.
SCIM Provisioning in the Azure Portal
The following steps should be used to set up SCIM in the Azure portal.
-
If you do not have an existing enterprise application, then create it by clicking on Create your own application, Non-Gallery.
-
API Endpoint and Secret:
-
Use the API endpoint and secret from the SingleStore portal in the Provisioning section of the application.
-
Ensure you add
'/?aadOptscim062020'to the end of the URL.Refer: Known issues with SCIM for further details. -
Click on Test Connection.
-
Check out the Send an email notification when a failure occurs option for easier debugging.
-
Save the setting, (In case the grayed out buttons do not go back to normal display after saving, refresh the page.
)
-
-
Set up the SCIM attribute mapping:
-
SCIM User: Ensure the primary email id is valid and current so that SingleStore can match to the correct user.
It is strongly recommended to map userPrincipleName to email. However, if the userPrincipleName does not contain the primary email id, then enter the correct primary email id manually.
-
Remove all unsupported attributes in the SCIM User mapping as shown in the screenshot below:
-
SCIM Group: Leave the default settings.
-
-
Test with Provision on demand.
-
Add users/groups to the provision.
-
Test adding a user to SingleStore.
If adding a user syncs successfully, then the user should appear in the SingleStore Helios portal Users tab. -
Test other actions, such as delete.
-
-
If all the above tests are successful, you can turn on the provisioning.
Use the provision log to check for any errors or issues.
Remarks
-
When you create a new connection, wherein the SingleStore side does not have any details yet, but Azure has some of the previous provisioning information exisitng, this can cause an error.
In such a case, use Delete configuration in the Overview (preview) page to have a clean SCIM provision on the Azure side. -
If the Azure provisioning system tries to sync with non-existent attributes then delete and again re-enter the Attributes mapping.
Last modified: December 15, 2025