Collect Azure Active Directory B2C logs with Application Insights

This feature is available only for custom policies. For setup steps, select Custom policy in the preceding selector.

This article provides steps for collecting logs from Active Directory B2C (Azure AD B2C) so that you can diagnose problems with your custom policies. Application Insights provides a way to diagnose exceptions and visualize application performance issues. Azure AD B2C includes a feature for sending data to Application Insights.

The detailed activity logs described here should be enabled ONLY during the development of your custom policies.

Set up Application Insights

If you don't already have one, create an instance of Application Insights in your subscription.

To use an existing instance of Application Insights in your subscription, follow these steps:

1. Sign in to the Azure portal.
2. 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.
3. On the Portal settings | Directories + subscriptions page, find your Microsoft Entra directory in the Directory name list, and then select Switch.
4. Open the Application Insights resource that you created earlier.
5. On the Overview page, and record the Instrumentation Key

To create an instance of Application Insights in your subscription, follow these steps:

1. Sign in to the Azure portal.
2. 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.
3. On the Portal settings | Directories + subscriptions page, find your Microsoft Entra directory in the Directory name list, and then select Switch.
4. Select Create a resource in the left-hand navigation menu.
5. Search for and select Application Insights, then select Create.
6. Complete the form, select Review + create, and then select Create.
7. Once the deployment completes, select Go to resource.
8. Under Configure in Application Insights menu, select Properties.
9. Record the INSTRUMENTATION KEY for use in a later step.

Configure the custom policy

1. Open the relying party (RP) file, for example SignUpOrSignin.xml.

2. Add the following attributes to the <TrustFrameworkPolicy> element:

   DeploymentMode="Development"
   UserJourneyRecorderEndpoint="urn:journeyrecorder:applicationinsights"
   

3. 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 for a complete order of the RelyingParty child elements.

4. 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.

   <JourneyInsights TelemetryEngine="ApplicationInsights" InstrumentationKey="{Your Application Insights Key}" DeveloperMode="true" ClientEnabled="false" ServerEnabled="true" TelemetryVersion="1.0.0" />
   

   • 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.
   • ClientEnabled="true" sends the ApplicationInsights client-side script for tracking page view and client-side errors. You can view this in the browserTimings table in the Application Insights portal. By setting ClientEnabled= "true", you add Application Insights to your page script and you get timings of page loads and AJAX calls, counts, details of browser exceptions and AJAX failures, and user and session counts. This field is optional, and is set to false by default.
   • ServerEnabled="true" sends the existing UserJourneyRecorder JSON as a custom event to Application Insights.

   For example:

   <TrustFrameworkPolicy
     ...
     TenantId="fabrikamb2c.partner.onmschina.cn"
     PolicyId="SignUpOrSignInWithAAD"
     DeploymentMode="Development"
     UserJourneyRecorderEndpoint="urn:journeyrecorder:applicationinsights"
   >
   ...
   <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>
     ...
   </TrustFrameworkPolicy>
   

5. Upload the policy.

See the logs in Application Insights

There's a short delay, typically less than five minutes, before you can see new logs in Application Insights.

1. Open the Application Insights resource that you created in the Azure portal.
2. On the Overview page, select Logs.
3. Open a new tab in Application Insights.

Here's a list of queries you can use to see the logs:

Query	Description
traces	Get all of the logs generated by Azure AD B2C
traces | where timestamp > ago(1d)	Get all of the logs generated by Azure AD B2C for the last day.
traces | where message contains "exception" | where timestamp > ago(2h)	Get all of the logs with errors from the last two hours.
traces | where customDimensions.Tenant == "contoso.partner.onmschina.cn" and customDimensions.UserJourney == "b2c_1a_signinandup"	Get all of the logs generated by Azure AD B2C contoso.partner.onmschina.cn tenant, and user journey is b2c_1a_signinandup.
traces | where customDimensions.CorrelationId == "aaaa0000-bb11-2222-33cc-444444dddddd"	Get all of the logs generated by Azure AD B2C for a correlation ID. Replace the correlation ID with your correlation ID.

The entries may be long. Export to CSV for a closer look.

For more information about querying, see Overview of log queries in Azure Monitor.

See the logs in VS Code extension

We recommend you to install the Azure AD B2C extension for VS Code. With the Azure AD B2C extension, the logs are organized for you by the policy name, correlation ID (the application insights presents the first digit of the correlation ID), and the log timestamp. This feature helps you to find the relevant log based on the local timestamp and see the user journey as executed by Azure AD B2C.

Set Application Insights API access

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.

To get Application Insights ID and key:

1. In Azure portal, open the Application Insights resource for your application.

2. Select Configure, then select API Access.

3. Copy the Application ID

4. Select Create API Key

5. Check the Read telemetry box.

6. Copy the Key before closing the Create API key blade and save it somewhere secure. If you lose the key, you need to create another.

   

Set up Azure AD B2C VS Code extension

Now that you have Azure Application insights API ID and Key, you can configure the VS Code extension to read the logs. Azure AD B2C VS Code extension provides two scopes for settings:

• User Global Settings - Settings that apply globally to any instance of VS Code you open.
• Workspace Settings - Settings stored inside your workspace and only apply when the workspace is opened (using VS Code open folder).

1. From the Azure AD B2C Trace explorer, click on the Settings icon.

   

2. Provide the Azure Application Insights ID and key.

3. Click Save

After you save the settings, the Application insights logs appear on the Azure AD B2C Trace (App Insights) window.

Configure Application Insights in Production

To improve your production environment performance and better user experience, it's important to configure your policy to ignore messages that are unimportant. You also need to make sure that you don't log Personally Identifiable Information (PII). Use the following configuration in production environments and no logs are sent to your application insights.

1. Set the DeploymentMode attribute of the TrustFrameworkPolicy to Production.

   <TrustFrameworkPolicy xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/online/cpim/schemas/2013/06" PolicySchemaVersion="0.3.0.0"
   TenantId="yourtenant.partner.onmschina.cn"
   PolicyId="B2C_1A_signup_signin"
   PublicPolicyUri="http://yourtenant.partner.onmschina.cn/B2C_1A_signup_signin"
   DeploymentMode="Production"
   UserJourneyRecorderEndpoint="urn:journeyrecorder:applicationinsights">
   

2. Set the DeveloperMode of the JourneyInsights to false.

   <UserJourneyBehaviors>
     <JourneyInsights TelemetryEngine="ApplicationInsights" InstrumentationKey="{Your Application Insights Key}" DeveloperMode="false" ClientEnabled="false" ServerEnabled="true" TelemetryVersion="1.0.0" />
   </UserJourneyBehaviors>
   

3. Upload and test your policy.

Next steps

• Learn how to troubleshoot Azure AD B2C custom policies