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-custom-policies.md
+21-4Lines changed: 21 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: celestedg
8
8
ms.service: active-directory
9
9
ms.workload: identity
10
10
ms.topic: troubleshooting
11
-
ms.date: 04/06/2021
11
+
ms.date: 04/08/2021
12
12
ms.author: mimart
13
13
ms.subservice: B2C
14
14
---
@@ -81,18 +81,31 @@ You can include the correlation ID in your Azure AD B2C tokens. To include the c
81
81
82
82
To diagnose problems with your custom policies, use [Application Insights](troubleshoot-with-application-insights.md). Application Insights traces the activity of your custom policy user journey. It provides a way to diagnose exceptions and observe the exchange of claims between Azure AD B2C and the various claims providers that are defined by technical profiles, such as identity providers, API-based services, the Azure AD B2C user directory, and other services.
83
83
84
-
We recommend installing the [Azure AD B2C extension](https://marketplace.visualstudio.com/items?itemName=AzureADB2CTools.aadb2c) for [VS Code](https://code.visualstudio.com/). With the Azure AD B2C extension, the logs are organized for you by policy name, correlation ID (Application Insights presents the first digit of the correlation ID), and the log timestamp. This feature helps you find the relevant log based on the local timestamp and see the user journey as executed by Azure AD B2C.
84
+
We recommend installing the [Azure AD B2C extension](https://marketplace.visualstudio.com/items?itemName=AzureADB2CTools.aadb2c) for [VS Code](https://code.visualstudio.com/). With the Azure AD B2C extension, the logs are organized for you by policy name, correlation ID (Application Insights presents the first digit of the correlation ID), and the log timestamp. This feature helps you find the relevant log based on the local timestamp and see the user journey as executed by Azure AD B2C.
85
85
86
86
> [!NOTE]
87
-
> The community has developed the Visual Studio Code extension for Azure AD B2C to help identity developers. The extension is not supported by Microsoft and is made available strictly as-is.
87
+
> - There is a short delay, typically less than five minutes, before you can see new logs in Application Insights.
88
+
> - The community has developed the Visual Studio Code extension for Azure AD B2C to help identity developers. The extension is not supported by Microsoft and is made available strictly as-is.
88
89
89
90
A single sign-in flow can issue more than one Azure Application Insights trace. In the following screenshot, the *B2C_1A_signup_signin* policy has three logs. Each log represents part of the sign-in flow.
90
91
92
+
The following screenshot shows the Azure AD B2C extension for VS Code with Azure Application Insights trace explorer.
93
+
91
94

92
95
96
+
### Filter the trace log
97
+
98
+
With the focus on the Azure AD B2C trace explorer, start to type the first digit of the correlation ID, or a time you want to find. You will see a filter box in the top-right of the Azure AD B2C trace explorer showing what you have typed so far, and matching trace logs will be highlighted.
99
+
100
+

101
+
102
+
Hovering over the filter box and selecting **Enable Filter on Type** will show only matching trace logs. Use the **'X' Clear button** to clear the filter.
103
+
104
+

105
+
93
106
### Application Insights trace log details
94
107
95
-
When you select an Azure Application Insights trace, the extension opens the **Application Insights details** page with the following information:
108
+
When you select an Azure Application Insights trace, the extension opens the **Application Insights details** window with the following information:
96
109
97
110
- **Application Insights** - Generic information about the trace log, including the policy name, correlation ID, Azure Application Insights trace ID, and trace timestamp.
98
111
- **Technical profiles** - List of technical profiles that appear in the trace log.
@@ -102,6 +115,10 @@ When you select an Azure Application Insights trace, the extension opens the **A
102
115
- **Exceptions** - List of exceptions or fatal errors that appear in the trace log.
103
116
- **Application Insights JSON** - The raw data the returns from the Application Insights.
104
117
118
+
The following screenshot shows an example of the Application Insights trace log details window.
119
+
120
+

121
+
105
122
## Troubleshoot JWT tokens
106
123
107
124
For JWT token validation and debugging purposes, your can decode JWTs using a site like [https://jwt.ms](https://jwt.ms). Create a test application that can redirect to `https://jwt.ms` for token inspection. If you haven't already done so, [register a web application](tutorial-register-applications.md), and [enable ID token implicit grant](tutorial-register-applications.md#enable-id-token-implicit-grant).
0 commit comments