Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Viva Pulse: New Pulse tenant admin dashboard for users with Pulse admin access

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions we saw
  • Seen 5 Nov 2024 late October 2024 → mid-November 2024

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

Updated November 5, 2024: We have updated the rollout timeline below. Thank you for your patience.

Human Resources and IT departments need a way to track user telemetry and usage to ensure that Microsoft Viva Pulse is being used effectively and has a strong return on investment. They also want to identify any issues related to user adoption that hinder the rollout of Pulse in an organization. With the rollout of the tenant admin dashboard, Pulse admins will be able to visualize usage metrics in their tenant. This rollout will include metrics such as total pulses sent, response rate per pulse, and responses per pulse.

When this will happen

General Availability (Worldwide): We will begin rolling out early November 2024 (previously late October) and expect to complete by mid-November 2024 (previously early November).

How this will affect your organization

Before this rollout, the Pulse tenant admin dashboard does not exist, and Pulse admins are not able to visualize and measure their Pulse usage and return on investment.

After this rollout, the tenant admin dashboard's initial release will include these metrics:

  1. Total pulses sent: The number of pulses sent in a specified time period
  2. Response Rate: Response rate per pulse, averaged across all pulses sent in a specified time period
  3. Responses per pulse: Average responses per pulse in a specified time period

The tenant admin dashboard will be on by default.

What you need to do to prepare

As a Pulse admin, to open the tenant admin dashboard, go to Viva Pulse on the app or on the web, and from the homepage select Usage Dashboard. The dashboard will help HR and IT their Pulse understand their usage and present ways to increase adoption and engagement.

As a Pulse admin, you can manage the new dashboard in the Viva Pulse admin center > Manage > Usage dashboard tab. Learn more:

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation.

What changed

Between archive captures, newest first
  1. Updated November 5, 2024: We have updated the rollout timeline below. Thank you for your patience. Human Resources and IT departments need a way to track user telemetry … When this will happen: General Availability (Worldwide): We will begin rolling out late Octoberearly November 2024 (previously late October) and expect to complete by mid-November 2024 (previously early November 2024.November). How this will affect your organization: Before this rollout, the Pulse tenant …

  2. · first version seen

Learn more

Links from the notice and their documentation checks

No related announcements were found in the saved public history. Check the source for newer announcements.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 2 linked pages have not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 02:37 UTC · 274 of 275 readable · 258 fully read · 11 waiting for GitHub's hourly limit · documentation 448/469 current