Microsoft Roadmap, messagecenter en blogs updates van 22-09-2024

Updated September 20, 2024: We have updated the content. Thank you for your patience.

Starting December 1st, we’re going to start gradually dropping messages that have multiple From addresses (also known as P2 From headers) without a Sender header from being sent via Exchange Online.

If we see significant traffic exhibiting multiple From addresses (P2 From headers) without a Sender header in your tenant in the month of September, we will send you a Message Center Post by October 15th alerting you and providing some sample message IDs.

We are doing this to comply with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2) which mandates the Sender header to be present and contain a single address if the From header has more than one address. Noncompliance with this could be exploited by attackers, allowing them to impersonate a sender address by misleading the client into using the From header to determine the sender instead of the Sender header.

[When this will happen:]

December 1st, 2024

[How this affects your organization:]

If email clients including devices and applications that you use to send messages, do so using multiple From addresses but without a Sender address header after December 1st, you will get an NDR error code 550 5.1.20 “Multiple From addresses are not allowed without Sender address’”.

[What you can do to prepare:]

When this change is in effect, if you need to send a message that has more than one email address in the From field, make sure that you have a single email address in the Sender header.

If you expect this change to cause any issues for your organization, please share that feedback.

As mentioned in MC715413/MC814570, with Intune’s October (2410) service release, Intune will be moving to support Android 10 and later for user-based management methods which includes:

• Android Enterprise personally-owned work profile
• Android Enterprise corporate owned work profile
• Android Enterprise fully managed
• Android Open Source Project (AOSP) user-based
• Android device administrator
• App protection policies (APP)
• App configuration policies (ACP) for managed apps

Moving forward, we will end support for one or two versions annually in October until we only support the latest four major versions of Android. You can learn more about this change by reading the blog: Intune moving to support Android 10 and later for user-based management methods in October 2024

Important: Userless methods of Android device management (Dedicated and AOSP userless) and Microsoft Teams certified Android devices will not be impacted by this change.

[How this will affect your organization:]

For user-based management methods (as listed above), Android devices running Android 9 or earlier will no longer be supported. For devices on unsupported Android OS versions:

• Intune technical support will no longer be provided.
• Intune will no longer make changes to address bugs or issues.
• New and existing features are not guaranteed to work. 

While Intune will not prevent enrollment or management of devices on unsupported Android OS versions, functionality is not guaranteed, and use is not recommended.

[What you need to do to prepare:]

Notify your helpdesk, if applicable, about this updated support statement. The following admin options are available to help warn or block users:

• Configure a conditional launch setting for APP with a minimum OS version requirement to warn and/or block users.
• Use a device compliance policy and set the action for noncompliance to send a message to users before marking them as noncompliant.
• Set enrollment restrictions to prevent enrollment on devices running older versions.

For more details, read the blog: Intune moving to support Android 10 and later for user-based management methods in October 2024

Coming soon: Updates to the Microsoft 365 Cloud Policy service setting Turn off sharing recommendation in the Microsoft 365 admin center will disable the ability for users to share or edit folder permissions with individual users in Microsoft Outlook on the web and new Microsoft Outlook for Window desktops. We will not change anything else about how the policy currently works.

This message is associated with Microsoft 365 Roadmap ID 415467.

[When this will happen:]

Targeted Release: We will begin rolling out early October 2024 and expect to complete by late October 2024.

General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by early December 2024.

General Availability (GCC, GCC High, DoD): We will begin rolling out mid-December 2024 and expect to complete by late December 2024. [How this will affect your organization:]

Before this rollout, the policy blocks users’ ability to update default and anonymous permission levels for shared folders. This functionality will remain after the rollout, when users will also not able to share or edit individual user permissions. The current policy and how it works with calendar sharing will not be affected by this change and will remain as is.

After the rollout: The steps to update this policy at https://config.office.com/officeSettings/officePolicies will not change:

After this rollout, this screen will change (and the lower half of the screen is intentionally grayed out):

This change is 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.

Review your current configuration to determine the impact for your organization.

Learn more: Overview of Cloud Policy service for Microsoft 365 – Microsoft 365 Apps | Microsoft Learn

#newoutlookforwindows

We are continuously refining our defense-in-depth approach, ensuring optimal protection when intermediaries are involved in your email traffic. We’re enhancing the assignment of Bulk Complaint Level (BCL) scores when connectors are utilized, particularly for instances where Composite Authentication (CAUTH) is set to None.

We are rolling out a significant update that will result in more accurate BCL scoring for bulk emails. This adjustment ensures that the presence of intermediaries is factored into the scoring, making bulk email filtering more consistent and reflective of the actual sender’s reputation. As a result, organizations can expect enhanced email filtering precision, leading to more reliable and effective management of bulk emails.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High): We will begin rolling out early October 2024 and expect to complete by late October 2024.

[How this will affect your organization:]

