# How do I meet data residency requirements with third-party software?

Canonical page: https://launchinyourcloud.com/questions/data-residency/

Map where the application and every connected service process, store and access data. Include backups, logs, telemetry, AI, identity, support and control planes. Choose documented locations that meet your requirements; selecting a deployment region alone does not establish complete residency.

Answer page: https://launchinyourcloud.com/questions/data-residency/
Answer reviewed: 2026-11-21

- [Review regulated and sovereign deployment](/scenarios/regulated-sovereign/)
- [Map operating responsibilities](/downloads/shared-responsibility-template.md)


## Make a location and access inventory

For each data class, record its processing location, storage, replicas, backups, logs, exports and deletion process. Add the identity provider, model endpoints, monitoring, license service and vendor management plane when they receive relevant information. Include remote administrative and support access in the review.

## Example: an application region is only the first row

A document service can run in the selected region while sending diagnostic logs to another service or calling an externally hosted model. That is a possible architecture to investigate, not a claim about every product. Disabling one integration may change the result without changing the application’s main region.

Define approved locations and access conditions with the people responsible for your obligations. Obtain product-specific evidence, test enabled data flows and record configuration controls. A provider’s headquarters, region name or marketing statement does not settle the entire installation’s residency question.

