Skip to content

Commit 7655459

Browse files
authored
Merge pull request #221448 from MicrosoftDocs/main
Publish to Live, Wednesday 4AM PST, 12/14
2 parents c5c0008 + e02cb0d commit 7655459

File tree

107 files changed

+3246
-784
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

107 files changed

+3246
-784
lines changed

articles/active-directory-b2c/data-residency.md

Lines changed: 23 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -9,55 +9,67 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 08/16/2021
12+
ms.date: 12/12/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
ms.custom: references_regions
1616
---
1717

1818
# Azure Active Directory B2C: Region availability & data residency
1919

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.
2121

2222
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.
2323

2424
Azure AD B2C is **generally available worldwide** with the option for **data residency** in the **United States, Europe, Asia Pacific, or Australia**.
2525

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).
2927

3028
## Region availability
3129

3230
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).
3331
## Data residency
3432

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.
3634

3735
Data residency is determined by the country/region you select when you [create an Azure AD B2C tenant](tutorial-create-tenant.md):
3836

3937
![Screenshot of a Create Tenant form, choosing country or region.](./media/data-residency/data-residency-b2c-tenant.png)
4038

41-
Data resides in the **United States** for the following countries/regions:
39+
Data resides in the **United States** for the following locations:
4240

4341
> 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)
4442
45-
Data resides in **Europe** for the following countries/regions:
43+
Data resides in **Europe** for the following locations:
4644

4745
> 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)
4846
49-
Data resides in **Asia Pacific** for the following countries/regions:
47+
Data resides in **Asia Pacific** for the following locations:
5048

5149
> 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)
5250
53-
Data resides in **Australia** for the following countries/regions:
51+
Data resides in **Australia** for the following locations:
5452

5553
> Australia (AU) and New Zealand (NZ)
5654
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.
5856

5957
> Argentina, Brazil, Chile, Colombia, Ecuador, Iraq, Paraguay, Peru, Uruguay, and Venezuela
6058
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+
6173
## Remote profile solution
6274

6375
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).

articles/active-directory-b2c/index.yml

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ metadata:
1616
ms.collection: collection
1717
author: kengaderdus
1818
ms.author: kengaderdus
19-
ms.date: 08/31/2022
19+
ms.date: 12/14/2022
2020

2121
## FRONT MATTER END
2222

@@ -125,15 +125,11 @@ conceptualContent:
125125
- text: Protocols
126126
url: ../active-directory/develop/v2-app-types.md?bc=%2fazure%2factive-directory-b2c%2fbread%2ftoc.json&toc=%2fazure%2factive-directory-b2c%2fTOC.json
127127
itemType: concept
128-
# - text: Authentication library
129-
# url: ../active-directory/develop/msal-overview.md?bc=%2fazure%2factive-directory-b2c%2fbread%2ftoc.json&toc=%2fazure%2factive-directory-b2c%2fTOC.json
130-
# itemType: concept
131-
# - text: Identity providers
132-
# url: add-identity-provider.md
133-
# itemType: concept
134-
- text: Authenticate users in a Node.js web app(Quick course)
135-
url: /learn/modules/authenticate-users-node-web-app-use-azure-active-directory-b2c/
136-
itemType: learn
128+
- text: Authentication library
129+
url: ../active-directory/develop/msal-overview.md?bc=%2fazure%2factive-directory-b2c%2fbread%2ftoc.json&toc=%2fazure%2factive-directory-b2c%2fTOC.json
130+
itemType: concept
131+
132+
137133
## CARD 3 ######################
138134
- title: 'Authenticate: Sign in users'
139135
links:
@@ -155,6 +151,10 @@ conceptualContent:
155151
- text: Enable single sign-on (SSO)
156152
url: session-behavior.md
157153
itemType: how-to-guide
154+
155+
- text: Authenticate users in a Node.js web app(Quick course)
156+
url: /learn/modules/authenticate-users-node-web-app-use-azure-active-directory-b2c/
157+
itemType: learn
158158
# - text: 'Quickstart: Single-page app'
159159
# url: configure-authentication-sample-spa-app.md
160160
# itemType: quickstart

articles/active-directory/develop/workload-identity-federation-create-trust.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: how-to
1111
ms.workload: identity
12-
ms.date: 10/31/2022
12+
ms.date: 12/13/2022
1313
ms.author: ryanwi
1414
ms.custom: aaddev
1515
ms.reviewer: shkhalid, udayh, vakarand
@@ -27,6 +27,8 @@ In this article, you learn how to create, list, and delete federated identity cr
2727

2828
## Important considerations and restrictions
2929

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.
31+
3032
[!INCLUDE [federated credential configuration](./includes/federated-credential-configuration-considerations.md)]
3133

3234
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).

articles/active-directory/fundamentals/active-directory-access-create-new-tenant.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
2626
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.
2727

2828
>[!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.
3030
3131
### To create a new tenant
3232

0 commit comments

Comments
 (0)