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

Sensitive meetings to be excluded from Viva Insights metrics

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

End-users of Outlook have the ability to set a meeting to have a ‘Private’ or ‘Confidential’ sensitivity level in order to protect the information of a meeting they consider sensitive. To ensure that these meetings cannot be analyzed, Viva Insights would remove these meetings from metric computation.

When this will happen

We will begin rolling this out in mid-September 2024 and expect to complete by mid-October 2024.

How this will affect your organization

As this change begins rolling out, your organization will see the following updates:

  • Sensitive meetings would be excluded from the output of Meeting Query
  • Subjects of sensitive meetings would remain hidden and cannot be used in any query

What you need to do to prepare

No action needed from your organization. You may consider updating your training and documentation as appropriate.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

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.
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 03:41 UTC · 274 of 275 readable · 259 fully read · 11 waiting for GitHub's hourly limit · documentation 447/469 current