• Admins using connectors may observe changes in bulk email filtering as the new BCL scoring system provides more accurate reflections of bulk email traffic. This update will automatically be available by default, and admins should expect to see these changes reflected in their filtering logs and reports.
• After the rollout, admins can expect to see an increase in the volume of bulk emails reflected in their Threat Protection Status (TPS) report. Specifically, when viewing data under Email > Spam and breaking down the chart by Detection Technology > Bulk, the updated scoring will provide a clearer insight into bulk email traffic handled by the system.

[What you need to do to prepare:]

Review your email filtering logs to assess the impact of the updated BCL scoring. Admins should also evaluate any custom rules or configurations in place and make necessary adjustments to optimize filtering based on the new scoring system.

For more details on BCL scoring and how it impacts your email security, see Bulk complaint level (BCL) in EOP.

We’re rolling out new and improved DLP Policy tips in New Outlook to support top DLP predicates & exceptions, all advanced classifiers, and override capabilities.

* Features mentioned above are enabled based on Licenses. Please review license requirements here.

The number of supported conditions has been updated:

• E3 and equivalent licenses: DLP Policy tips on New Outlook for Windows will support following DLP conditions (and corresponding exceptions):
  • Content contains OOB/custom sensitive information types
  • Content is shared from Microsoft 365
• E5 and equivalent licenses: In addition to the above, DLP Policy tips on New Outlook for Windows will now support a richer set of DLP conditions (and corresponding exceptions), including the following:
  • Content contains Sensitivity label
  • Sender is
  • Sender domain is
  • Sender is member of
  • Recipient is
  • Recipient domain is
  • Recipient is a member of
  • Subject contains words

Additionally, DLP Policy tips now support advanced classifiers like Trainable classifiers, Exact data match (EDM), and Named Entities, as well as an override feature that gives end users the ability to quickly and easily modify or override policies (if allowed in the DLP rule configuration), ensuring that the sensitive data is always protected, while still allowing end users to work efficiently.

For more details, admins can refer documentation here.

Please note that any existing conditions outside this updated list, which may currently trigger Policy Tips in New Outlook, will stop working after October 18th, 2024.

[When this will happen:]

We will begin rolling out in late October 2024 and expect to complete rollout by late November 2024.

[How this will affect your organization:]

If you are not using New Outlook this shall not impact you.

If you do not configure the Data Loss Prevention policies to enable policy tips for emails with sensitivity labels, this will not impact you.

If your organization is currently using Data loss prevention policies to enable policy tips and Oversharing pop-up, you will soon see them in New outlook with enhanced experience.

[What you need to do to prepare:]

At this time, there is no action required from you.

You can access Data Loss Prevention in the Microsoft Purview compliance portal. You can create new DLP policies or leverage the existing ones to use DLP Policy tips as an additional layer of security for sensitive data.

Learn more:

• Learn about data loss prevention
• Learn about New Outlook

Users with Microsoft Word, Excel, and PowerPoint on Windows desktops and the web will soon have access to an updated version of the Office Add-ins Store in these applications. This store will continue to support users in exploring, installing, and managing Office Add-ins provided by Microsoft and third parties.

With this new feature, minor users will no longer be permanently blocked from getting Office Add-ins from the Office Add-ins Store.

Learn more:

• View, manage, and install add-ins for Excel, PowerPoint, and Word – Microsoft Support
• Understand how to configure the Age Group property in Microsoft Entra admin center

[When this will happen:]

Targeted Release: We will begin rolling out late October 2024 and expect to complete by late November 2024.

General Availability (Worldwide): We will communicate timing with a new Message center post in the future.

[How this will affect your organization:]

Users will experience a new Office Add-ins Store in Word, Excel, and PowerPoint on both Windows desktops and on the web. Minor users not blocked by tenant administrators will be able to get Office Add-ins from the Office Add-ins Store.

This feature will be available by default.

[What you need to do to prepare:]

Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

For educational tenant administrators:

• If you wish to continue blocking minor students from getting Office Add-ins from the Office Add-ins Store, please ensure the user’s License Type is set to student, the Age group property is not set to Adult, and go to Microsoft admin center > Org settings > User owned apps and services to ensure the option Non-adult student is unchecked.
• For student users who you want to have access to the Office Add-ins Store, make sure their Age group property is set to Adult.

Educational tenant admins: The last step in Microsoft admin center to blocking minor students from getting Office Add-ins from the Office Add-ins Store:

Anonymous users (guests) who join Microsoft Teams meetings in the Chrome web browser will soon experience performance improvements.

This message is associated with Microsoft 365 Roadmap ID 401116.

[When this will happen:]

Targeted Release: We will begin rolling out early November and expect to complete by mid-November 2024.

General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by late-November 2024.

General Availability (GCC, GCC High and DoD): We will begin rolling out early January 2025 and expect to complete by late January 2025.

[How this will affect your organization:]

Before this rollout, anonymous users (guests) may experience longer wait times when attempting to join a Teams meeting.

After this rollout, anonymous users (guests) will be able to join meetings faster, even on low-end devices.

[What you need to do to prepare:]

You may want to update your internal documentation to inform your users about this improvement. However, because the improvement is for external users and does not change the look of Teams, you can skip this step./p>