2021 CW 40 Microsoft 365 Message Center changes

from 09/27/2021 to 10/03/2021

14 Office 365 Message Center Items were changed and 21 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 Action Required By changes

MC ID MC Title Old Value New Value MC Action required by
MC283912 (Updated) Yammer Public Links API Changes 2021-11-30T09:00:00Z 2022-03-01T09:00:00Z 03/01/2022

MC End Time changes

MC ID MC Title Old Value New Value MC Action required by
MC283912 (Updated) Yammer Public Links API Changes 2022-01-01T09:00:00Z 2022-04-30T10:00:00Z 03/01/2022
MC268191 (Updated) Meeting Join Custom Branding 2021-10-15T09:00:00Z 2021-11-30T08:00:00Z N/A
MC273627 (Updated) Manage the health of Microsoft Teams Rooms devices 2021-10-31T08:00:00Z 2021-11-12T08:00:00Z N/A
MC274185 (Updated) Microsoft Stream: Viewing the transcript for a Microsoft Teams meeting recording 2021-10-31T08:00:00Z 2021-11-30T08:00:00Z N/A
MC277112 (Updated) Introducing background effects on web 2021-10-29T09:00:00Z 2021-11-30T08:00:00Z N/A
MC285602 (Updated) OneDrive: New Command Bar 2021-10-30T09:00:00Z 2021-11-20T08:00:00Z N/A
MC265759 (Updated) Microsoft Defender for Office 365: Extending Secure by Default for Exchange Transport Rules (ETRs) 2021-10-31T08:00:00Z 2021-11-30T08:00:00Z N/A
MC266077 (Updated) SharePoint Collapsible Sections 2021-10-31T08:00:00Z 2021-11-30T08:00:00Z N/A
MC277639 (Updated) Microsoft 365 roadmap site updates 2021-10-31T08:00:00Z 2021-11-20T08:00:00Z N/A
MC286780 (Updated) Content from camera now launched in Teams 2021-11-06T08:00:00Z 2021-12-10T08:00:00Z N/A
MC287353 (Updated) Hardware Support for AJA and Blackmagic Devices 2021-11-01T08:00:00Z 2021-12-31T08:00:00Z N/A

MC How Affect changes

MC ID MC Title Old Value New Value MC Action required by
MC283912 (Updated) Yammer Public Links API Changes On December 1, 2021, the following API calls will be affected by this change:
GET api/v1/open_graph_objects?url=https://
If you are using GET api/v1/open_graph_objects?url=https:// - then currently this returns one single OGO id. Once this change is released it will return a list of OGO ids as now each time a link or URL is added to a message it generates a new OGO id.
GET /messages/open_group_objects/[:id].json
If you are using GET /messages/open_group_objects/[:id].json - then after the change you can use any of the OGO ids associated with a URL and this API will return a feed of messages that the user has access to relating to that link.
POST /message.json
If you are using POST /message.json - and the og_url is a SharePoint URL, you will need to call this API using an AAD token. Instructions to obtain an AAD token can be found here. Additionally, if using a SharePoint URL do not pass a thumbnail image URL to og_image as Yammer fetches the thumbnail associated with the SharePoint URL.
Phase 1 (November 1st, 2021) - No breaking change to GET api/v1/open_graph_objects?url=https://
After November 1st, we will add a list consisting of a single OGO (which is the same OGO currently being returned by the API) to the response of GET api/v1/open_graph_objects?url=https:// - this is unlikely to affect your usage of this API, but we still recommending checking how you are consuming the API before the change happens.
Here is an example of what the response of the API will look like:
{
"id": 12345,
...,
"ogos": [{
"id": 12345,
....
}]
}
Phase 2 (February 1st, 2022) – No breaking change to GET api/v1/open_graph_objects?url=https://

Then on February 1st, 2022, all public Open Graph Objects (OGOs) will be associated with only the message it is attached to. These links, and the messages associated with them, are only visible to users who have access to the conversations the Open Graph Objects were a part of.
Previously, there was only one OGO in each Yammer Network per absolute URL. Now there will be multiple OGOs that exist because this new change will create one OGO per message the URL is attached to.
GET api/v1/open_graph_objects?url=https:// - will return, in the existing field, any OGO id from the list. In the new field, it will return the full list of OGOs for that url.
Phase 3 (March 1st, 2022) – Breaking change to GET api/v1/open_graph_objects?url=https://
Following this, on or after March 1st, 2022 you will experience changes to the following APIs:
GET api/v1/open_graph_objects?url=https://
If you are using GET api/v1/open_graph_objects?url=https:// - this API will change to only return a list of the OGO ids. Here is an example of what the response of the API will look like:
{
"ogos": [{
"id": 12345,
....
}, {
"id": 67890,
....
}]
}
GET /messages/open_group_objects/[:id].json

