Overview
Azure Blob Storage publishing lets your workspace publish Shorthand stories directly to an Azure container through a saved publishing location.
Note: Azure Blob Storage publishing is available on selected plans. A workspace owner can contact Shorthand to discuss availability.
Set up and use Azure Blob Storage publishing
Have these details ready before creating the publishing location:
The Azure Storage Account name
The Container that will store the published story files
The URL Base where readers will load the files, including the protocol, hostname, and any path
Either an access key connection string or a shared access signature (SAS) token
Access to Workspace Settings → Publishing
The URL Base must serve files from the configured container, either directly or through a custom domain or content delivery network (CDN).
Important: A connection string and a SAS token are credentials. Store them securely. Do not share them in email, chat, screenshots, source code, or support tickets.
Create the publishing location
From the Shorthand dashboard, select Settings.
Under Workspace Settings, select Publishing.
On Workspace publishing options, find Azure Blob Storage 1 click external hosting.
Select Create.
Find the Azure Blob Storage card under Workspace Settings → Publishing, then select Create.
Keep this Shorthand form open while you collect the matching values from Azure.
Gather the Azure storage details
In the Azure portal, open Storage accounts.
Select the storage account that will hold your Shorthand stories.
Open Storage accounts in the Azure portal, then choose the account you want Shorthand to publish to.
In the storage account menu, use Containers, Access keys, and Shared access signature to find the values required by Shorthand.
These Azure menu items contain the container and authentication details used in the Shorthand form.
Record these values:
Storage Account: The storage account name
Container: The container that will hold the published story files
URL Base: The public base URL that maps to the container, such as
https://<storage-account>.blob.core.windows.net/<container>/, or a configured custom domain or CDN URL
Choose the authentication method
Shorthand supports an access key connection string or a shared access signature (SAS) token.
Use an access key connection string
In the storage account, go to Security + networking → Access keys.
Select Show keys.
Copy a complete Connection string.
Copy a complete connection string from Access keys and keep it secret.
For more detail, see Microsoft's guide to view storage account access keys and connection strings.
Use a shared access signature token
Go to Security + networking → Shared access signature.
Use HTTPS only and set an appropriate expiry.
Ask your Azure administrator for the narrowest access that still lets Shorthand upload, list, replace, and delete published blobs.
Generate the SAS and copy the SAS token, not the complete service URL.
Use this screen to find the account SAS settings. The selections shown are illustrative, not recommended permissions.
See Microsoft's shared access signature overview.
Tip: A SAS token can limit access and expire without rotating the storage account key. Choose a lifetime that still allows Shorthand to verify, publish, republish, and unpublish stories.
Enter the publishing details and save
Return to the Shorthand form, then:
Enter a clear Name. Team members will use this name to choose the location in the Editor.
Optionally enter a Description to help team members identify the correct location.
Enter the Storage Account, Container, and URL Base values from Azure.
Under Authentication Method, choose Access Key Connection String or Shared Access Signature (SAS) Token.
Paste the matching credential into the field that appears.
Select Save.
Important:URL Base must point to the location from which readers will load the published files. If the URL does not map to the configured container, the story URL or its assets will not work.
Verify the connection
Find the new Azure Blob Storage publishing location under Workspace Settings → Publishing.
Select Verify.
Wait for the Publish Configuration Verified confirmation.
Verification uploads and then deletes a small temporary file. A successful result confirms that the storage account, container, and credential permit both operations. If verification fails, use the troubleshooting steps below before publishing.
Publish your story
Open the story in the Shorthand Editor.
Select Publish.
Choose the publishing location that uses your Azure Blob Storage configuration.
Under Set the story URL, review or enter the directory name. This becomes part of the published URL.
Review the directory and complete URL before selecting Publish to this URL.
Check the complete URL shown in the publishing panel.
Select Publish to this URL.
When publishing finishes, open the exact URL shown by Shorthand and check the story and its media.
Important: Publishing to a directory that already contains a story overwrites the files at that URL. Use a short, unique directory name, such as annual-report, and confirm the destination before publishing.
To update the story later, republish it to the same publishing location and URL.
Best practices and troubleshooting
Save is disabled: Check that every required field is complete and that you selected the correct Authentication Method.
Verification fails: Confirm the Storage Account and Container names, check that the connection string is complete or the SAS token has not expired, and confirm that the credential permits upload, list, replace, and delete operations.
The story publishes, but the URL does not load: Confirm that URL Base maps to the configured container and that the Azure endpoint, custom domain, or CDN serves the published files to readers.
A credential was rotated or expired: Open Workspace Settings → Publishing, select Edit, enter the replacement credential, then select Save and Verify.
Team members cannot find the location: Check the location's Name, enabled state, team assignment, and publishing permissions.
FAQs
Does connecting Shorthand make the Azure container public?
Does connecting Shorthand make the Azure container public?
No. The connection string or SAS token allows Shorthand to manage published files. You must separately configure the Azure endpoint, custom domain, or CDN so readers can load the story from URL Base.
Should I use a connection string or a SAS token?
Should I use a connection string or a SAS token?
Both methods are supported. A connection string uses a storage account access key. A SAS token can be restricted and given an expiry. Follow your organisation's Azure security policy.
What access does a SAS token need?
What access does a SAS token need?
The token must allow Shorthand to verify the connection and manage the published files. This includes the Blob service operations needed to upload, list, replace, and delete blobs. Your Azure administrator should grant the narrowest permissions that support those operations.
Who can publish to the Azure location?
Who can publish to the Azure location?
Access for teams and team members depends on the workspace's publishing permissions.
What happens when I republish a story?
What happens when I republish a story?
Republishing to the same location and URL replaces the previously published files with the latest version of the story.