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

Viva Pulse Customization Control Migration

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".

What the notice says

Microsoft’s text, safely structured

Updated February 8, 2024: We have updated the timing of this change below. Thank you for your patience.

The customization control in the Viva Pulse Admin Experience will soon be managed through centralized feature access management in Viva through PowerShell. This customization control provides admins the ability to turn on or off customization capabilities for survey authors to add their own questions to existing stock templates or edit existing stock questions. With centralized feature access management, admins can configure access at the tenant level, group level (using AAD groups or M365 Groups), or at the user level, for maximum flexibility.

When this will happen

These changes are expected to be completed by late February 2024 (previously mid-January).

How this will affect your organization

  • At the end of October, the two customization controls will be consolidated to one customization control called ‘Survey question customization’. The value currently set for the “New questions” control will be the value of the new consolidated customization control. Management of the control will change to PowerShell configurations through centralized feature access management. The UX for this control in the Viva Pulse Admin Experience will be removed.
  • For any tenant that has previously disabled the customization control, you will have a policy assigned to everyone in the tenant that maintains that disabled state. The admin can then manage/edit/delete that policy after the migration.

Admins will soon be able to manage the customization feature control for their specific users, groups, or the entire tenant by using PowerShell. Use the Add-VivaModuleFeaturePolicy cmdlet to create a new access policy to disable customization in Viva Pulse. The attributes of the policy are defined using specific parameters of the cmdlet. Policies are used to restrict or grant access to the specified feature for specific users, groups, or the entire tenant.

For more information about the PowerShell cmdlets and detailed instructions on how to create a policy, please review:

What you need to do to prepare

Review and assess the impact on your organization. Determine if you want to create a policy to configure granular access to the Customization feature in Viva Pulse.

What changed

Between archive captures, newest first
  1. … groups or M365 Groups), or at the user level, for maximum flexibility.  When[When this will happen:happen:] These changes are expected to be completed by late February 2024 (previously mid-January).  How[How this will affect your organization:organization:] At the end of October, the two customization controls will be consolidated … Microsoft Learn Remove-VivaModuleFeaturePolicy (ExchangePowerShell) | Microsoft Learn Update-VivaModuleFeaturePolicy (ExchangePowerShell) | Microsoft Learn What[What you need to do to prepare:prepare:] Review and assess the impact on your organization. Determine if you want … policy to configure granular access to the Customization feature in Viva Pulse. Additional resources:[Additional resources:] Control access to features in Viva

  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.
  • 4 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 06:51 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current