How to Troubleshoot Viva Insights (2026 Guide)
Why Viva Insights Stops Working , The Real Reasons
I've seen this exact scenario play out in IT support queues across dozens of organizations: someone opens Microsoft Teams on a Monday morning, clicks the Viva Insights app, and either gets a blank screen, a spinning loader that never stops, or a message that says "We're still processing your data." Their manager wants to see focus time metrics. Their HR team is waiting on wellbeing reports. And nothing loads.
Viva Insights problems are uniquely frustrating because the error feedback is almost always vague. Microsoft designed the product to be "set and forget," but when it breaks, finding the actual cause requires digging through license assignments, data processing pipelines, Azure Active Directory configurations, and Teams app permissions , often all at once.
Here's what actually goes wrong, in order of how often I see it in the field:
License mismatches are the number one culprit. Viva Insights Personal insights require at minimum a Microsoft 365 E1, E3, or E5 license, or a standalone Viva Insights add-on. If a user's license was recently changed, not fully provisioned, or is sitting in a "grace period" state, the dashboard will appear broken even though everything looks fine in the admin center. The service just silently fails.
Data processing delays are the second most common cause. After a license is assigned, Microsoft's backend needs between 24 and 72 hours, sometimes longer in large enterprise tenants, to process historical collaboration data. During this window, dashboards show incomplete or zero data. The system won't tell you it's still processing unless you know exactly where to look.
Exchange Online mailbox misconfiguration is a less obvious but very real issue. Viva Insights pulls calendar and email metadata directly from Exchange Online. If a user's mailbox is hosted on-premises in a hybrid setup, or if the mailbox provisioning is incomplete, insights data simply won't flow. The Teams app will open, but the metrics panels stay empty.
Tenant-level opt-out settings can block the entire service. An admin may have disabled Viva Insights at the organization level without realizing it affects individual users. There's no visible warning to end users, the app just doesn't work.
Teams app deployment issues, including cached app manifests, outdated app versions, and policy assignments in the Teams Admin Center, cause Viva Insights to fail to load properly even when licensing is perfect.
The good news: most of these are fixable in under 30 minutes once you know what to look for. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before diving into the full troubleshooting process, try this single sequence. It resolves about 60% of Viva Insights problems without any admin intervention, and you can do it yourself in under five minutes.
Step 1: In Microsoft Teams, click on the three dots (•••) in the left sidebar to open the app list. Find Viva Insights, right-click it, and select Unpin. Then go to Apps → Search for "Viva Insights", find the app, and re-add it. This forces Teams to pull a fresh copy of the app manifest and clears any cached state.
Step 2: Sign out of Teams completely. Don't just close the window, click your profile picture in the top-right corner, select Sign out, and wait for the app to close. Then reopen Teams and sign back in with your work account. This refreshes your authentication token, which expires after a set period and can silently break Viva Insights data requests.
Step 3: Clear the Teams desktop app cache. Close Teams fully (right-click the system tray icon and choose Quit), then open File Explorer and navigate to:
%appdata%\Microsoft\TeamsDelete the contents of the Cache, blob_storage, databases, GPUCache, IndexedDB, and Local Storage folders. Leave the folders themselves in place, just empty them. Restart Teams. This eliminates corrupted local data that can prevent the Viva Insights app from rendering.
Step 4: Open a browser and go directly to https://insights.viva.microsoft.com. If the web portal loads your data correctly but the Teams app still doesn't, the problem is isolated to the Teams client, not your license or data pipeline. If the web portal also fails, you've confirmed a license or backend issue that requires admin-level investigation.
insights.viva.microsoft.com while signed in with your work account. This bypasses browser extensions, cached credentials, and local group policy overrides. If it works there but nowhere else, you're dealing with a client-side problem, not a backend one. This single test saves an enormous amount of diagnostic time.
This is where I always start with enterprise escalations. Even when a user "has an E3 license," the specific Viva Insights service plan within that license might be disabled. Let me walk you through checking it properly.
Open a browser and go to https://admin.microsoft.com. Sign in with a Global Admin or User Admin account. In the left navigation, go to Users → Active users and find the affected user. Click on their name, then click the Licenses and apps tab.
Expand the license assigned to the user (e.g., "Microsoft 365 E3") by clicking the arrow next to it. Scroll down through the service plan list until you find entries related to Viva. The ones that must be toggled ON are:
- Microsoft Viva Insights
- Exchange Foundation (required for mailbox data access)
If either is toggled off, enable them and click Save changes. After saving, it typically takes 15–30 minutes for the change to propagate, but data processing can take up to 72 hours before you see populated metrics in dashboards.
You can also check and fix this in bulk using PowerShell if you're managing multiple affected users:
Connect-MsolService
Get-MsolUser -UserPrincipalName "user@yourdomain.com" | Select-Object -ExpandProperty Licenses | ForEach-Object { $_.ServiceStatus }Look for any service with ProvisioningStatus : Disabled in the Viva or Exchange rows. If the service plan shows as Disabled, re-enable it through the admin center UI. If it shows PendingActivation, wait 30 minutes and check again, provisioning is still in progress.
When it's working correctly, the user will see their focus time, meeting hours, and network data populate in the Viva Insights dashboard within 24–72 hours of the license being active.
Here's something that catches a lot of IT teams off guard: Viva Insights has a separate opt-in/opt-out toggle at the organization level that is completely independent of individual user license assignments. An admin can turn off Viva Insights for the entire tenant, and no individual user will ever see a clear error explaining why their dashboard doesn't work.
To check and correct this, go to https://admin.microsoft.com, then navigate to Settings → Org settings → Services tab. Scroll down and find Viva Insights in the list.
Click on it. You'll see a panel with toggle options including:
- Allow access to Viva Insights features in Microsoft 365
- Allow Microsoft to use anonymized data to improve Viva Insights models
Make sure the first toggle is enabled. If it's off, that's your answer, enable it, save the setting, and wait approximately 30–60 minutes for the change to propagate across the tenant.
There's also a separate Viva Insights admin portal that larger organizations use. Access it at https://insights.viva.microsoft.com/admin. From here, admins can see the overall tenant data processing status, manage analyst access, and confirm whether the organizational data upload (if used) is current. If your organization uses the Advanced Insights or Leader/Manager Insights features, check this portal for any data pipeline errors or stale upload warnings. A red status indicator here means backend data jobs have failed and need to be retriggered by an admin.
Once the tenant settings are confirmed correct, ask the affected users to wait up to one hour, then sign out and back into Teams before testing again.
Viva Insights is deeply dependent on Exchange Online. It reads calendar event metadata, email send/receive patterns (not content, just metadata), and out-of-office settings to build the insights it shows you. When that Exchange connection breaks, the Viva Insights dashboard goes blank or shows stale data.
I've seen this most often in hybrid Exchange environments where a user's mailbox is still on-premises, or where a mailbox was recently migrated and the cloud object hasn't fully synchronized. Here's how to verify.
Run the following in Exchange Online PowerShell to check mailbox status:
Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com
Get-Mailbox -Identity "user@yourdomain.com" | Select-Object DisplayName, RecipientTypeDetails, ExchangeGuid, WhenMailboxCreatedThe RecipientTypeDetails must show UserMailbox for Viva Insights to work. If it shows RemoteUserMailbox, the mailbox is on-premises and Viva Insights cannot process it properly without a full migration to Exchange Online.
Also check the mailbox provisioning date. If WhenMailboxCreated is very recent (within the last 48–72 hours), Viva Insights simply hasn't had time to ingest the data yet. There's nothing wrong, it just needs time.
If the ExchangeGuid is all zeros (00000000-0000-0000-0000-000000000000), the mailbox object is corrupted and needs to be re-provisioned. Open a ticket with Microsoft Support for this specific scenario, as it requires backend tenant operations.
After confirming the mailbox looks correct, verify the user's calendar permissions are not overly restrictive. In Outlook, go to File → Office Account → Manage Settings and confirm that Viva Insights has not been manually blocked from accessing calendar data.
The Viva Insights Teams app has its own deployment and permission policy chain. Even if licensing is perfect and the backend is healthy, a misconfigured Teams policy can prevent the app from showing up or loading correctly for specific users or groups.
Sign into the Teams Admin Center at https://admin.teams.microsoft.com. Navigate to Teams apps → Manage apps. In the search bar, type "Viva Insights." Click on the app to open its settings panel.
Check the Status field. It must be set to Allowed. If it shows Blocked, click the Status toggle to enable it. This single setting controls whether the app is available in the entire tenant, regardless of user-level policies.
Next, navigate to Teams apps → Setup policies. Click on the policy assigned to the affected users (usually Global (Org-wide default) unless your org uses custom policies). Scroll to the Installed apps section. If Viva Insights is not listed there, click Add apps, search for Viva Insights, and add it. This pushes the app automatically to users covered by that policy, removing the need for manual installation.
For users who are assigned a custom app permission policy, go to Teams apps → Permission policies, find the policy, and confirm that Microsoft apps are set to Allow all apps or that Viva Insights is explicitly listed in the allowed apps list.
After making policy changes, expect propagation to take anywhere from 30 minutes to 4 hours. Ask users to fully quit and restart Teams before retesting. In my experience, policy changes in Teams Admin Center are one of the quieter failure modes, they break silently and fix silently, so patience is required after making changes here.
Sometimes Viva Insights isn't broken at the backend or admin level, the user's own personal settings are misconfigured, or the notification preferences got corrupted during an update. I know this sounds simple, but I've seen it stump people for days.
In Microsoft Teams, open the Viva Insights app and click on the Settings gear icon (usually in the top-right corner of the app). Review the following toggles:
- Insights notifications, if disabled, users won't receive digest emails or Teams nudges
- Focus plan, if the focus plan setup is incomplete or paused, focus time metrics won't display
- Quiet time, if overly restrictive schedules are set here, they can interfere with how insights surface in Teams
Scroll to the bottom of the Settings panel and look for a Reset all settings option or toggle individual features off and back on. This triggers a fresh configuration sync with the Viva Insights backend.
For the Outlook add-in version of Viva Insights (the "Insights" sidebar that appears in Outlook on the web and Outlook desktop), open Outlook, click the Insights button in the ribbon or from Home → Insights, then click the settings gear inside the panel. Toggle off and re-enable each category.
If the Outlook Insights add-in is missing entirely, it may have been disabled. In Outlook desktop, go to File → Options → Add-ins. In the "Manage" dropdown at the bottom, select COM Add-ins and click Go. Look for Microsoft Viva Insights. If it's unchecked, check it and click OK. Then restart Outlook.
If it's listed under Disabled Application Add-ins, you'll need to enable it via Manage: Disabled Items from the same dropdown. Select the Viva Insights entry and click Enable. Restart Outlook to apply.
Advanced Troubleshooting for Viva Insights
If the five steps above haven't resolved the issue, you're dealing with something that requires deeper investigation. Here's where I go when the standard fixes don't work.
Group Policy Interference
In domain-joined environments, Group Policy Objects can block Viva Insights in several ways. The most common is a policy that restricts Office add-ins across the board. Check your GPO configuration at the following path:
User Configuration\Administrative Templates\Microsoft Outlook [version]\Miscellaneous\
→ "List of managed add-ins"If this policy is enabled and Viva Insights (ucaddin.dll or the ProgID MicrosoftViva.InsightsAddin) is not in the allowed list, the add-in will be silently disabled every time Outlook starts. Add it with value 1 (enabled, user cannot disable) or 2 (enabled, user can disable).
Azure AD Conditional Access Blocking Data Access
Conditional Access policies that restrict access to Microsoft Graph API can prevent Viva Insights from pulling collaboration data. In the Azure portal (https://portal.azure.com), go to Azure Active Directory → Security → Conditional Access → Sign-in logs. Filter by the affected user and look for any blocked sign-in attempts to the application "Microsoft Viva Insights" (App ID: 0ef3db4a-a278-4a5c-a9bb-e87c45bc7617). If you see failure events, trace back to which Conditional Access policy is blocking it and evaluate whether an exclusion is appropriate.
Event Viewer Analysis for Teams App Failures
For Teams client crashes or failures specifically when opening Viva Insights, the Windows Event Viewer often holds useful diagnostic data. Open Event Viewer (Win+R, type eventvwr.msc), then navigate to Windows Logs → Application. Filter for Event ID 1000 (application crash) with source Teams.exe. Event ID 1026 (.NET Runtime errors) can also appear when the Teams app encounters an unhandled exception loading a web-based app like Viva Insights.
Checking Data Processing Status via PowerShell
Advanced Insights admins can use the following PowerShell command after connecting to the Viva Insights module to check the status of organizational data processing jobs:
Install-Module -Name Microsoft.Graph -Scope CurrentUser
Connect-MgGraph -Scopes "InsightsApp.Read.All"
Get-MgUserInsight -UserId "user@yourdomain.com"A null or empty response here confirms the Graph API is not returning insights data for that user, pointing to either a license issue or a data processing backlog on Microsoft's side. Cross-reference with the Microsoft 365 Service Health Dashboard at https://admin.microsoft.com/adminportal/home#/servicehealth, specifically look for incidents tagged VIV (Viva Insights service incidents).
Prevention & Best Practices
I've worked with enough organizations to know that most Viva Insights outages are preventable. The ones that aren't usually resolve themselves within 72 hours. Here's how to make sure you're in the first group.
Standardize your onboarding checklist. Every new user getting a Microsoft 365 license should have their Viva Insights service plan verified within 24 hours of account creation. Build this into your onboarding runbook. A five-minute license check at provisioning time prevents a three-hour support ticket two weeks later when a manager complains their team's wellbeing scores aren't showing up.
Monitor the Microsoft 365 Service Health Dashboard proactively. Subscribe to email alerts for incidents tagged with VIV (Viva Insights) and EXO (Exchange Online). Go to https://admin.microsoft.com/adminportal/home#/servicehealth, click Preferences, and enable email notifications for these workloads. When there's a known Microsoft-side outage, you'll know before your users start raising tickets.
Don't change license assignments during business hours. License changes trigger data reprocessing jobs that can temporarily surface incomplete dashboards. Schedule license modifications during off-hours maintenance windows to minimize user impact. This is especially true for large bulk changes affecting dozens or hundreds of users at once.
Keep Teams updated. Viva Insights receives frequent updates through the Teams update mechanism. Running an outdated Teams client is a common cause of partial rendering failures and feature incompatibilities. In Teams, go to Settings → About → Check for updates and make sure clients are on the latest ring-appropriate version.
- Pin the Viva Insights service health page to your IT team's browser bookmarks bar, check it first whenever users report issues
- Use the Microsoft 365 admin center's Adoption Score feature to baseline Viva Insights usage before an incident so you have a comparison point after recovery
- Create a saved PowerShell script that checks Viva service plan status for any user UPN, it takes 30 seconds to run and cuts license diagnostic time dramatically
- Document your tenant-level Viva Insights settings (org opt-in status, analyst permissions, data retention settings) in your IT runbook, these are invisible to end users and easy to forget
Frequently Asked Questions
Why does Viva Insights say "We're still processing your data" and never load?
This message almost always means one of two things: the license was very recently assigned (within the past 24–72 hours) and the data pipeline hasn't finished yet, or the tenant-level opt-in setting for Viva Insights is disabled. Check https://admin.microsoft.com → Settings → Org settings → Viva Insights and confirm the service is enabled. If it was already enabled and more than 72 hours have passed since license assignment, check the Microsoft 365 Service Health Dashboard for any active VIV incidents. In rare cases, a support ticket to Microsoft is needed to manually trigger a data reprocessing job for a specific user.
Viva Insights works in my browser but not in the Teams app, what gives?
This is almost always a Teams client caching issue or an app policy problem. Start by clearing your Teams cache: close Teams completely, navigate to %appdata%\Microsoft\Teams, and delete the contents of the Cache and Local Storage folders. If that doesn't fix it, go to the Teams Admin Center and check that Viva Insights isn't blocked under Manage apps and that your app setup policy includes it in the installed apps list. Also make sure you're running the latest version of Teams, go to your profile picture in Teams and click Check for updates.
My Viva Insights data looks wrong, it shows way fewer meeting hours than I actually had. Why?
Viva Insights counts meetings differently than you might expect. It only counts meetings where you were an accepted attendee and the meeting was on your primary calendar. Tentative accepts, declined meetings, and meetings on secondary or shared calendars are excluded. Additionally, meetings over 8 hours long are automatically excluded as outliers. If your Exchange mailbox was recently migrated or your calendar data is stored in a non-primary calendar (common with third-party scheduling tools like Calendly), those events won't count. There's also a known delay of up to 7 days for recent data, the last week of calendar activity may not yet be fully processed.
Can my manager or employer see my personal Viva Insights data?
Personal Insights data, the focus time, meeting hours, and wellbeing suggestions you see in your own dashboard, is completely private and visible only to you. Microsoft built this privacy guarantee into the product architecture: personal insights are processed and displayed only for the individual user. Manager and Leader insights, which appear in a separate section of the admin portal, show only aggregated and de-identified data for teams of 10 or more people, with no individual-level breakdowns. Your employer cannot use Viva Insights to see your individual productivity metrics, calendar details, or email behavior patterns.
Viva Insights notifications stopped showing up in Teams and email, how do I turn them back on?
Open the Viva Insights app in Teams and click the gear/settings icon. Make sure Insights notifications is toggled on. Then check your Teams notification settings: click your profile picture → Settings → Notifications, scroll down to find Viva Insights, and make sure notifications aren't set to "Off." For email digests specifically, go to https://insights.viva.microsoft.com, click your profile, then Settings, and verify that email subscriptions for your weekly digest are enabled. Also check your Junk/Spam folder in Outlook, Viva Insights digest emails sometimes get caught by overly aggressive spam filters, particularly in organizations using third-party email security gateways.
We bought Viva Insights licenses but the admin portal at insights.viva.microsoft.com shows no data at all, what do we check?
The most common cause in a brand-new deployment is that the Viva Insights admin hasn't been assigned yet or the initial organizational data setup hasn't been completed. Go to https://admin.microsoft.com, navigate to Settings → Org settings → Viva Insights, and verify that at least one user has been assigned the Insights Administrator role. Then open the Viva Insights admin portal and look for an initial setup wizard or data configuration prompt, for Advanced Insights, you need to upload an organizational data file (a CSV with employee attributes like role, department, and manager hierarchy) before any analyst-facing dashboards will populate. If no organizational data has been uploaded, the portal will remain empty regardless of how long you wait.