If you are using GET /messages/open_group_objects/[:id].json - then after the change you can use any of the OGO ids associated with a URL and this API will return a feed of messages that the user has access to relating to that link.
Note: If you have not developed custom integration with Yammer or use 3rd party software which includes specific API calls, you can safely ignore this message.
Other Updates (available now)
In addition, if you are using the POST /message.json API and the og_url is a SharePoint URL, to receive a response with metadata for the URL you will need to call this API using an AAD token. Instructions to obtain an AAD token can be found here. Additionally, if using a SharePoint URL do not pass a thumbnail image URL to og_image as Yammer fetches the thumbnail associated with the SharePoint URL.

03/01/2022
MC277112 (Updated) Introducing background effects on web Web users will now have the ability to use background effects for video calls. You can manage the Video effects policy via PowerShell or via the Tenant Admin dashboard. Web users will now have the ability to use background effects for video calls. You can manage the Video effects policy via Powershell or via the Tenant Admin dashboard. N/A
MC277639 (Updated) Microsoft 365 roadmap site updates The below changes are coming to help your organization better organize and manage key information on the the Microsoft 365 roadmap.
UI changes
See last added will be removed from the header and can be accessed in the filters, under New/updated
Filters will be moving just below the header image, inline with the search bar, so it’s easier to view your selected filters and if you have search turned on
The features will be displayed on feature cards, as opposed to a table format, in order to optimize space and make information easier to view
You will be able to sort the feature cards by either preview date or Generally Available (GA) date
Status will be represented visually on the feature card to save space and make it easier to perform a quick scan
Feature cards will be easier to collapse if you want to explore looking at the status, title, and preview and GA dates
On the feature card;
you will be able to see tags organized by category (product, release phase, platform, cloud instance)
you will be able to initiate a feedback submission (the feedback experience does not change)
Mobile view – the same changes will be applicable in mobile view so you can easily view, sort, filter, and search
API changes
Preview date will be a new data point available to you
The filters or tags will be prefaced by a category name

Understanding the new Preview data
Not all features will have public previews, however when a public preview date is available, it will be displayed
The status of a roadmap item (In Development, Rolling Out or Launched) will be in relation to the GA date and not the preview date
The Preview data will be available and the roadmap item’s description will be updated to read, “This item is currently available in Public Preview” when the following is true:
Roadmap item has a Preview Tag, Preview Date and we are in the Preview Month

The below changes are coming to help your organization better organize and manage key information on the the Microsoft 365 roadmap.
UI changes
See last added will be removed from the header and can be accessed in the filters, under New/updated
Filters will be moving just below the header image, inline with the search bar, so it’s easier to view your selected filters and if you have search turned on
The features will be displayed on feature cards, as opposed to a table format, in order to optimize space and make information easier to view
You will be able to sort the feature cards by either preview date or Generally Available (GA) date as well as by oldest to newest
Status will be represented visually on the feature card to save space and make it easier to perform a quick scan
Feature cards will be easier to collapse if you want to explore looking at the status, title, and preview and GA dates
On the feature card;
you will be able to see tags organized by category (product, release phase, platform, cloud instance)
you will be able to initiate a feedback submission (the feedback experience does not change)
Mobile view – the same changes will be applicable in mobile view so you can easily view, sort, filter, and search
API changes
Preview date will be a new data point available to you
The filters or tags will be prefaced by a category name

Understanding the new Preview data
Not all features will have public previews, however when a public preview date is available, it will be displayed
The status of a roadmap item (In Development, Rolling Out or Launched) will be in relation to the GA date and not the preview date
The Preview data will be available and the roadmap item’s description will be updated to read, “This item is currently available in Public Preview” when the following is true:
Roadmap item has a Preview Tag, Preview Date and we are in the Preview Month
Below is a sample of the updated JSON format enabling both the new preview dates and the categories for the various tags
{
"id": 68731,
"title": "Microsoft Teams: Microsoft Graph API for Teams Export (Preview)",
"description": "Enterprise Information Archiving (EIA) for Microsoft Teams is a key scenario for our customer as it allows them to solve for retention, indexing, e-discovery, classification, and regulatory requirements. The Teams Export API allows the export of Teams Messages (1:1 and group chat) along with attachments (file links and sticker), emojis, GIFs and user @Mentions. This API supports polling daily Teams messages and allows archiving of deleted messages up to 30 days.",
"status": "In development",
"moreInfoLink": null,
"publicRoadmapStatus": "Include this month",
"tags": [
{
"tagName": "Microsoft Teams",
"tagCategoryId": 1
},
{
"tagName": "Web",
"tagCategoryId": 2
},
{
"tagName": "",
"tagCategoryId": 3
},
{
"tagName": "Worldwide (Standard Multi-Tenant)",
"tagCategoryId": 4
}
],
"created": "2020-09-22T16:34:04.613Z",
"modified": "2021-08-31T23:29:25.33Z",
"publicDisclosureAvailabilityDate": "September CY2021",
"publicPreviewDate": "April CY2021"
},

N/A
MC288051 (Updated) Upcoming Changes to Auto-Expanding Archive Once this limit takes effect, your users will not be able to extend their online archives beyond 1.5TB. As currently noted in our documentation, auto-expanding archive is only supported for mailboxes used for individual users or shared mailboxes with a growth rate that does not exceed 1 GB per day. Using journaling, transport rules, or auto-forwarding rules to copy messages to Exchange Online Archiving for the purposes of archiving is not permitted. A user's archive mailbox is intended for just that user. Microsoft reserves the right to deny unlimited archiving in instances where a user's archive mailbox is used to store archive data for other users or in other cases of inappropriate use.
If you have previously worked with Microsoft Support to provide exceptions for existing archives exceeding 1.5TB, those specific archives will not be affected by this change. You will not, however, be able to create any new archives that exceed 1.5TB.
Once this limit takes effect, your users will not be able to extend their online archives beyond 1.5TB. As currently noted in our documentation, auto-expanding archive is only supported for mailboxes used for individual users or shared mailboxes with a growth rate that does not exceed 1 GB per day. Using journaling, transport rules, or auto-forwarding rules to copy messages to Exchange Online Archiving for the purposes of archiving is not permitted. A user's archive mailbox is intended for just that user. Microsoft reserves the right to deny auto-expanding archiving in instances where a user's archive mailbox is used to store archive data for other users or in other cases of inappropriate use.
If you have previously worked with Microsoft Support to provide exceptions for existing archives exceeding 1.5TB, those specific archives will not be affected by this change. You will not, however, be able to create any new archives that exceed 1.5TB.
N/A

MC Messages changes

MC ID MC Title Old Value New Value MC Action required by
MC283912 (Updated) Yammer Public Links API Changes We're making some changes to public OGOs (Open Graph Objects).
On December 1, 2021, all public Open Graph Objects (OGOs) will be associated with only the message it is attached to. These links, and the messages associated with them, are only visible to users who have access to the conversations the Open Graph Objects were a part of.
Previously, there was only one OGO in each Yammer Network per absolute URL. Now there will be multiple OGOs that exist because this new change will create one OGO per message the URL is attached to.
Note: If you have not developed custom integration with Yammer or use 3rd party software which includes specific API calls, you can safely ignore this message.
[Key points]
Timing: December 1, 2021
Control type: admin control
Action: review and assess
Updated September 27, 2021: We have updated this message with additional details for clarity. Thank you for your feedback.
We're making some changes to public OGOs (Open Graph Objects) over the next two quarters. The effected APIs are:
GET api/v1/open_graph_objects?url=https://
GET /messages/open_group_objects/[:id].json
[Key points]
Timing: March 1, 2022
Control type: admin control
Action: review and assess
03/01/2022
MC268191 (Updated) Meeting Join Custom Branding Updated August 03, 2021: We have updated the rollout timeline below. Thank you for your patience. Additionally, this feature will be available as a preview until December 31, 2021. After that, an Advanced Communications license is required to continue using this feature, as noted below.
This new release of meeting Join Custom Branding will allow tenant admins to upload their company logo to the Teams admin portal so it appears on the meeting pre-join and lobby screens for meetings organized by members of their tenant.
The logo will be seen by users joining on desktop, web, and mobile.
This message is associated with Microsoft 365 Roadmap ID 79957.
[When this will happen:]
Rollout will begin at the end of August and be complete in early September (previously late July).
Updated September 28, 2021: We have updated the rollout timeline below. Thank you for your patience. Additionally, this feature will be available as a preview until December 31, 2021. After that, an Advanced Communications license is required to continue using this feature, as noted below.
This new release of meeting Join Custom Branding will allow tenant admins to upload their company logo to the Teams admin portal so it appears on the meeting pre-join and lobby screens for meetings organized by members of their tenant.
The logo will be seen by users joining on desktop, web, and mobile.
This message is associated with Microsoft 365 Roadmap ID 79957.
[When this will happen:]
Rollout will begin at the mid-October (previously end of August) and be complete at the end of October (previously early September).
N/A
MC273627 (Updated) Manage the health of Microsoft Teams Rooms devices This coming feature update will allow you to control the impact of peripherals on the health of Microsoft Teams Rooms (Windows) devices. You will obtain visibility into how peripheral issues affect the health, and experience of the meeting room devices. Before this update, the health evaluation was done by the Teams admin center system. With the new feature, you will be able to customize the health evaluation to what is best for your organization.
This feature will not impact any legacy configuration or setup of your organization.
[When this will happen:]
We will begin rolling this out in late August and expect to complete rollout early September.
Updated September 28, 2021: We have updated the rollout timeline below. Thank you for your patience.
This coming feature update will allow you to control the impact of peripherals on the health of Microsoft Teams Rooms (Windows) devices. You will obtain visibility into how peripheral issues affect the health, and experience of the meeting room devices. Before this update, the health evaluation was done by the Teams admin center system. With the new feature, you will be able to customize the health evaluation to what is best for your organization.
This feature will not impact any legacy configuration or setup of your organization.
[When this will happen:]
We will begin rolling this out in late August and expect to complete rollout early October (previously early September).
N/A
MC274185 (Updated) Microsoft Stream: Viewing the transcript for a Microsoft Teams meeting recording This, Microsoft Stream, new release will allow the end user to view the transcript for a Microsoft Teams meeting recording in the transcript pane next to the video player.
This message is associated with Microsoft 365 Roadmap ID 82057.
[When this will happen:]
Targeted release (entire org): will begin rolling this out in early August and expect to complete rollout early September.
Standard release: will begin rolling this out in late August and expect to complete rollout late September.
Updated September 28, 2021: We have updated the rollout timeline below. Thank you for your patience.
This, Microsoft Stream, new release will allow the end user to view the transcript for a Microsoft Teams meeting recording in the transcript pane next to the video player.
This message is associated with Microsoft 365 Roadmap ID 82057.
[When this will happen:]
Targeted release (entire org): will begin rolling this out in early August and expect to complete rollout early September. - complete
Standard release: will begin rolling this out in early October (previously late August) and expect to complete rollout late October (previously late September).
N/A
MC277112 (Updated) Introducing background effects on web Introducing background effects on web. If you want to change what appears behind you in your video meeting or call, you can either blur your background or replace it entirely with any image you want.
Note: Blurring or replacing your background might not prevent sensitive information from being visible to other people in the call or meeting.
This message is associated with Microsoft 365 Roadmap ID 85738
[When this will happen:]
We expect this rollout to begin in early September and expect the rollout to be completed by late September
Updated September 28, 2021: We have updated the rollout timeline below. Thank you for your patience.
Introducing background effects on web. If you want to change what appears behind you in your video meeting or call, you can either blur your background or replace it entirely with any image you want.
Note: Blurring or replacing your background might not prevent sensitive information from being visible to other people in the call or meeting.
This message is associated with Microsoft 365 Roadmap ID 85738

[When this will happen:]

We expect this rollout to begin in early October (previously early September) and expect the rollout to be completed by late October (previously late September)

N/A
MC285602 (Updated) OneDrive: New Command Bar With this update users will be able to easily identify the right file and access primary commands. The new simplified view will permit users to focus on the content while at the same time being visually pleasing.
This message is associated with Microsoft 365 Roadmap ID 85602.
[When this will happen:]
Targeted release (entire org): Will begin rolling out in mid-September and expect to be complete in late September.
Standard release: Will begin rolling out in late September and expect to be complete in early October.
Note: Some users may see this feature before other users within your organization.
Updated September 28, 2021: We have updated the rollout timeline below. Thank you for your patience.
With this update users will be able to easily identify the right file and access primary commands. The new simplified view will permit users to focus on the content while at the same time being visually pleasing.
This message is associated with Microsoft 365 Roadmap ID 85602.
[When this will happen:]
Targeted release (entire org): Will begin rolling out in mid-September and expect to be complete in late September.
Standard release: Will begin rolling out in late September and expect to be complete in mid-October (previously early October).
Note: Some users may see this feature before other users within your organization.
N/A
MC286779 (Updated) Image Utility Edit Control A set of utility tools to quickly fix and format an image on OneDrive for Business will soon be available. Capabilities will include; rotate, crop (freeform crop and fixed aspect ratio crop), and flip (horizontally and vertically).
The update will also include a set of commonly used adjustments to adjust the quality of the photograph to change the look. This feature will be available as sliders for users to increase/decrease the intensity of each adjustment. Adjustments are additive to each other, and users can adjust individual slider and see the direct result on the enlarged image.
Note: Currently, only Jpeg and Jpg file are supported. The feature is going to support PNG files soon.
This message is associated with Microsoft 365 Roadmap ID 85625.
[When this will happen:]
We expect this to begin rolling out in late September, and expect the rollout to be completed by late October.
Updated September 28, 2021: We have updated the message to ensure it is visible to all impacted organizations. Thank you for your patience.
A set of utility tools to quickly fix and format an image on OneDrive for Business and SharePoint Online will soon be available. Capabilities will include; rotate, crop (freeform crop and fixed aspect ratio crop), and flip (horizontally and vertically).
The update will also include a set of commonly used adjustments to adjust the quality of the photograph to change the look. This feature will be available as sliders for users to increase/decrease the intensity of each adjustment. Adjustments are additive to each other, and users can adjust individual slider and see the direct result on the enlarged image.
Note: Currently, only Jpeg and Jpg file are supported. The feature is going to support PNG files soon.
This message is associated with Microsoft 365 Roadmap ID 85625.
[When this will happen:]
We expect this to begin rolling out in late September, and expect the rollout to be completed by late October.
N/A
MC286990 (Updated) Exchange Online and Basic Auth – September 2021 Update We're making some changes to improve the security of your tenant. We announced in 2019 we would be retiring Basic Authentication for legacy protocols, and in early 2021 we announced we would begin to retire Basic Authentication for protocols not being used in tenants, but not disable Basic Authentication for any in-use protocols until further notice.
Today, we are announcing that we are restarting the program to end the use of Basic Auth in Exchange Online. Beginning October 1, 2022, we will begin to disable Basic Auth in all tenants, regardless of usage.
We previously communicated this change via several Message Center posts: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20) and MC237741 (Feb. ‘21) and you can always read the latest information about our plans to turn off Basic Authentication here.
Beginning early 2022, as we roll out the changes necessary to support this effort, we are also going to begin disabling Basic Auth for some customers on a short-term and temporary basis.
We will randomly select tenants and disable Basic Auth for all protocols for a period of 12-48 hours. After this time, these protocols will be re-enabled, if the tenant admin has not already re-enabled them using our self-service tools.
During this time all clients and apps that use Basic Auth in that tenant will be affected, and they will be unable to connect. Any client or app using Modern Auth will not be affected. Users can use alternate clients (for example, Outlook on the Web instead of an older Outlook client that does not support Modern Auth) while they upgrade or reconfigure their client apps.
Updated September 27, 2021: We have updated the content for additional clarity. Thank you for your feedback.
We're making some changes to improve the security of your tenant. We announced in 2019 we would be retiring Basic Authentication for legacy protocols, and in early 2021 we announced we would begin to retire Basic Authentication for protocols not being used in tenants, but not disable Basic Authentication for any in-use protocols until further notice.
Today, we are announcing that, effective October 1, 2022, we will begin to permanently disable Basic Auth in all tenants, regardless of usage (with the exception of SMTP Auth, which can still be re-enabled after that).
We previously communicated this change via several Message Center posts: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20) and MC237741 (Feb. ‘21) and you can always read the latest information about our plans to turn off Basic Authentication here.
Beginning early 2022, as we roll out the changes necessary to support this effort, we are also going to begin disabling Basic Auth for some customers on a short-term and temporary basis.
We selectively pick tenants and disable Basic Auth for all affected protocols except SMTP AUTH for a period of 12-48 hours. After this time, Basic Auth for these protocols will be re-enabled, if the tenant admin has not already re-enabled them using our self-service tools.
During this time all clients and apps that use Basic Auth in that tenant will be affected, and they will be unable to connect. Any client or app using Modern Auth will not be affected. Users can use alternate clients (for example, Outlook on the Web instead of an older Outlook client that does not support Modern Auth) while they upgrade or reconfigure their client apps.
10/22/2022
MC265759 (Updated) Microsoft Defender for Office 365: Extending Secure by Default for Exchange Transport Rules (ETRs) Updated August 24, 2021: We have updated the content for additional clarity. Thank you for your feedback.
Microsoft believes it’s critical to keep our customers secure by default. We have determined that legacy overrides tend to be too broad and cause more harm than good. As a security service, we believe it's imperative that we act on your behalf to prevent your users from being compromised. This means these legacy overrides will no longer be honored for email messages we believe are malicious. We already apply this approach with malware messages and now we have extended it to messages with high confidence phish verdicts. We have been taking a very deliberate approach to rolling out these changes in phases to ensure customers are not surprised and there are no negative side effects. We began to rollout Secure by Default for high confidence phishing messages by the override type starting in December 2020 (Roadmap ID 60827). Today, we’re at a point in our Secure by Default journey where the following overrides are not honored for malicious emails (malware or high confidence phish emails):

Allowed sender lists or allowed domain lists (anti-spam policies)
Outlook Safe Senders
IP Allow List (connection filtering)
We are now extending Secure by Default to cover high confidence phishing messages for the remaining legacy override type, Exchange mail flow rules (also known as transport rule or ETRs).
[Key Points]
Timing: We will begin rolling out Secure by Default for ETRs starting at the end of August (previously early August) and complete rollout by end of September (previously early September).
Action: Review and assess impact.

Updated September 30, 2021: We have updated the rollout timeline below. Thank you for your patience.
Microsoft believes it’s critical to keep our customers secure by default. We have determined that legacy overrides tend to be too broad and cause more harm than good. As a security service, we believe it's imperative that we act on your behalf to prevent your users from being compromised. This means these legacy overrides will no longer be honored for email messages we believe are malicious. We already apply this approach with malware messages and now we have extended it to messages with high confidence phish verdicts. We have been taking a very deliberate approach to rolling out these changes in phases to ensure customers are not surprised and there are no negative side effects. We began to rollout Secure by Default for high confidence phishing messages by the override type starting in December 2020 (Roadmap ID 60827). Today, we’re at a point in our Secure by Default journey where the following overrides are not honored for malicious emails (malware or high confidence phish emails):

Allowed sender lists or allowed domain lists (anti-spam policies)
Outlook Safe Senders
IP Allow List (connection filtering)
We are now extending Secure by Default to cover high confidence phishing messages for the remaining legacy override type, Exchange mail flow rules (also known as transport rule or ETRs).
[Key Points]
Timing: We will begin rolling out Secure by Default for ETRs starting at the end of August (previously early August) and complete rollout by end of October (previously the end of September).
Action: Review and assess impact.

N/A
MC266077 (Updated) SharePoint Collapsible Sections Updated August 24, 2021: We have updated the rollout timeline below. While in Targeted Release we received valuable feedback around the behavior of anchor links when used in collapsible sections as well as some formatting issues experienced by users of right-to-left languages. We feel that both of these issues are important for us to address prior to making the feature generally available. We are actively addressing these issues now and expect the solution to reach General Availability with all fixes in place by the end of September 2021. Thank you for your patience.
This new feature will allow users to create rich, information-dense SharePoint pages. As part of this release, we will enable the page author to configure sections within the SharePoint page to be able to expand, collapse and set the default page-load state for the section.
This message is associated with Microsoft 365 Roadmap ID 67147.
[When this will happen:]
We will begin rolling out to Targeted release (select users and organization) in early July (complete) and expect to be complete for Standard release in late September (previously late July).
Updated September 30, 2021: As shared previously, the new Collapsible Sections was deployed to 100% of Targeted Release customers. We held the solution at the Targeted Release phase while we addressed some issues that were reported with the solution. The issues have now been addressed and we will be resuming the global rollout to all customers. It is now our expectation that we’ll complete the rollout of the feature by the end of October 2021. Thank you for your patience.
This new feature will allow users to create rich, information-dense SharePoint pages. As part of this release, we will enable the page author to configure sections within the SharePoint page to be able to expand, collapse and set the default page-load state for the section.
This message is associated with Microsoft 365 Roadmap ID 67147.
[When this will happen:]
We will begin rolling out to Targeted release (select users and organization) in early July and expect to be complete for Standard release in late October (previously late September).
N/A
MC277639 (Updated) Microsoft 365 roadmap site updates Updated September 10, 2021: We have updated the rollout timeline below. Thank you for your patience.
We will be making updates to the Microsoft 365 roadmap on how you view, filter, search for, and sort the information.
[When this will happen:]
We will roll this out in late September (previously early September).
Updated September 30, 2021: We have updated the rollout timeline below and provided additional details. Thank you for your patience.
We will be making updates to the Microsoft 365 roadmap on how you view, filter, search for, and sort the information.
[When this will happen:]
We will roll this out in mid-October (previously late September).
N/A
MC286780 (Updated) Content from camera now launched in Teams As hybrid workplaces become more common, we're excited to let you know that content from camera will soon be available in Microsoft Teams. This option enables users to stream content from directly from physical artefacts such as whiteboards and documents in a legible way. During a Teams call, users will be able to access the projection options simply by clicking Share > Content from camera.
Two key projection options:
Whiteboard mode: Users can point their laptop webcam to their whiteboard to project it to their audience. If the camera detects a whiteboard in view, it is straightened, zoomed in and the presenter's hand or body does not block the content as she writes on it.
Document mode: Users can attach an external USB camera, such as a document camera, mounted over a document, to project to their audience.
This message is associated with Microsoft 365 Roadmap ID 86062.
[When this will happen:]
We will begin rolling this out in late September and expect to complete rollout by early October.
Updated September 30, 2021: We have updated the rollout timeline below. Thank you for your patience.
As hybrid workplaces become more common, we're excited to let you know that content from camera will soon be available in Microsoft Teams. This option enables users to stream content from directly from physical artefacts such as whiteboards and documents in a legible way. During a Teams call, users will be able to access the projection options simply by clicking Share > Content from camera.
Two key projection options:

Whiteboard mode: Users can point their laptop webcam to their whiteboard to project it to their audience. If the camera detects a whiteboard in view, it is straightened, zoomed in and the presenter's hand or body does not block the content as she writes on it.
Document mode: Users can attach an external USB camera, such as a document camera, mounted over a document, to project to their audience.
This message is associated with Microsoft 365 Roadmap ID 86062.
[When this will happen:]
We will begin rolling this out in mid-October (previously late September) and expect to complete rollout by late of October (previously early October).

N/A
MC287353 (Updated) Hardware Support for AJA and Blackmagic Devices The ability for Teams clients to stream content from a client to the local network via Network Device Interface (NDI) is being expanded to enable streaming content to select attached hardware devices. Users with the ability to turn on NDI will also be able to push content to attached hardware devices from AJA or Blackmagic Designs. This will enable users to push content from Teams out via attached SDI or HDMI devices.

This message is associated with Microsoft 365 Roadmap ID 82812 & 83486

[When this will happen:]

We expect to roll this out in late September and expect the rollout to be complete by mid-October.

Updated September 30, 2021: We've updated the rollout timeline below. Thank you for your patience.
The ability for Teams clients to stream content from a client to the local network via Network Device Interface (NDI) is being expanded to enable streaming content to select attached hardware devices. Users with the ability to turn on NDI will also be able to push content to attached hardware devices from AJA or Blackmagic Designs. This will enable users to push content from Teams out via attached SDI or HDMI devices.

This message is associated with Microsoft 365 Roadmap ID 82812 & 83486

[When this will happen:]

We expect to roll this out in in late October (previously late September) and expect the rollout to be complete by mid-November (previously mid-October).

N/A
MC288051 (Updated) Upcoming Changes to Auto-Expanding Archive We will be removing the word ‘Unlimited’ from our service description and related public documentation for the auto-expanding archiving feature, and instituting a 1.5TB limit for archive mailboxes. This limit is not configurable.
[Key points]
Timing: This change will take effect beginning November 1, 2021 and is applicable to all environments.
Roll-out: tenant level
Action: review and assess
Updated September 30, 2021: We have updated the content below for additional clarity. Thank you for your patience.
We will be removing the word ‘Unlimited’ from our service description and related public documentation for the auto-expanding archiving feature, and instituting a 1.5TB limit for archive mailboxes. This limit is not configurable.
[Key points]
Timing: This change will take effect beginning November 1, 2021 and is applicable to all environments.
Roll-out: tenant level
Action: review and assess
N/A

MC MessageTagNames changes

MC ID MC Title Old Value New Value MC Action required by
MC283912 (Updated) Yammer Public Links API Changes Feature update, Admin impact Updated message, Feature update, Admin impact 03/01/2022
MC273627 (Updated) Manage the health of Microsoft Teams Rooms devices Feature update, Admin impact Updated message, Feature update, Admin impact N/A
MC274185 (Updated) Microsoft Stream: Viewing the transcript for a Microsoft Teams meeting recording New feature, User impact Updated message, New feature, User impact N/A
MC277112 (Updated) Introducing background effects on web Feature update, User impact, Admin impact Updated message, Feature update, User impact, Admin impact N/A
MC285602 (Updated) OneDrive: New Command Bar New feature, User impact Updated message, New feature, User impact N/A
MC286779 (Updated) Image Utility Edit Control New feature, User impact Updated message, New feature, User impact N/A
MC286780 (Updated) Content from camera now launched in Teams New feature, User impact, Admin impact Updated message, New feature, User impact, Admin impact N/A
MC287353 (Updated) Hardware Support for AJA and Blackmagic Devices Feature update, User impact Updated message, Feature update, User impact N/A
MC288051 (Updated) Upcoming Changes to Auto-Expanding Archive 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
MC277112 (Updated) Introducing background effects on web https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=85738 https://www.microsoft.com/en-ww/microsoft-365/roadmap?filters=&searchterms=85738 N/A

MC Title changes

MC ID MC Title Old Value New Value MC Action required by
MC283912 (Updated) Yammer Public Links API Changes Yammer Public Links API Changes (Updated) Yammer Public Links API Changes 03/01/2022
MC273627 (Updated) Manage the health of Microsoft Teams Rooms devices Manage the health of Microsoft Teams Rooms devices (Updated) Manage the health of Microsoft Teams Rooms devices N/A
MC274185 (Updated) Microsoft Stream: Viewing the transcript for a Microsoft Teams meeting recording Microsoft Stream: Viewing the transcript for a Microsoft Teams meeting recording (Updated) Microsoft Stream: Viewing the transcript for a Microsoft Teams meeting recording N/A
MC277112 (Updated) Introducing background effects on web Introducing background effects on web (Updated) Introducing background effects on web N/A
MC285602 (Updated) OneDrive: New Command Bar OneDrive: New Command Bar (Updated) OneDrive: New Command Bar N/A
MC286779 (Updated) Image Utility Edit Control Image Utility Edit Control (Updated) Image Utility Edit Control N/A
MC286990 (Updated) Exchange Online and Basic Auth – September 2021 Update Exchange Online and Basic Auth – September 2021 Update (Updated) Exchange Online and Basic Auth – September 2021 Update 10/22/2022
MC286780 (Updated) Content from camera now launched in Teams Content from camera now launched in Teams (Updated) Content from camera now launched in Teams N/A
MC287353 (Updated) Hardware Support for AJA and Blackmagic Devices Hardware Support for AJA and Blackmagic Devices (Updated) Hardware Support for AJA and Blackmagic Devices N/A
MC288051 (Updated) Upcoming Changes to Auto-Expanding Archive Upcoming Changes to Auto-Expanding Archive (Updated) Upcoming Changes to Auto-Expanding Archive N/A

CW40 New Office 365 Message Center items

MC ID MC Title MC Category MC Workload MC Major Change MC Action required by
MC287809 Removal of Wi-Fi MAC address on personally-owned work profile devices and device administrator Android 9 Plan For Change Microsoft Intune False N/A
MC287944 Viva Learning general availability Plan For Change Microsoft 365 suite True N/A
MC288050 Microsoft 365 Compliance Center: Core and Advanced eDiscovery: Enhanced Keyword Query Language (KQL) editor experience Stay Informed Microsoft 365 suite False N/A
MC288051 (Updated) Upcoming Changes to Auto-Expanding Archive Plan For Change Exchange Online True N/A
MC288052 Reminder: IE11 desktop application retires in 9 months on June 15, 2022 – Set up IE mode today (non-LTSC, non-Server) Plan For Change Microsoft 365 Apps False 06/15/2022
MC288054 Configuration Change: Power BI app for Microsoft Teams automatic installation and availability for government customers Plan For Change Power BI, Microsoft Teams True N/A
MC288055 CART Caption support in Microsoft Teams Meetings Plan For Change Microsoft Teams False N/A
MC288066 Updates available for Microsoft 365 Apps for Current Channel Stay Informed Microsoft 365 Apps False N/A
MC288218 Attack Simulation Training lighting up in new regions Stay Informed Exchange Online False N/A
MC288400 Dynamics 365 – Service Update 21094 for EUR Stay Informed Dynamics 365 Apps False N/A
MC288467 Peer5 now available for Teams Live Events Stay Informed Microsoft Teams False N/A
MC288469 What’s New in the Microsoft Intune Service Update for September 2021 Stay Informed Microsoft Intune False N/A
MC288472 Reminder: Update to Microsoft 365 and Outlook for Windows connectivity Plan For Change Exchange Online, Microsoft 365 Apps True 11/01/2021
MC288473 Known Issue: Users unable to update Android Company Portal from Huawei AppGallery Prevent Or Fix Issue Microsoft Intune False N/A
MC288489 Update to user enrollment experience in Autopilot Stay Informed Microsoft Intune False N/A
MC288630 Exchange online auto-expanding archive–Automatic archive of mailbox items in Purges,Versions and Discovery Holds folders Stay Informed Exchange Online False N/A
MC288633 M365 Records Management, Information Governance & eDiscovery– Optimized behavior of file versions preserved in SPO & ODB Plan For Change Microsoft 365 suite, SharePoint Online True N/A
MC288634 Project for the web and Project Operations – Popups required when using task view in a PowerApps Plan For Change Project for the web False N/A
MC288636 The Attack Simulation Training landing page is now customizable Stay Informed Microsoft 365 suite False N/A
MC288642 OneDrive and SharePoint: Improved Move/Copy user experience Stay Informed SharePoint Online, OneDrive for Business False N/A
MC288686 In Development for Microsoft Intune is now available Stay Informed Microsoft Intune False N/A

Login to your account

Welcome Back, We Missed You!