Check which released records reached the archive this month.
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.
Azure
Transfer reconciliation
- Records sent, destinations and failed transfers
- Missing or unmatched information
- Next steps for your team to 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.
2Start 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.
3Before 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.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
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.