The goal of this post is to compile all publicly announced Office 365 service changes for 2019, especially those that may require admin action, into a single reference. These changes are listed below in chronological order, based on the "Action Required" or "Effective" date. Additional information and resources related to these changes are provided where applicable. Updates will be made to this post as new service changes are announced, or updates to announced changes are provided.
Note: All changes may not have been communicated to your tenant / environment.
- Moved Blocking Flash, Shockwave and Silverlight controls in Office 365 Semi-Annual Channel to Archive
- Moved Azure AD credentials will be required for Yammer Enterprise log in to Archive
- Moved OneDrive retiring support for Mac OS X 10.10 and 10.11 to Archive
- Added Office 365 from the Office Portal will not include OneNote 2016 for Semi-Annual Channel Users on Windows 10 - effective February 12, 2019, and moved to Archive
- Added Retiring the Skype for Business Call Analytics (preview) experience - effective February 15, 2019
- Added Retirement of the SharePoint feedback button - effective February 18, 2019
- Added Role-based access to alerts in Office 365 Security - effective February 19, 2019
- Added SharePoint tenant opt-out for modern lists is retiring in 2019 - action required by March 29, 2019
- Updated Retirement of 3DES in Office 365 - action required by February 28, 2019
- Updated Discontinuation of support for Session Border Controllers in Exchange Online Unified Messaging - action now required by December 1, 2019
- Added Azure AD credentials will be required for Yammer Enterprise log in - effective January 31, 2019
- Added OneDrive retiring support for Mac OS X 10.10 and 10.11 - effective February 1, 2019
- Added Retirement of 3DES in Office 365 - effective February 28, 2019
- Added Microsoft StaffHub Retirement - effective October 1, 2019
- Added We're removing Visio web access from SharePoint Online - action required by September 29, 2019
- Added Blocking Flash, Shockwave and Silverlight controls in Office 365 Semi-Annual Channel - effective January 2019
- Added Retirement of Skype for Business app on Windows 10 Mobile - effective December 2019
- Added Discontinuation of support for Session Border Controllers in Exchange Online Unified Messaging - action required by April 30, 2019
- Added Retirement of support for Third-Party Audio Conferencing Providers in Skype for Business Online - action required by April 1, 2019
Retiring the Skype for Business Call Analytics (preview) experience
Effective: February 15, 2019
Details: Skype for Business Call Analytics (preview) is being replaced with new capabilities available in the Microsoft Teams and Skype for business admin center. Administrators will no longer be able to access the Skype for Business Call analytics (preview) once this change is implemented on February 15th, 2019. Instead we recommend searching for a user’s call history from the new Microsoft Teams and Skype for Business admin center -> User Page -> Call History.
Additional Information: Call Analytics and Call Quality Dashboard
Retirement of the SharePoint feedback button
Effective: February 18, 2019
Details: For SharePoint users to easily provide product feedback and suggestions we included a footer link to our UserVoice forums. As we've continued to update the SharePoint user experience, we want to ensure that the options to provide feedback to one's administrator or to Microsoft are clear.
Starting 2/18/2019 we will be removing the feedback button from the footer of SharePoint home and all modern site pages where it currently appears and instead providing options for feedback through the help menu. UserVoice isn’t going away – and your feedback continues to help us prioritize our work! The UserVoice forums will still be available for providing product feedback and suggestions. And we will be adding a new, clearer way to provide feedback from within the product in the coming months.
There is no action required. If you had previously enabled or disabled the button using the Set-SPOTenant -UserVoiceForFeedbackEnabled property this setting will no longer be required as the button will no longer be displayed for any tenant sites. If you are encouraging your users to provide product feedback, please send users directly to the SharePoint UserVoice forums.
Additional Information: SharePoint page enhancements
Role-based access to alerts in Office 365 Security
Effective: February 19, 2019
Details: We’re updating alert policies in the Office 365 Security & Compliance Center with more granular role-based access control. With this feature, admins will have more granular control over which alerts can be viewed by whom in the Office 365 Security & Compliance Center.
Today, when admins go to the View alerts page in the Office 365 Security & Compliance Center, they can see all alerts regardless of the category of alerts if they have the "ManageAlerts" or "ViewOnlyManageAlerts" role. After the release, roles a user has will determine what category of alerts they have access to. For example, a Compliance admin will no longer have access to Threat management or Mail flow alerts, which helps them better focus on triaging and investigating compliance related alerts, like Data governance, Data loss prevention, etc.
We'll be gradually rolling this out to customers starting February 19, 2019 and the roll out will be completed worldwide by the end of March. To see the complete role and category mapping, please review the article linked below in Additional Information.
Additional Information: Alert policies in the Office 365 Security & Compliance Center
Retirement of 3DES in Office 365
Effective: February 28, 2019
Details: As previously communicated (MC124104 in October 2017, MC126199 in December 2017 and MC128929 in February 2018), we are planning to move all of our online services to Transport Layer Security (TLS) 1.2+ to provide best-in-class encryption, and to ensure our service is more secure by default. As part of this plan, we’ll be retiring 3DES beginning February 28, 2019. In order to help you prepare for this change, we have provided reports for you to track your TLS 1.0/1.1 and 3DES usage. Additionally, we have addressed the concerns and questions you have had with these reports.
Starting February 28, 2019, we’ll begin retiring 3DES. This means that all connections to Office 365 using the cipher 3DES will not work. Please keep in mind that Office 365 will NOT retire TLS 1.0/1.1 on February 28, 2019, even though the reports contain information about both TLS 1.0/1.1 and 3DES connections. Expect issues connecting to Office 365 services if you are using 3DES from this date forwards. TLS 1.0/1.1 connections without the 3DES cipher will not be affected.
Ensure that all client-server and browser-server connections, using 3DES to connect to Office 365 services, have been updated. The following provides instructions on how to access the reporting:
- By going to http://securescore.microsoft.com, you can find the overview of your TLS 1.0/1.1 and 3DES usage for Exchange.
- Click on ‘Score Analyzer’ and scroll to the - Remove TLS dependencies tab.
- Here you will see a summary of your TLS 1.0/1.1 and 3DES usage.
- If you want more details on who is connecting using these weaker ciphers and protocols – click on the ‘Get Details’ button that will launch a flyout where you can click on ‘Launch now’.
- This will take you to the Secure Trust Portal (http://servicetrust.microsoft.com) where you can download your user and agent information.
The reports contain the following information:
- Usernames/IP addresses of the users/devices connecting to Exchange using TLS 1.0/1.1 or 3DES
- Which protocol/cipher is being used for the connection - this will either be TLS 1.0/1.1 or 3DES
- The user agent string that is being used for this connection - this gives information about the type of device used for the connection
The report refreshes daily. If you have made any changes and updated any clients/devices, you would need to wait for 24 hours to see this change in the reports. Please review the article in Additional Information for more details.
SharePoint tenant opt-out for modern lists is retiring in 2019
Effective: March 29, 2019
Details: We’re making it easier for users to get to our latest feature updates. Starting April 1, 2019, it will no longer be possible to restrict an entire organization (tenant) to classic mode for lists and libraries. Lists and libraries may still use classic mode using the granular opt-out switches that we provide at the site collection, site, list, and library levels. Additionally, lists that use certain features and customizations that are not supported by modern will still be automatically switched to classic mode.
After April 1, lists and libraries that are in classic mode as a result of tenant opt-out will automatically be shifted to modern. Users will benefit from enhancements and new features such as attention views, PowerApps integration, Flow, column formatting, and the filters pane.
The SharePoint Modernization scanner identifies sites and lists that have customizations that are not supported by modern UI. Although many of these lists will automatically remain in classic mode even after this change, you may wish to keep some sites running entirely in classic to avoid users switching between different experience modes within a single site.
Administrators can use a PowerShell script to enable or disable the modern experience for a single site collection or for a list of site collections as provided by the SharePoint Modernization scanner. Alternately, users can still use the “return to classic” option on modern views of lists or libraries to temporary return to classic, and list owners can use List Settings to configure that list to use the classic experience for all users.
Additional Information: Delivering SharePoint modern experiences
Retirement of support for Third-Party Audio Conferencing Providers in Skype for Business Online
Action Required by: April 1, 2019
Details: Beginning April 1, 2019, we are retiring support of our integration of third-party audio conferencing providers (ACP) in Skype for Business Online Meetings. On April 1, 2019, the following changes will be observed:
- Participants who attempt to join any Skype for Business meeting via dial-in numbers provided by a third-party ACP service will no longer be connected to the Skype for Business meeting
- Users enabled for a third-party ACP service will no longer have their dial-in information automatically included in any new Skype for Business meeting invites
To prepare for this change, we encourage affected organizations to notify their enabled users of this planned update prior to April 1, 2019. After this date, users can continue to use Skype for Business with no interruption to their online meetings; however, organizations will need to enable their users for Audio Conferencing if they require dial-in audio conferencing with Skype for Business or Microsoft Teams.
Depending on the desired end state of the organization, there are three paths that can be followed:
- Migrate to Microsoft Audio Conferencing
- Continue to separately use a third-party audio conferencing provider
- Stop using dial-in conferencing altogether
For more information, please review the details provided at the link below in "Additional Information".
We're removing Visio Web Access from SharePoint Online
Effective: September 29, 2019
Details: Last September, we announced that we would be removing Visio Web access from SharePoint Online. Since then we have listened to your feedback and are extending the timeline to September 2019 to allow more time for the migration of your existing Visio content to the newer platforms.
Beginning September 30, 2019, users in your organization will only be able to view Visio diagrams in their browser, but not create or edit. Visio Online viewing is available to most Office 365 subscriptions.
Additional Information: Migrate from Visio Web Access to Visio Online
Microsoft StaffHub Retirement
Effective: October 1, 2019
Details: Effective October 1, 2019, Microsoft StaffHub will be retired. We're building StaffHub capabilities, including schedule and task management, into Microsoft Teams. The Teams mobile app now includes shift management and a home screen experience. Additional capabilities for firstline workers will roll out to Teams over time. These changes are part of our continued efforts to empower every employee with Microsoft 365. With capabilities for firstline workers now in Teams, every employee in your organization will be able to use Teams to streamline their workday, collaborate with coworkers, and access information and expertise to help them do their best work.
Additional Information: Microsoft Teams for firstline workers
Discontinuation of support for Session Border Controllers in Exchange Online Unified Messaging
Action Required by: December 1, 2019
Details: In July 2017, we announced that support for Session Border Controllers (SBC) that connect third party PBX systems to Exchange Online Unified Messaging (UM) would be discontinued as of July 2018. After feedback from customers and partners concerned about this change, we are announcing additional time for customers to prepare. The new date for discontinuation will be December 1, 2019. Customers with existing deployments remain fully supported until this date. However, Microsoft strongly advises all customers to begin their voicemail transition now.
There are different alternatives for customers currently using an on-premises PBX system that connects to Exchange Online. We recognize that customers may also choose a combination of these options for their organization.
- Office 365 - We belive the best option for customers is to transition to the cloud and use Office 365. This would include the enterprise voice workload and Cloud Voicemail. Customers would use Microsoft Teams for collaboration and voice services.
- Skype for Business Server - In this configuration, customers would deploy an on-premises Skype for Business server and take advantage of the services for voicemail supported by the server.
- Third-Party Voicemail System - With this approach, the customer acquires a third-party voicemail system that provides all the capabilities required to process voicemail and then place it in the user's Exchange mailbox.
- Microsoft Tech Community Discussion
- New date for discontinuation of support for Session Border Controllers in Exchange Online Unified Messaging
Retirement of Skype for Business app on Windows 10 Mobile
Effective: December 2019
Details: The Windows Phone app for Skype for Business is being retired. After this change takes effect, new users will no longer be able to download the app from the Microsoft Store, and the app will no longer be supported. Although Microsoft continues to support Windows 10 Mobile, we are not focused on building new features for the system. We will continue to invest in Skype for Business mobile apps for iOS and Android and also in desktop apps for Windows and Mac.
Existing users of the Windows Phone app for Skype for Business will continue to be able to use the app. Moreover, they will continue to be able to re-download the app from the Windows Store.
Beginning in December 2019, Skype for Business on Windows 10 Mobile, will no longer be available for download.
The Skype for Business app may continue to work after this date, but this is not guaranteed. This app will no longer receive updates or support. If you need to continue using Skype for Business on Windows Phone, we recommend that you install the app before the date cited above.
Additional Information: Windows Phone app for Skype for Business is being retired
Blocking Flash, Shockwave and Silverlight controls in Office 365 Semi-Annual Channel
Effective: January 2019
Details: We are announcing an upcoming change to Office that blocks activation of Flash, Shockwave and Silverlight controls within Office. We are taking this step based on the following factors:
- Use of some of these controls in exploit campaigns to target end users of Office
- Low observed use of these controls within Office
- Upcoming end of support for some of these components (Flash / Silverlight)
Note: This change will not apply to Office 2016, Office 2013 or Office 2010. This change only applies to Office 365 subscription clients in the Semi-Annual Channel and is targeted to take effect in January 2019.
Azure AD credentials will be required for Yammer Enterprise log in
Effective: January 31, 2019
Details: Starting January 31, 2019, Yammer Enterprise users that try to log in using legacy Yammer credentials instead of an Azure Active Directory (AAD) account will be redirected to a new sign up flow and will be asked to create a new password. After completing the required steps, an AAD account with no Office 365 licenses will be automatically created for the user. This process is called self-service signup.
- After changing their password, these users will be able to access your Yammer network, and will have access to all their groups and data. After the AAD account is created for a user, admins can manage the user from the Office 365 admin center.
- After the AAD account is created for a user, admins can manage the user from the Office 365 admin center.
As a Yammer admin, if you want to prevent these users who don’t have Office 365 licenses from accessing your Yammer network, you can choose to enforce Office 365 licenses. For instructions, see Enforce Office 365 identity for Yammer users.
Additional Information: AAD credentials will be required for Yammer Enterprise log in
OneDrive retiring support for Mac OS X 10.10 and 10.11
Effective: February 1, 2019
Details: The OneDrive engineering team is committed to bringing you the best, most secure, end user experience possible. To support that commitment, the OneDrive Desktop application (sync client) will look to phase out support for Mac OS X Yosemite 10.10 and 10.11. These changes will go into effect February 1st, 2019. Note: Mac OS X Yosemite 10.10 has been out of mainline support since August 2017.
- Existing OneDrive sync client installations on unsupported operating systems will stop updating. These clients will continue to run, but functionality will no longer be tested. It is not advised to continue to run on these unsupported operating systems.
- New installations on unsupported operating systems will be blocked.
- Bugs and issues found on or specific to unsupported operating systems will no longer be investigated or fixed.
Additional Information: OneDrive Message Center Updates October 16 - 31, 2018
Office 365 from the Office Portal will not include OneNote 2016 for Semi-Annual Channel Users on Windows 10
Effective: February 12, 2019
Details: In September 2018, Microsoft announced that OneNote for Windows 10 would be the default OneNote experience, and additional information was provided in a blog in April 2018. As we complete our rollout, we are now moving into the final Semi-Annual Channel. If you are not using the Semi-Annual Channel, you can ignore this Message Center post. Starting on Tuesday Feb 12, 2019, OneNote 2016 will not be included by default when a user on the Semi-Annual Channel downloads and installs Office 365 on Windows 10 from the Office Portal.
This change does not affect managed deployments of Office where admins still have full control on whether to include or exclude OneNote 2016. OneNote for Windows 10 is available in the Microsoft Store. If the Store is disabled, we recommend enabling the Microsoft Store for Business, which allows whitelisting approved applications.
If your users still require OneNote 2016, they can still install it. Please see the Additional Information for a help article on installing OneNote 2016 for self-service users.
Additional Information: OneNote 2016 is missing after installing Office 2019 or Office 365