OpsWork Book a demo

Data Residency

UK South. Your tenant. Your subscription.

Every Azure resource that touches customer data is deployed into the customer's own subscription in UK South. Customer email and documents never leave the customer's Microsoft 365 tenant. This page summarises where every byte lives and why.

Last updated: 13 June 2026

Customer perimeter

Your tenant. Your subscription.

Customer email, documents and project data stay inside the customer's own Microsoft 365 tenant and Azure subscription throughout.

Region

UK South for every customer resource.

Azure Functions, Logic Apps, Key Vault, Application Insights, Log Analytics, Azure OpenAI and Blob backups all provision into UK South. No exceptions for production customer environments.

Transfers

No customer data leaves the UK.

There is no OpsWork-side copy, mirror or aggregate of customer content. Cross-customer pattern memory does not exist. No data lake. No model training.

Where every byte lives

Surface-by-surface residency map.

Surface Location Region Note
Customer email and documents Customer's own Microsoft 365 tenant Customer-controlled (UK for UK customers) OpsWork never copies email or documents out of the customer tenant.
Agent compute (Azure Functions, Logic Apps) Customer's Azure subscription UK South Deployed by the OpsWork wizard into the customer's own subscription. The resource group, billing and access are owned by the customer.
Operational storage (Key Vault, Application Insights, Log Analytics) Customer's Azure subscription UK South Secrets, audit log, telemetry. All inside the customer's resource group.
AI inference (Azure OpenAI) Customer's Azure subscription UK South — Standard deployment Prompts and completions are not retained by the model and are not used to train any model. Azure OpenAI runs inside Microsoft Azure; OpenAI is not a sub-processor.
Knowledge graph (Microsoft Fabric / OneLake) Customer's Microsoft tenant UK South Project, RFI, quotation and decision history. Indexed inside the customer environment for Robert, James and Michael.
Backups (Azure Blob) Customer's Azure subscription UK South, locally redundant Customer-controlled retention. Quarterly restore test documented in the operations runbook.
Marketing website (opswork.uk) Cloudflare Pages EU points of presence (Workers configuration restricts edge to EU) No customer data is processed on the marketing website. Lead-form submissions land in the OpsWork sales mailbox; see the privacy policy for handling.
Transactional email (system notifications) Microsoft 365 / Microsoft Graph (Office 365 connector) UK South / customer UK tenant OpsWork-generated wizard and notification email is sent via Microsoft Graph (Office 365 connector, ADR-018). SendGrid was removed 2026-05-10. Customer-content email flows through the customer's Microsoft 365 tenant.

What this means

Six commitments that make residency real.

Customer-controlled boundary

OpsWork deploys into the customer's own Microsoft 365 tenant and Azure subscription. The data perimeter is the customer's, not OpsWork's. Customer holds the keys, the resource locks and the billing.

UK South for all production processing

Per ADR-002, every Azure resource that processes customer data is provisioned in UK South. The wizard refuses to deploy outside UK South for customer environments. We do not use a non-UK region as a hot standby.

No customer data leaves the tenant

OpsWork Ltd does not receive, copy, mirror or aggregate customer email, documents, project data or AI prompts off-tenant. There is no central OpsWork data lake. Cross-customer pattern memory does not exist.

No training on customer data

Customer prompts and completions are not used to train, fine-tune or evaluate any model — ours, Microsoft's or OpenAI's. This is contractually guaranteed in the Data Processing Agreement.

International transfer surface = none for customer content

Customer content does not transit outside the UK as part of OpsWork's processing. The only data that leaves the UK is OpsWork's own corporate correspondence (which uses EU-region transactional email).

30-day change notice

If a sub-processor or region is added, removed or replaced, every customer receives 30 days' written notice before the change takes effect, with a right to object and terminate without penalty if the objection cannot be resolved.

For your reviewer

Procurement, InfoSec, legal and DPO checks.

OpsWork is operated by Saqib Engineering Ltd (Companies House registration 15866031) trading as OpsWork. The Customer is the Data Controller. OpsWork Ltd is the Data Processor under UK GDPR Article 28. Microsoft Corporation is a sub-processor in respect of the underlying Azure and Microsoft 365 platform that hosts the customer environment.

The contractual position on residency is set out in the Data Processing Agreement. The full sub-processor list is at opswork.uk/sub-processors. The privacy position for individuals is at opswork.uk/privacy. The security control set is at opswork.uk/security.

Available on request

Architecture review pack

Components, identities, data flows, residency map.

Available on request

DPIA template

Pre-populated for OpsWork deployments to UK HV consultancies.

Available on request

Security questionnaire responses

Standard frameworks supported.

Available on request

UK South region attestation

Microsoft evidence pack for Azure UK South.

Email [email protected] to request the procurement pack, or [email protected] for a 20-minute residency walk-through.