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

Fix to respect Cloud Policy settings for Auto-create Loop workspaces for Teams meetings feature

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

We previously announced the release of a feature in Teams via a Message Center post: MC792605 - Microsoft Teams: Auto-create Microsoft Loop workspaces to share meeting content. We shared that Teams meeting organizers of recurring meetings will be prompted in chat to create a Loop workspace after their meeting is completed. The feature helps users gather shared meeting content into a Loop workspace.

In response to your feedback, we are improving the ability for you to control this feature through Microsoft 365 Cloud Policy.

When this will happen

Available now.

How this affects your organization

We are now responding to feedback from you, and the button to create a Loop workspace from Teams meeting chat will not be visible if the Loop workspace creation is disabled on your tenant. This is done by setting the Microsoft 365 Cloud Policy "Create and view Loop workspaces in Loop" to "disabled".

What you need to do to prepare

Review your current configuration and make changes as appropriate for your organization.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Other posts named in this one

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 00:16 UTC · 274 of 275 readable · 251 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current