Overview
Stigg’s integration with Azure Blob Storage allows you to export your product catalog, customer, and subscription data to an Azure container as structured files — useful for data lake pipelines, custom ETL workflows, or archival.Stigg’s native data export integrations are included in the Scale plan, and are also available as an optional add-on to the Growth plan. See Stigg’s pricing for more details.
Exported entities
When connecting Azure Blob Storage, you can choose which Stigg entity groups to include in the sync. All groups are selected by default. See Exported entities for the full list of entity groups and the tables within each.Entity schema
Setting up the integration
Prerequisites
- An Azure storage account with a Blob Storage container
- A shared access signature (SAS) token with read, write, delete, list, add, and create permissions on the container
Generate a SAS token
In the Azure portal, navigate to your storage account and select Shared access signature.Configure the SAS token with the following permissions: Read, Write, Delete, List, Add, Create. Set an appropriate expiry date.Copy the generated SAS token — you’ll need it when connecting.
Connect Stigg with Azure Blob Storage
In Stigg, navigate to Integrations > Apps > Azure Blob Storage.Enter the following information in the connection form:
Click Test & connect.
| Field | Description |
|---|---|
| Storage account name | The name of your Azure storage account |
| Container name | The name of the Blob Storage container |
| Folder name | The folder path within the container where data will be written. Use . for the container root. |
| SAS token | The shared access signature token generated above |
Select entities to export
After entering your connection details, expand the Entities to export section to choose which entity groups to include in the sync. All groups are selected by default.See Exported entities for a description of each group.