Skip to content

Commit 50f3654

Browse files
authored
Update compliance diagnostics documentation
Updated the compliance diagnostics documentation to include a new CI code and modified the date.
1 parent dc02533 commit 50f3654

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Microsoft365/purview/purview/diagnostics/purview-compliance-diagnostics.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,12 @@ ms.custom:
1010
- sap:Microsoft Purview Compliance
1111
- Microsoft Purview
1212
- CSSTroubleshoot
13-
- CI 2772, 1283, 5607, 8191
13+
- CI 2772, 1283, 5607, 8191, 8567
1414
ms.reviewer: shadans, sathyana, meerak, v-shorestris
1515
appliesto:
1616
- Microsoft Purview
1717
search.appverid: MET150
18-
ms.date: 11/19/2025
18+
ms.date: 12/05/2025
1919
---
2020

2121
# Self-help diagnostics for Microsoft Purview
@@ -55,7 +55,7 @@ The following table lists the available diagnostics on **Solutions** pages. You
5555

5656
**Note**: To run these diagnostics, the minimum requirement is that you're an administrator with the Organization Configuration role assigned to you.
5757

58-
When you select a diagnostic on a Solutions page, it begins by running the [Check-PurviewConfig](/powershell/module/exchangepowershell/check-purviewconfi) cmdlet to check your organization's configuration settings in Microsoft Purview. Then the diagnostic calls the appropriate cmdlet listed in the following table to perform checks that are specific to your issue.
58+
When you select a diagnostic on a Solutions page, it begins by running the [Check-PurviewConfig](/powershell/module/exchangepowershell/check-purviewconfig) cmdlet to check your organization's configuration settings in Microsoft Purview. Then the diagnostic calls the appropriate cmdlet listed in the following table to perform checks that are specific to your issue.
5959

6060
| **Issue** | **Checks performed** | **Commandlet Used** | **Solutions page** |
6161
|-|-|-|-|

0 commit comments

Comments
 (0)