Back up Procore, Autodesk Forma and Aconex projects to Azure Blob Storage in your own subscription.

What does SIINC write into an Azure Blob container?

The original files with their revisions, plus JSON metadata for each record, encrypted and laid out in a documented folder structure you can read with standard Azure tools. The first run is a Full backup of everything in scope. After that, Sync runs add only what changed since the last run, hourly as standard, and records deleted in the platform are kept for the term of your plan.

A Procore RFI, an Autodesk Forma submittal and an Aconex mail thread all end up in the same governed place: a container in your company's Azure subscription, not a store held by SIINC or by the platform.

Why keep construction backups in your own Azure subscription?

Because the copy then follows your organisation's rules, set by your own Azure administrators. The Blob container sits in your subscription, so you choose the region, and your retention, immutability and access policies apply to SIINC backups as they do to the rest of your Azure data.

Azure has its own controls for records that must not change. Microsoft says immutable storage for Azure Blob data keeps data write once, read many under time-based retention policies, so it cannot be changed or deleted until the retention period ends. SIINC works with Azure immutable storage turned on, and settings like these belong to your Azure subscription and stay under your own governance.

• The region where the data sits
• How long backups are kept, under your own retention rules
• Who in your organisation can read, change or delete them

Reading Azure Blob backups with or without SIINC

The Procore Workbench, Autodesk Portal and Aconex Portal read straight from your Blob container, so your team can search a project and download records without a platform login. The backups are stored as files and records you can read with standard Azure tools, so the copy stays useful even without SIINC.

What you need to set up Azure Blob

A Blob container in your Azure subscription, in the region you choose, and credentials with write access to it. There are no agents to install and nothing runs on your network.

How SIINC checks an Azure Blob container before the first backup

SIINC runs a write test before it saves the storage connection. If the credentials cannot write to the container, you find out while setting up, not after the first scheduled run.

Once the connection is saved, every backup run is recorded with its scope, size, warnings and errors, and summaries are emailed to your team.

What it costs to keep SIINC backups in Azure Blob Storage

Two separate bills. Azure charges you for the Blob storage directly, at your own rates, in your own subscription. SIINC charges per GB per month for the service, portals, scheduling, monitoring and support on the data it backs up.