Skip to content

Commit 7c49980

Browse files
committed
Replacing InstrumentationKey with ConnectionString
1 parent 4e9c8e7 commit 7c49980

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,7 @@ Open the *TrustFrameworkExtensions.xml* file from the starter pack. Add the tech
138138
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.Insights.AzureApplicationInsightsProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
139139
<Metadata>
140140
<!-- The ApplicationInsights instrumentation key, which you use for logging the events -->
141-
<Item Key="InstrumentationKey">xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</Item>
141+
<Item Key="ConnectionString">xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</Item>
142142
<Item Key="DeveloperMode">false</Item>
143143
<Item Key="DisableTelemetry ">false</Item>
144144
</Metadata>

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ To create an instance of Application Insights in your subscription, follow these
7777
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.
7878

7979
```xml
80-
<JourneyInsights TelemetryEngine="ApplicationInsights" InstrumentationKey="{Your Application Insights Key}" DeveloperMode="true" ClientEnabled="false" ServerEnabled="true" TelemetryVersion="1.0.0" />
80+
<JourneyInsights TelemetryEngine="ApplicationInsights" ConnectionString="{Your Application Insights ConnectionString}" DeveloperMode="true" ClientEnabled="false" ServerEnabled="true" TelemetryVersion="1.0.0" />
8181
```
8282

8383
* `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
102102
<Endpoint Id="Token" UserJourneyReferenceId="RedeemRefreshToken" />
103103
</Endpoints>
104104
<UserJourneyBehaviors>
105-
<JourneyInsights TelemetryEngine="ApplicationInsights" InstrumentationKey="{Your Application Insights Key}" DeveloperMode="true" ClientEnabled="false" ServerEnabled="true" TelemetryVersion="1.0.0" />
105+
<JourneyInsights TelemetryEngine="ApplicationInsights" ConnectionString="{Your Application Insights ConnectionString}" DeveloperMode="true" ClientEnabled="false" ServerEnabled="true" TelemetryVersion="1.0.0" />
106106
</UserJourneyBehaviors>
107107
...
108108
</TrustFrameworkPolicy>
@@ -195,7 +195,7 @@ To improve your production environment performance and better user experience, i
195195

196196
```xml
197197
<UserJourneyBehaviors>
198-
<JourneyInsights TelemetryEngine="ApplicationInsights" InstrumentationKey="{Your Application Insights Key}" DeveloperMode="false" ClientEnabled="false" ServerEnabled="true" TelemetryVersion="1.0.0" />
198+
<JourneyInsights TelemetryEngine="ApplicationInsights" ConnectionString="{Your Application Insights ConnectionString}" DeveloperMode="false" ClientEnabled="false" ServerEnabled="true" TelemetryVersion="1.0.0" />
199199
</UserJourneyBehaviors>
200200
```
201201

0 commit comments

Comments
 (0)