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
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -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 **CONNECTION STRING** 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
@@ -77,7 +77,7 @@ To create an instance of Application Insights in your subscription, follow these
77
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 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.
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