Microsoft Roadmap, messagecenter en blogs updates van 01-02-2025

Updated February 1, 2025: This update serves as a reminder that SharePoint 2013 workflow will retire and stop working in 14 months from now (April 2, 2026).

Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only encompass SharePoint, but all the productivity services you use with Microsoft 365 and beyond. With the continued investment in Power Automate as the universal solution to workflow, Microsoft is retiring SharePoint 2013 workflows.

[When this will happen:]

• Starting April 2nd, 2024, SharePoint 2013 workflows will be turned off for any newly created tenants.
• Starting April 2nd, 2026, Microsoft will remove the ability to run, or create and execute SharePoint 2013 workflows for existing tenants.

[How this will affect your organization]

If your organization still uses SharePoint 2013 workflows, they will no longer function after April 2nd, 2026. We recommend customers to move to Power Automate or other supported solutions.

[What you need to do to prepare]

You will want to notify your users, workflow developers and site owners. Update your user training and prepare your help desk.

For admins

• Use the Microsoft 365 Assessment tool to scan your tenants for legacy workflow usage.
• Review Guidance: Migrate from classic workflows to Power Automate flows in SharePoint
• Review the Power Automate resources as a solution to legacy workflows.

Note: There will not be an option to extend SharePoint 2013 workflow beyond April 2nd 2026.

Learn more:

• Detailed support article with additional resources. 
  

Updated February 1, 2025: This update serves as a reminder that Azure ACS in Microsoft 365 will retire and stop working in 14 months from now (April 2, 2026).

Since the first use of Azure Access Control Services (ACS) by SharePoint in 2013, Microsoft has evolved the authorization and authentication options for SharePoint Online via Microsoft Entra ID (a.k.a. Azure AD). Using Microsoft Entra ID as auth platform for your SharePoint Online customizations will provide your applications the most secure, compliant and future proof model. With our continued investment in Microsoft Entra ID, Microsoft is retiring the use of Azure ACS as auth platform for SharePoint Online.

[Key Points:]

• Major: Retirement
• Timeline:
  • Starting November 1st, 2024, new tenants will not be able use Azure ACS.
  • Starting April 2, 2026, Microsoft will remove the ability use SharePoint ACS for existing tenants.
• Action: Review and assess impact

[How this will affect your organization]

If your organization still uses Azure ACS to grant custom developed or third party applications access to SharePoint Online, they will no longer have access after April 2nd, 2026. We recommend customers to update their customizations to use Microsoft Entra ID and ask their solution vendors to do the same.

[What you need to do to prepare]

You will want to notify your Azure ACS users and developers. Update your user training and prepare your help desk.

For admins

• Use the Microsoft 365 Assessment tool to scan your tenants for Azure ACS usage.
• Review the guidance for migrating from Azure ACS to Microsoft Entra ID.
• There will not be an option to extend Azure ACS usage for SharePoint Online beyond April 2nd 2026.

Learn more

• Support update for the retirement of Azure ACS for SharePoint Online in Microsoft 365.

Updated February 1, 2025: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 14 months from now (April 2, 2026).

Since the release of SharePoint Add-Ins in 2013, Microsoft has evolved SharePoint extensibility using SharePoint Framework (SPFx) enabling you to write applications that can be used in Microsoft SharePoint, Viva Connections and Microsoft Teams. With our continued investment in SharePoint Framework, Microsoft is retiring SharePoint Add-Ins.

[Key Points:]

• Major: Retirement
• Timeline:
  • Starting July 1st, 2024, SharePoint Add-Ins cannot be installed from the public marketplace, also referred to as store by existing tenants. Installation from a private app catalog stays possible.
  • Starting November 1st, 2024, new tenants will not be able use SharePoint Add-Ins, regardless of their origin (public marketplace, private tenant catalog).
  • Starting April 2nd, 2026, Microsoft will remove the ability use SharePoint Add-Ins for existing tenants.
• Action: Review and assess impact

[How this will affect your organization:]

