Azure Storage Data Sources
Use Azure Storage Account for blobs and Azure File Share for named SMB-style shares. They may use the same storage account, but they are different Data sources and selectors.
Both creation forms expose an optional Store source files switch under Processing, off by default. Enable it only when the original blob or file-share binary must be retained in addition to extracted text and indexed chunks. See Store Source Files for the canonical behavior and storage trade-off.
Prepare the Connection
An admin first creates an Azure Storage Account connection. The credential or connection string belongs in Connections. Never paste DefaultEndpointsProtocol=..., an account key, or SAS secret into the Data-source selector.
Prefer a read-only, container/share-scoped credential where the released connection design supports it. Record the owner and rotation process without copying the secret into descriptions or tickets.
Azure Storage Account (Blobs)
Use it for application exports, generated documents, archive feeds, and repositories published to Blob Storage.
| Field | What to enter |
|---|---|
| Name | Feed and purpose, for example Production exports — Approved PDFs |
| Description | Owner, account/container context, selector convention, exclusions |
| Connection ID | Stored Azure Storage connection |
| Sync frequency | On Demand, Daily, Weekly, or Monthly |
| Blobs | One or more blob names, paths, or selectors expected by the configured source |
At least one Blob value is required. The current form validates presence, not whether the selector matches readable data. Always inspect resulting files and logs.
Azure File Share
Use Azure File Share for documents published to an Azure SMB share, including files copied from Windows servers. Siesta AI reads the named share through an Azure Storage connection; it does not connect directly to the original Windows folder.
Follow Azure File Share Data Sources for mounting the share, copying files with ACLs, entering share names, and checking the first import. That guide also explains the independent copy and ingestion schedules.
Which One Should You Use?
Use the object that already owns updates: blobs for pipeline/object delivery, File Share for an SMB-style share. Do not choose File Share merely because the storage account also exposes one.
Admin Verification
After key rotation, run a controlled synchronization and verify representative documents. Split sources when account/container/share ownership, audience, retention, or schedule differs. A successful status without expected files is not an acceptance test.