Registering an Azure App for Snowflake Integration

Learn how to register a new application in Microsoft Azure to establish a secure connection with Snowflake. This guide covers configuring API scopes, generating client secrets, and granting the necessary admin permissions for seamless integration.

Julie Gallina
38 steps
4 minutes

Azure

Create an Entra App Registration for the Snowflake Client

Click "App registration"

Type the preferred name of the Client, for the sake of this demonstration, we will use "snowflake-client-EXAMPLE"

The supported account type should be "Single tenant only". Leave the Redirect URI value null.

Click "Register"

Copy the Directory (tenant) ID value. This replaces the <tenant> variable in the Snowflake SECURITY INTEGRATION script and verification auth token CURL request. Additionally, Authenticx requires this value for the integration.

Drop down the Manage permissions

Click "Expose an API" to configure this resource

Click "Add"

You may modify the default GUID or leave it as is. Once you are satisfied with the value, click "Save"

Copy the Application ID URI. This replaces the <SNOWFLAKE_APPLICATION_ID_URI> variable in the Snowflake SECURITY INTEGRATION script and verification auth token CURL request. Additionally, Authenticx requires this value for the integration.

Click "Add a scope" to allow a more limited resource to be used for the Client Id / Secret creation

Give the scope a name, for example "session:writer"

Then, give the scope a display name, for example "Write to specified tables"

Lastly, give the scope a display name, for example "Authenticx role for writing to specific tables in Snowflake"

Save the Scope by clicking "Add scope"

Go back to home Microsoft Entra ID page to create another application

Click Add

Click "App registration"

Type the preferred name of the Client, for the sake of this demonstration, we will use "snowflake-client-EXAMPLE"

The supported account type should be "Single tenant only". Leave the Redirect URI value null.

Click "Register"

Copy the Application (client) ID. This replaces the <OAUTH_CLIENT_ID> variable in the verification auth token CURL request. Additionally, Authenticx requires this value for the integration.

Click "Certificates & secrets"

Generate a secret by clicking "New client secret"

Add an appropriate description in the "Description" field, for example "Authenticx Snowflake Secret"

Click "Add"

Copy the secret value, it will never be visible again once leaving this page. Additionally, Authenticx requires this value for the integration.

Lastly, we need to configure the API permissions by clicking "API permissions"

Click "Add a permission"

Click "APIs my organization uses"

Search the Application you created above in steps 1-5 by name. For example, "snowflake-client-EXAMPLE"

Select the Appropriate Application

Click the check box next to the Scope created in steps 12-16 to add this permission

Click "Add permissions" to save

Click "Grant admin consent" to fully allow the resources to communicate to each other

Securely provide the Client Id, Client Secret, and Application ID URI to your Authenticx implementation team.

You are done. Pat yourself on your back.

Registering an Azure App for Snowflake Integration

Julie Gallina
38 steps
4 minutes

Azure

Create an Entra App Registration for the Snowflake Client

Click "App registration"

Type the preferred name of the Client, for the sake of this demonstration, we will use "snowflake-client-EXAMPLE"

The supported account type should be "Single tenant only". Leave the Redirect URI value null.

Click "Register"

Drop down the Manage permissions

Click "Expose an API" to configure this resource

Click "Add"

You may modify the default GUID or leave it as is. Once you are satisfied with the value, click "Save"

Click "Add a scope" to allow a more limited resource to be used for the Client Id / Secret creation

Give the scope a name, for example "session:writer"

Then, give the scope a display name, for example "Write to specified tables"

Lastly, give the scope a display name, for example "Authenticx role for writing to specific tables in Snowflake"

Save the Scope by clicking "Add scope"

Go back to home Microsoft Entra ID page to create another application

Click Add

Click "App registration"

Type the preferred name of the Client, for the sake of this demonstration, we will use "snowflake-client-EXAMPLE"

The supported account type should be "Single tenant only". Leave the Redirect URI value null.

Click "Register"

Copy the Application (client) ID. This replaces the <OAUTH_CLIENT_ID> variable in the verification auth token CURL request. Additionally, Authenticx requires this value for the integration.

Click "Certificates & secrets"

Generate a secret by clicking "New client secret"

Add an appropriate description in the "Description" field, for example "Authenticx Snowflake Secret"

Click "Add"

Copy the secret value, it will never be visible again once leaving this page. Additionally, Authenticx requires this value for the integration.

Lastly, we need to configure the API permissions by clicking "API permissions"

Click "Add a permission"

Click "APIs my organization uses"

Search the Application you created above in steps 1-5 by name. For example, "snowflake-client-EXAMPLE"

Select the Appropriate Application

Click the check box next to the Scope created in steps 12-16 to add this permission

Click "Add permissions" to save

Click "Grant admin consent" to fully allow the resources to communicate to each other

Securely provide the Client Id, Client Secret, and Application ID URI to your Authenticx implementation team.

You are done. Pat yourself on your back.