Skip to content

Commit cfd6357

Browse files
author
Suzi Zuber
committed
Merge branch 'main' into suzuber/new-vmware-cloud-director-availability-article
2 parents c2421fe + bdb591a commit cfd6357

File tree

648 files changed

+5559
-3533
lines changed

Some content is hidden

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

648 files changed

+5559
-3533
lines changed

.openpublishing.redirection.json

Lines changed: 94 additions & 96 deletions
Large diffs are not rendered by default.

CODEOWNERS

Lines changed: 0 additions & 9 deletions
This file was deleted.

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,9 @@ ms.date: 01/17/2023
99
ms.author: godonnell
1010
ms.subservice: B2C
1111
zone_pivot_groups: b2c-policy-type
12+
13+
# Customer intent: I want to enrich tokens with claims from external identity data sources using APIs or outbound webhooks.
14+
1215
---
1316

1417
# Enrich tokens with claims from external sources using API connectors

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

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,15 @@ description: Configure an API connector to be used in a sign-up user flow.
55
ms.service: active-directory
66
ms.subservice: B2C
77
ms.topic: how-to
8-
ms.date: 12/20/2022
8+
ms.date: 01/24/2024
99
author: garrodonnell
1010
ms.author: godonnell
1111
manager: CelesteDG
1212
ms.custom: it-pro, b2c-support
1313
zone_pivot_groups: b2c-policy-type
14+
15+
#Customer Intent: As a developer or IT administrator, I want to use API connectors to integrate sign-up user flows with REST APIs to customize the sign-up experience and integrate with external systems.
16+
1417
---
1518

1619
# Add an API connector to a sign-up user flow

articles/active-directory-b2c/add-identity-provider.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,9 @@ ms.custom: mvc
1111
ms.topic: how-to
1212
ms.service: active-directory
1313
ms.subservice: B2C
14+
15+
#Customer Intent: As a developer integrating Azure AD B2C into my application, I want to add an identity provider, so that users can sign in with their existing social or enterprise accounts without creating a new account.
16+
1417
---
1518

1619
# Add an identity provider to your Azure Active Directory B2C tenant

articles/active-directory-b2c/add-password-reset-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.author: godonnell
1111
ms.subservice: B2C
1212
zone_pivot_groups: b2c-policy-type
1313

14-
#Customer intent: As a developer, I want to enable my users to reset their passwords without the need for admin intervention, so that they can recover their accounts if they forget their passwords.
14+
#Customer Intent: As an Azure AD B2C administrator, I want to set up a password reset flow for local accounts, so that users can reset their passwords if they forget them.
1515
---
1616

1717
# Set up a password reset flow in Azure Active Directory B2C

articles/active-directory-b2c/add-sign-up-and-sign-in-policy.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ ms.author: godonnell
1414
ms.subservice: B2C
1515
ms.custom: "b2c-support"
1616
zone_pivot_groups: b2c-policy-type
17+
18+
#Customer Intent: As a developer integrating Azure Active Directory B2C into my application, I want to set up a sign-up and sign-in flow, so that users can sign up and sign in with local or social accounts, and reset their passwords if needed.
19+
1720
---
1821

1922
# Set up a sign-up and sign-in flow in Azure Active Directory B2C

articles/active-directory-b2c/analytics-with-application-insights.md

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.topic: how-to
1111

12-
ms.date: 01/11/2024
12+
ms.date: 01/26/2024
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
zone_pivot_groups: b2c-policy-type
@@ -38,6 +38,8 @@ In Azure Active Directory B2C (Azure AD B2C), you can send event data directly t
3838
- Measure performance.
3939
- Create notifications from Application Insights.
4040

41+
[!INCLUDE [active-directory-b2c-limited-to-custom-policy](../../includes/active-directory-b2c-public-preview.md)]
42+
4143
## Overview
4244

4345
To enable custom event logs, add an Application Insights technical profile. In the technical profile, you define the Application Insights instrumentation key, the event name, and the claims to record. To post an event, add the technical profile as an orchestration step in a [user journey](userjourneys.md).
@@ -183,11 +185,13 @@ Open the *TrustFrameworkExtensions.xml* file from the starter pack. Add the tech
183185
184186
## Add the technical profiles as orchestration steps
185187

