Skip to content

Commit a88e184

Browse files
author
gitName
committed
merge conflict
2 parents abbf403 + 6ce67ee commit a88e184

File tree

7,754 files changed

+123697
-130902
lines changed

Some content is hidden

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

7,754 files changed

+123697
-130902
lines changed

.github/policies/disallow-edits.yml

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -153,15 +153,19 @@ configuration:
153153

154154
- description: Disallow sign-off for articles in the /articles/reliability folder.
155155
if:
156-
# If a 'sign-off' comment is added to a PR in the articles/reliability folder , and the PR author isn't Anastasia or John...
157-
- payloadType: Issue_Comment
158-
- isPullRequest
159-
- filesMatchPattern:
160-
matchAny: true
161-
pattern: articles/reliability/*
156+
# If a 'sign-off' comment is added to a PR that's assigned to anaharris-ms, and the PR author isn't Anastasia or John...
157+
- or:
158+
- payloadType: Issue_Comment
159+
- payloadType: Pull_Request_Review_Comment
160+
- isAction:
161+
action: Created
162+
- isActivitySender:
163+
issueAuthor: True
164+
- isAssignedToUser:
165+
user: anaharris-ms
162166
- commentContains:
163-
pattern: \#sign-off
164-
isRegex: false
167+
pattern: '#sign-off'
168+
isRegex: False
165169
- not:
166170
or:
167171
- isActivitySender:

.openpublishing.redirection.json

Lines changed: 799 additions & 30 deletions
Large diffs are not rendered by default.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -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/billing.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: kengaderdus
55
manager: CelesteDG
66
ms.service: azure-active-directory
77
ms.topic: reference
8-
ms.date: 09/11/2024
8+
ms.date: 03/10/2025
99
ms.author: kengaderdus
1010
ms.subservice: b2c
1111
ms.custom: fasttrack-edit
@@ -29,7 +29,7 @@ A monthly active user (MAU) is a unique user that performs an authentication wit
2929

3030
If Azure AD B2C [Go-Local add-on](data-residency.md#go-local-add-on) is available in your country/region, and you enable it, you'll be charged per MAU, which is an added charge to your Azure AD B2C [Premium P1 or P2 pricing](https://azure.microsoft.com/pricing/details/active-directory-b2c/) license. Learn more [About Local Data Residency add-on](#about-go-local-add-on)
3131

32-
Also, if you choose to provide higher levels of assurance by using multifactor authentication (MFA) for Voice and SMS, you'll be charged a worldwide flat fee for each MFA attempt that month, whether the sign in is successful or unsuccessful.
32+
Also, if you choose to provide higher levels of assurance by using multifactor authentication (MFA) for Voice and SMS, you'll be charged a fee for each MFA attempt that month, whether the sign in is successful or unsuccessful.
3333

3434

3535
> [!IMPORTANT]
@@ -85,7 +85,7 @@ A subscription linked to an Azure AD B2C tenant can be used for the billing of A
8585
### Create the link
8686

8787
1. Sign in to the [Azure portal](https://portal.azure.com).
88-
1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Azure AD B2C tenant from the **Directories + subscriptions** menu.
88+
1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Microsoft Entra tenant from the **Directories + subscriptions** menu.
8989
1. Select **Create a resource**, and then, in the **Search services and Marketplace** field, search for and select **Azure Active Directory B2C**.
9090
1. Select **Create**.
9191
1. Select **Link an existing Azure AD B2C Tenant to my Azure subscription**.

articles/active-directory-b2c/claimsschema.md

Lines changed: 3 additions & 3 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"
@@ -110,7 +110,7 @@ In the following example, when the Identity Experience Framework interacts with
110110
</ClaimType>
111111
```
112112

113-
As a result, the JWT token issued by Azure AD B2C, emits the `family_name` instead of ClaimType name **surname**.
113+
As a result, the JWT issued by Azure AD B2C, emits the `family_name` instead of ClaimType name **surname**.
114114

115115
```json
116116
{

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

Lines changed: 5 additions & 5 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
@@ -229,16 +229,16 @@ Follow the steps in [Test the custom policy](custom-policies-series-validate-use
229229

230230
1. In the first screen, for **Account Type**, select **Personal Account**.
231231
1. For **Access Code**, enter *88888*, and then select **Continue**.
232-
1. Enter the rest of the details as required, and then select **Continue**. After the policy finishes execution, you're redirected to `https://jwt.ms`, and you see a decoded JWT token.
232+
1. Enter the rest of the details as required, and then select **Continue**. After the policy finishes execution, you're redirected to `https://jwt.ms`, and you see a decoded JWT.
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
@@ -35,7 +35,7 @@ In this article, you learn how to:
3535

3636
## Scenario overview
3737

38-
In [Create branching in user journey by using Azure AD B2C custom policies](custom-policies-series-branch-user-journey.md), users who select *Personal Account* need to provide a valid invitation access code to proceed. We use a static access code, but real world apps don't work this way. If the service that issues the access codes is external to your custom policy, you must make a call to that service, and pass the access code input by the user for validation. If the access code is valid, the service returns an HTTP `200 OK` response, and Azure AD B2C issues JWT token. Otherwise, the service returns an HTTP 4xx response, and the user must reenter an access code.
38+
In [Create branching in user journey by using Azure AD B2C custom policies](custom-policies-series-branch-user-journey.md), users who select *Personal Account* need to provide a valid invitation access code to proceed. We use a static access code, but real world apps don't work this way. If the service that issues the access codes is external to your custom policy, you must make a call to that service, and pass the access code input by the user for validation. If the access code is valid, the service returns an HTTP `200 OK` response, and Azure AD B2C issues JWT. Otherwise, the service returns an HTTP 4xx response, and the user must reenter an access code.
3939

4040
:::image type="content" source="media/custom-policies-series-call-rest-api/screenshot-of-call-rest-api-call.png" alt-text="A flowchart of calling a R E S T A P I.":::
4141

@@ -228,7 +228,7 @@ Follow the steps in [Test the custom policy](custom-policies-series-validate-use
228228
229229
1. For **Account Type**, select **Personal Account**
230230
1. Enter the rest of the details as required, and then select **Continue**. You see a new screen.
231-
1. For **Access Code**, enter *88888*, and then select **Continue**. After the policy finishes execution, you're redirected to `https://jwt.ms`, and you see a decoded JWT token. If you repeat the procedure, and enter a different **Access Code**, other than *88888*, you see an error, **The access code you entered is incorrect. Please try again.**
231+
1. For **Access Code**, enter *88888*, and then select **Continue**. After the policy finishes execution, you're redirected to `https://jwt.ms`, and you see a decoded JWT. If you repeat the procedure, and enter a different **Access Code**, other than *88888*, you see an error, **The access code you entered is incorrect. Please try again.**
232232

233233
## Step 5 - Enable debug mode
234234

@@ -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: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,21 +10,21 @@ 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
1717

1818

19-
#Customer intent: As a developer using Azure Active Directory B2C, I want to collect and manipulate user inputs by writing a custom policy, so that I can customize the user interface and process the inputs as claims in a JWT token.
19+
#Customer intent: As a developer using Azure Active Directory B2C, I want to collect and manipulate user inputs by writing a custom policy, so that I can customize the user interface and process the inputs as claims in a JWT.
2020

2121
---
2222

2323
# Collect and manipulate user inputs by using Azure Active Directory B2C custom policy
2424

2525
Azure Active Directory B2C (Azure AD B2C) custom policies allows you to collect user inputs. You can then use inbuilt methods to manipulate the user inputs.
2626

27-
In this article, you learn how to write a custom policy that collects user inputs via a graphical user interface. You'll then access the inputs, process then, and finally return them as claims in a JWT token. To complete this task, you'll:
27+
In this article, you learn how to write a custom policy that collects user inputs via a graphical user interface. You'll then access the inputs, process then, and finally return them as claims in a JWT. To complete this task, you'll:
2828

2929
- Declare claims. A claim provides temporary storage of data during an Azure AD B2C policy execution. It can store information about the user, such as first name, last name, or any other claim obtained from the user or other systems. You can learn more about claims in the [Azure AD B2C custom policy overview](custom-policy-overview.md#claims).
3030

@@ -260,7 +260,7 @@ Replace the existing contents of the `HelloWorldJourney` User Journey with the f
260260
</OrchestrationSteps>
261261
```
262262

263-
According to the orchestration steps, we collect user inputs, set values for *objectId*, *displayName* and *message* claims, and finally send the Jwt token.
263+
According to the orchestration steps, we collect user inputs, set values for *objectId*, *displayName* and *message* claims, and finally send the JWT.
264264

265265
## Step 6 - Update relying party
266266

@@ -486,7 +486,7 @@ Follow the steps in [Upload custom policy file](custom-policies-series-hello-wor
486486

487487
:::image type="content" source="media/custom-policies-series-collect-user-input/screenshot-of-accepting-user-inputs-in-custom-policy.png" alt-text="screenshot of accepting user inputs in custom policy.":::
488488

489-
After the policy finishes execution, you're redirected to `https://jwt.ms`, and you see a decoded JWT token. It looks similar to the following JWT token snippet:
489+
After the policy finishes execution, you're redirected to `https://jwt.ms`, and you see a decoded JWT. It looks similar to the following JWT snippet:
490490

491491
```json
492492
{
@@ -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: 5 additions & 5 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
@@ -141,7 +141,7 @@ If you haven't already done so, create the following encryption keys. To automat
141141
</ClaimsProvider>
142142
```
143143

144-
We've declared a JWT Token Issuer. In the `CryptographicKeys` section, if you used different names to configure the signing and encryption keys in [step 1](#step-1---configure-the-signing-and-encryption-keys), make sure you use the correct value for the `StorageReferenceId`.
144+
We've declared a JWT Issuer. In the `CryptographicKeys` section, if you used different names to configure the signing and encryption keys in [step 1](#step-1---configure-the-signing-and-encryption-keys), make sure you use the correct value for the `StorageReferenceId`.
145145

146146
1. In the `UserJourneys` section of the `ContosoCustomPolicy.XML` file, add the following code:
147147

@@ -267,7 +267,7 @@ After you upload the file, Azure AD B2C adds the prefix `B2C_1A_`, so the names
267267
1. For **Select application** on the overview page of the custom policy, select the web application such as *webapp1* that you previously registered. Make sure that the **Select reply URL** value is set to`https://jwt.ms`.
268268
1. Select **Run now** button.
269269

270-
After the policy finishes execution, you're redirected to `https://jwt.ms`, and you see a decoded JWT token. It looks similar to the following JWT token snippet:
270+
After the policy finishes execution, you're redirected to `https://jwt.ms`, and you see a decoded JWT. It looks similar to the following JWT snippet:
271271

272272
```json
273273
{
@@ -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: 5 additions & 5 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
@@ -38,7 +38,7 @@ This how-to guide series consists of multiple articles. We recommend that you st
3838

3939
|Article | What you'll learn |
4040
|---------|---------|
41-
|[Write your first Azure Active Directory B2C custom policy - Hello World!](custom-policies-series-hello-world.md) | Write your first Azure AD B2C custom policy. You return the message *Hello World!* in the JWT token. |
41+
|[Write your first Azure Active Directory B2C custom policy - Hello World!](custom-policies-series-hello-world.md) | Write your first Azure AD B2C custom policy. You return the message *Hello World!* in the JWT. |
4242
|[Collect and manipulate user inputs by using Azure AD B2C custom policy](custom-policies-series-collect-user-input.md) | Learn how to collect inputs from users, and how to manipulate them.|
4343
|[Validate user inputs by using Azure Active Directory B2C custom policy](custom-policies-series-validate-user-input.md) | Learn how to validate user inputs by using techniques such as limiting user input options, regular expressions, predicates, and validation technical profiles|
4444
|[Create branching in user journey by using Azure Active Directory B2C custom policy](custom-policies-series-branch-user-journey.md) | Learn how to create different user experiences for different users based on the value of a claim.|
@@ -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)