Merge pull request #109004 from amitabhphogat/patch-1

Updated the order for in policy #41062

Author: Court72

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

@@ -72,7 +72,7 @@ To create an instance of Application Insights in your subscription, follow these
    UserJourneyRecorderEndpoint="urn:journeyrecorder:applicationinsights"
    ```
 
-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" />`.
+1. If it doesn't already exist, add a `<UserJourneyBehaviors>` child node to the `<RelyingParty>` node. It must be located after `<Endpoints><Endpoint Id="Token" UserJourneyReferenceId="RedeemRefreshToken" /></Endpoints>`.
 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.
 
     ```xml
@@ -96,6 +96,10 @@ To create an instance of Application Insights in your subscription, follow these
     ...
     <RelyingParty>
       <DefaultUserJourney ReferenceId="UserJourney ID from your extensions policy, or equivalent (for example: SignUpOrSigninWithAzureAD)" />
+      <Endpoints>
+         <!--points to refresh token journey when app makes refresh token request-->
+         <Endpoint Id="Token" UserJourneyReferenceId="RedeemRefreshToken" />
+      </Endpoints>
       <UserJourneyBehaviors>
         <JourneyInsights TelemetryEngine="ApplicationInsights" InstrumentationKey="{Your Application Insights Key}" DeveloperMode="true" ClientEnabled="false" ServerEnabled="true" TelemetryVersion="1.0.0" />
       </UserJourneyBehaviors>