Control 4.4: Copilot in Viva Suite Governance — Troubleshooting

Common issues and resolution steps for Copilot governance across the Viva suite.

Common Issues

Symptoms: The Copilot Chat analytics dashboard in Viva Insights shows no data, or all department adoption rates appear as zero despite known Copilot Chat activity.
Root Cause: Data delay (Copilot Chat usage data takes 48–72 hours to appear in Viva Insights analytics), licensing gap (Viva Insights P2 or Viva Suite license required), or analytics not enabled in the Viva Insights Admin portal.
Resolution:
Verify the Viva Insights P2 or Viva Suite license is assigned to users whose data should appear in analytics.
Confirm Copilot Chat analytics is enabled: navigate to the Viva Insights Admin portal (insights.viva.office.com > Admin > Advanced Insights settings) and verify the Copilot analytics toggle is On.
Allow up to 72 hours for Copilot Chat usage data to populate in the analytics dashboard — check again after the data propagation period.
If data still does not appear after 72 hours, verify that users have the Microsoft 365 Copilot license assigned (Copilot Chat usage data requires an active Copilot license).
Run Script 2 from the PowerShell Setup guide to confirm the usage report API returns data — if it fails, the license or settings configuration is the root cause.

Symptoms: Viva Engage community content surfacing in Teams channels is not appearing in Teams-scoped eDiscovery searches or Communication Compliance review queues.
Root Cause: The Engage-to-Teams integration is active for display purposes but the compliance policies were not updated to include the Teams channel locations receiving Engage content; or the Engage content is treated as Yammer-origin only and requires Yammer-scoped policy search.
Resolution:
Verify which Teams channels receive surfaced Engage content by checking the Viva Engage Admin Center > Communities > [Community] > Connected Teams channels.
In Microsoft Purview > Data Lifecycle Management, confirm that the relevant Teams retention policy explicitly includes the Teams channels receiving Engage content.
For eDiscovery searches, use both Yammer/Viva Engage and Teams locations in the same search to capture all instances of Engage content regardless of where it was viewed.
In Microsoft Purview > Communication Compliance, update the policy scope to include both Yammer messages and Teams channel messages — this dual-location coverage ensures Engage content is captured regardless of which interface the employee used.
Allow up to 24 hours for updated policy scopes to propagate before re-testing.

Symptoms: Copilot-assisted Viva Engage posts are not appearing in the communication compliance review queue despite active policies.
Root Cause: Communication compliance policy may not include Viva Engage / Yammer as a monitored location.
Resolution:
Verify the communication compliance policy includes "Yammer" or "Viva Engage" as a supervised location.
Confirm the user is in the supervised user scope.
Allow up to 24 hours for new policy locations to propagate.
Test with a known policy-triggering phrase to verify detection.

Symptoms: Copilot surfaces confidential or highly sensitive content on the Viva Connections dashboard.
Root Cause: Sensitivity labels may not be properly restricting Copilot's content grounding for the Viva Connections surface.
Resolution:
Verify sensitivity labels are applied to the sensitive content.
Check that the label configuration includes access restrictions.
Review SharePoint site permissions for the content source.
Consider using Restricted SharePoint Search to limit Copilot's content scope.

Symptoms: Copilot recommends alternative courses when users search for mandatory compliance training.
Root Cause: AI recommendations may prioritize relevance or engagement metrics over compliance mandates.
Resolution:
Ensure mandatory compliance training is marked as required in Viva Learning.
Configure learning paths that enforce sequential completion of mandatory training.
Communicate to users that Copilot recommendations supplement but do not replace required training.
Work with the Viva Learning team to pin mandatory training in the user experience.

Symptoms: Copilot-generated progress analysis in Viva Goals does not match actual goal completion data.
Root Cause: Copilot may be generating insights from incomplete or stale data, or data integration between systems is delayed.
Resolution:
Verify goal data integration sources are current and accurately synced.
Cross-reference Copilot progress insights with the actual goal data in Viva Goals.
Report inaccurate insights through the feedback mechanism for model improvement.
Advise users to verify Copilot insights against actual data before making decisions.

Check Viva licensing: Verify Viva suite and Copilot licenses are properly assigned. Viva Insights P2 or Viva Suite is required for Copilot Chat analytics.
Verify Copilot Chat analytics enabled: Confirm in Viva Insights Admin portal > Advanced Insights settings that Copilot analytics is toggled On.
Review compliance policies: Confirm Engage/Yammer is included in communication compliance scope and that Teams channel locations are added for Engage-to-Teams integration coverage.
Test sensitivity labels: Verify labels are applied and enforced in Viva Connections content.
Verify data integrations: Check that Viva Goals data sources are current and synced.
Allow data propagation: Copilot Chat usage data in Viva Insights has a 48–72 hour delay; retention policy scope changes propagate within 24 hours.

Severity	Condition	Escalation Path
Critical	Sensitive content exposed via Viva Connections	IT Security + Compliance
High	Communication compliance gap for Engage — including Engage-to-Teams integration	Compliance team — policy update
High	Copilot Chat analytics showing individual-level data (privacy violation)	IT Admin + Privacy Officer — verify minimum group size configuration
Medium	AI recommendation conflicts with compliance training	HR + Compliance + IT
Low	Minor Viva Goals insight inaccuracies	Document and report to Microsoft
Low	Copilot Chat insights data delay	Monitor — allow 72 hours for data population