Public mode

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

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 02:30 UTC Customize Public modeDiscuss ChangeIntel on Discord

Managing Microsoft Viva Engage no longer requires the assignment of a Microsoft 365 license seat

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

Rollout

Roadmap
393230

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 this installation saw
  • Seen 6 Jun 2024 the end of May 2024 → mid-June 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, with source markup removed
Updated June 6, 2024: We have updated the rollout timeline below. Thank you for your patience. To align with best practices for Microsoft 365 core workload administration, we are changing the service plan requirements for certain admin roles in Microsoft Viva Engage. After this change rolls out, Global admins and Engage admins (also called the Yammer administrator role in Entra ID) will have the ability to perform Viva Engage administration without being assigned a service plan for Viva Engage. This message is associated with Microsoft 365 Roadmap ID: 393230. When this will happen: General Availability (Worldwide): We will begin rolling out mid-May 2024 and expect to complete by the mid-June 2024 (previously late May). How this will affect your organization: Previously when the commonly used Block Office 365 users without Yammer licenses option was selected, you needed to assign Engage Core or Yammer Enterprise service plans to Engage admins and global admins to access the Engage website (https://engage.cloud.microsoft), the Engage admin center, or legacy network admin center. After this rollout, license enforcement will not apply to the Global admin or Engage admin roles. This rollout does not apply to other roles, including Yammer Network Administrator, Yammer Verified Administrator, Corporate Communicator, Answers Administrator, and Community Administrator. These roles will continue to require a “Viva Engage Core” service plan when the tenant is configured to require a per-user license. Note: Engage admins and Global admins who wish to access Viva Engage inside the Microsoft Teams application should ensure they have access to the right licensing required to access Teams. Learn more about licensing for Teams: All Microsoft Teams Product Plans | Microsoft Teams What you need to do to prepare: You can choose to unassign the “Viva Engage core” and/or the “Yammer enterprise” service plan from Engage admins/ Global admins, since it’s no longer a prerequisite to access Viva Engage, Engage admin center or the legacy network admin center. You can also choose to unassign the entire Microsoft 365 seat for these roles if it was earlier assigned for the sole purpose of Viva Engage administration. Consider using the Engage admin role within Entra ID as more Engage experiences integrate with the rest of Microsoft 365. The Verified Administrator role is internal to Engage and not recognized by applications relying on Entra ID. This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation as appropriate. We will update this comm before rollout with revised documentation.

Microsoft Entra roles mentioned

Links open the current public role definition. A mention does not establish tenant impact, assignment, or historical permissions.

What changed

Between archive captures, newest first
    • Tags New feature, Admin impact → Updated message, New feature, Admin impact

    Updated June 6, 2024: We have updated the rollout timeline below. Thank you for your patience. To align with best practices for Microsoft 365 core workload administration, we … will begin rolling out mid-May 2024 and expect to complete by the end of May 2024.mid-June 2024 (previously late May). How this will affect your organization: Previously when the commonly used Block …

  1. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

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.
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 27 Oct 02:30 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current