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
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/troubleshoot-with-application-insights.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: kengaderdus
6
6
manager: CelesteDG
7
7
ms.service: azure-active-directory
8
8
ms.topic: troubleshooting
9
-
ms.date: 01/22/2024
9
+
ms.date: 04/17/2025
10
10
ms.author: kengaderdus
11
11
ms.subservice: b2c
12
12
zone_pivot_groups: b2c-policy-type
@@ -49,7 +49,7 @@ To use an existing instance of Application Insights in your subscription, follow
49
49
1. Make sure you're using the Microsoft Entra directory that has your Azure subscription, and not your Azure AD B2C directory. Select the **Directories + subscriptions** icon in the portal toolbar.
50
50
1. On the **Portal settings | Directories + subscriptions** page, find your Microsoft Entra directory in the **Directory name** list, and then select **Switch**.
51
51
1. Open the Application Insights resource that you created earlier.
52
-
1. On the **Overview** page, and record the **Instrumentation Key**
52
+
1. On the **Overview** page, and record the **Connection String**
53
53
54
54
To create an instance of Application Insights in your subscription, follow these steps:
55
55
@@ -61,7 +61,7 @@ To create an instance of Application Insights in your subscription, follow these
61
61
1. Complete the form, select **Review + create**, and then select **Create**.
62
62
1. Once the deployment completes, select **Go to resource**.
63
63
1. Under **Configure** in Application Insights menu, select **Properties**.
64
-
1. Record the **INSTRUMENTATION KEY** for use in a later step.
64
+
1. Record the **CONNECTION STRING** for use in a later step.
65
65
66
66
## Configure the custom policy
67
67
@@ -74,10 +74,10 @@ To create an instance of Application Insights in your subscription, follow these
74
74
```
75
75
76
76
1. If it doesn't already exist, add a `<UserJourneyBehaviors>` child node to the `<RelyingParty>` node. It must be located after `<DefaultUserJourney ReferenceId="UserJourney Id" from your extensions policy, or equivalent (for example:SignUpOrSigninWithAAD" />`. See [RelyingParty schema reference](./relyingparty.md) for a complete order of the **RelyingParty** child elements.
77
-
1. Add the following node as a child of the `<UserJourneyBehaviors>` element. Make sure to replace `{Your Application Insights Key}` with the Application Insights **Instrumentation Key** that you recorded earlier.
77
+
1. Add the following node as a child of the `<UserJourneyBehaviors>` element. Make sure to replace `{Your Application Insights Key}` with the Application Insights **Connection String** that you recorded earlier.
* `DeveloperMode="true"` tells ApplicationInsights to expedite the telemetry through the processing pipeline. Good for development, but constrained at high volumes. In production, set the `DeveloperMode` to `false`.
@@ -102,7 +102,7 @@ To create an instance of Application Insights in your subscription, follow these
@@ -144,7 +144,7 @@ We recommend you to install the [Azure AD B2C extension](https://marketplace.vis
144
144
After you set up the Application Insights, and configure the custom policy, you need to get your Application Insights **API ID**, and create **API Key**. Both the API ID and API key are used by Azure AD B2C extension to read the Application Insights events (telemetries). Your API keys should be managed like passwords. Keep it secret.
145
145
146
146
> [!NOTE]
147
-
> Application Insights instrumentation key that your create earlier is used by Azure AD B2C to send telemetries to Application Insights. You use the instrumentation key only in your Azure AD B2C policy, not in the VS Code extension.
147
+
> Application Insights connection string that your create earlier is used by Azure AD B2C to send telemetries to Application Insights. You use the connection string only in your Azure AD B2C policy, not in the VS Code extension.
148
148
149
149
To get Application Insights ID and key:
150
150
@@ -195,7 +195,7 @@ To improve your production environment performance and better user experience, i
0 commit comments