If your organization still uses SharePoint Add-Ins, they will no longer function after April 2nd, 2026. We recommend customers to port their customizations to SharePoint Framework (SPFx) and ask their solution vendors for updated solutions.

[What you need to do to prepare]

You will want to notify your Add-In users and developers. Update your user training and prepare your help desk.

For admins

• Use the Microsoft 365 Assessment tool to scan your tenants for SharePoint Add-In usage.
• Disable SharePoint Add-Ins on your tenant using SharePoint Online Management Shell
• Review the guidance for migrating from SharePoint Add-Ins to SharePoint Framework.
• There will not be an option to extend SharePoint Add-Ins beyond April 2nd 2026.

New: How to disable SharePoint Add-Ins on your tenant

Admins can disable SharePoint Add-Ins with the Set-SPOTenant SharePoint Management Shell PowerShell command.

Connect-SPOService -Url https://<tenant>-admin.sharepoint.com

Set-SPOTenant -IsSharePointAddInsDisabled $true

After SharePoint Add-Ins are disabled, users will not be able to add SharePoint Add-Ins to their sites, and admins cannot add new SharePoint Add-Ins to the tenant and site collection app catalogs. SharePoint Add-Ins already added to sites will stay available and can still be used by the site’s users.

New: SharePoint Add-Ins will not be available from the public marketplace

After July 1, 2024, users browsing the public marketplace (AppSource) will see SharePoint Add-In, but if they select Get it now, a message will explain that SharePoint Add-Ins are retired and cannot be added. If you still require a specific SharePoint Add-In, contact the Add-In creator to understand the possible options.

Learn more

• Support update for the retirement of SharePoint Add-Ins in Microsoft 365.

Updated January 31, 2025: We have updated the rollout timeline below. Thank you for your patience.

Coming soon: Microsoft Copilot for Microsoft 365 usage in your tenant will be added to the Microsoft Graph API to facilitate the creation of customized reporting and analytics. Metrics included in the Graph API will match those available in the Copilot for Microsoft 365 usage report in the Microsoft 365 admin center, including tenant-level count of enabled users and active users, as well as last activity date per user (totals for each Microsoft 365 app and a grand total). A Microsoft Copilot for Microsoft 365 license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 396562 and with MC724835 Microsoft 365 admin center Usage report: Microsoft Copilot with Graph-grounded chat (Preview) (published March 2024).

[When this will happen:]

Public Preview: We will begin rolling out early September 2024 and expect to complete by mid-September 2024.

General Availability (Worldwide): We will begin rolling out late June 2025 (previously early March) and expect to complete by late July 2025 (previously late March). 

[How this will affect your organization:]

Before this rollout, the Graph API did not include Copilot for Microsoft 365 usage.

After this rollout, admins can use the Graph API to create customized reporting and analytics for Copilot for Microsoft 365 usage.

Sample request for one of the three APIs: getMicrosoft365CopilotUserCountSummary.

Sample response:

HTTP/1.1 200 OK

Content-Type: application/json

Content-Length: 537

