Skip to content
infolio infolio
Sync setup guide 6 min read Updated 2026-07-15

How to Use Azure Blob Storage to Sync an infolio Knowledge Base

A setup checklist for using Azure Blob Storage as an infolio custom sync source: storage account, container, endpoint, connection string, SAS or access key, permissions, and recovery testing.

Quick answer

Azure Blob Storage fits users who already manage Azure storage accounts. Before configuring infolio, prepare the storage account, container, endpoint, and the credential type requested by the product: connection string, SAS, or access key.

Steps

1

Create a dedicated storage account and container

Prepare a separate Storage account or at least a separate container for infolio. Blob Storage stores unstructured data, and a dedicated container reduces permission and cleanup risk.

  • Record the storage account name.
  • Create an infolio-specific container.
  • Do not mix sync data with public static sites or production app data.
2

Prepare endpoint and credential

Microsoft documents that connection strings are available from the Access keys page and include AccountName and AccountKey. Azure also supports SAS for limited delegated access.

  • Prefer HTTPS endpoints.
  • Use the credential type requested by infolio: connection string, SAS, or key.
  • Do not store AccountKey or SAS values in ordinary notes.
3

Limit permissions and expiry

If you use SAS, set a narrow resource scope, permission set, and expiry. Microsoft recommends user delegation SAS when possible because it is secured with Microsoft Entra credentials rather than the account key.

  • Grant only the permissions needed for the infolio container.
  • Avoid broad SAS tokens that never expire.
  • Record expiry and rotation dates.
4

Configure Azure Blob sync in infolio

Enter the storage account, container, endpoint, and credential requested by infolio. Test read, write, and recovery with a small knowledge base before relying on it.

  • Check SAS permissions or AccountKey if you see 403 errors.
  • Check endpoint and protocol if connection fails.
  • Confirm the container name is correct.
5

Verify recovery and key rotation

Connect another device to the same Azure Blob sync source and confirm knowledge-base recovery. Keep key rotation notes so devices do not lose sync after credential changes.

  • Confirm documents, whiteboards, and workspaces recover.
  • Confirm vault unlocking still works.
  • Validate the new credential before disabling the old one.

Related pages

Azure Blob sync source See when Azure Blob sync fits infolio workflows. Multi-cloud sync article Compare tradeoffs across sync sources. Object storage sync definition Understand the basics of object storage sync.

FAQ

Should I use a connection string or SAS for Azure Blob sync?

It depends on the current infolio fields and your security strategy. A connection string is direct but broad; SAS can limit resources, permissions, and expiry.

What should I do before rotating Azure access keys?

Validate the new credential in infolio before disabling the old one, otherwise other devices may stop syncing.