How to Troubleshoot Viva Pulse: Full Fix Guide
Why Viva Pulse Troubleshooting Is So Frustrating
I've seen this exact situation play out on dozens of tenant deployments: a manager logs into Microsoft Teams, opens the Viva Pulse app, tries to send a survey to their team , and either the app won't load, the send button does nothing, or respondents report they never got the invitation email. Meanwhile, the error message on screen is something uselessly vague like "Something went wrong" or, even worse, complete silence with a spinning loader that never resolves.
Viva Pulse sits at an awkward intersection of several Microsoft services. It needs Microsoft Teams to surface the UI, Entra ID (formerly Azure Active Directory) to handle identity and permissions, Microsoft 365 Groups or Teams membership to determine who gets surveyed, and Exchange Online to deliver invitations. When any one of those underlying services has a hiccup , or when a license isn't provisioned correctly, Viva Pulse is the one that goes dark, and you're left guessing which layer broke.
The most common triggers I see in real deployments are:
- License assignment gaps. Viva Pulse requires a Microsoft Viva Suite or Viva Workplace Analytics and Employee Feedback license. If IT provisioned Microsoft 365 E3 or E5 but skipped the Viva add-on, the app simply won't function, it just won't tell you that clearly.
- Entra ID app consent not granted. The Viva Pulse enterprise application in Entra ID needs tenant-wide admin consent. Without it, individual users hit silent authentication failures.
- Teams app policy blocking deployment. If your tenant uses managed app permission policies, Viva Pulse may be blocked at the Teams admin level before it ever reaches users.
- Exchange Online mail flow blocks. Survey invitations are sent from
noreply@email.teams.microsoft.com. If your transport rules or spam filters reject that domain, respondents never see the survey link. - Privacy and minimum response threshold not met. Viva Pulse protects anonymity by withholding results until a minimum number of responses are collected (default: 5). Managers waiting on results think the tool is broken when really it's working exactly as designed.
Microsoft's own error messages don't help here because Pulse is a relatively new addition to the Viva family, the error surfacing is still immature compared to, say, SharePoint or Exchange. You're often flying blind until you know exactly where to look.
This guide walks you through every layer, from a 60-second license check all the way to PowerShell-level diagnostics and Group Policy inspection. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go deep on PowerShell or admin portals, run through this 90-second check. It resolves about 40% of Viva Pulse issues I encounter in the field.
Step 1, Clear the Teams cache. Open Task Manager, kill all Microsoft Teams processes, then delete the contents of %appdata%\Microsoft\Teams\Cache and %appdata%\Microsoft\Teams\Application Cache\Cache. Relaunch Teams.
Step 2, Confirm your license in the Microsoft 365 admin center. Go to admin.microsoft.com → Users → Active users → [your user] → Licenses and apps. Look for either "Microsoft Viva Suite" or "Viva Workplace Analytics and Employee Feedback" in the licensed products list. If it's not there, that's your culprit right now, stop here, assign the license, wait 15–30 minutes for propagation, and try again.
Step 3, Check the Viva Pulse app status in Teams Admin Center. Navigate to teams.microsoft.com/admin → Teams apps → Manage apps, search for "Viva Pulse," and confirm its status shows Allowed. If it reads Blocked, click the app name, toggle it to Allowed, and give Teams 10–15 minutes to push the change.
Step 4, Try the web version. Open a browser and go to pulse.viva.cloud.microsoft. If Pulse works there but not inside Teams, the issue is isolated to the Teams desktop client (cache or client version). If it fails in both places, the problem is back-end, license, consent, or service health.
Step 5, Check Microsoft 365 Service Health. Go to admin.microsoft.com → Health → Service health and look for any active advisories under "Microsoft Viva" or "Microsoft Teams." Microsoft has had several Viva Pulse service degradations in 2025–2026 that caused widespread send/receive failures with no user-facing error. If there's an active incident, all you can do is wait it out.
noreply@email.teams.microsoft.com. Check your mail flow rules before spending an hour in the Pulse admin settings.
The Microsoft 365 admin center UI is good for checking one user at a time, but if you need to confirm license assignment across a whole department, or if you suspect the license was assigned but not activated, PowerShell gives you the definitive answer fast.
Open PowerShell as Administrator and connect to Microsoft Graph:
# Install module if needed
Install-Module Microsoft.Graph -Scope CurrentUser
# Connect with required scopes
Connect-MgGraph -Scopes "User.Read.All", "Directory.Read.All"
# Check a specific user's licenses
Get-MgUserLicenseDetail -UserId "user@yourdomain.com" | Select-Object SkuPartNumberIn the output, look for VIVA (Viva Suite) or WORKPLACE_ANALYTICS_FEEDBACK. If neither appears, the user genuinely doesn't have a Pulse license. Assign it from the admin center or via:
# Get the SKU ID for Viva Suite
$sku = Get-MgSubscribedSku | Where-Object { $_.SkuPartNumber -eq "VIVA" }
# Assign to user
Set-MgUserLicense -UserId "user@yourdomain.com" `
-AddLicenses @{SkuId = $sku.SkuId} `
-RemoveLicenses @()After assignment, licensing changes typically propagate within 15–30 minutes for most tenants, though I've seen domain-joined hybrid environments take up to 2 hours. You can force a token refresh on the user's machine by running dsregcmd /forcerecovery from an elevated command prompt.
If the license shows as assigned but Pulse still won't load, the issue is almost certainly an Entra ID admin consent problem, move to Step 2.
This is the single most-missed step in Viva Pulse deployments. Even when licenses are assigned and Teams policies are correct, individual users will hit silent authentication failures if the Viva Pulse enterprise application hasn't been granted tenant-wide admin consent in Entra ID.
Here's how to check and fix it:
Go to entra.microsoft.com → Applications → Enterprise applications. In the search box, type Viva Pulse. Click the application when it appears.
Navigate to Permissions → Admin consent. You'll see a list of permissions. If the "Status" column shows any permission with a yellow warning icon or if the "Granted for [Tenant Name]" column is blank, admin consent has not been fully granted.
To grant it, click Grant admin consent for [Your Tenant Name]. A pop-up authentication dialog will appear, complete it with Global Administrator credentials. You should see all permissions flip to a green checkmark with "Granted for [Tenant]."
If the Viva Pulse enterprise app doesn't appear in your list at all, it means no user in your tenant has attempted to authenticate to it yet, so the app registration was never created. In that case, use this direct consent URL (replace YOUR_TENANT_ID with your actual tenant GUID from Entra ID → Overview):
https://login.microsoftonline.com/YOUR_TENANT_ID/adminconsent?client_id=906ac929-1cd9-45be-9b47-5ee1f78bb825Open that URL while logged in as a Global Administrator. Accept the permissions dialog. The app will now be registered and consented in your tenant. Users who were previously stuck will typically see the fix take effect within 5–10 minutes, no client restart required.
If your organization manages Teams with custom app permission policies, which is very common in enterprise and education tenants, Viva Pulse might be licensed correctly and consented correctly, but still completely invisible to users because the Teams app policy blocks it before it loads.
Go to admin.microsoft.com → Teams admin center (or navigate directly to admin.teams.microsoft.com). In the left nav, go to Teams apps → Permission policies.
You'll see one or more policies listed. Click the policy assigned to the affected users. Under Microsoft apps, check whether it's set to Allow all apps or Allow specific apps and block all others. If it's the latter, Viva Pulse needs to be in the allowed list explicitly.
To add it: click Allow apps, search for "Viva Pulse," select it, and click Allow. Save the policy.
Also check Teams apps → Setup policies. If Viva Pulse should be pinned to the Teams left rail for your users, you can add it here under Pinned apps → Add apps → search Viva Pulse. This isn't required for functionality, but it dramatically reduces "I can't find it" support tickets.
Policy changes in Teams Admin Center can take anywhere from 5 minutes to 4 hours to propagate to all users, depending on tenant size. Tell affected users to fully quit and relaunch Teams, not just minimize it. On Windows, right-click the Teams icon in the system tray and choose Quit, then relaunch from Start. A simple window close leaves the Teams background process running and the policy won't refresh.
This one baffles managers constantly. They send a Pulse survey, their direct reports never receive the invitation email, and they assume the tool is broken. The tool is usually fine. The problem is email delivery.
Viva Pulse sends survey invitations from the domain email.teams.microsoft.com, specifically from addresses like noreply@email.teams.microsoft.com. If your Exchange Online transport rules, anti-spam policies, or third-party email security gateway (Proofpoint, Mimecast, etc.) flags this domain, the emails silently disappear before users ever see them.
Start your diagnosis in the Exchange admin center. Go to admin.exchange.microsoft.com → Mail flow → Message trace. Enter the recipient's email address, set the time range to cover when the survey was sent, and run the trace. Look for messages from the email.teams.microsoft.com domain. If you see a status of FilteredAsSpam, Quarantined, or Failed, that's your answer.
The fix: create a safe sender or bypass rule. In Exchange admin center → Mail flow → Rules, create a new rule:
Rule name: Allow Viva Pulse Invitations
Apply this rule if: The sender domain is 'email.teams.microsoft.com'
Do the following: Set the spam confidence level (SCL) to -1
Bypass spam filteringIf you use Proofpoint or Mimecast, you'll need to allowlist email.teams.microsoft.com and the IP ranges published in Microsoft's official IP range list (specifically the "Teams" service tag). Check your third-party gateway's admin console under Safe Senders or Permitted Senders.
After the rule is in place, resend the Pulse survey from the manager's account. New invitations should arrive within a few minutes. Previously sent surveys won't retroactively deliver, they'll need to be resent.
This is the most common "broken" report that turns out to be expected behavior. A manager sends a 10-question Pulse survey to 8 team members. Four people respond. The manager logs in to see results and gets a message saying results aren't available yet, or sees a grayed-out dashboard. They open a support ticket convinced something is wrong. Nothing is wrong.
Viva Pulse has a built-in anonymity protection system that requires a minimum number of responses before results are shown. The default threshold is 5 responses. Until that minimum is met, the results page shows nothing, to protect individual respondents from being identified in small teams.
As an admin, you can view and adjust this threshold. Go to pulse.viva.cloud.microsoft → Admin settings → Privacy settings. You'll see the current minimum response threshold. The minimum you can set it to is 3, Microsoft doesn't allow lower than that, by design, and I agree with that call.
If the threshold genuinely is a problem for your small team, the practical workaround is to expand the survey audience. Include more people, adjacent team members, cross-functional stakeholders, so you're more likely to hit 5+ responses organically.
There's a separate scenario where results disappear even after the threshold is met: the survey expiry window. Pulse surveys expire after a configurable period (default: 2 weeks). After expiry, the survey closes and results are locked, but they're still viewable in the Past pulses section of the Pulse app. If a manager thinks results vanished, have them click Sent pulses → Past in the Pulse UI. The results are there; they're just archived.
For IT admins troubleshooting survey configuration issues in bulk, the Viva Pulse admin API is accessible via Microsoft Graph. Use the endpoint GET /beta/employeeExperience/engagementAsyncOperations to query survey states programmatically if you're managing large-scale deployments.
Advanced Troubleshooting for Viva Pulse
Diagnosing via the Microsoft 365 Admin Diagnostics Tool
Microsoft quietly added a self-service diagnostic tool to the admin center that covers Viva Pulse specifically. In admin.microsoft.com, click the ? (Help) icon in the top-right corner, type "Viva Pulse" in the search box, and look for the diagnostic option labeled Run diagnostic: Viva Pulse. Enter the affected user's UPN and let it run. It checks license, consent, Teams policy, and service health in one sweep and gives you an actionable result, often faster than manual inspection.
Event Viewer and Sign-In Log Analysis
For Entra ID authentication failures that aren't obvious from the surface, pull the sign-in logs. In entra.microsoft.com → Monitoring → Sign-in logs, filter by User, set the Application to Viva Pulse, and look at the Status column. A failure with error code AADSTS700016 means the application wasn't found in the tenant, you haven't granted admin consent yet. Error code AADSTS65001 means consent is needed for specific permissions. Error code AADSTS53000 points to a Conditional Access policy blocking the app.
Conditional Access Policy Conflicts
If your tenant has Conditional Access policies enforcing device compliance, MFA, or location-based restrictions, Viva Pulse can get caught in those policies. Go to entra.microsoft.com → Protection → Conditional Access → Policies. Look for any policy targeting "All cloud apps" or specifically listing Viva Pulse. Check whether the policy requires compliant devices or specific network locations. Users on unmanaged devices or working from unexpected locations will fail silently.
The fix is to either add a Viva Pulse exclusion to the restrictive policy, or (better) create a specific policy for Viva Pulse that's appropriately scoped. Don't just disable CA policies wholesale, talk to your security team first.
Network Proxy and Firewall Endpoints
In corporate environments with web proxies or strict firewall rules, Viva Pulse requires access to several Microsoft endpoints. The ones I most commonly see blocked are:
*.viva.cloud.microsoft
pulse.viva.cloud.microsoft
*.teams.microsoft.com
*.microsoftonline.com
*.office.netIf your proxy uses SSL inspection, add these to your inspection bypass list, deep packet inspection of Microsoft authentication traffic breaks OAuth flows in ways that produce confusing symptoms like "app loads but won't let me log in" or "the survey sends but data never appears."
Hybrid Identity and AD Sync Issues
If your organization uses Microsoft Entra Connect (formerly Azure AD Connect) to sync on-premises Active Directory accounts, Viva Pulse authentication depends on those synced attributes being clean. Run Start-ADSyncSyncCycle -PolicyType Delta on your Entra Connect server and check the Synchronization Service Manager for any sync errors on affected user accounts. The most common culprits are mismatched UPNs, duplicate proxy addresses, or the msExchRecipientTypeDetails attribute conflicting with cloud-only settings.
If you've confirmed correct licensing, granted admin consent, verified Teams app policies, ruled out mail flow blocks, and Viva Pulse still won't function, escalate. Specifically: if Entra ID sign-in logs show successful authentications but Pulse still shows errors, that points to a back-end service provisioning issue that only Microsoft can resolve on their side. Open a support ticket at Microsoft Support and include your tenant ID, the affected user's UPN, the exact error message or behavior, a screenshot of the sign-in logs, and a timestamp of when the failure occurred. The more specific you are, the faster Tier 2 can dig into the back-end telemetry.
Prevention & Best Practices for Viva Pulse
Most Viva Pulse issues aren't bugs, they're configuration gaps that open up when the app is first deployed or when organizational changes happen (new hires, license reassignments, policy updates). Tightening your deployment process eliminates almost all of the repeat tickets I see in mature tenants.
Run a pre-deployment checklist before rolling out Pulse. Before announcing Viva Pulse to any business unit, confirm all four pillars: license assigned, Entra ID admin consent granted, Teams app policy set to Allow, and Exchange Online transport rules permitting email.teams.microsoft.com. Skipping even one of these creates a wave of confusing day-one support tickets. Document this checklist in your internal IT runbook.
Set up a dedicated Viva Pulse test account. Keep a licensed test user (something like viva-test@yourdomain.com) that you can use to quickly validate end-to-end Pulse functionality, sending a survey, receiving the invitation email, submitting a response, and viewing results, whenever you make tenant-level changes. This takes about 5 minutes to verify and saves hours of reactive troubleshooting later.
Monitor license assignments during organizational changes. When employees change departments, managers, or roles, license reassignments sometimes drop Viva add-ons accidentally, especially if IT uses group-based licensing and the user moves between Entra ID groups. Set up a Microsoft 365 admin center alert or a Power Automate flow that flags when Viva Suite licenses are removed unexpectedly.
Educate managers on the anonymity threshold. At least 30% of Viva Pulse "it's broken" reports I've seen are actually managers confused about the 5-response minimum. A single internal email explaining how the threshold works, sent when you first deploy Pulse, eliminates a huge category of support noise. Frame it as a feature ("your team's responses stay private"), not a limitation.
Keep the Teams client updated. Viva Pulse functionality depends on Teams client versions. Older Teams clients, especially Windows clients that haven't been updated in 3+ months, sometimes render the Pulse tab incorrectly or fail to load the app frame entirely. Enable automatic Teams updates in your organization or push updates via your endpoint management tool (Intune, SCCM) on a monthly cadence.
- Bookmark admin.microsoft.com → Health → Service health, check it first whenever Pulse behavior changes suddenly across multiple users simultaneously.
- Enable the Viva Pulse app in your Teams global (org-wide default) app permission policy so new users don't need individual policy exceptions.
- Add
email.teams.microsoft.comto your Exchange Online safe senders list as part of your standard Microsoft 365 onboarding runbook, before Pulse is even deployed. - Schedule a quarterly review of Viva add-on license assignments to catch accidental removals before they become user-facing problems.
Frequently Asked Questions
Why does Viva Pulse say "Something went wrong" every time I try to open it in Teams?
This generic error almost always comes down to one of three things: a missing Viva license, missing Entra ID admin consent, or a Teams app permission policy blocking the app. Start by checking your license in admin.microsoft.com → Users → Active users → Licenses and apps, look for Viva Suite or Viva Workplace Analytics and Employee Feedback. If the license is there, go to entra.microsoft.com → Enterprise applications → Viva Pulse → Permissions and confirm admin consent has been granted. If both look fine, check Teams admin center → Teams apps → Permission policies to make sure Viva Pulse isn't blocked. Run through those three in order and you'll find the cause 90% of the time.
My team members say they never received the Viva Pulse survey invitation email, what's going on?
Survey invitations are sent from noreply@email.teams.microsoft.com, and this domain frequently gets caught by corporate spam filters or third-party email security gateways like Proofpoint or Mimecast. Run a message trace in Exchange admin center → Mail flow → Message trace for the affected recipients and look for messages from that domain. If they show as filtered, quarantined, or rejected, create a mail flow bypass rule in Exchange Online that sets the spam confidence level (SCL) to -1 for mail originating from email.teams.microsoft.com. For third-party gateways, add that domain to your safe senders or permitted senders allowlist in the gateway's admin console. After the rule is in place, you'll need to resend the survey, already-sent invitations won't be retroactively delivered.
Viva Pulse results are showing "not enough responses", is there a way to lower the minimum?
Yes, you can lower it, but only down to 3, Microsoft enforces a hard minimum of 3 responses to maintain basic anonymity protection. To change the threshold, go to pulse.viva.cloud.microsoft → Admin settings → Privacy settings as a Viva Pulse admin and adjust the minimum response count. That said, I'd encourage you to think carefully before lowering it in small teams, with only 3 respondents, it can be very easy for a manager to figure out who said what, which defeats the purpose of anonymous feedback and can erode trust in the tool. If you consistently struggle to hit the threshold, consider expanding your survey audience to include a wider group rather than reducing the minimum.
Viva Pulse works fine on the web but won't load inside the Teams desktop app, what's different?
When Pulse works at pulse.viva.cloud.microsoft but not inside Teams, the problem is isolated to the Teams desktop client itself, not your licenses or tenant config. The most common cause is a corrupted Teams client cache. Quit Teams completely (right-click the system tray icon → Quit), delete the contents of %appdata%\Microsoft\Teams\Cache and %appdata%\Microsoft\Teams\Application Cache\Cache, then relaunch Teams. If that doesn't fix it, check that your Teams client is up to date by clicking your profile picture → Check for updates. Outdated Teams clients, particularly anything more than 2–3 months behind the current release, have known rendering issues with newer Viva apps. In a managed environment, push the latest Teams version via Intune or SCCM.
I'm a manager and I can't see the "Send a Pulse" button in the Viva Pulse app, why is it missing?
The ability to send a Pulse survey is controlled by a role assignment in the Viva Pulse admin settings, not just by having a license. By default, survey sending might be restricted to specific roles or groups depending on how your IT team configured the deployment. Have your Viva Pulse admin check pulse.viva.cloud.microsoft → Admin settings → Who can send Pulses and confirm your account or group is included in the allowed senders list. Also double-check that your license includes the full Viva Pulse feature set, some organizations deploy a limited Viva license that covers the respondent experience but not the survey-creation experience. If you've recently changed roles or departments, your group membership may have changed in a way that removed you from the allowed senders group.
Viva Pulse was working fine last week and suddenly stopped for everyone in our org, what should I check first?
A sudden, org-wide failure almost always points to either a Microsoft service incident or an admin-level configuration change that went wrong. Your first stop is admin.microsoft.com → Health → Service health, look for any active advisories or incidents under Microsoft Viva or Microsoft Teams. If there's an active incident, Microsoft is already working on it and your only option is to wait and monitor the incident timeline. If service health is clean, think about what changed in your tenant recently: were any Conditional Access policies updated, were app permission policies modified, was a large license reassignment processed, or was an Entra ID admin consent accidentally revoked? Pull the Entra ID audit logs from entra.microsoft.com → Monitoring → Audit logs and filter for the past 48 hours, look for any changes to enterprise application permissions or policy assignments that coincide with when Pulse stopped working.