Microsoft Viva Insights vs eMonitor: Why Collaboration Metadata Is Not Enough

What Viva Insights Tracks — and What It Does Not

Understanding the exact scope of Viva Insights is the first step in deciding whether you need an additional tool alongside it. The list of what Viva Insights covers is genuinely useful. The list of what it does not cover is equally important — and often surprises M365 administrators who assumed Microsoft was providing comprehensive workforce visibility.

What Microsoft Viva Insights Does Track

• Meeting time: Total hours per week spent in calendar meetings, including back-to-back meeting rates and long meeting frequency (defined by Microsoft as meetings over one hour).
• Email analytics: Volume of emails sent and received, after-hours email activity, and average response times to colleagues.
• Focus time: Uninterrupted two-hour blocks with no meetings or Teams activity, which Viva Insights can automatically schedule and protect in users' calendars via MyAnalytics (now part of Viva Insights).
• Network and collaboration connections: Which colleagues each employee interacts with most frequently, collaboration diversity scores, and organizational network analysis at the aggregate level.
• Wellbeing signals: After-hours work trends, weekend email activity, and overwork risk indicators derived from M365 activity timestamps.
• Manager one-on-one rates: Frequency of calendar-based one-on-one meetings between managers and their direct reports.
• Teams-specific signals: Teams call time, channel participation, and chat activity volume (metadata only — not content).

What Microsoft Viva Insights Does Not Track

• Application usage: Viva Insights has no visibility into which applications are open on an employee's device at any point. A developer who is in a focused coding session and a developer who is streaming video both appear identical to Viva Insights if they have no scheduled meetings.
• Website visits: Browsing activity — including time spent on social media, news sites, or non-M365 web applications — is entirely outside Viva Insights' scope.
• Idle and active time: Viva Insights cannot detect whether an employee's device is actively being used or sitting idle. A two-hour focus block appears as protected time whether the employee is coding, reading, or away from their desk entirely.
• Screen activity: No screenshots, screen recordings, or visual verification of work output are available through Viva Insights.
• File operations: File creation, editing, deletion, and access — outside of SharePoint metadata — are not tracked by Viva Insights.
• Non-M365 application time: Time spent in tools like Slack, Figma, VS Code, Salesforce, or any application outside the Microsoft 365 ecosystem is invisible to Viva Insights.
• Keystroke and mouse activity: Device-level engagement signals are outside Viva Insights' design scope entirely.

Microsoft documents these boundaries publicly in the Viva Insights privacy guide (see Sources section below). The gaps are not limitations in the traditional sense — they are architectural decisions reflecting Microsoft's deliberate choice to build a collaboration analytics tool rather than an endpoint monitoring platform.

The Endpoint Visibility Gap That Viva Insights Leaves Open

Microsoft Viva Insights answers a specific set of questions well: Are employees overloaded with meetings? Are they sending email after hours? Do they have enough uninterrupted time to do focused work? Are managers meeting regularly with their reports? These are legitimate questions with real impact on employee wellbeing and collaboration efficiency.

But managers overseeing remote and hybrid teams face a different set of questions that Viva Insights cannot answer. Consider this scenario: a 200-person software company has deployed M365 E5, which includes Viva Insights. Their remote developers are showing healthy collaboration patterns — meeting load is reasonable, focus time blocks are being protected, and after-hours activity is low. The Viva Insights data looks good.

What the data cannot tell them: whether those developers are actually writing code during focus time, which applications they are using, how often they step away from their desks, or whether any of them are spending significant portions of their workday on non-work activities. A developer with three hours of scheduled focus time appears identical in Viva Insights whether they spend those hours in VS Code or watching YouTube.

The Four Questions Viva Insights Cannot Answer

• What are employees actually doing during work hours? Application usage data answers this directly. Viva Insights has no access to this layer.
• How much of the workday is genuinely active versus idle? Idle time detection at the device level requires endpoint monitoring. Viva Insights derives activity signals from M365 metadata only.
• Are remote employees present and working during their scheduled shifts? A clock-in system or activity-based presence detection addresses this. Viva Insights does not have this capability.
• What is happening on the device outside the Microsoft 365 ecosystem? Teams and Outlook data represent a fraction of a typical knowledge worker's digital environment. The rest — browser activity, local applications, file system operations — is invisible to Viva Insights.

These are not niche edge cases. For any organization with significant remote or hybrid headcount, these questions are central to understanding workforce productivity. The absence of endpoint visibility in Viva Insights is not a flaw — it is a deliberate boundary. The question is whether your organization needs visibility beyond that boundary, and for most teams managing remote workers, the answer is yes.

Real-World Use Case: M365 Enterprise With Remote Teams

