DriftOps polls an Azure Blob Storage container on a schedule. New blobs matching your file pattern are downloaded, compared against the linked contract, and drift events are created for any differences.

Prerequisites

• An Azure Storage account with a container holding the files you want to monitor
• Either a connection string or a storage account name and key

Create the connection

1. Go to Cloud Connections and click New Connection.
2. Select Azure Blob as the provider.
3. Fill in the form:
   • Name: a label for this connection
   • Connection String or Account Name + Account Key (see Authentication options)
   • Container Name: the exact name of the Blob container
   • Prefix (optional): a virtual directory prefix, e.g. incoming/orders/
   • File Pattern: glob pattern, e.g. *.json
   • Contract: the contract to compare incoming files against
   • Poll Interval: how often to check (minutes, default 60)
4. Click Save.

Credentials are encrypted with Fernet before storage. The raw credentials are never returned by the API.

Authentication options

Connection string (recommended for simplicity):

Find your connection string in the Azure Portal under your storage account at Access keys. It looks like:

DefaultEndpointsProtocol=https;AccountName=mystorageaccount;AccountKey=...;EndpointSuffix=core.windows.net

Account name + account key:

Use the storage account name (e.g. mystorageaccount) and either key1 or key2 from the Access keys page.

DriftOps requires only read access to the container. If you want to scope permissions tightly, create a Shared Access Signature (SAS) token with Read and List permissions and convert it to a connection string format.

Configuration options

Troubleshooting

Authentication error

• Verify the connection string is complete and not truncated.
• If using account name + key, check that you copied the key correctly. Azure keys are base64-encoded and long.
• Confirm the storage account is not behind a firewall that blocks DriftOps.

Container not found

• Container names in Azure are lowercase only. Double-check the casing.
• Confirm you have at least Storage Blob Data Reader role on the container if using Azure AD rather than account keys.

No files processed

• Check that the file pattern matches your blob names.
• If using a prefix, verify it matches the blob path exactly. Azure virtual directories are case-sensitive.