You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Active Directory B2C (Azure AD B2C) provides support sending event data directly to [Application Insights](../azure-monitor/app/app-insights-overview.md) by using the instrumentation key provided to Azure AD B2C. With Application Insights technical profile, can get detailed and customized event logs for your user journeys, such as:
22
+
Azure Active Directory B2C (Azure AD B2C) supports sending event data directly to [Application Insights](../azure-monitor/app/app-insights-overview.md) by using the instrumentation key provided to Azure AD B2C. With an Application Insights technical profile, you can get detailed and customized event logs for your user journeys to:
23
23
24
24
* Gain insights on user behavior.
25
25
* Troubleshoot your own policies in development or in production.
@@ -29,10 +29,10 @@ Azure Active Directory B2C (Azure AD B2C) provides support sending event data di
29
29
30
30
## Protocol
31
31
32
-
The **Name** attribute of the **Protocol** element needs to be set to `Proprietary`. The **handler** attribute must contain the fully qualified name of the protocol handler assembly that is used by Azure AD B2C, for application insights:
32
+
The **Name** attribute of the **Protocol** element needs to be set to `Proprietary`. The **handler** attribute must contain the fully qualified name of the protocol handler assembly that is used by Azure AD B2C for Application Insights:
The following example shows the common application insights technical profile. Other application insights technical profiles include the AzureInsights-Common to leverage its configuration.
35
+
The following example shows the common Application Insights technical profile. Other Application Insights technical profiles include the AzureInsights-Common to leverage its configuration.
36
36
37
37
```xml
38
38
<TechnicalProfileId="AzureInsights-Common">
@@ -43,7 +43,7 @@ The following example shows the common application insights technical profile. O
43
43
44
44
## Input claims
45
45
46
-
The **InputClaims** element contains a list of claims to send to the Application Insights. You can also map the name of your claim to a name you prefer to appear in Application Insights. Following example shows how to send telemetries to Application Insights. Properties of an event are added through the syntax `{property:NAME}`, where NAME is property being added to the event. DefaultValue can be either a static value or a value that's resolved by one of the supported [claim resolvers](claim-resolver-overview.md).
46
+
The **InputClaims** element contains a list of claims to send to Application Insights. You can also map the name of your claim to a name you prefer to appear in Application Insights. The following example shows how to send telemetries to Application Insights. Properties of an event are added through the syntax `{property:NAME}`, where NAME is property being added to the event. DefaultValue can be either a static value or a value that's resolved by one of the supported [claim resolvers](claim-resolver-overview.md).
47
47
48
48
```XML
49
49
<InputClaims>
@@ -54,7 +54,7 @@ The **InputClaims** element contains a list of claims to send to the Application
54
54
</InputClaims>
55
55
```
56
56
57
-
The **InputClaimsTransformations** element may contain a collection of **InputClaimsTransformation** elements that are used to modify the input claims or generate new ones before sending to the Application Insights.
57
+
The **InputClaimsTransformations** element may contain a collection of **InputClaimsTransformation** elements that are used to modify the input claims or generate new ones before sending to Application Insights.
58
58
59
59
## Persist claims
60
60
@@ -74,8 +74,8 @@ The CryptographicKeys element is not used.
74
74
| Attribute | Required | Description |
75
75
| --------- | -------- | ----------- |
76
76
| InstrumentationKey| Yes | The Application Insights [instrumentation key](../azure-monitor/app/create-new-resource.md#copy-the-instrumentation-key), which will be used for logging the events. |
77
-
| DeveloperMode| No | A Boolean that indicates whether developer mode is enabled. Possible values: `true`, or `false` (default). This metadata controls how events are buffered. In a development environment with minimal event volume, enabling developer mode results in events being sent immediately to Application Insights.|
78
-
|DisableTelemetry |No |A Boolean that indicates whether telemetry should be enabled or not. Possible values: `true`, or `false` (default).|
77
+
| DeveloperMode| No | A Boolean that indicates whether developer mode is enabled. Possible values: `true` or `false` (default). This metadata controls how events are buffered. In a development environment with minimal event volume, enabling developer mode results in events being sent immediately to Application Insights.|
78
+
|DisableTelemetry |No |A Boolean that indicates whether telemetry should be enabled or not. Possible values: `true` or `false` (default).|
Azure Active Directory B2C (Azure AD B2C) provides support for verifying a phone number by using Azure Multi-Factor Authentication (MFA). Use this technical profile to generate and send a code to a phone number, and then verify the code. The Azure MFA technical profile may also return an error message. The validation technical profile validates the user-provided data before the user journey continues. With the validation technical profile, an error message is display on a self-asserted page.
21
+
Azure Active Directory B2C (Azure AD B2C) provides support for verifying a phone number by using Azure Multi-Factor Authentication (MFA). Use this technical profile to generate and send a code to a phone number, and then verify the code. The Azure MFA technical profile may also return an error message. The validation technical profile validates the user-provided data before the user journey continues. With the validation technical profile, an error message displays on a self-asserted page.
22
22
23
23
This technical profile:
24
24
25
-
-Provides doesn't have user interface to interact with the user. Rather it's called from a [self-asserted](self-asserted-technical-profile.md) technical profile, or a [display control](display-controls.md) as a [validation technical profile](validation-technical-profile.md).
26
-
- Uses the Azure MFA service to generates and sends a code to a phone number, and then verifies the code.
25
+
-Doesn't provide an interface to interact with the user. Instead, the user interface is called from a [self-asserted](self-asserted-technical-profile.md) technical profile, or a [display control](display-controls.md) as a [validation technical profile](validation-technical-profile.md).
26
+
- Uses the Azure MFA service to generate and send a code to a phone number, and then verifies the code.
Azure Active Directory B2C (Azure AD B2C) provides support for enroll and verify phone number. This technical profile:
21
+
Azure Active Directory B2C (Azure AD B2C) provides support for enrolling and verifying phone numbers. This technical profile:
22
22
23
-
- Provides user interface to interact with the user.
24
-
- Uses content definition control the look and feel.
25
-
-Uses both phone call and text messages to validate the phone number.
26
-
- Supports multiple phone numbers. User can select one of phone numbers to verify.
27
-
- If a phone number is provided, the phone factor asks the user to verify the phone number. If not provided, it asks the user to enroll a new phone number.
28
-
- Returns a claim indicates whether user provides a new phone number. You can use this claim to decide whether the phone number should be persisted to the Azure AD user profile.
23
+
- Provides a user interface to interact with the user.
24
+
- Uses content definition to control the look and feel.
25
+
-Supports both phone calls and text messages to validate the phone number.
26
+
- Supports multiple phone numbers. The user can select one of the phone numbers to verify.
27
+
- If a phone number is provided, the phone factor user interface asks the user to verify the phone number. If not provided, it asks the user to enroll a new phone number.
28
+
- Returns a claim indicating whether the user provided a new phone number. You can use this claim to decide whether the phone number should be persisted to the Azure AD user profile.
29
29
30
30
## Protocol
31
31
32
-
The **Name** attribute of the **Protocol** element needs to be set to `Proprietary`. The **handler** attribute must contain the fully qualified name of the protocol handler assembly that is used by Azure AD B2C, for phone factor:
32
+
The **Name** attribute of the **Protocol** element needs to be set to `Proprietary`. The **handler** attribute must contain the fully qualified name of the protocol handler assembly that is used by Azure AD B2C for phone factor:
<!--A claim that contain the phone number. If the claim is empty, Azure AD B2C asks the user to enroll a new phone number. Otherwise, it asks the user to verify the phone number -->
52
+
<!--A claim that contains the phone number. If the claim is empty, Azure AD B2C asks the user to enroll a new phone number. Otherwise, it asks the user to verify the phone number.-->
Following example demonstrates using multiple phone numbers. For more information, see [sample policy](https://github.com/azure-ad-b2c/samples/tree/master/policies/mfa-add-secondarymfa)
57
+
The following example demonstrates using multiple phone numbers. For more information, see [sample policy](https://github.com/azure-ad-b2c/samples/tree/master/policies/mfa-add-secondarymfa).
58
58
59
59
```XML
60
60
<InputClaims>
@@ -64,17 +64,17 @@ Following example demonstrates using multiple phone numbers. For more informatio
64
64
</InputClaims>
65
65
```
66
66
67
-
The InputClaimsTransformations element may contain a collection of InputClaimsTransformation elements that are used to modify the input claims or generate new ones before presenting the phone factor page.
67
+
The InputClaimsTransformations element may contain a collection of InputClaimsTransformation elements that are used to modify the input claims or generate new ones before presenting them to the phone factor page.
68
68
69
69
## Output claims
70
70
71
71
The OutputClaims element contains a list of claims returned by the phone factor technical profile.
72
72
73
73
```xml
74
74
<OutputClaims>
75
-
<!-- The verified phone number. The partner claim type must be set to `Verified.OfficePhone` -->
75
+
<!-- The verified phone number. The partner claim type must be set to `Verified.OfficePhone`.-->
@@ -91,7 +91,7 @@ The **CryptographicKeys** element is not used.
91
91
| Attribute | Required | Description |
92
92
| --------- | -------- | ----------- |
93
93
| ContentDefinitionReferenceId | Yes | The identifier of the [content definition](contentdefinitions.md) associated with this technical profile. |
94
-
| ManualPhoneNumberEntryAllowed| No | Specify whether or not a user is allowed to manually enter in a phone number. Possible values: `true`, or `false` (default).|
94
+
| ManualPhoneNumberEntryAllowed| No | Specify whether or not a user is allowed to manually enter a phone number. Possible values: `true` or `false` (default).|
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/technical-profiles-overview.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ manager: celestedg
9
9
ms.service: active-directory
10
10
ms.workload: identity
11
11
ms.topic: reference
12
-
ms.date: 03/18/2020
12
+
ms.date: 03/20/2020
13
13
ms.author: mimart
14
14
ms.subservice: B2C
15
15
---
@@ -29,12 +29,11 @@ A technical profile enables these types of scenarios:
29
29
-[Azure Multi-Factor Authentication](multi-factor-auth-technical-profile.md) - provides support for verifying a phone number by using Azure Multi-Factor Authentication (MFA).
30
30
-[Claims transformation](claims-transformation-technical-profile.md) - Call output claims transformations to manipulate claims values, validate claims, or set default values for a set of output claims.
31
31
-[JWT token issuer](jwt-issuer-technical-profile.md) - Emits a JWT token that is returned back to the relying party application.
-[OAuth1](oauth1-technical-profile.md) - Federation with any OAuth 1.0 protocol identity provider.
34
33
-[OAuth2](oauth2-technical-profile.md) - Federation with any OAuth 2.0 protocol identity provider.
35
34
-[One time password](one-time-password-technical-profile.md) - Provides support for managing the generation and verification of a one-time password.
36
35
-[OpenID Connect](openid-connect-technical-profile.md) - Federation with any OpenID Connect protocol identity provider.
37
-
-[Phone factor](phone-factor-technical-profile.md) - Support for enroll and verify phone numbers.
36
+
-[Phone factor](phone-factor-technical-profile.md) - Support for enrolling and verifying phone numbers.
38
37
-[RESTful provider](restful-technical-profile.md) - Call to REST API services, such as validate user input, enrich user data, or integrate with line-of-business applications.
39
38
-[SAML2](saml-technical-profile.md) - Federation with any SAML protocol identity provider.
40
39
-[SAML token issuer](saml-issuer-technical-profile.md) - Emits a SAML token that is returned back to the relying party application.
0 commit comments