Snowflake × Azure ADLS Integration Guide
Snowflake · Cloud Integrations
Theory
The full Azure setup is a chain, and each link depends on the one before it. First prepare the Azure side (tenant ID, container, path). Then create the storage integration in Snowflake and run DESC INTEGRATION. An admin opens the consent URL, and you assign Snowflake's service principal a Storage Blob Data role on the container. Next create a file format and an external stage using the integration, grant USAGE on the integration and stage to the loading role, and finally run COPY INTO.
Most failures come from one broken link: consent not granted, the role assigned at the wrong scope, a URL outside STORAGE_ALLOWED_LOCATIONS, or the loading role missing USAGE. Testing with LIST after each step finds the problem quickly.
Why we use it
Seeing the whole sequence prevents half-finished setups and makes debugging systematic. When a load fails, you can walk the chain in order instead of guessing.
When to use it
Use this as a checklist for every new Azure source and when a previously working load starts failing with access errors. For several containers, reuse one integration and add stages.
The Full Setup Sequence
Note the tenant ID and container path, run CREATE STORAGE INTEGRATION, open the AZURE_CONSENT_URL from DESC STORAGE INTEGRATION as an Azure admin, assign Snowflake's service principal a Storage Blob Data role on the container, create an external STAGE on that integration, then COPY INTO your table. You never register your own Azure app.
Where Setups Usually Break
A single misconfigured RBAC role at the container level is the most common point of failure — DESC STORAGE INTEGRATION is the most useful command for debugging a stalled connection.
Validating Each Step
Test the stage independently with LIST @stage_name before attempting a full COPY INTO, so a permissions problem shows up immediately rather than mid-load.
How it works
- Prepare tenant ID, container and path
- CREATE STORAGE INTEGRATION and DESC it
- Grant admin consent and assign the Blob Data role
- Create the file format and external stage
- Does LIST @stage work as the loading role? Yes: Run COPY INTO the table. No: Check consent, role scope, allowed locations and grants.
- Load succeeds; schedule it or add Snowpipe
Example
-- 1. Note tenant ID, storage account, container and path
-- 2. CREATE STORAGE INTEGRATION ... STORAGE_PROVIDER = 'AZURE'
-- 3. DESC STORAGE INTEGRATION -> open AZURE_CONSENT_URL as an Azure admin
-- 4. Assign Storage Blob Data Reader/Contributor to the Snowflake service principal
-- 5. CREATE STAGE ... STORAGE_INTEGRATION = azure_integration
-- 6. LIST @stage, then COPY INTOKey points
- Validate each step before moving to the next
- DESC STORAGE INTEGRATION helps debug consent and permission issues
- A missing Azure role assignment or Snowflake grant is the most common failure
- Test LIST as the same role that will run COPY
- Role assignments can take a few minutes to apply