We have identified telemetry issues with the Sharing Report that resulted in inaccurate counts for files shared internally and files shared externally. We are making updates that will address these issues and improve report accuracy. We'll begin rolling this feature out soon.

After the update, “Files shared internally” is the number of files that have been shared with users within the organization, or with users within groups (that might include external users).

Also, “Files shared externally” might see an increase in the numbers as there are additional events that are being tracked and categorized within external sharing.

Please note that we are working on changes to further improve clarity over time.

[How does this affect me?]

In some cases, files shared internally or externally were being improperly counted. Specifically, events where files were being shared with security groups or Office 365 groups. Moving forward these will now be counted as Files Shared Internally. This update will address these issues going forward, additionally we will backfill the last 180 days to ensure continuity.

We will be rolling out this change starting May 15th, 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more about the Microsoft 365 analytics data model.

Information on SharePoint activity reports.

Information on OneDrive for Business activity reports.

As previously communicated (MC171089) Office 365 Skype for Business is 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 July 10, 2019.

[How does this impact me?]

Starting July 10, 2019, Office 365 Skype for Business will begin retiring 3DES. This means that all connections to Office 365 Skype for Business using the cipher 3DES will not work. Clients that still require 3DES such as Lync Phone Edition, Lync Mac 2011 and Lync 2010 will not be able to login to Office 365 Skype for Business.

Expect issues connecting to Office 365 Skype for Business services if you are using 3DES from this date onwards. TLS 1.0/1.1 connections without the 3DES cipher will not be affected.

[What should I do to prepare for this change?]

Update or replace clients and devices that rely on 3DES to connect to Office 365 Skype for Business prior to July 10, 2019.

Please review the Additional Information for more guidance details.

We’re updating Sharing links that block download for Office files. We'll begin rolling this feature out soon.

This message is associated with Office 365 Roadmap ID: 27499.

[How does this affect me?]

We are updating the feature that lets users create sharing links which block download for Office files. First, we will expand support for "specific people" links. Second, we will allow users to create "block download" links from File Explorer, Office apps, and the rest of the apps which use the common Office 365 file sharing experience.

We'll be gradually rolling this out to Standard Release organizations over the course of this week, and the roll out will be completed worldwide by mid-May 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

New feature: Office 365 Group card enhancements: search members, renew groups, approve pending members

End users will soon be able to search members in the Office 365 Groups hover card that is available on Outlook on the web and SharePoint Online. As well, group owners will also be able to renew groups and approve pending members from the expanded view of the hover card.

No net new functionality is being introduced--the functionalities already exist in other parts of Outlook on the web or SharePoint Online.

This message is associated with Microsoft 365 Roadmap ID 49175

[How does this affect me?]

Users will no longer need to leave the page that they were working in to do these tasks.

We'll be gradually rolling this out, beginning with Targeted release users, then with Standard release customers in April, and the roll out will be completed worldwide by the end of June.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change.

Busy on Busy in Microsoft Teams is a new Office 365 feature. We’ll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 49990.

[How does this affect me?]

Busy on Busy is a feature that allows callers to know if a user is already on another call or meeting when contacting them. When a call comes in to a user who is already engaged in a call or meeting, this setting alerts the calling party that the user is busy by playing a busy signal or an appropriate message.

This feature can be enabled using the enable Busy on Busy setting in the Teams Calling Policy. It is off by default and requires administrator action to enable.

We'll be gradually rolling this out to all Teams organizations towards the end of April, and the roll out will be completed worldwide by the end of May 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

There are updates coming to the authentication behavior on Azure AD (M365) sign-in pages. We'll begin rolling these changes out soon.

This message is associated with Microsoft 365 Roadmap ID: 33845.

[How does this affect me?]

Azure AD sign-in uses a process, called Home Realm Discovery, to determine where to send a user to authenticate after they enter their username on the sign-in screen. This process will be updated with an upgraded user lookup behavior. The new behavior will make intelligent decisions by reading tenant and user level settings based on the username entered on the sign-in page. This functionality will pave the path towards a passwordless future by enabling alternative credentials like FIDO 2.0.

After this change takes place, we'll check to see if the username that is entered on the sign-in page exists in their respective domain before deciding where to redirect the user to provide their credentials. Additionally, this behavior will introduce new and improved error messaging on the sign-in pages if the username the user entered doesn't match an account in the respective domain.

