Skip to main content

Integration guideSeal API and Scripts

Azure

Send selected Seal records to Azure storage and call approved Azure services.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

Seal to AzureSeal API and Scripts

Seal sends
Selected Seal records and reports
Source of truth
Agreed when scoped
Set up
Scoped with your team
Neil › Transfer reconciliation
draft

Check which released records reached the archive this month.

Neil

  • Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
Reads
Selected Seal records and reports
Returns
  • Records sent, destinations and failed transfers
  • Missing or unmatched information
  • Next steps for your team to review
Illustrative work with Azure: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Send selected Seal records or reports to Azure Blob Storage or Azure Data Lake for storage or further analysis. A Script triggered by a Seal event or schedule can call the Azure services you approve, such as Azure Functions. Agree the records, destination, credentials and failure handling before relying on the transfer.

Connection setup and permissions

Use Seal’s APIs or scripting engine for a connection tailored to your process. Agree the data mapping, access and direction of transfer before implementation.

2Write Seal records and reports to Azure Blob Storage.

Route

Put Blob creates a blob, or replaces the whole content of a blob with the same name.⁠¹ Azure Data Lake Storage is Blob Storage with a hierarchical namespace, not a separate service. There, Path Update appends and flushes data to a file.⁠²³

Record identity

A blob’s name is unique within its container.⁠⁴ Put Blob checks a supplied Content-MD5 and fails with 400 if it does not match, and its response carries a CRC64 calculated by the service. On a Data Lake append and flush, Content-MD5 is checked in transit but not stored with the file.⁠¹³

Revisions

With blob versioning on, every write creates a new version, and Put Blob returns the ID of the version it wrote.⁠⁵¹ Blob versioning and version-level immutability are not supported on accounts with a hierarchical namespace, and Path Create overwrites its destination by default.⁠⁵⁶⁷ A locked time-based retention policy holds blobs write-once and cannot be deleted or shortened.⁠⁶

When it fails

A second run overwrote a stored report
If-None-Match: * makes a write succeed only when no blob of that name exists.⁠⁸ Send records that must never change with that header, and look into a refused write as a duplicate.
A Data Lake file cannot be rolled back
Accounts with a hierarchical namespace keep no blob versions.⁠⁵ Give each Seal record version its own path, or use a Blob Storage account with versioning on for records you must keep.

Check one record

Write one approved report to a test container with versioning on. Check the returned CRC64 against the file Seal sent. Write a revised copy under the same name and confirm two version IDs, each matched to its Seal record version.

3Start with the job.

Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.

Discuss this connection →

4Before it goes live.

Access and any write-back

Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.

Verification and release

Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.

Read the assurance detail →

References

  1. 1Azure Storage REST API: Put Blob.
  2. 2Microsoft: Azure Data Lake Storage introduction.
  3. 3Azure Data Lake Storage REST API: Path Update.
  4. 4Azure Storage: naming containers, blobs and metadata.
  5. 5Microsoft: blob versioning.
  6. 6Microsoft: immutable storage for blobs.
  7. 7Azure Data Lake Storage REST API: Path Create.
  8. 8Azure Storage: conditional headers.