Skip to content

Commit 7ff7921

Browse files
committed
resolved conflicts
2 parents 0508741 + b5de55a commit 7ff7921

File tree

6,976 files changed

+119557
-100185
lines changed

Some content is hidden

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

6,976 files changed

+119557
-100185
lines changed

.openpublishing.redirection.json

Lines changed: 261 additions & 11 deletions
Large diffs are not rendered by default.

ThirdPartyNotices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ see the [LICENSE](LICENSE) file, and grant you a license to any code in the repo
77
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
88
may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
99
The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
10-
Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
10+
You can find Microsoft general trademark guidelines at [Microsoft Trademark and Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks).
1111

12-
Privacy information can be found at https://privacy.microsoft.com/en-us/
12+
For privacy information, see [privacy at Microsoft](https://privacy.microsoft.com/en-us/).
1313

1414
Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents,
1515
or trademarks, whether by implication, estoppel, or otherwise.

articles/active-directory-b2c/add-api-connector.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -629,7 +629,7 @@ Ensure that:
629629
* Your API explicitly checks for null values of received claims that it depends on.
630630
* Your API implements an authentication method outlined in [secure your API Connector](secure-rest-api.md).
631631
* Your API responds as quickly as possible to ensure a fluid user experience.
632-
* Azure AD B2C will wait for a maximum of *20 seconds* to receive a response. If none is received, it will make *one more attempt (retry)* at calling your API.
632+
* Azure AD B2C will wait for a maximum of *10 seconds* to receive a response. If none is received, it will make *one more attempt (retry)* at calling your API.
633633
* If using a serverless function or scalable web service, use a hosting plan that keeps the API "awake" or "warm" in production. For Azure Functions, it's recommended to use at minimum the [Premium plan](../azure-functions/functions-scale.md) in production.
634634
* Ensure high availability of your API.
635635
* Monitor and optimize performance of downstream APIs, databases, or other dependencies of your API.

articles/active-directory-b2c/api-connectors-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ Using Azure AD B2C, you can add your own business logic to a user journey by cal
8585
![Diagram of a RESTful service claims exchange](media/api-connectors-overview/restful-service-claims-exchange.png)
8686

8787
> [!NOTE]
88-
> If there is slow or no response from the RESTful service to Azure AD B2C, the timeout is 30 seconds and the retry count is two times (meaning there are 3 tries in total). Currently, you can't configure the timeout and retry count settings.
88+
> HTTP requests may be cancelled if there is a slow or no response from the RESTful service to Azure AD B2C. The default timeout is 10 seconds and the default retry count is one (meaning there are 2 tries in total).
8989
9090
## Calling a RESTful service
9191

@@ -165,7 +165,7 @@ A null value in a database is used when the value in a column is unknown or miss
165165
When an element is null, either:
166166

167167
- Omit the key-value pair from the JSON.
168-
- Return a value that corresponds to the Azure AD B2C claim data type. For example, for a `string` data type, return empty string `""`. For an `integer` data type, return a zero value `0`. For a `dateTime` data type, return a minimum value `1970-00-00T00:00:00.0000000Z`.
168+
- Return a value that corresponds to the Azure AD B2C claim data type. For example, for a `string` data type, return empty string `""`. For an `integer` data type, return a zero value `0`. For a `dateTime` data type, return a minimum value `0001-01-01T00:00:00.0000000Z`.
169169

170170
The following example demonstrates how to handle a null value. The email is omitted from the JSON:
171171

articles/active-directory-b2c/claimsschema.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
22
title: "ClaimsSchema: Azure Active Directory B2C"
3-
description: Specify the ClaimsSchema element of a custom policy in Azure Active Directory B2C.
3+
description: Specify the ClaimsSchema element of a custom policy in Azure AD B2C. Define and manage claim types for user attributes and input controls.
44

55
author: kengaderdus
66
manager: CelesteDG
77

88
ms.service: azure-active-directory
99

1010
ms.topic: reference
11-
ms.date: 01/11/2024
11+
ms.date: 03/21/2025
1212
ms.author: kengaderdus
1313
ms.subservice: b2c
1414
ms.custom: "b2c-support"

articles/active-directory-b2c/custom-policies-series-branch-user-journey.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create branching in user journey by using Azure AD B2C custom policy
33
titleSuffix: Azure AD B2C
4-
description: Learn how to enable or disable Technical Profiles based on claims values. Learn how to branch in user journeys by enabling and disabling Azure AD B2C custom policy technical profiles.
4+
description: Learn how to create branching in user journeys using Azure AD B2C custom policies. Enable or disable technical profiles based on claim values.
55

66
author: kengaderdus
77
manager: CelesteDG
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 10/11/2024
13+
ms.date: 03/21/2025
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: b2c
@@ -233,12 +233,12 @@ Follow the steps in [Test the custom policy](custom-policies-series-validate-use
233233
1. Repeat step 5, but this time, select **Account Type**, select **Contoso Employee Account**, and then follow the prompts.
234234

235235

236-
## Next steps
236+
## Related content
237237

238238
In [step 3](#step-3---configure-or-update-technical-profiles), we enable or disable the technical profile by using the `EnabledForUserJourneys` element. Alternatively, you can use [Preconditions](userjourneys.md#preconditions) inside the user journey orchestration steps to execute or skip an orchestration step as we learn later in this series.
239239

240240
Next, learn:
241241

242242
- About [User Journey Orchestration Steps Preconditions](userjourneys.md#preconditions).
243243

244-
- How to [Use the TrustFrameworkPolicy schema file to validate Azure AD B2C policy files](custom-policies-series-install-xml-extensions.md).
244+
- How to [Use the TrustFrameworkPolicy schema file to validate Azure AD B2C policy files](custom-policies-series-install-xml-extensions.md).

articles/active-directory-b2c/custom-policies-series-call-rest-api.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Call a REST API by using Azure Active Directory B2C custom policy
2+
title: Call a REST API by using Azure AD B2C custom policy
33
titleSuffix: Azure AD B2C
4-
description: Learn how to make an HTTP call to external API by using Azure Active Directory B2C custom policy.
4+
description: Learn how to call a REST API using Azure AD B2C custom policy. Make HTTP calls to external APIs to send and receive data from external services.
55

66
author: kengaderdus
77
manager: CelesteDG
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements, devx-track-js
13-
ms.date: 10/11/2024
13+
ms.date: 03/21/2025
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: b2c
@@ -93,7 +93,7 @@ You need to deploy an app, which serves as your external app. Your custom policy
9393
"requestId": "requestId",
9494
"userMessage" : "The access code you entered is incorrect. Please try again.",
9595
"developerMessage" : `The provided code ${req.body.accessCode} does not match the expected code for user.`,
96-
"moreInfo" :"https://docs.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
96+
"moreInfo" :"https://learn.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
9797
};
9898
res.status(409).send(errorResponse);
9999
}
@@ -138,7 +138,7 @@ You need to deploy an app, which serves as your external app. Your custom policy
138138
"requestId": "requestId",
139139
"userMessage": "The access code you entered is incorrect. Please try again.",
140140
"developerMessage": "The provided code 54321 does not match the expected code for user.",
141-
"moreInfo": "https://docs.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
141+
"moreInfo": "https://learn.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
142142
}
143143
```
144144
Your REST service can return HTTP 4xx status code, but the value of `status` in the JSON response must be `409`.
@@ -313,7 +313,7 @@ If your REST API returns data, which you want to include as claims in your polic
313313
314314
Use the steps in [Receiving data](api-connectors-overview.md?pivots=b2c-custom-policy#receiving-data) to learn how to format the data the custom policy expects, how to handle nulls values, and how to parse REST the API's nested JSON body.
315315

316-
## Next steps
316+
## Related content
317317

318318
Next, learn:
319319

articles/active-directory-b2c/custom-policies-series-collect-user-input.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 10/11/2024
13+
ms.date: 03/21/2025
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: b2c
@@ -504,10 +504,10 @@ After the policy finishes execution, you're redirected to `https://jwt.ms`, and
504504
}.[Signature]
505505
```
506506

507-
## Next steps
507+
## Related content
508508

509509
Next, learn:
510510

511511
- About the [types of Technical Profiles](technicalprofiles.md#types-of-technical-profiles) in Azure AD B2C's custom policies.
512512

513-
- How to [Validate user inputs by using custom policy](custom-policies-series-validate-user-input.md).
513+
- How to [Validate user inputs by using custom policy](custom-policies-series-validate-user-input.md).

articles/active-directory-b2c/custom-policies-series-hello-world.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Write your first Azure AD B2C custom policy - Hello World!
33
titleSuffix: Azure AD B2C
4-
description: Learn how to write your first custom policy. A custom that shows of returns Hello World message.
4+
description: Learn how to write your first Azure AD B2C custom policy. Configure keys, build the policy file, upload it to Azure, and test the custom policy.
55

66
author: kengaderdus
77
manager: CelesteDG
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 10/11/2024
13+
ms.date: 03/21/2025
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: b2c
@@ -286,7 +286,7 @@ After the policy finishes execution, you're redirected to `https://jwt.ms`, and
286286

