You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/active-directory-b2c-reference-tenant-type.md
+13-14Lines changed: 13 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,29 +15,25 @@ ms.subservice: B2C
15
15
16
16
# Azure Active Directory B2C: Region availability & data residency
17
17
18
-
Region availability and data residency are two very different concepts that apply differently to Azure AD B2C from the rest of Azure. This article will explain the differences between these two concepts and compare how they apply to Azure versus Azure AD B2C.
18
+
Region availability and data residency are two very different concepts that apply differently to Azure AD B2C from the rest of Azure. This article explains the differences between these two concepts, and compares how they apply to Azure versus Azure AD B2C.
19
19
20
-
## Summary
20
+
Azure AD B2C is **generally available worldwide** with the option for **data residency** in the **United States, Europe, or Asia Pacific**.
21
21
22
-
Azure AD B2C is **generally available worldwide** with the option for **data residency in United States or Europe**.
22
+
[Region availability](#region-availability) refers to where a service is available for use.
23
23
24
-
## Concepts
25
-
26
-
**Region availability** refers to where a service is available for use.
27
-
28
-
**Data residency** refers to where user data is stored.
24
+
[Data residency](#data-residency) refers to where user data is stored.
29
25
30
26
## Region availability
31
27
32
28
Azure AD B2C is available worldwide via the Azure public cloud.
33
29
34
-
This differs from the model most other Azure services follow which couple availability with data residency. You can see examples of this in both Azure's [Products Available By Region](https://azure.microsoft.com/regions/services/) page and the [Active Directory B2C pricing calculator](https://azure.microsoft.com/pricing/details/active-directory-b2c/).
30
+
This differs from the model followed by most other Azure services, which typically couple *availability* with data *residency*. You can see examples of this in both Azure's [Products Available By Region](https://azure.microsoft.com/regions/services/) page and the [Active Directory B2C pricing calculator](https://azure.microsoft.com/pricing/details/active-directory-b2c/).
35
31
36
32
## Data residency
37
33
38
34
Azure AD B2C stores user data in either United States, Europe, or the Asia Pacific region.
39
35
40
-
Data residency is determined based on which country/region is selected when [creating an Azure AD B2C tenant](active-directory-b2c-get-started.md).
36
+
Data residency is determined by the country/region you select when you [create an Azure AD B2C tenant](active-directory-b2c-get-started.md):
41
37
42
38

43
39
@@ -59,9 +55,12 @@ The following countries/regions are in the process of being added to the list.
59
55
60
56
## Preview tenant
61
57
62
-
If you had created a B2C tenant during Azure AD B2C's preview period, it is likely that your **Tenant type** says **Preview tenant**. If this is the case, you MUST use your tenant only for development and testing purposes, and NOT for production apps.
58
+
If you had created a B2C tenant during Azure AD B2C's preview period, it's likely that your **Tenant type** says **Preview tenant**.
59
+
60
+
If this is the case, you must use your tenant ONLY for development and testing purposes. Do NOT use a preview tenant for production applications.
61
+
62
+
**There is no migration path** from a preview B2C tenant to a production-scale B2C tenant. You must create a new B2C tenant for your production applications.
63
63
64
-
> [!IMPORTANT]
65
-
> There is no migration path from a preview B2C tenant to a production-scale B2C tenant. Note that there are known issues when you delete a preview B2C tenant and re-create a production-scale B2C tenant with the same domain name. You have to create a production-scale B2C tenant with a different domain name.
64
+
There are known issues when you delete a preview B2C tenant and create a production-scale B2C tenant with the same domain name. *You must create a production-scale B2C tenant with a different domain name*.
66
65
67
-

66
+

0 commit comments