Security

Kept in your Microsoft 365. Approved by you.

Your project information is a business asset. OpsWork runs in your own Microsoft 365 and Azure, so your email, files and records stay where they are, and nothing leaves until you approve it.

Your business stays fenced inside your own Microsoft 365 with your key; OpsWork prepares only what it needs inside it; you approve; everything is ready when IT or an auditor asks.

For your IT reviewer

Where it runs
In your own Microsoft 365 and Azure. There is no central OpsWork copy of your project data.
Location
UK South only.
Approval
Nothing goes out without your approval.
Support access
Only with your approval, for a defined scope, and it can be revoked.
Sign-in
Your own Microsoft sign-in rules, such as MFA and Conditional Access, apply.
Your data
Never used to train any model. This is guaranteed in the Data Processing Agreement.

The detailed data-location and component table is in the procurement pack. Ask for the IT pack

Everything in one place: Trust

Where your data lives.

Your email, drawings and project records stay in your own Microsoft 365 and Azure, in the UK South region. They are yours, and they are still yours when the service ends.

Published commitments

Residency commitments

Read these commitments alongside the processing arrangements in the DPA and Privacy Policy.

Customer-controlled boundary
OpsWork deploys into the customer's own Microsoft 365 tenant and Azure subscription. Customer holds deployment keys, resource locks and billing. Optional OCR has the separately disclosed Microsoft-managed processing boundary below.
UK South for all production processing
Every Azure resource that processes customer data is provisioned in UK South. OpsWork cannot be set up outside UK South for customer environments. We do not use a non-UK region as a hot standby.
Disclosed processing boundary, no OpsWork-owned OCR tenant
Customer-owned deployment does not mean every processing copy stays in customer-owned storage. Optional OCR uses Microsoft-managed UK South temporary storage, logically isolated per customer, after your managing director has explicitly acknowledged it. It does not use an OpsWork-owned shared tenant or central content lake.
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.
UK processing location is not a blanket transfer guarantee
OCR processing and temporary storage are configured for UK South. This does not by itself establish the location of every Microsoft support or onward-access operation. Applicable Microsoft terms, access safeguards and any transfer mechanisms require contractual review before use.
14-day change notice
If a sub-processor or region is added, removed or replaced, every customer receives 14 days' written notice before the change takes effect. If the controller objects on reasonable data protection grounds and we cannot resolve it, the controller may cancel the affected service at the end of the period already paid for. No refund is due.

This page describes how the products are designed today. It does not form part of the contract and is not a warranty. Our contractual commitments are in the Terms of service and the Data Processing Agreement. You remain responsible for securing your own Microsoft 365 and Azure tenant.