Stay on top of M365 changes
Keep track of upcoming changes, including new and changed features, planned maintenance, or other important announcements.
In March ’20 we sent MC207028 advising customers that Microsoft will start to notify users in Outlook that they can get Outlook for iOS and Android for certain customers in select markets. This message is to let you know that this change now applies to customers worldwide including customers that: Subscribed to education Office 365 and Microsoft 365 plans Are in the European Union and European Economic Area Key points: Timing: August 12, 2020 Control: Admin control via PowerShell for Outlook on the web Action: review and assess With deep integration across OneDrive, Teams and Office apps, Outlook is the best way to experience Microsoft 365 on a mobile device. Outlook mobile integrates Microsoft 365 enterprise-grade security to protect company data for a mobile workforce with built in protection against viruses, spam, phishing attacks and other threats. Many customers are not aware they can get additional functionality and commercial use rights to Outlook mobile as part of their Office 365 and Microsoft 365 services at no extra cost. Note: These changes do not apply for customers subscribed to government Office 365 and Microsoft 365 plans. How this affects your organization: Users who use Outlook with their work or school accounts but are not using Outlook mobile may see a notice that they can get Outlook for their phone. If they dismiss the notice or start to use Outlook mobile, the notification will not reappear. A quick link or scannable code will be provided to simplify downloading the app to the mobile device of their choice. What you need to do to prepare: If you prefer that users in your organization do not see notifications about Outlook mobile in Outlook on the web, you can block these notifications by using the MobileAppEducationEnabled cmdlet control. In a later release, this same cmdlet will be able to manage notifications in Outlook for Windows too but for now, you can complete this form to submit your request to block these notifications in Outlook for Windows. You will need to provide your tenant ID. Requests will take 7 days to take effect (you will not receive a confirmation that your request has been received or processed).
We are adding new Power Platform features to make it easier for customers to create, deploy and manage key business apps and chatbots directly within Microsoft Teams. This message is associated with Microsoft 365 Roadmap ID 66407. When this will happen The rollout will begin in mid-August and be complete by the end of August. How this will affect your organization Select Microsoft 365 and Office 365 subscriptions that include Power Apps and Power Automate are expanding with the introduction of Microsoft Dataflex – a built-in, flexible datastore supporting relational, image and file data with a one-click experience for deploying solutions natively in Teams. Your users will be able to access these public preview features in Teams beginning in mid-August. With Dataflex, Power Apps will provide an integrated app studio that lets users build and deploy custom apps within Teams. Your end users will also be able to build and deploy custom chatbots in Teams with the introduction of Power Virtual Agents. We are also adding Power Automate capabilities, including the ability to trigger flows directly from Teams messages. This new Power Platform functionality for Teams is included at no additional cost with your Microsoft 365 and Office 365 licenses. Existing Power Platform functionality available for use in Office 365 more broadly outside of Teams remains unchanged. What you need to do to prepare Once this update is complete, you will see new service plans – Microsoft Dataflex and Power Virtual Agents for Teams – in the list of plans included with your subscription. These changes will not impact other features in your subscription, besides what is mentioned above. However, you may consider updating your internal documentation to reflect these additional capabilities, as needed. The following admin controls are available in Teams Admin center to enable/disable the new functionality in public preview – App permissions policies: Admins can turn the Power Platform maker/builder experience off or on in Teams by selecting Power Apps and/or Power Virtual Agents applications available under ‘Microsoft Apps’. This setting is available for a specific set of users or for the tenant all up. More information on App permissions policies can be found here – Manage app permission policies in Microsoft Teams Note: Admin controls to enable/disable new Power Platform deployment capabilities in Teams will not be available by public preview. This control will be introduced by GA in the Teams admin center. Existing Power Platform functionality within Office 365 remains unchanged.
As Microsoft Teams has become the core communications client for Microsoft 365, this is a reminder the Skype for Business Online service will retire July 31, 2021.At that point, access to the service will end. Note: Neither the Skype consumer service nor Skype for Business Server deployments will be affected by the retirement of the Skype for Business Online service. Current Skype for Business Online customers will experience no change in service up to the retirement date. Support for the integration of third-party party Audio Conferencing Providers (ACP) into Skype for Business Online will continue through the end of service July 31, 2021. How does this affect me? You are receiving this message because your organization may be using Skype for Business Online. While your organization will no longer be able to use Skype for Business Online once the service is retired 12 months from now, you may continue to use Microsoft Teams as part of your existing Microsoft 365 licensing agreement. What do I need to do to prepare for this change? We encourage customers using Skype for Business Online to plan and begin the upgrade to Teams today. To help, Microsoft offers comprehensive transition resources including a proven upgrade framework, guidance for technical and organizational readiness, free instructor-led training, and FastTrack onboarding assistance for eligible subscriptions. Please click Additional Information to learn more.
Teams already provides live captions as a way to follow along with what is being said in a meeting. We will soon add speaker attribution to captions so that everyone knows who is speaking. This message is associated with Microsoft 365 Roadmap ID 65949. When this will happen We will begin a gradual rollout in mid-August and expect the rollout to be complete by the end of August. How this will affect your organization Live captions improved accessibility of Microsoft Teams. Identifying who is speaking when there are multiple speakers in a meeting makes live captions more useful and improves comprehension. Note: Remarks made by participants joining from a conference room device will be attributed to the room rather than to an individual in the room. What you need to do to prepare Live captions with speaker attribution is available in new meeting and calling experiences.
As communicated previously in MC198427 (Dec ’19) Office 2016 for Mac and Office 2010 will reach their end of support on October 13, 2020. After this date, Microsoft will no longer provide technical support, bug fixes, or security updates for Office 2016 for Mac and Office 2010. You will still be able to use these versions of Office, but over time, organizations may face an increase in security risks and compliance issues. Also, as previously announced, after October 13, 2020, customers will need to be running Microsoft 365 Apps, Office 2019 or Office 2016 to connect to Office 365 services. Microsoft will not take any active measures to block legacy versions of the Office client from connecting to Office 365 services, but these older clients may encounter performance and/or reliability issues over time. For related Office client support timelines, see the Microsoft 365 and Office system requirements matrix. Key Points: Major: Retirement Timing: October 13, 2020 Action: review and assess [How this will affect your organization:] If your organization is still running Office 2016 for Mac or Office 2010 after October 13, 2020, they will no longer receive technical support, security fixes, or bug fixes from Microsoft. If your organization is running any Office client older than Office 2016, Microsoft will not take any active measures to block them from connecting to Office 365 services. However, legacy clients attempting to connect to a modern, always-up-to-date cloud service may experience performance and reliability issues. Customers will face an increased security risk, and may find themselves out of compliance depending on specific regional or industry requirements. Microsoft Help may not be able to resolve issues that arise due to unsupported service connections. [What you need to do to prepare:] Because of the changes listed above, we strongly recommend that you upgrade to one of the latest versions of Office as soon as possible: Microsoft 365 Apps, the subscription version of Office that comes with most Office 365 enterprise plans. Microsoft 365 Apps can be installed on up to five PCs or Macs, five tablets, and five mobile devices. Office 2019, which is a one-time purchase and available for one PC or Mac per license. A key difference between Microsoft 365 Apps and Office 2019 is that Microsoft 365 Apps is updated on a regular basis with new features. Office 2019 has the same set of features that it had when it was released in October 2018. Prior to deploying either version, please check the System requirements for Microsoft 365 and Office as well as the Microsoft 365 and Office system requirements matrix to ensure that the version you choose is supported on the operating system you are using. In order to identify users on Office 2010 and Office 2013 clients, deploy Microsoft 365 Apps or a supported non-subscription version of Office to those desktops, and ensure that they will have supported access to Office 365 services after October 13, 2020, there are two Microsoft Endpoint Configuration Manager dashboards (updated as part of version 1902) that you can use: the Configuration Manager Product Lifecycle dashboard allows you to see which versions of Office are running on your desktops, to determine which will need updated Office apps to help ensure a seamless connection to Office 365 services the Microsoft 365 Apps Upgrade Readiness report on the Office 365 client management dashboard helps to identify desktops in your organization that are ready to upgrade to Microsoft 365 Apps. Additional information: Office 2010 end of support roadmap. End of Support for Office 2016 for Mac Deployment guide for Office for Mac Office versions and connectivity to Office 365 services Microsoft 365 and Office system requirements matrix Microsoft Office End of Support Tech Community
We’re adding the ability for admin to manage OneDrive storage limits for individual users in the Microsoft 365 admin center. This message is associated with Microsoft 365 Roadmap ID 65148 When this will happen This change has begun rolling out and will be complete by the end of July 2020. How this will affect your organization Admins will be able to manage OneDrive storage limits for individual users who have OneDrive enabled using the Microsoft 365 admin center. Admins can configure OneDrive storage settings by clicking Edit under Storage on the OneDrive tab of the user details. What you need to do to prepare You may consider updating your training and documentation as appropriate.
We’re changing the default tenant policy setting for Teams inline message translation. Key points Timing: early August; complete mid-August Roll-out: tenant level Control type: admin control Action: review and assess by August 3, 2020. How this will affect your organization If you have not previously customized the messaging policy for your tenant or assigned your users a custom messaging policy, message translation will be enabled by default. Users in tenants where message translation is enabled will be able to translate chat or channel messages by clicking “Translate” from the message actions menu. Currently, message translation is available for Teams desktop client and the Teams web app. It recently rolled out for the Teams iOS app (MC216842, May 2020). What you need to do to prepare If you have not previously customized the default messaging policy or assigned your users a custom messaging policy, message translation will be enabled by default. If you do not want users in your tenant to be able to access or use message translation, you must proactively set the policy to disable message translation by August 3, 2020. The specific setting is: TeamsMessagingPolicy.AllowUserTranslation
With this feature, users will have a file sharing and access control experience in Teams that is similar to their experience with other Microsoft 365 apps. Key points Microsoft 365 Roadmap ID 51230 Timing: mid-August; complete mid-September Roll-out: tenant level Control type: admin control Action: review and assess How this will affect your organization With this update, when users share a file from within Teams, they will have the option to create sharing links that provide access to anyone, people within your organization, people with existing access or specific people, including those in a 1:1 chat, group chat, or channels. Before users share a file in a chat and channels, they will be notified if recipients don’t have permission to view the file. The user can change permissions before they share the file (if they have permission to do so). What you need to do to prepare Teams honors the sharing controls defined in SharePoint. For example, if external sharing is disabled in SharePoint, then it is disabled in Teams as well. The default file link permission in Teams will be the same that is set at Tenant level, unless it is over ridden at site level. Review your file sharing options in the SharePoint admin portal to ensure that they align with the requirements in your tenant.
Support for Office 2016 and Office 2019 connections to Office 365 cloud services will continue until October 2023. Up to date information on current system requirements can be found under on the Office system requirements page, with related timelines available in the Office system requirements matrix. How does this affect me? Microsoft will not take any active measures to block older Office clients, such as Office 2013 and Office 2010, from connecting to Office 365 services. However, legacy clients attempting to connect to a modern, always up- to- date cloud service may experience performance and reliability issues. Customers will face an increased security risk, and may find themselves out of compliance depending on specific regional or industry requirements. Microsoft Help may not be able to resolve issues that arise due to unsupported service connections. What do I need to do to prepare for this change? In order for you to better understand whether and how your organization is affected by this change, and where you need to migrate users, there are two System Center Configuration Manager dashboards (updated as part of version 1902) that can help: the SCCM Product Lifecycle dashboard allows you to see which versions of Office are running on your desktops, to determine which will need updated Office apps to help ensure a seamless connection to Office 365 services the Office 365 ProPlus Upgrade Readiness report on the Office 365 client management dashboard helps to identify desktops in your organization that are ready to upgrade to Office 365 ProPlus with high confidence. Use these dashboards to identify users on Office 2010 and Office 2013 clients, deploy Office365 ProPlus or a supported version of Office perpetual to those desktops, and ensure that they will have supported access to Office 365 services after October 13, 2020.
You can enable Data Loss Prevention (DLP) to automatically block external access to new files in SharePoint Online and OneDrive for Business until those files have been fully scanned for sensitive information. This message is associated with Microsoft 365 Roadmap 34247. When this will happen We will roll this out the end of June; we expect the rollout to be complete by mid-July. How this will affect your organization This capability is available for all new files uploaded to both OneDrive and SharePoint. When new files are added to SharePoint or OneDrive in Microsoft 365, it takes time for them to be crawled and indexed. It takes additional time for the DLP policy to scan the content and apply rules to protect sensitive content. Currently, if external sharing is turned on, sensitive content could be shared and accessed by guests before any Office DLP rule completes its processing. By treating all new files as sensitive until they have been scanned, this feature gives a Global or SharePoint admin the ability to block guest accounts from accessing files until the DLP completes its scan. If the file has no sensitive content based on the DLP policy, then guests can access the file. If the policy identifies a file with sensitive content, then guests continue to be prohibited from accessing the file. What you need to do to prepare To mark new files sensitive by default: You will need to change a tenant property using PowerShell and a cmdlet. You need to enable least one DLP policy covering all SharePoint and OneDrive content.
We are pleased to launch the first stage of Microsoft Lists, a Microsoft 365 app. Microsoft Lists home (web) is the central place for all the lists you access across different sites. Key Points Microsoft 365 Roadmap ID 64160 Timing: targeted release in late July; complete for all by mid-October 2020 Roll-out: tenant level Control type: user control How this will affect your organization Lists helps you organize, collaborate and share. You can quickly start a list from scratch or get inspired by ready-made templates. View your recently accessed lists no matter where they are stored and favorite lists that need quick access. To get to the Lists home page on the web, click the Lists icon in the Microsoft 365 app launcher. The Lists home page provides easy access to your recently visited and favorite lists. What can users do on Lists? View all their recently accessed lists as part of the “Recent lists” section View all favorite lists as part of the “Favorites” section. Any list can be favorited for quick access from Lists home or from the list on their SharePoint site. View all the personal lists they’ve created Create a new list: from scratch, from an Excel spreadsheet, from an existing list or from 8 ready-made templates Rename a list Share a list Search for lists What’s new in List creation? Full visual refresh of the experience Ability to create a list from 8 ready-made templates Ability to create a personal list, that the user owns and can share. These personal lists are stored in the user’s my site What you need to do to prepare Consider notifying your end users about the availability of Microsoft 365 Lists home (web) and update end user training and documentation. Watch for future announcements about integration with Microsoft Teams as well as an iOS app.
We are making it possible for you to customize quarantine notifications with your organization logo, custom display name, and a custom disclaimer. This message is associated with Microsoft 365 Roadmap ID 64781 When this will happen We will begin rolling this out in to standard release customers mid-July through the end of July. We will begin rolling this out to government customers the end of July through mid-August. How this will affect your organization Example of custom logo Example of custom disclaimer What you need to do to prepare Admins will be able to enable these features through a new quarantine policy cmdlet and later through a new quarantine user interface. We will update this post when documentation for the new quarantine policy becomes available.