Azure Blob Storage + Transloadit

Build the integration

This Template imports one Azure Blob, resizes it, and stores the result under processed/ in the configured container.

1. Create an Azure Blob container and retrieve a storage account key.
2. Save the account, key, and container as Template Credentials named my_azure_credentials.
3. Paste the Instructions into a Template and start an Assembly from that Template.

{
  "steps": {
    "imported": {
      "robot": "/azure/import",
      "credentials": "my_azure_credentials",
      "path": "incoming/photo.jpg"
    },
    "resized": {
      "robot": "/image/resize",
      "use": "imported",
      "width": 1200,
      "height": 1200,
      "resize_strategy": "fit"
    },
    "exported": {
      "robot": "/azure/store",
      "use": "resized",
      "credentials": "my_azure_credentials",
      "path": "processed/${file.url_name}"
    }
  }
}

Authentication

• Save the Azure storage account name, account key, and Blob container as Transloadit Template Credentials.
• Use a dedicated storage account or rotate the account key on a schedule because Shared Key grants broad authority over the account.
• Do not place the account key directly in a public Template or client application.

Limitations and operational notes

• The Azure Robots currently authenticate with the storage account and account key. They do not accept Microsoft Entra ID, managed identity, or SAS credentials.
• Microsoft recommends Entra ID or a user-delegation SAS when possible, so review whether Shared Key is acceptable for your security policy.
• A generated SAS result URL is optional and expires after the number of seconds configured with sas_expires_in.