{

"@odata.context": "https://graph.microsoft.com/beta/reports/getMicrosoft365CopilotUserCountSummary(period='D7')?$format=application/json",

"value": [

{

"reportRefreshDate": "2024-06-26",

"adoptionByProduct": [

{

"reportPeriod": 7,

"anyAppEnabledUsers": 354590,

"anyAppActiveUsers": 144022,

"microsoftTeamsEnabledUsers": 354449,

"microsoftTeamsActiveUsers": 88737,

"wordEnabledUsers": 354449,

"wordActiveUsers": 17493,

"powerPointEnabledUsers": 354449,

"powerPointActiveUsers": 7245,

"outlookEnabledUsers": 354449,

"outlookActiveUsers": 38140,

"excelEnabledUsers": 354449,

"excelActiveUsers": 2554,

"oneNoteEnabledUsers": 354449,

"oneNoteActiveUsers": 1382,

"loopEnabledUsers": 354449,

"loopActiveUsers": 955,

"copilotChatEnabledUsers": 354449,

"copilotChatActiveUsers": 64401

}

This feature 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 admins about this change and update any relevant documentation.

Before rollout, we will update this post with revised documentation.

To learn more about Microsoft’s own review of this product with its works councils, please consider reading: https://aka.ms/Copilot/MSWorksCouncilsArticle 

Updated January 31, 2025: We are proactively opting tenants out of the rollout that were detected as sending high volumes of emails exhibiting multiple From addresses without a Sender address header. These exempted senders will only be able to send emails exhibiting multiple From addresses without a Sender address header to recipients belonging to the same tenant as the sender. We will provide a subsequent update by the end of February with an updated timeline for tenants that are opted out.

Starting February 3 (previously December 1), 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 processed 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:]

February 3, 2025 (previously December 1st)

We are delaying the rollout start date from December to February 3rd 2025 in order to provide more time to customers for investigating messages exhibiting multiple P2 From Addresses without a Sender Address.

Most of the traffic exhibiting multiple P2 From Addresses without a Sender Address will be inbound spam destined for your tenant sent by malicious spammers on the internet.

Some customers are sending legitimate emails with this malformed header configuration. On October 15, we sent a targeted MC post to customers showing high volumes of messages exhibiting multiple P2 From Addresses without a Sender Address as they may be impacted by this change.

For investigating if you will be impacted by this change, focus your investigation on messages sent using On Premises Inbound Connectors to Exchange Online. Authenticated mail submission is not impacted because submitting messages like this using those submissions are not allowed (Graph, Outlook clients, SMTP AUTH Client Submission).

[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.

Updated January 31, 2025: We have updated the rollout timeline below. Thank you for your patience.

We’re introducing a new policy that gives IT admins enhanced flexibility with distinct settings for voice and face enrollment. This adjustment provides greater control over managing these features, allowing organizations to tailor to their needs. Voice and face biometric enrollment will be enabled by default, enabling voice isolation and speaker recognition in meeting rooms and enhancing intelligent meeting recaps and Microsoft Copilot for meetings.

This message is associated with Microsoft 365 Roadmap ID 413708.

[When this will happen:]

General Availability (Worldwide, GCC):

• We will begin rolling out the new policy in early October 2024 and expect complete by mid-October 2024.
• The policy will be enabled beginning in mid-March 2025 (previously early February) and expect to be complete by late March 2025 (previously mid-February).

[How this will affect your organization:]

These changes will provide your organization with increased flexibility in managing voice and face enrollments. By using separate settings, you can customize for your organization’s specific needs. The enrollment policy will be enabled by default. Once enabled, these enrollments will activate features like Voice Isolation and enhanced speaker recognition, leading to more efficient and productive meetings.

[What you need to do to prepare:]

To ensure you have enough time to prepare for this change, you have until mid-January 2025 to configure everything to best suit your needs. If your organization requires keeping face and voice enrollments off, be sure to review the new policy and adjust the settings during this time. This period provides an opportunity to optimize how you manage voice and face data, enhancing your team’s control over the process.

The new csTeamsAIPolicy will replace the current csTeamsMeetingPolicy, introducing two separate settings for face and voice enrollment: EnrollFace and EnrollVoice. Each can be set to Enabled or Disabled.

To help you get ready, review:

• Set-CsTeamsMeetingPolicy
• Get-CsTeamsAIPolicy 

For more information about voice and face enrollment, visit Overview of voice and face enrollment – Microsoft Teams | Microsoft Learn

Updated January 31, 2025: We have updated the rollout timeline below. Thank you for your patience.

Coming soon in Microsoft Viva Learning in Microsoft 365: Admins will be able to edit Learning paths.

Before this rollout, admins are not able to edit the content of Learning paths. They can only edit metadata such as the title, description, thumbnail, preview, duplicate, and they can also delete the Learning path.

This feature will be available by default to Viva Learning premium users.

This message is associated with Microsoft 365 Roadmap ID 396286.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). 

[How this will affect your organization:]

After this rollout, admins can edit a published Learning path to change the content. They can also edit the metadata, as before the rollout. Admins and Learners will be able to see the latest changes after editing.

Note: Editing a published Learning path may change the progress and experience of the Learner.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Updated January 31, 2025: We have updated the rollout timeline below. Thank you for your patience.

A new csTeamsAIPolicy policy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-March 2025 (previously mid-February) 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:]

The new Microsoft PowerShell cmdlets are available now for admins to configure, to ensure a smooth transition.

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-March 2025 (previously mid-February) and is expected to be fully in effect by late March 2025 (previously late February).

[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

If your organization prefers to disable voice and face enrollments, review and update your settings before mid-February 2025.

Important: The EnrollUserOverride setting can be assigned globally, directly to users, or to groups in PowerShell.

Admins must ensure that changes are applied consistently across all these locations to avoid unintended configurations.

Updated January 31, 2025: We have updated the rollout timeline below. Thank you for your patience.

The AI and Copilot Resources Provider that powers the out-of-box (OOB) Microsoft Copilot Academy will be visible by default to users who have Copilot licenses. Admins will be able to enable, disable, and apply permissions to the content of this provider.

This message is associated with Microsoft 365 Roadmap ID 412064.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). 

[How this will affect your organization:]

If a tenant has at least one Copilot license, Knowledge admins or Knowledge managers will be able to view AI and Copilot Resources Provider by default under Admin > Manage providers tab. They can delete and reconfigure as needed.

They can also apply permissions to the content of this provider through Admin >Manage permissions > Provider tab. 

• By default, providers content is visible to Copilot licensed users.
• On applying permissions, the content becomes visible to the selected group.
• On removing permissions, the content returns to the default behavior.

Users with Copilot licenses will also be able to search for AI and Copilot Resources content:

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Updated January 31, 2025: The policy setting is available in Cloud Policy as of January 30, 2025. Currently the policy setting is only available in English. But we’re working on making the localized versions available as soon as we can.

Multiple account access to Copilot in Microsoft 365 desktop and mobile apps will be available soon.

[When will this happen]

General availability (Worldwide): We will begin rolling out in early March 2025 and expect to complete by late March 2025.

Cloud Policy to manage use will be available by late January 2025.

[How this will affect your organization]

As an M365 service, Copilot can be used across signed in accounts in clients that allow you to sign in with multiple accounts. This lets users use their Copilot value on any document to which they have permission. Note that Copilot data protection is always based on the identity used to access the file. This ensures enterprise data protection for files in your organization, regardless of which account grants Copilot access. The setting for web grounding in Copilot is also based on the identity used to access the file. If you disabled web grounding in Copilot, users will not be able to use web grounding even when using Copilot access from another account. This feature will be available starting in March 2025, at which point, users signed into accounts with external Copilot licenses will be able to use Copilot on their work and school documents in Word, Excel, PowerPoint, Outlook and OneNote desktop and mobile apps.

[What you need to do to prepare]

If you wish to restrict multiple account access to Copilot, you can use the “Multiple account access to Copilot for work documents” Cloud Policy.  This policy setting is expected to be available in Cloud Policy by the end of January 2025

[Additional information]

For more information, see Multiple account access to Copilot for work and school documents.

Microsoft Teams will soon have a new location sharing setting that will allow users to grant location access to specific features. This change will affect emergency dynamic policy and the network bandwidth policy.

This message applies to Teams for Windows desktop (version 24H2 or greater) and Teams for Mac desktop. VDI clients will not be supported at this time. [When this will happen:]

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

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

[How this will affect your organization:]

Before this rollout: Location access was governed exclusively at the operating system level. With this update, location consent will also be required from users at the individual application level. As a result, users gain more granular control over which specific application features can access their location.

After this rollout, Teams users can grant location access to certain Teams features. The setting for IT insights for admins feature are in Teams Settings > Privacy > Location. The setting for the Emergency calls feature is in the user’s device’s location settings. The user can find a link to their device’s location settings in Teams Settings > Privacy > Location:

If a user consented to location access before the rollout, the user will be prompted to confirm their selection in this new popup that will display after the next Teams version update. If a user has not previously consented, they will not see the popup and can adjust their preferences in Settings.

[What you need to do to prepare:]

NOTE: After this rollout, dynamic emergency calling may not work as intended unless users allow location detection at the operating system level and app level. This dynamic emergency calling issue includes scenarios where admins have configured a network site for their users (location must be enabled by the user). To ensure emergency calls are properly routed to the nearest public safety answering point (PSAP), please advise your users to accept the new location requests from Teams. This also applies to users who may have consented to location access before the rollout.

You can communicate this requirement by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that end users have location turned on is crucial for proper functioning of emergency calls and their safety. Learn more about sending a custom message: Manage emergency calling policies in Microsoft Teams – Microsoft Teams | Microsoft Learn

To continue managing video and media settings with the network roaming policy, users must enable Insights for IT admins in Teams Settings > Privacy > Location > Insights for IT admins.

Learn more about the changes to location services and privacy policies

• Windows location service and privacy – Microsoft Support
• Enable location sharing – Microsoft Support (will be updated before rollout)

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. Please notify your users and admins about this change and update any relevant documentation.

Coming soon for Microsoft Teams: When you have several peripheral devices connected to Teams, the one you use to answer a call will temporarily become the main device that will sync with Teams when using the device’s buttons. After the call, the original device selected in Teams settings will take over again as the main device. After this rollout, users can use multiple native Bluetooth devices can be confident that call controls will function correctly with all of them.

This message applies to Teams for Windows desktop.

This message is associated with Microsoft 365 Roadmap ID 475853.

[When this will happen:]

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

General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-March 2025 and expect to complete by mid-April 2025.

[How this will affect your organization:]

After this rollout, users will be able to switch between their connected peripheral devices when answering a call without manually changing the selected device in Teams settings. 

This change will be available 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.

Learn more: Phones and Devices for Microsoft Teams – Microsoft Teams | Microsoft Learn

Before rollout, we will update this post with new documentation

Coming soon to new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web: Users can customize folder icon colors, making it easier to visually differentiate and personalize folders.

This message is associated with Microsoft 365 Roadmap ID 472921.

[When this will happen:]

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

General Availability (Worldwide): We will begin rolling out late March 2025 and expect to complete by late March 2025.

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

[How this will affect your organization:]

After this rollout, this feature will be available for all Outlook accounts except for shared mailboxes and shared folders. Colors work for light and dark mode. Note: Some Outlook themes will have low contrast with some folder colors.

To change the color of a folder, a user can hover over the folder name, select the three-dot menu, select Change color and then choose a color.

To turn off the color, follow the same process, and select Automatic.

The folder color will display in the list of folders and in Favorites if the colored folder is added to Favorites.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before or after the rollout. 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.

#newoutlookforwindows

We will retire the video Record feature from the Microsoft 365 Copilot mobile app for Android and iOS starting March 17, 2025, and ending March 31, 2025. Instead, we recommend using the device’s video recording feature.

After the retirement, users will no longer be able to record new videos from the Capture tab but will be able to view and access videos that they have already recorded and saved in their Microsoft OneDrive account or on their device.

This retirement 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.

• Windows 11, version 24H2 
• Cloud solutions for frontline workers 
• Microsoft Pluton Security Processor 
• Microsoft Entra security recommendations 
• Passkeys in Microsoft Authenticator 
• New Microsoft 365 Copilot experiences  
• Previews of Copilot+ PC improvements 
• Other improvements released in December 

• Windows IT Pro Blog 
• Microsoft Security 
• Microsoft Intune Blog 
• Windows Insider Blog 
• Windows 11 update history 
• Release notes for Microsoft 365 Copilot 
• Features removed or no longer developed in Windows Server 

• Deprecation: What it means in the Windows lifecycle
• Microsoft Lifecycle Policy
• Windows client features lifecycle
• Deprecated features for Windows client