| Announcement ID | MC892652 | Published Date | 09-19-2024 | |
| Service | General | Last Updated | 09-19-2024 | |
| Category | Stay informed | Expiration Date | 01-31-2025 | |
| Roadmap ID | 416296 | Action Required by Date | ||
| Tags | Admin impact, Feature update, User impact | |||
| Summary |
|---|
| Microsoft Outlook is enhancing security by making feedback policy checks more restrictive across all user accounts. Eligibility for feedback submission will be based on the most restrictive policy value among a user's accounts. This change will start rolling out in late September 2024 for Targeted Release and in late October 2024 for General Availability. No admin action is required before the rollout. |
| More Information |
|---|
Before this rollout, when we determine whether a user is entitled to submit feedback for Microsoft Outlook, we only look at the feedback policy for a user's primary account (also known as the global account). This message applies to new Outlook on Windows desktop and Outlook on the web. After this rollout, we will make the feedback policy check more restrictive, which is more secure. We will base their eligibility on the most feedback restrictive policy value in all of the user's accounts. For example, if any of the user's accounts have feedback disabled by a policy, we will not show the Feedback button in the Help tab of the ribbon in Outlook for any of their accounts. When this will happen:Targeted Release: We will begin rolling out late September 2024 and expect to complete by late October 2024. General Availability (Worldwide): We will begin rolling out late October 2024 and expect to complete by late November 2024. How this will affect your organization:A user with a policy that disables feedback on one of their accounts will lose access to feedback for all their accounts. After this rollout, this change will be on by default. What you need to do to prepare:This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. |