Configuring Azure ADLS Integration
Snowflake · Cloud Integrations
Theory
CREATE STORAGE INTEGRATION ... STORAGE_PROVIDER = 'AZURE' records your AZURE_TENANT_ID and the allowed container paths. Running DESC INTEGRATION then shows AZURE_CONSENT_URL and AZURE_MULTI_TENANT_APP_NAME. An Azure admin opens the consent URL and accepts, which adds Snowflake's application to your tenant as a service principal. In the Azure portal you then assign that service principal a Storage Blob Data role on the container.
Once consent and the role are in place, you create external stages with STORAGE_INTEGRATION = azure_integration and a URL inside the allowed locations. One integration can serve many stages, for example one per folder or container.
Why we use it
This handshake gives Snowflake access without storing an account key or SAS token in SQL. Access is controlled in Azure, and removing the role assignment immediately cuts Snowflake off.
When to use it
Use this for all production Azure stages. A SAS token in CREATE STAGE is acceptable only for quick tests. Create one integration per tenant and set of allowed locations, and reuse it across stages.
Creating the Storage Integration Object
CREATE STORAGE INTEGRATION links Snowflake to your Azure tenant ID and target container in one statement, mirroring the AWS storage integration pattern.
The Consent Step
Running DESC INTEGRATION afterward reveals a consent URL that an Azure admin must open and approve — without this step, Snowflake's application has no actual permission yet.
Reusing One Integration
A single integration object can back multiple external stages pointed at different containers or folders inside its allowed locations, so you don't need to repeat the consent and role-assignment steps for every new data source.
How it works
- CREATE STORAGE INTEGRATION with tenant ID and allowed locations
- DESC INTEGRATION to read the consent URL and app name
- Azure admin opens the consent URL and accepts
- Assign the Snowflake service principal a Blob Data role on the container
- CREATE STAGE using the integration
- Does LIST @my_azure_stage return files? Yes: Grant stage usage and start loading. No: Recheck consent, role scope and URL.
- Integration is ready for reuse
Example
DESC INTEGRATION azure_integration;
-- AZURE_CONSENT_URL: open this to grant Snowflake access
-- AZURE_MULTI_TENANT_APP_NAME: grant this app access to your container
CREATE OR REPLACE STAGE my_azure_stage
STORAGE_INTEGRATION = azure_integration
URL = 'azure://myaccount.blob.core.windows.net/mycontainer/data/'
FILE_FORMAT = my_csv_format;Key points
- DESC INTEGRATION reveals the consent URL for admin approval
- Grant Snowflake's service principal a role on the container
- One integration can back multiple external stages
- Stage URLs must sit inside STORAGE_ALLOWED_LOCATIONS
- No account keys or SAS tokens are stored in Snowflake SQL