Stay on top of M365 changes
Keep track of upcoming changes, including new and changed features, planned maintenance, or other important announcements.
Outlook for iOS and Android will soon roll out a number of new features, including a different location for the New Message and New Event buttons, the ability to create a task from an email, suggested meeting actions in the reading pane, and new capabilities for formatting. Outlook for iOS: new location for compose and create event, Roadmap ID 65440 Rolling out in early July Outlook for Android: rich text options, Roadmap ID 65442 Rolling out in early July Outlook for iOS: create task from an email message, Roadmap ID 60722 Rolling out in mid-July How this affects your organization Outlook for iOS: new location for compose and create event The button to begin composing a new email and creating a new event is moving from the top right of the screen to the bottom right and will be a floating button. Outlook for iOS: create task from an email message By selecting this option from behind the message ellipses, a new task will be added to tasks in Microsoft 365 and sync with To Do with the email subject as the task name and the email linked back. The newly created task can also be visible in the Search homepage within Outlook for iOS. Users can manage their tasks with the To Do app. Outlook for Android: rich text options At the beginning of July, we will roll out the option to use rich text treatments such as bold, underline, bullets, and lists to email message. These new formatting options will be available by tapping the icon on the toolbar above the keyboard. What you need to do to prepare There is no action you need to take to prepare for this change, but you might consider updating your user documentation and alerting your help desk.
We are pleased to offer Cortana voice assistance in the Teams iOS and Android mobile app, which allows users to perform communication, collaboration, and meeting-related tasks by speaking natural language. At the time of this release, the feature will be be enabled only for users in the U.S. Expansion to additional languages and regions will happen as part of future releases. Key points Microsoft 365 Roadmap ID 65346 Timing: mid-August and complete by the first of September Control type: admin control Action: control who can use via TeamsCortanaPolicy How this will affect your organization Users can speak to Cortana by clicking on the microphone button located in the upper right of the Teams mobile app. They can connect with someone while on the go by making a voice query such as “call Megan” or “send a message to my next meeting.” Users can also join meetings by saying “join my next meeting.” Users can also share files and check their calendar. Example of Cortana flow Cortana in Teams meets Office 365 enterprise-level privacy, security, and compliance promises as reflected in the Online Services Terms (OST). What you need to do to prepare The feature will be enabled by default for tenants. The policy to turn this feature off will be available at the end of July; we will update this MC post with those details when they are available. Tenant admins can control who in their tenant can use Cortana voice assistance in Teams via a policy (TeamsCortanaPolicy) which is set at either a user account level or tenant level. At launch, admins can also use the CortanaVoiceInvocationMode field within this policy control to determine whether Cortana is disabled or enabled with push button invocation only. Note that at the time of this initial release, the Teams mobile app will not support wake word activation, but it will be supported in the future.
Large Gallery view (preview) for Microsoft Teams meetings provides a new way to view video from up to 49 participants at once on a single screen. Similar to the normal Gallery view, Large Gallery automatically adapts the layout of participant videos in a Teams meeting into defined grids (e.g. 7×7) for optimal viewing. Large Gallery is an optional participant view that is turned off by default for each meeting, and each meeting user may switch in or out of Large Gallery view at any time. Large Gallery is being made available as a public preview feature and uses a new flexible design to deliver a network-optimized client video experience that works on multiple device categories. During the preview, the Large Gallery experience will be available for desktop Teams client (Windows, Mac) and mobile Teams client (iOS, Android) users. In order to take advantage of this new view, users will need to turn on the new multi-window meeting experience and must have ten (10) or more participants in an active meeting with video turned on. This message is associated with Microsoft 365 Roadmap ID 65333 When this will happen We will begin rolling out the feature to production with the new multi-window experience for desktop clients in early July and target full availability including mobile clients for iOS and Android by the end of August. How this will affect your organization As a result of utilizing Large Gallery, more users may enable video during their Teams meetings. While in preview, user interactivity with individual participant videos (pin single participant, mute audio) shown in Large Gallery will be limited. Users needing participant-level controls can continue to use the Teams roster and Large Gallery together as a combined tool. What you need to do to prepare Before adopting Large Gallery view, users should be made familiar with the new multi-window experience for Teams meetings (MC212453, May 2020).
As users scroll horizontally across a list or documentary library in Quick Edit, the far left column will soon remain in place. This message is associated with Microsoft 365 Roadmap ID 64866 When this will happen We will roll this out to targeted release users beginning early July; we expect the rollout to be complete by late July 2020. We will roll this out to standard release users beginning late July; we expect the rollout to be complete by the end of September 2020. How this will affect your organization This interface change will make it easier for users to navigate very wide lists.
(Updated) The Planner app in Teams will be renamed with an updated experience powered by Planner and To Do
Updated June 26, 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 details and roll-out timeline belowThe Planner app in Teams will become the Tasks app. Users will now be able see their individual tasks and team tasks in a single app. We’re also introducing both a list view and a new mobile tasks experience within the Teams app for mobile devices. The Planner app will be renamed after the rollout is complete, as described below. We will begin roll-out in July (previously June) and expect to be complete in August (previously mid-July). This message is associated with Microsoft 365 Roadmap ID 57213 and 65385 How does this affect me? Users will see individual tasks powered by To Do (which also powers Outlook tasks) and team tasks powered by Planner. Existing Planner tabs will behave the same as they do today but will show an additional list view. Users will be able to add new Tasks tabs to the channels in teams they belong to. Users can also access the Tasks app in the same ways they previously accessed the Planner app. Renaming the Planner app in Teams to Tasks and enabling a mobile experience in Teams We’re planning to rename the Planner app to Tasks. The new Tasks experience will contain individual tasks and team and channel tasks, similar to how Files encompasses a user’s personal files in their own OneDrive for Business as well as their team and channel files. We’ll make this adjustment in two steps. Once we’ve made the new tasks experience broadly available to all public cloud organizations, we’ll enable the Tasks in Teams mobile experience and complete a logo update and an interim rename of the Planner app. Its interim name will be Tasks by Planner and To Do. This will help ensure the app can be found when searching for Planner while adding a tab or searching for the app in the app catalog. A few months after the interim name change, the app name on desktop will be shortened to Tasks. This name change applies only to the Planner app in Teams. All other Planner clients and To Do clients will keep their existing names, and users can continue to use those clients to manage tasks just as they do today. Task publishing functionality will be available as part of a private preview. Note – Government tenants will see the name change when it rolls out but will not see the additional user experience changes until a later date. We will communicate via Message center once these are available.
Microsoft is increasing the Max File Size from 15GB to 100GB for a single file. We previously announced this feature late in 2019 and are fully rolling out to ALL tenants at this time. This change applies to OneDrive for Business and SharePoint Online. For best performance, we recommend uploading very large files using the OneDrive Desktop client. We apologize that we did not communicate this ahead of the roll-out and we are working to improve this in the future. This message is associated with Microsoft 365 Roadmap ID 49368 When this will happen This feature is available now. How this will affect your organization End users will no longer receive errors when trying to upload a file larger than 15GB, but less than 100GB. This will enable productivity, storage, and protection on large files in your organization. What you need to do to prepare You may consider updating your training and documentation as appropriate. Additionally, if your tenant has large files that have not been able to be uploaded before, we recommend you test a few large files. There are many factors that may impact your upload including bandwidth, location, other network traffic.
Inline chat message translation lets users translate Teams mobile chat messages into the language they choose. This feature is rolling out first for iOS; we will send a separate message when we have the schedule for Android. This message is associated with Microsoft 365 Roadmap ID 63227. When this will happen The updated iOS app will be released to the store in late June 2020. We anticipate that the rollout will be complete by mid-July. How this affects your organization When using the Teams mobile iOS app, users who receive a chat message in another language can choose to translate that chat message into the language they have set in Settings > General > Translation. To translate a chat message, press-and-hold the message to see the translation option. What you need to do to prepare For your end users to have the benefit of inline chat message translation, you must enable the feature. There are two ways to do this. 1. Enable this setting using the Set-CsTeamsMessagingPolicy cmdlet. -AllowUserTranslation Determines whether a user is allowed to translate messages to their client languages. Set this to TRUE to allow. Set this to FALSE to prohibit. The policy takes a few minutes to apply. Users might need to sign out and sign back in to Teams. 2. In the Microsoft Teams admin center, select Messaging Policies from the left navigation, then either create a new policy or edit an existing policy, and set the Allow users to translate messages option to On.
Sensitivity labels in Microsoft Teams, Microsoft 365 groups, and SharePoint sites generally available
Your ability to apply sensitivity labels to Microsoft Teams sites, Microsoft 365 groups (formerly Office 365 groups), and SharePoint sites is moving out of public preview into general availability. This extends the protection options we announced in May, when sensitivity label protection for Office files in SharePoint and OneDrive became generally available. This feature is related to Microsoft 365 Roadmap ID 64965. When this will happen We will begin rolling this out in late June and expect the rollout to be complete in early July. How this affects your organization When you create sensitivity labels in the Microsoft 365 compliance center, you can now apply them to the following containers: Microsoft Teams sites, Microsoft 365 groups (formerly Office 365 groups), and SharePoint sites. Use the following label settings to help apply the following policies: Access from unmanaged devices External user access Privacy (public or private) of Microsoft 365 group-connected Teams sites The following apps and services support the new sensitivity labels for Microsoft 365 groups: Admin centers: Azure Active Directory(AAD) Security & Compliance SharePoint Forms Outlook Outlook desktop app for Windows Outlook for the Mac Outlook for the web Outlook mobile app for Android and iOS SharePoint Stream Teams The following apps and services do not support the new sensitivity labels for Microsoft 365 groups: Admin centers: Exchange Microsoft365 Teams Dynamics 365 Planner Power BI Project Yammer What you need to do to prepare This is an opt-in feature. A global or SharePoint admin must enable it using PowerShell If you have already enabled the feature, we will honor that setting. If you have not turned on the feature, read here for more info
Walkie Talkie, which provides instant push-to-talk communication, will soon be available in Public Preview on Teams for Android. This message is associated with Microsoft 365 Roadmap ID 57157. When this will happen We will begin the rollout in mid-July and expect to be complete by end of July. How this will affect your organization During Public Preview, you need to enable Walkie Talkie using the Teams Admin Center to provide access to people in your organization. Once enabled, Walkie Talkie will become available on the Android app within 48 hours. Walkie Talkie allows users to connect with their team using the same underlying channels they are members of. Only users who connect to Walkie Talkie in a channel become participants and can communicate with each other using push-to-talk. What you need to do to prepare During Public Preview, this app is not pre-installed. If you wish to enable this feature in your tenant, add Walkie Talkie to the App Setup Policy assigned to users.
So glad when this (Ability to update the root site to a communication site) will be rolled out (end of July 2020) been waiting for this for about 2 years. This optional feature allows SharePoint admins and site owners to enable the modern communication site experience on any classic team site that meets the requirements, including the root site. This message is associated with Microsoft 365 Roadmap ID 46338. When this will happen We will begin gradually rolling out this feature to Targeted Release (for entire organization) customers by the end of June 2020. The rollout will be completed for all customers by the end of July 2020. How this will affect your organization A SharePoint communication site is a great tool for sharing information with others in your organization. Now, classic team sites can enjoy the benefits of modern communication sites. What you need to do to prepare This is an optional feature that will not have any impact in your environment until a SharePoint admin or site owner enables this feature on a site. To enable this feature on a classic team site, a SharePoint admin or site owner must run a PowerShell cmdlet. Enabling the communication site experience does not change any site permissions or remove any content. Learn how to run the PowerShell cmdlet.
Outlook for Windows is introducing e-mail signatures that will be stored in the cloud rather than being stored locally on the user’s Windows device. This message is associated with Microsoft 365 Roadmap ID 60371 When this will happen We will begin rolling this out to Microsoft 365 Monthly Channel, Targeted, in late July. (This is Insiders Slow Channel which will soon be called Microsoft Beta.) We expect to roll this out to the Monthly Channel, Production, in late August. How this will affect your organization The feature is on by default. Traditionally, signatures were stored locally on a user’s Windows device. With this feature, signatures will now be associated with an email account. Signatures will be stored in the user mailbox and will be available on any devices running Outlook for Windows that has been configured with that email account. When the feature becomes available, Outlook will read the existing local signatures. Outlook will copy signatures selected as default for New messages or Replies/forwards to the account mailbox, making them available across multiple devices. What you need to do to prepare The feature is on by default. Because this new feature is changing how Outlook manages signatures stored on a local drive, third-party add-ins which provided this functionality will no longer work when this feature is enabled. Learn how to mitigate this for your users.
Updated June 11, 2020: To provide clarity, this feature is to enhance the administration of self-service purchasing for tenants using it. If your tenant is not using the self-service purchasing capabilities this will not impact you.In January we launched the self-service purchase feature that allowed users in a tenant to purchase Power platform products directly from Microsoft. This feature came with the ability for admins to turn off self-service purchase of individual products via Power Shell. Starting in July, we’re introducing new capabilities for IT Admins to manage information worker subscriptions in their tenant. In particular, IT Admins will be able to move information workers to another subscription or remove a subscription via a button in the Admin Center. When this will happen This feature will gradually roll out beginning in July. We anticipate the rollout will be complete by early August. How this will affect your organization Once this feature is available Admins will be able to manage self-service purchases, made by users in their tenant, within Admin center under Billing > Your products. Admins will have an option to “Take control of subscription”. This will allow Admins to: cancel the subscription move users from the subscription to another subscription while cancelling the original subscription What you need to do to prepare You may consider updating your training and documentation as appropriate.