Microsoft Copilot in Viva Insights uses workplace productivity signals to generate personalized recommendations and summaries for employees and managers. These signals come from Microsoft 365 apps, organizational data, and user activity patterns. Without understanding which data sources Copilot reads, you cannot control what information appears in your Viva Insights dashboards or Copilot responses. This article explains each productivity signal source, how Copilot processes them, and how to configure access for your tenant.
Key Takeaways: Copilot in Viva Insights Signal Sources
- Microsoft 365 Graph data: Copilot reads calendar, email, chat, and document activity from Exchange Online, Teams, and SharePoint to generate insights.
- Organizational data from HR systems: Manager hierarchy, department, and role data from your HRIS or Azure AD enriches Copilot responses with team context.
- Viva Insights advanced metrics: Copilot uses focus time, meeting hours, and collaboration patterns from Viva Insights to produce personalized productivity summaries.
Understanding Productivity Signal Sources for Copilot
Copilot in Viva Insights does not generate insights from raw data alone. It relies on three categories of signal sources: Microsoft 365 Graph data, organizational data from your tenant, and Viva Insights computed metrics. Each source provides a different layer of context that Copilot combines to produce relevant output.
Microsoft 365 Graph data includes calendar events, email metadata, Teams chat activity, and document collaboration events. Copilot reads this data in near real time to understand your work patterns. For example, if you have a series of recurring meetings with the same group, Copilot can suggest a recurring focus block after those meetings.
Organizational data comes from Azure Active Directory and optionally from your HR system through the Viva Insights organizational data upload. This data includes employee names, job titles, departments, and reporting lines. Copilot uses this hierarchy to provide manager-specific insights such as team meeting overload or after-hours work trends.
Viva Insights advanced metrics are precomputed by the Viva Insights service. These include average focus hours per week, meeting hours per day, collaboration hours, and network size. Copilot reads these metrics to generate personalized recommendations without needing to recalculate raw data each time.
How Copilot Processes Signal Sources
When a user opens a Copilot prompt in Viva Insights, the system queries the Microsoft 365 Graph for recent activity from the past 28 days by default. It then enriches that data with organizational context from Azure AD. Finally, it retrieves precomputed Viva Insights metrics for the same period. Copilot combines these three layers into a single response. The response never includes raw message content or document text unless the user explicitly asks for it and has permission to view that content.
Steps to Configure Signal Sources for Copilot in Viva Insights
Before configuring signal sources, verify that your tenant has the Viva Insights service plan enabled and that users have appropriate licenses. Copilot in Viva Insights requires a Microsoft 365 E5 or Viva Insights license with the Copilot add-on.
- Open the Microsoft 365 admin center
Sign in as a Global Administrator or Viva Insights Administrator. Go to Admin centers > Viva Insights. - Navigate to the Data sources page
In the Viva Insights admin center, select Settings > Data sources. This page lists all connected signal sources. - Enable Microsoft 365 Graph data
Under the Microsoft 365 section, toggle Allow Copilot to access Microsoft 365 Graph data to On. This enables Copilot to read calendar, email, and chat metadata. - Upload organizational data if not already present
If your organizational data is not synced from Azure AD, select Upload HR data and follow the CSV template instructions. Required fields include EmployeeId, ManagerId, Department, and JobTitle. - Confirm Viva Insights advanced metrics are active
Go to Settings > Advanced insights and ensure that Computed metrics is enabled. Copilot requires these metrics to generate productivity summaries. - Test the configuration
Open the Viva Insights app in Microsoft Teams or the web app. Type a prompt such as Show my focus time trends this week. Verify that Copilot returns a response with data from all three sources.
Common Misunderstandings About Signal Sources
Copilot reads the content of all my emails and chats
Copilot does not read the body text of emails or chat messages by default. It reads only metadata: subject lines, timestamps, participants, and meeting durations. To access message content, a user must explicitly request it and have the necessary permissions. Tenant administrators can restrict metadata access through data source settings.
Organizational data must be uploaded manually
If your tenant uses Azure Active Directory with proper attributes populated, Copilot reads organizational data automatically. Manual upload is only required when you need additional HR fields such as cost center or location that are not in Azure AD. The CSV upload is optional for basic hierarchy data.
Viva Insights metrics are recalculated with every Copilot request
Viva Insights precomputes metrics daily. Copilot reads these cached values instead of recalculating them. This reduces processing time and ensures consistency between Viva Insights dashboards and Copilot responses. Metrics update every 24 hours at the time configured in the Viva Insights admin center.
Disabling one signal source stops all Copilot features
Disabling Microsoft 365 Graph data prevents Copilot from generating personalized recommendations based on your calendar and collaboration patterns. However, Copilot can still use organizational data and Viva Insights metrics to provide generic productivity tips. The response quality degrades significantly without Graph data.
Copilot in Viva Insights Signal Sources vs Microsoft Graph Connectors
| Item | Copilot in Viva Insights Signal Sources | Microsoft Graph Connectors |
|---|---|---|
| Data types | Calendar metadata, email metadata, Teams chat metadata, organizational hierarchy, precomputed Viva metrics | External data from third-party systems like Salesforce, ServiceNow, or custom databases |
| Access scope | Limited to Microsoft 365 tenant data and Viva Insights computed metrics | Can index any external content and make it searchable via Microsoft Graph |
| Configuration | Enabled through Viva Insights admin center settings | Configured through Microsoft 365 admin center or PowerShell |
| Permissions model | Uses existing Microsoft 365 permissions plus Viva Insights admin roles | Requires separate connector permissions and ACL mapping |
| Update frequency | Near real time for Graph data, daily for Viva metrics | Configurable from minutes to days depending on connector |
Copilot in Viva Insights uses only internal Microsoft 365 signals. Graph Connectors extend Copilot to external data sources. If you need Copilot to query data from a CRM or HR system outside Microsoft 365, you must configure a Graph Connector. The two systems are complementary. For most Viva Insights scenarios, the built-in signal sources are sufficient.
You now know which signal sources Copilot in Viva Insights uses and how to configure them. Start by enabling Microsoft 365 Graph data and verifying organizational hierarchy in Azure AD. Next, confirm that Viva Insights advanced metrics are active. For advanced scenarios, consider uploading additional HR fields or connecting a Graph Connector to bring external data into Copilot responses.