Secure Files - Azure

Not every file belongs on a public CDN: contracts, price sheets, member downloads. If those already sit in Azure Blob Storage, the Secure Files app lets editors attach them to content without opening up the container.

What you can do

• Secure File field: a custom field for content and component models that attaches a file from your Azure container.
• File selector: editors pick the file from a selector inside Agility.
• Pre-signed delivery: your front end generates a pre-signed SAS URL that gives access to one blob for a limited time.
• Your account, your container: you supply the container name and the storage connection string.

Who it's for

Teams publishing gated or sensitive downloads who already run on Azure, and developers comfortable generating SAS URLs on the server. It's a poor fit if you need public, cacheable assets; use the regular media library for those.

Setup needs a storage account, a container and its keys. The docs include the SAS URL code example.

Get started

1. Create a storage account In the Azure portal, create an Azure Blob Storage account.
2. Create a container Add the container that will hold your secure files.
3. Retrieve access keys Copy the storage connection string and access key from the Azure portal.
4. Install and configure Open Settings → Apps in Agility, add Secure Files - Azure and enter the container name and connection string.
5. Add the field Add the Secure File custom field to a content or component model, then generate SAS URLs on your server to deliver files.