Preparing Azure ADLS Integration
Snowflake · Cloud Integrations
Theory
Before connecting Snowflake to Azure storage, gather a few things. You need your Azure tenant ID (from Microsoft Entra ID, formerly Azure AD), the storage account and container name, and the path Snowflake should read. Snowflake URLs for Azure use the form azure://<account>.blob.core.windows.net/<container>/<path>, for both Blob storage and ADLS Gen2.
Access is granted through Azure role-based access control. Snowflake provides a multi-tenant application; once an admin consents to it, it appears in your tenant as a service principal, and you give it a role such as Storage Blob Data Reader (read only) or Storage Blob Data Contributor (needed to unload or purge files) on the container or storage account.
Why we use it
Preparing the Azure side first avoids the most common integration failures: wrong tenant ID, wrong URL format or missing role assignments. It also lets the Azure admin approve exactly the access Snowflake needs.
When to use it
Do this before creating the storage integration whenever data lives in Azure storage. Decide early whether Snowflake only reads (Reader) or also writes (Contributor), and scope the role to the container rather than the whole account.
Consenting to Snowflake's Azure App
After you create the storage integration, DESC STORAGE INTEGRATION returns an AZURE_CONSENT_URL and an AZURE_MULTI_TENANT_APP_NAME. Opening the consent URL as an Azure admin adds Snowflake's multi-tenant service principal to your tenant — you do not register an app yourself.
Granting Container Access
Give that service principal the Storage Blob Data Reader role (or Storage Blob Data Contributor if Snowflake must also unload or purge files) on the storage account or container — the Azure equivalent of an AWS IAM role, with no keys stored in Snowflake.
Blob Storage and ADLS Gen2
The same integration works for Azure Blob Storage and ADLS Gen2 (Blob Storage with a hierarchical namespace). Use the azure://<account>.blob.core.windows.net/<container>/ URL form in STORAGE_ALLOWED_LOCATIONS and stage URLs.
How it works
- Data lives in an Azure storage container
- Note the tenant ID from Microsoft Entra ID
- Note the storage account, container and path
- Will Snowflake also unload or delete files? Yes: Plan the Storage Blob Data Contributor role. No: Plan the Storage Blob Data Reader role.
- Find an Azure admin who can grant consent and role assignments
- Ready to create the storage integration
Example
CREATE OR REPLACE STORAGE INTEGRATION azure_integration
TYPE = EXTERNAL_STAGE
STORAGE_PROVIDER = 'AZURE'
ENABLED = TRUE
AZURE_TENANT_ID = 'your-azure-tenant-id'
STORAGE_ALLOWED_LOCATIONS = ('azure://myaccount.blob.core.windows.net/mycontainer/data/');Key points
- The integration needs your Azure tenant ID
- Use the blob.core.windows.net endpoint in Snowflake URLs, also for ADLS Gen2
- Container-level role assignments control what Snowflake can read
- Reader is enough to load; Contributor is needed to unload or purge
- Role assignments can take a few minutes to take effect