The goal of this post is to compile all publicly announced Office 365 service changes per month in 2019, especially those that may require admin action. 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.
- Added Outlook on the web – New experience roll out – effective July 22, 2019
Retirement of 3DES in Office 365
Action Required By: July 9, 2019
Details: Starting July 10, 2019, Office 365 will begin retiring the 3DES cipher. This means that all connections to Office 365 using the cipher 3DES will not work. TLS 1.0/1.1 connections without the 3DES cipher will not be affected. Client software and devices that rely on the 3DES cipher to connect to Office 365 should be updated or replaced prior to July 10, 2019.
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 which devices or clients are 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 Service Trust Portal where you can download your user and agent information.
Please review the information linked below for more guidance details.
- Preparing to use TLS 1.2 in Office 365
- Preparing for 3DES Retirement in Office 365 Skype for Business
- Encryption in Office 365
- Solving the TLS 1.0 Problem, 2nd Edition
Microsoft Teams coming to existing installs of Office 365 ProPlus and Office 365 Business / Business Premium (Monthly Channel)
Effective: July 9, 2019
Details: Starting July 9th, the Teams client will be added to existing installations on the Monthly Channel, and as a modern online service, Teams will continue to auto-update on a regular cadence.
As part of the Teams deployment, admins now have the ability to disable the initial auto-start of Teams. Teams starts automatically by default.
Note: If you decide to change this behavior, you must do it before Teams is deployed.
If Teams is already installed in a user’s machine, they are not impacted by this change.
While we strongly encourage you to adopt Teams, we enable you to deploy at your own pace. If you wish to exclude it from your installation or disable auto-start of Teams, you are fully in control. You can find guidance on deploying Teams as a part of Office 365 ProPlus: Deploy Microsoft Teams with Office 365 ProPlus.
Retirement of Public website 3rd party link from the M365 Admin Center
Effective: July 15, 2019
Details: Once the link within the Admin center is removed, administrators should work directly with their Microsoft partner or a 3rd party website provider to create and host a public website. We’ll be gradually rolling this change out starting on July 15, 2019 and the change will be complete by the end of August.
Additional Information: Use a public website with Office 365
Outlook on the web – New experience roll out
Effective: July 22, 2019
Details: Starting on July 22, 2019, the new Outlook on the web will become the default experience for Mail, Calendar and People and we will remove the opt-in toggle. With this change users will not be able to move back or see the classic experience. This change will override the PowerShell command which previously blocked the opt-in toggle.
Note: The toggle removal does not affect Tasks. If you blocked the opt-in toggle using PowerShell, you won’t see any changes in Tasks. If you have not blocked the opt-in toggle, then users will continue to see the opt-in toggle.
We will start rolling out the new Outlook on the web as the default experience on July 22, 2019 to Targeted Release customers, and following with non-Targeted Release customers on August 3, 2019. The roll out will be completed for all customers by the end of September 2019.
This enhancement is related to Microsoft 365 Roadmap ID 49202.
Additional Information: Faster, with a modern design, and new features – the new Outlook on the web is here
Support for Data Privacy communications in Message Center
Action Required by: July 26, 2019
Details: Message Center is being updated to support the communication of messages related to the privacy or security of the Microsoft 365 service to a restricted set of recipients. Once implemented, only the Global Admin and newly added Message Center Privacy Reader role will have access to these messages.
The new Privacy Reader role is available now. Starting July 26th, privacy/security communications in Message Center will only be available to the Global administrator or individuals assigned to the Privacy Reader role.
Global admins or users assigned the new Message Center Privacy Reader role will be able to filter the view in Message Center to see Data Privacy messages and configure data privacy specific email preferences. Due to the potential sensitivity of the information being communicated in posts related to privacy or security, related email notifications and API content will contain general information with a link back to the Message Center to view the relevant details.
Note: Email notifications are not available within GCC at this time.
If your organization needs to comply with GDPR or HIPAA regulations, we recommend that the person assigned to this Message Center Privacy Reader role also be responsible for overseeing your organization’s data protection strategy and GDPR/HIPAA compliance implementation.
Please review the links below to learn more about communications in Message Center.