Skip to content

Commit e80eeba

Browse files
authored
Update troubleshoot-primary-refresh-token.md
Corrected event viewer naming. We still have AAD in event viewer logs (not Microsoft Entra ID)
1 parent bf18a89 commit e80eeba

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/active-directory/devices/troubleshoot-primary-refresh-token.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,19 +88,19 @@ To get the PRT error code, run the `dsregcmd` command, and then locate the `SSO
8888

8989
<a name='method-2-use-event-viewer-to-examine-azure-ad-analytic-and-operational-logs'></a>
9090

91-
#### Method 2: Use Event Viewer to examine Microsoft Entra analytic and operational logs
91+
#### Method 2: Use Event Viewer to examine AAD analytic and operational logs
9292

9393
1. Select **Start**, and then search for and select **Event Viewer**.
9494
1. If the console tree doesn't appear in the **Event Viewer** window, select the **Show/Hide Console Tree** icon to make the console tree visible.
9595
1. In the console tree, select **Event Viewer (Local)**. If child nodes don't appear underneath this item, double-click your selection to show them.
9696
1. Select the **View** menu. If a check mark isn't displayed next to **Show Analytic and Debug Logs**, select that menu item to enable that feature.
97-
1. In the console tree, expand **Applications and Services Logs** > **Microsoft** > **Windows** > **Microsoft Entra ID**. The **Operational** and **Analytic** child nodes appear.
97+
1. In the console tree, expand **Applications and Services Logs** > **Microsoft** > **Windows** > **AAD**. The **Operational** and **Analytic** child nodes appear.
9898

9999
> [!NOTE]
100100
> In the Microsoft Entra Cloud Authentication Provider (CloudAP) plug-in, **Error** events are written to the **Operational** event logs, and information events are written to the **Analytic** event logs. You have to examine both the **Operational** and **Analytic** event logs to troubleshoot PRT issues.
101101
102-
1. In the console tree, select the **Analytic** node to view Microsoft Entra ID-related analytic events.
103-
1. In the list of analytic events, search for Event IDs 1006 and 1007. Event ID 1006 denotes the beginning of the PRT acquisition flow, and Event ID 1007 denotes the end of the PRT acquisition flow. All events in the **Microsoft Entra ID** logs (both **Analytic** and **Operational**) that occurred between Event ID 1006 and Event ID 1007 are logged as part of the PRT acquisition flow. The following table shows an example event listing.
102+
1. In the console tree, select the **Analytic** node to view AAD-related analytic events.
103+
1. In the list of analytic events, search for Event IDs 1006 and 1007. Event ID 1006 denotes the beginning of the PRT acquisition flow, and Event ID 1007 denotes the end of the PRT acquisition flow. All events in the **AAD** logs (both **Analytic** and **Operational**) that occurred between Event ID 1006 and Event ID 1007 are logged as part of the PRT acquisition flow. The following table shows an example event listing.
104104

105105
| Level | Date and Time | Source | Event ID | Task Category |
106106
|-----------------|--------------------------|---------|----------|--------------------------------|

0 commit comments

Comments
 (0)