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 · 8/9 advisories · checked 15:44 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: In-app survey feedback policies will be managed by default with Microsoft 365 Cloud Policy

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, with source markup removed
We're updating how feedback policies are managed for in-app surveys in Microsoft Teams. As part of this change, Teams for Windows desktop and Teams for the web will stop using Teams-specific feedback policies and instead adopt the Cloud Policy service for Microsoft 365. This change aligns survey feedback with other in-app feedback experiences, simplifying policy management across your organization. This change will be on by default. Note: Before this rollout, the Teams feedback policy is also on by default. The new policy is common across all M365 apps and now includes Microsoft Teams too. This message is associated with MC790791 (Updated) Microsoft Teams: Changes to in-app feedback experience and feedback policy (Teams Desktop and Teams for web), published May 2024 and updated August 2024. When this will happen: General Availability (Worldwide): We will begin rolling out late June 2025 and expect to complete by mid-July 2025. How this will affect your organization: Give a compliment/Report a problem experience has already migrated over to Cloud Policy Service and Surveys now will also use the same policy as other in-app feedback experiences. This will make managing feedback easier as all feedback entry points can be controlled through a single tenant policy. After this rollout, there will be no change in how users send or submit feedback through surveys or other in-app feedback mechanisms. However, survey feedback will now be governed by the same Microsoft 365 Cloud Policy that controls other feedback entry points (such as Give a compliment or Report a problem). This unification simplifies administration by enabling centralized control of all feedback experiences. NOTE: Teams for iOS and Android will continue to use Teams-specific feedback policies for now. We will publish a separate MC post when those platforms transition to Cloud Policy. What you need to do to prepare: Review currently used Teams feedback policies and ensure Microsoft 365 cloud feedback policies are updated to reflect your organization needs for in-app feedback collection. Teams feedback policies: Manage feedback policies in Microsoft Teams - Microsoft Teams | Microsoft Learn Learn about Microsoft feedback for your organization - Microsoft 365 admin | Microsoft Learn Cloud Feedback Policy Service: Manage Microsoft feedback for your organization - Microsoft 365 admin | Microsoft Learn Overview of Cloud Policy service for Microsoft 365 - Microsoft 365 Apps | Microsoft Learn This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your admins and/or users about this change and update internal documentation.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

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

Other posts named in this one

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 26 Oct 15:44 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current