Data residency of MFA (email OTP), sign-in logs and SSPR data in an Entra External ID tenant in Japan with Go-Local

上田 信介 20 Reputation points
2026-11-16T12:52:19.2+00:00

We created a Microsoft Entra External ID external tenant with Country/Region set to Japan and the Go-Local data residency add-on enabled. We plan to use it to sign in a few dozen users of a service for healthcare organizations, and we need to explain to those organizations where authentication-related data is stored.

For each of the three items below, could you tell us where the data is stored at rest (in Japan only, or possibly outside Japan; and if outside, which region)?

  1. Multifactor authentication data
    • We use email one-time passcode (Email OTP) as the only second factor. We don't use SMS or voice.
      1. Sign-in logs and audit logs
        • We couldn't find a row that names sign-in logs in the same table. Does the "Microsoft Entra authentication Service" row ("Microsoft Entra authentication Service generates log data in Azure Storage, and in the datacenter where the service instance runs.", "In geo location") cover sign-in logs and audit logs? If not, where are they stored for a Go-Local external tenant?
        1. Self-service password reset data
          • Users set their password from "Forgot password?" on the sign-in page, using an email one-time passcode. Where is the data used in this flow (email address, one-time passcode, reset records) stored? The same table mentions SSPR only in the password writeback row, and we couldn't find anything about password reset in external tenants.

Also, which of these three are covered by Go-Local and which are not? If there is a document that lists what Go-Local covers, a link would be appreciated.

For each answer, please include a link to the Microsoft documentation that supports it, if one exists.

Thank you.

Microsoft Security | Microsoft Entra | Microsoft Entra External ID
0 comments No comments

Answer accepted by question author

AI answer

2026-11-16T12:53:37.7066667+00:00

A Japan Go-Local external tenant keeps covered External ID Core Store and component data in Japan, but Microsoft explicitly identifies MFA as a centralized exception; the public documentation does not explicitly classify every sign-in/audit-log or External ID SSPR artifact.

Summary

Data Documented storage at rest Covered by Japan Go-Local?
Email OTP used as MFA MFA customer data can be stored in the United States; processing is global Not fully—MFA is a documented exception
Sign-in and audit logs Relevant authentication/IAM component log data is documented as “in geo location,” but Microsoft does not explicitly map the named External ID sign-in and audit-log datasets to those rows Likely covered at the service-component level, but Japan-only storage of these named datasets is not explicitly documented
SSPR email address, OTP, and reset records The flow and its use of Email OTP are documented, but artifact-level storage locations are not Not explicitly documented; do not represent all SSPR artifacts as Japan-only without written Microsoft confirmation

1. Email OTP as the MFA second factor

External tenants support Email OTP as an MFA second factor when the first factor is email/username plus password.^1^

For Japan, Microsoft states that some Entra features do not support storage of customer data in Japan and specifically identifies Microsoft Entra multifactor authentication: it stores customer data in the US and processes it globally.^2^

Therefore, the defensible answer is:

  • Email OTP used as MFA is not covered by a Japan-only residency statement.
  • MFA-related customer data may be stored in the United States, notwithstanding Go-Local.
  • The general table’s “North America and/or in geo location” wording does not establish Japan-only residency for this configuration.^3^

The detailed MFA residency article lists MFA data stores and retention but does not separately classify Email OTP for an External ID tenant. It also distinguishes Azure AD B2C authentication in parts of its data-store table, so it should not be used to infer a Japan-specific Email OTP commitment absent an explicit statement.^4^

2. Sign-in logs and audit logs

External tenants have sign-in and audit logs with the same functionality as workforce tenants; their built-in activity-log retention is seven days.^5^

The residency table says:

  • The authentication service generates log data in Azure Storage in the datacenter where its service instance runs; its location is “in geo location.”
  • IAM services generate log and usage data in Azure Tables, Azure SQL, and reporting services; their location is also “in geo location.”^3^

However, the documentation does not explicitly say that the administrator-visible datasets named Sign-in logs and Audit logs map exactly to those two component rows. Consequently:

  • The component documentation supports in-geo handling of authentication and IAM service logs.
  • It does not provide a sufficiently explicit statement to promise healthcare customers that every field and copy of the named sign-in/audit-log datasets is stored only in Japan.
  • The “authentication Service” row should not be treated as an explicit, comprehensive sign-in/audit-log residency commitment.

If logs are exported, the export destination has its own residency. External-tenant log export through Azure Monitor is currently identified as preview.^5^ Select a Japan-hosted destination and assess that destination separately; exporting does not establish where the original Entra-managed copy resides.

3. Self-service password reset

For external tenants, SSPR supports Email OTP: the user enters an email address, receives a passcode, verifies it, and then creates a new password.^6^

The available documents do not state where these individual External ID SSPR artifacts are stored:

  • email address used for verification;
  • generated one-time passcode;
  • OTP validation state;
  • password-reset transaction or audit record.

The password-writeback row in the general residency table concerns Microsoft Entra Connect and on-premises password writeback. It does not establish residency for cloud-only External ID SSPR.^3^

A user’s persisted directory attributes and password data belong to the tenant’s Core Store, which Go-Local places in the selected Japan geo. But the documentation does not establish that transient OTP data and reset records are Core Store data. Because Email OTP is also used by the authentication/MFA services, those artifacts should not be declared Japan-only without confirmation.

Also assess the user’s email provider separately: delivery places a copy of the OTP message in the recipient’s mailbox, whose residency is controlled by that mail provider rather than by External ID Go-Local.

Go-Local allows an external tenant to store its Core Store data and covered Entra component/service data in Japan; it is not an all-features guarantee.^7^ Microsoft describes the add-on as storing external identity data in a selected region and currently offers it in Japan and Australia.^8^

For contractual or healthcare compliance documentation, use these classifications:

  1. MFA Email OTP: US storage/global processing may occur.
  2. Sign-in/audit logs: in-geo component behavior is documented, but Japan-only residency of the named datasets is not explicit.
  3. SSPR: Core Store data is covered; OTP and reset-record residency is undocumented.

Request written confirmation through Microsoft support or your Microsoft account representative for the unresolved log and SSPR artifacts, including their replicas, backups, diagnostic copies, and transient stores. A support statement or contractual data-residency term is needed before asserting “Japan only.”


References

  1. MFA in external tenants - Microsoft Entra External ID
  2. Customer data storage for Japan customers - Microsoft Entra
  3. Microsoft Entra ID and data residency
  4. Data residency and customer data for Microsoft Entra multifactor authentication
  5. Supported features in workforce and external tenants
  6. Enable self-service password reset
  7. Create an external tenant
  8. Microsoft Entra External ID pricing and billing overview
AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.