A mid-sized IT services firm with 350 employees moves to a fully remote model and deploys M365 E5 across the organization. Viva Insights shows healthy collaboration metrics: average meeting load is 14 hours per week (within Microsoft's recommended range), after-hours activity is below the team average, and focus time is being scheduled and protected. The HR leadership team is pleased with the data.

Six months later, a project manager notices that several team members' deliverable output has declined significantly despite their Viva Insights profiles showing normal collaboration patterns. The PM escalates to the CTO. Without endpoint visibility, the investigation relies entirely on output quality and one-on-one conversations — a slow, subjective process that takes three weeks to reach any conclusions.

The Same Scenario With eMonitor Deployed Alongside Viva Insights

eMonitor's application tracking data surfaces the discrepancy within the first week: two team members on the underperforming project are showing 60 to 80 minutes per day of idle time during core hours, and their productive application time (IDE, project management tools, document editors) is significantly lower than the team average for the same roles. A third team member shows high application activity but predominantly in non-work applications.

The manager now has specific, objective data to bring to a support conversation with the team rather than a vague sense that "something isn't right." The resolution path is faster, fairer, and less awkward for everyone. The employees can see their own data through eMonitor's employee-facing dashboard, so the conversation starts from a shared understanding of the facts rather than a manager's subjective impression.

This scenario represents the core value of pairing Viva Insights with eMonitor: Viva Insights confirms that collaboration patterns are healthy at the structural level, while eMonitor provides the endpoint data needed to understand actual work activity when output signals suggest a problem.

Running eMonitor Alongside Microsoft 365

eMonitor operates independently of Microsoft 365. It does not require any M365 permissions, API connections, or changes to your Azure AD tenant configuration. This independence is an architectural advantage: eMonitor's data does not pass through Microsoft's infrastructure, there are no licensing dependencies, and adding or removing eMonitor has no impact on your M365 configuration.

Deployment in M365 Environments

The eMonitor desktop agent installs on Windows, macOS, Linux, and Chromebook. For enterprise rollouts across M365-managed devices, IT administrators can distribute the agent via Microsoft Intune, Group Policy, or any third-party MDM solution. Most organizations complete full deployment for a 500-user team within a single working day. There is no need to configure Azure AD integration or modify M365 admin settings.

Identity and User Management

eMonitor manages users independently of Azure AD. IT administrators provision employees in the eMonitor portal, which can be done manually or via bulk import (CSV upload). For organizations that prefer to link eMonitor user records to their Azure AD directory, eMonitor supports SSO authentication through standards-compliant identity providers, including Azure AD-backed SSO. This allows employees to sign in to the eMonitor portal using their M365 credentials without requiring separate passwords.

Teams Notifications

eMonitor can deliver manager alerts and daily activity summaries to Microsoft Teams channels through webhook integration. When a monitored employee exceeds a configured idle threshold or a productivity score drops below a set level, the alert can be routed directly to the relevant Teams channel alongside the manager's regular operational notifications. This keeps monitoring alerts in the same communication environment M365 teams already use, reducing tool-switching for managers.

Data Separation and Privacy

Because eMonitor does not read M365 signals, user data in eMonitor is separate from the data Microsoft processes through Viva Insights. This separation is relevant for organizations operating under GDPR or other data protection frameworks: the two data streams are processed independently, each with their own lawful basis and retention policies. eMonitor's monitoring data is stored in eMonitor's infrastructure (not Microsoft's), and administrators control retention periods, access levels, and deletion policies independently. For organizations using Workday alongside their M365 stack, see our coverage of Workday integration for workforce data.

eMonitor's Full Capability Set for M365 Enterprises

Beyond filling the endpoint visibility gap left by Viva Insights, eMonitor provides a comprehensive workforce monitoring platform that addresses multiple operational needs. The following capabilities are available within eMonitor and are absent from Viva Insights by design.

Productivity Classification Engine

eMonitor classifies each application and website as productive, non-productive, or neutral based on role-specific rules configured by administrators. A developer's time in GitHub is productive. A customer service agent's time in the CRM is productive. Time on social media or streaming services during work hours is non-productive. Each role definition can be customized, and classification rules can be applied at the individual, team, or organization level. The result is a productivity score per employee per day that reflects actual work activity, not calendar-based time estimates.

Attrition Risk Detection

eMonitor's attrition prediction module analyzes behavioral and activity signals to identify employees at risk of disengagement or departure. Signals include sustained drops in productivity scores, increased idle time, reduced application diversity (using fewer tools as engagement falls), and work-life balance indicators like extended overtime patterns. These signals complement Viva Insights' collaboration data: an employee whose meeting participation and email response times look normal in Viva Insights may still show attrition risk signals at the endpoint level that eMonitor surfaces weeks before a resignation occurs.

Data Loss Prevention

eMonitor's DLP module monitors file operations, USB device connections, and unauthorized web access. When an employee connects an unauthorized USB device, accesses a restricted domain, or deletes a significant number of files in a short period, eMonitor generates an alert and logs the event with full details. This capability is entirely outside Viva Insights' scope and complements Microsoft Purview (formerly Microsoft Information Protection) for organizations that need endpoint-level DLP alongside M365's content-level protection.

Automated Timesheets and Project Tracking

eMonitor generates timesheets automatically from activity data, with support for project and task-level time allocation. For billable teams, this means every minute of client work is captured and attributed correctly — regardless of whether it happens in a Microsoft 365 application. A consultant using a client-specific project management tool, a developer in a local IDE, or a designer in Adobe Creative Cloud all have their time tracked accurately. Viva Insights produces no timesheet data and has no project allocation capability.

Frequently Asked Questions