Skip to content

Commit bcf1871

Browse files
authored
Merge pull request #134388 from yoelhor/patch-49
Update data-residency.md
2 parents f3e7677 + c7bddab commit bcf1871

File tree

1 file changed

+14
-2
lines changed

1 file changed

+14
-2
lines changed

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

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: celestedg
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 06/06/2020
12+
ms.date: 10/20/2020
1313
ms.author: mimart
1414
ms.subservice: B2C
1515
ms.custom: references_regions
@@ -55,6 +55,14 @@ The following countries/regions are in the process of being added to the list. F
5555

5656
> Argentina, Australia, Brazil, Chile, Colombia, Ecuador, Iraq, New Zealand, Paraguay, Peru, Uruguay, and Venezuela.
5757
58+
## Remote profile solution
59+
60+
With Azure AD B2C [custom policies](custom-policy-overview.md), you can integrate with [RESTful API services](custom-policy-rest-api-intro.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).
61+
- During the sign-up and profile editing flows, Azure AD B2C calls a custom REST API to persist the user profile to the remote data source. The user's credentials are stored in Azure AD B2C directory.
62+
- Upon sign-in, after credentials validation with a local or social account, Azure AD B2C invokes the REST API, which sends the user's unique identifier as a user primary key (email address or user objectId). The REST API reads the data from the remote database and returns the user profile.
63+
64+
After sign-up, profile editing, or sign-in is complete, Azure AD B2C includes the user profile in the access token that is returned to the application. For more information, see the [Azure AD B2C Remote profile sample solution](https://github.com/azure-ad-b2c/samples/tree/master/policies/remote-profile) in GitHub.
65+
5866
## Preview tenant
5967

6068
If you had created a B2C tenant during Azure AD B2C's preview period, it's likely that your **Tenant type** says **Preview tenant**.
@@ -65,4 +73,8 @@ If this is the case, you must use your tenant ONLY for development and testing p
6573

6674
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*.
6775

68-
![Screenshot of a tenant type, as preview tenant.](./media/data-residency/preview-b2c-tenant.png)
76+
![Screenshot of a tenant type, as preview tenant.](./media/data-residency/preview-b2c-tenant.png)
77+
78+
## Next steps
79+
80+
- [Create an Azure AD B2C tenant](tutorial-create-tenant.md).

0 commit comments

Comments
 (0)