Microsoft Entra ID
Standards

Snowflake Provisioning Tutorial

In brief

The tutorial now links to Snowflake SCIM documentation, specifies using an account administrator, explains the SQL script, emphasizes that `AAD_PROVISIONER` is case-sensitive and uppercase, and adds related authentication links.

What Entra admins need to know

Use the clarified roles and capitalization when configuring provisioning, and refresh SCIM access tokens before their six-month expiry to keep synchronization working.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Step 2: Configure Snowflake to support provisioning with Microsoft Entra ID

Before you configure Snowflake for automatic user provisioning with Microsoft Entra ID, you need to enable System for Cross-domain Identity Management (SCIM) provisioning on Snowflake. For more information, see CREATE SECURITY INTEGRATION (SCIM).

  1. Sign in to Snowflake as an administrator and executeaccount administrator.

  2. Execute the following from either the Snowflake worksheet interface or SnowSQL.

    use role accountadmin;
     create role if not exists aad_provisioner;
     grant create user on account to role aad_provisioner;
     grant create role on account to role aad_provisioner;
     grant role aad_provisioner to role accountadmin;
     create or replace security integration aad_provisioning
         type = scim
         scim_client = 'azure'
         run_as_role = 'AAD_PROVISIONER';
     select system$generate_scim_access_token('AAD_PROVISIONING');
    

Use This script performs the ACCOUNTADMIN role.following tasks:

Screenshot of a worksheet in the Snowflake UI with the SCIM access token called out.

  1. Uses the ACCOUNTADMIN role.
![Screenshot of a worksheet in the Snowflake UI with the SCIM access token called out.](media/Snowflake-provisioning-tutorial/step-2.png)
  1. CreateCreates the custom role AAD_PROVISIONER. AllAAD_PROVISIONER. The users and roles in Snowflake created by Microsoft Entra ID isare owned by the scoped down AAD_PROVISIONER role.

    Screenshot showing the custom role.

![Screenshot showing the custom role.](media/Snowflake-provisioning-tutorial/step-3.png)
  1. Let the ACCOUNTADMIN role create the security integration usingthat uses the AAD_PROVISIONER custom role.

    Screenshot showing the security integrations.

    The value AAD_PROVISIONER is case-sensitive and must always be capitalized.
![Screenshot showing the security integrations.](media/Snowflake-provisioning-tutorial/step-4.png)
  1. Create and copy the authorization token to the clipboard and store securely for later use. Use this token for each SCIM REST API request and place it in the request header. The access token expires after six months and a new access token can be generated with this statement. For more information, see SYSTEM$GENERATE_SCIM_ACCESS_TOKEN.

    Screenshot showing the token generation.

Connector limitations

Snowflake-generated SCIM tokens expire in 6 months. Be aware that you need to refresh these tokens before they expire, to allow the provisioning syncs to continue working. For more information, see SYSTEM$GENERATE_SCIM_ACCESS_TOKEN.

Just-in-time (JIT) application access with PIM for Groups

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…