287287
Notice the `message` and `sub` claims, which we set as [output claims](relyingparty.md#outputclaims) in the `RelyingParty` section.
288288

289-
## Next steps
289+
## Related content
290290

291291
In this article, you learned and used four sections that are included in an Azure AD B2C custom policy. These sections are added as child elements the `TrustFrameworkPolicy` root element:
292292

articles/active-directory-b2c/custom-policies-series-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Create and run your own custom policies in Azure Active Directory B2C
2+
title: Create and run your own custom policies in Azure AD B2C
33
titleSuffix: Azure AD B2C
4-
description: Learn how to create and run your own custom policies in Azure Active Directory B2C. Learn how to create Azure Active Directory B2C custom policies from scratch in a how-to guide series.
4+
description: Learn how to create and run custom policies in Azure AD B2C. Follow a how-to guide series to build custom policies from scratch for complex user journeys.
55

66
author: kengaderdus
77
manager: CelesteDG
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 10/11/2024
13+
ms.date: 03/21/2025
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: b2c
@@ -48,7 +48,7 @@ This how-to guide series consists of multiple articles. We recommend that you st
4848
|[Set up a sign-up and sign-in flow by using Azure Active Directory B2C custom policy](custom-policies-series-sign-up-or-sign-in.md). | Learn how to configure a sign-up and sign-in flow for a local account(using email and password) by using Azure Active Directory B2C custom policy. You show a user a sign-in interface for them to sign in by using their existing account, but they can create a new account if they don't already have one.|
4949
| [Set up a sign-up and sign-in flow with a social account by using Azure Active Directory B2C custom policy](custom-policies-series-sign-up-or-sign-in-federation.md) | Learn how to configure a sign-up and sign-in flow for a social account, Facebook. You also learn to combine local and social sign-up and sign-in flow.|
5050

51-
## Next steps
51+
## Related content
5252

5353
- Learn about [Azure AD B2C TrustFrameworkPolicy BuildingBlocks](buildingblocks.md)
5454

0 commit comments

Comments
 (0)