Microsoft Roadmap, messagecenter en blogs updates van 19-10-2024

Updated October 18, 2024: We have updated the SMTP AUTH Clients Submission Report in the Exchange admin center, adding the Authentication Protocol column to show if Basic auth or OAuth is being used to submit email to Exchange Online. The data will build up over the next 90 days. Thank you for your patience.

Today, we are announcing that Exchange Online will permanently remove support for Basic authentication with Client Submission (SMTP AUTH) in September 2025. After this time, applications and devices will no longer be able to use Basic auth as an authentication method and must use OAuth when using SMTP AUTH to send email.

Basic auth is a legacy authentication method that sends usernames and passwords in plain text over the network. This makes it vulnerable to credential theft, phishing, and brute force attacks. To improve the protection of our customers and their data, we are retiring Basic auth from Client Submission (SMTP AUTH) and encouraging customers to use modern authentication methods that are more secure.

[When this will happen:]

We will be making this change in September 2025.

[How this will affect your organization:]

In September 2024, we will update the SMTP AUTH Clients Submission Report in the Exchange admin center to show if Basic auth or OAuth is being used to submit email to Exchange Online. In January 2025, we will send a Message Center post to tenants who are using Basic auth with Client Submission (SMTP AUTH) to alert them to the upcoming change. In August 2025, about 30 days before we disable Basic auth we will send another Message Center post to tenants who are still using Basic auth with Client Submission (SMTP AUTH).

During September 2025, we will remove support for Basic auth with the Client Submission (SMTP AUTH) endpoints:

• smtp.office365.com
• smtp-legacy.office365.com

Once Basic auth is permanently disabled, any clients or apps connecting using Basic auth with Client Submission (SMTP AUTH) will receive this response:

• 550 5.7.30 Basic authentication is not supported for Client Submission.

[What you need to do to prepare:]

If your client supports OAuth, follow these steps: Authenticate an IMAP, POP or SMTP connection using OAuth

If your client doesn’t support OAuth and you must use Basic Auth with Client Submission (SMTP AUTH), you will need to switch to one of the following alternatives before September 2025:

• If you are using basic authentication with Client Submission (SMTP AUTH) to send emails to recipients internal to your tenant, you can use Microsoft 365 High Volume Email. Please visit this site to learn more: Manage high volume emails for Microsoft 365 Public preview
• If you are using basic authentication with Client Submission (SMTP AUTH) to send emails to recipients internal and external to your tenant, you can use Azure Communication Services Email. Please visit this site to learn more: Overview of Azure Communication Services email
• If you have an Exchange Server on-premises in a hybrid configuration, you can use Basic auth to authenticate with the Exchange Server on-premises or configure the Exchange Server on-premises with a Receive connector that allows anonymous relay on Exchange servers. Please visit this site to learn more: Allow anonymous relay on Exchange servers

Regardless of the volume of email, if you must use Basic auth to send email with Exchange Online, then you must use one of the alternatives.

We understand that this change requires some adjustments, but we believe that this is a necessary step to enhance the security and reliability of our email service and your data.

Updated October 17, 2024: We have updated the content. Thank you for your patience.

We’re making an update to the behavior of email notification in Project for the web. When a project or roadmap is shared with a Microsoft 365 group, only if the group has 50 or less members will an email notification be sent to each member of the group notifying them a plan or roadmap has been shared with them.

If the group has more than 50 members then group members will not receive an email notification when a project or roadmap is shared with the group. 

Individual notification settings will continue to be respected when these emails are sent.

[When this will happen:]

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

[How this will affect your organization:]

For users of Project for the web if a project or roadmap is shared with a group has 50 or less members in it, an email notification is sent to each member informing them the project or roadmap was shared with them. For groups with more than 50 members, an email is not sent when a project or roadmap is shared with the group.

[What you need to do to prepare:]

Update any business documentation or processes which will be impacted by this change. 

Version 5.0 of the Quality of Experience Report (QER) for the Microsoft Teams Call Quality Dashboard (CQD) in Microsoft Power BI has reached General Availability and is live on the Microsoft downloads website for tenant admins and IT pros to start using today.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): Available now.

[How this will affect your organization:]

The biggest highlight of version 5.0 is the inclusion of the new Intelligent media quality classifiers, enabling IT admins to narrow the scope of their investigations by helping to identify possible root cause(s) for media quality degradation. We have also updated the design to provide a cleaner experience and to visually align the report with Teams and the Teams admin center. Also, a new feedback submission feature allows customers to submit feedback directly to the CQD Product Group through the Power BI report.

[What you need to do to prepare:]

We recommend reviewing the latest documentation on using Call Quality Dashboard with Power BI reporting templates. For first-time users, please review how to the instructions for installing and configuring the Microsoft Call Quality Connector for Power BI Desktop to ensure you can use the QER and other available templates for CQD.

Learn more

• Use Power BI to analyze CQD data for Microsoft Teams – Microsoft Teams | Microsoft Learn
• Install Power BI Connector to use CQD query templates – Microsoft Teams | Microsoft Learn

A new csTeamsAIPolicy policy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-January 2025) will give IT admins more control over voice and face enrollment settings, allowing organizations to manage these features based on their needs. After rollout, voice and face profile enrollment will be enabled by default, and users can benefit from voice isolation, speaker recognition, and attribution in meeting rooms, resulting in smarter meeting recaps and enhanced functionality for Microsoft 365 Copilot in meetings. To access Copilot features, a Microsoft 365 Copilot license is required. This message applies to Teams for Windows desktop and Mac desktop.

NOTE: Microsoft doesn’t use the voice and face profiles of users to train any models or for any other purposes other than providing the voice and face enrollment feature in Microsoft Teams.

This message is associated with Microsoft 365 Roadmap ID 413708.

[When this will happen:]

General Availability (Worldwide, GCC): The new Microsoft PowerShell cmdlets are available now for preparation and to ensure a smooth transition. The policy takes effect starting in mid-January 2025 and is expected to be fully in effect by mid-January 2025.

[How this will affect your organization:]

Before this rollout, the current policy csTeamsMeetingPolicy has a single setting, EnrollUserOverride, that allows the administrator to enable or disable the enrollment of both face and voice profile of users.

After this rollout, the new csTeamsAIPolicy will replace the existing enrollment setting in csTeamsMeetingPolicy. The new csTeamsAIPolicy has two settings, EnrollFace and EnrollVoice, that will be set to Enabled by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date. Review your current configuration to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation.

If your organization prefers to disable voice and face enrollments, review and update your settings before mid-January 2025. To help you get started, review:

• Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn
• Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

Learn more: Overview of voice and face enrollment – Microsoft Teams | Microsoft Learn

In Microsoft Defender XDR, on the Settings > Identities page, we will retire the Alert notifications page starting mid-November 2024. We expect to complete by mid-November 2024.

[How this will affect your organization:]

As an alternative, please use the Incident email notifications page in Microsoft Defender XDR settings to create and manage all new and existing notification rules. This update will help streamline and enhance your notification experience in the Defender XDR portal.

[What you need to do to prepare:]

To ensure uninterrupted notifications, it is essential to transfer all existing notification settings to the Email Notifications page under Defender XDR settings. Please note that if incidents notifications are not set up through the XDR page, you will no longer receive alerts emails notifications after the deprecation date.

Learn more: Get incident notifications by email in Microsoft Defender XDR – Microsoft Defender XDR | Microsoft Learn.