2024 CW 44 Microsoft 365 Message Center changes

from 10/28/2024 to 11/03/2024

5 Office 365 Message Center Items were changed and
30 Office 365 Message Center Items were added

Please note: Only common Message Center messages are in this list you should always check your Message Center for additional messages

Subscibe to cloudscout.one Enterprise plan to get individual reports for your Office 365 tenant

Changes

MC End Time changes

MC ID MC Title Old Value New Value MC Action required by
MC888049 (Updated) Microsoft Teams: Enhanced discovery of apps and one-click app installation across Teams 01/06/2025 09:00:00 2025-02-17T09:00:00Z N/A
MC902782 (Updated) Exchange Online token deprecation plan 11/30/2025 09:00:00 2025-12-29T09:00:00Z N/A

MC How Affect changes

MC ID MC Title Old Value New Value MC Action required by
MC905757 Microsoft SharePoint: Customize your individual sites and experiences with fonts and themes Before this rollout: Site owners have limited ability to customize their sites and experiences with branding.

After this rollout, site branding adds an additional option to customize a single site with a unique theme and font package created and managed by the site owners, adding this option to the branding available from your organization and from Microsoft.

Note: Themes will continue to be inherited from the hub for associated sites.

Site owners will be able to create, rename, and delete themes and font packages (where available in a tenant). This will not impact the themes and font packages provided from the organization or from Microsoft.

As communicated in MC905757 Microsoft SharePoint: Customize your individual sites and experiences with fonts and themes (October 2024), we are introducing a new site branding feature for SharePoint. We are adding an additional capability to this feature allowing site owners to copy branding assets utilized in another site for use within their site. This will create an independent copy of these site branding assets in the destination site.

Notes:

Themes will continue to be inherited from the hub for associated sites.

Searching and copying site branding across sites in different geographies is not currently supported.

Site owners will be able to create, rename, and delete themes and font packages (where available in a tenant). This will not have any impact on the themes and font packages provided from the organization or from Microsoft.

Before this rollout: Site owners have limited ability to customize their sites and experiences with branding.

After this rollout, site branding adds an additional option to customize a single site with a unique theme and font package created and managed by the site owners, adding this option to the branding available from your organization and from Microsoft.

Note: Themes will continue to be inherited from the hub for associated sites.

Site owners will be able to create, rename, and delete themes and font packages (where available in a tenant). This will not impact the themes and font packages provided from the organization or from Microsoft.

