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/data-residency.md
+23-11Lines changed: 23 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,55 +9,67 @@ manager: CelesteDG
9
9
ms.service: active-directory
10
10
ms.workload: identity
11
11
ms.topic: reference
12
-
ms.date: 08/16/2021
12
+
ms.date: 12/12/2022
13
13
ms.author: kengaderdus
14
14
ms.subservice: B2C
15
15
ms.custom: references_regions
16
16
---
17
17
18
18
# Azure Active Directory B2C: Region availability & data residency
19
19
20
-
Azure AD B2C identity data is stored in a geographical location based on the country/region provided when you create the tenant.
20
+
Azure Active Directory B2C (Azure AD B2C) stores customer data in a geographic location based on how a tenant was created and provisioned. For the Azure portal or Azure AD API, the location is defined when a customer selects a location from the pre-defined list.
21
21
22
22
Region availability and data residency are two different concepts that apply to Azure AD B2C. This article explains the differences between these two concepts, and compares how they apply to Azure versus Azure AD B2C.
23
23
24
24
Azure AD B2C is **generally available worldwide** with the option for **data residency** in the **United States, Europe, Asia Pacific, or Australia**.
25
25
26
-
[Region availability](#region-availability) refers to where a service is available for use.
27
-
28
-
[Data residency](#data-residency) refers to where user data is stored.
26
+
[Region availability](#region-availability) refers to where a service is available for use. [Data residency](#data-residency) refers to where customer data is stored. For customers in the EU and EFTA, see [EU Data Boundary](#eu-data-boundary).
29
27
30
28
## Region availability
31
29
32
30
Azure AD B2C is available worldwide via the Azure public cloud. You can see availability of this service 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/). Also, Azure AD B2C service is highly available. Learn more about [Service Level Agreement (SLA) for Azure Active Directory B2C](https://azure.microsoft.com/support/legal/sla/active-directory-b2c/v1_1).
33
31
## Data residency
34
32
35
-
Azure AD B2C stores user data in the United States, Europe, the Asia Pacific region, or Australia.
33
+
Azure AD B2C stores customer data in the United States, Europe, the Asia Pacific region, or Australia.
36
34
37
35
Data residency is determined by the country/region you select when you [create an Azure AD B2C tenant](tutorial-create-tenant.md):
38
36
39
37

40
38
41
-
Data resides in the **United States** for the following countries/regions:
39
+
Data resides in the **United States** for the following locations:
42
40
43
41
> United States (US), Canada (CA), Costa Rica (CR), Dominican Republic (DO), El Salvador (SV), Guatemala (GT), Mexico (MX), Panama (PA), Puerto Rico (PR) and Trinidad & Tobago (TT)
44
42
45
-
Data resides in **Europe** for the following countries/regions:
43
+
Data resides in **Europe** for the following locations:
46
44
47
45
> Algeria (DZ), Austria (AT), Azerbaijan (AZ), Bahrain (BH), Belarus (BY), Belgium (BE), Bulgaria (BG), Croatia (HR), Cyprus (CY), Czech Republic (CZ), Denmark (DK), Egypt (EG), Estonia (EE), Finland (FT), France (FR), Germany (DE), Greece (GR), Hungary (HU), Iceland (IS), Ireland (IE), Israel (IL), Italy (IT), Jordan (JO), Kazakhstan (KZ), Kenya (KE), Kuwait (KW), Latvia (LV), Lebanon (LB), Liechtenstein (LI), Lithuania (LT), Luxembourg (LU), North Macedonia (ML), Malta (MT), Montenegro (ME), Morocco (MA), Netherlands (NL), Nigeria (NG), Norway (NO), Oman (OM), Pakistan (PK), Poland (PL), Portugal (PT), Qatar (QA), Romania (RO), Russia (RU), Saudi Arabia (SA), Serbia (RS), Slovakia (SK), Slovenia (ST), South Africa (ZA), Spain (ES), Sweden (SE), Switzerland (CH), Tunisia (TN), Turkey (TR), Ukraine (UA), United Arab Emirates (AE) and United Kingdom (GB)
48
46
49
-
Data resides in **Asia Pacific** for the following countries/regions:
47
+
Data resides in **Asia Pacific** for the following locations:
50
48
51
49
> Afghanistan (AF), Hong Kong SAR (HK), India (IN), Indonesia (ID), Japan (JP), Korea (KR), Malaysia (MY), Philippines (PH), Singapore (SG), Sri Lanka (LK), Taiwan (TW), and Thailand (TH)
52
50
53
-
Data resides in **Australia** for the following countries/regions:
51
+
Data resides in **Australia** for the following locations:
54
52
55
53
> Australia (AU) and New Zealand (NZ)
56
54
57
-
The following countries/regions are in the process of being added to the list. For now, you can still use Azure AD B2C by picking any of the countries/regions above.
55
+
The following locations are in the process of being added to the list. For now, you can still use Azure AD B2C by picking any of the locations previously listed.
58
56
59
57
> Argentina, Brazil, Chile, Colombia, Ecuador, Iraq, Paraguay, Peru, Uruguay, and Venezuela
60
58
59
+
## EU Data Boundary
60
+
61
+
The EU Data Boundary is Microsoft's commitment for our public sector and commercial customers in the EU and EFTA to process and store their customer data in the EU.
62
+
63
+
### Services temporarily excluded from the EU Data Boundary
64
+
65
+
Some services have work in progress to be EU Data Boundary compliant, but this work is delayed beyond January 1, 2023. The services listed will become compliant over the coming months. The following details explain the customer data that these features currently transfer out of the EU Data Boundary as part of their service operations:
66
+
67
+
***Reason for customer data egress** - These features haven't completed changes to fully process admin actions and user sign-in actions within the EU Data Boundary.
68
+
***Types of customer data being egressed** - User account and usage data, and service configuration such as policy.
69
+
***Customer data location at rest** - In the EU Data Boundary.
70
+
***Customer data processing** - Some processing may occur globally.
71
+
***Services** - Administrator actions in the Azure portal or APIs, and User Sign-In Service
72
+
61
73
## Remote profile solution
62
74
63
75
With Azure AD B2C [custom policies](custom-policy-overview.md), you can integrate with [RESTful API services](api-connectors-overview.md), which allow you to store and read user profiles from a remote database (such as a marketing database, CRM system, or any line-of-business application).
Copy file name to clipboardExpand all lines: articles/active-directory/develop/workload-identity-federation-create-trust.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
9
9
ms.subservice: develop
10
10
ms.topic: how-to
11
11
ms.workload: identity
12
-
ms.date: 10/31/2022
12
+
ms.date: 12/13/2022
13
13
ms.author: ryanwi
14
14
ms.custom: aaddev
15
15
ms.reviewer: shkhalid, udayh, vakarand
@@ -27,6 +27,8 @@ In this article, you learn how to create, list, and delete federated identity cr
27
27
28
28
## Important considerations and restrictions
29
29
30
+
To create, update, or delete a federated identity credential, the account performing the action must have the [Application Administrator](/azure/active-directory/roles/permissions-reference#application-administrator), [Application Developer](/azure/active-directory/roles/permissions-reference#application-developer), [Cloud Application Administrator](/azure/active-directory/roles/permissions-reference#cloud-application-administrator), or Application Owner role. The [microsoft.directory/applications/credentials/update permission](/azure/active-directory/roles/custom-available-permissions#microsoftdirectoryapplicationscredentialsupdate) is required to update a federated identity credential.
To learn more about supported regions, time to propagate federated credential updates, supported issuers and more, read [Important considerations and restrictions for federated identity credentials](workload-identity-federation-considerations.md).
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/active-directory-access-create-new-tenant.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
26
26
After you sign in to the Azure portal, you can create a new tenant for your organization. Your new tenant represents your organization and helps you to manage a specific instance of Microsoft cloud services for your internal and external users.
27
27
28
28
>[!Note]
29
-
>If you're unable to create Azure AD B2C tenant, review your user settings page to ensure that tenant creation isn't switched off. If tenant creation is switched off, ask your _Global Administrator_ to assign you a _Tenant Creator_ role.
29
+
>If you're unable to create Azure AD or Azure AD B2C tenant, review your user settings page to ensure that tenant creation isn't switched off. If tenant creation is switched off, ask your _Global Administrator_ to assign you a _Tenant Creator_ role.
0 commit comments