Nightly backup of 311 requests
Each night, all Sentra 311 requests are written as a dated JSON file to the city's own Azure container.
Azure Blob Storage is Microsoft's object storage. Cities on Azure use containers for backups, data exports, archives and files exchanged with vendors, often alongside Microsoft 365 and Azure SQL.
SentraBridge reads files from a container, writes new ones and moves processed files to an archive path. Flows can turn database rows or API records into CSV or JSON files, or load files into another system. The files live in the city's storage; SentraBridge only logs counts and file names.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Files | CSV, JSON, JSON Lines, XML, fixed-width, ACH, BAI2, GeoJSON, Shapefile | write files (including positive pay), transfer documents | yes (new files) | Columns from the file |
Each night, all Sentra 311 requests are written as a dated JSON file to the city's own Azure container.
A permits or work order table in Azure SQL is exported nightly as a CSV so there is a plain-text copy outside the database.
A vendor writes daily files into a container; SentraBridge reads new files, loads rows into SQL Server and archives the files.
Records from several systems are written in one shape as JSON Lines for the city's analytics team to pick up.
Systems cities commonly connect with Azure Blob Storage, each with its own connector page.
With a container SAS token. It needs read, add, create, write, delete and list rights on that container, and you set its expiry.
Yes. A scheduled flow reads a table or query and writes it as a dated CSV or JSON file to the container.
No. File contents pass through memory. Run history records which files were read or written and how many rows.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.