N/A
MC921916 (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed With OCSI enabled for all tenants, end users will be able to take advantage of features such as autosave, real time user collab, and merging in the case of conflicts of Office files. Autosave is a feature that end users will see in Word, Excel, and PowerPoint files; it is a toggle at the top left of the file header that will ensure that even if the user does not manually save a file, the file will be saved automatically to OneDrive and SharePoint. With real time user collaboration, different users can collaborate on the same file at the same time. Version history allows users to see when and who made changes to a file and provides the ability to restore to a previous version of the file within the Office app. If there are conflicts within a file that does not require user input, Office will merge the conflicts and ensure that the Office file is up to date with the latest changes. If user input is required to merge conflicts, Office will show the merge conflicts and prompt the user to choose which edits to prioritize. With OCSI enabled for all tenants, end users will be able to take advantage of features such as autosave, real time user collab, and merging in the case of conflicts of Office files. Autosave is a feature that end users will see in Word, Excel, and PowerPoint files; it is a toggle at the top left of the file header that will ensure that even if the user does not manually save a file, the file will be saved automatically to OneDrive and SharePoint. With real time user collaboration, different users can collaborate on the same file at the same time. Version history allows users to see when and who made changes to a file and provides the ability to restore to a previous version of the file within the Office app. If there are conflicts within a file that does not require user input, Office will merge the conflicts and ensure that the Office file is up to date with the latest changes. If user input is required to merge conflicts, Office will show the merge conflicts and prompt the user to choose which edits to prioritize. N/A

MC Messages changes

MC ID MC Title Old Value New Value MC Action required by
MC888049 (Updated) Microsoft Teams: Enhanced discovery of apps and one-click app installation across Teams Updated September 27, 2024: We have updated the rollout timeline below. Thank you for your patience.

We are rolling out enhanced app discovery for Microsoft Teams. This rollout allows users to easily discover and use apps that they have previously used in group chats, channels, and meetings, enabling users to consent to use the app everywhere in Teams with one click. This message applies to Teams on Windows and Mac desktops and to Teams on the web.

This message is associated with Microsoft 365 Roadmap ID 397089.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-November 2024 (previously early October) and expect to complete by late November 2024 (previously late October).
Updated October 28, 2024: We have updated the rollout timeline below. Thank you for your patience.

We are rolling out enhanced app discovery for Microsoft Teams. This rollout allows users to easily discover and use apps that they have previously used in group chats, channels, and meetings, enabling users to consent to use the app everywhere in Teams with one click. This message applies to Teams on Windows and Mac desktops and to Teams on the web.

This message is associated with Microsoft 365 Roadmap ID 397089.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-December 2024 (previously mid-November) and expect to complete by early January 2024 (previously late November).
N/A
MC902782 (Updated) Exchange Online token deprecation plan We're contacting you because your tenant uses legacy Exchange Online tokens that are deprecated and Outlook add-ins that still use them will break when tokens are turned off.

Legacy Exchange Online user identity tokens and callback tokens are deprecated and will soon be turned off for all Exchange Online tenants. This is part of Microsoft's Secure Future Initiative to protect orgs in the current threat landscape. If add-ins use legacy tokens to make calls to Exchange, developers need to migrate from Exchange tokens to using Nested App Authentication (NAA) and Entra ID tokens ASAP.

Code changes to add-ins using legacy Exchange Online tokens are required to ensure they continue to work. We recommend you update affected add-ins to use NAA, which provides simple authentication and top tier identity protection through APIs designed specifically for add-ins in Office hosts.

NOTE: This change only applies to Exchange Online; add-ins used in on-premises environments are not impacted by this change.

[Recommended actions:]

Administrators: Identify which add-ins need to be updated and contact the ISVs or developers of those applications to get updates.

Developers: Check the add-in code to see if the related API calls are used and then make appropriate updates.

Register: The updated add-ins require an application registration in Microsoft Azure. Developers need to create an application registration for each add-in. Admins need to consent to the application registration for each add-in's required permissions.

Don't wait: Add-ins are often part of mission critical functions, and the updates will take time to implement. It's best to implement updates well before legacy Exchange Online tokens are turned off.

[When will Microsoft turn off legacy Exchange Online tokens?]

The following table lists the key milestones based on which Office app release channel tenant you're using. Note that the GA date for NAA varies based on channel. We'll soon provide tooling via PowerShell for Microsoft 365 administrators to reenable legacy Exchange tokens for their tenant or specific add-ins if those add-ins are not yet migrated to NAA.

NAA availability for Outlook on Mac, Android, iOS, new Outlook, and Outlook on the web will align with the Microsoft 365 Current Channel release. Support for Work and School accounts as well as Microsoft account will be available for Classic Outlook on Windows, Outlook on Mac, Android, and iOS at GA. Work and School accounts will be supported on new Outlook and Outlook on the web at GA, with Microsoft account support shortly thereafter.

Date ReleaseChannel(s) Legacy tokens status and NAA GA

Oct 2024All channelsNew PowerShell options for enabling/disabling legacy tokens for entire tenant or specific AppIDs.

Oct 2024Current ChannelLegacy tokens turned off for tenants not using them; NAA will GA in Current Channel.

Nov 2024Monthly Enterprise ChannelLegacy tokens turned off for tenants not using them; NAA will GA in Monthly Enterprise Channel.

Jan 2025Current and Semi-Annual ChannelsLegacy tokens turned off for all tenants in Current and Semi-Annual Channels. Admins can reenable via PowerShell. NAA will GA in Semi-Annual Channels.

Feb 2025Monthly Enterprise ChannelLegacy tokens turned off for all tenants in Monthly Enterprise. Admins can reenable via PowerShell.

June 2025Semi-Annual Extended ChannelLegacy tokens off for all tenants in Semi-Annual Extended Channel. NAA will GA in Semi-Annual Extended Channel.

June 2025All channelsAdmins can no longer re-enable legacy tokens via PowerShell; contact Microsoft.

Oct 2025All channelsLegacy tokens turned off for all tenants, there will be no re-enable option.

Note: If a single tenant uses multiple Microsoft 365 apps / Office release channels, Legacy Exchange Online tokens will be turned off based on the "slowest" release channel.

[How do I check which Outlook add-ins are impacted?]

Add-ins may use the legacy Exchange tokens to get resources from Exchange through the EWS or Outlook REST APIs. Sometimes an add-in requires Exchange resources for some use cases and not others, making it difficult to figure out whether the add-in requires an update. We recommend reaching out to add-in developers and owners to ask them if their add-in code references the following APIs:

makeEwsRequestAsync

getUserIdentityTokenAsync

getCallbackTokenAsync

We'll provide tooling via PowerShell for Microsoft 365 admins in October 2024 to turn legacy Exchange tokens on or off in your tenant. This will allow you to test if any add-ins are using Exchange tokens. We'll provide more info when the tooling is ready in the Outlook legacy token deprecation FAQ.

If you rely on an independent software vendor (ISV) for your add-in, we recommend you contact them as soon as possible to confirm they have a plan and a timeline for moving off legacy Exchange tokens. ISV developers should reach out directly to their Microsoft contacts with questions to ensure they're ready for the end of Exchange legacy tokens. If you rely on a developer within your organization, we recommend you ask them to review the Updates on deprecating legacy Exchange Online tokens for Outlook add-ins blog and ask any questions to the Outlook extensibility PM team on the OfficeDev/office-js GitHub issues site.

[How do I keep up with the latest guidance?]

We'll share additional guidance on the Office Add-ins community call, the M365 developer blog, and the Outlook legacy token deprecation FAQ.

Ask questions about NAA and legacy Exchange Online token deprecation on the OfficeDev/office-js GitHub issues site. Please put "NAA" in the title.

Additional resources:

NAA public preview blog

Microsoft 365 developer blog: Updates on deprecating legacy Exchange Online tokens for Outlook add-ins

NAA docs to get started

NAA FAQ

NAA Outlook sample

NAA WXP sample

Updated Oct 30, 2024: We have updated the content.

We're contacting you because your tenant uses legacy Exchange Online tokens that are deprecated and Outlook add-ins that still use them will break when tokens are turned off.

Legacy Exchange Online user identity tokens and callback tokens are deprecated and will soon be turned off for all Exchange Online tenants. This is part of Microsoft's Secure Future Initiative to protect orgs in the current threat landscape. If add-ins use legacy tokens to make calls to Exchange, developers need to migrate from Exchange tokens to using Nested App Authentication (NAA) and Entra ID tokens ASAP.

Code changes to add-ins using legacy Exchange Online tokens are required to ensure they continue to work. We recommend you update affected add-ins to use NAA, which provides simple authentication and top tier identity protection through APIs designed specifically for add-ins in Office hosts.

NOTE: This change only applies to Exchange Online; add-ins used in on-premises environments are not impacted by this change.

[Recommended actions:]

Administrators: Identify which add-ins need to be updated and contact the ISVs or developers of those applications to get updates.

Developers: Check the add-in code to see if the related API calls are used and then make appropriate updates.

Register: The updated add-ins require an application registration in Microsoft Azure. Developers need to create an application registration for each add-in. Admins need to consent to the application registration for each add-in's required permissions.

Don't wait: Add-ins are often part of mission critical functions, and the updates will take time to implement. It's best to implement updates well before legacy Exchange Online tokens are turned off.

[When will Microsoft turn off legacy Exchange Online tokens?]

Microsoft begins turning off legacy Exchange online tokens in February 2025. From now until February 2025, existing and new tenants will not be affected. We'll provide tooling for administrators to reenable Exchange tokens for tenants and add-ins if those add-ins aren't yet migrated to NAA.

DateLegacy tokens status

Feb 2025Legacy tokens turned off for all tenants. Admins can reenable legacy tokens via PowerShell.

Jun 2025Legacy tokens turned off for all tenants. Admins can no longer reenable legacy tokens via PowerShell and must contact Microsoft for any exception

Oct 25Legacy tokens turned off for all tenants. Exceptions are no longer allowed.

[When is NAA generally available for my channel?]

The general availability (GA) date for NAA depends on which channel you are using.

DateNAA General Availability (GA)

Oct 2024LNAA is GA in Current Channel.

Nov 2024NAA will GA in Monthly Enterprise Channel.

Jan 25NAA will GA in Semi-Annual Channel.

Jun 25NAA will GA in Semi-Annual Extended Channel.

[How do I check which Outlook add-ins are impacted?]

From October 30th through mid-November 2024, we'll roll out new tooling via PowerShell for Microsoft 365 administrators to turn legacy Exchange tokens on or off in your tenant. If you find you need to reenable legacy Exchange tokens, you can use the PowerShell cmdlets to do so. The tooling will also report if any add-ins are using legacy tokens over the last 28 days. Once the tooling is available will update the Outlook legacy token deprecation FAQ with additional documentation details.

Add-ins may use the legacy Exchange tokens to get resources from Exchange through the EWS or Outlook REST APIs. Sometimes an add-in requires Exchange resources for some use cases and not others, making it difficult to figure out whether the add-in requires an update. We recommend reaching out to add-in developers and owners to ask them if their add-in code references the following APIs:

makeEwsRequestAsync

getUserIdentityTokenAsync

getCallbackTokenAsync

We'll provide tooling via PowerShell for Microsoft 365 admins in October 2024 to turn legacy Exchange tokens on or off in your tenant. This will allow you to test if any add-ins are using Exchange tokens. We'll provide more info when the tooling is ready in the Outlook legacy token deprecation FAQ.

If you rely on an independent software vendor (ISV) for your add-in, we recommend you contact them as soon as possible to confirm they have a plan and a timeline for moving off legacy Exchange tokens. ISV developers should reach out directly to their Microsoft contacts with questions to ensure they're ready for the end of Exchange legacy tokens. If you rely on a developer within your organization, we recommend you ask them to review the Updates on deprecating legacy Exchange Online tokens for Outlook add-ins blog and ask any questions to the Outlook extensibility PM team on the OfficeDev/office-js GitHub issues site.

[How do I keep up with the latest guidance?]

We'll share additional guidance on the Office Add-ins community call, the M365 developer blog, and the Outlook legacy token deprecation FAQ.

Ask questions about NAA and legacy Exchange Online token deprecation on the OfficeDev/office-js GitHub issues site. Please put "NAA" in the title.

Additional resources:

NAA public preview blog

Microsoft 365 developer blog: Updates on deprecating legacy Exchange Online tokens for Outlook add-ins

NAA docs to get started

NAA FAQ

NAA Outlook sample

NAA WXP sample

N/A
MC902782 (Updated) Exchange Online token deprecation plan Updated Oct 30, 2024: We have updated the content.

We're contacting you because your tenant uses legacy Exchange Online tokens that are deprecated and Outlook add-ins that still use them will break when tokens are turned off.

Legacy Exchange Online user identity tokens and callback tokens are deprecated and will soon be turned off for all Exchange Online tenants. This is part of Microsoft's Secure Future Initiative to protect orgs in the current threat landscape. If add-ins use legacy tokens to make calls to Exchange, developers need to migrate from Exchange tokens to using Nested App Authentication (NAA) and Entra ID tokens ASAP.

Code changes to add-ins using legacy Exchange Online tokens are required to ensure they continue to work. We recommend you update affected add-ins to use NAA, which provides simple authentication and top tier identity protection through APIs designed specifically for add-ins in Office hosts.

NOTE: This change only applies to Exchange Online; add-ins used in on-premises environments are not impacted by this change.

[Recommended actions:]

Administrators: Identify which add-ins need to be updated and contact the ISVs or developers of those applications to get updates.

Developers: Check the add-in code to see if the related API calls are used and then make appropriate updates.

Register: The updated add-ins require an application registration in Microsoft Azure. Developers need to create an application registration for each add-in. Admins need to consent to the application registration for each add-in's required permissions.

Don't wait: Add-ins are often part of mission critical functions, and the updates will take time to implement. It's best to implement updates well before legacy Exchange Online tokens are turned off.

[When will Microsoft turn off legacy Exchange Online tokens?]

Microsoft begins turning off legacy Exchange online tokens in February 2025. From now until February 2025, existing and new tenants will not be affected. We'll provide tooling for administrators to reenable Exchange tokens for tenants and add-ins if those add-ins aren't yet migrated to NAA.

DateLegacy tokens status

Feb 2025Legacy tokens turned off for all tenants. Admins can reenable legacy tokens via PowerShell.

Jun 2025Legacy tokens turned off for all tenants. Admins can no longer reenable legacy tokens via PowerShell and must contact Microsoft for any exception

Oct 25Legacy tokens turned off for all tenants. Exceptions are no longer allowed.

[When is NAA generally available for my channel?]

The general availability (GA) date for NAA depends on which channel you are using.

DateNAA General Availability (GA)

Oct 2024LNAA is GA in Current Channel.

Nov 2024NAA will GA in Monthly Enterprise Channel.

Jan 25NAA will GA in Semi-Annual Channel.

Jun 25NAA will GA in Semi-Annual Extended Channel.

[How do I check which Outlook add-ins are impacted?]

From October 30th through mid-November 2024, we'll roll out new tooling via PowerShell for Microsoft 365 administrators to turn legacy Exchange tokens on or off in your tenant. If you find you need to reenable legacy Exchange tokens, you can use the PowerShell cmdlets to do so. The tooling will also report if any add-ins are using legacy tokens over the last 28 days. Once the tooling is available will update the Outlook legacy token deprecation FAQ with additional documentation details.

Add-ins may use the legacy Exchange tokens to get resources from Exchange through the EWS or Outlook REST APIs. Sometimes an add-in requires Exchange resources for some use cases and not others, making it difficult to figure out whether the add-in requires an update. We recommend reaching out to add-in developers and owners to ask them if their add-in code references the following APIs:

makeEwsRequestAsync

getUserIdentityTokenAsync

getCallbackTokenAsync

We'll provide tooling via PowerShell for Microsoft 365 admins in October 2024 to turn legacy Exchange tokens on or off in your tenant. This will allow you to test if any add-ins are using Exchange tokens. We'll provide more info when the tooling is ready in the Outlook legacy token deprecation FAQ.

If you rely on an independent software vendor (ISV) for your add-in, we recommend you contact them as soon as possible to confirm they have a plan and a timeline for moving off legacy Exchange tokens. ISV developers should reach out directly to their Microsoft contacts with questions to ensure they're ready for the end of Exchange legacy tokens. If you rely on a developer within your organization, we recommend you ask them to review the Updates on deprecating legacy Exchange Online tokens for Outlook add-ins blog and ask any questions to the Outlook extensibility PM team on the OfficeDev/office-js GitHub issues site.

[How do I keep up with the latest guidance?]

We'll share additional guidance on the Office Add-ins community call, the M365 developer blog, and the Outlook legacy token deprecation FAQ.

Ask questions about NAA and legacy Exchange Online token deprecation on the OfficeDev/office-js GitHub issues site. Please put "NAA" in the title.

Additional resources:

NAA public preview blog

Microsoft 365 developer blog: Updates on deprecating legacy Exchange Online tokens for Outlook add-ins

NAA docs to get started

NAA FAQ

NAA Outlook sample

NAA WXP sample

Updated Oct 30, 2024: We have updated the content.

We're contacting you because your tenant uses legacy Exchange Online tokens that are deprecated and Outlook add-ins that still use them will break when tokens are turned off.

Legacy Exchange Online user identity tokens and callback tokens are deprecated and will soon be turned off for all Exchange Online tenants. This is part of Microsoft's Secure Future Initiative to protect orgs in the current threat landscape. If add-ins use legacy tokens to make calls to Exchange, developers need to migrate from Exchange tokens to using Nested App Authentication (NAA) and Entra ID tokens ASAP.

Code changes to add-ins using legacy Exchange Online tokens are required to ensure they continue to work. We recommend you update affected add-ins to use NAA, which provides simple authentication and top tier identity protection through APIs designed specifically for add-ins in Office hosts.

NOTE: This change only applies to Exchange Online; add-ins used in on-premises environments are not impacted by this change.

[Recommended actions:]

Administrators: Identify which add-ins need to be updated and contact the ISVs or developers of those applications to get updates.

Developers: Check the add-in code to see if the related API calls are used and then make appropriate updates.

Register: The updated add-ins require an application registration in Microsoft Azure. Developers need to create an application registration for each add-in. Admins need to consent to the application registration for each add-in's required permissions.

Don't wait: Add-ins are often part of mission critical functions, and the updates will take time to implement. It's best to implement updates well before legacy Exchange Online tokens are turned off.

[When will Microsoft turn off legacy Exchange Online tokens?]

Microsoft begins turning off legacy Exchange online tokens in February 2025. From now until February 2025, existing and new tenants will not be affected. We'll provide tooling for administrators to reenable Exchange tokens for tenants and add-ins if those add-ins aren't yet migrated to NAA.

DateLegacy tokens status

Feb 2025Legacy tokens turned off for all tenants. Admins can reenable legacy tokens via PowerShell.

Jun 2025Legacy tokens turned off for all tenants. Admins can no longer reenable legacy tokens via PowerShell and must contact Microsoft for any exception

Oct 25Legacy tokens turned off for all tenants. Exceptions are no longer allowed.

[When is NAA generally available for my channel?]

The general availability (GA) date for NAA depends on which channel you are using.

DateNAA General Availability (GA)

Oct 2024NAA is GA in Current Channel.

Nov 2024NAA will GA in Monthly Enterprise Channel.

Jan 25NAA will GA in Semi-Annual Channel.

Jun 25NAA will GA in Semi-Annual Extended Channel.

[How do I check which Outlook add-ins are impacted?]

From October 30th through mid-November 2024, we'll roll out new tooling via PowerShell for Microsoft 365 administrators to turn legacy Exchange tokens on or off in your tenant. If you find you need to reenable legacy Exchange tokens, you can use the PowerShell cmdlets to do so. The tooling will also report if any add-ins are using legacy tokens over the last 28 days. Once the tooling is available will update the Outlook legacy token deprecation FAQ with additional documentation details.

Add-ins may use the legacy Exchange tokens to get resources from Exchange through the EWS or Outlook REST APIs. Sometimes an add-in requires Exchange resources for some use cases and not others, making it difficult to figure out whether the add-in requires an update. We recommend reaching out to add-in developers and owners to ask them if their add-in code references the following APIs:

makeEwsRequestAsync

getUserIdentityTokenAsync

getCallbackTokenAsync

We'll provide tooling via PowerShell for Microsoft 365 admins in October 2024 to turn legacy Exchange tokens on or off in your tenant. This will allow you to test if any add-ins are using Exchange tokens. We'll provide more info when the tooling is ready in the Outlook legacy token deprecation FAQ.

If you rely on an independent software vendor (ISV) for your add-in, we recommend you contact them as soon as possible to confirm they have a plan and a timeline for moving off legacy Exchange tokens. ISV developers should reach out directly to their Microsoft contacts with questions to ensure they're ready for the end of Exchange legacy tokens. If you rely on a developer within your organization, we recommend you ask them to review the Updates on deprecating legacy Exchange Online tokens for Outlook add-ins blog and ask any questions to the Outlook extensibility PM team on the OfficeDev/office-js GitHub issues site.

[How do I keep up with the latest guidance?]

We'll share additional guidance on the Office Add-ins community call, the M365 developer blog, and the Outlook legacy token deprecation FAQ.

Ask questions about NAA and legacy Exchange Online token deprecation on the OfficeDev/office-js GitHub issues site. Please put "NAA" in the title.

Additional resources:

NAA public preview blog

Microsoft 365 developer blog: Updates on deprecating legacy Exchange Online tokens for Outlook add-ins

NAA docs to get started

NAA FAQ

NAA Outlook sample

NAA WXP sample

N/A
MC905757 Microsoft SharePoint: Customize your individual sites and experiences with fonts and themes Coming soon for Microsoft SharePoint: Site owners will be able to create font packages and themes for their sites and experiences by combining the branding assets that the organization provides or by creating their own.

The Change the look experience will contain branding created in the SharePoint brand center (or with Microsoft PowerShell) for their organization as well as their own local site branding. These will continue to be previewed and applied via the Change the Look experience for your sites and experiences.

This message is associated with Microsoft 365 Roadmap ID 375500.

[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, GCC, GCC High, DoD): We will begin rolling out early November 2024 and expect to complete by late November 2024.

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

Coming soon for Microsoft SharePoint: Site owners will be able to create font packages and themes for their sites and experiences by combining the branding assets that the organization provides or by creating their own.

The Change the look experience will contain branding created in the SharePoint brand center (or with Microsoft PowerShell) for their organization as well as their own local site branding. These will continue to be previewed and applied via the Change the Look experience for your sites and experiences.

This message is associated with Microsoft 365 Roadmap ID 375500.

[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, GCC, GCC High, DoD): We will begin rolling out early November 2024 and expect to complete by late November 2024.

N/A
MC920179 (Updated) Microsoft Teams: The new streamlined Chat and Channels experience We've been listening to user feedback on the pace of work and the challenges of keeping up with conversations, managing messages scattered across different locations, and triaging quickly. To address this, we've streamlined the chats, teams, and channels experience to make it easier for users to stay on top of what matters most.

For more details and screenshots, refer to Microsoft Teams announces out a new chat and channels experience | Microsoft 365 Blog

This message applies to Teams on Windows desktops, Mac desktops, the web, and iOS and Android devices.

This message excludes Education tenants. We will send a future post with an update on the plan for Education tenants.

This message is associated with Microsoft 365 Roadmap ID 415249.

[When this will happen:]

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

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

General Availability (GCC, GCC High, DoD): We will begin rolling out mid-April 2025 and expect to complete by late April 2025.
Updated October 29, 2024: We have updated the rollout timeline below. Thank you for your patience.

We've been listening to user feedback on the pace of work and the challenges of keeping up with conversations, managing messages scattered across different locations, and triaging quickly. To address this, we've streamlined the chats, teams, and channels experience to make it easier for users to stay on top of what matters most.

For more details and screenshots, refer to Microsoft Teams announces out a new chat and channels experience | Microsoft 365 Blog

This message applies to Teams on Windows desktops, Mac desktops, the web, and iOS and Android devices.

This message excludes Education tenants. We will send a future post with an update on the plan for Education tenants.

This message is associated with Microsoft 365 Roadmap ID 415249.

[When this will happen:]

Updated October 29, 2024: We have updated the rollout timeline below. Thank you for your patience.

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

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

General Availability (GCC, GCC High, DoD): We will begin rolling out mid-April 2025 and expect to complete by late April 2025.
N/A
MC921916 (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed CLONE GALLATIN + AIRGAP

We're removing the EnableAllOcsiClients OneDrive group policy in the Microsoft 365 admin center.

This message is associated with Microsoft 365 Roadmap ID 429874.

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

We're removing the EnableAllOcsiClients OneDrive group policy in the Microsoft 365 admin center. OCSI is the coordination between office and OneDrive for syncing office documents to the cloud.

This message is associated with Microsoft 365 Roadmap ID 429874.
N/A

MC MessageTagNames changes

MC ID MC Title Old Value New Value MC Action required by
MC902782 (Updated) Exchange Online token deprecation plan Admin impact, Retirement Updated message, Admin impact, Retirement N/A
MC920179 (Updated) Microsoft Teams: The new streamlined Chat and Channels experience New feature, User impact Updated message, New feature, User impact N/A
MC921916 (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed User impact, Admin impact Updated message, User impact, Admin impact N/A

MC prepare changes

MC ID MC Title Old Value New Value MC Action required by
MC902782 (Updated) Exchange Online token deprecation plan https://aka.ms/NAAdocs

https://aka.ms/NAAFAQ

https://aka.ms/NAApreviewblog

https://aka.ms/NAAsampleOffice

https://aka.ms/NAAsampleOutlook

https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/

https://devblogs.microsoft.com/microsoft365dev/updates-on-deprecating-legacy-exchange-online-tokens-for-outlook-add-ins/?commentid=1131

https://github.com/OfficeDev/office-js/issues

https://learn.microsoft.com/javascript/api/outlook/office.mailbox?view=outlook-js-preview#outlook-office-mailbox-getuseridentitytokenasync-member(1)

https://learn.microsoft.com/javascript/api/outlook/office.mailbox?view=outlook-js-preview#outlook-office-mailbox-makeewsrequestasync-member(1)

https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens

https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-tokenUn%2Fu0TIrdZt7Lws1LzA%2FtgoU5X8h9ock%3D&reserved=0
https://aka.ms/NAAdocs

https://aka.ms/NAAFAQ

https://aka.ms/NAApreviewblog

https://aka.ms/NAAsampleOffice

https://aka.ms/NAAsampleOutlook

https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/

https://devblogs.microsoft.com/microsoft365dev/updates-on-deprecating-legacy-exchange-online-tokens-for-outlook-add-ins/?commentid=1131

https://github.com/OfficeDev/office-js/issues

https://learn.microsoft.com/javascript/api/outlook/office.mailbox?view=outlook-js-preview#outlook-office-mailbox-getuseridentitytokenasync-member(1)

https://learn.microsoft.com/javascript/api/outlook/office.mailbox?view=outlook-js-preview#outlook-office-mailbox-makeewsrequestasync-member(1)

https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens

https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-tokenUn%2Fu0TIrdZt7Lws1LzA%2FtgoU5X8h9ock%3D&reserved=0

https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens
N/A
MC905757 Microsoft SharePoint: Customize your individual sites and experiences with fonts and themes Admins will need to take no action for this feature to be available. This will be available by default to all site owners without admin action and cannot be disabled.

You may want to notify your users about this change and update any relevant documentation.

https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=375500
Admins will need to take no action for this feature to be available. This will be available by default to all site owners without admin action and cannot be disabled.

You may want to notify your users about this change and update any relevant documentation.

Additional resources

Site branding - Microsoft Support

https://support.microsoft.com/en-us/office/site-branding-43312345-aa4b-495c-95ea-101d7fd5dc1f

https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=375500
N/A

MC Title changes

MC ID MC Title Old Value New Value MC Action required by
MC902782 (Updated) Exchange Online token deprecation plan Exchange Online token deprecation plan (Updated) Exchange Online token deprecation plan N/A
MC920179 (Updated) Microsoft Teams: The new streamlined Chat and Channels experience Microsoft Teams: The new streamlined Chat and Channels experience (Updated) Microsoft Teams: The new streamlined Chat and Channels experience N/A
MC921916 (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed N/A

CW44 New Office 365 Message Center items

MC ID MC Title MC Category MC Workload MC Major Change MC Action required by
MC920310 Introducing Meeting Prep for Financial Services (Preview) Stay Informed Microsoft Teams False N/A
MC920307 Copilot Pages coming to Microsoft Copilot Plan For Change Microsoft 365 suite False N/A
MC920306 Categorize single items in conversation view in new Microsoft Outlook for Windows and web Stay Informed Microsoft 365 for the web, Microsoft 365 apps False N/A
MC920301 Microsoft Viva Engage: Top questions in your communities Stay Informed Microsoft Viva False N/A
MC920300 Microsoft Entra: Enablement of Passkeys in Authenticator for passkey (FIDO2) organizations with no key restrictions Plan For Change Microsoft Entra True 03/03/2025
MC920299 Microsoft Purview | Audit: Enable audit log search for content searches that target Microsoft SharePoint Online Plan For Change SharePoint Online, Microsoft Purview False N/A
MC920298 Microsoft Teams admin center: Admins can disable the ability to send messages in meeting chat before and after a meeting Plan For Change Microsoft Teams False N/A
MC920179 (Updated) Microsoft Teams: The new streamlined Chat and Channels experience Plan For Change Microsoft Teams True N/A
MC920104 Upcoming changes to email service notification recipients Plan For Change Dynamics 365 Apps False 12/01/2024
MC921116 Microsoft Teams: Automatic location updates with building details for BYOD rooms and bookable desks Stay Informed Microsoft Teams False N/A
MC921115 Microsoft Viva Engage: New features for Microsoft 365 Copilot adoption community Stay Informed Microsoft Viva False N/A
MC921113 Support for the Word Mobile, Excel Mobile, and PowerPoint Mobile UWP applications will end on October 14, 2025 Plan For Change Microsoft 365 apps True N/A
MC921112 Microsoft PowerPoint: Web viewer add-in retires December 2024 Plan For Change Microsoft 365 for the web, Microsoft 365 apps True N/A
MC921110 End of Microsoft Places Preview Program Stay Informed Microsoft 365 suite False N/A
MC921105 Product transitions to the cloud.microsoft domain – October 2024 Plan For Change Microsoft 365 suite, Microsoft 365 for the web False N/A
MC921916 (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed Plan For Change OneDrive for Business True N/A
MC921752 Retirement of the SharePoint SendEmail API Plan For Change SharePoint Online, Power Apps in Microsoft 365, Microsoft Power Automate in Microsoft 365 True N/A
MC922633 Microsoft Intune In Development for November 2024 is now available Stay Informed Microsoft Intune False N/A
MC922630 Microsoft OneDrive: We will remove the "EnableHoldTheFile" group policy Plan For Change Microsoft 365 suite, OneDrive for Business True N/A
MC922629 Microsoft Copilot 365 in Viva Glint will support the summarization of employee survey comments Plan For Change Microsoft Viva False N/A
MC922627 Microsoft Copilot extending to Teams and Outlook Plan For Change Microsoft 365 suite, Microsoft Copilot (Microsoft 365) False N/A
MC922626 Microsoft Forms: New streamlined and modernized experience Stay Informed Microsoft Forms False N/A
MC922625 Microsoft Viva Insights: Users can request delegate access Plan For Change Microsoft Viva False N/A
MC922624 Microsoft Viva Engage: Mute conversations in feeds and digests Plan For Change Microsoft Viva False N/A
MC922623 Microsoft new Outlook for Windows and Outlook for the web: Changing how to disable/enable Plan For Change Exchange Online, Microsoft 365 for the web, Microsoft 365 apps True N/A
MC922620 Microsoft Places app ON by default Plan For Change Microsoft 365 apps True N/A
MC922500 Power Automate - Cloud flows are automatically defined in Dataverse solutions Stay Informed Microsoft Power Automate False N/A
MC923419 Microsoft Loop: Configure guest sharing for tenants with sensitivity labels Stay Informed Microsoft 365 for the web False N/A
MC923413 System generated emails from workflows and alerts will now show SharePoint Online as the sender display name Plan For Change SharePoint Online False N/A
MC923176 Microsoft Loop: Sensitivity labels at the container level Plan For Change Microsoft 365 apps False N/A

Share to MS Teams

Login to your account

Welcome Back, We Missed You!