We'll begin gradually rolling this out in early May, and the roll out will be completed worldwide by mid-May, 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything to prepare for this change. Please click Additional information to learn more.

We’re updating Office 365 Enterprise plan names. This change will be made in late April, 2019.

[How does this affect me?]

The license display names of the Office 365 Enterprise plans will be updated to remove the word "Enterprise" (e.g. "Office 365 Enterprise E3" will be updated to "Office 365 E3").

This name change will go into effect on April 30, 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk.

New Outlook on the web - Search filters is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 50409.

[How does this affect me?]

The new Search filters will allow you to search with more specific terms such as folders, From, To, Subject, keywords, date range, and attachment. To use Search filters, go to the Search box and then click on Filters on the right side of the box.

We'll be gradually rolling this out to Targeted Release organizations beginning in mid-April, and the roll out will be completed worldwide by the end of June 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

Full-fidelity shared libraries in OneDrive for Business is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 49093.

[How does this affect me?]

Not only can you sync shared libraries from SharePoint Online and Microsoft Teams to your PC or Mac using OneDrive, you can now view shared libraries in OneDrive on the web with support for viewing file metadata. Initial capabilities include viewing ,sorting and grouping by custom metadata and changing your file view to any previously saved file view.

We'll be gradually rolling this out to Targeted Release organizations in mid-April, and the roll out will be completed worldwide by the end of May 2019.

There is nothing you need to do to prepare for this change. The Additional Information will be updated shortly with additional details.

We’re updating the banner for classic sites using structural navigation. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID 50442.

[How does this affect me?]

If SharePoint Online detects that structural navigation is causing the page to render slowly, site owners will see the following banner and have the opportunity to learn more:

“Slow performance detected. Your site is using structural navigation, which decreases page performance. Learn how to improve performance by using a different navigation method.”

We'll be gradually rolling this out to Targeted Release organizations in early April, and we anticipate rollout completion by the end of April 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

We’re updating Teams support for Meeting Migration Service. We'll begin rolling this feature out soon.

[How does this affect me?]

Currently, the Meeting Migration Service (MMS) updates existing Skype for Business meetings when either users move from on-premises to the cloud or when a user's audio-conferencing settings change. Up till now, the updated meetings have remained Skype for Business meetings.

With this new support, MMS can now convert existing Skype for Business meetings to Teams, and it can also update existing Teams meetings to reflect audio conferencing changes. MMS will be triggered to update a user’s existing meetings in the following scenarios:

• When a user is migrated from on-premises to the cloud (whether to Skype for Business Online or to TeamsOnly).
• When an admin makes a change to the user’s audio-conferencing settings
• When an online user is upgraded to Teams only, or when a user's mode in TeamsUpgradePolicy is set to SfBwithTeamsCollabAndMeetings
• When you use a PowerShell cmdlet.

We'll be rolling this out to customers starting May 8, 2019, and the roll out will be completed worldwide by the end of May.

[What do I need to do to prepare for this change?]

If you have PowerShell scripts that grant TeamsUpgradePolicy AND you do not want meetings to be migrated to Teams, update these scripts to also pass the new parameter MigrateMeetingsToTeams $false. For details, see: Grant-CsTeamsUpgradePolicy

Otherwise, you don't need to do anything but may consider updating your training and documentation. Please click Additional information to learn more.

We are making some changes to the Information Protection Administrator and Privileged Role Administrator roles.

This enhancement is related to Microsoft 365 Roadmap IDs 50422 and 50424.

[How does this impact me?]

1. Information Protection Administrator: We are updating the name of this role to “Azure Information Protection Administrator” in the Azure portal and Microsoft 365 admin center.
2. Privileged Role Administrator: A Privileged Role Administrator can manage only role assignments today. To reduce dependency on the Global administrator we are enabling the additional abilities:
• ability to consent/revoke any delegated or app permissions (including permissions to Microsoft or Azure Active Directory Graph)
• ability to create, update, delete Administrative Units, including membership management

We will begin rolling out these changes in May and will be completed in June.

[What should I do to prepare for this change?]

There is nothing you need to do to prepare for this change. We would suggest updating your training and process documentation as appropriate.

Please see additional information to learn more.

The new SharePoint admin center will be the default experience for organizations. We have completed rolling out to Office 365 organizations of 50 or fewer licenses, as communicated in MC173771, and are now rolling out more broadly.

