A Map You Can Audit: Evidencing Data Residency Across a UK Cloud Estate
Photo: Florian Hirzinger - www.fh-ap.com, CC BY-SA 3.0, via Wikimedia Commons
Most UK organisations can name the cloud region they selected. Fewer can show, with dated evidence, where their data actually rests across primary storage, backups, disaster recovery copies, logging pipelines and vendor support systems. The gap matters because boards, customers and regulators increasingly ask not simply whether a provider is trustworthy, but where specific data is held and how that location is controlled.
A residency check is not a legal audit. It is an operational examination that produces a documented trail. It should be repeatable, proportionate and owned by someone inside the business. For many small and mid-sized UK estates, a quarterly review can be completed in a few hours once the first pass has established the scope.
Begin with the promise, not the dashboard
Residency evidence only has meaning against a stated commitment. Start by collecting the documents that define what has been promised: the master services agreement, data processing agreement, service description, UK region selection records and any sector-specific contractual clauses. Note whether the commitment covers data at rest only, or also support access, backups and telemetry.
Build a simple register. List each material service, the data classification it holds, the contracted location and the evidence source. A payroll system, a document store and a logging platform will not carry the same obligations. The register does not need to be elaborate, but it should be dated and versioned.
Follow the subprocessor chain
Cloud providers rarely deliver a service alone. Subprocessors may handle messaging, monitoring, content delivery, identity verification or support tooling. Ask for the current subprocessor list and a mapping of each relevant subprocessor to the service you use. Confirm how changes are notified and where the list is published.
Evidence should include a dated export of the subprocessor list, not a screenshot of a marketing page. Where a subprocessor operates outside the UK, record the transfer mechanism cited in the contract and the location of any remote access. This is not about second-guessing the provider's legal position; it is about knowing which questions to escalate.
Test the copies, not just the primary store
Residency statements often focus on the primary region. Backups, snapshots, disaster recovery replicas and archive tiers can sit elsewhere. Ask where backup vaults are configured, whether cross-region replication is enabled and which region pair is in use. For Microsoft 365, check tenant storage location and the configured data residency commitments for core workloads.
A configuration export from the cloud console is useful evidence, provided it is dated and shows the relevant settings. Where a provider manages backups on your behalf, request a written confirmation of backup location and retention. Keep these artefacts alongside the register rather than in an email thread.
Support access is a location too
A dataset can be stored in the UK and still be viewed by an engineer elsewhere. Ask how remote support is delivered, which teams can access customer data, what approvals are required and whether access is logged. For higher-assurance workloads, ask whether support can be restricted to UK-based personnel or whether customer-managed keys prevent vendor access.
Evidence might include the support policy, a sample of access logs and a description of break-glass procedures. You do not need to review every support case. You do need to know whether the provider can demonstrate that access is controlled and recorded.
Logging exports and the evidence trail
Audit logs are only useful if they are retained and exportable. Confirm where logging data is stored, how long it is retained and whether exports can be restricted to a UK region. Export a sample of configuration and audit records each quarter and store them with a timestamp.
The aim is a coherent evidence pack: register, contract extracts, subprocessor list, configuration exports, backup confirmations and support-access records. A reviewer should be able to follow the trail without relying on verbal assurance.
The quarterly routine
A practical cadence looks like this. First, confirm the scope: which services and data classes are in view. Second, collect the evidence listed above. Third, compare the evidence against the stated commitment and note exceptions. Fourth, assign an owner and a date to each exception. Fifth, record a short sign-off noting what was reviewed and what remains unresolved.
Keep the pack in a controlled location with access limited to those who need it. A one-page summary for the board is sufficient: services reviewed, evidence obtained, exceptions raised and actions taken. Avoid presenting the review as a legal opinion. It is an assurance artefact, not a substitute for advice on UK GDPR or sector regulation.
Who to ask
Procurement or vendor management should hold the contract and subprocessor correspondence. The platform or IT lead should own configuration exports and backup settings. Security or compliance should review support-access records. Finance may need to confirm that the services in scope match what is being paid for.
Where a provider cannot supply evidence, record the gap plainly. A missing artefact is not proof of wrongdoing, but it is a reason to ask a more specific question. Over time, the register becomes a useful history of what changed and when.
A map that can be checked
Data residency is not a one-time statement made at contract signature. It is a property of a living estate, affected by configuration changes, new services and provider updates. The organisations that manage it well tend to be those that can produce a dated map and explain its boundaries. That is a more modest ambition than a legal audit, and a more useful one for most UK businesses.