Understanding Compliance Between Commercial, Government, DoD & Secret Offerings - Sept 2024 Update
Understanding compliance between Commercial, Government, DoD & Secret Offerings: There remains much confusion as to what service supports what standards best. If you have CMMC, DFARS, ITAR, FedRAMP, CJIS, IRS and other regulatory requirements and you are trying to understand what service is the best fit for your organization then you should read this article.November 2024 - Microsoft 365 US Public Sector Roadmap Newsletter
SharePoint Online We will be retiring the Revoke-SPOUserSession PowerShell cmdlet for Microsoft SharePoint Online (SPO) starting early November 2024 We're making some changes to on-demand indexes used to support SharePoint and OneDrive Search using Application Permissions Teams Speed dial customization using line keys for non-touch phones and sidecars - GCC October, GCCH November Purview Information Protection - Default sensitivity labels and policies enhancements Customize communication compliance policies with language-specific trainable classifier condition Ability to increase configuration of CPU and GPU device resource utilization limits in Forensic Evidence Microsoft 365 Project for the web Email Notification Update - GCC Microsoft Product Placemat for CMMC - October 2024 Update We are actively building acceleration by developing resources for both partners and Defense Industrial Base (DIB) companies to leverage in their Cybersecurity Maturity Model Certification (CMMC) journey. Microsoft Copilot for Microsoft 365 GCC GA Update: Empowering Public Sector Innovation - Updated Nov 6 We know our valued US Government GCC customers have been eagerly awaiting the Microsoft 365 Copilot GCC launch in October 2024. To deliver the best product experience, we anticipate general availability (GA) Q4 calendar year 2024, and we'll update our public roadmap with a more specific date as available. Enhancing Security with CISA’s ScubaGear Baselines for Microsoft 365 In today's digital age, securing an organization's information is more critical than ever. The Cybersecurity and Infrastructure Security Agency (CISA) stood up a program called Secure Cloud Business Applications (SCuBA). Where to Start with Microsoft Teams Apps in Gov Clouds Customers in our Office 365 government clouds, GCC, GCCH, and DoD, are continuing to evolve how they do business in the hybrid workplace. As Microsoft Teams is the primary tool for communication and collaboration, customers are looking to improve productivity by integrating their business processes directly into Microsoft Teams via third-party party (3P) applications or line-of-business (LOB)/homegrown application integrations. What’s New in Microsoft Teams | October 2024 Teams webinars is now available in the Government Community Cloud High (GCCH) environment, providing a secure and compliant platform for hosting large-scale virtual events. Microsoft 365 Government Community Call Watch past episodes of Jay Leask and other members of the Government Community on LinkedIn! Microsoft 365 Government Adoption Resources Empowering US public sector organizations to transition to Microsoft 365 Microsoft 365 Public Roadmap This link is filtered to show GCC, GCC High and DOD specific items. For more general information uncheck these boxes under “Cloud Instance”. Stay on top of Microsoft 365 changes Here are a few ways that you can stay on top of the Office 365 updates in your organization. Microsoft Tech Community for Public Sector Your community for discussion surrounding the public sector, local and state governments. Microsoft 365 for US Government Service Descriptions Office 365 Platform (GCC, GCCH, DoD) Office 365 U.S. Government GCC High endpoints Office 365 U.S. Government DoD endpoints Microsoft Purview (GCC,GCCH,DoD) Enterprise Mobility & Security (GCC, GCCH, DoD) Microsoft Defender for Endpoint (GCC, GCCH, DoD) Microsoft Defender for Cloud Apps Security (GCC, GCCH, DoD) Microsoft Defender for Identity Security (GCC, GCCH, DoD) Azure Information Protection Premium Exchange Online (GCC, GCCH, DoD) SharePoint(GCC, GCCH, DoD) OneDrive (GCC, GCCH, DoD) Teams (GCC,GCCH,DoD) Office 365 Government (GCC, GCCH, DoD) Power Apps (GCC, GCCH, DoD) Power Automate US Government (GCC, GCCH, DoD) Power BI (GCC, GCCH, DoD) Planner (GCC, GCCH, DoD) Outlook Mobile (GCC, GCCH, DoD) Viva Insights (GCC) Dynamics 365 US Government Public Sector Center of Expertise We bring together thought leadership and research relating to digital transformation and innovation in the public sector. We highlight the stories of public servants around the globe, while fostering a community of decision makers. Join us as we discover and share the learnings and achievements of public sector communities. Microsoft Teams for US Government Adoption Guide Please note:This section is for informational purposes only. It is presented as is and as available with no warranty and no supportability given expressly or implied. Questions, comments, concerns and all other feedback must be presented in the comment section below the post, thank you! SharePoint Online MC925386 — Microsoft SharePoint: Feed for Viva Connections web part and Video news link end of support starting November 5, 2024 As communicated in MC846391: Microsoft SharePoint: Feed for Viva Connections web part and Video news link retires starting September 1, 2024 (August 2024), this is the final reminder that the end-of-life support for the Feed for Viva Connections webpart and the Video news link is onNovember 5, 2024. OnSeptember 1, 2024, we removed the Feed for Viva Connections web part from the toolbox. Also, we removed the Video news link from the + New menu in the organizational site. Site editors can no longer add a new feed for Viva Connections web part to a site or embed new video links to the Viva Connections feed. OnNovember 5, 2024,we will end support for the Feed for the Viva Connections web part and the Video news link. Site editors are encouraged to use the web parts;News,Viva Engage,File and Media, andHighlighted content, as well asvideo pagesas alternative solutions. Note: Any Feed for Viva Connections web parts that have not been replaced with the recommended alternative solutions by November 5, 2024, will result in an empty web part that no longer displays content or any Video news links that have not been removed. Visitors to the site will instead see an error message. For more information, refer to theViva Connections Feed web part and Video news link retirement support guidance. MC922630 — Microsoft OneDrive: We will remove the "EnableHoldTheFile" group policy Microsoft 365 Roadmap ID429875 We will remove the EnableHoldTheFilegroup policy for Microsoft OneDrive from the Microsoft 365 admin center. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early April 2025 and expect to complete by late April 2025. How this will affect your organization: Before this rollout, if a tenant has disabledEnableHoldTheFileand users experience file conflicts, Microsoft OneDrive automatically creates a copy of the file in conflict. When tenants disableEnableHoldTheFile, users may have to manage hundreds of conflicts because OneDrive automatically copies a file instead of allowing users to choose to merge conflicts. After this rollout, theEnableHoldTheFilegroup policy will be removed and the experience associated with theEnableHoldTheFilegroup policy will be enabled for all tenants. If a user opens a Microsoft Word, Excel, and PowerPoint file and there is a conflict that requires user input to resolve, the user will be given the option to choose the file variation to keep. If the conflict cannot be resolved, a banner will display to eitherSave a Copyof the file orDiscard Changesif the user doesn't care about the changes that were made. User notification to choose the file variation to keep in PowerPoint: User notification toSave a CopyorDiscard Changesin PowerPoint: User notification toSave a CopyorDiscard Changes in Word: What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change, especially if the policy was disabled, and update any relevant documentation. Learn more:IT Admins - Use OneDrive policies to control sync settings - SharePoint in Microsoft 365 | Microsoft Learn(direct link to the section calledAllow users to choose how to handle Office file sync conflicts) MC921916 — (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed Microsoft 365 Roadmap ID429874 Updated October 31, 2024: We have updated the content. Thank you for your patience. We're removing theEnableAllOcsiClientsOneDrive group policy in the Microsoft 365 admin center. OCSI is the coordination between office and OneDrive for syncing office documents to the cloud. How this will affect your organization: After this rollout, theEnableAllOcsiClientsgroup policy will be removed, and Microsoft Office and Microsoft OneDrive will be able to communicate smoothly to ensure existing Office features like autosave, version history, real time user collaboration, and merging in the case of conflicts can work properly for end users. Before this rollout, tenants had the option to disable this feature with a GPO, and when they disable the GPO, existing Office features like autosave, version history, real time user collaboration, and merging in the case of conflicts cannot work properly. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will be rolling out in April 2025. How this will affect your organization: With OCSI enabled for all tenants, end users will be able to take advantage of features such as autosave, real time user collab, and merging in the case of conflicts of Office files. Autosave is a feature that end users will see in Word, Excel, and PowerPoint files; it is a toggle at the top left of the file header that will ensure that even if the user does not manually save a file, the file will be saved automatically to OneDrive and SharePoint. With real time user collaboration, different users can collaborate on the same file at the same time. Version history allows users to see when and who made changes to a file and provides the ability to restore to a previous version of the file within the Office app. If there are conflicts within a file that does not require user input, Office will merge the conflicts and ensure that the Office file is up to date with the latest changes. If user input is required to merge conflicts, Office will show the merge conflicts and prompt the user to choose which edits to prioritize. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change, especially if the policy is disabled, educate them about autosave, real time user collab, and merging in the case of M365 application conflicts, and update any relevant documentation. For more information, seeAllow users to choose how to handle Office file sync conflicts. MC921752 — Retirement of the SharePoint SendEmail API We will be retiring the Utility.SendEmail API from SharePoint. The SP.Utilities.Utility.SendEmail could be used to send emails from custom applications or processes within SharePoint Online, including Power Automate, and custom workflows. From custom code the API can be referenced via REST as (“/_api/SP.Utilities.Utility.SendEmail”) while for CSOM, it would be “Utility.SendEmail” with more information on the original implementation atUtility.SendEmail methodfor CSOM. When this will happen: October 31, 2025 How this will affect your organization: Any components, custom code, or Power Automate connections that utilize the SP.Utilities.Utility.SendEmail API, should be updated before the end of life date. The API will stop providing services on the retirement date and will no longer send any email requests from that date. What you need to do to prepare: Migrate any custom code, power automate, processes or policies running within SharePoint Online that have been configured to send email using the SP.Utilities.Utility.SendEmail API. The following are recommended or alternative approaches: Use Microsoft Graph to send email using the user: SendMail API (Part of the Outlook mail workload)Automate creating, sending, and processing messages Customizations through Power Automate may also utilize the Outlook connector and utilize “Send an email” within the Actions.Overview of using Outlook and Power Automate Learn more: Retirement of the SharePoint SendEmail API Automate creating, sending, and processing messages Overview of using Outlook and Power Automate MC923413 — System generated emails from workflows and alerts will now show SharePoint Online as the sender display name We are making changes to system generated emails from SharePoint workflows and alerts display names.Note: this is a continuation of MC711021 (January '24). To align system generated emails with best practices, SharePoint Online workflow and alert emails will be displayed as “SharePoint Online”. There is no change to the underlying sending email address, no-reply@sharepointonline.com. If your organization uses the "Send email notifications from your domain" feature, the email address will comply with your configured domain. When this will happen: We are continuing the rollout and expect complete by late November 2024. How this will affect your organization: If your users have Outlook rules or other processes surrounding the email display name only, those will need to be updated accordingly. Existing policies and rules utilizing the email address will not be affected. Additionally, if you’re calling the "SendEmail" API or calling SharePoint workflow or alert services via CSOM or REST API’s those emails will follow the new display convention as well. What you need to do to prepare: Inform users of the potential change in their workflow and alert processes from SharePoint. MC915497 — SharePoint list and library rules will send from the no-reply@sharepointonline.com email address We're making a change to how emails are sent for customers that use list or document library rules, which can be created from the Automate dropdown. Users can specify an automated email based on when a change occurs, a new file or item is added, a file or item is deleted, and file or item metadata conditions. To align system generated emails with best practices, these emails will now come from the no-reply@sharepointonline.com email address with the display name "SharePoint Online". Previously, these emails would be sent on behalf of the user that made a file or item update. When will this happen: Available now How this will affect your organization: Your users may notice the change in email address and display name for certain business processes and workflows that rely on automated emails from SharePoint list or document libraries. What you need to do to prepare: No action is required, existing rules will continue to operate. If you have any email policies or workflows based on a specific sender, those will need to include the no-reply@sharepointonline.com address. For additional information review:Create a rule to automate a list or library - Microsoft Support MC915485 — Microsoft SharePoint: Updates to font management capabilities Microsoft 365 Roadmap ID420933 We are introducing updates that provide capabilities for managing custom fonts for Microsoft SharePoint and Microsoft Viva Connections. This includes the ability to hide theFrom Microsoftfont packages fromChange the look,the ability to apply a font package in your site templates, and updated availability for theFrom Microsoftfont packages. When this will happen: Targeted Release: We will begin rolling out mid-October 2024 and expect to complete by early November 2024 General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early November 2024 and expect to complete by early December 2024. How this will affect your organization: This rollout will include new Microsoft PowerShell commands that will allow you to get information about theFrom Microsoftfont packages and the ability to hide these font packages if desired. More details for these commands will be available in ourPowerShell documentation. We will also provide an update to add an additional site script action that will allow developers and administrators to include and apply font packages as a part of a site template. Sample action details: { "verb": "applyFontPackage", "fontPackageTitle": "Amasis MT", "fontPackageId": "1e7a7803-045d-44df-9c7a-d2f2f8562e51", "fontPackageStore": "OutOfBox" } This rollout will also include a change to allow tenants that meet the requirements for custom fonts to discover the feature without needing to activate the SharePoint brand center. For tenants that are currently using the Organization Assets Library functionality with Public content delivery network (CDN), these organizations will seeFontsand theFrom Microsoftfont packages inChange the lookwithout any additional actions. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Get started with the SharePoint Online Management Shell | Microsoft Learn(will be updated) MC912181 — Microsoft SharePoint: Add approvals to any document library Microsoft 365 Roadmap ID420336 As an extension to the previous communication MC757613(Updated) Microsoft SharePoint: Add approvals to any SharePoint list(originally sent March 2024, updated August 2024), we will soon add approvals to document libraries in Microsoft SharePoint Online. When this will happen: Targeted Release: We will begin rolling out early November 2024 and expect to complete by late November 2024. General Availability (Worldwide, GCC): We will begin rolling out early December 2024 and expect to complete by late January 2025. How this will affect your organization: Before this rollout: Users are not able to add approvals to document libraries in SharePoint Online. After this rollout, users will be able to configure approvals by going to theAutomatedropdown menu from the command bar in SharePoint Online document libraries and then selecting theConfigure Approvalsoption to enable and disable approvals on the library. Note: When editing files, any in-flight approvals will be cancelled if changes are saved. To discourage edits of in-progress approvals, files will open in view-only mode in Microsoft Word, Excel, and PowerPoint for the web, and the same Windows desktop applications will show that the document isMarked as final. After approvals are enabled, a user can create a file and submit it for approval. By creating an approval request and specifying the approver, the request will appear in theApprovalsapp in Microsoft Teams or can be approved directly in the library in SharePoint. Once approved, the file metadata is updated. Note: Disabling approvals will only hide the relevant columns. In-progress approvals will still be actionable in Teams. At any time, you can manually add approvals columns back into your views. Configure approvals in SharePoint Online: Enable configured approvals: Approvals column: Disable configured approvals: This feature is on by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Inform your users of the newApprovalsfunctionality for libraries and lists. Share the support documentationApprovals in lists, which will be updated before this rollout begins to include library support. MC909173 — Publishing new InfoPath Forms in SharePoint Online will not be allowed for inactive tenants in this December As announced earlier inMC616550 (June '23), InfoPath Forms Service is being deprecated and will be removed from existing tenants after July 14, 2026. To support this transition, we will prevent the publication of new InfoPath forms in SharePoint Online for tenants with no detected usage of the InfoPath forms service. This proactive action aims to reduce the migration effort for new InfoPath forms in anticipation of the service's retirement. Key Points: Major: Retirement update Timeline: After December 20, 2024, Microsoft will prevent the publication of new InfoPath forms for tenants who are not actively using InfoPath services. Action: Review and assess impact How this will affect your organization: After December 20, 2024, InfoPath designers and publishers will no longer be able to publish new forms to SharePoint Online as no active usage of the InfoPath forms service has been detected in your tenant over the past year. Existing published forms will remain unaffected, and end users can continue to fill in these forms in SharePoint Online if needed. What you need to do to prepare: As we have detected no usage of the InfoPath forms service in your tenant over the past year, we recommend running theMicrosoft 365 Assessment tooland using thePower BI InfoPath Reportto confirm this. If active usage is detected, please raise the issue with your support engineer for our further assistance. If you need a solution for the form scenario in your organization, we recommend using the modern solutions ofMicrosoft Power Apps,Microsoft Power AutomateorMicrosoft Forms, and additional details can be found in thisblog. MC906496 — Microsoft OneDrive and Microsoft SharePoint: New setting to disable presence in the file viewer Microsoft 365 Roadmap ID419814 Administrators can now use theMicrosoft SharePoint Online Management Shellto disable the user presence feature in the Microsoft OneDrive and SharePoint file viewer on a per-site collection basis. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late October 2024 and expect to complete by late November 2024. How this will affect your organization: Before this rollout: When previewing a file in the OneDrive and SharePoint file viewer, users can see the presence of other users who have the file open. This behavior will not change by default. After this rollout, if desired, SharePoint admins can use the SharePoint Online Management Shell to disable the presence feature for a given site collection. This can be done by updating to the latest version of the SharePoint Online Management Shell and runningSet-SPOSite -HidePeoplePreviewingFiles $truealong with a list of valid site identifiers. Learn more:Set-SPOSite (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn. By default, this feature is available for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation if you choose to enable this feature. MC905757 — Microsoft SharePoint: Customize your individual sites and experiences with fonts and themes Microsoft 365 Roadmap ID375500 Updated October 31, 2024: We have updated the content. Thank you for your patience. Coming soon for Microsoft SharePoint: Site owners will be able to create font packages and themes for their sites and experiences by combining the branding assets that the organization provides or by creating their own. TheChange the lookexperience will contain branding created in the SharePoint brand center (or with Microsoft PowerShell) for their organization as well as their own local site branding. These will continue to be previewed and applied via the Change the Look experience for your sites and experiences. When this will happen: Targeted Release: We will begin rolling out early October 2024 and expect to complete by late October 2024. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early November 2024 and expect to complete by late November 2024. How this will affect your organization: As communicated in MC905757 Microsoft SharePoint: Customize your individual sites and experiences with fonts and themes (October 2024), we are introducing a new site branding feature for SharePoint. We are adding an additional capability to this feature allowing site owners to copy branding assets utilized in another site for use within their site. This will create an independent copy of these site branding assets in the destination site. Notes: Themes will continue to be inherited from the hub for associated sites. Searching and copying site branding across sites in different geographies is not currently supported. Site owners will be able to create, rename, and delete themes and font packages (where available in a tenant). This will not have any impact on the themes and font packages provided from the organization or from Microsoft. Before this rollout: Site owners have limited ability to customize their sites and experiences with branding. After this rollout, site branding adds an additional option to customize a single site with a unique theme and font package created and managed by the site owners, adding this option to the branding available from your organization and from Microsoft. Note: Themes will continue to be inherited from the hub for associated sites. Site owners will be able to create, rename, and delete themes and font packages (where available in a tenant). This will not impact the themes and font packages provided from the organization or from Microsoft. What you need to do to prepare: Admins will need to take no action for this feature to be available. This will be available by default to all site owners without admin action and cannot be disabled. You may want to notify your users about this change and update any relevant documentation. Additional resources Site branding - Microsoft Support Microsoft Viva MC867656 — (Updated) Microsoft Viva Connections news notifications in GCC, GCC High, and DoD Microsoft 365 Roadmap ID410198 Updated October 10, 2024: We have updated the rollout timeline below. Thank you for your patience. With this feature update, existing news notifications in Microsoft Viva Connections will now be available in GCC, GCC High, and DoD. When this will happen: General Availability (GCC): We will begin rolling out late September 2024 (late August) and expect to complete by early October 2024 (early September). General Availability (GCC High, DoD): We will begin rolling out early October 2024 (early September) and expect to complete by late October 2024 (mid-October). How this will affect your organization: News notifications are delivered via Microsoft Teams in the desktop, mobile, and web environments in the following scenarios: News is published to a SharePoint team or communication site that a user follows or by someone that a user works closely with. News is boosted. Someone comments on a new News post. Someone "Likes" a News post. Someone is @mentioned in a comment on a news post. End users can control which notifications they want to see in the following ways: On Teams desktop and web, specific notification types can be selectively enabled or disabled underSettings > Notifications and activity > Viva Connections. These settings are respected on Teams mobile as well. On Teams mobile, notifications can't be selectively enabled or disabled, but users can toggle all push notifications (including Viva Connections) in the Teams mobile app underSettings > Notifications > General Activity > Apps on Teams. Notifications will still be visible under the Microsoft Teams activity feed. There is no tenant level setting to turn off Viva Connections News notifications. For more information, seeViva Connections News notifications. What you need to do to prepare: This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. MC846391 — (Update) Microsoft SharePoint: Feed for Viva Connections web part and Video news link retires starting September 1, 2024 Updated October 10, 2024: We have updated the content. Thank you for your patience. As communicated in MC846391 Microsoft SharePoint: Feed for Viva Connections web part and Video news link retires starting September 1, 2024 (August 2024), this is a reminder that we will start the second phase of retiring the Feed for Viva Connections web part and the Video news link on November 5, 2024. We will begin retiring theFeed for Viva Connections web partand theVideo news linkon September 1, 2024. OnSeptember 1, 2024,we removed the Feed for Viva Connections web part from the toolbox. Also, we will remove the Video news link from the+ Newmenu in the organizational site. Site editors will not be able to add a new feed for Viva Connections web part to a site or embed new video links to the Viva Connections feed. OnNovember 5, 2024, we will end support for feed for the Viva Connections web part and the Video news link. Site editors are encouraged to use the web partsNews,Viva Engage,File and Media, andHighlighted content, as well asvideo pagesas alternative solutions. Note: Any Feed for Viva Connections web parts that have not been replaced with the recommended alternative solutions byNovember 5, 2024,will result in an empty web part that no longer displays content or any Video news links that have not been removed. Visitors to the site will instead see an error message. What you need to do to prepare: This change will happen automatically on the specified dates. Site editors and SharePoint admins should plan for the retirement and update and/or replace the affected SharePoint sites with the recommended alternatives. Notify your users about this change and update any relevant documentation. For more information, refer to theViva Connections Feed web part and Video news link retirement support guidance. Microsoft Teams MC925999 — Microsoft 365 app: Auto release and check-in for Microsoft Places Coming soon for Microsoft Teams and Microsoft Places: New ways for users to check in to meeting rooms and prevent rooms from automatically releasing. After this rollout, customers will be able to check in through Teams Chat and email for all enabled rooms. The pre-rollout options to check in through Teams panels or Teams Rooms will continue. This message is related to MC922620Microsoft Places app ON by default(October 2024) When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-November 2024 and expect to complete by late November 2024. How this will affect your organization: Before this rollout, users are able to check in and auto-release rooms through these options: An attendee can check in through a Teams panel. An attendee can check in by joining a meeting through Microsoft Teams Rooms. After this rollout, check in and auto-release will need Teams panels on Teams app version 1449/1.0.97.2024061108 or higher. Users can choose from these three options to check in to a room: An attendee can check in through a Teams panel. (Same as before the rollout) An attendee can check in by joining a meeting through Microsoft Teams Rooms. (Same as before the rollout) The organizer or an attendee can check in through Teams Chat. (New) Any rooms that currently have auto-release and check-in enabled through Teams panels will automatically receive these additional check-in options without any extra setup required. These features are on by default. Check in through Teams Panel: Check in through Microsoft Teams Rooms: Left: Check in through Teams Chat at the start of the meeting. Right: Check in is successful: Check in through email for in person meetings: For all check in options, users will see that the room has been released in Chat: Note:Auto-release and check in does not currently support or automatically release the room for in-person meetings and non-Teams online meetings such as Zoom or Webex. These features will come soon. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Lean more:Enabling Auto Release for your rooms - Microsoft 365 Places | Microsoft Learn(will be updated before rollout) MC923415 — Microsoft Teams: Virtualized Desktop Infrastructure status indicator Microsoft 365 Roadmap ID423472 This new feature is designed to be a visual indicator of the optimization status in Microsoft Teams for Virtualized Desktop Infrastructure (VDI) users. Users in VDI used to rely on theellipsis(...)> Settings > Aboutmenu to display the optimization status for their session (AVD Media Optimized, Citrix HDX Media Optimized, VMware Media Optimized). The new status indicator will provide the user with an easy-to-understand status message, like "Optimized" or "Not Optimized", some contextual information about the optimization mode (optimized with the WebRTC-based solution or the new SlimCore-based solution), and in the not optimized case it will provide a brief description of the problem and an error code, for better supportability. When this will happen: Targeted Release: We will begin rolling out early December 2024 and expect to complete by late December 2024. General Availability (Worldwide, GCC): We will begin rolling out early January 2025 and expect to complete by late January 2025. How this will affect your organization: Once this feature is rolled out, users will be able to quickly understand whether their audio/video is optimized for virtual desktop environments (offloading to the endpoint/user's device) before joining a meeting and take actions to fix problems or report back to their IT support with an error code. This feature is available by default. What you need to do to prepare: As this feature introduces new UI components, admins should update their internal documentation and communications so that end-users understand the new status indicator feature. MC920298 — Microsoft Teams admin center: Admins can disable the ability to send messages in meeting chat before and after a meeting Microsoft 365 Roadmap ID422808 Coming soon for Microsoft Teams admin center: For the existingMeeting chatcontrol, we will add two new options that allow admins to disable meeting chat before and after a meeting,In-meeting only for everyone and In-meeting only except anonymous users. This message applies to Teams for Windows desktops and Mac desktops, Teams on the web, and Teams for iOS/Android. When this will happen: Targeted Release: We will begin rolling out early December 2024 and expect to complete by mid-December 2024. General Availability (Worldwide): We will begin rolling out early January 2025 and expect to complete by mid-January 2025. General Availability (GCC, GCC High): We will begin rolling out mid-January 2025 and expect to complete by late January 2025. General Availability (DoD): We will begin rolling out late January 2025 and expect to complete by early February 2025. How this will affect your organization: After this rollout, admins will find the two new options in the Teams admin center >Meetings > Meeting policies > Meeting engagement > Meeting chat. Admins can select from fiveMeeting chatoptions: On for everyone On for everyone but anonymous users Off In-meeting only for everyone (new) In-meeting only except anonymous users (new) Admins can select theIn-meeting onlyoptions to disable the ability of meeting participants to send messages in the meeting chat before or after the meeting, for meetings organized by specific users in their tenant. When one of theIn-meeting onlyoptions is selected, participants can read past chat history, but they can only send messages in the meeting chat while the meeting is active. The new options will be available for admins to configure. This rollout will respect the options selected by admins before the rollout. To use the new options, admins must select one of them. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation. Learn more:Manage chat in Teams meetings - Microsoft Teams | Microsoft Learn(will be updated before rollout) MC920179 — (Updated) Microsoft Teams: The new streamlined Chat and Channels experience Microsoft 365 Roadmap ID415249 Updated October 29, 2024: We have updated the rollout timeline below. Thank you for your patience. We’ve been listening to user feedback on the pace of work and the challenges of keeping up with conversations, managing messages scattered across different locations, and triaging quickly. To address this, we’ve streamlined the chats, teams, and channels experience to make it easier for users to stay on top of what matters most. For more details and screenshots, refer toMicrosoft Teams announces out a new chat and channels experience | Microsoft 365 Blog This message applies to Teams on Windows desktops, Mac desktops, the web, and iOS and Android devices. This message excludes Education tenants. We will send a future post with an update on the plan for Education tenants. When this will happen: Updated October 29, 2024: We have updated the rollout timeline below. Thank you for your patience. Public Preview / Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by mid-November 2024. General Availability (Worldwide): We will begin rolling out late January 2025 and expect to complete by early February 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out mid-April 2025 and expect to complete by late April 2025. How this will affect your organization: Before this rollout, users have separateChatandTeamsviews (apps) with no option to unify these views; custom sections of chats and channels were not possible; and there was no view for collecting all personal mentions in one list across chats and channels. The new experience brings chat, teams, and channels into one place, inChat, so users can easily navigate between all conversations without switching between contexts. Users start in the combinedChatview but can opt to keep chat separate from teams and channels like before. In the Chat view, users will see these sections (in order): Favoritescontaining any previously pinned chats and channels Chatssorted by most recent Teams and channels, organized in same order as in theTeamsview Also, users can create custom sections to organize projects and topics that can include individual, group, and meeting chats, as well as channels. Favorites, Chats,andTeams and channelsin one list in Teams for Windows: Favorites, Chats,andTeamsandchannelsin one list in Teams for iOS (also available for Android): New filters forUnread, Chat, Channels, Meetingsand more help users focus on relevant conversation in their list. Filters persist until turned off. The new @mention view gathers all personal @mentions into one interactive list. Users can quickly access messages with @mentions across chats, channels, and meetings. Customizing the experience Users can tailor their chat and channels experience in TeamsSettings. Users can choose to keep chat, teams, and channels combined inChat(default) or switch to separateChatandTeamsviews. In the combinedChatview, message previews are off by default to simplify the list. Users can turn on message previews inSettings. When using the separateChatandTeamsviews, users can still use the new filters and the @mentions view to triage and organize topics with custom sections. Starting the new experience A self-service guided onboarding flow in Teams will help users discover the new experience and configure it to their preferences. Users who prefer to keep chat and channels separate can easily do so during the onboarding process or later, without IT assistance. When the new experience is available in your tenant, this screen will display to users: The Get started button will take users to the new combined chat, teams, and channels experience in Chat, and highlight the location of settings. Users will have the option to defer the new experience up to three times over the course of approximately three days, providing flexibility while also moving an organization to the new experience overall. This feature is on by default. The new experience has no admin policy. Each user can make choices to optimize for how they work best. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. To help prepare organizations for the new features, product guides for admins and users will be available on the adoption web pageThe new Microsoft Teams chat and channels experiencebefore rollout begins. For admins whoopt in to emails for recommended Microsoft 365 training, an email for users will summarize the update when released. MC920084 — Microsoft Teams: Usage reports for bookable desks Microsoft 365 Roadmap ID421604 With this rollout, admins will have access to reports and insightful usage analytics for desk pools (workspace resource accounts) that have at least one associated peripheral. These capabilities will be available in the Teams Rooms Pro Management portal if the desk pool has aMicrosoft Teams Shared Devices licenseassigned. This message applies to tenants with Teams Rooms Pro or Teams Shared device licenses. When this will happen: General Availability (Worldwide): We will begin rolling out early December 2024 and expect to complete by mid-December 2024. General Availability (GCC): We will begin rolling out early January 2025 and expect to complete by mid-January 2025. How this will affect your organization: The Teams Rooms Pro Management portal will have a new tab underReportscalledDesk usage.Desk pools that have at least one peripheral associated and are licensed with a Teams Shared device license will appear under this tab. Admins will be able to review overall metrics about their desk pools such as the number of total associated desks, the number of desks that are unused, and the percentage of reservations that were unplanned. For each desk pool, they will be able to review more analytics such as utilization, total reservations, reservation occupancy (percentage of time that desk pool was utilized during reservations), and more. Admins will also be able to select a specific desk pool to review specific metrics, such as a peak utilization matrix. This change will be available by default to tenants with the required license and associated peripherals. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. We recommend that admins ensure they have Teams Shared Devices licenses in their tenant before this rollout. You may also want to notify your admin team about this change and update any relevant documentation. Also, we recommend setting up desk pools with up to 8 seats in each pool. We will show analytics for up to 8 desks per desk pool. Learn more:Setting up Bookable Desks in Microsoft Teams - Microsoft Teams | Microsoft Learn(will be updated soon after rollout) MC918570 — Microsoft Teams: Custom name on Teams panels Microsoft 365 Roadmap ID417153 Prior to this new feature, the display name on a Microsoft Teams panel could not be customized. It would always match the Global Adress Book (GAL) name for the account that is shown in Teams and Outlook. With this rollout, we will be providing admins with the ability to customize this display name. This feature will be supported for accounts that have a Teams panel and a Teams Rooms Pro or Teams Shared Device license. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early December 2024 and expect to complete by mid-December 2024. How this will affect your organization: An admin must choose to use the feature. This feature is set to off as default, so there is no change to the current experience otherwise. To change the display name on the panel, navigate toTeams Rooms Pro Management Portal>Planning>Inventoryand thenclick on the account you’d like to customize. On the pane that opens on the right, there will be a custom name field which an admin can edit to enter in the new display name. Please note that the custom name will be displayed on the Teams panel home screen, so we recommend making sure it is clear and understandable to your users. By default, this field will be filled with the GAL name. In addition, please note that this will not change the display name shown on Microsoft Teams Rooms if you have one inside of the room. Within 24 hours of the name being updated, the Teams panel home screen will reflect the new name. The home screen will also have a tooltip that, when selected, will show the user the GAL name. In Teams admin settings, an admin can view the GAL name and custom name if one has been applied. It is not possible to edit the name in these admin settings. Editing can only be done in the Teams Rooms Pro Management Portal. If you would like to remove the new custom name, you can simply remove the custom name from the field in the Pro Management Portal, and the display name on Teams panel will default back to the GAL name. What you need to do to prepare: This rollout will happen by the specified date with no admin action required. You may want to update any relevant documentation as appropriate and plan to update your devices to the latest Teams app when it becomes available. MC916866 — (Updated) Microsoft Teams: Shifts Graph APIs in beta moved to production (v1.0) Microsoft 365 Roadmap ID422813 Updated October 24, 2024: We have updated the rollout timeline below. Thank you for your patience. The Shifts Graph APIs will transition from beta to production. This change brings enhanced stability and reliability to the APIs, ensuring a seamless experience for developers and users. When this will happen: General Availability (Worldwide and GCC): We will begin rolling out mid-January 2025 (previously mid-November) and expect to complete by late January 2025 (previously late November). How this will affect your organization: You may continue using the API endpoints in beta. However, we recommend migrating to the production endpoints. To refer to a list of all production (v1.0) APIs, go to the following page and navigate toTeamwork and communications>Shift management:Microsoft Graph REST API v1.0 endpoint reference - Microsoft Graph v1.0 | Microsoft Learn This update is available by default. What you need to do to prepare: To update Microsoft Graph APIs from beta to production, change your API calls from the beta endpoint to the v1.0 endpoint and thoroughly test your application to ensure compatibility. Check for any differences between the versions, and update any documentation accordingly. MC915488 — Reminder: Microsoft Teams Phones impacted by retirement of CNS Service API support--Software application update required As communicated previously in MC896706 about the retirement of CNS Service API support for older Android clients, this retirement impacts Microsoft Teams devices including Teams Phone devices. To avoid disruption, an update to Teams phone application version 1449/1.0.94.2023082303 or greater is required for Teams Phone devices. These updates must be completed before January 15, 2024, to avoid disruption. Teams devices are governed by the Modern Lifecycle Policy and require users to stay on the most up-to-date version of the Teams phone devices application. Automatic updates ensure that users have the latest capabilities, performance and security enhancements, and service reliability. When will this happen: On January 15, 2025 (previously by the end of September 2024), Microsoft will stop supporting the legacy services infrastructure for chat messaging, impacting Teams Phone devices on app versions earlier than 1449/1.0.94.2024011003. How this will affect your organization: The retirement of the CNS service API incoming calls, voicemail and missed call notifications scenarios on Teams Phone devices. Teams Phone devices app versions 1449/1.0.94.2024011003 and later are not impacted. Update Teams Phone devices to latest Teams Phone app or an app version greater than 1449/1.0.94.2024011003. Manual update process In the Teams admin center, select the device category underTeams devices.Select all respective devices from the list and then selectUpdate. UnderManual updates, select the Teams application and then select theUpdatebutton to update to the latest app. If all your devices are eligible to receive automatic updates, use that option to get the latest Teams app version. Automatic update process To help bring the devices to the latest versions, automatic updates will continue at an accelerated pace to ensure adherence to the retirement timeline. Updates can include both firmware and Teams app updates, as applicable to bring the device to the latest versions. These updates will be scheduled outside of normal business hours in the local time of the device, to help minimize impact to your organization. Since it is important that the devices get updated as soon as possible, we will not adhere to the configured maintenance window for the devices. For organizations with users around the globe, we recognize that "outside of normal business hours" might affect you differently. We apologize for the impact this may have on your users. MC915486 — (Updated) Microsoft Teams: Users can take control during screensharing on the web Microsoft 365 Roadmap ID420327 Coming soon to Microsoft Teams on the web: Users will be able to use theTake controlfeature during screensharing on the web, like they can in Teams for Windows desktop. When this will happen: Targeted Release: We will begin rolling out early December 2024 and expect to complete by mid-December 2024. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-January 2025 and expect to complete by late January 2025. How this will affect your organization: Before this rollout, users are not able to use theTake controlfeature in Teams on the web. After this rollout, users can use the feature: This feature will be available to Teams on the web users. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.< Before rollout, we will update this post with revised documentation. MC913445 — (Updated) Microsoft Teams: Intelligent recap support for ad-hoc meetings and calls Microsoft 365 Roadmap ID411573 Updated October 30, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Teams: Intelligent recap will be available for ad-hoc meetings and calls, like those started fromMeet nowor chat. After this rollout, Teams Premium or Microsoft 365 Copilot licensed users can browse a meeting recording by speakers and topics, as well as access AI-generated notes, AI-generated tasks, and name mentions after an ad-hoc meeting ends. This message applies to Teams on Windows and Mac desktops, Teams on the web, and Teams for Android/iOS. When this will happen: Targeted Release: We will begin rolling out early December 2024 (previously early November) and expect to complete by mid-December 2024 (previously mid-November). General Availability (Worldwide, GCC): We will begin rolling out early January 2025 (previously mid-November) and expect to complete by early February 2025 (previously early December). How this will affect your organization: After this rollout, users in your tenant can turn on the recording or transcription to get intelligent recap for ad-hoc meetings started fromMeet nowor chat (1:1 chat or group chat), just as they can with scheduled meetings. After these meetings end, users will see the meeting thumbnail in the meeting chat or call chat. Users can select theView recapbutton to access theRecappage: TheRecappage: This new feature is on by default. Note:Additional improvements will be available in future releases, including Recap notifications, Notes, Content, and more. What you need to do to prepare: No admin action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation. Learn more:Meeting recap in Microsoft Teams - Microsoft Support(will be updated before rollout) MC912709 — (Updated) Microsoft Teams: Bookable desks and BYOD rooms supported in GCC Updated November 5, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Teams: Bookable desks and Bring Your Own Device (BYOD) rooms. To set up these two solutions, admins must have access to the Teams Rooms Pro Management portal. Bookable desk features in Teams desktop, including plug-in-based reservations and peripheral discovery and inventory in the Teams Rooms Pro Management portal (released earlier in 2024), will be available to enhance your flexible work environments. In the future, admins will also get valuable analytics and insights for space management and planning. Bring your own device (BYOD) meeting room features including Shared Display mode and peripheral discovery, inventory, and reports in the Teams Rooms Pro Management portal (released earlier in 2024) also will be available. When this will happen: General Availability (GCC): We will begin rolling out early December 2024 (previously early November) and expect to complete by mid-December 2024 (previously mid-November). How this will affect your organization: Before this rollout, admins are not able to set up bookable desks and BYOD rooms in their tenant. After this rollout, admins will have the option to set up bookable desks and BYOD rooms in their tenant. This feature is default off on Teams desktop client. To enable bookable desks and BYOD: Open Microsoft PowerShell in admin mode and runConnect-MicrosoftTeams. If you don't have the Microsoft Teams module installed, please runInstall-Module -Name MicrosoftTeams -Force -AllowClobber To confirm the current status of the policy, runGet-CsTeamsBYODAndDesksPolicy To enable the policy for the whole tenant, runSet-CsTeamsBYODAndDesksPolicy -Identity "Global" -DeviceDataCollection Enabled. You can also enable the policy for only a specific group of users. For more information on the policy and how to get started, please see ourdeskandroomguides. We also have auser support article for desksandrooms. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout To prepare for this feature, we recommend reviewing the published guides and documentation, discussing this new feature with your team, and share instructions if needed. Learn more Setting up Bookable Desks in Microsoft Teams - Microsoft Teams | Microsoft Learn Bring Your Own Device Rooms in Pro Management Portal - Microsoft Teams | Microsoft Learn For users:First things to know about bookable desks in Microsoft Teams - Microsoft SupportandUse shared display mode in meeting rooms - Microsoft Support MC912707 — (Updated) Microsoft Teams: New policy for voice and face enrollment will default to "On" (configure now) Microsoft 365 Roadmap ID413708 Updated October 25, 2024: We have updated the content. Thank you for your patience. A newcsTeamsAIPolicypolicy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-January 2025) will give IT admins more control over voice and face enrollment settings, allowing organizations to manage these features based on their needs. After rollout, voice and face profile enrollmentwill be enabled by default, and users can benefit from voice isolation, speaker recognition, and attribution in meeting rooms, resulting in smarter meeting recaps and enhanced functionality for Microsoft 365 Copilot in meetings. To access Copilot features, a Microsoft 365 Copilot license is required. This message applies to Teams for Windows desktop and Mac desktop. NOTE: Microsoft doesn't use the voice and face profiles of users to train any models or for any other purposes other than providing the voice and face enrollment feature in Microsoft Teams. When this will happen: General Availability (Worldwide, GCC): The new Microsoft PowerShell cmdlets are available now for preparation and to ensure a smooth transition. The policy takes effect starting in mid-January 2025 and is expected to be fully in effect by mid-January 2025. How this will affect your organization: Before this rollout, the current policycsTeamsMeetingPolicyhas a single setting,EnrollUserOverride, that allows the administrator to enable or disable the enrollment of both face and voice profile of users. After this rollout, the newcsTeamsAIPolicywill replace the existing enrollment setting incsTeamsMeetingPolicy. The newcsTeamsAIPolicyhas two settings,EnrollFaceandEnrollVoice, that will be set toEnabledby default. What you need to do to prepare: This rollout will happen automatically by the specified date. Review your current configuration to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation. If your organization prefers to disable voice and face enrollments, review and update your settings before mid-January 2025. To help you get started, review: Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn Learn more:Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn MC912178 — Microsoft Teams: Download Transcription and View RTMP-In 708 Captions for Town hall and Webinar Microsoft 365 Roadmap ID417156 Before this rollout, in a Microsoft Teams town hall or webinar, the organizer does not have the option to download the transcript after the event has ended. Also, if an organizer has indicated through the meeting options before the event that an RTMP-In feed will be used, the 708 captions does not display in the attendee captions or transcript. After this rollout, in a town hall or webinar, the organizer can download the transcript after the event has ended. Also, if an organizer has indicated through the meeting options before the event that an RTMP-In feed will be used, the 708 captions will be displayed in both the attendee captions and transcripts. The transcript can be downloaded in Teams for Windows and Mac desktops and Teams for the web. The 708 captions during the meeting will be displayed in Teams for Windows and Mac desktops, Teams for the web, and Teams for Android and iOS. When this will happen: Targeted Release: We will begin rolling out early November 2024 and expect to complete by mid-November 2024. General Availability (Worldwide, GCC): We will begin rolling out mid-November 2024 and expect to complete by late November 2024. How this will affect your organization: To indicate before the event has started if an encoder or RTMP-In feed will be used, go to the event in the Teams calendar > SelectManage event> SelectMeeting options> EnableRTMP-In To download transcripts after the town hall or webinar, go to the event in the Teams calendar > SelectManage event> SelectRecordings> SelectDownload transcripts This change will be on by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation. Learn more Manage town hall recordings in Microsoft Teams - Microsoft Support(will be updated before rollout) Use RTMP-In in Microsoft Teams(will be updated before rollout) MC911620 — Microsoft Teams: New Event chat for Premium town halls Microsoft 365 Roadmap ID418117 Coming soon to Microsoft Teams: Everyone including attendees will be able to chat with each other in a town hall. The newEvent chatfeature will be optimized to support a large number of messages and people chatting at one time.Event chatis available for town halls scheduled by organizers that have Teams Premium and can be configured through meeting options by the organizers who have scheduled the town hall. This message applies to Teams for Windows desktop, Teams Mac desktop, Teams on the web, and Teams for Android/iOS. When this will happen: Targeted Release: We will begin rolling out early November 2024 and expect to complete by mid-November 2024. General Availability (Worldwide): We will begin rolling out mid-December 2024 and expect to complete by late December 2024. How this will affect your organization: Before this rollout: In a Teams Premium town hall, only presenters, organizers, and co-organizers can chat with each another in a private event group chat. After this rollout, all users including attendees in Teams Premium town halls will be able to chat. NewEvent chatis only available during the event and will only display the last 200 messages sent in the town hall. The chat panel will be optimized to support up to 20,000 users and a large volume of messages per second. Organizers, co-organizers, and presenters can still chat with each another in the private event group chat. Event chatwill be on by default for all Premium town halls in your organization. If you do not want this experience for your organization or for certain people in your organization, you can disable this feature with user-level policies in the Teams admin center or with Microsoft PowerShell. Messages forEvent chatin town halls are only stored in the mailbox of the organizer and are not stored in the attendees' mailboxes. These messages will remain in the organizer’s mailbox for up to 30 days. The tenant administrator will not be able to see who accessed the messages or which messages the attendees accessed during the town hall or meeting. The attendees' view ofEvent chatin a town hall: What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. You may also set the user level policy for certain organizers if you do not wish for them to useEvent chatin their town halls. To disableEvent chatfor organizers in your organization: Set-CSTeamsEventPolicy -Identity[User's identity] -TownhallChatExperienceNone If you would like to try this feature before early November 2024, please email EventMembersDGL@microsoft.com. Before rollout, we will update this post with revised documentation. MC908117 — Microsoft Teams: Swap screens on Teams Rooms on Android Microsoft 365 Roadmap ID415243 Coming soon to Microsoft Teams Rooms on Android: As an admin, you can configure dual display mode and swap the screens of dual display devices using device settings and the Teams admin center. This feature allows you to deliberately set the display mode of your device and also to fix reversed display installations remotely and at scale, enhancing your device management capabilities. A Teams Rooms Pro license is required for this feature. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by late November 2024. General Availability (GCC High): We will begin rolling out early December 2024 and expect to complete by mid-December 2024. How this will affect your organization: Before this rollout Teams Rooms on Android devices automatically enter dual display mode when two external displays are physically connected to a Teams Rooms on Android device. Because the display mode depends only on the physical connection to the device, rooms can be easily misconfigured when external displays are accidentally disconnected or intentionally unplugged by room users without admin approval. If external displays are set up in reverse (with the main display on the left and the extended display on the right), admins are not able to correct the misconfiguration with remotely. Admins must send someone to each affected room to manually swap cables. After this rollout A Teams Rooms on Android device will only operate in dual display mode if admins physically connect two external displays to the device and explicitly set the device to run in dual display mode using Teams admin settings on the device or the Teams Rooms on Android configuration profile in the Teams admin center >General > Dual display mode. If dual display mode is enabled for a device but only one external display signal is detected through the physical connection to the device, an error message about the disconnected display is shown on the device, prompting room users to contact IT support for resolution. This setting helps ensure that the Teams Rooms on Android app is showing the user interface configured by the admin. Teams Rooms devices with dual displays are designed with the main display (where the calendar is shown) on the right side and the extended display (where the date, time, and room information are shown) on the left side. When dual display devices are reversely installed, you can fix display positioning errors made during device setup with minimal effort. You can swap the display using Teams admin settings on the device or the Teams Rooms on Android configuration profile in the Teams admin center >General > Dual display mode > Swap screens This feature will be off by default and available for admins to configure. What you need to do to prepare: After updating your Teams Rooms on Android devices to the latest app version through the Teams admin center, you may notify your users about the change and update your training and documentation as appropriate. This rollout will happen automatically by the specified date with no admin action required before the rollout. MC908115 — (Updated) Microsoft Teams: Meeting organizers can turn off copying of captions, transcript and recap Microsoft 365 Roadmap ID416072 Updated October 30, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Meeting organizers with eligible licenses will have aMeeting optioncontrol calledTurn off copying and forwarding of meeting chat, live captions, and transcript.When this control is enabled, meeting participants won’t be able to copy the meeting chat, live captions, live transcript, or any insights generated from intelligent meeting recap. This message applies to tenants with Teams Premium licenses on Teams for Windows desktop, Mac desktop, Teams on the web, and Teams for Android/iOS. When this will happen: Targeted Release: We will begin rolling out early December 2024 (previously mid-November) and expect to complete by mid-December 2024 (previously late November). General Availability (Worldwide, GCC): We will begin rolling out mid-December 2024 (previously late November) and expect to complete by early January 2025 (previously early December). General Availability (GCC High, DOD): We will begin rolling out early February 2025 (previously early January) and expect to complete by late February 2025 (previously early January).Note:Only applicable for live captions and transcript. How this will affect your organization: Before this rollout: Meeting organizers have a control inMeeting optionsforTurn off copying or forwarding of meeting chat. After this rollout: TheTurn off copying or forwarding of meeting chatcontrol inMeeting optionswill become theTurn off copying and forwarding of meeting chat, live captions, and transcriptscontrol, which allows meeting organizers to prevent meeting participants from copying meeting chat, live captions, transcripts, and AI-generated insights in the meeting recap. Forwarding and sharing messages to Outlook will also be disabled. This updated control will be on by default and available for meeting organizers to enable. What you need to do to prepare: No admin action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation. Before rollout, we will update this post with revised documentation. MC907108 — Microsoft Teams: Admin email support for "Report a problem" on Teams Rooms on Android Coming soon to Microsoft Teams Rooms on Android: As an admin, you can configure an email address for receiving issues submitted by users through theReport a problemfeature on Teams Rooms on Android devices. The email address can be set through device settings or the Teams admin center. This feature will allow you to collect logs and feedback directly from your device Teams Rooms on Android devices, enhancing your ability to triage, respond, and escalate issues as needed. Microsoft 365 Roadmap ID415247. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by late November 2024. General Availability (GCCH): We will begin rolling out early December 2024 and expect to complete by mid-December 2024. How this will affect your organization: Before the rollout: When room users encounter issues while using the conference room, there is no way for them to directly report issues to admins from the Teams Rooms on Android devices. After the rollout When you configure an email address in Teams admin settings> General > Logs and feedback,theReport a problemoption on Teams Rooms on Android devices will be enabled, and any feedback submitted by room users usingReport a problemwill be sent to the email address in the device settings. You can also choose to have app logs automatically attached to the feedback you receive in email. Admin controls in the Teams admin center: Admin controls in the device settings: Users can accessReport a problemfrom theHelpbutton on the home screen or theMorebutton in meetings.Report a problemcan also be accessed on the pre-sign in screens. The email you will receive will contain the feedback entered by the room user and will include information like the room account, device model, and app version. If configured, the email will also include app logs as an attachment. NOTE: If you’re reaching out to Microsoft Support regarding an issue you receive through email, make sure to download complete device logs from the Teams admin center. For more information, seeCollect Teams Android device logs | Microsoft Learn. This feature will be off by default and available for admins to configure. If you don’t have physical access to the Teams Rooms on Android device, you can also remotely configure an email address for log and feedback collection through the Teams Rooms on Android configuration profile found on the Teams admin center. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. After the rollout: After updating your Teams Rooms on Android devices to the latest app version through the Teams admin center, configure your devices as desired, notify your users about the change, and update your training and documentation as appropriate. MC906501 — Microsoft Teams: Net Promoter Score survey on Teams Rooms on Android Coming soon to Microsoft Teams Rooms on Android: Users can rate how likely they are to recommend Microsoft Teams Rooms from 1 to 5 and provide their comments in a Net Promoter Score (NPS) survey delivered on Teams Rooms on Android devices. Microsoft 365 Roadmap ID415245. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by late November 2024. General Availability (GCCH): We will begin rolling out early December 2024 and expect to complete by mid-December 2024. How this will affect your organization: Before this rollout: NPS surveys do not appear on Android devices. After this rollout Like Teams Rooms on Windows and other Teams platforms, NPS surveys will appear periodically after meetings end on Teams Rooms on Android devices. NPS surveys gauge the likelihood of users recommending Microsoft products and services to their peers, and the feedback gathered is used to improve Microsoft products and services. This feature will be on by default and available for admins to allow or prevent NPS surveys. If you do nothing, the surveys will be on by default. As an admin, you can prevent room accounts from getting NPS surveys with Microsoft PowerShell. Learn more atManage feedback policies in Microsoft Teams - Microsoft Teams | Microsoft Learn. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. After updating your Teams Rooms on Android devices to the latest app version through the Teams admin center, you may want to notify your users about this change and update your training and documentation as appropriate. MC903632 — (Updated) Microsoft Teams Rooms on Android: 3x3 video gallery on dual displays Microsoft 365 Roadmap ID415239 Coming soon for Teams Rooms on Android: We will increase video participants displayed in Gallery view for dual displays from 10 to 18 video participants total, 9 (3x3) on each screen, that will be displayed when no content is being shared during meetings. This rollout aligns the Gallery experience with Teams Rooms on Windows. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by early November 2024. General Availability (GCC High): We will begin rolling out late November 2024 and expect to complete by late November 2024. How this will affect your organization: Due to device capability requirements and performance implications, 3x3 video gallery support for dual displays will only be available on the following Teams Rooms on Android devices: Yealink MeetingBar A40, Poly Studio X52, and Poly Studio G62. We will include more details in the Microsoft Learn documentation that will be included in the release notes. Before rollout, we will update this message with a link to the release notes. This change will be on by default. What you need to do to prepare: No action is needed to prepare for this change. Please notify your users about this new experience and update your training and documentation as appropriate. MC899179 — (Updated) Microsoft Teams: Menu bar icon for Mac devices (GCC, GCCH, DoD) Microsoft 365 Roadmap ID416069 Updated October 22, 2024: We have updated the content. Thank you for your patience. Coming soon: Microsoft Teams for Mac devices is adding an extension to the macOS Menu Bar, where users will find a Teams icon with a persistent indicator of their presence status. Users can change their presence status with the Menu Bar extension, which also contains additional actions for streamlining Teams workflows. When this will happen: Targeted Release: We will begin rolling out mid-October 2024 and expect to complete by mid-November 2024 (previously late October). General Availability (GCC, GCC High, DoD): We will begin rolling out mid-November 2024 and expect to complete by mid-December 2024. How this will affect your organization: Before this rollout, Teams users on Mac devices do not have a persistent indicator of their Teams presence status. After this rollout, Teams users on Mac devices will have the Menu Bar extension by default. If a user prefers not to have the icon present in the macOS Menu Bar, it can be disabled from the Teams Settings. More details on how to use or disable Teams Menu Bar extension will be available in the documentation:Take quick actions in Microsoft Teams from a Mac - Microsoft Support The feature will be available for users after an update to the latest version of Teams: 24277.3502.3161.3007 What you need to do to prepare: The feature will be enabled automatically for users after Teams updates to the build containing this functionality. No admin action is required. You may want to notify your users about this change and update any relevant documentation. MC892055 — (Updated) Microsoft Teams: Participant roster grouping in Teams BYOD meeting rooms Microsoft 365 Roadmap ID413711 Updated October 16, 2024: We have updated the rollout timeline below. We will not be rolling this out to organizations in GCC High or DoD during the timeline outlined below. We will communicate via Message center when we are ready to proceed. Organizations in GCC High and DoD can safely disregard this message. Thank you for your patience. Coming soon for Microsoft Teams: When users join a Teams meeting with their laptop in bring your own device (BYOD) meeting rooms, they will appear in the In-room participant section of the roster, which enables individual identification and meeting intelligence capabilities. As communicated in MC814577(Updated) Microsoft Teams: Roster grouping for in-room participants through Proximity Join for Teams Rooms on Windows(July 2024), we will launch this same experience in September 2024 for joining a nearby meeting with a Microsoft Teams Room and a companion device. Unique to BYOD meeting rooms, the roster group will be displayed asMeeting spaceif the connected device is NOT identified in the Teams Pro Management Portal (PMP). If the device is identified in the PMP, the roster group will display the configured meeting room name. This message applies to Teams for Windows and Mac desktops. When this will happen: Targeted Release: We will begin rolling out mid-October 2024 (previously early October) and expect to complete by late October 2024 (previously mid-October). General Availability (Worldwide): We will begin rolling out mid-October 2024 and expect to complete by late October 2024. General Availability (GCC): We will begin rolling out mid-October 2024 and expect to complete by late November 2024. How this will affect your organization: Before this rollout: Users joining a Teams meeting from a BYOD meeting room will be displayed as an individual participant in theParticipantsroster. Room node treatments will only be applicable to users joining from a Microsoft Teams Room. After this rollout, this update will be available by default for all users joining a Teams meeting from a BYOD meeting room. After joining, in-room participants will automatically be grouped under the room node on the Participant roster. The two scenarios in which in-room participants can be ungrouped from the room node are: Raised hand: We will continue to follow the sequential order of raised hands on the roster. In-room participants who use their companion device to raise their hand will appear on the roster in the order in which they raised their hand. Role assignment: For changes in roles (presenters and attendees), in-room participants can be broken up and placed in the appropriate category on the roster. (This is an existing feature before this rollout.) In both scenarios, room information will be listed below participant name. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Before rollout, we will update this post with revised documentation. MC887377 — (Updated) Microsoft Teams: Refreshed view of all your teams and channels page Microsoft 365 Roadmap ID411779 Updated October 16, 2024: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams: An updated view of all teams on oneYour teamspage. An updatedManage Team > Channelspage, helping team owners and team members to filter, search and manage channels in the team from one page. Team members will be able to navigate to the list of channels from the Your teams page with a single click. This message applies to Teams on Windows desktop, Mac desktop, and on the web. When this will happen: Targeted Release: We will begin rolling out early October 2024 and expect to complete by early October 2024. General Availability (Worldwide): We will begin rolling out mid-October 2024 and expect to complete by late October 2024. General Availability (GCC, GCCH, DoD): We will begin rolling out early December 2024 and expect to complete by early December 2024. How this will affect your organization: Before this rollout, Team owners and members can hover on the team name on the left side of Teams, select the three dots, and go to Manage team to individually manage the team and its channels. Team owners and members can see all the teams they belong to from the Your teams page. Selecting a team on the Manage teams page takes Team owners and members to the team’s General channel. After this rollout: Team owners and members will be able to view their teams from the Your teams page, and access channels in each team. To navigate to the Your teams page, select Your teams and channels from the three dots in the top right corner of the left panel Team owners and members can select a team name to review the channels in the team and choose channels of interest to show in Teams Team owners and members can search and sort on theYour Teamspage or hide all channels. When all channels of a team are hidden, the team will not show in the Teams and channels list on the left side of Teams. Team owners and members can also view the channels in the team from theManage Team > Channelspage, and show channels of interest by filtering, sorting, and searching for channels in the team from one page. These features will be on by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your Team owners and members about this change and update any relevant documentation. MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar Microsoft 365 Roadmap ID409226 Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Team Premium customers: Event organizers will be able to set sensitivity labels for town halls and webinars. Sensitivity labels allow organizations to protect and regulate access to sensitive content created through collaboration in Teams. Sensitivity labels are available only for Teams Premium users on Mac and Windows desktops. When this will happen: Targeted release: We will begin rolling out in mid-October October 2024 (previously early October) and expect to complete by late October 2024 (previously mid-October). General Availability (Worldwide, GCC): We will begin rolling out in mid-October 2024 and expect to complete by late November 2024 (previously late October). How this will affect your organization: Before this release: Sensitivity labels were not available for town halls and webinars. After this rollout, events created or updated by an organizer with a Teams Premium license can apply a sensitivity label to their event. Organizers will be notified if their configured settings are not valid for the selected sensitivity. Specific options underEvent accessmay be enabled or disabled based on the sensitivity label set for the event For upcoming events that have already been scheduled prior to rollout, the sensitivity of the event will be set toNone. If an event organizer chooses to modify the sensitivity for a scheduled event after the rollout, this action may affect event settings that were previously configured. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Before rollout, we will update this post with revised documentation. MC884009 — (Updated) Microsoft Teams: Start/stop recording on Teams Rooms on Windows Microsoft 365 Roadmap ID412072 Updated October 31, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Windows: Users can start or stop recording meetings directly from a Teams Rooms on Windows device. This feature requires a Teams Rooms Pro license and Teams Rooms on Windows app version 5.2. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-January 2025 (previously early December) and expect to complete by late January 2025 (previously mid-December). General Availability (GCC High): We will begin rolling out early February 2025 (previously mid-December) and expect to complete by mid-February 2024 (previously mid-January). General Availability (DoD): We will begin rolling out mid-February (previously early January) and expect to complete by late February 2025 (previously mid-January). How this will affect your organization: Before the rollout: When attending a meeting using a Teams Rooms on Windows device, if users want to record the meeting, they need to also join the meeting on a companion device to initiate the meeting recording. After the rollout Start/stop recording is supported in any meeting where a participant belongs to the same tenant as the organizer, including scheduled meetings, ad-hoc meetings, channel meetings (only for channel members), and Teams Cast sessions. Users can selectStart recordingorStop recordingfrom theMoremenu, shown here at the bottom of the screen When users start recording aMeet noworWhiteboardsession initiated from a Teams Rooms on Windows device, users must ensure that they invite themselves to the meeting so they can access the meeting chat on their Teams desktop or mobile app where the recording file will be available after the meeting. This feature will be on by default and available for admins to configure. As an admin, you can allow or prevent users (including room accounts) from recording meetings with the Teams meeting recording policy: Using the Teams admin center: Learn more atManage Teams recording policies for meetings and events - Microsoft Teams | Microsoft Learn. Using Microsoft PowerShell: Learn more atSet-CsTeamsMeetingPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn. NOTE: Both the meeting organizer and the recording initiator (room account) need to have recording permissions to record the meeting, or the start/stop recording button will not be available. Also, if the meeting organizer usesMeeting optionsto remove permissions from the room account to record the meeting, the start/stop recording button will not be available as well. Start/stop recording is not supported in these scenarios: Teams calls including P2P, group, and PSTN calls External/cross-tenant Teams meetings and calls Third-party meetings and calls including Direct Guest Join and SIP NOTE: Avoid assigning Microsoft OneDrive for Business licenses to your room accounts to ensure that IT-managed room accounts do not become owners of the recording files. What you need to do to prepare: After your Teams Rooms devices are updated to the 5.2 app, configure the desired meeting recording policy, notify your users about this change, and update your training and documentation as appropriate. This rollout will happen automatically by the specified date with no admin action required before the rollout. MC866454 — (Updated) Microsoft Teams: VDI users can upload custom backgrounds Microsoft 365 Roadmap ID410366 Updated October 29, 2024: We have updated the rollout timeline below. Thank you for your patience. If Microsoft Teams users want to change what appears behind them in a video meeting, they can either blur their background, use Teams virtual background templates, or with a Teams Premium license, they can change their Teams meeting background to a branded logo or image specific to their company. After this rollout, users on the new VDI (Virtual Desktop Infrastructure) solution for Teams can replace their background with any desired image. This message applies to theNew VDI solution for Teamsonly. When this will happen: Targeted Release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October). General Availability (Worldwide): We will begin rolling out early November 2024 (previously late October).and expect to complete by mid-November 2024 (previously early November. General Availability (GCC): We will begin rolling out mid-November 2024 (previously early November) and expect to complete by late November 2024 (previously late October). How this will affect your organization: Users on the new VDI optimization for Teams will be able to upload their own background image as their background through theVideo effects and settingsoption This feature is on by default. What you need to do to prepare: Make sure you meet the minimum system requirements for the new VDI solution as described inNew VDI solution for Teams - Microsoft Teams | Microsoft Learn This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. MC866447 — (Updated) CAPTCHA Verification for Anonymous Meeting Participants Updated October 15, 2024: We have updated the rollout timeline below. Thank you for your patience. Microsoft Teams tenants will soon be able to enable verification for anonymous meeting participants via CAPTCHA. This release of CAPTCHA Verification for Anonymous Meeting Participants will be rolling out across Microsoft Teams Desktop, Mobile and Web and will provide additional security against malicious bot and third-party app joins. When this will happen: General Availability (GCC): We will begin rolling out late October 2024 (previously early October) and expect to complete by mid-November 2024 (previously mid-October) How this will affect your organization: Tenants can enable anonymous meeting attendee verification via CAPTCHA in the Teams Admin Center. When enabled, any users that join the meeting as an anonymous user will be required to pass a CAPTCHA verification before landing in the meeting (including the meeting lobby, if enabled). What you need to do to prepare: This feature is off by default and Tenant Admins will need to enable CAPTCHA verification for their tenants through Meeting policies in the Teams Admin Center. MC862235 — (Updated) Microsoft Teams: Digital signage on Teams Rooms on Windows Microsoft 365 Roadmap ID400700 Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Windows: Inform, connect, and engage your employees with digital signage on Teams Rooms on Windows. Users can view dynamic content and relevant information on front-of-room displays when devices are not in use. Admins can configure tenant-wide and room-specific settings from the Teams Rooms Pro Management portal. Integrations with selected third-party digital signage providers (Appspace,XOGO) are available, along with the use of web URLs as signage sources. This feature requires the Teams Rooms Pro license and the Teams Rooms on Windows app version 5.2. When this will happen: General Availability (Worldwide): We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October). How this will affect your organization: Before the rollout: When Teams Rooms on Windows devices are idle, the front-of-room display remains static, showing the Teams Rooms home screen with the room information, calendar, and background image. After the rollout You can configure digital signage on your Teams Rooms on Windows devices to show dynamic content and relevant information (such as how to guides, important announcements, company news, upcoming events, and more) on the front-of-room displays when the device is not in use for meetings or presentations. Tapping the touch console during signage mode brings users back to the home screen. When the device is in signage mode, you have the option to show the Teams Rooms banner so that users can see the room information and calendar alongside the signage. You can also adjust the display period of signage mode – the activation and deactivation timers as well as whether signage mode will adhere or bypass the operating system’s screen timeout setting. Supported signage sources include selected third-party digital signage providers (Appspace, XOGO) and web URLs. To integrate with supported third-party content management systems, a separate subscription to the provider is needed. If you don’t use any of the supported providers, you can use the custom URL option and enter a web application URL. To ensure URLs load successfully, the URL must start with https, be publicly available on the internet (no authentication required), and can be viewed in an iframe. NOTE: Microsoft SharePoint and Microsoft OneDrive URLs are not supported for the custom URL option. To enable digital signage for your tenant, go to Teams Rooms Pro Management portal >Settings > Digital signage> turn ON the setting as desired. By default, the Global Admin and Teams Rooms Pro Manager role have permissions to configure tenant-wide digital signage settings, including turning the feature on and off, adding and deleting signage sources, and assigning signage settings to any room in the tenant. The Global Admin and/or Teams Rooms Pro Manager role can use the Role-based Access Controls (RBAC) to grant additional users permissions to manage digital signage settings for the tenant or for specific rooms/room groups. This feature is off by default and available for admins to configure. What you need to do to prepare: Start planning your digital signage deployment strategy and governance model, deciding between centralized, localized, or blended approach to content creation, distribution, and management. You may also begin preparing content on the supported signage sources. This rollout will happen automatically by the specified date with no admin action required before the rollout. After your devices are updated to the 5.2 app, configure digital signage for your tenant as desired,notify your users about this change, and update any relevant documentation. MC854652 — (Updated) Microsoft Teams: Meeting participants can choose a breakout room from a list Microsoft 365 Roadmap ID121269 Updated November 4, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Microsoft Teams meeting organizers can make the list of breakout rooms visible to all meeting participants and allow them to choose which room to join. Enabling this setting in breakout rooms allows participants to move freely from one room to another, simplifying breakout room coordination for meeting organizers and participants. This message applies to Teams for Windows, Mac, and the web. When this will happen: Targeted Release: We will begin rolling out early January 2025 (previously early December) and expect to complete by mid-December 2024 (previously mid-December). General Availability (Worldwide, GCC): We will begin rolling out mid-January 2024 (previously mid-December) and expect to complete by late January 2025 (previously early January). General Availability (GCC High, DoD): We will begin rolling out early February 2025 (previously early January) and expect to complete by late February 2025 (previously late January). How this will affect your organization: Before this rollout: Only the meeting organizer can assign meeting participants to breakout rooms. Participants cannot move between rooms. After this rollout: Meeting participants can select their breakout rooms of choice if the meeting organizer selects this option during setup. Organizers can look for the new feature under the breakout rooms panel when setting up breakout rooms: This feature is on by default and accessible to all meeting participants on the affected platforms if enabled by meeting organizers. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. MC818885 — (Updated) Microsoft Teams: Multiple camera view for Teams Rooms on Windows Microsoft 365 Roadmap ID402517 Updated October 29, 2024: We have updated the rollout timeline below. Thank you for your patience. Microsoft Teams Rooms on Windows will be soon able to send up to four single-stream USB camera feeds to render on the receiver side, so remote meeting participants can view all cameras simultaneously. This opt-in feature requires admins to first enable the multiple camera view and map cameras to the desired order that will be displayed on the receiver side. With multiple camera view enabled, remote meeting participants will be able to follow all the action in the room and manually switch to the desired room. This message applies to Teams for Desktop (Windows, Mac). When this will happen: Targeted release: We will begin rolling out early December 2024 (previously early November) and expect to complete by December 2024 (previously mid-November). General Availability (Worldwide): We will begin rolling out mid-December 2024 (previously mid-November) and expect to complete by late December 2024 (previously late November). General Availability (GCC): We will begin rolling out in mid-December 2024 (previously mid-November) and expect to complete by early January 2025 (previously early December). How this will affect your organization: Before the rollout Multiple camera views are not available in Teams Rooms on Windows. After the rollout A multiple camera view can create more visibility and coverage for large and complex spaces, such as multipurpose rooms, classrooms, and executive boardrooms. Admins can set up multiple camera views in two ways: Admins can configure settings on a local device by turning on the Multiple camera view toggle and using the dropdown menu to map the cameras. Admins can configure multiple camera viewusing Remote Accessin theMicrosoft Teams Rooms Pro Management portal. After the feature is enabled, in-room participants can disable multiple camera view with the Camera chevron button on the meeting console. This action will return the device to a single camera view, and all receiver-side participants will see a single camera view. This in-room setting will only affect that meeting and the device will revert to the admin settings for the next meeting. Remote participants will see the multiple camera view by default. On the top right corner of the room's video tile, a remote participant can use the arrows to switch to the desired camera view. This toggle will only affect the remote participant's own view and will not affect other meeting participants. Admin setting to configureMultiple camera viewon a local device In-meeting console setting with Multiple camera view toggle What you need to do to prepare: To prepare for the change, create a plan for the rooms that may require multiple cameras in consideration of the space, meeting scenario, and the desired experience for in-room and remote participants. Then, configure the multiple camera view on the local device or in the Teams Pro Management portal and notify your users about this new experience. You may want to update relevant training documentation. Before rollout, we will update this post with revised documentation. MC814584 — (Updated) Microsoft Teams: Q&A will be generally available in late August 2024 Microsoft 365 Roadmap ID395935 Updated October 9, 2024: We have updated the rollout timeline below. Thank you for your patience In Microsoft Teams, organizers of meetings, webinars, and town halls will soon be able to enable a Q&A feature for their events. This interactive tool allows for real-time engagement, enabling organizers to field and answer questions from attendees. It is particularly effective for large, structured gatherings such as all-hands meetings or training sessions. When this will happen: General Availability (GCC): We will begin rolling out early September 2024 (previously late August) and expect to complete by late October 2024 (previously late September). How this will affect your organization: Organizers can enable the Q&A feature in their Microsoft Teams meetings via Meeting Options by toggling on Q&A. This provides structured dialogue, allowing attendees to ask questions, reply, and react by clicking the Q&A icon within the meeting interface. Moderators can enable moderation to review questions before publishing them live. Additionally, they can allow attendees to submit questions anonymously by turning on the anonymous posts option. This Q&A feature be automatically enabled upon rollout. Enabling Q&A through Meeting Options while setting up your meeting Moderate attendee questions in Q&A as the organizer What you need to do to prepare: Please inform the meeting organizers at your organization that they can use the Q&A feature in their meetings, webinars and town hall. Additional Resources: Follow these instructions to enable the Q&A feature: Q&A in Microsoft Teams meetings - Microsoft Support Your organization may have requirements to limit which users can enable the Q&A feature. Please use Meeting Policies in the Teams admin center to manage which users can enable the Q&A feature in their events: Manage Q&A in Teams meetings and events - Microsoft Teams | Microsoft Learn Using Teams Town Hall with Teams Q&A: Get started with town hall in Microsoft Teams - Microsoft Support MC814577 — (Updated) Microsoft Teams: Roster grouping for in-room participants through Proximity Join for Teams Rooms Microsoft 365 Roadmap ID400702 Updated October 23, 2024: We have updated the content. Thank you for your patience. When joining a meeting in Teams Room on Windows or Android with a companion device (laptop or mobile), in-room participants will be grouped under the room node. Participants must join through Proximity Join. This update includes additional UI elements to create visual clarity of the in-room participants who are together. When this will happen: General Availability (Worldwide): We will begin rolling out late September 2024 (previously mid-September) and expect to complete by mid-November 2024 (previously late September). General Availability (GCC, GCC High, DoD): We will begin rolling out mid-September 2024 and expect to complete rollout by late October 2024 (late September). How this will affect your organization: This update is available by default if the companion device has enabled the Bluetooth setting and the Teams Room device has any one of the following XML <SkypeSettings> configuration settings enabled: <BluetoothAdvertisementEnabled>true</BluetoothAdvertisementEnabled> <UltrasoundAdvertisementEnabled>true</UltrasoundAdvertisementEnabled> <RoomQRcodeEnabled>true</RoomQRcodeEnabled> On the roster, in-room participants will automatically be grouped under the room node. The two scenarios in which in-room participants can be ungrouped from the room node are: Raised hand: For raised hand, we continue to follow the sequential order of raised hands. Therefore, in-room participants who use their companion device to raise their hand will be broken up and ordered accordingly. Role assignment: For changes in roles (Presenters/Attendees), in-room participants can be broken up and placed in the appropriate category on the roster. In both scenarios, the room information will be listed below the participant's name. What you need to do to prepare: This rollout will happen automatically. You may want to notify your users about this change and update any relevant documentation as appropriate. MC810411 — (Updated) Microsoft Teams Rooms: Enhanced cross-platform meetings via SIP join Microsoft 365 Roadmap ID400703 Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Microsoft Teams Rooms on Windows will be enabled to join meetings like Google Meet, Zoom, Cisco Webex, Amazon Chime, RingCentral, and others from conferencing services that support SIP (Session Initiation Protocol) join. You’ll experience the look and feel of a Teams Rooms meeting with access to some third-party platform in-meeting controls (depending on the platform being used). Features include up to 1080p video quality, dual screen support, different meeting layouts, and HDMI ingest. This capability requires a SIP calling plan from a Cloud Video Interop (CVI) partner; this plan is currently available throughPexip in the Microsoft Azure Marketplace. This message applies to Teams Rooms customers with a Pro license. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October 2024). General Availability (GCC High): We will begin rolling out mid-November 2024 (previously late September) and expect to complete by late November 2024 (previously mid-October). How this will affect your organization: Before this rollout: Teams Rooms does not support third-party SIP conferencing services to join meetings. Teams Room does support dialing into SIP endpoints. After the rollout: The default state of this feature is off. Device settings with all conferencing services enabled. Teams Rooms Pro license and plan with CVI provider needed What you need to do to prepare: If you do not want to use this feature, no action is needed. This rollout will not impact you. To enable SIP dialing from the Teams Rooms on Windows: Ensure the Teams Room has a Pro license assigned Ensure the Teams Room has a license to dial SIP from one of our certified CVI providers Run the PowerShell commands to assign the right policy to the Teams Room Change the settings in the device to enable one or more conferencing services to dial from the Teams Room Learn more What’s new from Teams Rooms and Devices at InfoComm 2024 - Microsoft Community Hub Enable Teams Rooms devices to join third-party meetings - Microsoft Teams | Microsoft Learn (will be updated just before rollout begins) This rollout will happen automatically by the specified date with no admin action required before the rollout. If you enable the feature, you may want to notify your users about this change and update any relevant documentation as appropriate. MC809602 — (Updated) Microsoft Teams: New skin tone settings and reactions Microsoft 365 Roadmap ID323766 Updated October 23, 2024: We have updated the rollout timeline below. Thank you for your patience. With skin tone settings and reactions in Microsoft Teams, users will be able to set a preferred skin tone for relevant emojis and reactions. Each user can change their own skin tone setting in the Teams appSettings > Appearance and accessibilitymenu or in the emoji/reaction menu on Desktop or web. The skin tone rollout will apply to emojis and reactions in chats, channels, and meetings on all Teams platforms (Teams for Desktop, Teams for web, Teams for Mac, and Teams Mobile). When this will happen: Targeted Release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October). General availability (Worldwide, GCC): We will begin rolling out early November 2024 (previously late October) and expect to complete by mid-November 2024 (previously early November). General availability (GCC High, DoD): We will begin rolling out mid-November 2024 (previously mid-November) and expect to complete by late November 2024 (previously late October). How this will affect your organization: Changing skin tone in the emoji menu in Teams for Desktop Changing skin tone in Teams Settings > Appearance and accessibility in Teams for Desktop Changing skin tone in Teams Settings > Appearance on Teams Mobile The selected skin tone appears in reactions in chats, channels, and meetings What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. We will update this post before rollout with revised documentation. MC808828 — (Updated) Microsoft Teams: Custom background and daily restart windows for Teams panels Microsoft 365 Roadmap ID402183 Updated October 10, 2024: We have updated the rollout timeline below. Thank you for your patience. We are pleased to share that you will soon have the ability to upload and apply custom backgrounds to your Microsoft Teams Panel devices to showcase your brand identity. This feature requires either a Teams Rooms Pro license or a Teams Shared Device license and will be available with the next Teams Panels app update. The next app update will also allow you to configure a daily device restart window for every Teams panel device, regardless of license. The restart window will be set from 2:00am to 3:00am in the device's local time zone by default to keep the device healthy. When this will happen: General Availability (Worldwide and GCC): We will begin rolling out early September 2024 (previously early August) and expect to complete by late October 2024 (previously late September). How this will affect your organization: Custom backgrounds: To set custom backgrounds for your Teams Panel devices, go to Teams admin center >Teams devices>Panels>Configuration profiles>AddorEdit>Device settings>Background>Use a custom background. You can upload one image at a time. The image must meet these requirements: Minimum resolution: 1280x720 Format: JPG, JPEG, or PNG Minimum size: 100KB Maximum size: 2MB Note: The image may be scaled to fill the frame or center cropped to fit the display if the ratio and resolution do not match. After the images are saved in the configuration profile and the configuration profile is assigned to one or multiple Teams panel devices, the custom background will be applied to the devices that are logged in with a properly licensed resource account. You can also switch the background from the custom image to one of the default images or vice versa on your Teams panel (Settings>Teams admin settings>Backgrounds). To replace the custom background saved on the device, you must go to the Teams admin center and upload and save a new image in the configuration profile. Daily device restart window: By default, the daily device restart window will be between 2:00am to 3:00am in the device’s local time zone. You will be able to adjust this window or turn it off on the device or in Teams admin center. To change it on the device, go to your Teams panel device settings(Settings > Teams admin settings > Device restart). To change it remotely, go to Teams admin center >Teams devices>Panels>Configuration profiles>AddorEdit>General>Daily device restart window> save and assign the changes in configuration profiles to one or multiple devices. What you need to do to prepare: This rollout will happen by the specified date with no admin action required before the rollout. You may want to update any relevant documentation as appropriate and plan to design custom background images for your devices. We will update this post with a link to our learn docs with design guidelines when it is available. MC808822 — (Updated) Microsoft Teams: Custom background and daily restart windows for Teams panels (GCC High) Microsoft 365 Roadmap ID402183 Updated October 10, 2024: We have updated the rollout timeline below. Thank you for your patience. We are pleased to share that you will soon have the ability to upload and apply custom backgrounds to your Microsoft Teams Panel devices to showcase your brand identity. This feature requires either a Teams Rooms Pro license or a Teams Shared Device license and will be available with the next Teams Panels app update. The next app update will also allow you to configure a daily device restart window for every Teams panel device, regardless of license. The restart window will be set from 2:00am to 3:00am in the device's local time zone by default to keep the device healthy. When this will happen: General Availability (GCC High): We will begin rolling out early September 2024 and expect to complete by late October 2024 (previously late September). How this will affect your organization: Custom backgrounds: To set custom backgrounds for your Teams Panel devices, go to Teams admin center >Teams devices>Panels>Configuration profiles>AddorEdit>Device settings>Background>Use a custom background. You can upload one image at a time. The image must meet these requirements: Minimum resolution: 1280x720 Format: JPG, JPEG, or PNG Minimum size: 100KB Maximum size: 2MB Note: The image may be scaled to fill the frame or center cropped to fit the display if the ratio and resolution do not match. After the images are saved in the configuration profile and the configuration profile is assigned to one or multiple Teams panel devices, the custom background will be applied to the devices that are logged in with a properly licensed resource account. You can also switch the background from the custom image to one of the default images or vice versa on your Teams panel (Settings>Teams admin settings>Backgrounds). To replace the custom background saved on the device, you must go to the Teams admin center and upload and save a new image in the configuration profile. Daily device restart window: By default, the daily device restart window will be between 2:00am to 3:00am in the device’s local time zone. You will be able to adjust this window or turn it off on the device or in Teams admin center. To change it on the device, go to your Teams panel device settings(Settings > Teams admin settings > Device restart). To change it remotely, go to Teams admin center >Teams devices>Panels>Configuration profiles>AddorEdit>General>Daily device restart window> save and assign the changes in configuration profiles to one or multiple devices. What you need to do to prepare: This rollout will happen by the specified date with no admin action required before the rollout. You may want to update any relevant documentation as appropriate and plan to design custom background images for your devices. We will update this post with a link to our learn docs with design guidelines when it is available. MC808160 — (Updated) Microsoft Teams: Office 365 Connectors feature retires starting August 15, 2024 Updated October 16, 2024: Updated information related to Office 365 Connectors Retirement in Teams - Webhook URL Migration. Thank you for your patience. As shared in the last communication, we are publishing guidance for owners of webhook-based connectors to update their URLs with a new structure. To allow ample time for replacing URLs, connector owners will have untilJanuary 31, 2025, which is an extension from our previous deadline of December 31, 2024.See below for complete guidance. Webhook-based connectors within the O365 Connectors service in Teams are transitioning to a new URL structure due to the implementation of further service hardening updates. During this transition, you may receive notifications to update your configured connector to use the new URL. We strongly recommend that you update your connector immediately to prevent any disruption to connector services. URLs for all webhook-based connectors must be updated by January 31, 2025 for the connectors to continue posting messages into Teams.Keep in mind the entire O365 Connectors service in Teams will be retired at the end of 2025, so consider moving your webhooks to the Workflows app within Teams to avoid conducting another migration. Documentation:Create incoming webhooks with Workflows for Microsoft Teams - Microsoft Support How this will affect your organization: This change is needed only for webhook-based Connectors such as Incoming Webhook and third-party connectors where a URL is provided for posting messages. The change is not required for polling-based connectors such as RSS. To update webhook URLs for existing O365 Connectors, follow these steps:Manage Microsoft 365 connectors and custom connectors - Microsoft Teams | Microsoft Learn Go toManage Channelin a Teams channel, selectEditunder the Connectors option, and selectConfiguredsection. Review the existing connections listed on this page. 2.Do one of the following to generate a new URL: For connectors that contain a webhook URL, selectManageandUpdate URL. For other types of connectors, remove the connector and recreate the connector configuration. Replace the old URL with the new URL (or the new connection in the service that triggers the post). You'll know the new URL is ready for you to copy when the Configure page shows a message that the URL is updated ("Url is up-to-date"). What you need to do to prepare: The below dates are still unchanged and were communicated in previous updates: Entire O365 Connector service in Teams will retire in December 2025. Developers will no longer be able to create new Office 365 Connectors from the Developer Portal starting August 15th, 2024. Additional documentation: Create incoming webhooks with Workflows for Microsoft Teams - Microsoft Support Browse and add workflows in Microsoft Teams - Microsoft Support Note about parity features for the Workflows app We are currently developing a method for webhooks in the Workflow app to support the following scenarios and will share more details before March 30, 2025. Post messageCard formatted message payloads (so you do not have to reformat the payload to adaptive card) Post to private channels MC806095 — (Updated) Classic Microsoft Teams: Uninstallation resuming for Windows only Updated October 14, 2024: As an update, we would like to inform you that we are resuming the automatic uninstallation of classic Teams in your organization starting October 21, 2024. The attempt to uninstall classic Teams will commence in a staggered rollout. This message applies to: Teams for Windows on non-VDI and VDI with the new Teams Only policy. Please see MC807466 for Mac details on the automatic uninstallation. VDI customers in persistent environments where Classic Teams is version 1.7.00.7956 or higher. Persistent VDI environments are environments where Classic Teams was installed with the .exe installer in Appdata\Local. Note:For customers in non-persistent VDI environments where Teams was installed using the MSI in C:\Program Files (x86), this MC Post does not apply, and IT admins should remove Classic Teams from the golden image. What you need to do to prepare No additional changes are needed. This is for informational purposes only. Can I uninstall classic Teams manually? Please refer toHow to uninstall the classic Teams clientfor details. --Original message for reference-- Out of caution, we have paused automatic uninstallation of classic Microsoft Teams due to a rare issue impacting the Teams Meeting Add-in in Microsoft Outlook application. This message applies to Teams for Windows only. We will update this message when we are ready to resume the uninstallation. How this will affect your organization This pause will only impact customers who have not already uninstalled classic Teams. This issue could result in the Microsoft Teams Meeting Add-in in Outlook disappearing from the Outlook application for Windows or could cause failure when users try to schedule or join Teams meetings. What you need to do to prepare If your users are experiencing this issue, a temporary workaround is to use the Microsoft Teams Calendar to schedule or join meetings. To repair users who continue to experience the Teams Meeting Add-in issues in Outlook, please refer toTeams meeting add-in missing from Outlook and new Teams - Microsoft Teams | Microsoft Learn Can I uninstall classic Teams manually? Customers who experience this issue after the automatic uninstallation of classic Teams or after they manually uninstall classic Teams can review the troubleshooting steps inTeams meeting add-in missing from Outlook and new Teams - Microsoft Teams | Microsoft Learn Additional details can be found in theWhat happens if we can’t update users to new Teamssection ofEnd of availability for classic Teams client MC803293 — (Updated) Microsoft Teams: Enhanced Chat contextual info and Search Microsoft 365 Roadmap ID398956 Updated September 25, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams: As in the General channel, chat users will have access to contextual information includingPeople,Pinnedmessages,Sharedfiles and links, and will be able to search from chat. This message applies to Teams for Desktop, web, and Mac. When this will happen: Targeted Release: We will begin rolling out late July 2024 and expect to complete by late July 2024. General Availability (Worldwide and GCC): We will begin rolling out early September 2024 (previously mid-Augus) and expect to complete by mid-September 2024 (previously late August). General Availability (GCC High, DoD): We will begin rolling out mid-September 2024 and expect to complete by mid-January 2025 (previously early October). How this will affect your organization: Before this rollout: Users lacked one place to find contextual information in chat. After this rollout, users can select the new entry point in the top right corner of the chat window to access contextual chat information(People, Pinnedmessages,Sharedfiles and links). Users can also search the chat and pin multiple messages: The default state of this feature is on and is accessible to all Teams users (Desktop, web, Mac). What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate. Before rollout, we will update this post with revised documentation. MC798684 — (Updated) Microsoft Teams: Custom backgrounds for Teams Rooms on Android Microsoft 365 Roadmap ID380671 Updated October 10, 2024: We have updated the rollout timeline below. Thank you for your patience. Soon, you can upload images on the Microsoft Teams admin center to apply as custom backgrounds for your Teams Rooms on Android devices to showcase your brand identity or provide support information in your meeting rooms. This feature requires a Teams Rooms Pro license and will be available with the next Teams Rooms on Android app release. When this will happen: General Availability (Worldwide and GCC): We will begin rolling out early August 2024 (previously early July) and expect to complete by mid-August 2024 (previously mid-July). General Availability (GCC High): We will begin rolling out mid-August 2024 and expect to complete by late October 2024 (previously late September). Note: There can be a delay between when features are released by Microsoft and when they become available on a particular device model and make. How this will affect your organization: To manage custom backgrounds for your Teams Rooms on Android devices, log intoTeams admin center> go toTeams devices>Teams Rooms on Android> selectConfiguration profiles>AddorEdit>Device settings>Background> selectUpload a custom background. You can upload up to three images and specify which one goes to the main display, extended display, or touch console. Note: In a dual screen setup, the main display is where the room calendar is shown and is meant to be placed on the right side. The extended display is where the date/time and room information is shown and is meant to be placed on the left side. No matter how many screens your devices may have, the main display and extended display inputs are required in the Teams admin center configuration profile, while the touch console input is optional. When you push the configuration profile to a single screen device, only the main display image will show up. When you have two front-of-room displays or when you connect a second display later, the extended display image will be shown. If no image is uploaded for the touch console, a purple gradient default image will be displayed as the background. Custom background image files must meet the following requirements: Minimum resolution: front-of-room display (1920 x 1080), touch console (1280 x 720). Format: JPG, JPEG, and PNG. Maximum size: 20MB. Note: If the aspect ratio and the resolution of the image do not match with the aspect ratio and resolution supported by the display, the image may be scaled to fill the frame of the display and/or center-cropped. Once the images are saved in the configuration profile and the configuration profile is assigned to your Teams Rooms on Android devices, at the next device restart, the custom background image will be applied to the devices that are logged in with a resource account that has a Teams Rooms Pro license. On your Teams Rooms on Android device settings (Settings>Teams admin settings>General>Background), you can switch the background of your device from the custom image pushed to the device to one of the default images or vice versa. To change the custom image saved on the device, you must go to the Teams admin center. What you need to do to prepare: Plan on designing custom background images for your devices and updating your devices to the latest app version through the Teams admin center. More detailed design guidelines similar to the Teams Rooms on Windows PSD templates will be provided on the Microsoft Learn website closer to the release. MC797476 — (Updated) Teams: Updated developer tools to share content from Teams apps to chats, channels, and meetings Microsoft 365 Roadmap ID394670 Updated October 10, 2024: We have updated the rollout timeline below. Thank you for your patience. Today, users can share content to a Microsoft Teams meeting directly from a standalone webapp (in the browser) if developers have embedded aShare-in-Meetingcontrol in their webapps. Today, this control allows users to share content only to an ongoing Teams meeting (or a new ad-hoc meeting) on the same device. In this rollout, we will retain the control's existing capabilities, and we will enhance the control to enable users to share content to a meeting scheduled for the future. We will combine theShare-in-Meetingcontrols with the existing Share to Teamsdialog box, so users can use one dialog box to share from a Teams app to Teams chats, channels, or meetings. We are also introducing the ability for users to choosePresent Nowfrom the dialog to present contentin a Teams meeting.Developers can choose to opt into the features in this rollout. This rollout applies to Teams for Windows, the web, and Mac. When this will happen: Public Developer Preview: We will begin rolling out early June 2024 and expect to complete by mid-June 2024. Targeted Release: We will begin rolling out early September 2024 (previously early August) and expect to complete by mid-October 2024 (previously mid-September). General Availability (Worldwide, GCC): We will begin rolling out mid-September 2024 (previously mid-August) and expect to complete by late October 2024 (previously late September). How this will affect your organization: Additional enhancements for developers in this this rollout: When a meeting begins, the app side panel is opened automatically for the user who shared the content to the meeting. Exposes shared content information for the app to get the list of content shared, display the content, and have it readily available in the side panel. Notifies the meeting participants through an experience in the meeting chat that a user has shared content in the meeting. App developers can embed the Share to Teams control on their external webapp Using theShare to Teamscontrol, users can select a chat, channel, or meeting to share their content to. Users can also choose to present the contentontoin a Teams meeting with thePresent Nowfeature. What you need to do to prepare: This rollout will happen by the specified date with no admin action required before the rollout. Please notify your app developers about this change and update any relevant documentation as appropriate. Before rollout, we will update this post with revised documentation. MC797474 — (Updated) Microsoft Teams: Channel cards Microsoft 365 Roadmap ID397883 Updated October 10, 2024: We have updated the content below with additional information. Thank you for your patience. Microsoft Teams users will soon be able to get a quick overview about a channel using Channel cards. Channel cards will rollout across Microsoft Teams for desktop and web. Channel cards can be found by hovering over the channel name in the header or wherever a channel is mentioned. Channel cards will provide information about a channel, including the description, last activity time, team name, and membership information. The card also provides a quick entry to notification settings, owner channel management, and the channel roster. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling early July 2024 and expect to complete by late October 2024 (previously late September). How this will affect your organization: Users will have a simpler way to get important information about channels. This new feature provides key contextual information as well as quick actions. What you need to do to prepare: This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. MC792603 — (Updated) Microsoft Teams: Ask to join a shared channel with a channel link Microsoft 365 Roadmap ID325330 Updated October 10, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams: In-tenant users who attempt to access ashared channelwith a link will be able to request to join the channel. Channel owners will receive the join request and can decide to approve or deny request. This rollout applies to Teams for Desktop and Mac. When this will happen: Targeted Release: We will begin rolling out mid-June 2024 and expect to complete by mid-June 2024. General Availability (Worldwide, GCC): We will begin rolling out late June 2024 and expect to complete by late June 2024. General Availability (GCC High, DoD): We will begin rolling out mid-July 2024 and expect to complete by late October 2024 (previously mid-September). How this will affect your organization: Before the rollout, a user who selects a channel with a link receives aYou don’t have accessmessage. After the rollout, a user who selects a channel with a link receives will be able to ask to join a channel After the rollout, out-of-tenant users who click on a shared channel link from another tenant will continue to see theYou don’t have accessmessage. Admins cannot turn off this feature. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate. Before rollout, we will update this post with revised documentation. MC783217 — (Updated) Microsoft Teams: Disable attendee emails for town halls and webinars Microsoft 365 Roadmap ID392826 Updated October 16, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: In Microsoft Teams, we are releasing a toggle to disable attendee email notifications for town halls and webinars. When will this happen: Targeted Release: We will roll out early October 2024 (previously mid-September) and expect to complete mid-October 2024 (previously late September). General Availability (Worldwide): We will roll out mid-October 2024 (previously early August) and expect to complete late October 2024 (previously mid-August). General Availability (GCC): We will roll out late October 2024 (previously early September) and expect to complete early December 2024 (previously late November). How this will affect your organization: This is useful for organizers who want to send email notifications from third-party platforms. When this toggle is turned on, attendee emails will be enabled and will be sent through the Teams Events email platform. When this toggle is turned off, all attendee emails from the Teams Event Email platform will be disabled. The toggle button will be enabled upon rollout. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate. MC781595 — (Updated) Microsoft Teams: Tenant-wide policy for permission to download meeting transcription Microsoft 365 Roadmap ID332800 Updated October 22, 2024: We have updated the content below for accuracy. Thank you for your patience. Coming soon for Microsoft Teams: A new policy for IT admis to restrict permissions to download new meeting transcript files (stored in Microsoft OneDrive) for all users in the tenant. Admins can exempt people from the policy who are members of specified security groups such as governance or compliance specialists who require download access to meeting transcripts. This rollout applies to Teams for Mac and Teams for desktop. When this will happen: Targeted Release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May). General Availability (Worldwide, GCC): We will begin rolling out mid-June 2024 (previously late May) and expect to complete by late June 2024 (previously early June). General Availability (GCC High): We will begin rolling out late August 2024 (previously mid-July) and expect to complete by mid-September 2024 (previously late July) General Availability (DoD): We will begin rolling out late September 2024 (previously mid-August) and expect to complete by late November 2024 (previously mid-October). What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation as appropriate. Learn more:Block the download of Teams meeting recording files from SharePoint or OneDrive - Microsoft Teams | Microsoft Learn(We will update this comm before rollout with revised documentation.) MC750668 — (Updated) Microsoft Teams: Access Workflows from the three-dot menu on shared file Microsoft 365 Roadmap ID381643 Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Microsoft Teams will be bringing Workflows powered by Microsoft Power Automate to the three-dot menu for files shared in Teams chat or channels. When this will happen: Targeted release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October). Worldwide: We will begin rolling out early November 2024 (previously late October) and expect to complete by late November 2024 (previously early November). GCC: We will begin rolling out early December 2024 (previously late October) and expect to complete by mid-December 2024 (previously early November). How this will affect your organization: To make sure Microsoft Teams provides the best workflow experience for our users, we are making it easier to configure and run workflows for files. A user will be able to select the three-dot menu on files shared in Teams chat or channels, and then chooseWorkflows. FromWorkflows, the user will choose an instant workflow to run on a file. The user must set up the workflows in advance. A user can set up a new workflow for files by selectingSee more workflowsat the bottom of the three-dot menu. This launches the Workflows task module, where a user can choose a template to start setting up a new workflow. Examples of file workflows include Request approval for selected file, Get notified in Teams when a file is updated, Create a PDF copy of the file, and Add a task for this file. If the Power Automate app is disabled in the Teams admin center, users will not see this option in the three-dot menu. This feature will only be available in the New Teams client on the desktop and on the web. What you need to do to prepare: No action is needed from you to prepare for this rollout. You may want to notify your users about this change so they can find the new entry point for Workflows. MC727452 — (Updated) Microsoft Teams: Organizers can configure who can record and transcribe Microsoft 365 Roadmap ID116819 Updated October 17, 2024: We have updated the rollout timeline below. Thank you for your patience. We are changingWho can recordtoWho can record and transcribefor organizers with a Microsoft Teams Premium license for desktop or mobile. When this will happen: Targeted Release: We will begin rolling out mid-June 2024 (previously early June) and expect to complete by late June 2024 (previously mid-June). General Availability (Worldwide): We will begin rolling out late June 2024 (previously mid-June) and expect to complete by late November 2024 (previously late September). How this will affect your organization: If an admin turned onTranscriptionin the Teams admin center, Teams meeting organizers reviewingMeeting optionswill seeWho can record and transcribe, with two options: Organizers and co-organizers Organizers, co-organizers, and presenters With this rollout, organizers can manage the roles that can start recording and transcription for a meeting. What you need to do to prepare: No action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate. Learn more Admins: TheRecording & transcriptionsection ofTeams settings and policies reference - Microsoft Teams | Microsoft Learn Users:View live transcription in Microsoft Teams meetings - Microsoft Support MC726122 — (Updated) Microsoft Teams: View, download, and delete Microsoft OneDrive transcript files Microsoft 365 Roadmap ID365720 Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. We are beginning the process to standardize all transcript storage to OneDrive, starting with the storage of transcripts for meetings that only have transcription enabled. Previously, meetings with only transcription enabled saved the transcript file to the meeting organizer’s Exchange Online, while meetings with both recording and transcription enabled saved two transcript copies—one that is coupled with the recording saved to OneDrive and another transcript copy saved to the meeting organizer’s Exchange Online. Now with this feature, meetings that have only transcription enabled will also save two copies (one in OneDrive and one in Exchange Online), but all meeting transcript entry points in Teams app will point to the OneDrive copy only, no entry points for meeting transcripts will source from the Exchange Online copy.At the same time, meeting transcripts will stop saving in Exchange Online altogether and all transcript storage will be standardized on OneDrive only. The rollout of this feature also improves both the experience of meeting organizers to manually delete the transcript, as well as the ability for IT administrators to apply retention policies to the transcripts from meetings that only had transcription enabled. A summary of the deletion experience for meeting transcripts is captured in the following table: When this will happen: Targeted release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May). General Availability (Worldwide, GCC): We will begin rolling out mid-June 2024 (previously late May) and expect to complete by late August 2024 (previously mid-August). GCC High: We will begin rolling out late August 2024 and expect to complete by mid-September 2024. DoD: We will begin rolling out late September 2024 and expect to complete by late November 2024 (previously mid-October). How this will affect your organization: There is no change to the end user experience for viewing and downloading Teams meeting transcripts. The only change for meeting organizers and co-organizers is for any meetings that are held after this feature rolls out, they can delete all copies of the meeting transcript directly from the Teams app, instead of having to manually delete all copies of the transcript from two places (Teams app and Stream). For IT administrators, they can start applying retention policies for the copy of the transcript saved in OneDrive, including scenarios where a meeting only had transcription enabled. This retention policy won’t affect the copies saved in Exchange Online, to bulk delete transcript files saved in Exchange Online—please refer to thisdocumentation. We will also update the default transcript permissions. After the rollout, when the new policy is not applied, only meeting organizers and co-organizers will have permission to download or delete the transcript file, and meeting participants can only view the transcript in Teams or Microsoft Stream. Regardless of whether the new policy is applied, the meeting organizer will be able to select in Stream the participants who are restricted from downloading, viewing, and editing the transcript in Stream. What you need to do to prepare: There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate. MC717969 — (Updated) New Virtual Desktop Infrastructure solution for Microsoft Teams Microsoft 365 Roadmap ID375418 Updated October 10, 2024: We have updated the rollout timeline below. Thank you for your patience. The new Virtual Desktop Infrastructure (VDI) solution for Microsoft Teams is a redesigned version of the existing VDI optimization (WebRTC based) that provides enhanced performance, reliability, security, and streamlined support. By leveraging the same media engine used in the native Microsoft Teams desktop clients, it offers the following: Advanced meeting capabilities: o Gallery View 3x3 and 7x7 o Background images from My Organization o 1080p o Include Computer sound while screensharing o Hardware acceleration on the endpoint Telephony and voice capabilities o Location Based Routing and Media Bypass o QoS o Human Interface Device (HID) o Noise suppression Better supportability via Teams Admin Center / Call Quality Dashboard It also provides a simpler media engine update experience for users, without requiring frequent upgrades of the VDI infrastructure or VDI clients. This release applies to Microsoft Windows endpoints connecting to Microsoft Azure Virtual Desktops, Microsoft Windows 365, and Citrix VDI environments only. The Remote Desktop client for Windows (1.2.5112) or an upcoming version of the Windows App from the Microsoft Store bundle a new small component (known as Microsoft Teams Plugin) capable of establishing a dynamic virtual channel with Microsoft Teams running on the virtual desktop, subsequently silently downloading the new media engine on the user's device which keeps it up to date without user or admin intervention. For Citrix Workspace app for Windows (2203 Long Term Service Release [LTSR], or 2302 Current Release[CR] or higher), admins can get the Microsoft Teams plugin installed using tools like Microsoft System Center Configuration Manager (SCCM) or Microsoft Endpoint Configuration Manager (MECM) without requiring an upgrade. The future 2402 LTSR version of the Workspace app will also present a UI to users to install the plugin or a new command line argument for scripted rollouts. When this will happen: Targeted Release: We will begin rolling out late June 2024 (previously mid-June) and expect to complete by early August 2024 (previously late June). General Availability: We will begin rolling out in early August 2024 (previously late July) and expect to complete by early November 2024 (previously mid-September). How this will affect your organization: The new VDI solution for Microsoft Teams is enabled by default on the new Teams app and becomes the default optimization mode if the endpoint meets the minimum requirements. It can be disabled via TAC policy. What you need to do to prepare: The new VDI solution requires the new Microsoft Teams client to be deployed. It also requires the client-side plugin component, as described above. MC704955 — (Updated) Now get Real Time Calendar Notifications in Teams Microsoft 365 Roadmap ID314355 Updated October 9, 2024: We have updated the rollout timeline below. Thank you for your patience. You can now get the Calendar Notifications in Teams from the Activity Feed. You will get calendar notifications in the Activity Feed for the below scenarios:LISTBREAK o Meeting invite (including channel meetings you are explicitly invited to) o Meeting updates o Meeting cancellations o Meeting forwards (as an organizer) When you get a calendar notification, you will see an unread notification in the Activity Feed pane or at the bell icon. When you click on a notification, you will see the details of the meeting/event in the right pane. When this will happen: Targeted Release: We will begin rolling out mid-March 2024 and expect to complete by early April 2024 (previously late March). General Availability (Worldwide, GCC, GCC High & DoD): We will begin rolling out early April 2024 (previously late March) and expect to complete by late October 2024 (previously late September). How this will affect your organization: Users will get Calendar notifications in the Activity Feed within Teams. These notification settings for Calendar can be modified from "Notifications and activity" in the Settings menu in Teams. What you need to do to prepare: There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate. MC704035 — (Updated) Microsoft Teams: Integrate Chat notification with Meeting RSVP status Microsoft 365 Roadmap ID161739 Updated October 17, 2024: We have updated the rollout timelines below. Thank you for your patience. Microsoft Teams users will soon be able to control how they get notified in meeting chats through RSVP to their meetings. When they decline a meeting, they will not receive notifications or see the chats in chat list; when they accept a meeting, they will receive notification for all new messages. This release of Microsoft Teams Meeting ID will be rolling out across Microsoft Teams Desktop, Mobile and Web and will provide an additional way for users to control their chat list by selecting which meetings they want to receive message updates from. When this will happen: Targeted Release will begin rolling out early December 2024 (previously early November) and expect to complete by mid-December 2024 (previously mid-November). Worldwide will begin rolling out early January 2025 (previously early December) and expect to complete by mid-January 2025 (previously mid-December). GCC will begin rolling out January 2025 (previously early November) and expect to complete by mid-January 2025 (previously mid-November). GCC High will begin rolling out mid-January 2025 (previously mid-November) and expect to complete by late January 2025 (previously late November). DoD will begin rolling out late January 2025 (previously early October) and expect to complete by early February 2025 (previously mid-October). How this will affect your organization: You will not receive notifications or see chats from meetings you declined. You will be able to set how you want to be notified for meetings you RSVP with Accept or Tentative from Microsoft Teams settings. What you need to do to prepare: You might want to notify your users about this new capability to control meeting chat notifications by RSVP to meetings. MC697433 — (Updated) Affected Teams behavior in Chrome due to privacy sandboxing Updated September 30, 2024: Chrome will no longer be rolling out this change to general availability. Users will instead be able to choose whether they would like to enable privacy sandboxing. Read more about their update here:A new path for Privacy Sandbox on the web. Our recommendations below still apply if your users are using privacy sandboxing in Chrome. Thank you for your patience. Starting in January, Chrome will begin gradually rolling outprivacy sandboxing in the webto 1% of their users, with general rollout happening in late 2024. This will impact some Teams experiences in Chrome. The recommendation is to use the Teams desktop client if you are part of the rollout cohort. When this will happen: Starting in January 2024 and continuing through the remainder of 2024. How this will affect your organization: Teams users who are using Google Chrome with this recent change will start seeing the following experiences: The new Teams web app will display a banner and require users to click it every 24 hours to remain signed in. This will impact users in your organization who can't use the Teams desktop app. The new Teams web app may include embedded experiences, such as apps, that no longer work. When this happens, Teams will give users the option of opening the embedded experience in a separate browser tab, or using the Teams desktop app. Classic Teams will show options to switch to the new Teams web app, and/or to use the desktop app. Other affected experiences include Teams chat in Outlook web app and Dynamics 365. The ‘Share to Teams’ dialog found in Outlook and other web apps or sites is also affected. What you need to do to prepare: We are providing this information for your awareness. If your organization accesses Teams in the Chrome browser, some of your users may start being affected by this change. The recommendation is to use to the Teams desktop client. Enterprise administrators can also use theBlockThirdPartyCookiesandCookiesAllowedForUrlspolicies to ensure their users are not impacted, allowing them time to make necessary changes to not rely on this policy or third-party cookies. URLs should be allowed for Teams: [*.]microsoft.com [*.]microsoftonline.com [*.]teams.skype.com [*.]teams.microsoft.com [*.]sfbassets.com [*.]skypeforbusiness.com [*.]sharepoint.com [*.]onenote.com MC688109 — (Updated) Co-organizer experience updates in Teams Webinars and Townhalls Microsoft 365 Roadmap ID168524 Updated October 16, 2024: We have updated the rollout timeline below. Thank you for your patience. Scheduling, setting up, and managing an event is not a simple task. Which is why we allow co-organizer to be added to the event so they can work alongside or on behalf of the organizer. So far co-organizers were able to set up event theming, manage registration, meeting options, view reports and more but were not able to edit event details like title, date/time, description, event group; nor publish or cancel event. Now they can! Co-organizer can edit event details, publish, and cancel the event like the organizer can. So once the co-organizer is added they will have full parity of experience as organizer and control/manage/edit event. When this will happen: Targeted release: We will begin rolling out early January 2025 (previously early December) and expect to complete by mid-January 2024 (previously mid-December). General Availability (Worldwide, GCC): We will begin rolling out mid-January 2025 (previously mid-December) and expect to complete by mid-January 2025 (previously early January). How this will affect your organization: When co-organizer opens the event scheduling page, they should have the ability to edit the details page, publish, and cancel the event. What you need to do to prepare: Nothing required to prepare. MC686919 — (Updated) Simplified Compose Experience for Teams Microsoft 365 Roadmap ID123486 Updated October 9, 2024: We have updated the rollout timeline below. Thank you for your patience. Teams Compose is the heart of collaboration, where all Teams messages flow each month. It's also the gateway to a wealth of features, from Copilot to Files, Loops, Video, and Platform Apps. While Teams' capabilities have grown by leaps and bounds, the compose experience has remained largely unchanged. This update addresses usability, scalability, and information density challenges. We've simplified the compose experience, enhancing usability for various rich authoring scenarios, establishing scalable patterns for all compose actions, and optimizing it for your everyday needs. Get ready to enjoy a more seamless and efficient collaboration experience! This is for the new Teams experience only. When this will happen: Targeted Release: We will begin rolling out early-December 2023 and expect to complete by mid-December 2023. Worldwide: We will begin rolling out mid-April 2024 (previously early April) and expect to complete by mid-May 2024 (previously late April). GCC, GCC High and DoD: We will begin rolling out in late May 2024 (previously early May) and expect to complete rollout by late October 2024 (previously late September). How this will affect your organization: All Teams users will still be able to do everything they have previously done in Teams, but now, accessing these features will be easier and clearer. What you need to do to prepare: No changes are required to prepare for this change. MC683928 — (Updated) Microsoft Teams: In-meeting Error Messaging Microsoft 365 Roadmap ID167211 Updated October 9, 2024: We have updated the rollout timeline below for DoD organizations. Thank you for your patience. Microsoft Teams Meeting users will be notified directly through the error message on meeting right pane for why they cannot access meeting chats when their chat access is limited by policy or due to system limitations and unexpected errors. When this will happen: Targeted Release: We will begin rolling out mid-November and expect to complete by late November. Worldwide: We will begin rolling out early December and expect to complete by mid-December. GCC: We will begin rolling out early January and expect to complete by mid-January. GCC High: We will begin rolling out mid-January and expect to complete by late January. DoD: We will begin rolling out early February and expect to complete by late October 2024 (previously late September). How this will affect your organization: Once available, users will begin to understand why they cannot access certain chats during meetings. What you need to do to prepare: There is no action needed to prepare for this change. MC674737 — (Updated) Microsoft Teams: Emojis, GIFs and Stickers Unified in One Picker Microsoft 365 Roadmap ID84023 Updated October 9, 2024: We have updated the rollout timeline below. Thank you for your patience. Users can soon find all of their emojis, GIFs, and stickers in a combined picker in Microsoft Teams. When this will happen: Targeted Release: We will begin rolling out in early December 2023 (previously late November) and expect to complete rollout by late January 2024 (previously mid-December). Worldwide: We will begin rolling out in early April 2024 (previously mid-March) and expect to complete rollout by late July 2024. GCC, GCC High, DoD: We will begin rolling out in late July 2024 (previously early June) and expect to complete rollout by late October 2024 (previously late September). How this will affect your organization: Users can find emojis, GIFs, and stickers combined in one menu under the smiley face icon. All the fun content will remain as normal for users to add in their messages. What you need to do to prepare: There is nothing you need to do to prepare. MC673714 — (Updated) Microsoft 365 admin center: New Premium Teams Usage Report Microsoft 365 Roadmap ID163426 Updated October 11, 2024: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience. A new product usage report will be available within Microsoft 365 admin center usage reports to help Admins understand how Microsoft Teams Premium is being used within their organization by daily active users, features, and by paid and trial license types. Teams Premium usage reports will include daily active users of all up all Teams Premium features and active users per feature under meeting protection, meeting personalization, meeting intelligence, virtual events and advanced webinars pillars, and user level usage of each feature so that you know how people are utilizing Teams Premium licenses and how the adoption and engagement is in the organization. The report displays trends over the last 7/30/90/180 days. When this will happen: Preview: Will be available in late June 2024. General Availability: We will not be proceeding with this change at this time. How this will affect your organization: Admins with thecorrect permissionswill soon have access to new usage reports for Teams Premium. What you need to do to prepare: To access the new reports, go toReports -> Usage -> Teams Premium. For more information regarding these reports, please review the followingdocumentation. Purview MC920308 — Microsoft Purview | Information Protection: Auto-labeling policies will support "Fingerprint based SIT" Microsoft 365 Roadmap ID396173 Coming soon to Microsoft Purview | Information Protection: Admins will be able to use auto-labeling policies to automatically label files and emails withFingerprint based SIT(sensitive info type). When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late November 2024 and expect to complete by mid-December 2024. How this will affect your organization: Before this rollout, admins are not able to use auto-labeling policies to automatically label files and emails withFingerprint based SIT. After this rollout, you can configureFingerprint based SITusing the conditionContent contains sensitive information types. Files that matchFingerprint based SITwill show in simulation. Note: Contextual summary is not available forFingerprint based SITs. This change will be on by default and available for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Review use cases and set up for configuring document fingerprinting. Learn more About document fingerprinting | Microsoft Learn Automatically apply a sensitivity label in Microsoft 365 | Microsoft Learn MC920299 — Microsoft Purview | Audit: Enable audit log search for content searches that target Microsoft SharePoint Online By default, searches conducted from various Microsoft 365 entry points into Microsoft SharePoint Online are not collected in the Microsoft Purview audit log search. You may enable these searches to be collected by following these instructions:Step 4: Enable SearchQueryInitiated eventsinGet started with auditing solutions | Microsoft Learn. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): Available now. How this will affect your organization: To capture searches initiated by users against SharePoint online, you must enableSearchQueryInitiatedSharePointfor each user. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation. MC917744 — Microsoft Purview | Communication Compliance: Policy template to detect Microsoft 365 Copilot interactions Microsoft 365 Roadmap ID422328 Coming soon to Microsoft Purview | Communication Compliance: A new policy template to analyze all Microsoft 365 Copilot prompts and responses. When this will happen: General Availability (GCC): We will begin rolling out mid-November 2024 and expect to complete by early December 2024. How this will affect your organization: The new template will analyze Copilot prompts and responses to help ensure content prohibited by your organizational policies, such as harassing or threatening language, is not being used in Copilot interfaces. Also, administrators can choose to select Copilot chats as a checked location in the policy creation wizard for any new or existing policies. This empowers you to fine-tune your management strategy precisely for your organization’s needs, with a focus on user privacy protection. Whether you set specific conditions or deploy trainable classifiers, this feature provides flexibility and adaptability in compliance management, ensuring your organization's communications remain secure, compliant, and respectful of user privacy. The new Copilot for Microsoft 365 dedicated Communication Compliance policy: The new policy template will be available by default for admins to configure. Microsoft Purview Communication Compliance provides the tools to help organizations detect business conduct and regulatory compliance violations (e.g. SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to help ensure user-level privacy. Note:If a policy is configured to monitor Copilot and there's no Copilot messages being sent then no data will come in What you need to do to prepare: To create a policy to detect Copilot, select theDetect Microsoft Copilot for Microsoft 365 interactionspolicy template, fill in the required information, and submit the policy for creation. You can access the Communication Compliance solution in theMicrosoft Purview compliance portal. Learn more Learn about communication compliance | Microsoft Learn Detect channel signals with communication compliance | Microsoft Learn This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation. MC916867 — Microsoft Purview Audit: Audit Search Graph API Microsoft 365 Roadmap ID167531 Microsoft Graph offers a unified API endpoint for accessing data from multiple Microsoft cloud services in a single response. This feature provides a newAudit Log Query APIfor Microsoft Purview that enables you to create applications that programmatically query and retrieve your organization’s audit activity logs. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out early November 2024 and expect to complete by mid-November 2024. How this will affect your organization: Admins in your organization with access to search the audit log will be able to programmatically access the audit logs through the new Audit Log Query Graph API. You can now also manage access to audit logs in a more granular manner by assigning workload-specific permissions for six major workloads. What you need to do to prepare: To access the new Audit Log Query Graph API, register your application with Microsoft Graph and add the relevant Graph permissions. You may want to notify your users about this change and update any relevant documentation as appropriate. Microsoft Purview Audit enables customers to centrally visualize cloud log data generated across their enterprise, helping them effectively respond to security events, forensic investigations, internal investigations and compliance obligations. Thousands of user and admin operations performed in dozens of Microsoft 365 services and solutions are captured, recorded, and retained in customers' unified Microsoft Purview audit logs. Resources Learn about theAudit Search Graph API Learn aboutMicrosoft Purview Audit Access to search the Audit log in Get started with auditing solutions | Microsoft Learn Register your application with Microsoft Graph:Use the Microsoft Graph API - Microsoft Graph | Microsoft Learn Learn how toUse the Microsoft Graph API - Microsoft Graph | Microsoft Learn MC912712 — Microsoft Purview | Data Loss Prevention: Ability to fetch the original file resulting in policy match as evidence Microsoft 365 Roadmap ID165301 Data Loss Prevention (DLP) investigators have the option to keep, preview, and download as evidence the full file that resulted in a Microsoft Purview DLP policy match on Microsoft Windows devices. When this will happen: General Availability (GCC): We will begin rolling out late October 2024 and expect to complete by late November 2024. How this will affect your organization: If you choose to not use this feature, there is no impact on your organization. If your organization requires you to keep a copy of the original file that matches a DLP rule, then you will be able to preview and download the original file for further workflow from Activity explorer and DLP Alert tabs. What you need to do to prepare: Please set up an Azure blob storage to store these evidence files, and then create a policy and select the activities for which you wish to collect the original file as evidence. Lean more Learn about evidence collection for file activities on devices. Get started with collecting files that match data loss prevention policies from devices MC911618 — (Updated) Microsoft Purview | Insider Risk Management: Multi-policy settings in Adaptive Protection Microsoft 365 Roadmap ID171735 Updated October 23, 2024: We have updated the rollout timeline below. Thank you for your patience. Protection is a feature in Microsoft Purview | Insider Risk Management that allows organizations to identify risky users and create dynamic policies in Data Loss Prevention, Conditional Access, and Data Lifecycle Management. After this rollout, admins will be able to select multiple Insider Risk Management policies in theRisk levels for Adaptive Protectionsettings. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-November 2024 (previously mid-October) and expect to complete by mid-December 2024 (previously mid-November). How this will affect your organization: Before this rollout, admins can select single Insider Risk Managment policies in theRisk levels for Adaptive Protectionsettings. This new feature will be on by default and available for admins to configure. What you need to do to prepare: No action is required for this update. To configure user risk level for Adaptive Protection, admins can go to the Microsoft Purview compliance portal >Insider Risk Management > Adaptive Protection (preview) > Risk levels for Adaptive Protection Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. Learn more:Help dynamically mitigate risks with Adaptive Protection (preview) | Microsoft Learn MC889527 — (Updated) Microsoft Purview | Data Loss Prevention for endpoints: Enhanced DLP capabilities for macOS endpoints Microsoft 365 Roadmap ID389839 Updated October 15, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Purview | Endpoint Data Loss Prevention: We are adding two new features to the DLP capabilities for macOS endpoints: Context-based classification Matched condition and short evidence for advanced classification When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late November 2024 (previously late September) and expect to complete by early December 2024 (previously early October). How this will affect your organization: Before this rollout: Context-based classification and matched condition support was not available for Mac endpoints. After this rollout: Context-based classification: Admins will be able to use contextual parameters (FileType Is, FileExtension Is) as DLP policy conditions. Admin can define these parameters individually or in conjunction with content-based conditions. Matched conditions and short evidence for advanced classification: Matched conditions show the cause of flagged DLP policy matches, providing admins with a more comprehensive investigation experience. To view this feature, go to theAlertsdashboard in theMicrosoft Purview compliance portal, select theEventstab, and then select theDetailstab to review the condition and its corresponding matched value. You can also see this in the DLP Rule matched activity in the Activity Explorer. The matched conditions section in the Purview compliance portal This feature is on by default and available for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your security team about this change and update any relevant documentation as appropriate. Learn more Get started with endpoint data loss prevention | Microsoft Learn The Microsoft Purview compliance portal MC883194 — (Updated) Microsoft Purview | Information Protection: Default sensitivity labels and policies enhancements (GCC) Updated October 10, 2024: We have updated the rollout timeline below. Thank you for your patience. When admins activate default labels and policies for Microsoft Purview Information Protection, labels will now be scoped to files, email, and meetings. Microsoft 365 Roadmap ID408172. When this will happen: General Availability (GCC): We will begin rolling out late October (previously late September) 2024 and expect to complete by late November 2024 (previously late October). How this will affect your organization: There is no impact to the organization with the current sensitivity labels. This will only affect organizations that choose to activate default labels. This new feature is available by default. What you need to do to prepare: This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. MC882266 — (Updated) Microsoft Purview | Information Protection: Message Recall for encrypted emails in Microsoft Outlook Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Purview: Information Protection's Advanced Message Encryption will provide email encryption capability in Microsoft Exchange Online and will be integrated with Message Recall for email stored in a cloud mailbox and sent within an organization. Users with a license for Microsoft 365 E5 or Microsoft Office 365 E5 will be able touse the new Microsoft Outlook for Windows and Outlook on the web to recall encrypted email from their Sent folder. The same behaviors for unencrypted email apply to encrypted email, as described inExchange Online Message Recall Updates - Microsoft Community Hub. Microsoft 365 Roadmap ID413431. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early October 2024 and expect to complete by late November 2024 (previously mid-November). How this will affect your organization: Before this rollout: Users with one of the specified licenses are not able to recall encrypted email from their Sent folder. The Message recall control is greyed out. After this rollout: Users with one of the specified licenses will be able to select an encrypted email in the Sent folder to recall the message. This feature will be on by default for users with one of the specified licenses. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more Exchange Online Message Recall Updates - Microsoft Community Hub Work with Cloud-based Message Recall | Microsoft Learn(will be updated before rollout) MC867662 — (Updated) Microsoft Purview | Insider Risk Management: Microsoft Information Protection (MIP) trainable classifiers Microsoft 365 Roadmap ID167221 Updated November 5, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Microsoft Purview Insider Risk Management will be rolling out support for Microsoft Information Protection (MIP) trainable classifiers. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late November 2024 (previously late October) and expect to complete by late December 2024 (previously late November). How this will affect your organization: Before this rollout: Admins are not able to use trainable classifiers in MIP. After this rollout: Use trainable classifiers from MIP to recognize various content types specific to your organization. Any content matching the trainable classifiers will be automatically highlighted in the alerts. If you are not interested in specific classifiers, you can exclude them inIRM settings > Global exclusions > Trainable classifiers. This feature is on by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation. Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. Learn more Set up global exclusions for insider risk management policies | Microsoft Learn Fine-tune exclusions in insider risk management by creating detection groups and modifying built-in indicator variants (preview) | Microsoft Learn MC846386 — (Updated) Microsoft Purview | Insider Risk Management: Bulk upload for priority user groups Microsoft 365 Roadmap ID409540 Updated October 10, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Purview | Insider Risk Management: Priority user groups will support bulk upload. When this will happen: Public Preview: We will begin rolling out mid-August 2024 and expect to complete by late August 2024. General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out mid-October 2024 (previously late September) and expect to complete by mid-November 2024 (previously late October). How this will affect your organization: Before this rollout: Insider Risk Management admins enter UPNs one at a time when adding to a new or existing priority user group. After this rollout: Insider Risk Management admins will be able to upload a CSV of UPNs (User Principal Names) that they would like to add to a new or existing priority user group: This feature is on by default and accessible to all Insider Risk Management admins with appropriate permissions. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation. Learn more:Prioritize user groups for insider risk management policies | Microsoft Learn(This page will be updated soon). MC843111 — (Updated) Microsoft Purview | Insider Risk Management: General availability of granular exclusion (GCC, GCC High, DoD) Microsoft 365 Roadmap ID389842 Updated August 29, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Microsoft Purview Insider Risk Management will roll out granular exclusion for general availability. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-October 2024 (previously late August) and expect to complete by late October 2024 (previously early September). How this will affect your organization: Before this rollout: Granular exclusion was only available in Public Preview. Before Public Preview, admins were not able to fine-tune Insider risk settings according to organizational preferences. After this rollout: Granular exclusion allows admins with appropriate permissions to adjust and fine-tune indicators according to organizational preferences and to help tailor risk detection that may lead to a potential security incident. For example, admins can configure the indicator Sending email with attachments to recipients outside the organization to only detect emails sent to personal domains (such as outlook.com). In this way, admins can reduce the number of false positives. This feature is on by default and accessible to admins with appropriate permissions. What you need to do to prepare: No admin action is needed to prepare for this rollout. To use granular exclusions, admins can configure the exclusion conditions in the Purview compliance portal atInsider risk settings > Policy indicatorsand selectIndicatorsto create variants of detections. You may want to notify your users about this change and update any relevant documentation. Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. You can access the Insider Risk Management solution in theMicrosoft Purview compliance portal. Learn more in the Create a variant of a built-in indicator section ofConfigure policy indicators in insider risk management | Microsoft Learn. MC808165 — (Updated) Microsoft Purview eDiscovery | Modernized eDiscovery in new Microsoft Purview portal Microsoft 365 Roadmap ID383744 Updated October 22, 2024: We have updated the content. Thank you for your patience. A modernized new user experience (UX) for Microsoft Purview eDiscovery will be available in the Purview portal. In this new UX experience, Content Search, eDiscovery Standard, and eDiscovery Premium are unified so that users can now navigate a shared workflow that simplifies the transition between non-premium and premium features. This UX modernization also introduces features that enhance the eDiscovery process. Some of these new features include: This new experience enhances Content Search security by placing all searches in an eDiscovery case. eDiscovery administrators and managers will have default access, with the ability to manage membership and control access to content searches. Users who are not eDiscovery administrators or managers will need to request to be added as case member in order to access content search. Enhanced search efficiency withmessage IDandsensitivity labelsfor faster access to information. Use of the improved search by Sensitive Information Type (SIT) interface for user-friendly selection without manual input. Advanced Data Source Mappingallows linking a user's OneDrive using input such as the user's mailbox Simple Mail Transfer Protocol (SMTP) address or user’s name, streamlining data retrieval and management. Acceleration through powerful investigation capabilities, such as user'sfrequent collaborators, providing a comprehensive view of the user's networks. Data Source Sync:Stay updated with the new Data Source synchronization feature, which allows users to easily track any new or removed data locations, ensuring that eDiscovery investigations remain aligned with the latest data source landscape. Introduction of the new visualStatisticsallows users to gain insights at a glance (such as Results containing Sensitive Information Types, top communication participants, etc.) Monitor long-running processes with an informed and transparent progress bar with the option to cancel (for certain process types) if needed. Obtain a full process report for all actions taken, such as statistics for holds and exports, bolstering the defensibility of your eDiscovery efforts. Customize your exports with new settings, including the option to export as a single PST file path truncation and the use of friendly names to make exported data more accessible. When this will happen: Public Preview: We will begin rolling out late July 2024 and expect to complete by late September 2024. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-November 2024 (previously early October) and expect to complete by late December 2024 (previously late November) How this will affect your organization: The unification of Content Search, eDiscovery Standard, and eDiscovery Premium into a single eDiscovery solution in the new Microsoft Purview portal will necessitate updates to your organization's training materials and documentation. The deprecation timeline for the classic eDiscovery experience will be announced when the new modernized experience becomes generally available (GA). We will ensure that customers have ample time to transition to the new modernized experience before retiring the classic version. What you need to do to prepare: Update internal documentation and provide training to all eDiscovery users in your organization. Learn more about thenew Purview Portal. Learn more about the modernized eDiscovery (preview) experience:Learn about eDiscovery (preview) solutions | Microsoft Learn MC805721 — (Updated) Purview | Insider Risk Management: Adaptive Protection is generally available in GCC, GCCH, and DoD Microsoft 365 Roadmap ID335856 Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Adaptive Protection integrates the breadth of intelligence in Microsoft Purview Insider Risk Management with the depth of protection in Microsoft Purview Data Loss Prevention, to continuously and automatically fine-tune policies and protect data where and when it matters the most. The capability is built into the Microsoft platform with no endpoint agents required so organizations can get started using this as soon as it rolls out. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-November (previously mid-October) 2024 and expect to complete by mid-December 2024 (previously mid-November). How this will affect your organization: Before the rollout: Admin are not able to configure custom definitions for insider risk levels in Insider risk managements or use insider risk levels as conditions in Data Loss Prevention (DLP) policies to apply dynamic controls to risky users. After the rollout: Adaptive Protection is a capability of Microsoft Purview that enables organizations to dynamically optimize the balance between data protection and productivity. By leveraging the machine learning-driven analysis in Insider Risk Management, Adaptive Protection detects potentially risky user actions that may result in a data security incident and automatically adds the user to a stricter Data Loss Prevention (DLP) policy. The protection policies are adaptive based on user context, ensuring low-risk users can maintain productivity and high-risk users have appropriate protection in place. What you need to do to prepare: To begin using this capability, configure risk levels for Adaptive Protection in Insider Risk Management and add a new condition for risk levels for Adaptive Protection in new or existing DLP policies for Exchange, Teams, or Devices. You can also set up Adaptive Protection using the one-click activation option from the home page of Microsoft Purview compliance portal. With one click, Adaptive Protection will create an Insider Risk Management policy based on aggregated risk insights of anonymized user activities in your organization, set your risk levels for Adaptive Protection, and create a DLP policy in test mode. The default state of this feature is off. Get started with Adaptive Protection in theMicrosoft Purview compliance portal>Insider risk management > Adaptive Protection References Learn aboutadaptive protection Learn aboutinsider risk management Learn aboutdata loss prevention Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies to manage security and compliance. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation as appropriate. MC795079 — Microsoft Purview | Insider Risk Management - Adaptive Protection - HR resignation date as a condition for risk level Microsoft 365 Roadmap ID124972and171748 Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. Microsoft Purview: The feature to configure HR resignation date as a condition for risk level in Adaptive Protection will be rolling out to General Availability. We communicated the preview for this feature in MC681240Adaptive Protection in Microsoft Purview: Public preview of HR resignation date as a condition for risk level (November 2023). When this will happen: General Availability: We will begin rolling out late June 2024 and expect to complete by mid-November 2024 (previously late mid-October). How this will affect your organization: When the HR connector has been configured, admins with appropriate permissions can now select the HR resignation date as a condition to assign a minor, moderate, or elevated risk level. For example, an admin can configure the elevated risk level to be assigned when an HR resignation date is sent via the HR connector. What you need to do to prepare: No action is required for this update. To configure user’s risk level for Adaptive Protection, admins can visit Insider Risk Management > Adaptive Protection (preview) > risk levels for Adaptive Protection. Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy. Additional Resources: You can access the Insider Risk Management solution in the Microsoft Purview compliance portal. Home - Microsoft Purview Learn more about adaptive risk mitigation: Help dynamically mitigate risks with Adaptive Protection (preview) | Microsoft Learn MC750666 — (Updated) Purview | Data Loss Prevention: Attachment details in Activity Explorer and Alerts for DLP rules in Exchange Microsoft 365 Roadmap ID379673 Updated October 24, 2024: To ensure the optimal experience for our customers, we have decided not to proceed with the rollout at this time. We will communicate via Message center when we are ready to proceed. Thank you for your patience. Thank you for your patience. We are rolling out new fields in Microsoft Exchange to help prevent data loss. With these updates, admins can see more details about attachments in emails that violate Data Loss Prevention (DLP) rules in Exchange, including name, size, and labels. When this will happen: We will begin rolling out late February 2025 and expect to complete by late April 2025. How this will affect your organization: These new details will be displayed in Activity Explorer, DLP Alerts, and Microsoft Theft Protection (MTP) Alerts. With these updates, you can get better insights into the violation before you start investigating the finer details of the issue. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. MC678065 — (Updated) Microsoft Purview compliance portal: Information Protection - New cmdlet for Content Explorer Microsoft 365 Roadmap ID117531 Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. The Content explorer Export feature has a limitation of exporting data only after drill down to specific location. This feature is now available in Public Preview and allows admins to use a new cmdlet within the Security & Compliance PowerShell, Export-ContentExplorerData, to export all rows of data for the content that are scanned and shown on the Content Explorer. When this will happen: This feature will begin rolling out mid-April 2025 (previously early March) and expect to complete by mid-May 2025 (previously early April). How this will affect your organization: This feature can be accessed through the Security & Compliance PowerShell, Export-ContentExplorerData. What you need to do to prepare: There are no additional settings needed for this feature. Get started with content explorer |Microsoft Learn Defender for Office 365 MC889519 — (Updated) Microsoft Defender for Office 365: Tenant Allow/Block List will support IPv6 allow and block entries Microsoft 365 Roadmap ID406166 Updated October 11, 2024: We have updated the timeline below. Thank you for your patience. NOTE:This applies to customers with Microsoft Exchange Online Protection or Microsoft Defender for Office 365 Plan 1 or Plan 2 service plans.https://learn.microsoft.com/defender-office-365/tenant-allow-block-list-ip-addresses-configure Soon, it will be possible to create IPv6 allow and block entries in theTenant Allow/Block Lists. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early October 2024 (previously late September) and expect to complete by mid-October 2024 (previously early November). How this will affect your organization: Before this rollout: Admins cannot block or allow IPv6 addresses. After this rollout, you can make IPv6 allow and block entries in these formats: Colon-hexadecimal notation single IPv6 address (for example, 2001:0db8:85a3:0000:0000:8a2e:0370:7334) Zero compression single IPv6 address (for example, 2001:db8::1) Classless inter-domain routing (CIDR) IPv6 (for example, 2001:0db8::/32). The range supported is 1-128. The IP block entry will drop any email sent from that IP at the edge, whereas the IP allow will just override the IP filtering, allowing the rest of the Defender for Office 365 stack to evaluate threats. IP block has a higher priority over IP allow entries. Admins can create entries in the Defender portal or with the Microsoft PowerShellNew-TenantAllowBlockListItemscmdlet (ListType parameter with value IP) without need for submissions. This change will not impact any of your currentTenant Allow/Block Listentries or your IPv4 entries in thehosted connection filter policyorenhanced filtering connection policy Last used date support for IPv6 allow and block will be added soon. Entry limits for IPv6: Exchange Online Protection: The maximum number of allow entries is 500, and the maximum number of block entries is 500 (1000 entries in total). Defender for Office 365 Plan 1: The maximum number of allow entries is 1000, and the maximum number of block entries is 1000 (2000 entries in total). Defender for Office 365 Plan 2: The maximum number of allow entries is 5000, and the maximum number of block entries is 10000 (15000 entries in total). Permissions: The sameexisting set of permissions we have for Tenant Allow/Block Listwill also apply to this rollout. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. If one wants to block emails from IPv6 addresses or allow email from IPv6 addresses, the admin need to create entries to do so. Additional references: Allow or block IP addresses using the Tenant Allow/Block List - Microsoft Defender for Office 365 | Microsoft Learn MC841229 — (Updated) Classic Microsoft Outlook for Windows: New reporting buttons integrated with Microsoft Defender for Office 365 Microsoft 365 Roadmap ID371388 Updated October 10, 2024: We have updated the content and timeline below with additional information Starting August 2024 for classic Outlook for Windows, we will add new built-in reporting buttons that allow users to report emails as phishing / junk / not junk. Admins can control the appearance and behavior of these buttons from theUser reportedsettingspage in the Microsoft 365 Defender portal (security.microsoft.com). Admins can also customize where messages get reported to (reporting mailbox, Microsoft, or both) and what the user sees both before and after reporting messages from these buttons. Your currentUser reportedsettings page will not be changed by this rollout. When this will happen: General Availability: If you are on the monthly enterprise/current channel build of Outlook, we will begin rolling out early August 2024 and expect to complete by mid-November 2024 (previously late September). Rollout to additional channels will follow the standard timing. How this will affect your organization: Before this rollout: Classic Microsoft Outlook for Windows users do not see reporting buttons. After the rollout: OWA (Outlook on the web) and new Outlook for Windows have had this functionality since November 2022 and there is no change to it. The new built-in buttons on Outlook for Windows will inherit your existing User reported settings from OWA. Other versions of Outlook such as Mac, Mobile (iPhone and Android) will not be affected by this change. We are working on the adding the reporting buttons to other versions of Outlook. If you have the reporting feature turned off in the Microsoft 365 DefenderUser reportedsettings page or are using a third-party add-in, the reporting buttons in classic Outlook for Windows won't be visible. The Microsoft reporting add-in (the Microsoft report message add-in and the Microsoft phishing add-in) will be supported until further notice. Customers who currently use the add-in and the new reporting buttons will see two sets of reporting buttons in the ribbon. However, when Outlook Mac and Mobile add the new reporting buttons in the near future, the reporting add-in will no longer be needed and can be removed. The selections you make on the user reported settings page will determine the reporting experience for your users whether they choose the add-in or built-in reporting option in Outlook. Either option will report to the same place (Microsoft, custom mailbox, or both) based on theUser reportedsettings selected. Unlike OWA and new Outlook for windows, the built-in reporting buttons in classic Outlook for windows do not support reporting from shared and delegate mailboxes. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more Report phishing and suspicious emails in Outlook for admins - Microsoft Defender for Office 365 | Microsoft Learn User reported settings - Microsoft Defender for Office 365 | Microsoft Learn Outlook MC923410 — New Microsoft Outlook for Windows is GA on November 4, 2024 (GCC) On November 4, 2024, the new Microsoft Outlook for Windows will transition from the Preview phase to General Availability for GCC moderate accounts. This milestone will not affect existing users who continue to use classic Outlook for Windows; however, GA status helps organizations move forward with their migration plans. A future announcement will cover General Availability for other US Government clouds (GCC High and DoD) and availability in other sovereign clouds. The new Outlook continues to be an opt-in experience. Please note that this update does not change any settings for your organization, will not automatically switch users from the classic version of Outlook for Windows, and will not introduce any disruptive changes. We will provide a minimum 12-month advance noticeprior to initiating any Microsoft-driven migration steps in managed enterprise environments. Learn more about how we are approaching our migration timeline:New Outlook for Windows: A Guide to Product Availability Key updates The new Outlook for Windows will receive full support from Microsoft’s support channels, including Assisted Support. In July 2024, we removed the “New” badge from the new Outlook app. The app name for the classic Outlook for Windows will include “(classic)” starting from version 2407. (Note: Existing shortcuts will not change.) We understand some organizations may have specific requirements that prevent them from transitioning from the classic Outlook app at this time. The new Outlook team is eager to gather your feedback and to understand your requirements. You can submit feedback through the Feedback Portal and your account team. Learn more about the future features of Outlook on the Microsoft 365 Roadmap:Microsoft 365 roadmap Side-by-side feature comparison of the classic and new Outlook:New and classic Outlook for Windows feature comparison Resources to help with change management and enterprise adoption:New Microsoft Outlook for Windows Recommended actions Control availability:Organizations retain control over the new Outlook’s availability. Policies can be set to hide the toggle in classic Outlook for Windows, block new mailboxes from being added, or remove new Outlook from certain Windows builds. For detailed instructions, refer toControl the installation and use of new Outlook Learn about policy management:New Outlook’s policies are managed through mailbox policies on the primary account, as they are for Outlook on the web. IT admins may choose to preconfigure an organization account as the primary account. Learn more:Policy Management - Deploy Office Prepare to manage updates:The new Outlook introduces features through service-based flighting, not through build updates. Features will be listed on theMicrosoft 365 Roadmapwith advance notice before releasing. Transition from COM to web add-ins:COM add-inswill not be supported in the new Outlook, and organizations need to transition to web add-ins instead. A variety of equivalent web add-ins are already available, and we offer assistance for organizations who rely on COM-only add-ins. Learn more about how toMigrate from COM to web add-insand review alist of available web add-ins. Plan for user migration:We will provide a 12-month advance notice before initiating Microsoft-driven migrations to the new experience in managed environments. We know organizations prefer to time and drive their own upgrades. Organizations are encouraged to review these resources to help get started. IT administrators can now review and share within their organizations: o Adoption and migration resources:New Microsoft Outlook for Windows o Support content and user training for the new Outlook:Getting started with the new Outlook for Windows o Admin documentation:Overview of the new Outlook for Windows MC917748 — Microsoft Teams and Microsoft Outlook: Name pronunciation on the profile card Microsoft 365 Roadmap ID420329 Coming soon to Microsoft Outlook and Microsoft Teams: A name pronunciation feature on the profile card in Microsoft Teams and Microsoft Outlook. This new feature helps promote diversity by giving working colleagues relevant information about each other. Names are a crucial part of a person’s identity. The incorrect pronunciation of a person’s name can lead to anxiety and offense in some cases. Correctly pronouncing a person’s name helps to create an inclusive environment. Pronunciation data is stored in each user's mailbox until the user deletes the recording. Learn more:Data Residency for Exchange Online - Microsoft 365 Enterprise | Microsoft Learn This message applies to Teams for Windows desktop, Teams for Mac desktop, new Outlook for Windows desktop, and new Outlook for web. When this will happen: Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by late November 2024. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-January 2025 and expect to complete by mid-February 2025. How this will affect your organization: After this rollout, users can record and share the correct pronunciation of their name on their profile card. With a click, users can play and listen to name pronunciations recorded by their colleagues. To open a profile card in Outlook, double-click a name in theToorFromfield in any sent or received email. To open your profile card in Teams, select your profile photo in the upper right corner of the screen, and then select your name. To listen to a colleague's recorded pronunciation, select the speaker icon on their profile card: To record the pronunciation of a name, open your profile card in Outlook or Teams, and select the microphone icon: What you need to do to prepare: This feature is off by default. As an admin, you can enable the feature in Microsoft Graph using these instructions:namePronunciationSettings resource type - Microsoft Graph beta | Microsoft Learn Before rollout, we will update this post with revised documentation. You may want to notify your users about this change and update any relevant documentation. #newoutlookforwindows MC909163 — Microsoft Outlook for Mac: New reporting buttons integrated with Microsoft Defender for Office 365 Microsoft 365 Roadmap ID371393 In September 2024, we added new built-in reporting buttons in new Microsoft Outlook for Mac desktops that allow users to report emails as phishing / junk / not junk. Admins can control the appearance and behavior of these buttons from theUser reported settings pagein the Microsoft 365 Defender portal (security.microsoft.com). Admins can also customize where messages get reported to (reporting mailbox, Microsoft, or both) and what the user sees both before and after reporting messages from these buttons. Your currentUser reported settingspage has not been changed by this rollout. This message applies to new Outlook for the Mac using version 16.89.24090815(16.89.908.0). When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): Available now. How this will affect your organization: Before this rollout: Outlook for Mac users did not see reporting buttons. After the rollout OWA (Outlook on the web), new Outlook for Windows, and classic Outlook for Windows have had this functionality since August 2024 and there is no change to it Other versions of Outlook such as Mobile (iPhone and android) will remain unaffected by this change. We are working on the adding the reporting buttons to other versions of Outlook. If you have the reporting feature turned off in the Microsoft 365 DefenderUser reported settingspage or are using a third-party add-in, the reporting buttons in Outlook for Mac will not be visible to users. The Microsoft reporting add-in (the Microsoft report message add-in and the Microsoft phishing add-in) will be supported until further notice. Customers who currently use the add-in and the new reporting buttons will see two sets of reporting buttons in the ribbon. However, when we add the new reporting buttons to Outlook Mobile clients in the near future, the reporting add-in will no longer be needed and can be removed. The selections you make on theUser reported settingspage will determine whether your users choose the add-in or built-in reporting option in Outlook. Either option will report to the same place (Microsoft, custom mailbox, or both) based on theUser reported settingsselected. Unlike OWA and new Outlook for windows, the built-in reporting buttons in Outlook for Mac do not support reporting from shared and delegate mailboxes. New reporting buttons in Outlook for Mac From all folders except junk folder: From the junk folder: What you need to do to prepare: Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation. Learn more Report phishing and suspicious emails in Outlook for admins - Microsoft Defender for Office 365 | Microsoft Learn User reported settings - Microsoft Defender for Office 365 | Microsoft Learn MC901831 — (Updated) New Microsoft Outlook for web and Windows: Organize and reorder folders Microsoft 365 Roadmap ID378775 Updated October 17, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: We will automatically import the folder order from classic Microsoft Outlook for Windows to new Microsoft Outlook for Windows and Outlook for the web. If users have not customized their folder order, the default view will continue to display folders alphabetically in the new Outlook. When this will happen: Targeted Release: We will begin rolling out late November 2024 (previously early October) and expect to complete by late December 2024 (previously early November). General Availability (Worldwide): We will begin rolling out January 2025 (previously early November) and expect to complete by early February 2025 (previously early December). General Availability (GCC, GCC High, DoD): We will begin rolling out early February 2025 (previously early December) and expect to complete by early March 2025 (previously early January). How this will affect your organization: Before this rollout: If a user enabled custom folder order in classic Outlook, the custom order is preserved in the new Outlook for Windows and Outlook on the web. This may result in changes to the folder structure for affected users, as the new Outlook supports only alphabetical ordering. After this rollout: users will see the custom folder order they previously enabled in classic Outlook. Special folders such asInbox, Drafts, Sent Items,and others will still remain at the top of the folder list, even when the rest of the folders are arranged alphabetically. This change is on by default. To change folder order, go to the new Outlook ribbon, and selectView > Layout > Folder pane. Choose one of these options: Order folders A to Z order: This will organize folders alphabetically Custom order Users can hover next to each folder name to see the three-dot menu where they can move folders with drag-and-drop or the move up/move down options What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more:Change the order of folders in the Folder Pane - Microsoft Support(will be updated before rollout) MC847877 — (Updated) Microsoft Outlook for iOS and Android: Choose fonts while composing Microsoft 365 Roadmap ID409969 Updated October 22, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Outlook for iOS and Android: We will add support for choosing fonts while composing emails. We will also improve support for fonts while reading emails. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-November 2024 (previously mid-October) and expect to complete by early December 2024. (previously early November). How this will affect your organization: When this update rolls out, users will be able to select fonts to use in emails, signatures, automatic replies, and calendar invitations: What you need to do to prepare: You might want to notify your users about this new capability and update your training and documentation as appropriate. MC799635 — (Updated) Microsoft Outlook: Add shared folders to Favorites Microsoft 365 Roadmap ID388913 Updated October 15, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon for new Microsoft Outlook for Windows and Outlook for web: Users will be able to add shared folders to theirFavoriteslist in the top left corner of the screen. This message does not apply to Outlook for Mac or Outlook for mobile devices. When this will happen: Targeted Release: We will begin rolling out early November 2024 (previously early October) and expect to complete by early December 2024 (previously early November). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-December 2024 (previously mid-November) and expect to complete by early January 2025 (previously early December) How this will affect your organization: This new functionality will enable users to add shared folders and individual folders from shared mailboxes to their Favorites. This means that users can easily access important folders from shared resources or individual colleagues, directly from their Favorites. Users can share calendars, or folders that contain mail, contacts, tasks, or notes. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate. Learn more:Open and use a shared mailbox in Outlook - Microsoft Support Exchange Online MC910986 — (Updated) Microsoft Exchange Online: Optional Help file parameter in Microsoft PowerShell will change Updated October 16, 2024: We have updated the content. Thank you for your patience. In Exchange Online PowerShell (EXO) V3.0, we introduced theConnect-ExchangeOnlinecmdlet to connect to the Microsoft Exchange Online environment through Microsoft PowerShell, which loads the help file by default. This help file is required for running theGet-Helpcmdlet. However, not many customers used theGet-Helpcmdlet. In EXO V3.3, we added the-SkipLoadingCmdletHelpparameter. When-SkipLoadingCmdletHelpis used withConnect-ExchangeOnline, help files do not load the on the customer system, which saves resources. However, starting with EXO V3.7, we are changing this default behavior. The Help file will not be loaded by default, and a new parameter-LoadCmdletHelpwill be required to load the cmdlet help and use theGet-Helpcmdlet. To avoid breaking existing scripts, the-SkipLoadingCmdletHelpparameter will continue exist, but will not function. When this will happen: General Availability (Worldwide): The changes will be available in EXO V3.7 (the next release of our EXO V3 module) in early November 2024. How this will affect your organization: Starting with EXO V3.7, if you want to use theGet-Helpcmdlet, you will have to use the parameter-LoadCmdletHelpalong withConnect-ExchangeOnline. What you need to do to prepare: This message only applies to customers who upgrade their EXO module version to 3.7.0. Earlier versions will not be affected by these changes. This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation. Learn more Connect-ExchangeOnline (ExchangePowerShell) | Microsoft Learn(will be updated before rollout) Get-Help (Microsoft.PowerShell.Core) - PowerShell | Microsoft Learn Download an EXO module fromPowerShell Gallery | ExchangeOnlineManagement 3.6.0. MC902782 — (Updated) Exchange Online token deprecation plan Updated Oct 30, 2024: We have updated the content. We’re contacting you because your tenant uses legacy Exchange Online tokens that are deprecated and Outlook add-ins that still use them will break when tokens are turned off. Legacy Exchange Onlineuser identity tokensandcallback tokensare deprecated and will soon be turned off for all Exchange Online tenants. This is part ofMicrosoft’s Secure Future Initiativeto protect orgs in the current threat landscape. If add-ins use legacy tokens to make calls to Exchange, developers need to migrate from Exchange tokens to using Nested App Authentication (NAA) and Entra ID tokens ASAP. Code changes to add-ins using legacy Exchange Online tokens are required to ensure they continue to work. We recommend you update affected add-ins to use NAA, which provides simple authentication and top tier identity protection through APIs designed specifically for add-ins in Office hosts. NOTE: This change only applies to Exchange Online; add-ins used in on-premises environments are not impacted by this change. Recommended actions: Administrators:Identify which add-ins need to be updated and contact the ISVs or developers of those applications to get updates. Developers:Check the add-in code to see if the related API calls are used and then make appropriate updates. Register:The updated add-ins require an application registration in Microsoft Azure. Developers need to create an application registration for each add-in. Admins need to consent to the application registration for each add-in's required permissions. Don’t wait:Add-ins are often part of mission critical functions, and the updates will take time to implement. It’s best to implement updates well before legacy Exchange Online tokens are turned off. When will Microsoft turn off legacy Exchange Online tokens? ***** Microsoft begins turning off legacy Exchange online tokens in February 2025. From now until February 2025, existing and new tenants will not be affected. We'll provide tooling for administrators to reenable Exchange tokens for tenants and add-ins if those add-ins aren't yet migrated to NAA. When is NAA generally available for my channel? The general availability (GA) date for NAA depends on which channel you are using. How do I check which Outlook add-ins are impacted? From October 30th through mid-November 2024, we'll roll out new tooling via PowerShell for Microsoft 365 administrators to turn legacy Exchange tokens on or off in your tenant. If you find you need to reenable legacy Exchange tokens, you can use the PowerShell cmdlets to do so. The tooling will also report if any add-ins are using legacy tokens over the last 28 days. Once the tooling is available will update theOutlook legacy token deprecation FAQwith additional documentation details. Add-ins may use the legacy Exchange tokens to get resources from Exchange through the EWS or Outlook REST APIs. Sometimes an add-in requires Exchange resources for some use cases and not others, making it difficult to figure out whether the add-in requires an update. We recommend reaching out to add-in developers and owners to ask them if their add-in code references the following APIs: makeEwsRequestAsync getUserIdentityTokenAsync getCallbackTokenAsync We’ll provide tooling via PowerShell for Microsoft 365 admins in October 2024 to turn legacy Exchange tokens on or off in your tenant. This will allow you to test if any add-ins are using Exchange tokens. We’ll provide more info when the tooling is ready in theOutlook legacy token deprecation FAQ. If you rely on an independent software vendor (ISV) for your add-in, we recommend you contact them as soon as possible to confirm they have a plan and a timeline for moving off legacy Exchange tokens. ISV developers should reach out directly to their Microsoft contacts with questions to ensure they're ready for the end of Exchange legacy tokens. If you rely on a developer within your organization, we recommend you ask them to review theUpdates on deprecating legacy Exchange Online tokens for Outlook add-insblog and ask any questions to the Outlook extensibility PM team on theOfficeDev/office-js GitHub issues site. How do I keep up with the latest guidance? We'll share additional guidance on the Office Add-ins community call, the M365 developer blog, and the Outlook legacy token deprecation FAQ. Ask questions about NAA and legacy Exchange Online token deprecation on theOfficeDev/office-js GitHub issues site. Please put "NAA" in the title. Additional resources: NAA public preview blog Microsoft 365 developer blog:Updates on deprecating legacy Exchange Online tokens for Outlook add-ins NAA docs to get started NAA FAQ NAA Outlook sample NAA WXP sample MC835648 — (Updated) Announcing IPv6 Enablement for Accepted Domains Updated October 8, 2024: We have updated the content. Thank you for your patience. Starting October 16, 2024, we're gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6. More information on IPv6 support for Microsoft 365 services can be found at:IPv6 support in Microsoft 365 services When this will happen: October 16, 2024 (previously October 1, 2024) How this will affect your organization: After we enable IPv6 for your Accepted Domains, when someone tries to send an email to one of your users and queries the MX record for the domain, they will receive both IPv4 and IPv6 addresses (AAAA records) in response to their MX record query. What you need to do to prepare: To take advantage of IPv6 connectivity, please make sure that you and your partner's update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4. The Exchange Online IPv6 endpoints can be found here:Microsoft 365 URLs and IP address ranges. To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please useDisable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn). IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either: Keep the sending server as IPv4. o Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6 Change the IP based connector to certificate domain based connector. o This applies to both OnPremises type (From:Your organization's email server, To:Office 365) and Partner Type connectors (From:Partner organization, To:Office 365). Update: If you are using any Exchange Transport Rules or Data Loss Prevention policies which rely on the SenderIPRanges predicate, you need to opt out all your domains from IPv6. You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain. Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th. After October 16, once IPv6 is enabled for your tenant, if you haven't explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled). IMPORTANT:To ensure your preferred settings are applied, please use the Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven't explicitly set it. If you have enabled DNSSEC for mail flow, you may have issues executing the Get-IPv6StatusForAcceptedDomain cmdlet for the DNSSEC-enabled domain. We are rolling out the fix now. Please ensure to run Disable-IPv6ForAcceptedDomain to opt out of the IPv6 enablement if you need to opt a DNSSEC-enabled domain out of the IPv6 by default rollout. The IPv6 rollout will not affect DNSSEC-enabled domains until after Nov 18th. MC711018 — (Updated) Microsoft Exchange Online: Support for inbound SMTP DANE with DNSSEC Microsoft 365 Roadmap ID63213 Updated October 22, 2024: Inbound SMTP DANE with DNSSEC is now in General Availability. Thank you for your patience. We are adding support for DNS-based Authentication of Named Entities (or DANE) for SMTP and Domain Name System Security Extensions (DNSSEC) for inbound mail to Exchange Online. DANE for SMTP is a security protocol that uses DNS to verify the authenticity of the certificates used for securing email communication with TLS and protecting against TLS downgrade attacks. DNSSEC is a set of extensions to DNS that provides cryptographic verification of DNS records, preventing DNS-spoofing and adversary-in-the-middle attacks to DNS. When this will happen: Public Preview: We will begin rolling out in July 2024. General Availability: We begin rolling out early September 2024 (previously late August) and expect to complete by late October 2024 (previously late September). How this will affect your organization: Inbound SMTP DANE with DNSSEC will be off by default. If you do not want to enable the feature, you do not need to do anything. If you want to enable the feature, please follow the documentation using Exchange PowerShell. When the feature is released, the documentation will be in theHow can Exchange Online customers use SMTP DANE inboundsection ofHow SMTP DNS-based Authentication of Named Entities (DANE) secures email communications | Microsoft Learn. By the end of 2024, we will release a new experience for enabling DNSSEC and SMTP DANE without using PowerShell. What you need to do to prepare: Review your domain configuration internally to ensure you won’t be impacted by any of the limitations below, and visitImplementing Inbound SMTP DANE with DNSSEC for Exchange Online Mail Flow - Microsoft Community Hubfor more detailed information on limitations: Not supported: Fully delegated domain, onmicrosoft.com domains, and domains purchased from Microsoft known as “viral” or self-service sign-up domains Supported with risk: 3rd-party gateways, connectors, and integration with hybrid mail flow (ex. if you are using a connector to smarthost to a domain that you want to enable with DNSSEC, you need to update the smarthost name for that connector [ex. contoso-com.mail.protection.outlook.com] to match the new MX record that will be provided during DNSSEC enablement or, preferably, to match the tenant's onmicrosoft.com domain [ex. tenant-name.onmicrosoft.com] before enabling the feature.) Microsoft 365 MC923419 — Microsoft Loop: Configure guest sharing for tenants with sensitivity labels Before this rollout, guest sharing for Microsoft Loop components, pages, and workspaces is available for tenants that have not configured sensitivity labels, as communicated in MC736437Microsoft Loop: Guest Sharing(March 2024). After this rollout and the rollout of Microsoft Information Protection for Loop workspaces, B2B (business to business) guest sharing for Loop workspaces, pages, and components will be available for all tenants, including those who have configured sensitivity labels, subject to admin policy. If admins configure the policy, users will be able to share Loop workspaces, pages, and components with people outside of your tenant. This message applies to Loop on the web and on iOS/Android devices. This message is related to MC923176Microsoft Loop: Sensitivity labels at the container level(November 2024). Note:Loop will respect your Microsoft OneDrive and Microsoft SharePoint sharing settings. If your tenant does not allow sharing with guests, then it will prevent guest sharing of Loop workspaces, pages, and components as well. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out in early November 2024 and expect to complete by early December 2024. How this will affect your organization: After this rollout, if admins have configured Microsoft SharePoint for B2B guest sharing, users in your organization will be able to share Loop workspaces, pages, and components with people outside of your tenant. Users can share pages and components with thePeople you chooseoption. Guest users cannot create workspaces. The user experience: TheSharebutton in the top left of the Loop app: Sharing menu with option to share workspace, page, or component: Copy link dialog box with theSettingsicon: Sharing dialog box withPeople you chooseselected: Admins: You can configure sharing of Loop workspaces, pages, and components with guests by enabling these policies in Microsoft SharePoint admin center >Policies > Sharing: Set the organization-level external sharing settings for to allow content to be shared withNew and existing guestsorExisting guests. Enable the B2B collaboration with external guests. Learn more:Overview: B2B collaboration with external guests for your workforce - Microsoft Entra External ID | Microsoft Learn Learn more: Guest/external sharing:Overview of Loop workspaces storage and permissions | Microsoft Learn(will be updated before rollout) Summary of governance, lifecycle, and compliance capabilities for Loop(direct link to section that says Loop workplace sensitivity labels are not available; will be updated before rollout) What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation. MC922626 — Microsoft Forms: New streamlined and modernized experience Microsoft 365 Roadmap ID400715 Microsoft Forms is updating the end-to-end experience with a new appearance for the portal page, form creation, and response analysis. Users can toggle between upgraded templates as they create their form and then view insights and suggested actions when the responses come in. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late October 2024 and expect to complete by early November 2024. How this will affect your organization: Employees who use Microsoft Forms will get the new UI experience after release. In the portal page, templates are organized into four categories – Feedback, Registration, Research, and Quiz. As users enter the design page, they'll find a wide selection of templates displayed in the left-side pane. They can browse and switch between different types/topics. In the right-hand pane, from the Style button, the users can select a style from our suggestions or personalize their own. Additionally, they can choose the layout for the cover page of the invitation. The results page has also has a new design. Users can now quickly analyze responses with charts and graphs, making the data easier to interpret for more effective analysis. This new feature is available by default. Learn more:Revamped Forms experience is now available for commercial users. What you need to do to prepare: This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. MC921113 — Support for the Word Mobile, Excel Mobile, and PowerPoint Mobile UWP applications will end on October 14, 2025 Support for the Word Mobile, Excel Mobile, and PowerPoint Mobile Universal Windows Platform (UWP) applications will end on October 14, 2025. After that date, no further updates, security fixes, or technical support will be available for these applications. When this will happen: This retirement will occur on October 14, 2025. How this will affect your organization: If Microsoft Windows-based devices within your organization are running Word Mobile, Excel Mobile, or PowerPoint Mobile, we recommend that the applications be removed before the October 14, 2025, end of support date. While they may continue to function, using unsupported software could lead to potential security risks and other issues. If you’re using Microsoft Intune, you can run a report to identify devices running these applications. In the Microsoft Intune admin center, go toAll services>Apps | Monitor>Discovered appsand search for "office.word", “office.excel”, or “office.powerpoint”. The application version will start with "16001.14326.xxxxx.x". What you need to do to prepare: To mitigate these risks and ensure your organization remains secure and compliant, we recommend removing these applications and switching to alternatives: Microsoft 365 mobile appfor iOS or Android phones and tablet devices. Word, Excel, and PowerPoint on the web.Learn more. Desktop versions of Word, Excel, and PowerPoint in a Microsoft 365 plan.Compare Microsoft 365 Enterprise Plans. For information about the end of support for the OneNote UWP application (OneNote for Windows 10) see:Moving to OneNote on Windows. Planning ahead will help you avoid potential disruptions and keep your organization’s software environment secure and up to date. MC911615 — Word, Excel, and PowerPoint for macOS – Planned update to compatibility Office add-ins and ODBC drivers Note: If your organization does not use macOS, you can safely disregard this message. Microsoft Word, Excel, and PowerPoint in Office for macOS Version 16.91 only load dynamic libraries that are codesigned with a valid Apple Developer ID. As a result, Office add-ins or Open Database Connectivity (ODBC) drivers that rely on unsigned or ad-hoc-signed dynamic libraries don't work as intended. However, most dynamic libraries used with Office apps are already codesigned, so this change is unlikely to affect most users. In this message, when non-Microsoft products is mentioned, it specifically refers to products and applications that enhance or extend Office functionality (like add-ins or integrations). This doesn't include all non-Microsoft software installed on your device. When will this happen: This change is expected to be live in production in mid-November 2024. How this affects your organization: Reason for the change: Microsoft requires executable code from non-Microsoft products be codesigned with a validApple Developer ID. This requirement ensures that only verified and properly signed code runs within Office applications, promoting code integrity and compliance with macOS development standards. Workflow changes for users: If your workflow uses unsigned dynamic libraries within Word, Excel, or PowerPoint for macOS, it no longer works as intended. You need to get an updated version of the product from the original software developer. What you can do to prepare: Actions required for developers: If your product uses dynamic libraries, make sure they're codesigned with an Apple Developer ID. Unsigned or ad-hoc-signed libraries are no longer allowed to load into Office app processes. For more information on the Apple Developer program and tools, see theApple Developer Program. Office applications support libraries codesigned for distribution through any Apple-supported distribution mechanism, including direct download by your customers. Steps for admins: Verify Deployed non-Microsoft Products: Check if you have any non-Microsoft products deployed to your users. These products often: o Extend Office functionality by adding menu or ribbon controls. o Communicate with other applications to share content with Office. o Support external data connections such as ODBC. Confirm codesigning compliance: Make sure that any non-Microsoft products follow best practices and codesigned any dynamic libraries included in their products. If any libraries aren't codesigned, contact the product developer for updates. Monitor system logs: Inspect the system console logs for Library Load Constraint Rejection messages. These messages from macOS identify any dynamic library that the OS rejects from loading into an Office app process. Consider proactively blocking all non-Microsoft libraries: To block these libraries, set the Office preference DisableVisualBasicExternalDylibs to true using Mobile Device Management (MDM) software. For more information, see theApple Platform Deployment guide. Warning: Blocking all non-Microsoft libraries from running within Visual Basic macros is a significant action and should only be considered if absolutely necessary for your organization's requirements on macOS computers. MC910978 — Support for Office 2016 and Office 2019 will end October 14, 2025: Upgrade recommended Support for Office 2016 and Office 2019 will end one year from today, on October 14, 2025. After that date, no further updates, security fixes, or technical support will be available for these versions of Office. While the applications may continue to function, using unsupported software could lead to potential security risks and other issues. Because migrations can take time, we recommend starting to upgrade any remaining devices your organization has running Office 2016 or Office 2019 to a supported version as soon as possible. What you need to do to prepare: To mitigate these risks and ensure your organization remains secure and compliant, we recommend upgrading devices running Office 2016 or Office 2019 toMicrosoft 365 E3, which includes Microsoft 365 Apps for enterprise plus core device management, security, and compliance capabilities. Microsoft 365 Apps for enterprise provides the latest versions of desktop apps like Word, Excel, and PowerPoint with regular updates and continuous support under theModern LifecyclePolicy and is eligible for the Microsoft 365 Copilot add-on. For scenarios that require a fully disconnected solution, we recommend upgrading toOffice LTSC 2024. Office LTSC 2024 includes a subset of the value in Microsoft 365 Apps and will be supported for five years under theFixed Lifecycle Policy. Resources to help you prepare for this transition: Read theupgrade guidancefor an overview of how to move from Office 2016 or Office 2019 to Microsoft 365 Apps. Consider engagingMicrosoft FastTrack, a Microsoft support service for moving to Microsoft 365 E3. Visit ourOffice End of Support Tech Communityfor more information and resources about the end of support for Office. Planning ahead will help you avoid potential disruptions and keep your organization’s software environment secure and up to date. MC908110 — (Updated) Project for the Web Email Notification Update Updated October 17, 2024: We have updated the content. Thank you for your patience. We're making an update to the behavior of email notification in Project for the web. When a project or roadmap is shared with a Microsoft 365 group, only if the group has 50 or less members will an email notification be sent to each member of the group notifying them a plan or roadmap has been shared with them. If the group has more than 50 members then group members will not receive an email notification when a project or roadmap is shared with the group. Individual notification settings will continue to be respected when these emails are sent. When this will happen: General Availability: We will begin rolling out mid-November 2024 and expect to complete by late November 2024. How this will affect your organization: For users of Project for the web if a project or roadmap is shared with a group has 50 or less members in it, an email notification is sent to each member informing them the project or roadmap was shared with them. For groups with more than 50 members, an email is not sent when a project or roadmap is shared with the group. What you need to do to prepare: Update any business documentation or processes which will be impacted by this change. MC906497 — Microsoft Stream: Less storage space consumed for Stream videos in Microsoft 365 Suite (GCC, GCCH, DoD) Video files tend to be very large and consume lots of space against your Microsoft OneDrive and Microsoft SharePoint storage quotas. Currently, when you make metadata changes such as title, description, transcripts, chapters, interactivity, thumbnails, media settings, and so on to files in Microsoft Stream, each of those changes cause new versions to be created. Each of these versions in Microsoft OneDrive and Microsoft SharePoint count the full file size towards consumed storage quota. Thus, for large video and audio files, these versions cause your storage consumption to quickly increase. To prevent this, we are changing how Microsoft Stream handles versioning. Any changes made specifically to chapters and transcripts of files from Stream will stop making versions, thus preventing storage from increasing as rapidly as it has in the past. When this will happen: General Availability (GCC, GCC High, DoD): Available now. How this will affect your organization: Changes to video and audio files from Stream will no longer take version snapshots. This means that any metadata changes in chapters and/or transcripts made through Stream cannot be reverted to previous versions. The following actions will no longer create a version in the file’s version history: Adding or editing chapters, transcripts, captions, or interactivity. Toggling transcript media settings. The following actions will still create a version in the file's version history: Editing title or description from within Stream. Adding audio tracks. Editing column metadata in SharePoint document library for a video file. Editing title or description from outside of Stream. Replacing the file with a new different version of the file. Toggling media settings (show/hide about video, chapters, interactivity, comments, analytics, etc.). Other operations outside of the Stream app. This change will happen by default, and there will not be a way to revert to the previous behavior where chapters and transcripts changed in Stream created versions. This change will only stop new versions from being taken from Stream. To clean up existing versions of files or versions taken outside of Stream, the SharePoint team has a separate capability and new settings coming that will help clean up low-value versions (see Roadmap ID145802). Admins must complete this action for each site, and it will take approximately 30 days before the new version of the site is in effect. For more information, visitVersioning in Stream - Microsoft Support. What you need to do to prepare: This rollout will happen automatically with no admin action required. This change will happen by default, and there are no settings to control it. You may want to notify your users about this change and update any relevant documentation as appropriate. MC823294 — (Updated) Microsoft Lists app: New drag and drop feature Microsoft 365 Roadmap ID380183 Updated October 15, 2024: We have updated the timeline below. Thank you for your patience. Coming soon for theMicrosoft Listsapp: Users will be able to reorder List items using drag and drop. When this will happen: Targeted Release: We will begin rolling out early August 2024 and expect to complete by mid-August 2024. Standard Release: We will begin rolling out late August 2024 and expect to complete by late October 2024 (previously early October). How this will affect your organization: Before this rollout: Users are not able to drag and drop list items to reorder them. After this rollout, Users will be able to drag and drop list items. This feature is on by default and accessible to allMicrosoft List appusers. Drag and drop items to reorder your items in Microsoft Lists! Drag and drop multiple items, too! What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Microsoft Lists App | Microsoft 365 Drag and drop to reorder list items - Microsoft Support MC822726 — (Updated) Microsoft Excel: Extending support for Insights Services to GCC Microsoft 365 Roadmap ID396171 Updated October 9, 2024: We have updated the rollout timeline below. Thank you for your patience. GCC customers will be able to use features in Microsoft Excel run by Insights Services, including Analyze Data, found on the Home tab. When this will happen: General Availability (GCC): We will begin rolling out mid-September 2024 (previously late August) and expect to complete by late October 2024 (previously late September). How this will affect your organization: Customers on GCC will now have the Analyze Data button in the Home tab on web, Microsoft Windows, and Mac. They can use this feature to get insights about their data and will also be able to receive Recommended Charts and Recommended Pivot Tables on web. For more information, visit: Analyze Data in Excel - Microsoft Support Recommended Charts What you need to do to prepare: This rollout will happen automatically. You can turn off Analyze Data by going to Trust Center Settings > Privacy Options > Privacy Settings > Turn off all connected experiences. You may want to notify your users about this change and update any relevant documentation as appropriate. MC805212 — (Updated) Microsoft 365 apps: Improved resharing experience Updated October 15, 2024: We have updated the rollout timeline below. Thank you for your patience. Currently, when you share a link with view-only permissions in Microsoft 365 apps,clicking onCopy linkdefaults to an "Only people with existing access" link that does not always target your intended people. With this new feature, when you share a link with view-only permissions with other people, those people will now be able to copy that same link directly from the Share dialog when they attempt to share. If your only option to share with others isOnly people with existing access, you will be able to send a request to the owner to share this file with specific people directly in the sharing control. The owner of the file will then receive a request and will be able to approve or reject the request. When this will happen: Targeted Release: We will begin rolling out mid-September (previously mid-August) 2024 and expect to complete by late September (previously late August) 2024. General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out late September (previously mid-September) 2024 and expect to late October 2024 (previously mid-October). How this will affect your organization: With this new feature, anyone who accesses a Microsoft 365 apps file with view-only permissions will see this new experience. Learn more:Sharing files, folders, and list items - Microsoft Support(content within will be updated before rollout begins). What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. MC803292 — (Updated) Modernized user-defined permissions experience for Word, Excel, and PowerPoint Microsoft 365 Roadmap ID189826 Updated October 25, 2024: We recently discovered a significant issue that has resulted in the temporary disabling of this feature until it is resolved. We apologize for any inconvenience this may cause. There is a new experience for selecting which users should have which permissions when a sensitivity label configured for user-defined permissions is applied to a file in Microsoft 365 apps or when a user applies protection using standalone Information Rights Management. When this will happen: Preview (Worldwide, GCC): We will begin rolling out mid-July 2024 and expect to complete by late July 2024. General Availability (Worldwide, GCC): We will begin rolling out early September 2024 and expect to complete by late November 2024 (previously late September). How this will affect your organization: Users will see a modernized dialog when configuring user-defined permissions, whether these are applied using a sensitivity label configured for user-defined permissions or with standalone Information Rights Management. There are new names for some usage rights groupings for pre-set permissions levels compared to those in Microsoft Azure Information Protection (AIP): Revieweris now calledRestricted Editor. Co-Authoris now calledEditor. Co-Owneris now calledOwner. The rights contained in each grouping are unchanged. SeeConfigure usage rights for Azure Information Protectionfor further information on usage rights. This new feature is available by default. What you need to do to prepare: If your organization has training materials or internal documentation regarding the use of pre-set permissions levels, you may need to make updates based on the new names for these permissions levels. MC714520 — (Updated) Apps for the web: Grid view for tasks in Microsoft To Do web version and To Do inside Microsoft Outlook Microsoft 365 Roadmap ID381749 Updated October 9, 2024: We have updated the rollout timeline below. Thank you for your patience. In Microsoft 365 apps for the web, users can see their tasks in a grid view and can update details inline in To Do on web and To Do app inside Microsoft Outlook. When this will happen: General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out late April 2024 (previously early April) and expect to complete by late November 2024 (previously late September). How this will affect your organization: When users open To Do on web within Microsoft Outlook, they will see their tasks in a tabular format or grid. They can continue to have the list view if preferred. What you need to do to prepare: There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate. Documentation - Office 365 IP Address and URL web service October 31, 2024 - GCC September 30, 2024 - GCC High September 30, 2024 - DODMicrosoft Ignite session: AI for the Public Sector with Microsoft 365 Copilot GCC available Nov 19
In today's rapidly evolving digital landscape, the public sector stands at the forefront of innovation, driven by the transformative power of AI. Microsoft 365 Copilot GCC (Government Community Cloud) is set to revolutionize how public sector organizations operate, offering new capabilities that will enhance human capabilities, streamline workflows, and support compliance with stringent security standards. AI for the Public Sector with Microsoft 365 Copilot GCC - OD803 Our Ignite On Demand session delves into the myriad ways Microsoft 365 Copilot GCC can empower your public sector organizations, from automating routine tasks to providing actionable insights that drive mission-critical decisions. We invite you to watch this session and discover how you can harness the power of AI to elevate your organization's capabilities. Microsoft Ignite | November 18-22, 2024| ignite.microsoft.com The '101 on Microsoft Ignite 2024' What:Microsoft Igniteto learn more | FullSession scheduler Where: Hybrid | Chicago, IL (sold out) and Global Digital (online; free to register) When: November 18-22, 2024 Primary X handle & official hashtag:#MSIgnite(join in) AND follow@MicrosoftTeams,@SharePoint,@OneDrive, and@Events_MSFT The Ignite presentation highlights several key areas where Microsoft 365 Copilot GCC can make a significant impact for public sector strategists. We explore the role of AI in the public sector, emphasizing how AI can alleviate the burden of digital debt by automating repetitive tasks and optimizing workflows. The session also showcases the features of Microsoft 365 Copilot GCC such as Microsoft 365 Copilot Business Chat and AI-driven insights in applications embedded in apps you use everyday Word, Excel, PowerPoint, Teams and Outlook. Additionally, the presentation underscores the importance of responsible AI practices and data privacy, detailing Microsoft's commitment to security and compliance within the GCC environment. To start building your AI skills today and prepare your organization for the future, we encourage you to explore the following resources: Microsoft 365 Copilot GCC Blog: aka.ms/M365CopilotGCCBlog Microsoft 365 Copilot GCC High/DOD Blog: aka.ms/MS365CopilotGCCHighBlog Microsoft 365 Copilot – Readiness and Adoption Guide for Public Sector Roadmap ID #415097-Microsoft 365 Copilot GCCgeneral availability -- the product referenced in this blog. Service description will be updated prior to general availabilityhere Roadmap ID #464984-Microsoft Copilotgeneral availability for GCC -- more information will be shared on this product closer to launch. Current information for WW/Ent environment on differences between these two products can be referencedhere. Additionally, you can learn more about the roadmap for government AI adoption and specific Copilot scenarios for the US government. By leveraging these resources, you can ensure your organization is well-equipped to navigate the AI-driven future and deliver exceptional public services. The Roadmap for Government AI Adoption US Gov specific Copilot Scenarios content Other Microsoft 365 Copilot resources (environment agnostic): 3 short explainer videos:Microsoft 365 Copilot data security and privacy commitments Microsoft 365 - How Microsoft 365 Delivers Trustworthy AI (2024-01) Data, Privacy, and Security for Microsoft 365 Copilot Secure by default with Microsoft Purview and protect against oversharing Microsoft Purview data security and compliance protections for Microsoft Copilot Apply principles of Zero Trust to Microsoft 365 Copilot Learn about retention for Microsoft 365 Copilot This blog was written with support from Microsoft 365 Copilot, my AI assistant for work.Microsoft Product Placemat for CMMC - October 2024 Update
This Microsoft Tech Community Public Sector Blog post is an update of the Microsoft Product Placemat for CMMC assisting the Defense Industrial Base (DIB) for compliance with the Cybersecurity Maturity Model Certification (CMMC) from the U.S. Department of Defense (DOD).Understanding Compliance Between Commercial, Government and DoD Offerings - September 2023 Update
Understanding compliance between Commercial, Government and DoD offerings: There remains much confusion as to what service supports what standards best. If you have DFARS, ITAR, FedRAMP, CJIS, IRS and other regulatory requirements and you are trying to understand what service is the best fit for your organization then you should read this article.Understanding Compliance Between Microsoft 365 Commercial, GCC, GCC-High and DoD Offerings
Understanding compliance between Commercial, GCC, GCC High and DoD offerings: There remains much confusion as to what service supports what standards best. If you have DFARS, ITAR, FedRAMP, CJIS, IRS and other regulatory requirements and you are trying to understand what service is the best fit for your organization then you should read this article.Understanding Compliance Between Commercial, Government and DoD Offerings - February 2021 Update
Understanding compliance between Commercial, Government and DoD offerings: There remains much confusion as to what service supports what standards best. If you have DFARS, ITAR, FedRAMP, CJIS, IRS and other regulatory requirements and you are trying to understand what service is the best fit for your organization then you should read this article.
