What are all the possible values for the tenant_region_scope optional claim?

Question

What are all the possible values for the tenant_region_scope optional claim?

DS 0

I'm building a multi-tenant app and using the tenant_region_scope optional claim in my Entra ID app registration to route users to region-specific infrastructure.

The optional claims reference documentation describes this claim only as "Region of the resource tenant" — it doesn't list what values can actually be returned.

I've tested this and found it that it returns EU, but i am not sure what other values does it return.

Is there a complete list of possible values for tenant_region_scope?

The docs gap here makes it difficult to write reliable routing logic against this claim.

Thanks.

VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-05-20T09:55:43.6366667+00:00

Hello DS,

The tenant_region_scope optional claim currently does not have a documented or supported list of possible values in Microsoft Entra ID.

As per the official documentation, this claim is only defined as**“Region of the resource tenant”**, and no enumeration of valid values (such as EU, NA, APAC, etc.) is provided or guaranteed.

https://learn.microsoft.com/en-us/entra/identity-platform/optional-claims-reference

Based on this, values like EU that you are observing are implementation-dependent and not part of a publicly defined contract. Microsoft does not publish or guarantee a fixed set of values for this claim, and they may vary or change over time.

Recommendation: You should avoid building strict routing logic that depends on specific tenant_region_scope values. Instead, treat the claim as indicative only, or use more deterministic approaches (such as tenant metadata or configuration maintained within your application) if you require reliable region-based routing.
VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-05-22T08:38:03.8633333+00:00

DS I’m following up on my previous comment as I haven’t received a response. Please let me know if you need any additional information or assistance from my side.
DS 0 Reputation points

2026-05-22T09:14:20.3433333+00:00

Hi Vemula,

Thank you for the response It helps.

You mentioned using "tenant metadata or configuration maintained within your application" as a more deterministic approach for region routing. Could you expand on what you mean by tenant metadata in this context?

Our setup is a multi-tenant Teams channel tab app (configurable tab). When a tenant admin installs the app, they go through the tab configuration page before the tab is pinned to a channel. We're considering using that configuration step to capture the tenant's region, either by asking the admin to select their region explicitly, or by detecting it automatically.

Is the configuration step in a Teams configurable tab the right place to capture and persist this, or is there a better point in the app lifecycle to do so

Our goal is to route the tenant to one of our regional backends (EU, UK, US, AU) once, store that mapping, and not rely on per-request token claims for routing thereafter. Thank you.

1 answer

Your answer

VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-05-20T09:55:43.6366667+00:00

Hello DS,

The tenant_region_scope optional claim currently does not have a documented or supported list of possible values in Microsoft Entra ID.

As per the official documentation, this claim is only defined as**“Region of the resource tenant”**, and no enumeration of valid values (such as EU, NA, APAC, etc.) is provided or guaranteed.

https://learn.microsoft.com/en-us/entra/identity-platform/optional-claims-reference

Based on this, values like EU that you are observing are implementation-dependent and not part of a publicly defined contract. Microsoft does not publish or guarantee a fixed set of values for this claim, and they may vary or change over time.

Recommendation: You should avoid building strict routing logic that depends on specific tenant_region_scope values. Instead, treat the claim as indicative only, or use more deterministic approaches (such as tenant metadata or configuration maintained within your application) if you require reliable region-based routing.
VEMULA SRISAI 13,900 Reputation points Microsoft External Staff Moderator

2026-05-22T08:38:03.8633333+00:00

DS I’m following up on my previous comment as I haven’t received a response. Please let me know if you need any additional information or assistance from my side.
DS 0 Reputation points

2026-05-22T09:14:20.3433333+00:00

Hi Vemula,

Thank you for the response It helps.

You mentioned using "tenant metadata or configuration maintained within your application" as a more deterministic approach for region routing. Could you expand on what you mean by tenant metadata in this context?

Our setup is a multi-tenant Teams channel tab app (configurable tab). When a tenant admin installs the app, they go through the tab configuration page before the tab is pinned to a channel. We're considering using that configuration step to capture the tenant's region, either by asking the admin to select their region explicitly, or by detecting it automatically.

Is the configuration step in a Teams configurable tab the right place to capture and persist this, or is there a better point in the app lifecycle to do so

Our goal is to route the tenant to one of our regional backends (EU, UK, US, AU) once, store that mapping, and not rely on per-request token claims for routing thereafter. Thank you.

Answer 1

The available context documents describe tenant_region_scope only as:

“Region of the resource tenant”

and list it as an optional claim and as a claim that can be used in claim sets, but they do not provide any enumeration or catalog of possible values for this claim.

No complete or partial list of valid tenant_region_scope values (such as EU, NA, etc.) is present in the provided documentation, nor any guidance on the exact value set or format beyond that description.

Because of this, a definitive list of all possible tenant_region_scope values cannot be given based on the available material.

References: