2020 CW 35 Microsoft 365 Message Center changes

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
MC219951	(Updated) Pin based verification process for support callers	2020-11-20T08;00;00Z	2020-12-31T08;00;00Z	N/A
MC220415	(Updated) Admin setting for PSTN participant phone number masking in Teams meetings	2020-10-31T07;00;00Z	2020-11-30T07;00;00Z	N/A
MC219922	(Updated) M365 Records Management: Proof of disposal for records - Roll-out Update	2020-10-10T07;00;00Z	2020-10-30T07;00;00Z	N/A
MC217887	(Updated) Microsoft Teams: New Audio (IPAudioMode) and Video Policies (IPVideoMode)	2020-09-30T07;00;00Z	2020-10-30T07;00;00Z	N/A

MC How Affect changes

MC ID	MC Title	Old Value	New Value	MC Action required by
MC219951	(Updated) Pin based verification process for support callers	We?re adding a PIN-based verification step to our existing phone-based verification process, to better protect your organization. If you contact us from a number not registered with your organization profile, the Microsoft support representative will send a verification code to your registered email or phone in your Admin Center profile. Provide this code to the support representative to grant them access to your organization?s account.	We?re adding a PIN-based verification step to our existing phone-based verification process, to better protect your organization. If you contact us from a number not registered with your Admin center profile, the Microsoft support representative will send a verification code to your registered email or phone in your Admin Center profile. Provide this code to the support representative to grant them access to your organization?s account.	N/A
MC219072	(Updated) Outlook for iOS web view user agent string changes	For most organizations, this change will not affect your users or your authentication flows. However, if your organization is relying on complex claims rules with on-premises (like Active Directory Federation Services) or third-party identity provider solutions that make decisions based on the user agent string, then you will need to update your claims rules to leverage the new user agent string taxonomy that Outlook for iOS with version 4.52.0 and later utilizes. Outlook for iOS utilizes different user agent strings, depending on the scenario. For Exchange Online connections and for Exchange administrators managing mobile device connections, Outlook for iOS utilizes the user agent strings defined in http;//aka.ms/manageom Managing Outlook for iOS and Android in Exchange Online. These user agent strings are not changing. However, for web view requests (like what is used during authentication attempts with identity providers) Outlook for iOS utilizes the following custom, dynamic user agent string format; Outlook-iOS/.prod.iphone () The development build number and AppStore version number changes with each release. For example, for version 4.45.0; Outlook-iOS/725.5057280.prod.iphone (4.45.0) Beginning with version 4.52.0, Outlook for iOS will no longer use this custom, dynamic user agent string for web view requests. Instead, Outlook for iOS will leverage the native web view user agent that is based on the iOS/iPadOS version. As a result, any changes to the user agent string will be controlled by Apple?s operating system releases; iOS; Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 iPadOS; Mozilla/5.0 (iPad; CPU OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 This change ensures that Outlook for iOS provides a consistent authentication experience with other Microsoft mobile apps by utilizing the same user agent string.	For most organizations, this change will not affect your users or your authentication flows. However, if your organization is relying on complex claims rules with on-premises (like Active Directory Federation Services) or third-party identity provider solutions that make decisions based on the user agent string, then you will need to update your claims rules to leverage the new user agent string taxonomy that Outlook for iOS with version 4.52.0 and later utilizes. Outlook for iOS utilizes different user agent strings, depending on the scenario. For Exchange Online connections and for Exchange administrators managing mobile device connections, Outlook for iOS utilizes the user agent strings defined in http;//aka.ms/manageom Managing Outlook for iOS and Android in Exchange Online. These user agent strings are not changing. However, for web view requests (like what is used during authentication attempts with identity providers) Outlook for iOS utilizes the following custom, dynamic user agent string format; Outlook-iOS/<development build number;.prod.iphone (<AppStore Version number;) The development build number and AppStore version number changes with each release. For example, for version 4.45.0; Outlook-iOS/725.5057280.prod.iphone (4.45.0) Beginning with version 4.52.0, Outlook for iOS will no longer use this custom, dynamic user agent string for web view requests. Instead, Outlook for iOS will leverage the native web view user agent that is based on the iOS/iPadOS version. As a result, any changes to the user agent string will be controlled by Apple?s operating system releases; iOS; Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 iPadOS; Mozilla/5.0 (iPad; CPU OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 This change ensures that Outlook for iOS provides a consistent authentication experience with other Microsoft mobile apps by utilizing the same user agent string.	N/A

MC IsMajorChange changes

MC ID	MC Title	Old Value	New Value	MC Action required by
MC220785	New Microsoft Teams meeting pre-join experience	False	True	N/A
MC221075	Outlook for Android: two-way calendar sync support	False	True	N/A
MC221062	Using Microsoft Authentication Library (MSAL) with Yammer Groups API	False	True	12/01/2020
MC220545	(Updated) Improvements to optional diagnostic data collection to better diagnose issues in Office	False	True	N/A

MC Messages changes

MC ID	MC Title	Old Value	New Value	MC Action required by
MC219951	(Updated) Pin based verification process for support callers	We?re adding a PIN-based verification step to our existing phone-based verification process, to better protect your organization. If you contact us from a number not registered with your organization profile, the Microsoft support representative will send a verification code to your registered email or phone in your Admin Center profile. Provide this code to the support representative to grant them access to your organization?s account. When this change will happen; Thursday, August 20, 2020	Updated August 25, 2020; Based on feedback we have updated the timeline and details of the post to provide more clarity. We appreciate your feedback. We?re adding a PIN-based verification step to our existing phone-based verification process, to better protect your organization. If you contact us from a number not registered with your organization profile, the Microsoft support representative will send a verification code to your registered email or phone in your Admin Center profile. Provide this code to the support representative to grant them access to your organization?s account. When this change will happen; September 1, 2020 to November 30, 2020	N/A
MC219072	(Updated) Outlook for iOS web view user agent string changes	We're making some changes to the Outlook for iOS client. On August 24, 2020, we're modifying the web view user agent string that is used during user authentication. Note; If your organization is not utilizing Outlook for iOS or rely on complex claims rules that utilize user agent strings for user authentication, you can disregard this message. Key Points; Timing; August 24, 2020 Action; review and assess	Updated August 25, 2020; We updated the content below to display as intended. We apologize for any confusion. We're making some changes to the Outlook for iOS client. On August 24, 2020, we're modifying the web view user agent string that is used during user authentication. Note; If your organization is not utilizing Outlook for iOS or rely on complex claims rules that utilize user agent strings for user authentication, you can disregard this message. Key Points; Timing; August 24, 2020 Action; review and assess	N/A
MC216379	(Updated) M365 Information Governance: Update to retention labels	We're introducing the ability to have Exchange items support retention labels for which period of retention or deletion is based upon when an item was labeled. Key points; Timing; Initiating release in mid-July and complete for all customers by early August. Rollout; Tenant level Control type; Admin Control Action; Confirm policy expiration date matches your expectation	Updated August 25, 2020; We are pleased to announce that this feature has completed rolling out and is available in your organization as applicable. We're introducing the ability to have Exchange items support retention labels for which period of retention or deletion is based upon when an item was labeled. Key points; Timing; Initiating release in mid-July and complete for all customers by early August. Rollout; Tenant level Control type; Admin Control Action; Confirm policy expiration date matches your expectation	N/A
MC221025	What?s New in the Microsoft Intune Service Update for August	Your MicrosoftIntune account has been updated to the latest service build. How does thisaffect me? You will see theservice release number updated in the Tenant Status blade of the Intune consolesoon. We?ve introduced some changes that we?re excited for you to try out. What do I needto do to prepare for this change? Click additionalinformation below to learn more about what?s new in this service release. We?llcontinue to update the What?s New page with any features that are releasedbetween now and the next monthly service update. More informationon how the Intune service updates each month is in this blog post; https://techcommunity.microsoft.com/t5/intune-customer-success/microsoft-intune-service-updates/ba-p/358728 style=background-color; rgb(255, 255, 255);Microsoft Intune Service Updates Additional Information; http;//aka.ms/intunewhatsnewtoday Intune What's New	Your Microsoft Intune account has been updated to the latest service build. How does this affect me? You will see the service release number updated in the Tenant Status blade of the Intune console soon. We?ve introduced some changes that we?re excited for you to try out. What do I need to do to prepare for this change? Click additional information below to learn more about what?s new in this service release. We?ll continue to update the What?s New page with any features that are released between now and the next monthly service update. More information on how the Intune service updates each month is in this blog post; https://techcommunity.microsoft.com/t5/intune-customer-success/microsoft-intune-service-updates/ba-p/358728 Microsoft Intune Service Updates Additional Information;http;//aka.ms/intunewhatsnewtoday Intune What's New	N/A
MC220415	(Updated) Admin setting for PSTN participant phone number masking in Teams meetings	With MC209349 (April 2020) and MC217648 (July 2020), we added a level of privacy for participants who call in to a Teams meeting via audio conferencing (PSTN) by automatically masking any PSTN participant phone number to users from outside of your organization who might be on the call. We are now adding an admin control for this feature. This message is associated with Microsoft 365 https://www.microsoft.com/microsoft-365/roadmap?filters=searchterms=67091 Roadmap ID 67091. When this will happenWe will begin rolling out this out in early September and expect the rollout to be complete by the end of September.	Updated August 27, 2020; To ensure the best possible experience for our users, we are delaying some of our deployments to reduce the amount of change flowing into the services. Please see the updated roll-out timeline below With MC209349 (April 2020) and MC217648 (July 2020), we added a level of privacy for participants who call in to a Teams meeting via audio conferencing (PSTN) by automatically masking any PSTN participant phone number to users from outside of your organization who might be on the call. We are now adding an admin control for this feature. This message is associated with Microsoft 365 https://www.microsoft.com/microsoft-365/roadmap?filters=searchterms=67091 Roadmap ID 67091. When this will happenWe will begin rolling out this out in early September and expect the rollout to be complete by the end of October (previously September).	N/A
MC219922	(Updated) M365 Records Management: Proof of disposal for records - Roll-out Update	We have completed the roll out of proof of https://docs.microsoft.com/microsoft-365/compliance/disposition disposal for records in SharePoint and OneDrive as we announced in MC212139 (May 2020). However, to ensure the best experience for our customers, we have paused the rollout of this change for email records in Exchange. This message is associated with Microsoft 365 https://www.microsoft.com/microsoft-365/roadmap?filters=searchterms=59217 Roadmap ID 59217. When this will happenWe will update this post when we have resumed the rollout for email records in Exchange.	Updated August 27, 2020; To ensure the best possible experience for our users, we are delaying some of our deployments to reduce the amount of change flowing into the services. Please see the updated roll-out timeline below We have completed the roll out of proof of https://docs.microsoft.com/microsoft-365/compliance/disposition disposal for records in SharePoint and OneDrive as we announced in MC212139 (May 2020). We are ready to continue the rollout of this change for email records in Exchange. This message is associated with Microsoft 365 https://www.microsoft.com/microsoft-365/roadmap?filters=searchterms=59217 Roadmap ID 59217. When this will happenRoll out will continue in late August and complete by the end of September.	N/A
MC217887	(Updated) Microsoft Teams: New Audio (IPAudioMode) and Video Policies (IPVideoMode)	Updated July 31, 2020; To ensure the best possible experience for our users, we are delaying some of our deployments to reduce the amount of change flowing into the services. Please see the updated roll-out timeline below We are adding a new setting to specifically control IP audio (IPAudioMode) as well as a new control for IP video (IPVideoMode) to allow IT administrators more control over how audio and video is managed in Teams meetings and group calls. In November 2019, we proposed changes in internet protocol (IP) policies for both video and audio in Teams meetings and group calls; based on your feedback, we revised the proposed changes. We apologize for any inconvenience that this delay in rollout may have caused. This message is associated with Office 365 https://www.microsoft.com/microsoft-365/roadmap?filters=searchterms=57082 Roadmap ID 57082. When this will happen We'll be gradually rolling this out in mid-August (previously late July). The rollout will be completed at the end of August (previously early August).	Updated August 27, 2020; To ensure the best possible experience for our users, we are delaying some of our deployments to reduce the amount of change flowing into the services. Please see the updated roll-out timeline below We are adding a new setting to specifically control IP audio (IPAudioMode) as well as a new control for IP video (IPVideoMode) to allow IT administrators more control over how audio and video is managed in Teams meetings and group calls. In November 2019, we proposed changes in internet protocol (IP) policies for both video and audio in Teams meetings and group calls; based on your feedback, we revised the proposed changes. We apologize for any inconvenience that this delay in rollout may have caused. This message is associated with Office 365 https://www.microsoft.com/microsoft-365/roadmap?filters=searchterms=57082 Roadmap ID 57082. When this will happen We'll be gradually rolling this out in mid-September (previously mid-August). The rollout will be completed at the end of September (previously end of August).	N/A
MC221062	Using Microsoft Authentication Library (MSAL) with Yammer Groups API	Starting December 1 2020, https://developer.yammer.com/docs/group_membershipsjsongroup_idid target=_blank style=background-color; rgb(255, 255, 255); font-family; sans-serif; font-weight; 400;;Yammer Groups API endpoints will only support the usage of Azure Active Directory (AAD) tokens. Yammer Groups API endpoints will no longer support the usage of https://developer.yammer.com/docs/authentication-1 target=_blank style=background-color; rgb(255, 255, 255); font-family; sans-serif; font-weight; 400;;Yammer OAuth tokens. Microsoft recommends that customers and partners transition to using https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-overview%C2%A0 target=_blank style=background-color; rgb(255, 255, 255); font-family; sans-serif; font-weight; 400;;Microsoft Authentication Library (MSAL) and AAD tokens with the Yammer API. Key Points; Major; Retirement Timing; December 1, 2020 Action; review and assess impact	Starting December 1 2020, https://developer.yammer.com/docs/group_membershipsjsongroup_idid Yammer Groups API endpoints will only support the usage of Azure Active Directory (AAD) tokens. Yammer Groups API endpoints will no longer support the usage of https://developer.yammer.com/docs/authentication-1 Yammer OAuth tokens. Microsoft recommends that customers and partners transition to using https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-overview%C2%A0 Microsoft Authentication Library (MSAL) and AAD tokens with the Yammer API. Key Points; Major; Retirement Timing; December 1, 2020 Action; review and assess impact	12/01/2020
MC220545	(Updated) Improvements to optional diagnostic data collection to better diagnose issues in Office	When a user runs an Office app, such as Word or Excel, diagnostic information is collected and saved to log files on the user?s device. These log files contain information about the processes and components running in the application, and can help detect, diagnose, and fix issues and help make improvements to Office. This information is very similar to optional diagnostic data that may already be collected subject to applicable privacy settings, but is more detailed and helps provide more context about technical issues that might occur when using Office apps. We want to let you know that these log files could be sent to Microsoft only if you have chosen to enable the collection and processing of https://docs.microsoft.com/deployoffice/privacy/optional-diagnostic-data optional diagnostic data by Microsoft. Note that even when you?ve enabled the processing of optional diagnostic data, Microsoft may not always collect these log files. We would process these files only in those situations where we think the additional information could be useful in resolving an issue. Key points; Timing; If you have enabled the collection and processing of optional diagnostic data, it will begin in mid September. Controls; Admin - https://docs.microsoft.com/en-us/deployoffice/privacy/manage-privacy-controls#policy-setting-for-diagnostic-data Policy setting for diagnostic data Action; review and assess impact The change will initially apply to Office on devices running Windows, beginning with Version 2008 of Microsoft 365 Apps in Current Channel. Log files could be sent for the following Office apps; Excel OneNote PowerPoint Word Log files could also be sent for Version 2008 and later of Project and Visio. In the coming months, this change will also apply to Outlook as well as Office running on Mac, iOS, and Android devices. For the latest information about which versions of Office and which operating systems this change applies to, see https://support.microsoft.com/office/fba86aac-70dc-4858-ae1f-ec2034346cdf Overview of diagnostic log files for Office	Updated August 28, 2020; We've updated this post to ensure that it is appropriately visible for organizations. There is no change to the content. When a user runs an Office app, such as Word or Excel, diagnostic information is collected and saved to log files on the user?s device. These log files contain information about the processes and components running in the application, and can help detect, diagnose, and fix issues and help make improvements to Office. This information is very similar to optional diagnostic data that may already be collected subject to applicable privacy settings, but is more detailed and helps provide more context about technical issues that might occur when using Office apps. We want to let you know that these log files could be sent to Microsoft only if you have chosen to enable the collection and processing of https://docs.microsoft.com/deployoffice/privacy/optional-diagnostic-data optional diagnostic data by Microsoft. Note that even when you?ve enabled the processing of optional diagnostic data, Microsoft may not always collect these log files. We would process these files only in those situations where we think the additional information could be useful in resolving an issue. Key points; Timing; If you have enabled the collection and processing of optional diagnostic data, it will begin in mid September. Controls; Admin - https://docs.microsoft.com/en-us/deployoffice/privacy/manage-privacy-controls#policy-setting-for-diagnostic-data Policy setting for diagnostic data Action; review and assess impact The change will initially apply to Office on devices running Windows, beginning with Version 2008 of Microsoft 365 Apps in Current Channel. Log files could be sent for the following Office apps; Excel OneNote PowerPoint Word Log files could also be sent for Version 2008 and later of Project and Visio. In the coming months, this change will also apply to Outlook as well as Office running on Mac, iOS, and Android devices. For the latest information about which versions of Office and which operating systems this change applies to, see https://support.microsoft.com/office/fba86aac-70dc-4858-ae1f-ec2034346cdf Overview of diagnostic log files for Office	N/A
MC221139	Office Scripts enabled by default	In January, we released Office Scripts, a featurethat enables users to automate theirrepetitive tasks in Excel Online, for public preview. We are now transitioning from public preview to making Office Scripts available by default for your organization. Key points Microsoft 365 https://www.microsoft.com/microsoft-365/roadmap?filters=searchterms=61687 Roadmap ID 61687 Timing; targeted release begins the end of August; rollout should be complete the end of October Roll-out; tenant level Control type; admin control Action; review and assess by October 1, 2020	In January, we released Office Scripts, a feature that enables users to automate their repetitive tasks in Excel Online, for public preview. We are now transitioning from public preview to making Office Scripts available by default for your organization. Key points Microsoft 365 https://www.microsoft.com/microsoft-365/roadmap?filters=searchterms=61687 Roadmap ID 61687 Timing; targeted release begins the end of August; rollout should be complete the end of October Roll-out; tenant level Control type; admin control Action; review and assess by October 1, 2020	10/01/2020

MC MessageTagNames changes

MC ID	MC Title	Old Value	New Value	MC Action required by
MC219951	(Updated) Pin based verification process for support callers	Admin impact	Admin impact,Updated message	N/A
MC219072	(Updated) Outlook for iOS web view user agent string changes	Admin impact,User impact	Admin impact,Updated message,User impact	N/A
MC216379	(Updated) M365 Information Governance: Update to retention labels		Updated message	N/A
MC220415	(Updated) Admin setting for PSTN participant phone number masking in Teams meetings	Admin impact,Feature update	Admin impact,Feature update,Updated message	N/A
MC219922	(Updated) M365 Records Management: Proof of disposal for records - Roll-out Update	Admin impact,Feature update	Admin impact,Feature update,Updated message	N/A

MC prepare changes

MC ID	MC Title	Old Value	New Value	MC Action required by
MC219951	(Updated) Pin based verification process for support callers	To help ensure an expedited Support experience, verify your profile email and phone details are updated in the Admin Center.	To help ensure an expedited Support experience, users with appropriate permissions can update their profile contact information in Admin center-;Users-;Active users-;Admin Name-;Manage contact information.'https://admin.microsoft.com/AdminPortal/Home#/users' target='_blank'; Direct link to Active users.	N/A

MC Title changes

MC ID	MC Title	Old Value	New Value	MC Action required by
MC219951	(Updated) Pin based verification process for support callers	Pin based verification process for support callers	(Updated) Pin based verification process for support callers	N/A
MC219072	(Updated) Outlook for iOS web view user agent string changes	Outlook for iOS web view user agent string changes	(Updated) Outlook for iOS web view user agent string changes	N/A
MC216379	(Updated) M365 Information Governance: Update to retention labels	M365 Information Governance; Update to retention labels	(Updated) M365 Information Governance; Update to retention labels	N/A
MC220415	(Updated) Admin setting for PSTN participant phone number masking in Teams meetings	Admin setting for PSTN participant phone number masking in Teams meetings	(Updated) Admin setting for PSTN participant phone number masking in Teams meetings	N/A
MC219922	(Updated) M365 Records Management: Proof of disposal for records - Roll-out Update	M365 Records Management; Proof of disposal for records - Roll-out Update	(Updated) M365 Records Management; Proof of disposal for records - Roll-out Update	N/A
MC220545	(Updated) Improvements to optional diagnostic data collection to better diagnose issues in Office	Improvements to optional diagnostic data collection to better diagnose issues in Office	(Updated) Improvements to optional diagnostic data collection to better diagnose issues in Office	N/A

CW35 New Office 365 Message Center items

MC ID	MC Title	MC Category	MC Workload	MC Major Change	MC Action required by
MC220872	Legacy OME support in Outlook for iOS slated for retirement	Plan For Change	Exchange Online, Microsoft 365 suite	True	N/A
MC220853	Reminder: Office 365 ATP External email forwarding controls and policy change	Plan For Change	Exchange Online, Exchange Online Protection	True	08/28/2020
MC220938	Updates available for Microsoft 365 Apps for Current Channel	Stay Informed	Office Client Applications	False	N/A
MC220931	Seamlessly share personal lists in To Do	Plan For Change	Microsoft 365 suite	True	09/25/2020
MC220987	Introducing live transcription in Microsoft Teams meetings	Stay Informed	Microsoft Teams	False	N/A
MC221025	What?s New in the Microsoft Intune Service Update for August	Stay Informed	Microsoft Intune	False	N/A
MC221015	Forms coming to the Office Mobile App	Stay Informed	Microsoft Forms	False	N/A
MC221062	Using Microsoft Authentication Library (MSAL) with Yammer Groups API	Plan For Change	Yammer Enterprise	True	12/01/2020
MC221075	Outlook for Android: two-way calendar sync support	Stay Informed	Exchange Online	True	N/A
MC221133	Machine learning feedback loop for trainable classifiers now in public preview	Stay Informed	Microsoft 365 suite	False	N/A
MC221125	New service plan for Content explorer	Stay Informed	Microsoft 365 suite	True	N/A
MC221115	Microsoft Search admin navigation name change	Stay Informed	Microsoft 365 suite	False	N/A
MC221113	Final Reminder: Office 365 ATP External email forwarding controls and policy change	Plan For Change	Exchange Online, Exchange Online Protection	True	N/A
MC221108	Search improvements in OneDrive for Business	Stay Informed	OneDrive for Business	False	N/A
MC221139	Office Scripts enabled by default	Plan For Change	Office for the web	True	10/01/2020
MC221134	In Development for Microsoft Intune is now available	Stay Informed	Microsoft Intune	False	N/A

---