This message is associated with Microsoft 365 Roadmap ID 46375.

[How does this affect me?]

The SharePoint admin center experience will default to the new admin center experience. You can switch back to the classic experience as necessary.

We'll be gradually rolling this out in early May and will be complete by the end of June.

[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk.

To switch to the classic experience temporarily, select “Classic SharePoint admin center” in the left pane of the new SharePoint admin center.

To control the default experience for all global and SharePoint admins in your organization:

In the new SharePoint admin center, select Settings in the left pane, and then select Default admin center experience. Turning the setting to Off will set the classic admin center as default and On will set the new admin center as default. This control is available now.

This change will be skipped for customers that have modified the setting of their default admin center experience.

Please click Additional information to learn more.

SharePoint Online organizational news: audience targeting is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 30695.

[How does this affect me?]

Audience targeting for news and highlighted allows page authors and site owners to tag pages and news posts with Azure Active Directory groups, and filter content within these web parts to people within those groups.

We'll be gradually rolling this out to Targeted Release “entire org” customers in mid-April, and we anticipate rollout completion by the end of June 2019.

[What do I need to do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk. Please click Additional information to learn more.

Microsoft Kaizala Pro will be available as part of your Office 365 plan beginning in late-May 2019.

Microsoft Kaizala Pro is a simple and secure work management and messaging app that brings unique capabilities to Microsoft 365 with its ability to have very large, flexible group types and the ability to connect and engage with people outside of an organization’s directory – including contract workers, vendors, partners, suppliers, customers and citizens. Kaizala enables phone number-based identity for easy onboarding, and a simple user experience for messaging and work management through the open directory. With Kaizala Pro, organizations own the data within their Office 365 connected Kaizala groups.

[How does this impact me?]

Kaizala Pro will be visible in the Office 365 app launcher and will be on-by-default for your organization.

Users will start seeing a Microsoft Kaizala icon in late-May 2019. Additionally, they will be able to start using the Kaizala Management Portal and link their Office 365 account on the Kaizala mobile app.

[What should I do to prepare for this change?]

If you would like to allow users to access Microsoft Kaizala, no action is needed. If you would like to disable Kaizala for your organization, you can follow the instructions for the tenant-level admin control.

Please click Additional Information to learn more about Kaizala.

Microsoft Kaizala Pro will be turned on for your tenant by default starting late-May 2019.

Microsoft Kaizala Pro is a simple and secure work management and messaging app that brings unique capabilities to Microsoft 365 with its ability to have very large, flexible group types and the ability to connect and engage with people outside of an organization’s directory – including contract workers, vendors, partners, suppliers, customers and citizens. Kaizala enables phone number-based identity for easy onboarding, and a simple user experience for messaging and work management through the open directory. With Kaizala Pro, organizations own the data within their Office 365 connected Kaizala groups.

[How does this affect me?]

As previously communicated, Kaizala Pro will be visible in the Office 365 app launcher. The change you will experience is Kaizala Pro will now be on-by-default for your organization.

Users will start seeing a Microsoft Kaizala icon in late-May 2019. Additionally, they will be able to start using the Kaizala Management Portal and link their Office 365 account on the Kaizala mobile app.

[What do I need to do to prepare for this change?]

If you would like to allow users to access Microsoft Kaizala, no action is needed. If you would like to disable Kaizala for your organization, you can follow tenant-level admin control instructions.

Please click Additional Information to learn more about Kaizala.

We’re updating the way meetings chat is controlled by creating a new, separate setting in CsTeamsMeetingPolicy to manage meetings chat, as a change from previous practice where meetings chat followed CsTeamsMessagingPolicy. We'll begin rolling this feature out soon, but will do it in stages to provide time for customers to make any changes.

[How does this affect me?]

At customers' request, we are making some changes to the way meetings chat is controlled. Prior to the change, it was controlled by the AllowUserChat setting of the CsTeamsMessagingPolicy. After this change, it will be controlled by a new setting, MeetingChatEnabledType, of the CsTeamsMeetingPolicy.

The change will be rolled out selectively on the basis of users’ upgrade mode:

• Users with effective upgrade mode of SfBOnly, SfBWithTeamsCollab, or SfBWithTeamsCollabAndMeetings do not have access to the Chat tab and hence do not conduct private or group chat in Teams. However virtually all such customers want to and should be permitted to chat in meetings, and many have requested this capability. Prior to this change they were not able to do so. For these users, this change will take effect on or after April 9.

• On the other hand, users with effective upgrade mode of Islands or TeamsOnly do have access to the Chat tab unless chat has been explicitly disabled in CsTeamsMessaging policy. When that happens, they also do not have access to meetings chat today. An example is EDU tenants, who frequently ban the use of all sorts of chat (both private chat, group chat and meetings chat) for students. For these users, this change will take effect on or after May 15. Prior to the change, tenant admins should review users for whom they want meetings chat to remain off, and make sure these users are granted the new setting.

The roll out will be completed worldwide for all tenants by 5/31/2019.

[What do I need to do to prepare for this change?]

Review your requirements and policies with respect to meetings chat. If you do not require meetings chat to be off for any user, you do not need to do anything. If you require meetings chat to be off for specific users, we recommend you apply CsTeamsMeetingPolicy's MeetingChatEnabledType setting with the Enum value of Disabled to these users.

The Additional Information will be updated shortly to reflect these changes.

We are excited to announce the To-Do & Planner Integration is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID 48624

[How does this affect me?]

Users who opt-in to the Planner integration will be able to see and edit tasks they have been assigned to in Planner within To-Do. These tasks will surface in the "Assigned to me" list, but will also appear in To-Do search results, My Day suggestions, and the Planned smart list (all tasks with a due date). Users may turn off this integration at any time via the To-Do Settings menu.

In order to use this integration in the Outlook Web task module, you must have the New Tasks module enabled. We previously announced this feature in February via MC173377

We'll be gradually rolling this out to customers in April, 2019, and the roll out will be completed worldwide by the end of May 2019.

This roll out is excluded from Office 365 subscriptions in GCC.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change.

As previously communicated in MC149144 on September 24, 2018, Microsoft Teams is evolving to include a new set of capabilities that will simplify schedule management and help deliver the tools for every worker to get the job done. As a result, we will be retiring Microsoft StaffHub on October 1, 2019 and we will be focusing our investments on Microsoft Teams. After October 1, 2019 users that attempt to log in to StaffHub will be greeted with a message directing them to download Microsoft Teams.

To help you in your transition to Microsoft Teams, we ask that you review the details below for pre-requisites related to user and data migration across Microsoft Teams and StaffHub.

[How does this affect me?]

If you’re receiving this notice, you have one or more people in your organization who currently use Microsoft StaffHub. Please communicate these details to the right stakeholders in your organization.

[What do I need to do to prepare for this change?]

If you would like to move your StaffHub teams to Shifts in Microsoft Teams the following pre-requisites are needed:

• Microsoft Teams must be enabled for the tenant.
• Note: Organizations who are still using Skype for Business can enable Teams to run alongside Skype for Business if they aren’t yet ready to upgrade to Teams.
• StaffHub users must be licensed to use Teams. Teams licenses are available in Office 365 F1, E1, E3 and E5, Microsoft 365 F1, E1, E3 E5, Office 365 Business Premium, and EDU.
• Office 365 Groups must be enabled for the tenant.
• Each StaffHub team requires an Office 365 group. If there is no Office 365 group associated with the StaffHub team, a new O365 group will be created at the time you move the StaffHub team.
• All StaffHub team members must be provisioned AAD users and members of the Office 365 group.
• StaffHub team owners/managers can convert an inactive accounts and link them with a provisioned account in StaffHub by going to the team settings page and updating the e-mail address to a valid UPN.

OR

• Administrators can run the Add-StaffHubMember and Remove-StaffHubUser cmdlets to remove a non-provisioned account from a StaffHub team and add them back with their UPN.

Please click Additional Information to learn more.

In MC171679 we introduced audit of mail reads/accessed by default for owners, admins and delegates under the MailItemsAccessed action, with automatic availability of the action for users on default audit configuration.

We have rolled back the feature, at this time, and so the MailItemsAccessed action will no longer be available.

This enhancement is related to Microsoft 365 Roadmap ID 32224.

[How does this impact me?]

Since the audit action has been rolled back, records for MailItemsAccessed will not be available for both Exchange Auditing and Unified Audit logs. You can continue to use MessageBind to have visibility to Mailread actions. This change does not impact the remaining set of verbs, or the process of enabling mailbox auditing by default.

[What should I do to prepare for this change?]

There is no action for you at this time. We plan to reinitiate the rollout of the MailItemsAccessed audit action soon and will send additional communication to inform you of the new timeline.

We’re releasing new Mail flow insights. There will be 6 new insights/reports added on the Mail flow dashboard in Security & Compliance Center. We'll begin rolling this feature out soon.

This message is associated with Office 365 Roadmap ID 49361.

[How does this affect me?]

You will be able to see more insights for your organization's mail flow.

We'll be gradually rolling this out to Targeted Release ("entire org") customers in early April, and the roll out to all customers is planned in May and will be completed worldwide by early June.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

Please click Additional information to learn more.

Restricted Users is a new Office 365 feature. We'll begin rolling this feature out soon. It is a replacement for the Exchange Action Center.

This message is associated with Microsoft 365 Roadmap ID: 31546.

[How does this affect me?]

The Action Center has been moved to the Security and Compliance Center (SCC) as a new feature called the Restricted Users portal. Administrators can now use SCC to remove restrictions from user accounts that have been blocked from sending mail to external users due to suspicious activity. We plan on expanding this feature to automate remediation actions that check for things like compromise, but also prevention tips like password change and enabling MFA.

We began gradually rolling this out in early March, and we anticipate roll out completion worldwide by the end of March 2019.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

We’re updating the Microsoft Teams Commercial Cloud Trial. We'll begin rolling this feature out soon.

This message is associated with Office 365 Roadmap ID 49456.

[How does this affect me?]

With the updated Microsoft Teams Commercial Cloud Trial offering, we are making it easier to manage all end-user initiated Teams trials. This will now be owned and controlled by the billing admin of the tenant, making this consistent with all other Microsoft 365 offers.

Starting in late April, all new Teams Trial users will begin leveraging this new offering. We will begin rolling out support for the migration of existing Teams Trial users to this new offering in late April and complete by early June. Once support is rolled out, users will be automatically migrated to the new offering next time they log into Teams.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

New feature: Autodesk integration for DWG files

Autodesk integration for DWG files is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID 33414

[How does this affect me?]

With the release of Autodesk integration for DWG files users will see actions available on the command bar and pop-up menus to open DWG files in AutoCAD (web app) in OneDrive for Business and SharePoint Online.

Tenant administrators will be able to disable this functionality through use of a PowerShell command if desired. Details for the use of PowerShell will be updated in the SharePoint Online Cmdlets documentation.

We'll be gradually rolling this out to Targeted Release "entire org" customers in mid March, and the roll out will be completed worldwide by the end of March.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

We previously announced the rollout of MyAnalytics via Message Center. This message is to update you on changes to availability and additional control functionality.

Starting April 15th you could begin to manage "Insights by MyAnalytics" at the tenant level from the Exchange Admin Center. The add-in functionality will begin rolling out on May 15th to give you additional time to manage your settings. We have provided this additional time and control so you can tailor the roll out of “Insights by MyAnalytics” to your organization.

This message is associated with Microsoft 365 Roadmap ID 45625.

This change will roll out to all customers with Microsoft 365 E5, E3, Business, Office 365 E5, E3, E1, Business Premium and Business Essentials licenses.

[How does this impact me?]

You may begin to see “Insights by MyAnalytics” in the Exchange Admin Center on April 15th. Click here for detailed instructions for how to manage Insights by MyAnalytics from the Exchange Admin Center.

[What should I do to prepare for this change?]

You don't need to do anything to prepare for this change.

The add-in is subject to the same GDPR compliance terms as Office 365, and all insights are only available to end users—no Admin or manager can see those insights. The add-in does not begin processing data for insights until a user clicks to enable it. Insights are never stored outside the user’s mailbox by the add-in. Click here to learn more about how Microsoft protects your privacy.

Please click Additional Information to learn more.

We're making several changes to Microsoft Whiteboard that will roll out over the next 3-4 months.

1. For all organizations with Whiteboard - Microsoft Whiteboard will appear as an available product in Office 365 and the service principal will be added to appropriate tenants that have Whiteboard enabled.
2. For all Office 365 tenants with Whiteboard located in Europe - Microsoft Whiteboard will automatically store whiteboard content in datacenters in that region.
3. For all organizations with Surface Hubs – If you manage Surface Hubs, the legacy 2016 application of Whiteboard will be upgraded to the latest version and the legacy version will no longer receive updates.

[How does this impact me?]

You are receiving this message because our reporting indicates that Microsoft Whiteboard is available for your tenant.

[What should I do to prepare for this change?]

You don't need to do anything, but may consider updating your user training, and notifying your helpdesk.

Please click Additional information to learn more.

Yammer tabs for Microsoft Teams is a new Office 365 feature. We'll begin rolling this feature out soon.

This message is associated with Microsoft 365 Roadmap ID: 31502

[How does this affect me?]

Starting today, Microsoft Teams users will be able to add a Yammer tab to their Teams channel that loads a specified group or topic feed from Yammer. This new feature will allow members to follow and share conversations in Yammer without having to leave Teams.

Your team members can participate in the Yammer conversation, right from Teams, or discuss a Yammer conversation in Teams before posting a reply to the wider Yammer group. When a Teams member goes to the Yammer tab, they are authenticated again by Yammer, so that they only see Yammer content that they have access to.

Members can only add tabs to a team if team members are enabled to do so.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

We’re updating how owners of groups in Outlook can manage membership requests. We'll begin rolling this feature out soon.

This message is associated with Office 365 Roadmap ID: 46436.

[How does this affect me?]

Powered by actionable messages, group owners will now have the capability to approve or decline membership requests right inside an email in Outlook on the web and in Outlook for Windows, without the need to navigate to other pages. Approved or declined requests will be visible to all the group owners. Owners can select one or multiple requests to approve or decline.

We’re gradually rolling this feature out over the next few weeks, and the roll out will be completed worldwide by the end of March 2019. Organizations in GCC, GCC High, DoD and BlackForest environments will receive this feature update in mid-April.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change. Please click Additional Information to learn more.

In an effort to improve and streamline user’s initial experience with Teams, we’re making an enhancement so that the desktop Teams app will now be downloaded automatically when new users with Office 365 ProPlus licenses first download the Office Pro Plus apps. We'll begin rolling this feature out soon.

This message is associated with Office 365 Roadmap ID: 46444.

[How does this affect me?]

After this change takes place for your organization, Microsoft Teams will be included in the initial user download with other apps like Word, PowerPoint and Excel in their Office 365 ProPlus subscription. You or your users will no longer need to separately download and install Teams. This change does not affect any existing users who are already licensed and using the service.

We began gradually rolling this change out to Targeted Release organizations in mid-January. On February 25, 2019 the rollout will continue to Monthly Channel, and to Semi-Annual Channel Targeted (SAC-T) subscribers on March 12. Semi-Annual Channel (SAC) subscribers will see this change in July 2019.

[What do I need to do to prepare for this change?]

If you want your new users to have access to Microsoft Teams by default, then there’s nothing you need to do to prepare for this change. If you would like to restrict access to Teams, or delay the rollout for your organization, please click Additional Information below.

New feature: Last Modified Date, Enhances RSS and Feedback features coming to the Microsoft 365 Public Roadmap

We'll be gradually rolling this out to all customers in early March 2019, and the roll out will be completed worldwide by the end of April 2019.

[How does this impact me?]

Starting in March, we will begin rolling out the following enhancements and features to the Microsoft 365 Public Roadmap:

• Last Modified Date: When this update is rolled out, the Last Modified Date will reflect the date information is updated for an individual feature item. This will allow better tracking when information changes for features that are important to you and your organization.
• Enhanced RSS Feeds: Currently, when a ‘More Information’ link is not provided for a feature, the M365 Roadmap RSS feed defaults to provide a link back to the roadmap. The RSS feed will be updated to include both a ‘View Roadmap Item’ link, directing users to the feature in the M365 Public Roadmap and a ‘More Information’ link that will direct users to more information when available. Not all features will have a ‘More Information’ link, as upcoming feature information is provided as early as possible and this information is not always available. ‘More Information’ links will continue to be provided in Message Center posts for specific features.
• Microsoft 365 Feedback Feature: We will be adding a feature to the M365 Public Roadmap which will allow users to share ideas and suggestions on how we can improve the M365 Public Roadmap experience. We look forward to hearing feedback on how we can continue to improve the M365 Public Roadmap experience.

[What do I need to do to prepare for this change?]

There is nothing you need to do to prepare for this change.

Please click the Additional Information link to access the Microsoft 365 Roadmap.