186-
Add new orchestration steps that refer to the technical profiles.
188+
Add new orchestration steps that refer to the technical profiles.
187189

188190
> [!IMPORTANT]
189191
> After you add the new orchestration steps, renumber the steps sequentially without skipping any integers from 1 to N.
190192
193+
1. Identify the policy file that contains your user journey, such as `SocialAndLocalAccounts/SignUpOrSignin.xml`, then open it.
194+
191195
1. Call `AppInsights-SignInRequest` as the second orchestration step. This step tracks that a sign-up or sign-in request has been received.
192196

193197
```xml
@@ -199,10 +203,12 @@ Add new orchestration steps that refer to the technical profiles.
199203
</OrchestrationStep>
200204
```
201205

202-
1. Before the `SendClaims` orchestration step, add a new step that calls `AppInsights-UserSignup`. It's triggered when the user selects the sign-up button in a sign-up or sign-in journey.
206+
1. Before the `SendClaims` orchestration step, add a new step that calls `AppInsights-UserSignup`. It's triggered when the user selects the sign-up button in a sign-up or sign-in journey. You may need to update the orchestration step, `Order="8"`,to make sure you don't skip any integer from the first to the last orchestration step.
203207

204208
```xml
205-
<!-- Handles the user selecting the sign-up link in the local account sign-in page -->
209+
<!-- Handles the user selecting the sign-up link in the local account sign-in page
210+
The `SendClaims` orchestration step comes after this one,
211+
-->
206212
<OrchestrationStep Order="8" Type="ClaimsExchange">
207213
<Preconditions>
208214
<Precondition Type="ClaimsExist" ExecuteActionsIf="false">
@@ -221,10 +227,12 @@ Add new orchestration steps that refer to the technical profiles.
221227
</OrchestrationStep>
222228
```
223229

224-
1. After the `SendClaims` orchestration step, call `AppInsights-SignInComplete`. This step shows a successfully completed journey.
230+
1. After the `SendClaims` orchestration step, call `AppInsights-SignInComplete`. This step shows a successfully completed journey. You may need to update the orchestration step, `Order="10"`, to make sure you don't skip any integer from the first to the last orchestration step.
225231

226232
```xml
227-
<!-- Track that we have successfully sent a token -->
233+
<!-- Track that we have successfully sent a token
234+
The `SendClaims` orchestration step come before this one,
235+
-->
228236
<OrchestrationStep Order="10" Type="ClaimsExchange">
229237
<ClaimsExchanges>
230238
<ClaimsExchange Id="TrackSignInComplete" TechnicalProfileReferenceId="AppInsights-SignInComplete" />

articles/active-directory-b2c/b2c-global-identity-funnel-based-design.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,15 @@
22
title: Build a global identity solution with funnel-based approach
33
titleSuffix: Azure AD B2C
44
description: Learn the funnel-based design consideration for Azure AD B2C to provide customer identity management for global customers.
5-
65
author: gargi-sinha
76
manager: martinco
8-
97
ms.service: active-directory
10-
118
ms.topic: conceptual
12-
ms.date: 12/15/2022
9+
ms.date: 01/26/2024
1310
ms.author: gasinh
1411
ms.subservice: B2C
12+
13+
#customer intent: I'm a developer, and I need to understand how to build a global identity solution using a funnel-based approach, so I can implement it in my organization's Azure AD B2C environment.
1514
---
1615

1716
# Build a global identity solution with funnel-based approach

articles/active-directory-b2c/b2c-global-identity-proof-of-concept-funnel.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,11 @@ manager: martinco
88
ms.service: active-directory
99

1010
ms.topic: conceptual
11-
ms.date: 12/15/2022
11+
ms.date: 01/26/2024
1212
ms.author: gasinh
1313
ms.subservice: B2C
14+
15+
#customer intent: As a developer, I want to understand how to build a global identity solution using a funnel-based approach, so I can implement it in my organization's Azure AD B2C environment.
1416
---
1517

1618
# Azure Active Directory B2C global identity framework proof of concept for funnel-based configuration

0 commit comments

Comments
 (0)