Comms Compliance Planner
Plan your Communication Compliance deployment. Choose policy templates, configure locations including Copilot and AI monitoring, set conditions, and run What If scenarios before touching your tenant.
Check off the prerequisites your organization has configured. These determine which locations and features are available and will flag warnings if a policy requires something you have not set up.
Required for all policies
Communication Compliance requires M365 E5, E5 Compliance, or the standalone Communication Compliance add-on.
Microsoft docsAssign the Communication Compliance Admin, Analyst, Investigator, and Viewer role groups. Case Management and Custodian roles are optional.
Microsoft docsMicrosoft 365 audit logging must be enabled for Communication Compliance to capture user activities and policy matches.
Microsoft docsRequired by specific locations
Viva Engage must be in Native Mode (all users in Entra ID, groups as M365 Groups, files in SharePoint) for Communication Compliance monitoring.
Required for monitoring non-M365 Copilot AI sources (Copilot in Fabric, Security Copilot, Copilot Studio, Azure AI). M365 Copilot monitoring is included in standard licensing.
Required to import communications from non-Microsoft apps such as Slack, WhatsApp, Bloomberg, and other third-party sources.
Optional
Create distribution groups or M365 Groups to simplify user scoping. Useful when targeting specific departments or teams rather than all users.
Microsoft docs