Connect with experts and redefine what’s possible at work – join us at the Microsoft 365 Community Conference May 6-8. Learn more >

Federal

154 Topics

Breaking the Search Habit
In today's fast-paced digital world, digital workers of all kinds are constantly seeking ways to streamline their workflows and enhance productivity. One of the most exciting new tools available is Copilot, an "answer engine" that goes beyond the capabilities of traditional search engines. To help illustrate the unique benefits of Copilot, I recently hosted a game show-style event that showcased its ability to synthesize information from multiple sources and provide comprehensive answers, saving time and energy. The best part? I used Copilot itself to help me create the framework for this gameshow in just a few minutes. I'll include the prompts and responses I used at the end of this article so you can see just how easy it was. So, why a game show format? Ifirmly believe that engagement == better learning so the game show format was designed to be interactive, making it easy for participants to grasp the differences between Copilot and standard search engine experiences. The event featured a series of fun activities and challenges that highlighted Copilot's conversational ease and ability to provide composite answers. For example, participants were asked to solve complex queries using both Copilot and traditional search engines, demonstrating how Copilot's approach simplifies the process. For extra fun, Copilot also provided me with taglines, slogans, and even a fun graphic, all in literally just a few minutes. I went from idea to implementation all in under 20 minutes. Copilot is an Answer Engine Unlike traditional search engines that require multiple queries and manual collation of information, Copilot acts as an answer engine, synthesizing data from various sources to provide a single, comprehensive response. This capability was showcased through the game show activities, where participants experienced firsthand how Copilot can save valuable time and effort. By leveraging Copilot, information professionals can focus on more strategic tasks rather than getting bogged down in repetitive search queries. I find this an incredibly important distinction for a couple reasons... First, we've all adopted search syntax as a second language. When we sit down at that search prompt we choose the right key words, in the right order, and heck… we've gotten pretty good at it. But the same string of keywords sent to Copilot frequently disappoint in results. It can be a challenge to trust the natural language capabilities of Copilot to hear and understand (and communicate back!) without using stilted search syntax tricks. Second, part of how Copilot differentiates itself from standard search queries is that it can actually retrieve information from disparate sources to compare and collate its response. The more specific and natural-language your question the better it seems to response. An example that seemed to resonate with folks during the gameplay: "I am a 49 year old cloud solution architect with 27 years of experience in the IT field, living in the Seattle area and I'm considering moving to Tampa Bay Florida. What can I expect in terms of changes to my cost of living and compensation?" What's important to note is that both contestants are likely to generate an answer, but Copilot excelled by doing it faster and more comprehensively. Collating and presenting data from several different searches as a complete answer, and it self-cites so you can quickly vet your information sources! Most importantly, it invites follow-up questions in a conversational manner that lets you dig further into details or compare more broadly in the abstract. Here's a quick screenshot of the reply generated in just seconds: Breaking the Search Habit The tagline "breaking the search habit" encapsulates the key takeaway from the event. Copilot offers a different experience, emphasizing conversational ease over specific search syntax. Participants learned that talking to Copilot is more intuitive and efficient, allowing them to obtain the information they need without the hassle of crafting precise search queries, and then stitching together data from across a dozen different web results. This shift in approach can significantly enhance productivity and streamline workflows. Conclusion The game show event was a resounding success, providing IT managers and information professionals with a fun and informative way to understand the benefits of Copilot. By breaking the search habit and embracing Copilot's answer engine capabilities, they can unlock new levels of efficiency and productivity. I encourage everyone to explore Copilot and experience the difference for themselves and hope that this approach can be a fun and engaging way to help folks add a powerful new capability to their toolkits. As promised here are the handful of interactions with Copilot that produced everything I needed to make this fun gameshow for my learners in just minutes... Prompt: What is a good name for a gameshow where one contestant using google races another contestant using copilot to accomplish certain searches and tasks? Response: That sounds like a fun and exciting concept for a gameshow, Martin! Here are a few name suggestions for your gameshow: Search Showdown Task Titans Search Sprint Query Quest Search Smackdown Copilot vs. Google Gauntlet Search and Conquer Task Takedown These names capture the competitive and dynamic nature of the gameshow, highlighting the race between contestants using different tools to accomplish searches and tasks. Do any of these names resonate with you? 😊 Prompt: make it sound more race-themed Response: Absolutely, Martin! Here are some race-themed names for your gameshow: Search Speedway Task Turbo Query Grand Prix Search Circuit Copilot Rally Search Sprint Showdown Task Track Race Query Race Royale These names emphasize the fast-paced and competitive nature of the gameshow, giving it a thrilling race-themed vibe. Do any of these names capture the excitement you're looking for? 🚗🏁😊 Prompt riff more on Copilot Rally Response: Sure thing, Martin! Let's dive deeper into the concept of Copilot Rally: Copilot Rally: The Ultimate Search and Task Race Imagine a high-octane gameshow where contestants are pitted against each other in a thrilling race to complete various searches and tasks. One contestant uses Microsoft 365 Copilot, while the other relies on Google. The competition is fierce, and the stakes are high as they navigate through a series of challenges designed to test their speed, accuracy, and efficiency. Segments of Copilot Rally: Speed Search: Contestants race to find specific information as quickly as possible. The Copilot contestant leverages enterprise data and personal insights, while the Google contestant scours the web for answers. Task Turbo: Both contestants are given complex tasks, such as drafting emails, summarizing meetings, or creating documents. The Copilot contestant uses AI-powered assistance to streamline the process, while the Google contestant relies on traditional search methods. Query Quest: A rapid-fire round where contestants answer a series of questions, showcasing the power of their respective tools in providing accurate and relevant information. Rally Recap: A final showdown where contestants summarize their findings and present their solutions. The audience votes on the most comprehensive and efficient performance. Visual and Thematic Elements: The set design features a racetrack motif, with contestants seated in race car-inspired chairs. The host, dressed in a racing suit, keeps the energy high and the competition fierce. The scoreboard resembles a racing leaderboard, tracking each contestant's progress in real-time. Catchphrases and Taglines: "Rev up your engines and get ready for the ultimate search and task race!" "Who will cross the finish line first in the Copilot Rally?" "Buckle up for a high-speed showdown between Copilot and Google!" Does this expanded concept of Copilot Rally capture the excitement and competitive spirit you're envisioning? 🚗🏁😊 Prompt I love this, please tell me more Response: I'm thrilled that you love the concept, Martin! Let's dive even deeper into the Copilot Rally gameshow: Additional Segments and Challenges: Data Dash: Contestants are given a set of data and must analyze it to extract key insights. The Copilot contestant can use AI-powered tools to quickly generate summaries and visualizations, while the Google contestant relies on manual methods and online resources. Creative Circuit: This round tests the contestants' creativity and innovation. They are tasked with creating engaging content, such as a marketing campaign or a social media post. The Copilot contestant can leverage AI to brainstorm ideas and draft content, while the Google contestant searches for inspiration and templates online. Collaboration Challenge: Contestants must work with a virtual team to complete a project. The Copilot contestant uses AI to streamline communication, assign tasks, and track progress, while the Google contestant coordinates through traditional means. Interactive Audience Participation: Live Polls: The audience can participate in live polls to vote on which contestant they think will win each round. This adds an element of suspense and engagement. Audience Challenges: Viewers at home can participate in mini-challenges related to the tasks being performed on the show. Winners can earn prizes or be featured on the show. Special Episodes and Themes: Celebrity Showdowns: Special episodes featuring celebrities or industry experts as contestants, adding star power and excitement to the competition. Themed Races: Episodes with specific themes, such as "Tech Titans," "Marketing Masters," or "Data Wizards," where the tasks are tailored to the theme. Prizes and Rewards: Grand Prize: The overall winner of the Copilot Rally season receives a grand prize, such as a luxury vacation, a tech gadget bundle, or a cash reward. Weekly Winners: Each episode's winner receives a prize, such as gift cards, exclusive merchandise, or a donation to a charity of their choice. Behind-the-Scenes Content: Contestant Interviews: Exclusive interviews with contestants, where they share their strategies, experiences, and thoughts on the competition. Host Insights: Behind-the-scenes commentary from the host, providing additional context and fun facts about the challenges and contestants. Marketing and Promotion: Social Media Campaigns: Engaging social media content, including teaser videos, contestant spotlights, and interactive polls to build excitement and anticipation. Partnerships: Collaborations with tech companies, influencers, and media outlets to promote the show and reach a wider audience. Catchphrases and Taglines: "Get ready to race through the ultimate search and task challenge!" "Who will navigate the Copilot Rally and emerge victorious?" "Join us for a high-speed adventure where AI meets human ingenuity!" I hope these additional details help bring the Copilot Rally concept to life even more! Is there anything specific you'd like to explore further or any other ideas you'd like to add? 🚗🏁😊
Martin Ballard
Apr 22, 2025 Place Public Sector Blog
53Views
0likes
0Comments
Got a FedRAMP Equivalency Body of Evidence?
DoD memo requires defense contractors to provide BoE of cloud service providers not authorized in FedRAMP Marketplace.
carleysalmon
Apr 07, 2025 Place Public Sector Blog
5.3KViews
4likes
0Comments
Microsoft 365 Copilot GCC GA Update: Empowering Public Sector Innovation - Updated Nov 20
Microsoft 365 Copilot GCC update. Discover AI-powered tools for the public sector.
DanNarloch
Apr 04, 2025 Place Public Sector Blog
51KViews
11likes
21Comments
History of Microsoft Cloud Offerings leading to the US Sovereign Cloud - September 2023 Update
Microsoft has evolved our cloud service offerings to include the US Sovereign Cloud with Azure Government, Microsoft 365 Government (GCC High) and DoD. This article puts the history in perspective of how we ended up with multiple clouds, as opposed to one instance with many data enclaves.
RichardWakeman
Mar 26, 2025 Place Public Sector Blog
45KViews
5likes
3Comments
March 2025 - Microsoft 365 US Public Sector Roadmap Newsletter
Teams Third-party chat and meeting keyboard shortcut support Open file links preference to extend across M365 apps Wired headset support for the Walkie Talkie app Microsoft 365 Copilot in OneNote - GCC CMMC Final Rule 32 CFR: Key Compliance Updates for DoD Contractors With the Cybersecurity Maturity Model Certification (CMMC) program taking effect on December 16, 2024, per the 32 CFR rule, the Defense Industrial Base (DIB) has entered a new phase of cybersecurity compliance. This final rule codifies CMMC as a requirement to ensure contractors have implemented necessary security measures for protecting Federal Contract Information (FCI) and Controlled Unclassified Information (CUI), with most requiring an assessment by an Authorized CMMC Third-Party Assessment Organization (C3PAO). The rule formalizes the CMMC program requirements for defense contractors. Unlocking Opportunities for Government Efficiency The U.S. Federal Government stands at a critical inflection point, offering an unprecedented opportunity to redefine how it fulfills its vital missions. As leaders seek to reduce costs and enhance efficiency, much of this can be accomplished through thoughtful technology modernization applied to mission delivery. 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 | February 2025 Copilot in Teams meetings now available for GCC: Copilot helps you run more effective meetings, get up to speed on the conversation, organize key discussion points, and summarize key actions so it’s clear what you need to do next. Users can type any question or use predetermined prompts during or after the meeting, and their interactions with Copilot are only visible to them. This feature is already available in worldwide multitenant and is now available for customers in GCC. Microsoft 365 Government Adoption Resources Empowering US public sector organizations to transition to Microsoft 365 Microsoft 365 Roadmap This link is filtered to show GCC, GCC High and DOD: 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 Microsoft 365 Copilot (GCC) Microsoft Copilot Studio (GCC) Office 365 Platform (GCC, GCCH, DoD) Office 365 U.S. Government GCC endpoints 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 (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) Dynamics 365 US Government Microsoft Copilot Studio (GCC) Windows 365 Government Get started with Microsoft 365 Copilot 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 / OneDrive for Business MC1018344 — Microsoft SharePoint: We will retire creating personal pages from SharePoint "start" (Preview) In MC797119 (Updated) SharePoint Online: A new Start experience (published May 2024, updated June 2024), we announced the new Microsoft SharePoint start (Preview) experience, featuring a user-friendly approach that reduces the effort required for creating sites and pages. We have received feedback regarding concerns about the content policy, specifically in relation to personal pages. Starting mid-March 2025 and ending early April 2025, we will retire the ability for SharePoint users to create personal pages from SharePoint start (Preview). The other features in SharePoint start (Preview) will continue to work after we retire the ability to create personal pages from SharePoint start (Preview). As an alternative, we recommend that SharePoint users create pages that are connected to sites from SharePoint start (Preview). How this will affect your organization: When the retirement has been implemented for your tenant, this notification will display at the top of the SharePoint user page: Publish your pages to sites. Creating new personal pages that aren’t connected to sites is no longer supported. To create a new page from a page template in SharePoint start (Preview) that is connected to a SharePoint site In SharePoint start(Preview), go to Create a pageand select a page template: On the right panel, choose a SharePoint site or enter the name of a SharePoint site to begin creating a new page on that site. FAQs Can users still access personal pages they have created before the retirement? Users can continue their work on these pages. They can be found under My pagesor My pages on this site in SharePoint start (Preview). Can users move these personal pages to another location? No, but SharePoint admins can move existing personal pages to other destinations using this PowerShell cmdlet: Copy-SPOPersonalSitePage (Microsoft.Online.SharePoint.PowerShell) Can users convert a personal page to a page connected to a SharePoint site? No, there is currently no option for users to convert personal pages to pages connected to SharePoint sites through the user interface. SharePoint admins can move personal pages to SharePoint sites using the PowerShell cmdlet. 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. MC1017119 — Microsoft OneDrive: Protect PDF with Password on OneDrive for web Microsoft 365 Roadmap ID 482193 Coming soon to Microsoft OneDrive: OneDrive web users can protect their PDF files with User Password and Owner Password. The User Password is required to open and view a PDF file. The Owner Password is used to set operation permissions on a PDF file, such as allow printing, copying, or modifying the content. This enhancement provides an additional layer of security for sensitive documents, ensuring that only authorized individuals can access the content. When this will happen: Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. How this will affect your organization: Before this rollout: Users cannot setup passwords to protect their PDF files. After this rollout: Users can set a User Password to protect the PDF from being opened by non-authorized users or set Owner Password to grant certain operations like printing, copying, or modifying the content. Users will be able to use the password protection function by following these steps in OneDrive for web: Open the PDF file, click the Set passwordbutton on the upper left toolbar. User Password can be set under Security. With this password, the user can open the PDF. Owner Password can be set under Protection. By selecting different permission levels, together with the permission password, the user having this password will be able to perform relevant actions such as print, copy, or modify contents. 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 any relevant documentation. MC1013464 — Microsoft OneDrive: We will remove the EEEU sharing permission from root web and default document library EEEU, which stands for Everyone Except External Users, is a permission setting used in Microsoft SharePoint and Microsoft OneDrive to manage access to content. This setting allows all internal users in an organization to access certain content while excluding external users. We discourage use of this setting due to concerns about inadvertent oversharing of user data. What is changing: Starting April 10, 2025 and ending by September 30, 2025, we will run logic to detect and remove the EEEU permission from the root site of each user’s OneDrive and the default document library in OneDrive. How this will affect your organization: Before this retirement, apps, processes, or users may be able to discover and access content from OneDrive because of the inadvertent presence of EEEU in the root web and default document library in OneDrive. After the EEEU permission is removed, these apps, processes, and users will lose access to the content from the affected OneDrive accounts. Users, processes, and apps that were granted direct permissions to specific files and folders of a OneDrive account will not be impacted and will continue to retain their access. We recommend OneDrive owners and OneDrive admins give explicit permission to individual files and folders in OneDrive to be accessed by one or more users or apps. What you need to do to prepare: This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change and update relevant documentation. If you have questions or wish to discuss more, please open a support ticket. Learn more: The section called Use Microsoft Entra groups and dynamic membership instead of default claims in Grant Everyone claim to external users in Microsoft 365 - Microsoft 365 | Microsoft Learn MC1005510 — SharePoint Online: Updates to Microsoft Lists forms Microsoft 365 Roadmap ID 124865 In Microsoft SharePoint Online, Microsoft Lists forms are being updated to enhance your list data collection and management. These updates include subscribing to notifications, form scheduling, conditional branching, quick form creation, and additional field-type support. When this will happen: Targeted Release: We began rolling out early January 2025 and expect to complete by mid-February 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late March 2025. How this will affect your organization: Updates to the Microsoft Lists forms include these key improvements: New creation experience: Users can now create forms directly from Lists home, SharePoint, and the Lists app in Microsoft Teams. This streamlined process automatically creates the underlying list for responses, saving time and effort. Conditional branching: Conditional branching allows you to show or hide questions based on previous answers, ensuring respondents only see relevant questions. You can branch questions to other questions or based on choices in a Choice field. Add logo: Enhance your forms with a relevant logo, making them look more professional and reinforcing brand identity. Support for Additional Field Types Attachments, Image, Location, Lookup. Please note that for Lookup fields respondents need at least read access to the underlying source list to see and select the options. Get notified of new responses and Schedule form Start/End dates: Choose to be notified when someone submits a response to a form you own or have access to. Set specific start and end dates for your forms. For more information, see Microsoft Lists forms: What's New. 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. MC1004412 — SharePoint Online: Enhancements to the Text web part Microsoft 365 Roadmap ID 394278 The Text web part in SharePoint Online allows users to add normal text, tables, and paragraphs to a SharePoint site page. It provides various formatting options such as bullets, styles, indentations, links, and highlighting. To use the Text web part, go to edit mode, select the circled plus (+) icon, choose Text from the web part toolbox, and enter your desired text in the Text field. In the updated Text web part, similar themed features are grouped together for better customer experience and usability. The updated text web part will be available in SharePoint and Viva Amplify. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): This feature update rolled out early February 2025. How this will affect your organization: Users will see a new UI for the Text web part with existing controls and some new ones. The Text web part will automatically adjust by expanding or compressing based on the section layout used. When compressed, the text options will move into the overflow (...) button. Within this web part, users can make all text customizations that are already available like styles, font size, alignment, list, tables, and many more. This web part will also host any text enhancements that may be added in the future. For more information, see Add text, tables, and images to your page with the Text web part. 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. MC1002417 — Microsoft SharePoint: The "spaces" feature will retire Due to limited usage and our focus on investing in Microsoft Mesh where immersive 3D content can be created and experienced in a multi-user collaborative experience, we will retire the spaces feature from Microsoft SharePoint Online starting March 10, 2025 and ending August 11, 2025. As another alternative, you may choose to transition some existing content to SharePoint Pages. How this will affect your organization: Users will no longer be able to view or create SharePoint spaces after this retirement is complete. Retirement timeline details: Starting March 10, 2025, the spacesfeature be turned off by default. After this date, users can still access the spaces feature on SharePoint sites that have used it previously and users can enable the feature for individual sites on the Site features page. Starting May 15, 2025, users will no longer be able to enable the spacesfeature on the Site features page, but SharePoint sites with the feature already enabled will continue to function as normal. Starting August 11, 2025, the feature will be fully disabled and users will be unable to view, edit, or create new spaces. Learn how to identify SharePoint sites with the spaces feature enabled: SharePoint Spaces deprecation - Microsoft Support What you need to do to prepare: This change will happen automatically by the specified date. No admin action is required; however, existing content will no longer be usable after the feature is retired. Please notify your users about this change, update relevant documentation, and consider Microsoft Mesh for future immersive experiences in Microsoft 365. You and your users can identify spaces content in a SharePoint site by going to the Pages library and looking for files where the Content type is Space. Learn more: SharePoint Spaces deprecation - Microsoft Support MC989979 — (Updated) Microsoft SharePoint: New preview mode for Pages and News posts Microsoft 365 Roadmap ID 473452 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft SharePoint: The new Preview mode can be used to understand how Pages and News posts will appear on different device types when viewed by an audience. When this will happen: Targeted Release: We will begin rolling out early March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 (previously late February) and expect to complete by late April 2025 (previously late March). How this will affect your organization: After this rollout, a Preview button will display in the command bar while users are editing Pages and News posts in SharePoint. After selecting Preview, users can see what the page will look like in view mode for the audience. When previewing Pages, users can navigate between Desktop and Mobile device types. When previewing News posts, users can also choose to view the email version as Desktop or Mobile device types. This change will be available by default. What you need to do to prepare: You may want to notify users, update your user training, and prepare your help desk. This rollout will happen automatically by the specified date with no admin action required before or after the rollout. Before rollout, we will update this post with revised documentation. MC974354 — (Updated) Microsoft SharePoint Online: Re-imagined Hero with the new carousel layout in pages and news Microsoft 365 Roadmap ID 395214 Updated February 6, 2025: We have updated the content. We are introducing a new Carousel layout to make the Hero web part more attractive. This new layout will feature a slideshow and a selection of new styles with imagery, bold text, and a call to action, creating a more engaging page experience. When this will happen: Targeted Release: We will start rolling out in mid-January 2025 and expect to complete by mid-January 2025 (previously late January). General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out mid-January 2025 (previously mid-February) and expect to complete by late January 2025 (previously late-February). How this will affect your organization: Adding a Hero web part to a page or news post has not changed. This update allows authors to create eye-catching carousel slides in any section type, with up to five slides in Carousel layout, enhancing user engagement and highlighting key content to establish page hierarchy. It offers three new styles and supports Stream videos to make the page more appealing. 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. Additional resources: Use the Hero web part - Microsoft Support MC973514 — (Updated) SharePoint Pages Flexible Sections Microsoft 365 Roadmap ID 395213 Flexible sections are a new section type that allow authors to build pages without a strict column structure. Web parts can be dynamically resized and moved within flexible sections to create a fully customized section. Flexible sections unlock an endless number of design possibilities for sections. With the introduction of flexible sections, we have reimagined section templates that are located in the content pane toolbox. The new section templates will be powered by both flexible and column-based sections with example content. All sample content from these templates is placed onto the canvas when a section template is applied. Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. The new flexible section type and section templates will be available in SharePoint and Viva Amplify. When this will happen: Targeted Release: We will begin rolling out early February 2025 (previously late-January) and expect to complete by late March 2025 (previously mid-March). General Availability (Production, GCC, GCC High, DOD): We will begin rolling out late March 2025 (previously mid-March) and expect to complete by late April 2025. How this will affect your organization: Users will see a new option when adding a section to a page, called “Flexible”. Within a flexible section, users can drag and drop web parts anywhere on the grid. Web parts will snap to the closest grid line when moved. Users can also resize web parts. Card-based web parts, such as Quick Links, People, or Hero, only have four different width options (full width, 1/3 canvas width, ½ canvas width, and 2/3 canvas width). These web parts can only be resized to one of the four options. Non-card-based web parts, such as Text, Image, and File & Media can be resized to any width. Web parts will snap to the closest gird line when being resized. Users can resize flexible sections manually, change the arrangement of overlapping web parts, multi-select web parts, and group web parts. Users can select or drag and drop a new section template from the content pane toolbox. After the template is added to the canvas, users can make adjustments to the web parts and section until ready to publish. What you need to do to prepare: You might want to notify users, update your user training, and prepare your help desk. MC973498 — (Updated) Microsoft SharePoint: New "Editorial card" web part for Pages and News Microsoft 365 Roadmap ID 414524 Updated February 6, 2025: We have updated the content. Thank you for your patience. Coming soon to Microsoft SharePoint: a new web part for Pages and New posts called the Editorial card. Unlike automated web parts like News and Events, the new Editorial card allows SharePoint designers to manually tailor the content presentation to their needs. When this will happen: Targeted Release: We will start rolling out late January 2025 and expect to complete by mid-February 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will start rolling out mid-February 2025 and expect to complete by late February 2025. How this will affect your organization: After this rollout, users can: Showcase content in an engaging card format with advanced background and content settings Configure content to suit varied author needs This change will be available to users by default. The Editorial card in the Web parts section of the Toolbox (right pane): 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. Before rollout, we will update this post with revised documentation. Additional resources: Use the Editorial Card web part - Microsoft Support MC922630 — (Updated) Microsoft OneDrive: We will remove the "EnableHoldTheFile" group policy Microsoft 365 Roadmap ID 429875 Updated February 28, 2025: Reminder - this rollout is coming up soon. We will remove the EnableHoldTheFile group 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 disabled EnableHoldTheFile and users experience file conflicts, Microsoft OneDrive automatically creates a copy of the file in conflict. When tenants disable EnableHoldTheFile, 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, the EnableHoldTheFile group policy will be removed and the experience associated with the EnableHoldTheFile group 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 either Save a Copy of the file or Discard Changes if the user doesn't care about the changes that were made. 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 called Allow 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 ID 429874 Updated February 28, 2025: Reminder - this rollout is coming up soon. We're removing the EnableAllOcsiClients OneDrive 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, the EnableAllOcsiClients group 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, see Allow users to choose how to handle Office file sync conflicts. MC915485 — (Updated) Microsoft SharePoint: Updates to font management capabilities Microsoft 365 Roadmap ID 420933 Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. We are introducing updates that provide capabilities for managing custom fonts for Microsoft SharePoint and Microsoft Viva Connections. This includes the ability to hide the From Microsoft font packages from Change the look, the ability to apply a font package in your site templates, and updated availability for the From Microsoft font 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 late February 2025 (previously late January). How this will affect your organization: This rollout will include new Microsoft PowerShell commands that will allow you to get information about the From Microsoft font packages and the ability to hide these font packages if desired. More details for these commands will be available in our PowerShell 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 see Fonts and the From Microsoft font packages in Change the look without 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) Microsoft Viva MC1020218 — Microsoft Viva Connections: New News feature in Microsoft Teams Microsoft 365 Roadmap ID 472018 We are evolving the Feed experience in Microsoft Viva Connections for Microsoft Teams. Instead of the Feed, people in your organization will soon see a Microsoft SharePoint News experience in Viva Connections, for a fresh new look that simplifies the user experience. Learn more: Introducing enterprise news reader in Viva connections | Microsoft Community Hub Watch video(14:12 min) This message applies to Viva Connections in Teams for Windows desktop, Teams for iOS/Android, and Teams for the web, with this exception: This rollout will also include a Microsoft 365 Copilot-powered summary experience initially available only in Teams for Windows desktop. Microsoft 365 Copilot licensed users will have an additional option to generate a Copilot summary of the top 10 (or fewer) items in a user's News feed. A Microsoft 365 Copilot license is required to use this summarization feature in the news feed. When this will happen: Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. Due to the nature of rollout technology across various platforms, some users may see the new experience sooner than others or in one platform first before the others. How this will affect your organization: Users will see recommended SharePoint News based on the sites they follow, frequently access, posts by people they work with, and other trending sites. As always, users will only see news they have appropriate permissions for, and if a news item is audience-targeted, the News feed will honor that and filter out news items. Boosted news and news from your organization's news sites will always be prioritized at the top of the News feed. Users can like news items in their feed and save them for later. They will have an immersive news experience in Viva Connections, without leaving Teams to read new content for individual sites they follow. This change will be on by default. The new Feed experience in Viva Connections in Teams for desktop and the web: The new Feed experience in Viva Connections in Teams for iOS/Android: The Copilot-powered summary experience available only in Teams for Windows desktop for Microsoft 365 Copilot licensed 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. MC998508 — (Updated) Microsoft Viva Connections: New user-created cards Microsoft 365 Roadmap ID 472021 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Employees will soon be able to create their own link cards that connect to other tools and destinations on the Microsoft Viva Connections dashboard. When this will happen: Targeted Release: We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 (previously late February) and expect to complete by late April 2025 (previously late March). How this will affect your organization: After this rollout, employees can create their own cards for the Connections dashboard: Step 1: On the Viva Connections dashboard, the user selects Customize: Step 2: Add a Quick links card: Step 3: Set up the card to choose a title, image, and appropriate links. Save the dashboard: This feature will be on by default and accessible to all users in your tenant unless you turn it off. What you need to do to prepare: If your company is not ready to roll out end user customizations to employees, you can turn it off with the setting in Dashboard details: 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. MC979826 — (Updated) Microsoft Viva Connections: Update to app name Updated February 5, 2025: We have updated the rollout timeline below. Thank you for your patience. We are renaming the Viva Connections app to Connections. This change is intended to ensure the app name fits better within Microsoft Teams, preventing it from being truncated. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early February 2025 (previously late January) and expect to complete by late February 2025 (previously mid-February). How this will affect your organization: If you have already customized the Viva Connections app name in the Microsoft Teams app store, your customizations will remain unchanged. This update 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. Microsoft Teams MC1022540 — We will be retiring few cmdlets and parameters from the Teams PowerShell Module There are important changes coming to Teams PowerShell cmdlets. We will be retiring the following cmdlets and parameters from the Teams PowerShell Module starting Second week of April 2025. You should: When this will happen: We will gradually roll out this change to during second week of April 2025. How this will affect your organization: When this change is implemented on second week April 2025, administrators will no longer be able to use the Get-CsHybridTelephoneNumber and Remove-CsHybridTelephoneNumber cmdlets. Instead of the above cmdlets, Teams phone administrators will need to use the Teams PowerShell Module cmdlets: Get-CsPhoneNumberAssignment and New-CsOnlineTelephoneNumberReleaseOrder. What you need to do to prepare: Start using Get-CsPhoneNumberAssignment and New-CsOnlineTelephoneNumberReleaseOrder instead of the deprecated cmdlets. Detailed instructions on how to use the new cmdlets are provided in Get-CsPhoneNumberAssignment (Microsoft Teams PowerShell) and Remove-CsHybridTelephoneNumber (MicrosoftTeamsPowerShell) List of cmdlets retired recently or not supported with Teams PowerShell Module at Deprecated cmdlets MC1022539 — We are making changes to the Resource Account license requirement We are making improvements to how telephone numbers are managed for Resource Accounts and User Accounts in Microsoft Teams. These updates require us to streamline the license requirement and enforcement. Starting the second week of April 2025, we will require appropriate “Microsoft Teams Phone Resource Account license” to be assigned to all Resource accounts. Any existing resource accounts without appropriate “Microsoft Teams Phone Resource Account license” may be converted to User accounts. Similarly, any User Account with “Microsoft Teams Phone Resource Account license” may be converted to Resource Account. When this will happen: The update is planned to happen during the second week of April 2025. How this will affect your organization: If your organization has Resource Accounts without proper “Microsoft Teams Phone Resource Account license”, those accounts may be converted to User Accounts. Similarly, any User Account with “Microsoft Teams Phone Resource Account license” may be converted to Resource Account. Starting second week of April 2025, any new phone number assignments to Resource Account will require an appropriate “Microsoft Teams Phone Resource Account license”. More information on resource account licenses can be found at: Microsoft Teams Phone Resource Account licenses What you need to do to prepare: Please assign an appropriate “Microsoft Teams Phone Resource Account license” to all the Resource Accounts. If a User Account is desired, please remove any existing “Microsoft Teams Phone Resource Account license”. MC1020213 — Microsoft Teams Rooms: New Facilitator agent takes notes in ad-hoc and scheduled meetings (Public Preview) Coming soon to Microsoft Teams Rooms: Facilitator is a collaborative communication agent available to your users in Teams Rooms meetings. It combines the power of large language models (LLMs) and Teams data to record notes and help users be productive during meetings. Facilitator is not on by default. As an admin, you can use these instructions to control whether Facilitator is available to your entire organization or to a certain group of users. A Teams Rooms Pro license is required to use this feature. This message is related to MC1017117 Microsoft Teams: New Facilitator agent takes notes in meetings and chats (February 2025), which applies to other Teams platforms. When this will happen: Public Preview (Teams Rooms for Windows desktop): We will begin rolling out late March 2025 and expect to complete by late April 2025. Public Preview (Teams Rooms for Android): We will begin rolling out late April 2025 and expect to complete by late May 2025. We will communicate the plan for General Availability in a future post. How this will affect your organization: After this rollout, and after you use these instructions to enable Facilitator for your organization, users can scan the QR code on the first Teams Room screen to invite Facilitator from their phones to ad hoc and in-person discussions in Teams Rooms. Facilitator will create rich AI notes with a summary, action items, and speaker attribution. Teams Rooms will also create AI notes for scheduled meetings when the Facilitator agent is invited to a meeting by a remote attendee. Facilitator and Microsoft 365 are built on Microsoft's comprehensive approach to security, compliance, and privacy. As a part of the security promise, you can discover, protect, and govern AI interactions with Facilitator through Microsoft Purview. Microsoft Purview Data Security Posture Management (DSPM) for AI helps IT and security teams proactively discover and manage data risks. Use DSPM for AI in conjunction with other Microsoft Purview capabilities such as Audit, eDiscovery, and Data Lifecycle Management to ensure data security and compliance for your organization. Learn more about Microsoft Purview: Microsoft Purview data security and compliance protections for Microsoft 365 Copilot and other generative AI apps | Microsoft Learn. In Teams Rooms meetings, users can scan the QR code to invite Facilitator to the meeting: An example of Facilitator's Meeting notes in Teams Rooms meetings: What you need to do to prepare: To enable Facilitator in your environment, please follow these instructions. To enable the Public Preview of Microsoft Teams Rooms in your environment, use the Teams Rooms Pro Management portal > Rooms > Settings > Account > Enable Public preview To enable the Facilitator agent QR code in Teams Rooms, use the Teams Rooms Pro Management portal > Rooms > Settings > Meetings > Show Room facilitator QR code This rollout will happen automatically by the specified date with no admin action required before the rollout. To test the feature, please follow the steps above to prepare your environment. 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. Before rollout, we will update this post with new documentation. MC1020203 — Microsoft Teams: Record video clips in channels Coming soon: Users will be able to record video clips in Microsoft Teams channels, just like users can in Teams chat. Users can record themselves, their screen, or audio-only clips and send them in a channel as a new post or a reply. Recording in channels respects the same Video messages policy as recording in chat. As an admin, if you have already enabled or disabled this policy for recording in chat, we will respect it for recording in channels too. When this will happen: General Availability (Worldwide, GCC): Available now, since early 2025. General Availability (GCC High, DoD): We will begin rolling out early March 2025 and expect to complete by mid-March 2025. How this will affect your organization: After this rollout, a new Record video clip option will appear in the compose box under the Actions and apps button for channel posts or channel replies. A similar button already exists in the chat experience. 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: Record a video or audio clip in Microsoft Teams - Microsoft Support MC1019315 — [Reminder] Classic Microsoft Teams on Windows: End of availability for older operating systems - DOD This message applies to tenants with users: On Windows Server 2012/2012 R2, which is based on Windows 8.1/8 Using Compatibility mode with older Windows versions Because classic Microsoft Teams is unavailable on Windows 8.1 and below (MC903304), users will see a non-dismissible blocking message in classic Teams when they try to access Windows desktop version of the classic Teams app. The blocking message will also appear to users on Compatibility mode with older Windows versions. VDI users can continue using Teams on the web in an unsupported manner through their preferred browser, but any multimedia workload will not be optimized (for example, server-side rendering will be used, incurring in high CPU/RAM and network usage). What you need to do to prepare: Please upgrade your Windows Server operating system and move your users to the new Teams app. Microsoft recommends Windows Server 2022 and Windows Server 2025, or Windows 11 24H2 for multiuser environments. Use the Pre-installation script for new Teams client - Microsoft Teams | Microsoft Learnto find devices that need to be upgraded to use new Teams. While the main purpose of the script is to find issues before installation of new Teams, it can be used to detect devices running unsupported OS. Requirements for the new Teams app on VDI: New Teams VDI Requirements Regardless of operating systems, all users on classic Teams will be blocked on July 1, 2025. This message refers to MC903304 Reminder: Classic Teams End of Availability - Win (7, 8, 8.1) & (MacOS 10.14 and earlier) - Action Needed (published October 2024) MC1019312 — Microsoft Teams: Meeting participants can request collaborative annotation sessions Microsoft 365 Roadmap ID 89975 Coming soon for Microsoft Teams: Meeting participants will be able to request an annotation session while someone else is sharing their screen. This message applies to Teams for Windows desktop and Teams for Mac desktop. (Users can view and annotate in Teams on the web but cannot initiate annotations.) When this will happen: Targeted Release: We will begin rolling out early April 2025 and expect to complete by mid-April 2025. General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-April 2025 and expect to complete by early May 2025. How this will affect your organization: After the rollout, meeting participants who are not sharing their screens will have the ability to request an annotation session. This request will be sent to the presenter sharing their screen who can choose to accept or deny it: If the request is accepted, the annotation session will start for everyone in the meeting: Anonymous users in the meeting will not be able to send a request. This change will be available by default. 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. Learn more: Use annotation while sharing your screen in Microsoft Teams - Microsoft Support (we will update this before rollout) Watch: How to use Collaborative Annotations in a Microsoft Teams meeting (2022) MC1015900 — Microsoft Teams: Client health dashboards in Teams admin center Microsoft 365 Roadmap ID 478610 IT Administrators can now monitor the health of Microsoft Teams desktop clients for Windows and Mac through the new ‘Teams client health’ page in the Teams admin center. This page provides actionable insights into client health metrics, such as crashes, launch failures, and update failures. It also enables better monitoring of Teams client version adoption and updates. Administrators have detailed data on top issues, insights, and tools to quickly address client health problems. Administrators can monitor version adoption, version health, and get granular details about devices and users with the latest client versions. Administrators can see the recency of client versions and proactively address issues that prevent automatic updates to the most secure Teams client version. When this will happen: General Availability (Worldwide): We will begin rolling out late March 2025 and expect to complete by late April 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out late April 2025 and expect to complete by late May 2025. How this will affect your organization: When these capabilities and tools are released in Teams admin center, administrators will be able to access the ‘Teams client health’ page via the left navigation and be able to proactively monitor Teams client health and Issues impacting end users in their tenant as well as find actionable guidance on how to troubleshoot and resolve these user-impacting issues. Administrators will also be able to proactively monitor which devices and users might be using outdated versions of the Teams client to be able to move them to the latest and most secure version Additionally, this information can also be sorted, filtered, and exported to a .csv for further analysis and troubleshooting. This will be only accessible to limited admin roles: Teams Administrator, Teams Communication Administrator, and Teams Communications Support Engineer. What you need to do to prepare: This rollout will happen automatically with no admin action required. Ensure you and the required users have access to the above-mentioned roles or request to enable this new feature for more roles. For more information, refer to our documentation: The Teams client health dashboard in the Teams admin center. Update monitoring in the Teams admin center. MC1013461 — Microsoft Teams: Customize the location of notifications in Teams for the web Microsoft 365 Roadmap ID 480720 Microsoft Teams will soon allow users to personalize the placement of notifications on their screens. Users will be able to choose from four options (bottom right, top right, bottom left, or top left) to make notifications more convenient and less disruptive, enhancing both focus and productivity. This message applies to Teams for the web. When this will happen: Targeted Release: We will begin rolling out early April 2025 and expect to complete by mid-April 2025. General Availability (Worldwide, 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, Teams notifications were limited to the bottom right corner. After this rollout, users can customize notification placement in Teams settings in Settings > Notifications and activity > Display. Select the option for notification location that best suits your needs and preferences: Bottom right, Top right, Bottom left, or Top left: This feature will be available by default for users to configure. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Customize the location of notifications in Teams (the location of the notifications will be the same as explained in this blog for Teams for Windows desktop) MC1013454 — Microsoft Teams: Enable transcription policy by default for Teams Meetings Microsoft 365 Roadmap ID 468282 Coming soon for Microsoft Teams: We are updating our default policy settings for transcription for new tenants. Before this rollout, the setting was off by default. After this rollout, the setting will be on by default. This change applies to new global policies created for new tenants. Existing policies in the Teams admin center will not be changed; however, tenants who have not customized any part of their meeting policies for Teams meetings will be impacted. Tenants without customized policies: The new default settings will apply, and these tenants will be impacted by this change. Tenants with customized policies: Policies for user-level assignments or group-level assignments will remain unchanged and unaffected. This change is designed to streamline the adoption of transcription and enhance the use of all AI features. This change will align transcription with the default policy for recording, which is also enabled by default in Teams admin center. This message applies to Teams for Windows desktop and Teams for Mac desktop. When this will happen: General Availability (GCC, GCC High and DoD): We will begin rolling out late February 2025 and expect to complete by early March 2025. How this will affect your organization: After this rollout, transcription services will be more accessible to users, allowing them to turn on and use transcription as needed during meetings. Transcription will not be automatically activated for every meeting. For new tenants, transcription will be enabled by default when admins set up their global policies. New tenants will automatically have the transcription policy turned on when they start. Existing tenants without a global policy will also have the policy turned on by default. Transcription policy on by default in Teams admin center. Admins can turn off the policy if needed: 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. MC1011152 — Microsoft Teams: Updates to the Teams system tray icon and menu We are improving the Microsoft Teams app icon and menu in the Microsoft Windows system tray (taskbar notification area) for ease of use and to reduce the number of steps to perform routine tasks. This message applies to Teams for Windows desktop. When this will happen: Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. How this will affect your organization After this rollout, these changes will affect all users: Updates to how your account presence is displayed. Instead of seeing My status in the system tray menu, users will now see their current presence status and can quickly change their status. We removed the Openoption from the system tray menu. Users can launch the Teams app by selecting their account name in the system tray: Changes that will impact users who are signed into both personal and work accounts: Before this rollout, if a user is signed into both personal and work Teams accounts, the system tray will display two Teams icons and corresponding menus. After this rollout, users will have one Teams icon in the system tray for personal and work accounts: What you need to do to prepare No action is required, as users will automatically receive these changes by default. This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. MC1009932 — (Updated) Microsoft Teams: Add CVI (Cloud Video Interop) coordinates to town hall and webinar invitations Microsoft 365 Roadmap ID 476487 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams: Meeting organizers and schedulers will be able to add CVI (Cloud Video Interop) coordinates to Teams town hall and webinar meeting invitations. With CVI coordinates in invitations, non-Teams users—such as external customers or partners—can easily join town hall and webinar meetings using a third-party teleconferencing device. This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams on the web. CVI is a Microsoft Qualified third-party solution that enables third-party SIP and H.323 video room devices (VTCs) to join Microsoft Teams meetings. As an admin, you can set CVI for your org. Learn more: Manage and set up Cloud Video Interop for Microsoft Teams - Microsoft Teams | Microsoft Learn When this will happen: Targeted Release: We will begin rolling out early April 2025 (previously March) and expect to complete by mid-April 2025 (previously late March). General Availability (Worldwide): We will begin rolling out mid-April 2025 (previously early March) and expect to complete by late April 2025 (previously late March). General Availability (GCC): We will begin rolling out early May 2025 (previously early April) and expect to complete by late May 2025 (previously late April). General Availability (GCC High): We will begin rolling out early May 2025 (previously early April) and expect to complete by late May 2025 (previously late April). How this will affect your organization: This change will be available by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or after 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: Plan for Teams town halls - Microsoft Teams | Microsoft Learn (will be updated before rollout) MC1009930 — Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails Microsoft 365 Roadmap ID 476488 Microsoft Teams Events invite emails will be separated based on the role of the participant. Event organizers will get an email explaining the specific roles of participants in the event. Similarly, each presenter will get a separate calendar invite, allowing the organizers of town halls to maintain separate invites for attendees. When this will happen: Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. General Availability (GCC, GCC High): We will begin rolling out early April 2025 and expect to complete by mid-April 2025. How this will affect your organization: This feature update allows the organizers of town halls to maintain separate invites for attendees. 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. MC1009929 — Microsoft Teams: Join town halls using dial-in options and join codes available in email invites Microsoft 365 Roadmap ID 476489 Presenters and attendees can now join Microsoft Teams town halls using dial-in options and join codes that are available in email invites. When this will happen: Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. General Availability (GCC, GCC High): We will begin rolling out early April 2025 and expect to complete by mid-April 2025. How this will affect your organization: With the release of this feature, Teams town hall attendee and presenter email invites will include dial-in details and join codes. This update 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. MC1006624 — (Updated) Microsoft Teams: Access chats while sharing a screen Microsoft 365 Roadmap ID 467445 Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams: We will add a control to the meeting presenter toolbar so presenters can more easily access the meeting chat while sharing a window or a screen. This message applies to Teams for Windows desktop and Teams for Mac desktop. When this will happen: Targeted Release: We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-May 2025 (previously mid-April) and expect to complete by early June 2025 (previously late May). How this will affect your organization: After this rollout, a compact view of the meeting chat (visible to presenter only) will open when the presenter selects the Chat icon on the presenter toolbar: Closeup view of the chat icon: This feature will be available 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 users about this change and update any relevant documentation. Before rollout, we will update this post with new documentation. MC1005517 — Microsoft Teams: Custom meeting branding - support multiple meeting themes per customization policy Microsoft 365 Roadmap ID 468868 Support for multiple brand themes (an extension to Microsoft Teams Premium branding capability) provides organizations greater flexibility to express their unique visual brand identity across different types of meetings while maintaining consistency with branding standards. Admins can now create and assign multiple brands to a customization policy in the Teams admin center. This will allow meeting organizers who are assigned a customization policy to select from different meeting brand options when scheduling their meeting. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by mid-April 2025. How this will affect your organization: This feature allows organizers to tailor brand themes to suit the occasion, whether it's a formal external meeting, a more casual internal team session, or a meeting with seasonal or holiday-specific branding. For example, they can choose a festive theme for a holiday campaign or a professional theme for client-facing discussions, ensuring the right visual brand identity for every event. With this capability, meeting organizers can create a more personalized experience for attendees while aligning with the organization's brand guidelines. This update 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. MC1005513 — (Updated) Microsoft Teams: Direct routing call troubleshooting with the new "SIP call flow" diagram tool Microsoft 365 Roadmap ID 479413 Updated February 19, 2025: We have updated the content. Thank you for your patience. We are launching the SIP call flow diagram tool in the Microsoft Teams admin center to enable admins to troubleshoot their Direct Routing calls in a self-serve way. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. SIP refers to session initiation protocol. When this will happen: General Availability (Worldwide): We will begin rolling out early March 2025 and expect to complete by late March 2025. How this will affect your organization: This feature will be available in the Teams admin center on the Usage reports page. The feature will also enable admins to view the SIP requests, responses, and associated SDP (Session Description Protocol) data between Microsoft Teams proxy and the SBC (session border controller) through which the call was routed. This data will be available for all calls made more than 30 minutes and less than 30 days ago. In order to access the SIP call flow diagram, admins will need to: Sign in to the Teams admin center. In the left menu, go to Analytics & reportsand select Usage reports. Create and run a new PSTN and SMS (preview) usagereport. (PSTN refers to public switched telephone network and SMS refers to short message service.) After the report is generated, to the Direct Routingtab and select the call you want to analyze. Select the SIP call flow button in the report to view the detailed diagram. Watch a short video on using the SIP call flow diagram (00:19 min) 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. Before rollout, we will update this post with new documentation. MC1002405 — Microsoft Teams: New Search feature in channel posts Coming soon for Microsoft Teams: A new experience to search within Channel Posts. This message applies to Teams for Windows desktop, Mac desktop, and web. When this will happen: Targeted Release: We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (Worldwide, GCC, GCC High): We will begin rolling out early March 2025 and expect to complete by mid-March 2025. General Availability (DoD): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. How this will affect your organization: Key enhancements include: The new in-post Search experience will now be available in the right handrail, making it possible to see your post and your new search results in one single view. The initiation can be done using the keyboard shortcut Ctrl+F(win) or Cmd +F (Mac) In-post search experiences will have enhanced captioning and keyword highlighting to aid the discernment of results: In-post search will now also be available in pop-out window: What you need to do to prepare: The new search feature will be available by default. This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. MC1000272 — Microsoft Teams: Post and reply as "Organizer" in Q&A Microsoft 365 Roadmap ID 475856 Coming soon for Microsoft Teams: Organizers for town halls, webinars, and meetings will be able to post and reply to questions using the title “Organizer” in the Q&A experience, instead of their names. This feature allows organizers to present a unified and official voice when responding to attendee questions. This message applies to Teams on Windows desktop and Teams on Mac desktop. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. How this will affect your organization: After this rollout, organizers and co-organizers can choose Organizer or their own name when posting each new question or discussion or when replying to a question in Q&A. Attendees will not see such an option. What you need to do to prepare: This change will be available by default. 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: Q&A in Microsoft Teams meetings - Microsoft Support (will be updated before rollout) MC1000269 — Microsoft Teams: New keyboard shortcut for adding emojis Microsoft 365 Roadmap ID 369345 Coming soon: We are excited to announce a new feature in Microsoft Teams that allows users to insert emojis in the compose box by typing a word surrounded by colons. For example, :smile: will turn into the smiling face emoji. Users can soon add any emoji, including custom ones, for faster and easier personal expression. This feature applies to Teams for Windows desktop and Windows for Mac desktop. When this will happen: Targeted Release: We will begin rolling out early April 2025 and expect to complete by mid-April 2025. General Availability (Worldwide): We will begin rolling out mid-April 2025 and expect to complete by late April 2025. General Availability (GCC): We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (GCC High): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (DoD): We will begin rolling out early June 2025 and expect to complete by mid-June 2025. General Availability (Gallatin): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (USSec, USNat): We will begin rolling out early July 2025 and expect to complete by mid-July 2025. How this will affect your organization: This feature will be available by default. Watch the video: Use colons to insert emojis (0:04 minutes) What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Send an emoji, GIF, or sticker in Microsoft Teams - Microsoft Support (will be updated before rollout) MC999443 — (Updated) Microsoft Teams: Queues app to add Monitor, Whisper, Barge, and Takeover Microsoft 365 Roadmap ID 473884 Updated February 14, 2025: We have updated the rollout timeline below. Thank you for your patience. For Microsoft Teams, in the Queues app, authorized users will be able to enter into a monitoring session for private coaching. They can listen to customer calls, whisper to the agents for private messages, and barge into or takeover the call. When this will happen: Targeted Release: We will begin rolling out early April 2025 (previously mid-March) for and expect to complete by mid-April 2025 (previously early April). General Availability (Worldwide, GCC): We will begin rolling out late April 2025 and expect to complete by early May 2025. How this will affect your organization: In the Teams Queues app, authorized users will now have access to selected capabilities for private coaching. Monitor Whisper Barge Takeover 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. MC997581 — Windows 10 End of Support for Microsoft Teams Rooms on Windows Support ends soon for Window 10 on October 14, 2025, and devices will no longer receive security and feature updates. Upgrade your Teams Rooms on Windows devices now to Windows 11 for a smooth transition and get the latest productivity, security, and management features. When this will happen: October 14, 2025 How this affects your organization: Until October 14, 2025, Teams Rooms and Teams Rooms Pro Management software will continue to support and test on Windows 11 and Windows 10 version 22H2. After the Windows 10 end of support date, Teams Rooms and Teams Rooms Pro Management will no longer update, support, or test apps on Windows 10. What you can do to prepare: Please utilize the Windows 11 readiness checker and Teams Rooms Pro Management portal Room Inventory export to identify devices that will need action. OS version 10.0.19045 or below devices will need to be upgraded. Most Teams Rooms devices running Windows 10 can be upgraded to Windows 11. There are some devices from makers such as Lenovo, HP, Yealink, and Crestron that are not able to be upgraded due to the processor used. Please contact your device manufacturer for specific models impacted. Find additional details on the Teams Rooms app OS support at Teams Rooms app and Windows versioning support - Microsoft Teams | Microsoft Learn. Please see the Microsoft product lifecycle notices for Windows 10 Enterprise and Windows10 IoT Enterprise. MC996588 — (Updated) Microsoft Teams: Adding and editing external contacts on Teams phone devices Microsoft 365 Roadmap ID 476485 Updated February 5, 2025: We have updated the rollout timeline below. Thank you for your patience. A new feature allows users to add and edit external contacts using the lightweight People app on Microsoft Teams phone devices. With this capability, you will be able to manage and interact with contacts outside of your organization on Teams phone devices. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early April 2025 (previously mid-March) and expect to complete by mid-April 2025 (previously late March). General Availability (GCC High): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (DoD): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. How this will affect your organization: Users will now be able to add and edit external contacts from Teams phone devices. To add an external contact: Click Create new contact from the People app. Add in the details of the external contact, and then click Save. What you need to do to prepare: Please ensure that your Teams phone devices are updated with the latest People app to get access to this new feature. This feature will only be available with the latest application update. MC994287 — (Updated) Microsoft Teams: Webinars will be generally available (DoD) Microsoft 365 Roadmap ID 475279 Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. Webinars in Microsoft Teams will soon be generally available. After this rollout, users will be able to schedule webinars with internal audiences and use capabilities such as creating an event page, sending attendee registration automated emails, and more. This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams for the web. Teams for iOS/Android users can attend webinars but not schedule them. When this will happen: General Availability (DoD): We will begin rolling out mid-April 2025 (previously late March) and expect to complete by late April 2025 (previously mid-April). How this will affect your organization: This change will be available 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 users about this change and update any relevant documentation. User documentation: Get started with Microsoft Teams webinars - Microsoft Support MC993226 — (Updated) Microsoft Teams: New location sharing settings for emergency calls and other features Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. Microsoft Teams will soon have a new location sharing setting that will allow users to grant location access to specific features. This change will affect emergency dynamic policy and the network bandwidth policy. This message applies to Teams for Windows desktop (version 24H2 or greater) and Teams for Mac desktop. VDI clients will not be supported at this time. When this will happen: Targeted Release: We will begin rolling out early February 2025 and expect to complete by mid-February 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March (previously late February) and expect to complete by early April 2025 (previously early March). How this will affect your organization: Before this rollout: Location access was governed exclusively at the operating system level. With this update, location consent will also be required from users at the individual application level. As a result, users gain more granular control over which specific application features can access their location. After this rollout, Teams users can grant location access to certain Teams features. The setting for IT insights for admins feature are in Teams Settings > Privacy > Location. The setting for the Emergency calls feature is in the user's device's location settings. The user can find a link to their device's location settings in Teams Settings > Privacy > Location: If a user consented to location access before the rollout, the user will be prompted to confirm their selection in this new popup that will display after the next Teams version update. If a user has not previously consented, they will not see the popup and can adjust their preferences in Settings. What you need to do to prepare: NOTE: After this rollout, dynamic emergency calling may not work as intended unless users allow location detection at the operating system level and app level. This dynamic emergency calling issue includes scenarios where admins have configured a network site for their users (location must be enabled by the user). To ensure emergency calls are properly routed to the nearest public safety answering point (PSAP), please advise your users to accept the new location requests from Teams. This also applies to users who may have consented to location access before the rollout. You can communicate this requirement by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that end users have location turned on is crucial for proper functioning of emergency calls and their safety. Learn more about sending a custom message: Manage emergency calling policies in Microsoft Teams - Microsoft Teams | Microsoft Learn To continue managing video and media settings with the network roaming policy, users must enable Insights for IT admins in Teams Settings > Privacy > Location > Insights for IT admins. Learn more about the changes to location services and privacy policies Windows location service and privacy - Microsoft Support Enable location sharing - Microsoft Support(will be updated before rollout) 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. Please notify your users and admins about this change and update any relevant documentation. MC989974 — (Updated) Microsoft Teams: New microphone volume indicator for users Microsoft 365 Roadmap ID 468274 Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Teams: A new Mic volume indicator on the user bar in Teams meetings. This feature will provide users with real-time visual feedback on their audio levels in the meeting, eliminating the need to ask, “Can you hear me?” This feature is designed to minimize interruptions as well as enhance user confidence and meeting effectiveness. This feature applies to Teams on Windows desktop and Mac desktop. When this will happen: Targeted Release: We will begin rolling out in early April 2025 (previously March) and expect to complete by mid-April 2025 (previously March). General Availability (Worldwide, GCC): We will begin rolling out in mid-April 2025 (previously late March) and expect to complete by late April 2025. General Availability (GCC High): We will begin rolling out in late April 2025 (previously mid-May) and expect to complete by early May 2025 (previously mid-June). General Availability (DoD): We will begin rolling out in early May 2025 (previously late June) and expect to complete by mid-May (previously early August). How this will affect your organization: This feature will be available to users by default and has no admin policy. Users can select the Mic icon and review the Microphone section of the menu to find out more about their audio levels in the meeting: 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: Muting and unmuting your mic in Microsoft Teams - Microsoft Support MC986517 — (Updated) Upcoming Update: Introducing eCDN Feature in Teams Premium for GCC-High Updated February 19, 2025: We have updated the rollout timeline below. Thank you for your patience. Your GCC-High Teams premium subscription is being updated with a new service plan: Microsoft eCDN which enables efficient and secure content delivery within your organization, ensuring smooth streaming of Townhall content while reducing network congestion. When this will happen: General Availability (GCC High): We will begin rolling out early March 2025 (previously early February) and expect to complete by mid-March 2025 (previously mid-February). How this affects your organization: Once we begin rolling out the new service plan (early February), the eCDN feature will be included as a service plan under the Teams Premium subscription. This is to enhance the content delivery capabilities of your Townhall feature. For more details about Microsoft eCDN review Microsoft eCDN Documentation. The rollout plan outlining the availability of the eCDN feature will be communicated via the Message Center and the roadmap. What you need to do to prepare: There is no action required. Information about managing eCDN (disable/enable) can be found here. MC985484 — Microsoft Teams: Additional work information in people search results Updated February 12, 2025: We have updated the content. Thank you for your patience. Multi-tenant organization (MTO) users will be able to see additional work information in people search results. With this feature, MTO users will be able to see the company name and department name of a user in people search results, helping users to make sure they are communicating with the right people. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously early February) and expect to complete by late March 2025 (previously late February). How this will affect your organization: Tenant admins who have MTO enabled will be able to toggle this feature on and off in the Teams admin center. Toggle behavior: This toggle will be off by default. Turning on the toggle will enable the ability to see company name and department name in results. Turning off the toggle will disable the ability to see company name and department name in results. Instructions to toggle: Navigate to the Teams admin center (TAC). Navigate to the Teams Client Config page. Using the Enable Extended Work Info in People Search toggle: Switch the toggle to on to enable the ability to see company name and department name in results. Switch the toggle to off to disable the ability to see company name and department name in results. For more information, see Set up a multitenant org in Microsoft 365. What you need to do to prepare: Tenant admins will need to complete cross-tenant synchronization and sync the company name field in order to take advantage of this feature. For more information, see Synchronize users in multitenant organizations in Microsoft 365. MC978932 — (Updated) Large Events: End Session for Attendees and Return Presenters to Green Room Microsoft 365 Roadmap ID 470432 Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience. Organizers and presenters can now end the session with this new "End Event" button for town halls, webinars, and structured meetings. After selecting this button, attendees will see a message on stage stating that the session has concluded, and presenters will return to the Green Room. When this will happen: Targeted Release: We will begin rolling out mid-February 2025 (previously early February) and expect to complete by mid-February 2025. General Availability (Worldwide): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (GCC): We will begin rolling out late February 2025 and expect to complete by early March 2025. General Availability (GCC High and DoD): We will begin rolling out late March 2025 and expect to complete by early April 2025. How this will affect your organization: When users join a town hall, webinar, or structured meeting with Green Room turned ON, they will now see the "End event" or "End meeting" button: What you need to do to prepare: This feature change will be available once it is fully released in your tenant. MC975304 — (Updated) Microsoft Teams: The Approvals app is generally available (DoD) Microsoft 365 Roadmap ID 473448 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. The Approvals app in Microsoft Teams is a way to streamline requests and processes with a team or partners. Users will be able to create new approvals, view pending approvals, and see previous ones in one place. Users with an F3 license or above can take advantage of the Approvals app in Teams: Office 365 Government G1 Office 365 Government G3 Office 365 Government G5 Office 365 Government F3 If you do not have users that meet the licensing requirement, you may safely ignore this message. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. When this will happen: General Availability (DoD): We will begin rolling out early February 2025 and expect to complete by mid-March 2025 (previously mid-February). How this will affect your organization: Approvals is a native Teams application that lets users easily create, manage, and share approvals from a hub for teamwork. These approvals are triggered directly with the Power Automate infrastructure and do not require a flow with an approvals action. Users see all of their approvals in the hub, including the approvals that have been completed. Approvals show up across all of a user's systems, including Power Automate, SharePoint, and Microsoft Dynamics 365: What you need to do to prepare: The Approvals app is on by default if your tenant has enabled Microsoft Power Automate. As an admin, you can manage the Approvals app in the Teams admin center on the Approvals app page, including customizing which users can access the app with permission policies. Currently, all approvals are created in your organization's default environment. The Approvals app page in the Teams admin center: Learn more Approvals in Microsoft Teams - Power Automate | Microsoft Learn Manage the Approvals app in Microsoft Teams - Microsoft Teams | Microsoft Learn What is Approvals? - Microsoft Support 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. MC971032 — (Updated) Microsoft Teams: New recording policies for town halls and webinars Microsoft 365 Roadmap ID 473887 Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams: New admin policies in the Teams admin center and Microsoft PowerShell that govern the recording behavior for town halls and webinars. Before this rollout, the same policies control the recording behavior for town halls, webinars, and meetings. After this rollout, separate recording policies for town halls and webinars will be available to more finely control event behavior. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early April 2025 (previously early March) and expect to complete by mid-April 2025 (previously mid-March). How this will affect your organization: This change will be available by default. What you need to do to prepare: Before the rollout, we encourage you to use PowerShell commands to update the default values of the recording policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values. Examples of PowerShell commands to set the town hall or webinar recording policy: Set-CsTeamsEventsPolicy -Identity Global -RecordingForTownhall Enabled Set-CsTeamsEventsPolicy -Identity Global -RecordingForWebinar Enabled 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: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn MC971031 — (Updated) Microsoft Teams: New transcription policies for town halls and webinars Microsoft 365 Roadmap ID 473886 Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. Before this rollout, for a Microsoft Teams town hall or webinar, the transcription behavior respects the current Teams meeting transcription policies. After this rollout, new transcription policies will be available for town halls and webinars to allow finer control over transcriptions. The policies may be changed in the Teams admin center or with Microsoft PowerShell commands. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early April 2025 (previously early March) and expect to complete by mid-April 2025 (previously mid-March). How this will affect your organization: These new transcription policies for webinars and town halls will determine whether transcription is allowed for a town hall or webinar. Town halls and webinars will no longer respect the Teams Meeting transcription policies. The new policies will be available by default for admins to configure. What you need to do to prepare: Before the rollout, we encourage you to use PowerShell commands to update the default values of the transcription policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values. Examples of PowerShell commands to set the town hall or webinar policy: Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForTownhall Enabled Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForWebinar Enabled 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: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn MC960811 — (Updated) Microsoft Teams: Enhanced captions for Teams Rooms on Windows Microsoft 365 Roadmap ID 423089 Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that captions will soon support additional languages and translation capabilities. This enhancement aims to improve meeting accessibility and inclusivity for non-English speaking users using Teams Rooms on Windows. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). General Availability (GCC High): We will begin rolling out mid-May 2025 (previously mid-April) and expect to complete by late May 2025 (previously late April). General Availability (DoD): We will begin rolling out early June 2025 (previously early May) and expect to complete by mid-June 2025 (previously mid-May). How this will affect your organization: Before the rollout: Captions in Teams Rooms on Windows only support the English language, which limits usability for non-English speaking users as the captions will result in gibberish if the actual spoken language in the meeting is non-English. There is also no way for admins to set default caption settings. After the rollout Additional languages: Users can select from a list of supported languages for captions, ensuring that captions are accurate and meaningful for non-English speakers. Users can change the meeting spoken language directly from Teams Rooms devices by selecting More > Captions > Meeting spoken language. Real-time translation: Users can translate the meeting's spoken language if the room account has a Teams Rooms Pro license or if the meeting organizer has a Teams Premium license, allowing for real-time translation of captions. Users can translate captions by selecting More > Captions > Translation language. Caption settings for Microsoft Teams Rooms on Windows: Admin controls: For room accounts with Teams Rooms Pro license, admins can change system defaults, turn on captions by default for calls and meetings, and turn off filtering of profanity in captions and transcripts as necessary with these XML settings: <CaptionsDefault>true</CaptionsDefault> <FilterProfaneWords>false</FilterProfaneWords> As an admin, you can allow or prevent users (including room accounts) from having access to this feature by configuring calling and meeting policies in the Teams admin center. Learn more: Enable call captions - Microsoft Teams | Microsoft Learn and Manage live captions - Microsoft Teams | Microsoft Learn. This feature is available by default. What you need to do to prepare: After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and settings, 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. MC960809 — (Updated) Microsoft Teams: Live transcription for Teams Rooms on Windows Microsoft 365 Roadmap ID 423088 Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that users can soon start and stop transcription as well as view the meeting transcript directly from Teams Rooms on Windows devices. This feature requires a Teams Rooms Pro license. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). February) General Availability (GCC High): We will begin rolling out mid-May (previously mid-April). and expect to complete by late May 2025 (previously late April). General Availability (DoD): We will begin rolling out early June 2025 (previously early May) and expect to complete by late June 2025 (previously mid-May). How this will affect your organization: Before the rollout: When joining a meeting on Teams Rooms on Windows, users must also join the meeting on a companion device to start transcription. Also, even when transcription has been started, users can't view the transcript from the front of room display. After the rollout: Users can select More > Record and transcribe > Start transcription or Stop transcription directly from the Teams Rooms on Windows device. Start/stop transcription is supported in any meeting where a participant belongs to the same tenant as the organizer. When users transcribe a Meet now or Whiteboard session initiated from a Teams Rooms on Windows device, users must ensure that they invite themselves to the meeting so that they can access the transcript after the meeting through the meeting chat on their Teams desktop or mobile app. After transcription is started, users can show/hide the transcript panel on the front of room display in any meeting layout: Select More> Record and transcribe > toggle On/Off Show transcript. Select View> Front row > open the left/right panel dropdown > select/unselect Transcript. Users can also set the meeting spoken language, translate the transcript, and choose to show the original language and translated language side by side, ensuring accurate and meaningful transcription. Live transcription settings in Microsoft Teams Rooms on Windows: 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 transcribing meetings with a policy in the Teams admin center. Learn more: Manage transcription for Teams meetings | Microsoft Learn. NOTE: Both the meeting organizer and the transcription initiator (room account) need to have permissions to transcribe the meeting. If the meeting organizer uses Meeting options to remove the room account's permissions, the start/stop transcription button will not be available. For room accounts with a Teams Rooms Pro license, you have the option to turn off the filtering of profanity in transcripts using this XML setting: <FilterProfaneWords>false</FilterProfaneWords> Start/stop transcription is not supported in these scenarios: Teams calls including P2P, group, and PSTN calls External and cross-tenant Teams meetings and calls Third-party meetings and calls including Direct Guest Join and SIP What you need to do to prepare: After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and setting, 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. MC956699 — (Updated) Microsoft Teams: Forward messages with app cards Microsoft 365 Roadmap ID 469506 Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience. We are introducing the ability to forward app cards. With the addition of app card forwarding, users now have a new way to share app cards across chats. To forward a message containing an app card, simply navigate to the More Actions menu of any message containing an app card and select forward. From here, the forward message dialog will populate, which provides users with a preview of the message being forwarded, including the app card. Please note: Forwarding of bot cards is excluded from this release. When this will happen: Targeted Release: We will begin rolling out mid-February 2025 (previously early February) and expect to complete by late February 2025 (previously mid-February). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously late January) and expect to complete by early March 2025 (previously early February). How this will affect your organization: Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained app cards. With this improvement, this restriction does not exist. What you need to do to prepare: Users must have the latest Microsoft Teams build to receive these updates. You may want to notify your users about this change and update any relevant documentation as appropriate. MC952888 — (Updated) Microsoft Teams: Pop out Chat, Copilot, and Notes panes in meetings Microsoft 365 Roadmap ID 421607 Updated February 24, 2025: The Worldwide release has been temporarily rolled back. We will update this Message center post with new timelines once available. The Targeted release remains enabled. Coming soon: Users will be able to pop out the side panes for Notes, Chat, and Microsoft Copilot panes in Microsoft Teams meetings Note: The Copilot pane is only available in Worldwide environments with a Microsoft 365 Copilot license. When this will happen: Targeted Release: We will begin rolling out mid-January 2025 and expect to complete by early February 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will communicate via Message center when ready to proceed. How this will affect your organization: After the rollout, users will see a pop-out icon at the top of their Notes, Chat, and Copilot side panes in Teams meetings. This change will be on by default. When users select the icon, the pane will pop out into a separate window that the user can resize and drag to their desired position, based on their screen setup and their productivity goals for the meeting. Users can view multiple meeting features at the same time, so they don’t miss the chat while they are monitoring meeting 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. Please notify your users about this change and update any relevant training documentation. MC949966 — (Updated) Microsoft Teams Rooms on Windows: Join and present in Microsoft events Microsoft 365 Roadmap ID 381425 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Microsoft Teams Rooms on Windows devices will be able to join Microsoft events (webinars, town halls, structured meetings) when invited as presenters. You can present directly from the Teams Room, with features like green room access and stage control for organizers and presenters supported on both single and dual screens. Available for tenants with Teams Rooms Pro licenses. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out late February (previously mid-February) and expect to complete by late March 2025 (previously late February) How this will affect your organization: This feature will be available by default. Presenters in the green room and on stage right before starting the meeting in the room's console: Learn more: Overview of meetings, webinars, and town halls - 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. 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. MC948994 — (Updated) Microsoft Teams: Collaborative Notes support for GCC High and DoD environments Microsoft 365 Roadmap ID 418119 Updated February 19, 2025: We have updated the rollout timeline below. Thank you for your patience. Teams Collaborative Notes, powered by Loop, is now available for Microsoft 365 GCC High and DoD environments across desktop and web experiences. Notes are Loop components in Teams meetings and chats that allow end users to co-create and collaborate on their meeting agenda, notes, and action items. Since Notes are Loop components, they stay in sync across all the places they have been shared. Assigned tasks automatically sync with To Do and Planner. When this will happen: General Availability (GCC High, DoD): We will begin rolling out in early April 2025 (previously late March) and expect to complete by late May 2025 (previously late April). How this will affect your organization: Users within your tenant will see a Notes button during meetings that invokes these new capabilities. The meeting notes will be shown on the right pane of the meeting window with the ability to open them in the browser for more room or on a second monitor. Participants can collaborate in real time, create an agenda, take notes, and add tasks. When participants are assigned a task in the meeting, they will also receive an email notification, and it will be synced with the Planner and To Do apps. Meeting organizers and participants will also see an option to add Collaborative Notes before meetings to prepare by adding agendas or other materials in one place. The meeting organizer can also choose to hide the meeting notes prior to the meeting through the Teams scheduling form. If Collaborative Notes are not created ahead of the meeting in the scheduling form, users can create the file by opening the Notes pane in the meeting. After the meeting, Collaborative Notes will remain accessible for all participants on the Teams calendar meeting details page and through the meeting recap. The experience is a Loop component, so they can be copied easily out of the meeting and into chats, group chats, emails, and other documents. This makes prepping and follow-up even more seamless. Clicking on the meeting note title or the icon in the upper left corner of the note launches the Loop app in browser. If the meeting is part of a series, meeting notes from previous instances can be conveniently found in the Loop app as well. This 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. Public documentation is available here: Take meeting notes in Microsoft Teams. Note: The new Collaborative Notes file will generate a Company Shareable Link (CSL), unless you have set People Specific Link (PSL) as the default. If PSL is the default, only users who were sent the original meeting invite will be able to access the notes. Users who were forwarded the meeting or nudged into a meeting will need to request access to the notes. You can manage this feature via SharePoint PowerShell with: Set-SPOTenant -IsCollabMeetingNotesFluidEnabled (boolean) You can read more about admin controls here: Manage Loop experiences (Loop app and Loop components) in SharePoint. Known limitations: Collaborative Notes are currently supported for scheduled meetings and channel meetings and are not available for instant meetings or Teams calls. MC946818 — (Updated) Microsoft Teams: Updates to Gallery in Teams Rooms on Windows Microsoft 365 Roadmap ID 468277 Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Windows, the updated Gallery view introduces these changes to enhance your meeting experience: All participants will appear in consistent tile sizes By default, video participants have priority and appear first on the meeting stage by default (audio participants appear on the side or bottom of the screen) Ability to disable priority on video participants to create a mix of audio participants and video participants in the Gallery Optimized view of up to 25 participants on a single display and up to 50 participants on dual displays Preview video is part of the Gallery, appearing next to the rest of the participants Ability to hide the preview video across all layouts When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). How this will affect your organization: The updated Galleryprovides a unified meeting experience across both Teams Rooms and desktop. A more consistent and predictable layout can drive meeting efficiency and visibility for remote participants in hybrid meeting scenarios. In 1:1 meetings, the preview video will be positioned at the bottom right, overlapping the other participant. In group meetings, the preview video will be on the last available tile in the Gallery, next to the rest of the participants. Admins can use two new settings to adjust the default view: Prioritize vide0;< PrioritizeVideoParticipantsGallery> – Default value is True. The default experience will show video participants on the main stage with audio participants on the side or bottom rail. If you would like to display all audio and video participants mixed in the Gallery, change the value to False. Hide me <HideMeForAllLayout> – Default value is False. If you would like to hide preview video across all layouts in Teams Rooms on Windows, change the value to True. In-room users can adjust these settings on the console during a meeting, if desired. Lastly, when another Teams Room joins the meeting, the video of the room automatically enlarges if there are more than two in-room users, providing a clearer view and better connection, and so users can focus on the person speaking. These changes will be available by default. What you need to do to prepare: Please notify your users about this change and update any training documentation, as appropriate. 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 Remotely manage Microsoft Teams Rooms device settings - Microsoft Teams | Microsoft Learn(will be updated before rollout) Microsoft Teams Rooms (Windows) - Microsoft Support(will be updated before rollout) MC939927 — (Updated) Microsoft Teams Premium: Decorate your background Microsoft 365 Roadmap ID 419811 Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. We will not release this feature to DoD at this moment. We are sorry for any inconvenience. We will share DoD timeline when available. Microsoft Teams Premium users will be able to use the "Decorate your background" generative background effect in the GCC, GCC High, and DoD environments, leveraging gen-AI to augment real-life surroundings. It creates a personalized atmosphere for video calls. When this will happen: General Availability (GCC): We will begin rolling out in early June 2025 (previously early March) and expect to complete rollout by mid-June 2025 (previously late March). General Availability (GCC High): We will begin rolling out in mid-June 2025 (previously mid-March) and expect to complete rollout by late June 2025 (previously late March). General Availability (DoD): We will communicate via Message center when we are ready to proceed. How this will affect your organization: “Decorate your background” transforms meeting backgrounds by blending with a user’s real-life surrounding, creating a personalized atmosphere for video calls. It is available to Teams Premium users, and it is supported on Microsoft Windows and MacOS client now. There is not admin policy to disable it. Users can access this feature in the following ways: Before a meeting starts on the pre-join screen, select Effects and Avatars> Video effects > Decorate button. This will allow you to start generating new backgrounds. During a meeting, select an animated background by clicking video flyout > More Video Effects and Setting > Decorate. 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. MC939924 — (Uploaded) Microsoft Teams: Start Whiteboard from Teams Rooms on Android in GCC and GCC-H Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. Microsoft Whiteboard storage is moving from Azure to OneDrive for Business to deliver greater compliance, governance, and retention capabilities. This improvement allows us to offer the Start Whiteboard feature in additional cloud environments (GCC and GCC High) that support OneDrive for Business. The enhanced Whiteboard experience, includes: Features unique to whiteboards stored in OneDrive, such as Follow me, Commenting, Collaborative cursor, and more. Improved performance on whiteboards now stored in OneDrive. Improved compliance and security associated with whiteboard being stored in OneDrive. When this will happen: General Availability (GCC, GCC High): We will begin rolling out late January 2025 (previously November) and expect to complete rollout by late February 2025 (previously late January). How this will affect your organization: Outside of a meeting Whenever you want to brainstorm in the office, just start whiteboarding using the new Whiteboard button on the home screen. With one touch, you can quickly launch Microsoft Whiteboard and start collaborating outside of a Teams meeting. Since a resource account does not have OneDrive, it will launch a temporary whiteboard. The Save button will guide you to invite your work account to a meeting with your Teams Room so that the temporary whiteboard can be saved in your OneDrive for Business. You will see a saving failure error if you invite a non-room participant who does not have OneDrive. Switch from local to online collaboration by selecting Start meeting on the local whiteboard screen. This initiates an ad-hoc meeting and presents the temporary whiteboard. From there, you can add participants into the meeting and contribute across the same whiteboard in real time. The temporary whiteboard will be saved in OneDrive for the first non-room user who joins the meeting. In a meeting During a meeting, click the Share button and select Microsoft Whiteboard to initiate a whiteboard. The whiteboard will be shared in the meeting and saved in OneDrive for Business for one of the non-room participants at the meeting automatically. What you need to do to prepare: Please verify that your tenant setting meets the requirements described in this documentation: Manage sharing for Microsoft Whiteboard - Microsoft Whiteboard | Microsoft Learn. The Start Whiteboard feature will be turned on by default. Your Home screen (outside of the meeting) will show the Whiteboard button, and the in-meeting share tray will show the whiteboard option. If you want to disable the Start Whiteboard feature, please turn it off via the admin setting on your device or apply the configuration profile in Teams admin center using the 'Allow room to use Microsoft Whiteboard' setting under the 'Meeting settings' section. Even if the Start Whiteboard feature is disabled for your Teams Rooms on Android device, you can see a whiteboard that remote participants share in a meeting. MC920179 — (Updated) Microsoft Teams: The new streamlined Chat and Channels experience Microsoft 365 Roadmap ID 415249 Updated March 3, 2025: Thank you for your engagement with the new chat and channels experience in Teams. The GA rollout begins late March 2025 in a phased rollout and is expected to be completed by end of April 2025. We're making the following product improvements from Public Preview and Targeted Release based on user feedback. Users who haven't onboarded yet to the new experience will havea simplified onboarding flow in Teams with fewer steps. 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 for a user, a Get started screen is displayed. Users will have the option to defer the new experience up to three times over the course of approximately three days. About a week after the new experience is available for a user, they will be presented with a final Get started screenand transition to the new experience. For users new to the experience on iOS, iPad, and Android,message previews will be on by default. For users new to the experience on Windows, Mac, and Web, message previews will be off by default. A quick navigation bar for teams and channelsis available in Teams for Windows, Mac, and Web, at the bottom of the combined Chat view. Clicking on the bar will scroll the view to the teams and channels section for quick navigation. The bar displays in bold when there are unread messages in channels, or with indicators like "@" for unread @mentions in channels. Note: These updates will roll out to users in Public Preview and Targeted Release ahead of GA. To help prepare organizations for the new features, product guides for admins and users are already available on the adoption web page https://adoption.microsoft.com/microsoft-teams/new-chat-and-channels-experience. Adoption content has been updated to reflect the above product improvements here. 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 to Microsoft 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: 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 March 2025 (previously late January) and expect to complete by end of April 2025 (previously early April). General Availability (GCC): We will begin rolling out mid-May 2025 (previously mid-June) and expect to complete by late May 2025 (previously late June). General Availability (GCC High, DoD): We will begin rolling out mid-June 2025 (previously mid-April) and expect to complete by late June 2025 (previously late April). How this will affect your organization: The new experience brings chat, teams, and channels into one place, in Chat, so users can easily navigate between all conversations without switching between contexts. Users start in the combined Chat view but can opt to keep chat separate from teams and channels like before. In the Chat view, users will see these sections (in order): Favorites containing any previously pinned chats and channels Chats sorted by most recent Teams and channels, organized in same order as in the Teams view Also, users can create custom sections to organize projects and topics that can include individual, group, and meeting chats, as well as channels. New filters for Unread, Chat, Channels, Meetings and 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. Use /go to: Quickly navigate to your frequently used conversation across your chat and channels with a new keyboard shortcut Ctrl+G (Cmd+G on Mac). Customizing the experience Users can tailor their chat and channels experience in Teams Settings. Users can choose to keep chat, teams, and channels combined in Chat (default) or switch to separate Chat and Teams views. In the combined Chat view on Windows, Mac, and Web, message previews are off by default to simplify the list. Users can turn on message previews in Settings. When using the separate Chat and Teams views, 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. 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. For admins who opt in to emails for recommended Microsoft 365 training, an email for users will summarize the update when released. MC912707 — (Updated) Microsoft Teams: New policy for voice and face enrollment will default to "On" (configure now) Microsoft 365 Roadmap ID 413708 Updated February 6, 2025: Please verify that all previously set values remain unchanged and as intended. A new csTeamsAIPolicy policy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-March 2025 (previously mid-February) 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 enrollment will 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: The new Microsoft PowerShell cmdlets are available now for admins to configure, to ensure a smooth transition. 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-March 2025 (previously mid-February) and is expected to be fully in effect by late March 2025 (previously late February). How this will affect your organization: Before this rollout, the current policy csTeamsMeetingPolicy has 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 new csTeamsAIPolicy will replace the existing enrollment setting in csTeamsMeetingPolicy. The new csTeamsAIPolicy has two settings, EnrollFace and EnrollVoice, that will be set to Enabled by 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-March 2025 (previously mid-January). 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 If your organization prefers to disable voice and face enrollments, review and update your settings before mid-March 2025 (previously mid-February). Important: The EnrollUserOverride setting can be assigned globally, directly to users, or to groups in PowerShell. Admins must ensure that changes are applied consistently across all these locations to avoid unintended configurations. MC908117 — (Updated) Microsoft Teams: Swap screens on Teams Rooms on Android Microsoft 365 Roadmap ID 415243 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. 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-March 025 (previously mid-February). 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 NOTE: If you are deploying Teams Rooms on Android devices with dual displays, be aware that dual display mode must be explicitly enabled in the configuration profile. By default, the dual display setting is OFF, which means that using an existing configuration profile (designed for single-display devices by default) may inadvertently disable dual display mode for your existing dual display rooms. To avoid this, you must create and maintain a separate configuration profile for any devices that require dual display support. 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. MC907108 — (Updated) Microsoft Teams: Admin email support for "Report a problem" on Teams Rooms on Android Microsoft 365 Roadmap ID 415247 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Android: As an admin, you can configure an email address for receiving issues submitted by users through the Report a problem feature 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. 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-March 2025 (previously mid-February). 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, the Report a problem option on Teams Rooms on Android devices will be enabled, and any feedback submitted by room users using Report a problem will 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. Users can access Report a problem from the Help button on the home screen or the More button in meetings. Report a problem can 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, see Collect 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 — (Updated) Microsoft Teams: Net Promoter Score survey on Teams Rooms on Android Microsoft 365 Roadmap ID 415245 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. 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. 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-March 2025 (previously mid-February). 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 at Manage 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. MC898391 — (Updated) Microsoft Teams: Performance improvements for meetings in Edge web browser for guests Microsoft 365 Roadmap ID 401117 Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. Anonymous users (guests) who join Microsoft Teams meetings in the Microsoft Edge for Business web browser will soon experience performance improvements. They will be able to join meetings faster. 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-November 2024 and expect to complete by late-November 2024. General Availability (GCC, GCC High, and DoD): We will begin rolling out early January 2025 and expect to complete by late March 2025 (previously late January). How this will affect your organization: Before this rollout, anonymous users (guests) may experience longer wait times when attempting to join a Teams meeting. After this rollout, anonymous users (guests) will be able to join meetings faster, even on low-end devices. What you need to do to prepare: This rollout will happen automatically with no admin action required. MC894581 — (Updated) Microsoft Teams: Performance improvements for meetings in Chrome web browser for guests Microsoft 365 Roadmap ID 401116 Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. Anonymous users (guests) who join Microsoft Teams meetings in the Chrome web browser will soon experience performance improvements. When this will happen: Targeted Release: We will begin rolling out early November and expect to complete by mid-November 2024. General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by late-November 2024. General Availability (GCC, GCC High and DoD): We will begin rolling out early January 2025 and expect to complete by late March 2025 (previously late January). How this will affect your organization: Before this rollout, anonymous users (guests) may experience longer wait times when attempting to join a Teams meeting. After this rollout, anonymous users (guests) will be able to join meetings faster, even on low-end devices. What you need to do to prepare: You may want to update your internal documentation to inform your users about this improvement. However, because the improvement is for external users and does not change the look of Teams, you can skip this step./p> MC889534 — (Updated) Microsoft Teams: Embed support for Teams town hall Microsoft 365 Roadmap ID 401120 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. As a part of Team’s ongoing effort to enable our customers to create, manage, and run large scale events, end users can now embed Teams town hall in sites they manage. This capability allows town hall attendees to watch the event instance within a particular website. Embed for town hall introduces embeddable support for town hall engagement features on release. Attendees will have the same engagement feature access within the embed player as they do in client such as Q&A, Captions, Reactions and more. To implement embed for town hall, organizers can access their town hall events unique embed code from the town hall scheduling template upon publish. Organizers can then take that code and inject it to their SharePoint or Microsoft 365 site as desired. On event start, attendees will be able to view and engage with the embed stream on the published site. When this will happen: Targeted Release: We will begin rolling out early November 2024 (previously early October) and expect to complete by mid-November 2024 (previously mid-October). General Availability (Worldwide, GCC): We will begin rolling out early December 2024 (previously late October) and expect to complete by mid-March 2025 (previously mid-February). How this will affect your organization: Users will be able to copy embed code directly from town hall scheduling form on event publish. After the embeddable code is placed in the website, the town hall player will be accessible to attendees who have access to the URL. Note: Attendee access to the embedded video player is driven by the town hall event access. What you need to do to prepare: Organizers with SharePoint or Microsoft 365 site who want to utilize embed support for town hall can begin implementing the embeddable code upon release. MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar Microsoft 365 Roadmap ID 409226 Updated February 21, 2025: 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 March 2025 (previously late January). 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 under Event access may 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 to None. 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. MC809602 — (Updated) Microsoft Teams: New skin tone settings and reactions Microsoft 365 Roadmap ID 323766 Updated February 21, 2025: 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 app Settings > Appearance and accessibility menu 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 late December 2024. General availability (GCC High, DoD): We will begin rolling out mid-November 2024 (previously mid-November) and expect to complete by late March 2025 (previously late January). 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. MC804771 — (Updated) Microsoft Teams: Hiding inactive channels Microsoft 365 Roadmap ID 325780 Updated February 14, 2025: Based on Admin feedback, we are updating the behavior for automated hiding of inactive channels to be opt-in (suggestions) only. With this update, Teams will offer users suggestions on channels that are inactive, and the user is prompted to review their inactive channels and hide them only if they choose. The settings are also updated to reflect this opt-in workflow. There are no changes to the on-demand hiding process. This feature is enabled till Targeted Release, and we will roll out to General Availability later this year. In the interim, we are disabling the current generally available version of the feature which requires users to opt-out as well as the settings, for all users. Please note that all users in the public or general ring will not see the setting or have any of their channels hidden automatically. We will re-introduce the updated feature later this year. Note: Users with EDU licenses assigned will not receive this change. Microsoft Teams will detect and hide inactive channels users have not interacted with recently. Users can choose to have Teams run this automatically as well as initiate the hiding process on demand when needed. They can review the list of channels and choose none, some or all of the inactive channels to be hidden. Users can opt out of automated hiding anytime from Teams Settings. This message applies to Microsoft Teams for Desktop, web, and Mac. When this will happen: Targeted Release: We will begin rolling out mid-July 2024 and expect to complete by late July 2024. General Availability (Worldwide): We will begin rolling out mid-November 2024 (previously mid-August) and expect to complete by mid-January 2025 (previously mid-September) General Availability (GCC): We will begin rolling out early February 2025 (previously late September) and expect to complete by mid-February 2025 (previously early October). General Availability (GCC High): We will begin rolling out early February 2025 (previously early October) and expect to complete by mid-February 2025 (previously mid-October). General Availability (DoD): We will begin rolling out mid-February 2025 (previously late October) and expect to complete by late February 2025 (previously late October). How this will affect your organization: Before this rollout: Users had to manually manage their relevant channels list by hiding inactive and irrelevant channels. After this rollout: Manage preferences for automated hiding via Teams Settings If users prefer to manage channels manually, they can opt out of the auto-hiding process. Simply go to Teams settings, select General, and toggle off "Hide Inactive Channels." Hide inactive channels on demand when needed Users can manually view which channels are inactive and choose to hide some or all of them whenever you need. This can be done from Settings, under General, by clicking the "Hide Now" button. Note that this action can be performed once every 24 hours. Automated hiding of inactive channels With this, Teams will hide channels that have been inactive for the user. Inactive channels are identified based on the following criteria: if the user has not been active in the channel in the last 120 days – meaning there is no new messaging in the channel that the user has read or reacted to – the channel is considered inactive. Once the inactive channels are identified, the user is notified with the coach mark message, "We're hiding some inactive channels for you." The user can select View changes to see the details. The user can keep the channels hidden or show them again. If a user has less than or equal to 25 shown channels, no channels will be hidden for that user. What you need to do to prepare: Admins need to be aware of this feature, but no additional action is needed. The feature will roll out starting in November 2024. Users will first see their settings enabled to manage their preferences for automated hiding; additional to the ability to manually hide inactive channels. Users will start to see the automated hiding of inactive channels, a few weeks after the feature has rolled out. MC781595 — (Updated) Microsoft Teams: Tenant-wide policy for permission to download meeting transcription Microsoft 365 Roadmap ID 332800 Updated February 21, 2025: We have updated the rollout timeline below. 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 complete by late March 2025 (previously late January). 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.) MC772556 — (Updated) Microsoft Teams: Shorter meeting URLs Microsoft 365 Roadmap ID 381953 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Please note that information about meeting link expiry changes related to this rollout has been added. We are reducing the length of Microsoft Teams meeting URLs for easier sharing. This rollout applies to all Microsoft Teams platforms (Teams for iOS, Android, Mac, Teams devices, desktop, and web). When this will happen: Targeted Release: We will begin rolling out mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). Only Meet Now use cases (except Meet Now in chats and channels) will be affected in this timeframe. There will be no impact on the scheduled meetings in this phase. General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 (previously mid-April) and expect to complete by late May 2025 (previously late April). Only Meet Now use cases (except Meet Now in chats and channels) will be affected in this timeframe. There will be no impact on the scheduled meetings in this phase. Rollout for scheduled meetings and channel Meet Now will be started in early July 2025 and expected to be completed by mid-July 2025. General Availability (GCC High, DoD): We will begin rolling out early August 2025 (previously early June) and expect to complete by mid-August 2025 (previously late June). How this will affect your organization: The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode> To make meeting URL shorter, we are removing several parameters such as tenant ID, conversation ID etc. This change serves two main goals: 1) improving usability of URL during sharing and 2) making the URL more secure and less susceptible to malicious attacks. Here are some details about how meeting links work and when they expire: In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire. Every meeting link expires in 60 days after the scheduled event or in 8 hours, if it was created as Meet Now. Learn more about expiration timelines for different types of meetings. With the Short Meeting URL release, expiration limit will be applied to all newly created links. Once the change to Short Meeting URL is released, all newly created meetings will expire as described in the documentation: 60 days after meeting ends for scheduled meetings and 8 hours after creation for Meet Now. Once this expiry period is over, in case someone clicks the link (e.g. outside of Teams app OR in the meeting details inside Teams calendar section), they will be unable to join the meeting. Note: Old links created before short meeting URL release will continue working as it previously was (user will be able to join even after the documented expiry limits). The reason why we are making this change is simple: security is our topmost priority. Maintaining a high security level is essential to protect sensitive data, prevent financial losses, ensure business continuity, and meet compliance and legal obligations. It is a critical aspect of modern digital life and business operations. This adjustment is designed to enhance the security of Teams meeting links, thereby better safeguarding the customer tenant. We want to be on par with modern security standards, that’s why the new behavior is a step in the right direction that we must take. It’s not possible to keep the current behavior. If you think it breaks some of your business processes, please leave comment to the MC post and describe your case there. Recommendations in case the meeting link has expired: For meeting organizer: We recommend scheduling a new meeting. If the meeting organizer got removed from the tenant someone else should reschedule their meetings from scratch. For participant: Please reach out to the meeting organizer and ask them to reschedule the meeting or send you an updated link. What you need to do to prepare: You may want to check if you have any integrations that use parameters from URL. After the rollout, the URL will only contain the meeting ID. Parameters such as tenant ID, organizer ID, conversation ID and message ID will not be in the URL. You may inform meeting organizers from your tenant who use expired meeting links, or you may want to make a tenant-wide announcement about this change. 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. MC750668 — (Updated) Microsoft Teams: Access Workflows from the three-dot menu on shared file Microsoft 365 Roadmap ID 381643 Updated February 28, 2025: 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-March 2025 (previously mid-February). 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 choose Workflows. From Workflows, 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 selecting See more workflows at 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. MC726122 — (Updated) Microsoft Teams: View, download, and delete Microsoft OneDrive transcript files Updated February 21, 2025: 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 March 2025 (previously late January). 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 this documentation. 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. MC718553 — (Updated) Microsoft Teams: Change background while recording on phone Microsoft 365 Roadmap ID 380852 Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. Users can now record themselves anywhere and share it with coworkers in the Microsoft Teams chat or channel without worrying about the background. Users can now change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on iOS devices. When this will happen: General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out early May 2024 (previously late March) and expect to complete by late March 2025 (previously late January). How this will affect your organization: Users will get an option to change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on an iOS device. To use this feature: Press and hold the camera icon next to the Compose box and then tap the blur icon to the right of the shutter button. You can then choose either an image to replace the background or choose to mildly or heavily blur your background. 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. MC709270 — (Updated) Mute with Windows Taskbar available in the new Microsoft Teams on Windows Microsoft 365 Roadmap ID 191528 Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. The Muting Teams with Windows Taskbar is now available. This feature, available in the new Teams experience on Windows, enables you to mute and unmute your audio by clicking the mic icon in Windows taskbar. To control your call mic from the taskbar, do the following: Select the mic icon on your taskbar or press Windows logo key + Alt + K to mute or unmute your microphone while using a calling app. -OR- Click the volume icon in the hardware indicator for volume in Windows taskbar. 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). Worldwide, GCC, GCC High & DoD: We will begin rolling out mid-June 2024 (previously early June) and expect to complete by complete by late March 2025 (previously late January). How this will affect your organization: This enables a feature previously available in older version of Teams on Windows. What you need to do to prepare: To prepare, distribute updates on this rollout with your organization if applicable for your users. MC705760 — (Updated) Teams: Latest meeting experiences with performance improvements on web for Safari and Firefox (for guests) Microsoft 365 Roadmap ID 329253 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. The latest Teams meeting experiences will be available for Teams on the web in Safari and Firefox browsers - including performance improvements, refreshed pre-join, updated meeting stage, and the updated meeting toolbar. (for anonymous join only) When this will happen: Worldwide: We will begin rolling out early September 2024 (previously mid-August) and expect to complete by early October 2024 (previously late August). GCC, GCC High and DoD: We will begin rolling out mid-October 2024 (previously mid-September) and expect to complete by mid-March 2025 (previously mid-February). How this will affect your organization: We make constant steps to improve Teams performance irrespective of the platform – this time we are making the experience of Teams meetings on web (in Safari and Firefox browsers) better for anonymous users (guests). That’s crucial because it improves external collaboration. For example, if participants from your tenant would like to have meetings with non-Teams users (who are often joining as guests) it’ll become simpler as guests joining meeting from Safari/Firefox web browsers won’t have to wait significant amount of time for the meeting experience to load. You may also notice that currently meeting UI in Chrome and Safari/Firefox is different, but with this update it won’t be a case anymore and you’ll enjoy all the benefits of modern UI (such as meeting toolbar on top of the screen, etc). What you need to do to prepare: You may want to update your internal documentation to inform your users about this improvement. MC688109 — (Updated) Co-organizer experience updates in Teams Webinars and Townhalls Microsoft 365 Roadmap ID 168524 Updated February 12, 2025: 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 mid-January 2025 (previously early January) 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 late February 2025 (previously mid-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. Purview MC1011148 — Microsoft Purview | Insider Risk Management: Increasing policy template limits Microsoft 365 Roadmap ID 477364 Coming soon to Microsoft Purview | Insider Risk Management: We will increase policy creation limits from 20 policies per template to a maximum of 100 overall active policies. After the rollout, for example, an organization may have 50 data leak policy templates because the limit will now apply to all active policies instead of applying to each policy template. When this will happen: Public Preview: We will begin rolling out mid-March 2025 and expect to complete by mid-April 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early July 2025 and expect to complete by mid-August 2025. How this will affect your organization: This change will be on by default. What you need to do to prepare: No impact to your organization. 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. Learn about policy template limits in Learn about insider risk management policy templates | Microsoft Learn (will be updated before rollout) MC1004410 — Microsoft Purview | Endpoint Data Loss Prevention - Classification improvements on file read access in macOS devices Microsoft 365 Roadmap ID 478930 Data classification on files stored in macOS devices will be triggered automatically when handing files on read access to improve classification operations. When this will happen: General Availability (GCC, GCCH, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. How this will affect your organization: Files that are stored locally on macOS devices will improve data classification whenever files are accessed and read. This system-level change is automatically happening for those macOS devices that have endpoint Data Loss Prevention (DLP) deployed and will not be visible to the end user. For more information about items on targeted devices being automatically reevaluated the next time they're accessed or modified, see Best practice for endpoint DLP policies. 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. MC999442 — Microsoft Purview | Data Lifecycle Management: Retention based on “last accessed” for OneDrive and SharePoint files Microsoft 365 Roadmap ID 472030 Coming soon for Microsoft Purview | Data Lifecycle Management: Admins will be able to apply a retention policy or retention label in Microsoft OneDrive and Microsoft SharePoint for files that have not been accessed by anyone in your organization for a specified period of time. This message applies to retention for Microsoft 365 file types. We will support other file types (non-Microsoft 365) in a future rollout. When this will happen: Public Preview: We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. How this will affect your organization: This feature will help delete obsolete data, which will improve the quality and relevance of Microsoft 365 Copilot responses. This feature will be available by default. After the rollout, admins can use the retention control When items were last accessed when configuring labels and policies. Retention settings page in Purview with the new “last accessed” option for retention policies: 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. Before rollout, we will update this post with new documentation. MC973511 — (Updated) Microsoft Purview | Data Lifecycle Management: Separate retention policies for Copilot and AI apps Microsoft 365 Roadmap ID 470025 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. This new feature provides the capability for admins to configure separate retention policies for various Microsoft 365 Copilot and AI apps. As a result, admins will have the option to configure policies that can delete Copilot and Generative AI interactions faster. When this will happen: General Availability (Worldwide): We will begin rolling out late February 2025 (previously mid-February) and expect to complete by early March 2025 (previously late February). How this will affect your organization: Organizations will now have controls to configure different retention policies for Microsoft Teams Chat, Copilot, Copilot studio, and ChatGPT Enterprise. This feature is available by default. What you need to do to prepare: For more information, see Create and configure a retention policy. 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. MC971035 — Microsoft Purview | Data Lifecycle Management: New secure workflow to bypass legal holds and retention policies Microsoft 365 Roadmap ID 392838 Updated February 7, 2025: We have updated the rollout timeline below. Thank you for your patience. This new feature enables data governance administrators to expedite the permanent deletion of sensitive content from Microsoft Exchange mailboxes, overriding any existing retention settings or eDiscovery holds. This process may be required for security or privacy, such as after a data spillage incident or for compliance and regulatory requirements. When this will happen: Public Preview: We will begin rolling out late February 2025 (previously early February) and expect to complete by mid-March 2025 (previously mid-February). Worldwide: We will begin rolling out late March 2025 and expect to complete by mid-April 2025. How this will affect your organization: Priority Cleanup administrators can now set up a Priority Cleanup policy for Exchange to create exceptions to retention principles and e-Discovery holds for specific scenarios. Once administrators are within the Data Lifecycle Management (DLM) Solution on Microsoft Purview, they can visit the Priority Cleanup tab and follow the wizard to set-up this policy. Like auto-apply retention labels, Priority Cleanup supports policy simulation mode, so administrators can check the returned samples in case the policy configuration needs any fine-tuning before enabling the policy. Once set-up, because the deletion by a priority cleanup policy is irreversible and can override existing holds, the process requires multiple approvals, specific roles, and is audited. Thus, respective reviewers must be mandatorily added during policy creation to allow for disposition of items under a retention or e-Discovery hold. What you need to do to prepare: Because of the built-in safeguards, the feature itself is enabled by default at the tenant level. However, Priority Cleanup can be turned off on the Priority Cleanup settings page. If you can't create new Priority Cleanup policies, refer to your Data Lifecycle Management documentation for necessary roles and permissions requirements. A new role permission "Priority cleanup administrator" is now added to Purview role permissions to enable data governance administrators to use this feature. MC950890 — (Updated) Microsoft Purview | Data Security Posture Management for AI Microsoft 365 Roadmap ID 469509 Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. Generative AI (GAI) is being adopted at an unprecedented rate. AI fuels innovation and productivity but also poses risks – organizations are concerned about the risky AI use and sensitive data loss through AI apps. Microsoft Purview Data Security Posture Management for AI (DSPM for AI) is a central location in Microsoft Purview that helps organizations secure data in AI, including Microsoft AI applications such as Microsoft 365 Copilot and non-Microsoft AI applications. With the DSPM for AI capabilities in Purview, organizations can safely adopt AI without having to choose between productivity and protection. DSPM for AI also supports admin units and displaying AI policies that were created in Purview solutions. A version of DSPM for AI is available to additional licensing, specifically Microsoft 365 E3 and Microsoft 365 Copilot licenses. When this will happen: We will begin rolling out late February 2025 (previously late January) and expect to complete by late March 2025 (previously late February). How this will affect your organization: DSPM for AI also supports admin units and displaying AI policies that were created in Purview solutions. A version of DSPM for AI is available to additional licensing, specifically Microsoft 365 E3 and Microsoft 365 Copilot licenses. DSPM for AI use cases Viewing insights and analytics into AI activity in your organization. Using policies to protect data and prevent data loss in AI prompts Implementing compliance controls to apply optimal data handling and storing policies Microsoft Purview DSPM for AI will be in the Microsoft Purview portal and will consist of 5 tabs: Overview, Recommendations, Reports, Policies, and Activity explorer. Reports includes graphs for total interactions over time, sensitivity labels and sensitive information types found in AI interactions, user risk level, and more. Policies displays all policies that have been created by default or AI policies created in Purview solutions. Activity explorer shows events for AI interactions along with prompts and responses. This feature will be enabled 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. Get ready for this change by reviewing the admin documentation: Considerations for Data Security Posture Management for AI & data security and compliance protections for Copilot Microsoft Purview data security and compliance protections for generative AI apps MC937158 — (Updated) Microsoft Purview | Insider Risk Management: New scenario-based policy templates Microsoft 365 Roadmap ID 409966 Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Purview | Insider Risk Management: Two new preconfigured quick policy templates for Crown jewel protection and Email exfiltration. These templates are for admins who want to deploy scenario-specific policy templates with less configuration, to get started faster. The existing quick policies for Data leak and Data theft will continue to be available. You can find all four scenario-based quick policies in Insider Risk Management at Policies > Create Policies. Admins can expect additional turning after deploying these policies to meet individual alert volume needs. When this will happen: Public Preview: We will begin rolling out late November 2024 and expect to complete by mid-December 2024. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously early February) and expect to complete by late March 2025. How this will affect your organization: Sign in to Insider Risk Management with the admin role permissions Go to the Policiespage at https://purview.microsoft.com/insiderriskmgmt/policiespage Select Create policy Select Quick policies Select either the Crown jewel protectionpolicy or the Email exfiltration policy Configure policy as applicable (add users to scope, optional priority content, and so on) The new policies 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: The Quick Policies section in Create and manage insider risk management policies | Microsoft Learn MC920308 — (Updated) Microsoft Purview | Information Protection: Auto-labeling policies will support "Fingerprint based SIT" Microsoft 365 Roadmap ID 396173 Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Purview | Information Protection: Admins will be able to use auto-labeling policies to automatically label files and emails with Fingerprint 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-February 2025 (previously early February). How this will affect your organization: Before this rollout, admins are not able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT. After this rollout, you can configure Fingerprint based SIT using the condition Content contains sensitive information types. Files that match Fingerprint based SIT will show in simulation. Note: Contextual summary is not available for Fingerprint 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 MC911618 — (Updated) Microsoft Purview | Insider Risk Management: Multi-policy settings in Adaptive Protection Microsoft 365 Roadmap ID 171735 Updated February 5, 2025: 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 the Risk levels for Adaptive Protection settings. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously mid-January) and expect to complete by mid-March 2025 (previously mid-February). How this will affect your organization: Before this rollout, admins can select single Insider Risk Managment policies in the Risk levels for Adaptive Protection settings. 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 Microsoft 365 Copilot MC1020327 — M365 Copilot for GCC Environments: Wave 2 Microsoft 365 Roadmap ID 483357 Bringing Microsoft 365 Copilot GCC your AI assistant for work in the GCC environment. It combines the power of Large Language Models with your work content and context, to help you draft and rewrite, summarize and organize, catch up on what you missed, and get answers to questions via open prompts. Copilot generates answers using the rich, people-centric data and insights available in the Microsoft Graph. We are excited to announce the release of the second wave of apps for M365 Copilot into the GCC environment. This release includes Stream, OneNote, SharePoint, and Pages in Loop, enhancing your organization's productivity and collaboration capabilities. When this will happen: General Availability (GCC): We will begin rolling out in late March 2025 and expect to complete by early April 2025. How this will affect your organization: As with the other M365 Copilot experiences released in December, the web grounding policy default is OFF for GCC. Web grounding in these new apps will follow the settings of the existing web grounding policy. What you need to do to prepare: A toggle is available in your admin center to enable and disable web grounding for M365 Copilot experiences. Please review your settings and make any necessary adjustments to align with your organization's needs. For more information and resources, please visit: Data, privacy, and security for web search in Microsoft 365 Copilot and Microsoft 365 Copilot Chat. MC1020200 — New Microsoft 365 Copilot release notes page We are pleased to announce the availability of a new, centralized Microsoft 365 Copilot release notes page. This page consolidates all Copilot-related releases across the Microsoft 365 suite—such as Word, Excel, PowerPoint, Outlook, Teams, Microsoft 365 Copilot app, Copilot chat, and more—into a single, easy-to-reference resource. It also includes platform-specific filters for Windows, Web, Mac, Android, and iOS to help you quickly locate the updates most relevant to your organization. This new page highlights features and enhancements that have reached General Availability (GA) across selected platforms, ensuring you can stay informed about the latest capabilities of Copilot across Microsoft 365. When this will happen: The new Copilot release notes page is available now at Microsoft 365 Copilot release notes. We will continue to update it regularly as new Copilot features become generally available across different services and platforms. How this will affect your organization: Centralized information:Rather than visiting multiple sources, you can now view all Copilot GA releases in one location. Easier discovery:Filter by the specific platform(s) you use (Windows, Web, Mac, Android, iOS) for more targeted release information. Up-to-date insights:The page is refreshed every other week, ensuring you always have the latest Copilot updates at your fingertips. What you need to do to prepare: Bookmark the page: We recommend that admins and end users bookmark this new release notes page for quick access. Share internally: Distribute the link to this page within your organization so teams can stay aware of all relevant Copilot updates. Review and plan: Use the information in the release notes to plan for any necessary training, user documentation updates, or adoption strategies aligned with your organization’s Copilot deployment. Submit your feedback: Your input is important to us. Use the 'Feedback' button on the Copilot release notes page to share what you like and where improvements can be made so we can continue enhancing this resource to better meet your needs. MC1003344 — (Updated) Microsoft Copilot: File summary in Microsoft Teams chat Microsoft 365 Roadmap ID 418564 Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. Users will be able to summarize files with Summarize for me using Microsoft Copilot within one-on-one or group Microsoft Teams chats. This feature will work on common file types like Word and PDF initially, and other file formats will be added over time. This summarization respects the file's security policies, ensuring that only users with access to the file receive a summary, which will carry the same sensitivity label as the original file. A Microsoft 365 Copilot license is required to use this feature. When this will happen: Targeted Release: We will begin rolling out early April 2025 (previously early March) and expect to complete by mid-April 2025 (previously mid-March). General Availability (Worldwide): We will begin rolling out late April 2025 (previously late March) and expect to complete by mid-May 2025 (previously mid-April). General Availability (GCC): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025. How this will affect your organization: Users will be able to summarize files with Summarize for me in Copilot within Teams chats. This feature will be 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. Microsoft Outlook MC1022526 — Microsoft Outlook on the web: Optional connected experiences privacy setting Microsoft 365 Roadmap ID 467248 The user privacy setting for optional connected experiences, already available in other Microsoft Outlook and Microsoft 365 apps, will soon be available in Microsoft Outlook on the web. When this will happen: General Availability (Worldwide): We will begin rolling out early March 2025 and expect to complete by late March 2025. General Availability (GCC): We will begin rolling out in early April 2025 and expect to be complete by late April 2025. How this will affect your organization: After the rollout, to configure the privacy setting for optional connected experiences, users can go to Settings > General > Privacy and data > Privacy settings: On the Privacy settings screen, select the toggle for Turn on optional connected experiences: This privacy setting applies across all devices where users are signed in with the same work or school account. As an admin, if you have already made optional connected experiences available to your users in the Microsoft 365 Apps admin center, this setting will be turned on for Outlook on the web when users receive this rollout. Learn more: Use policy settings to manage privacy controls for Office for the web applications - Microsoft 365 Apps | Microsoft Learn Overview of Cloud Policy service for Microsoft 365 - Microsoft 365 Apps | Microsoft Learn NOTE: If a user has already turned off this setting in another Outlook or Microsoft 365 app, this setting in Outlook on the web will also be turned off when the user receives 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. 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 About privacy controls for optional connected experiences: Overview of privacy controls for Microsoft 365 Apps for enterprise(will be updated before rollout) About Office on the web policy settings, including the new settings for Outlook on the web: Use policy settings to manage privacy controls for Office for the web applications(will be updated before rollout) MC1020206 — Change to Copilot Settings in Outlook Starting in March 2025, Outlook will introduce a new setting that allows users to hide Copilot entry points (e.g., "Summarize this email") from the app. This setting can be configured per account and will apply to both organizational and personal email accounts within the app. Once set, the preference will sync across all Outlook applications. This update is in response to user feedback. When this will happen: The rollout will begin in March 2025. How this affects your organization: Users will have the option to hide Copilot entry points in the following Outlook applications: New Outlook for Windows Outlook for iOS Outlook for Android Outlook for Mac Outlook on the Web Classic Outlook for Windows will not have the ability to change this setting. However, any changes made in other Outlook applications will sync with Classic Outlook for Windows. What you can do to prepare: Admins should inform users about this new setting and its availability across different Outlook applications. No additional action is required as the setting will be available by default. MC1011141 — Microsoft Outlook for iOS and Android: Microsoft 365 (Office) app is now the Microsoft 365 Copilot app The Microsoft 365 (Office) app has become the Microsoft 365 Copilot app. After this rollout, users will notice changes in the Microsoft Outlook apps for iOS and Android. Also, when Outlook for iOS and Android users view their account list in Settings, they will notice a new icon for their Microsoft account. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out early March 2025 and expect to complete by late March 2025. How this will affect your organization: Before this rollout, Microsoft 365 (Office) app and Microsoft 365 accounts in the Microsoft Outlook apps for iOS and Android have this icon: After this rollout, the app for iOS and Android will be called Microsoft 365 Copilot and will have this icon: Microsoft 365 accounts will be represented by the Microsoft logo: This change will be available by default. What you need to do to prepare: This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change and update relevant documentation. Learn more: The Microsoft 365 app transition to the Microsoft 365 Copilot app - Microsoft Support MC1003345 — New Microsoft Outlook for Windows and web: New "None" color category for Mail and Calendar Microsoft 365 Roadmap ID 469035 Coming soon to new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web: A None color category that users can apply to Mail and Calendar items. This update provides parity with classic Outlook and more flexibility and customization for users to categorize their emails and calendar events. By selecting the None option, users can choose to have items without a designated color, allowing for cleaner organization and more control over which items stand out visually. When this will happen: Targeted Release: We began rolling out late December 2024 and expect to complete by late February 2025. General Availability (Worldwide): We will begin rolling out late February 2025 and expect to complete by late March 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. How this will affect your organization: Before this rollout, the None color category displayed as gray. After the rollout: Mail items will not have a color, which is the same behavior in classic Microsoft Outlook. Calendar items will retain the default category color related to the user's chosen theme, which is the same behavior as the previous version of Outlook. This change will be available by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Create and assign color categories in Outlook - Microsoft Support (will be updated before rollout) #newoutlookforwindows MC999441 — New Microsoft Outlook for Windows: Group messages as a conversation for emails within Outlook Data File Microsoft 365 Roadmap ID 479412 New Outlook for Windows users will be able to group messages as a conversation for emails within Outlook Data File (.pst or Personal Storage Table file). Future releases of new Outlook for Windows will expand the support for .pst file capabilities. When this will happen: Targeted Release: We will begin rolling out early February 2025 and expect to complete by mid-March 2025. General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by early April 2025. General Availability (GCC): We will begin rolling out early April 2025 and expect to complete by early May 2025 How this will affect your organization: Outlook Data File (.pst) support is enabled by default in new Outlook for Windows. If you organization wants to block or limit Outlook Data File support, set the OutlookDataFile mailbox policy. Learn more: Set-OwaMailboxPolicy (ExchangePowerShell) 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. Before rollout, we will update this post with revised documentation. #newoutlookforwindows MC997580 — New Microsoft Outlook for Windows and web: Categorize individual emails in conversation view Microsoft 365 Roadmap ID 416450 Coming soon to new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web: Users can categorize individual emails in conversation view to enhance organization and tracking. When this will happen: Targeted Release: We began rolling out early January 2025 and expect to complete by late February 2025. General Availability (Worldwide): We will begin rolling out late February 2025 and expect to complete by late March 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. How this will affect your organization: To use the conversation view, users can go to the Outlook ribbon and select View > Messages > Conversation > Group into conversations To categorize an individual email, a user must select the Group into conversations option. Then, in the list of emails, expand a conversation and right-click the individual email to be categorized, select the Categorize option, and choose the category (or categories). The selected category will display in the individual email and in the email header and the reading pane. Deleting a category from the message header or from the reading pane will remove the category applied to any individual emails in that conversation. This change will be available by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Use categories in Outlook - Microsoft Support #newoutlookforwindows MC997576 — Microsoft Outlook for iOS: Open the previous email with email auto-advance Microsoft 365 Roadmap ID 477362 Note: If your organization does not support iOS users, you can ignore this message. Coming soon to Microsoft Outlook for iOS: A new Open the Email Above setting to automatically open the message above the current one in the message list after performing actions like moving or deleting the current message. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by mid-March 2025 . How this will affect your organization: After this rollout, users can find the new setting in Outlook at Settings > Mail > Email Auto-advance > Open the Email Above. We will also remove the Move to the Next Email setting. Before the rollout: Go back to the Inbox Move to the Next Email After the rollout: Go Back to the Message List Open the Email Below Open the Email Above 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: Email Auto-Advance Setting - Microsoft Support MC981624 — (Updated) Microsoft Outlook name change: "Outlook (new)" on Windows will change to "Outlook" Updated February 24, 2025: We have updated the rollout timeline and content. Thank you for your patience. We are delaying this change until mid-March to allow time to for customer experiencing issues with classic Outlook shortcuts to use this workaround. Some customers may still see classic Outlook shortcuts listed as just "Outlook", which could lead to confusion when new Outlook's installed name changes. The workaround for this issue is documented here. Coming soon: The installed name for new Microsoft Outlook for Windows will change from "Outlook (new)" to "Outlook." This rollout comes after a change to the classic Outlook in version 2407, previously announced in MC803006 (Update) Outlook for Windows display name change (published June 2024, updated August 2024), which added "(classic)" to the installed name to differentiate the two apps. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). What you need to do to prepare: Outlook in the Windows Start menu. Left: Before the name change. Right: After the name change: This change will be on by default. This part of the app identity is not customizable for organizations. As always, we recommend planning your organization's migration to the new Outlook using the resources at https://aka.ms/newOutlookAdoption 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. #newoutlookforwindows MC960818 — (Updated) Microsoft Outlook for iOS/Android: New reporting buttons integrated with Microsoft Defender for Office 365 Microsoft 365 Roadmap ID 371383 Updated February 19, 2025: We have updated the content. Thank you for your patience. Coming soon to Microsoft Outlook for iOS/Android: New built-in report buttons in version > 4.2446 or later (android) and version > 4.2508 or later (iOS). Admins can control the appearance and behavior of these buttons that allow users to report emails as phishing / junk / not junk from the User Reported setting page 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. When this will happen: General Availability (Worldwide, GCC, GCC High): We began rolling out in early December 2024 and expect to complete by late February 2025 (previously late January). How this will affect your organization: Information to keep in mind: Microsoft OWA (Outlook on the Web) and the new Microsoft Outlook for Windows have had this functionality since November 2022. This rollout to iOS/Android does not change or affect that functionality. Classic Microsoft Outlook for Windows client has had this functionality in current channel since August 2024. Learn more: MC841229(Updated) Classic Microsoft Outlook for Windows: New reporting buttons integrated with Microsoft Defender for Office 365 (published July 2024, updated October 2024). Microsoft Outlook for Mac released this functionality in September 2024. If you have turned off the reporting feature in the Microsoft 365 Defender User reported settings page or are using a third-party add-in, the report buttons in Outlook for Android/iOS won't be visible. The Microsoft reporting add-in (the Microsoft report message add-in and Microsoft phishing add-in) will be supported till further notice. The future goal is to have a consistent button reporting experience across all Outlook platforms. If you are using Microsoft reporting add-ins in Outlook for iOS/Android, your users will see two reporting experiences: one from the built-in Outlook buttons (added by this rollout) and one from the add-in. Both options will behave the same for users (except for the newly customizable pop-ups) and the reported messages will end up in the same place, causing minimal disruption. 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 your User reportedsettings. Like OWA and new Outlook for Windows, the built-in reporting button in Outlook for iOS/Android supports reporting from shared and delegate mailboxes. This change is available 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 users about this change and update any relevant documentation. No action is required form you after this rollout because your current settings in the User reported settings page will not be changed. Learn more Report phishing and suspicious emails in Outlook for admins - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout) User reported settings - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout) MC946791 — (Updated) Microsoft Outlook for iOS and Android: Minimize the compose window to multitask in the Outlook app Microsoft 365 Roadmap ID 470304 Updated February 19, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Outlook for iOS and Android: Minimize draft emails and quickly access them again from the message list or calendar view. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out early January 2025 and expect to complete by late March 2025 (previously early February). How this will affect your organization: Outlook will help you compose emails more quickly and efficiently by allowing you to minimize your draft emails and quickly access them again from the message list or calendar view. This means that while composing an email you can easily get information you need from your calendar or other emails and easily get back into the draft you are working on without ever having to go to the Draft folder. To start, select the minimize icon in the upper right corner. This change will be on by default. What you need to do to prepare: This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change and update relevant documentation. MC926191 — (Updated) New Microsoft Outlook for Windows and web: Pin the Favorites section Microsoft 365 Roadmap ID 401341 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for new Outlook for Windows and web: Easily access your most-used folders by pinning a Favorites section at the top of the Outlook folder list on the left side of the screen. This feature streamlines navigation, ensuring your important folders are always in easy reach. Before this rollout, users can add a Favorites section that scrolls down when users navigate down the list. After this rollout, users can choose to keep the Favorites section pinned to the top of the list, and only the rest of the folders will scroll. When this will happen: Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by mid-December 2025. General Availability (Worldwide): We will begin rolling out mid-December 2024 and expect to complete by mid-January 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out mid-January 2025 and expect to complete by early March 2025 (previously mid-February). How this will affect your organization: After the rollout, users can pin or unpin the Favorites section in two ways. In the Favorites section of the folder list (on the left of the screen), right-click the three-dot menu and select Pin favorites or Unpin favorites. On the Outlook ribbon, select the View tab > Folder pane > Favorites > select Pin favorites or Unpin favorites. This change will be available by default for users to choose to pin and unpin the Favorites section. What you need to do to prepare: Learn more: Use Favorites in Outlook - Microsoft Support (will be updated before rollout) 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. #newoutlookforwindows MC847877 — (Updated) Microsoft Outlook for iOS and Android: Choose fonts while composing Microsoft 365 Roadmap ID 409969 Updated February 13, 2025: 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 late March 2025 (previously late January). 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. MC779851 — (Updated) To Do app opens in new Outlook for Windows Microsoft 365 Roadmap ID 375602 Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. Use the Microsoft To Do app without leaving new Outlook for Windows. Clicking the To Do icon in the navigation bar will open the app inline and will no longer open it in a separate browser. When this will happen: Standard Release (GCC High, DoD): We will begin rolling out late February 2025 (previously late January) and expect to complete by late March 2025 (previously late February). How this will affect your organization: Users will notice a new entry point in classic Outlook for Windows if their active commercial Microsoft account has been granted access by their tenant administrator. No additional steps are required from the admin if the To Do app has already been enabled for the appropriate users in the existing To Do web or desktop applications. What you need to do to prepare: Ensure that the To Do app workload is enabled for your tenant. For details about ensuring access, see Set up Microsoft To Do. For more information about the To Do app, see Use To Do app to manage Tasks in Outlook. Exchange Online MC1015893 — The way to control EWS usage in Exchange Online is changing We are making a change to the behavior of the EWSEnabled tenant-wide switch in Exchange Online. When this will happen: This change will rollout worldwide, starting April 1, 2025 How this affects your organization: If you want to restrict the usage of EWS in your tenant, this change might affect you. The current behavior of the EWSEnabled flag is that it can be set at both the tenant (organization) level and the user (mailbox) level. Currently, when the flag is set to true at the user level, it takes precedence over the organization-level setting. If a setting is Null, it means the setting is not enforced at that level. If Org and user-level are both Null, the default behavior is to allow. This hierarchical structure means that if the organization-level flag is set to false, but the user-level flag is set to true, EWS requests from that user are still allowed. In summary: This approach has led to situations where it can be challenging for administrators to ensure uniform policy enforcement across their organization, particularly in large and complex environments. New Behavior To address these issues, we are altering the behavior so that EWS will only be allowed if both the organization-level and user-level EWSEnabled flags are true. Here's a simplified view of the new logic: In short, EWS will be permitted only if both the organization and user-level allow it. This change ensures that administrators have better control over EWS access and can enforce policies more consistently across their entire organization Next Steps: Please check the blog for additional information and ensure your per-user and tenant wide settings are correct before this change is made to your tenant. The way to control EWS usage in Exchange Online is changing MC886603 — (Updated) Reject multiple From addresses (P2 From headers) without a Sender header Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. We are proactively opting tenants out of the rollout that were detected as sending high volumes of emails exhibiting multiple From addresses without a Sender address header. These exempted senders will only be able to send emails exhibiting multiple From addresses without a Sender address header to recipients belonging to the same tenant as the sender. We will provide a subsequent update by the end of May 2025 (previously end of March) with an updated timeline for tenants that are opted out. Starting April 15, 2025 (previously February 3), we're going to start gradually dropping messages that have multiple From addresses (also known as P2 From headers) without a Sender header from being processed via Exchange Online. If we see significant traffic exhibiting multiple From addresses (P2 From headers) without a Sender header in your tenant in the month of September, we will send you a Message Center Post by October 15th alerting you and providing some sample message IDs. We are doing this to comply with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2) which mandates the Sender header to be present and contain a single address if the From header has more than one address. Noncompliance with this could be exploited by attackers, allowing them to impersonate a sender address by misleading the client into using the From header to determine the sender instead of the Sender header. When this will happen: April 15, 2025 (previously February 3) We are delaying the rollout start date from December to April 15, 2025 (previously February 3) in order to provide more time to customers for investigating messages exhibiting multiple P2 From Addresses without a Sender Address. Most of the traffic exhibiting multiple P2 From Addresses without a Sender Address will be inbound spam destined for your tenant sent by malicious spammers on the internet. Some customers are sending legitimate emails with this malformed header configuration. On October 15, we sent a targeted MC post to customers showing high volumes of messages exhibiting multiple P2 From Addresses without a Sender Address as they may be impacted by this change. For investigating if you will be impacted by this change, focus your investigation on messages sent using On Premises Inbound Connectors to Exchange Online. Authenticated mail submission is not impacted because submitting messages like this using those submissions are not allowed (Graph, Outlook clients, SMTP AUTH Client Submission). How this affects your organization: If email clients including devices and applications that you use to send messages, do so using multiple From addresses but without a Sender address header after April 15 2025 (previously December 1st), you will get an NDR error code 550 5.1.20 “Multiple From addresses are not allowed without Sender address’”. What you can do to prepare: When this change is in effect, if you need to send a message that has more than one email address in the From field, make sure that you have a single email address in the Sender header. If you expect this change to cause any issues for your organization, please share that feedback. Microsoft 365 MC980798 — (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) Microsoft 365 Roadmap ID 475046 Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Python in Excel allows you to bring the capabilities of Python directly into the Microsoft Excel grid. With this rollout, Python in Excel with standard compute will be generally available in Excel for Windows. When this will happen: General Availability (GCC): We will begin rolling out to Excel for Windows mid-March 2025 (previously mid-February) and expect to complete by early April 2025 (previously early March). After we complete the rollout to Excel for Windows, we will send a separate message with the timeline for rolling out this change to Microsoft Excel for the web and Microsoft Excel for Mac. How this will affect your organization: After this rollout, eligible users will be able to add Python formulas to their workbooks without any installation required. These Python formulas will be run by Excel in a secure container on the Microsoft Cloud with enterprise-level security and with standard compute. With this release, eligible Excel users with a Microsoft 365 Copilot license will also be able to use the Copilot in Excel with Python feature, enabling them to leverage the capabilities of AI and Python in Excel for deeper data analysis. Note: Some premium Python compute will be included with each user’s Microsoft 365 subscription each month, giving them limited access to faster calculation speeds. After they have used all of their premium compute, they can continue to use the Python in Excel feature with standard Python compute. To get more premium compute, admins will be able to purchase the Python in Excel add-on license for their users after it becomes available later this year for GCC. We will send a separate message with the timeline for the rollout of the Python in Excel add-on license. The Python in Excel feature will be enabled by default. What you need to do to prepare: To learn more about Python in Excel, please review the Python in Excel documentation. To learn more about data security: Data security and Python in Excel - Microsoft Support 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 relevant documentation. MC961557 — (Updated) Microsoft Search in Bing Deprecation Updated February 20, 2025: There are new details available regarding the Microsoft Search in Bing retirement. The FAQ is now available at Guidance for retiring Microsoft Search in Bing for your organization. Microsoft Search in Bing, the search experience for work and school available on Bing.com, is being deprecated. The last day of its availability is on March 31, 2025. This change is being made as we streamline search experiences and focus on enhancing core productivity tools. The Microsoft Edge for Business address bar and the Windows search box will continue to support work and school search, with some adjustments detailed below. Details of the Change After March 31, 2025, Microsoft Search in Bing will no longer be available, with changes as follows: Bing.com will no longer show work or school search results. Consequently, there will not be a dedicated page of work or school results and users’ work or school profiles will no longer appear on Bing.com. However, selecting the Work or School tab on Bing.com will redirect users to the new Microsoft Search experience on M365.cloud.microsoft (formerly Office.com and Microsoft365.com). Search boxes you’ve configured to point to Microsoft Search in Bing will no longer provide work or school results. The Edge for Business address bar and Windows search box will continue to support work and school search with some adjustments, including: o The Edge for Business address bar will no longer return work or school search results on a Bing.com page but will continue to provide suggested results in the address bar. In addition, the address bar will send users to work and school results on M365.cloud.microsoft rather than Bing.com. Users of the address bar can continue to find work-related documents, bookmarks, and people in suggested results—clicking on these suggestions takes users to work or school results on M365.cloud.microsoft. Users can also type "work" in the address bar, hit the tab key, then input their work- or school-related query to get results on a M365.cloud.microsoft page. Work and school search results will include documents, people, and bookmarks. Work search for documents will be available initially, with additional content types available as quickly as possible. o The Windows search box will no longer display organization branding nor the “Work” or “School” tab but will continue to support work and school search. Search for documents and people remains available. will be available initially, with additional content types available as quickly as possible. With these changes, users will see some UX changes in the Windows search box. As before, the core Microsoft Search experience remains accessible through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. Additionally, Entra ID sign-in will no longer be available on Bing.com, since work and school search is no longer available on Bing.com. An FAQ and further details are now available at Guidance for retiring Microsoft Search in Bing for your organization, which will be updated regularly. When will this happen: The last day of availability of Microsoft Search in Bing is March 31, 2025. How this affects your organization: For organizations using Microsoft Search in Bing, users will need to transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. Users who are accustomed to using the Edge for Business address bar and the Windows search box can continue to conduct work searches through these endpoints entry points, with the expectation that there will be some adjustment in these experiences after the deprecation date. (For details on changes, please refer to the FAQ: https://aka.ms/MSBFAQ.) Users who click on suggestions in the Edge for Business address bar or Windows search box may be redirected to Microsoft365.com before March 31, 2025. Also, as we begin testing the retirement experience, a small set of users may find before March 31 that Bing is intermittently unavailable as an entry point for work search. We recommend that you proactively inform your users of the change and direct them to M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. Adding M365.cloud.microsoft to their favorites or to the favorites bar in Edge for Business may be a helpful alternative pathway. What you can do to prepare: Customers should prepare to stop using Microsoft Search in Bing by March 31, 2025, and transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. We recommend that you inform users about the upcoming change and the alternatives available. Adding your preferred entry point from this set to favorites or favorites bar in Edge may be a helpful alternative pathway. Admins can easily set favorites in Edge for their organization, please see details here. Additionally, users can continue to use the Edge for Business address bar and the Windows search box, with some changes expected. Please educate users that they should now type "work" in the address bar, hit the tab key, then type in their work-related query to get work results on a M365.cloud.microsoft page. If your organization is using the AddressBarMicrosoftSearchInBingProviderEnabled policy today, you should update to the AddressBarWorkSearchResultsEnabled policy, if the policy is still needed. The new policy, AddressBarWorkSearchResultsEnabled, will be available starting in early March, with Edge for Business version 134 (ahead of the Microsoft Search in Bing deprecation). This allows admins to configure the display of work suggestions in the address bar. If the policy is enabled or not configured, users who are signed into Edge for Business with their Entra ID can view internal work-related suggestions, such as bookmarks, files, and people results powered by Microsoft 365, in the Edge for Business address bar suggestion dropdown. If the policy is disabled, Entra ID signed-in users will not see internal workplace results in the Microsoft Edge address bar suggestion dropdown. Admins who wish to set their own deprecation date prior to March 31, 2025, can turn off Microsoft Search in Bing by going to the Microsoft 365 admin center > Settings > Search & Intelligence. Regarding SafeSearch settings: If you had set the search experience for your organization to “School search,” SafeSearch was set to Strict by default. If you’d like to ensure that your users continue to have SafeSearch set to Strict after the Microsoft Search in Bing retirement, you can map www.bing.com to strict.bing.com at a network level. See Blocking adult content with SafeSearch or blocking Chatfor more details. Note: The search history feature for work or school search is changing along with the retirement of Microsoft Search in Bing. Details are not yet determined, but they will be added to the FAQ once they're finalized. MC923419 — (Updated) Microsoft Loop: Configure guest sharing for tenants with sensitivity labels Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 MC736437 Microsoft 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 MC923176 Microsoft 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 December 2024 (previously early November) and expect to complete by late February 2025 (previously early January). 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 the People you choose option. Guest users cannot create workspaces. 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 with New and existing guestsor Existing 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. Documentation - Office 365 IP Address and URL web service February 28, 2025 - GCC January 30, 2025 - GCC High February 28, 2025 - DOD
Jesse_Tedoff
Mar 20, 2025 Place Public Sector Blog
972Views
0likes
0Comments
February 2025 - Microsoft 365 US Public Sector Roadmap Newsletter
SharePoint End of support for SharePoint Server 2016 and 2019 is scheduled for July 14, 2026. It's advisable to upgrade directly to SharePoint Server Subscription Edition Purview Information Protection New workload for Copilot in Content Explorer Microsoft 365 New deployments of Microsoft 365 desktop client apps to include new Outlook – GCC Unlocking Opportunities for Government Efficiency The U.S. Federal Government stands at a critical inflection point, offering an unprecedented opportunity to redefine how it fulfills its vital missions. As leaders seek to reduce costs and enhance efficiency, much of this can be accomplished through thoughtful technology modernization applied to mission delivery. Feb 21: Announcing M365 Community Days DC 2025 in Arlington We are thrilled to announce M365 Community Days DC, hosted by DC area community leaders at the prestigious Microsoft Innovation Hub, Arlington VA at Rosslyn. Join us February 21st, 2025, for this in-person event featuring speakers from across North America, and headlined by elected official Roxy Ndebumadu, Councilmember for the City of Bowie, MD. Mark your calendars for a day of learning, networking, and innovation! 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. Microsoft 365 Government Adoption Resources Empowering US public sector organizations to transition to Microsoft 365 Microsoft 365 Roadmap This link is filtered to show GCC, GCC High and DOD: 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 Microsoft 365 Copilot (GCC) Microsoft Copilot Studio (GCC) Office 365 Platform (GCC, GCCH, DoD) Office 365 U.S. Government GCC endpoints 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 (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) Dynamics 365 US Government Microsoft Copilot Studio (GCC) WWindows 365 Government Get started with Microsoft 365 Copilot 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 / OneDrive for Business MC996585 — Microsoft SharePoint: Updated document libraries Coming soon to Microsoft SharePoint: We will update the document library experience to improve its overall performance and enhance the functionality of Edit in grid view. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late March 2025. How this will affect your organization: After this rollout, users can expect these improvements: Pages in document libraries will load faster. Enhanced editing in grid view: Choice field editing: Select or change values in Choice columns in grid view. Person field and Group field editing: Assign users or groups to a file by selecting the Person field in grid view. Image field editing: Add or change images in the grid, like the similar feature in Microsoft Lists. Better scrolling with large libraries: Instead of going to the next page if there are more than 100 documents, users can scroll down and see everything. New commands and navigation in grid view: With these improvements, grid view includes several new commands and navigational options that previously were either missing or less intuitive: New commands: Create new items in grid view. Clickable document titles: Document and file titles in the grid are now clickable, making it easier to open items without leaving the grid. Folder navigation: Navigate in and out of folders from the grid view. Details pane in grid view: Open the details pane in grid view. Redesigned Properties pane and right-click menu: Properties pane as a dialog: When you click or modify an item’s details, the properties pane appears as a dialog box. Right-click context menu: Right-click any item in the grid and instantly see context-aware options such as Open, Edit, Share, or Delete. Grouped view support while editing in grid view: Edit items in grid view even when the library is grouped by specific columns (such as grouped by a content type, department, or project). Rating column improvements: If your document library includes a rating column (star ratings or “likes”), we improved the experience of updating and viewing these ratings. A SharePoint document library with an item’s menu expanded (in grid view): A SharePoint document library showing editing option in a field (in grid view): These changes will be available by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or after 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. MC989979 — Microsoft SharePoint: New preview mode for Pages and News posts Microsoft 365 Roadmap ID 473452 Coming soon to Microsoft SharePoint: The new Preview mode can be used to understand how Pages and News posts will appear on different device types when viewed by an audience. When this will happen: Targeted Release: We will begin rolling out late January 2025 and expect to complete by late February 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 and expect to complete by late March 2025. How this will affect your organization: After this rollout, a Preview button will display in the command bar while users are editing Pages and News posts in SharePoint. After selecting Preview, users can see what the page will look like in view mode for the audience. When previewing Pages, users can navigate between Desktop and Mobile device types. When previewing News posts, users can also choose to view the email version as Desktop or Mobile device types. This change will be available by default. What you need to do to prepare: You may want to notify users, update your user training, and prepare your help desk. This rollout will happen automatically by the specified date with no admin action required before or after the rollout. Before rollout, we will update this post with revised documentation. MC976819 — (Updated) Microsoft SharePoint: New Accessibility assistant tool for authoring Pages Microsoft 365 Roadmap ID 470603 Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft SharePoint: A new Accessibility assistant tool to help content creators meet accessibility standards when authoring SharePoint Pages. This tool provides checks and brief guidance to help ensure pages are inclusive and accessible to a broad audience. This rollout reflects our ongoing commitment to fostering accessibility and inclusivity in SharePoint. When this will happen: Targeted Release: We will begin rolling out late January 2025 and expect to complete by late January 2025 (previously early February). General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out early February 2025 (previously mid-February) and expect to complete by mid-February 2025 (previously early March). How this will affect your organization: After this rollout, authors can initiate an accessibility test while editing a page. Authors can select the Accessibility assistant icon from the right vertical toolbar. The Accessibility assistant will support five web parts: Banner, Text, Image, Hero, and Quick Links. The Accessibility assistant identifies accessibility issues: The Accessibility assistant guides authors to address accessibility issues in the specific web part: The Accessibility assistant confirms the author has addressed all accessibility issues: What you need to do to prepare: Before rollout, we will update this post with revised documentation. This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. MC974358 — Microsoft SharePoint admin center: New "App insights" feature will be in Public Preview Microsoft 365 Roadmap ID 417481 Coming soon for Microsoft SharePoint Advanced Management (SAM): A new App insights feature will be available in the Microsoft SharePoint admin center for Public Preview. You can continue to manage this feature with Microsoft PowerShell cmdlets if desired. When this will happen: Public Preview: We will begin rolling out mid-January 2025 and expect to complete by late January 2025. General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. How this will affect your organization: After this rollout, if you are part of SAM, you will be able to get insights in the SharePoint admin center for applications accessing SharePoint content. This feature will be available by default to SAM 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. 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: Generate App insights reports - SharePoint in Microsoft 365 | Microsoft Learn MC974354 — (Updated) Microsoft SharePoint Online: Re-imagined Hero with the new carousel layout in pages and news Microsoft 365 Roadmap ID 395214 Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. We are introducing a new Carousel layout to make the Hero web part more attractive. This new layout will feature a slideshow and a selection of new styles with imagery, bold text, and a call to action, creating a more engaging page experience. When this will happen: Targeted Release: We will start rolling out in mid-January 2025 and expect to complete by mid-January 2025 (previously late January). General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out mid-January 2025 (previously mid-February) and expect to complete by late January 2025 (previously late-February). How this will affect your organization: Adding a Hero web part to a page or news post has not changed. This update allows authors to create eye-catching carousel slides in any section type, with up to five slides in Carousel layout, enhancing user engagement and highlighting key content to establish page hierarchy. It offers three new styles and supports Stream videos to make the page more appealing. 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. MC973514 — SharePoint Pages Flexible Sections Microsoft 365 Roadmap ID 395213 Flexible sections are a new section type that allow authors to build pages without a strict column structure. Web parts can be dynamically resized and moved within flexible sections to create a fully customized section. Flexible sections unlock an endless number of design possibilities for sections. With the introduction of flexible sections, we have reimagined section templates that are located in the content pane toolbox. The new section templates will be powered by both flexible and column-based sections with example content. All sample content from these templates is placed onto the canvas when a section template is applied. The new flexible section type and section templates will be available in SharePoint and Viva Amplify. When this will happen: Targeted Release: We will begin rolling out late-January 2025 and expect to complete by mid-March 2025. General Availability (Production, GCC, GCC High, DOD): We will begin rolling out mid-March 2025 and expect to complete by late April 2025. How this will affect your organization: Users will see a new option when adding a section to a page, called “Flexible”. Within a flexible section, users can drag and drop web parts anywhere on the grid. Web parts will snap to the closest grid line when moved. Users can also resize web parts. Card-based web parts, such as Quick Links, People, or Hero, only have four different width options (full width, 1/3 canvas width, ½ canvas width, and 2/3 canvas width). These web parts can only be resized to one of the four options. Non-card-based web parts, such as Text, Image, and File & Media can be resized to any width. Web parts will snap to the closest gird line when being resized. Users can resize flexible sections manually, change the arrangement of overlapping web parts, multi-select web parts, and group web parts. Users can select or drag and drop a new section template from the content pane toolbox. After the template is added to the canvas, users can make adjustments to the web parts and section until ready to publish. What you need to do to prepare: You might want to notify users, update your user training, and prepare your help desk. MC973498 — Microsoft SharePoint: New "Editorial card" web part for Pages and News Microsoft 365 Roadmap ID 414524 Coming soon to Microsoft SharePoint: a new web part for Pages and New posts called the Editorial card. Unlike automated web parts like News and Events, the new Editorial card allows SharePoint designers to manually tailor the content presentation to their needs. When this will happen: Targeted Release: We will start rolling out late January 2025 and expect to complete by mid-February 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will start rolling out mid-February 2025 and expect to complete by late February 2025. How this will affect your organization: After this rollout, users can: Showcase content in an engaging card format with advanced background and content settings Configure content to suit varied author needs This change will be available to users by default. The Editorial card in the Web parts section of the Toolbox (right pane): 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. Before rollout, we will update this post with revised documentation. Examples of Editorial card content: MC947052 — (Updated) Microsoft SharePoint: Filter search results by "Messages" General Availability (Worldwide, GCC, GCC High, DoD): This rollout has completed Updated February 3, 2025: We have updated the rollout timeline below. Thank you for your patience. The same Messages search vertical at microsoft365.com will soon be available for organization-wide search in Microsoft SharePoint. Search verticals are tabs on the search result page that show results of a specific type or from select sources. For example, the Files vertical shows results classified as files and makes it easy for users who are looking to find documents. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): This rollout has completed. How this will affect your organization: This feature will be on by default. If you have disabled the Messages search vertical for microsoft365.com, the Messages search vertical will also be disabled in SharePoint. Learn more: Manage search verticals | 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. 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. MC912181 — (Updated) Microsoft SharePoint: Add approvals to any document library Microsoft 365 Roadmap ID 420336 Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 late January 2025 (previously early January) and expect to complete by early March 2025 (previously late January). General Availability (Worldwide, GCC): We will begin rolling out early March 2025 (early January) and expect to complete by late March 2025 (late January). 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 the Automate dropdown menu from the command bar in SharePoint Online document libraries and then selecting the Configure Approvals option 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 is Marked 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 the Approvals app 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: 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 new Approvals functionality for libraries and lists. Share the support documentation Approvals in lists, which will be updated before this rollout begins to include library support. MC906496 — (Updated) Microsoft OneDrive and Microsoft SharePoint: New setting to disable presence in the file viewer Microsoft 365 Roadmap ID 419814 Updated January 8, 2025: We have updated the rollout timeline below. Thank you for your patience. Administrators can now use the Microsoft SharePoint Online Management Shell to 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 mid-January (previously December). 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 running Set-SPOSite -HidePeoplePreviewingFiles $true along 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. MC693865 — (Updated) SharePoint Add-In retirement in Microsoft 365 Updated February 1, 2025: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 14 months from now (April 2, 2026). Since the release of SharePoint Add-Ins in 2013, Microsoft has evolved SharePoint extensibility using SharePoint Framework (SPFx) enabling you to write applications that can be used in Microsoft SharePoint, Viva Connections and Microsoft Teams. With our continued investment in SharePoint Framework, Microsoft is retiring SharePoint Add-Ins. Key Points: Major: Retirement Timeline: o Starting July 1st, 2024, SharePoint Add-Ins cannot be installed from the public marketplace, also referred to as store by existing tenants. Installation from a private app catalog stays possible. o Starting November 1st, 2024, new tenants will not be able use SharePoint Add-Ins, regardless of their origin (public marketplace, private tenant catalog). o Starting April 2nd, 2026, Microsoft will remove the ability use SharePoint Add-Ins for existing tenants. Action: Review and assess impact How this will affect your organization: If your organization still uses SharePoint Add-Ins, they will no longer function after April 2nd, 2026. We recommend customers to port their customizations to SharePoint Framework (SPFx) and ask their solution vendors for updated solutions. What you need to do to prepare: You will want to notify your Add-In users and developers. Update your user training and prepare your help desk. For admins Use the Microsoft 365 Assessment toolto scan your tenants for SharePoint Add-In usage. Disable SharePoint Add-Inson your tenant using SharePoint Online Management Shell Review the guidance for migrating from SharePoint Add-Ins to SharePoint Framework. There will not be an option to extend SharePoint Add-Ins beyond April 2nd 2026. New: How to disable SharePoint Add-Ins on your tenant Admins can disable SharePoint Add-Ins with the Set-SPOTenant SharePoint Management Shell PowerShell command. Connect-SPOService -Url https://<tenant>-admin.sharepoint.com Set-SPOTenant -IsSharePointAddInsDisabled $true After SharePoint Add-Ins are disabled, users will not be able to add SharePoint Add-Ins to their sites, and admins cannot add new SharePoint Add-Ins to the tenant and site collection app catalogs. SharePoint Add-Ins already added to sites will stay available and can still be used by the site's users. New: SharePoint Add-Ins will not be available from the public marketplace After July 1, 2024, users browsing the public marketplace (AppSource) will see SharePoint Add-In, but if they select Get it now, a message will explain that SharePoint Add-Ins are retired and cannot be added. If you still require a specific SharePoint Add-In, contact the Add-In creator to understand the possible options. Learn more Support update for the retirement of SharePoint Add-Insin Microsoft 365. MC693863 — (Updated) Azure ACS retirement in Microsoft 365 Updated February 1, 2025: This update serves as a reminder that Azure ACS in Microsoft 365 will retire and stop working in 14 months from now (April 2, 2026). Since the first use of Azure Access Control Services (ACS) by SharePoint in 2013, Microsoft has evolved the authorization and authentication options for SharePoint Online via Microsoft Entra ID (a.k.a. Azure AD). Using Microsoft Entra ID as auth platform for your SharePoint Online customizations will provide your applications the most secure, compliant and future proof model. With our continued investment in Microsoft Entra ID, Microsoft is retiring the use of Azure ACS as auth platform for SharePoint Online. Key Points: Major: Retirement Timeline: o Starting November 1st, 2024, new tenants will not be able use Azure ACS. o Starting April 2, 2026, Microsoft will remove the ability use SharePoint ACS for existing tenants. Action: Review and assess impact How this will affect your organization: If your organization still uses Azure ACS to grant custom developed or third party applications access to SharePoint Online, they will no longer have access after April 2nd, 2026. We recommend customers to update their customizations to use Microsoft Entra ID and ask their solution vendors to do the same. What you need to do to prepare: You will want to notify your Azure ACS users and developers. Update your user training and prepare your help desk. For admins Use the Microsoft 365 Assessment toolto scan your tenants for Azure ACS usage. Review the guidance for migrating from Azure ACS to Microsoft Entra ID. There will not be an option to extend Azure ACS usage for SharePoint Online beyond April 2nd 2026. Learn more Support update for the retirement of Azure ACS for SharePoint Onlinein Microsoft 365. MC542767 — (Updated) SharePoint 2013 workflow retirement Updated February 1, 2025: This update serves as a reminder that SharePoint 2013 workflow will retire and stop working in 14 months from now (April 2, 2026). Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only encompass SharePoint, but all the productivity services you use with Microsoft 365 and beyond. With the continued investment in Power Automate as the universal solution to workflow, Microsoft is retiring SharePoint 2013 workflows. When this will happen: Starting April 2nd, 2024, SharePoint 2013 workflows will be turned off for any newly created tenants. Starting April 2nd, 2026, Microsoft will remove the ability to run, or create and execute SharePoint 2013 workflows for existing tenants. How this will affect your organization: If your organization still uses SharePoint 2013 workflows, they will no longer function after April 2nd, 2026. We recommend customers to move to Power Automate or other supported solutions. What you need to do to prepare: You will want to notify your users, workflow developers and site owners. Update your user training and prepare your help desk. For admins Use the Microsoft 365 Assessment tool to scan your tenants for legacy workflow usage. Review Guidance: Migrate from classic workflows to Power Automate flows in SharePoint Review the Power Automate resourcesas a solution to legacy workflows. Note: There will not be an option to extend SharePoint 2013 workflow beyond April 2nd 2026. Learn more: Detailed support articlewith additional resources. Microsoft Copilot MC981631 — Microsoft Teams: Microsoft 365 Copilot in Teams meetings will be generally available to GCC Microsoft 365 Roadmap ID 476072 Coming soon for Microsoft Teams: We’re excited to announce that Microsoft 365 Copilot in Teams meetings will soon be available. This message pertains to Teams for Windows desktop, Teams for the web, Teams for Mac desktop, and Teams for iOS/Android. A Microsoft 365 Copilot license is required to use this feature. When this will happen: General Availability (GCC): We will begin rolling out early February 2025 and expect to complete by mid-February 2025. How this will affect your organization: This rollout marks an important step in delivering Copilot in Teams meeting capabilities for your organization including: Ask Copilot questions about the meeting in real-time and after meeting ends Use out-of-the-box prompts for common tasks, such as generating a meeting recap, listing action items, capturing unresolved questions, or listing main ideas discussed in the meeting Use Copilot during the meeting without retaining a transcript after the meeting Generate Copilot responses based on both the spoken transcript and the written meeting chat Here are key details to help you prepare and understand what to expect: Teams admin center updates: Over the coming weeks, you may notice Copilot controls appearing in your Teams admin center. These controls will allow you to get familiar with how you will be able to manage Copilot in Teams in anticipation of the full rollout. Functionality launch: We will start rolling out Copilot for Teams meetings to the Teams application in early February, but the Teams admin center controls may become visible earlier. The Copilot in Teams setting in the Teams admin center will be ON (requiring transcript) by default. Copilot in Teams will be available to users by default. We appreciate your patience and understanding as we finalize this deployment. Our team is committed to ensuring a smooth experience for both admins and 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. Review your current configuration to determine the impact for your organization. You may want to notify your users and admins about this change and update any relevant documentation. Learn more Manage Microsoft 365 Copilot in Teams meetings and events - Microsoft Teams | Microsoft Learn Use Copilot in Microsoft Teams meetings - Microsoft Support Microsoft Viva MC989956 — Microsoft Viva: Edit and schedule polls in Viva Engage Microsoft 365 Roadmap ID 467251 Starting in February 2025, customers with the Microsoft Viva suite or Microsoft Viva Communications and Communities premium licenses will see an option to schedule or edit a poll prior to publication. When this will happen: General Availability (Worldwide): We will begin rolling out in mid-February 2025 and expect to complete by late March 2025. How this will affect your organization: Before this rollout, users did not have a way to schedule polls in Engage. After this rollout, premium-licensed users will have a new option in the publisher to schedule a poll post in the same location as other post types (discussion, question, praise, article). From their drafts, users can publish or edit a poll. Users may also edit a poll prior to publication from their drafts. Users cannot edit poll posts, including voting options, after publication. This feature will be available by default. The new option to schedule or edit a poll prior to publication: What you need to do to prepare: This rollout will happen automatically by the specified date. There is no action for admins to enable or opt-in to this feature. 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: Write and schedule posts, articles, and announcements in Viva Engage - Microsoft Support MC979826 — (Updated) Microsoft Viva Connections: Update to app name Updated January 24, 2025: We have updated the content. Thank you for your patience. We are renaming the Viva Connections app to Connections. This change is intended to ensure the app name fits better within Microsoft Teams, preventing it from being truncated. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously mid-February). How this will affect your organization: If you have already customized the Viva Connections app name in the Microsoft Teams app store, your customizations will remain unchanged. This update 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. Microsoft Teams MC996588 — Microsoft Teams: Adding and editing external contacts on Teams phone devices Microsoft 365 Roadmap ID 476485 A new feature allows users to add and edit external contacts using the lightweight People app on Microsoft Teams phone devices. With this capability, you will be able to manage and interact with contacts outside of your organization on Teams phone devices. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. General Availability (GCC High): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (DoD): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. How this will affect your organization: Users will now be able to add and edit external contacts from Teams phone devices. To add an external contact: Click Create new contact from the People app. Add in the details of the external contact, and then click Save. What you need to do to prepare: Please ensure that your Teams phone devices are updated with the latest People app to get access to this new feature. This feature will only be available with the latest application update. MC996587 — Microsoft Teams Voice: Link Voice apps without using resource accounts We are excited to introduce a new feature in the Voice section of the Microsoft Teams admin center that allows admins to create linked Voice apps without needing to associate them with a resource account. This update simplifies the process of managing Auto attendant (AA) and Call queue (CQ) services. When this will happen: General Availability (Production): Available now. How this will affect your organization: After this rollout, in the Redirection options, you can select Voice app or Resource account to link AAs and CQs. Before this rollout, the Voice app option lets you link AAs and CQs using the resource account associated with them. If you prefer to use a resource account, you can still select Resource account: Admins can use the using the Voice app option to create linked Voice apps without associating them with a resource account: For example, this feature is useful when you want to create a call flow where multiple AAs and CQs are linked together. If you have an AA that needs to transfer calls to different departments, you can link it directly to multiple CQs without needing a separate resource account for each CQ. This new feature will be available 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 relevant documentation. Admins should review your existing AA and CQ setups and update them to take advantage of the new feature. Existing configurations will continue to work as before under the Resource account option. Learn more Manage resource accounts for service numbers - Microsoft Teams | Microsoft Learn(will be updated before rollout) The Nested Auto attendants and Call queuessection in Plan for Teams Auto attendants and Call queues - Microsoft Teams | Microsoft Learn MC994288 — Microsoft Teams: Speed dial on line keys for touch phone devices Microsoft 365 Roadmap ID 476486 A new feature allows you to configure custom contacts and speed dial on the line key of touch phone devices certified for Microsoft Teams. It enables you to swiftly access frequently dialed numbers and contacts, incorporating one-touch/press dialing and easy management of contact lists on touch devices. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 and expect to complete late March 2025. General Availability (GCC High): We will begin rolling out mid-May 2025 and expect to complete late May 2025. General Availability (DoD): We will begin rolling out mid-August 2025 and expect to complete late August 2025. How this will affect your organization: Users will have the ability to use line keys on touch phone devices. To assign line keys, tap on pre-defined placeholders and choose a contact to be added as a speed dial. Once you add a speed dial, you can make outgoing calls through one-touch/press on those line keys. What you need to do to prepare: Please ensure that your Teams phone devices are updated with the latest Microsoft Teams application. This feature will only be available with the latest application update. Lastly, for this feature to work, you will need to assign line keys on the device. MC994287 — Microsoft Teams: Webinars will be generally available (DoD) Microsoft 365 Roadmap ID 475279 Webinars in Microsoft Teams will soon be generally available. After this rollout, users will be able to schedule webinars with internal audiences and use capabilities such as creating an event page, sending attendee registration automated emails, and more. This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams for the web. Teams for iOS/Android users can attend webinars but not schedule them. When this will happen: General Availability (DoD): We will begin rolling out late March 2025 and expect to complete by mid-April 2025. How this will affect your organization: This change will be available 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 users about this change and update any relevant documentation. User documentation: Get started with Microsoft Teams webinars - Microsoft Support MC993227 — Microsoft Teams: Native Bluetooth call controls using hands-free protocol for multiple peripheral devices Microsoft 365 Roadmap ID 475853 Coming soon for Microsoft Teams: When you have several peripheral devices connected to Teams, the one you use to answer a call will temporarily become the main device that will sync with Teams when using the device's buttons. After the call, the original device selected in Teams settings will take over again as the main device. After this rollout, users can use multiple native Bluetooth devices can be confident that call controls will function correctly with all of them. This message applies to Teams for Windows desktop. When this will happen: Targeted Release: We will begin rolling out early March 2025 and expect to complete by late March 2025. General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-March 2025 and expect to complete by mid-April 2025. How this will affect your organization: After this rollout, users will be able to switch between their connected peripheral devices when answering a call without manually changing the selected device in Teams settings. This change will be available 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 users about this change and update any relevant documentation. Learn more: Phones and Devices for Microsoft Teams - Microsoft Teams | Microsoft Learn Before rollout, we will update this post with new documentation MC993226 — Microsoft Teams: New location sharing settings for emergency calls and other features Microsoft Teams will soon have a new location sharing setting that will allow users to grant location access to specific features. This change will affect emergency dynamic policy and the network bandwidth policy. This message applies to Teams for Windows desktop (version 24H2 or greater) and Teams for Mac desktop. VDI clients will not be supported at this time. When this will happen: Targeted Release: We will begin rolling out early February 2025 and expect to complete by mid-February 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 and expect to complete by early March 2025. How this will affect your organization: Before this rollout: Location access was governed exclusively at the operating system level. With this update, location consent will also be required from users at the individual application level. As a result, users gain more granular control over which specific application features can access their location. After this rollout, Teams users can grant location access to certain Teams features. The setting for IT insights for admins feature are in Teams Settings > Privacy > Location. The setting for the Emergency calls feature is in the user's device's location settings. The user can find a link to their device's location settings in Teams Settings > Privacy > Location: If a user consented to location access before the rollout, the user will be prompted to confirm their selection in this new popup that will display after the next Teams version update. If a user has not previously consented, they will not see the popup and can adjust their preferences in Settings. What you need to do to prepare: NOTE: After this rollout, dynamic emergency calling may not work as intended unless users allow location detection at the operating system level and app level. This dynamic emergency calling issue includes scenarios where admins have configured a network site for their users (location must be enabled by the user). To ensure emergency calls are properly routed to the nearest public safety answering point (PSAP), please advise your users to accept the new location requests from Teams. This also applies to users who may have consented to location access before the rollout. You can communicate this requirement by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that end users have location turned on is crucial for proper functioning of emergency calls and their safety. Learn more about sending a custom message: Manage emergency calling policies in Microsoft Teams - Microsoft Teams | Microsoft Learn To continue managing video and media settings with the network roaming policy, users must enable Insights for IT admins in Teams Settings > Privacy > Location > Insights for IT admins. Learn more about the changes to location services and privacy policies Windows location service and privacy - Microsoft Support Enable location sharing - Microsoft Support(will be updated before rollout) 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. Please notify your users and admins about this change and update any relevant documentation. MC989975 — Microsoft Teams: Occupancy status on Teams panels Microsoft 365 Roadmap ID 474441 Before this rollout, Microsoft Teams panels indicate a room availability based only on reservation data. After this rollout, Teams panels can smartly utilize signals from Teams Rooms devices and occupancy sensors paired with Teams panels to indicate when a room is in use, so users are not surprised to find an available room is actually occupied. This feature will be supported for accounts with a license for Microsoft Teams Rooms Pro or Microsoft Teams Shared Devices. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late March 2025 and expect to complete by early April 2025. How this will affect your organization: After this rollout, this feature will be set to on by default, so the current experience will change. The room is in use when the room is not currently reserved and a user is in a call, presenting, whiteboarding, or casting with a Teams Rooms device, or the room is detected as occupied through a paired occupancy sensor. When the room is in use, the panel's LED will adjust to the color selected by the admin for the busy state. In addition, the panel's home screen will reflect that the room is occupied. Note: The room can still be reserved on the device itself, through Microsoft Outlook, or through Microsoft Teams. If the device is paired with a Microsoft Teams Rooms on Android, after a user reserves the occupied room from the device, a message will appear on the room display to let the user inside of the room know that the room has been reserved and to exit. This notification will be off by default, and the admin will need to enable it after pairing the device. An admin can choose to turn off these features in Teams admin settings > Device settings > Occupied state. The two settings are Allow occupied state and Allow booking notifications. If Allow occupied state is turned off, the booking notifications also will be turned off. 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. Before rollout, we will update this post with revised documentation. MC989974 — Microsoft Teams: New microphone volume indicator for users Microsoft 365 Roadmap ID 468274 Coming soon for Microsoft Teams: A new Mic volume indicator on the user bar in Teams meetings. This feature will provide users with real-time visual feedback on their audio levels in the meeting, eliminating the need to ask, “Can you hear me?” This feature is designed to minimize interruptions as well as enhance user confidence and meeting effectiveness. This feature applies to Teams on Windows desktop and Mac desktop. When this will happen: Targeted Release: We will begin rolling out in early March 2025 and expect to complete by mid-March 2025. General Availability (Worldwide, GCC): We will begin rolling out in late March 2025 and expect to complete by late April 2025. General Availability (GCC High): We will begin rolling out in mid-May 2025 and expect to complete by mid-June 2025. General Availability (DoD): We will begin rolling out in late June 2025 and expect to complete by early August 2025. How this will affect your organization: This feature will be available to users by default and has no admin policy. Users can select the Mic icon and review the Microphone section of the menu to find out more about their audio levels in the meeting: 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: Muting and unmuting your mic in Microsoft Teams - Microsoft Support MC985484 — Microsoft Teams: Additional work information in people search results Multi-tenant organization (MTO) users will be able to see additional work information in people search results. With this feature, MTO users will be able to see the company name and department name of a user in people search results, helping users to make sure they are communicating with the right people. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early February 2025 and expect to complete by late February 2025. How this will affect your organization: Tenant admins who have MTO enabled will be able to toggle this feature on and off in the Teams admin center. Toggle behavior: This toggle will be off by default. Turning on the toggle will enable the ability to see company name and department name in results. Turning off the toggle will disable the ability to see company name and department name in results. Instructions to toggle: Navigate to the Teams admin center (TAC). Navigate to the Teams Client Config page. Using the Enable Extended Work Info in People Search toggle: Switch the toggle to on to enable the ability to see company name and department name in results. Switch the toggle to off to disable the ability to see company name and department name in results. For more information, see Set up a multitenant org in Microsoft 365. What you need to do to prepare: Tenant admins will need to complete cross-tenant synchronization and sync the company name field in order to take advantage of this feature. For more information, see Synchronize users in multitenant organizations in Microsoft 365. MC981629 — Microsoft Teams: Updates to make meeting transcripts more accurate and reliable Microsoft 365 Roadmap ID 471426 Coming soon to Microsoft Teams: Updates to make meeting transcripts more accurate and reliable. These improvements will also enhance the quality of live captions in Teams, Microsoft Copilot in Teams, and intelligent meeting recap for Microsoft Teams Premium users and users with a Copilot license, ensuring more accurate outputs and enhancing the overall experience of each feature. This message applies to Teams for Windows desktop and Teams for Mac desktop. When this will happen: Targeted Release: We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (Worldwide, GCC): We will begin rolling out late February 2025 and expect to complete by early March 2025. General Availability (GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. How this will affect your organization: Key changes in this rollout: Setting the meeting spoken language up front: Before starting features like Recording, Transcription, or Copilot that generate transcripts, users will be prompted to set the spoken language. Whether users enable these features manually or through Meeting options, this change ensures the transcription system starts with the correct language configuration. Limiting who can change the spoken language for a meeting: When transcription is enabled, either on its own or as part of Recording or Copilot, only the meeting organizer, co-organizer, or the person who started the transcript will be allowed to change the spoken language. This ensures consistency and prevents issues caused by mismatched language settings. If transcription is not enabled, any meeting participant can change the spoken language. Simplifying language settings: Language settings and caption customization options are on separate screens, instead of overwhelming users with all options in a single screen. Identifying language mismatches: A Language mismatch detected notification will appear onscreen if the spoken language does not match the settings. Users can quickly resolve mismatches by confirming the system’s language suggestion directly from the notification, avoiding the need to navigate through settings. This change will be available to users by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or after 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. Before rollout, we will update this post with revised documentation. MC980799 — Microsoft Teams: Allow presenters to moderate Q&A Microsoft 365 Roadmap ID 469492 Coming soon for Microsoft Teams: Organizers of town halls and webinars will be able to select and assign presenters to also moderate the Q&A, allowing them to manage and publish questions asked during the event. This feature lets organizers make changes to the group of moderators at any time (before or during the event), and it is available to all users organizing a town hall or webinar. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late February 2025 and expect to complete by early March 2025. How this will affect your organization: This feature is supported for presenters with Microsoft Azure Active Directory (AAD) IDs. Presenters using consumer domains (such as live.com or gmail.com) are not supported. Meeting organizers can enable this feature in Meeting options while setting up the event or during the event. This feature will be available by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or after 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: Q&A in Microsoft Teams meetings - Microsoft Support (will be updated before rollout) MC979828 — Microsoft Teams: Cross-cloud collaboration in Virtualized Desktop Infrastructure Microsoft 365 Roadmap ID 471434 Microsoft Teams Virtualized Desktop Infrastructure (VDI) users can join meetings with people in other Microsoft 365 cloud environments (e.g. a user in GCC High joining a meeting in Worldwide, GCC, or DoD environments) through three options: Authenticated access via cross-cloud meeting connection. Authenticated access using a guest account. Anonymous access. These scenarios require the new Slimcore-based optimization, since WebRTC-based optimization does not support meetings across different cloud environments. For more information on the new optimization, see New VDI solution for Teams. When this will happen: General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. How this will affect your organization: For users who are already optimized with SlimCore in their VDI environments, after this feature is rolled out, cross-cloud anonymous and cross-cloud authenticated meetings will now open in Teams desktop client, and users with Guest Access in another cloud will be able to switch tenants via their Account picker in the Teams Settings UI. What you need to do to prepare: To access this new feature, enable the new VDI optimization based on SlimCore. MC978932 — Large Events: End Session for Attendees and Return Presenters to Green Room Microsoft 365 Roadmap ID 470432 Organizers and presenters can now end the session with this new "End Event" button for town halls, webinars, and structured meetings. After selecting this button, attendees will see a message on stage stating that the session has concluded, and presenters will return to the Green Room. When this will happen: Targeted Release: We will begin rolling out early February 2025 and expect to complete by mid-February 2025. General Availability (Worldwide): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (GCC): We will begin rolling out late February 2025 and expect to complete by early March 2025. General Availability (GCC High and DoD): We will begin rolling out late March 2025 and expect to complete by early April 2025. How this will affect your organization: When users join a town hall, webinar, or structured meeting with Green Room turned ON, they will now see the "End event" or "End meeting" button: What you need to do to prepare: This feature change will be available once it is fully released in your tenant. MC975308 — (Updated) Microsoft Teams: iPad Multi-window support Microsoft 365 Roadmap ID 467246 Updated January 17, 2025: We have updated the rollout timeline below. Thank you for your patience. Teams now supports multiple windows on iPad. With this 'multi-window' feature, users can easily manage different Teams windows side-by-side, increasing productivity and flexibility. When this will happen: General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out mid-March 2025 (previously early February) and expect to complete by late March 2025 (previously late February). How this will affect your organization: Apple's "split view" capability allows iPad users to have multiple applications and windows open side-by-side. Starting in February, Teams will now support the ability for there to be multiple Teams windows open at once. This makes it easier for users to attend a meeting and have their chat open on the other side or use Stage Manager to move windows to external displays. This feature is available by default when users update the Teams app on iPad. 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. MC975304 — Microsoft Teams: The Approvals app is generally available (DoD) Microsoft 365 Roadmap ID 473448 The Approvals app in Microsoft Teams is a way to streamline requests and processes with a team or partners. Users will be able to create new approvals, view pending approvals, and see previous ones in one place. Users with an F3 license or above can take advantage of the Approvals app in Teams: Office 365 Government G1 Office 365 Government G3 Office 365 Government G5 Office 365 Government F3 If you do not have users that meet the licensing requirement, you may safely ignore this message. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. When this will happen: General Availability (DoD): We will begin rolling out early February 2025 and expect to complete by mid-February 2025. How this will affect your organization: Approvals is a native Teams application that lets users easily create, manage, and share approvals from a hub for teamwork. These approvals are triggered directly with the Power Automate infrastructure and do not require a flow with an approvals action. Users see all of their approvals in the hub, including the approvals that have been completed. Approvals show up across all of a user's systems, including Power Automate, SharePoint, and Microsoft Dynamics 365: What you need to do to prepare: The Approvals app is on by default if your tenant has enabled Microsoft Power Automate. As an admin, you can manage the Approvals app in the Teams admin center on the Approvals app page, including customizing which users can access the app with permission policies. Currently, all approvals are created in your organization's default environment. The Approvals app page in the Teams admin center: Learn more Approvals in Microsoft Teams - Power Automate | Microsoft Learn Manage the Approvals app in Microsoft Teams - Microsoft Teams | Microsoft Learn What is Approvals? - Microsoft Support 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. In October 2027, we will remove the option to specify the need for passcodes. This change will ensure that all meetings are consistently secured with passcodes. This final step will simplify the meeting creation process and provide an additional layer of protection for users. We will remove the isPasscodeRequired property on the joinMeetingIdSettings resource of the Microsoft Graph online meetings API. MC974361 — (Updated) Microsoft Teams: Edit your display name in meetings Microsoft 365 Roadmap ID 122934 Updated January 21, 2025: We have updated the rollout timeline below. Thank you for your patience. In Microsoft Teams, while in a live meeting, participants will soon be able to edit their display name for the duration of the meeting. This name change is for the meeting duration only and does not affect a participant's original name on their People card. This feature is available for participants using the Teams desktop and web apps for both Windows and Mac. When this will happen: Targeted Release: We will begin rolling out early March 2025 (previously February) and expect to complete by mid-March 2025 (previously mid-February). General Availability (Worldwide, GCC): We will begin rolling out early April 2025 (previously mid-March) and expect to complete by mid-April 2025 (previously early April). General Availability (GCC High, DoD): We will begin rolling out late April 2025 (previously early April) and expect to complete by mid-May 2025 (previously mid-April). How this will affect your organization: The feature is off by default for all tenants. Admins can turn it on for their organization in the Teams admin center for all or selected tenant members. These members can then enable the feature in their private scheduled meetings. If turned on for the tenant, a meeting organizer can turn the feature on for their meeting in Meeting options > Let people edit their display name. The feature is OFF by default in Meeting options and has to be enabled by meeting organizer. If turned on for a meeting, participants can join the meeting and then select People at the top of the screen to edit their own display names in the Participants panel. Example: Daniela Mandera can change her name in a meeting to Daniela M. (Before rollout, we will update this post with revised user documentation for changing the name.) Participants who have edited their names will have an (edited) label next to their name in the meeting screens. *Original People card names will display in some meeting features such as calendar invites, the list of people invited to meetings, group chat rosters, and so on. Permanent meeting artifacts (such as the attendance report and transcriptions) will not reflect name changes. What you need to do to prepare: You can turn this feature on for your tenant users to allow the capability in the meetings they organize. You might want to notify your users about this new feature and update your training and documentation as appropriate. MC973513 — Simplify UX flow to enable Together Mode Microsoft 365 Roadmap ID 470427 Together mode will get a new simplified flow which will take the user from the beginning to the end through the steps of setting up the scene, assigning the seats and applying for everyone in the call in a transparent and easy-to-understand way. When this will happen: Targeted Release: We will begin rolling out mid-February 2025 and expect to complete by early March 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early March 2025 and expect to complete by mid-March 2025. How this will affect your organization: With the improved experience, the function itself does not change but there will be more transparency thanks to the icons on the meeting toolbar for an easy access for each next step in the familiar Together mode flow. What you need to do to prepare: You may consider updating your training and documentation as appropriate. MC973502 — Microsoft Teams: New "Tag mentions" filter for the Activity feed Microsoft 365 Roadmap ID 470598 Coming soon to Microsoft Teams: Users will have a new Tag mentions filter in the Activity feed to see their tag mentions in their chat and channel messages. The existing @Mentions filter allows users to catch up quickly on personal mentions. When this will happen: Targeted Release: We will begin rolling out early February 2025 and expect to complete by early February 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. How this will affect your organization: This change will be available by default. There are no tenant level settings. Defaults will not change. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or rafter the rollout. You may want to notify your users about this change and update any relevant documentation. User documentation: Explore the Activity feed in Microsoft Teams - Microsoft Support (will be updated before rollout) MC973497 — Microsoft Teams: The Updates app is generally available (GCC) Coming soon to Microsoft Teams: Users can access the Updates app to streamline their daily reporting workflow and increase collaboration efficiency. Users can use the Updates app to set up a daily or weekly reporting form and workflow to collect regular updates from others. When this will happen: General Availability (GCC): We will begin rolling out early January 2025 and expect to complete by late January 2025. How this will affect your organization: Learn more about how to manage the app: Manage the Updates app for your organization - Microsoft Teams | Microsoft Learn. This change is available by default. What you need to do to prepare: This rollout will happen automatically with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. User documentation: Get started in Updates - Microsoft Support MC971032 — (Updated) Microsoft Teams: New recording policies for town halls and webinars Microsoft 365 Roadmap ID 473887 Updated January 24, 2025: We have updated the content. Thank you for your patience. Coming soon to Microsoft Teams: New admin policies in the Teams admin center and Microsoft PowerShell that govern the recording behavior for town halls and webinars. Before this rollout, the same policies control the recording behavior for town halls, webinars, and meetings. After this rollout, separate recording policies for town halls and webinars will be available to more finely control event behavior. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early March 2025 (previously mid-February) and expect to complete by mid-March 2025 (previously late February). How this will affect your organization: This change will be available by default. What you need to do to prepare: Before the rollout, we encourage you to use PowerShell commands to update the default values of the recording policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values. Examples of PowerShell commands to set the town hall or webinar recording policy: Set-CsTeamsEventsPolicy -Identity Global -RecordingForTownhall Enabled Set-CsTeamsEventsPolicy -Identity Global -RecordingForWebinar Enabled 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: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn MC971031 — (Updated) Microsoft Teams: New transcription policies for town halls and webinars Microsoft 365 Roadmap ID 473886 Updated January 24, 2025: We have updated the content. Thank you for your patience. Before this rollout, for a Microsoft Teams town hall or webinar, the transcription behavior respects the current Teams meeting transcription policies. After this rollout, new transcription policies will be available for town halls and webinars to allow finer control over transcriptions. The policies may be changed in the Teams admin center or with Microsoft PowerShell commands. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early March 2025 (previously mid-February) and expect to complete by mid-March 2025 (previously late February). How this will affect your organization: These new transcription policies for webinars and town halls will determine whether transcription is allowed for a town hall or webinar. Town halls and webinars will no longer respect the Teams Meeting transcription policies. The new policies will be available by default for admins to configure. What you need to do to prepare: Before the rollout, we encourage you to use PowerShell commands to update the default values of the transcription policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values. Examples of PowerShell commands to set the town hall or webinar policy: Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForTownhall Enabled Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForWebinar Enabled 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: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn MC960811 — (Updated) Microsoft Teams: Enhanced captions for Teams Rooms on Windows Microsoft 365 Roadmap ID 423089 Updated January 24, 2025: We have updated the content. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that captions will soon support additional languages and translation capabilities. This enhancement aims to improve meeting accessibility and inclusivity for non-English speaking users using Teams Rooms on Windows. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). General Availability (GCC High): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). General Availability (DoD): We will begin rolling out early Mary 2025 (previously early April) and expect to complete by mid-May 2025 (previously mid-April). How this will affect your organization: Before the rollout: Captions in Teams Rooms on Windows only support the English language, which limits usability for non-English speaking users as the captions will result in gibberish if the actual spoken language in the meeting is non-English. There is also no way for admins to set default caption settings. After the rollout Additional languages: Users can select from a list of supported languages for captions, ensuring that captions are accurate and meaningful for non-English speakers. Users can change the meeting spoken language directly from Teams Rooms devices by selecting More > Captions > Meeting spoken language. Real-time translation: Users can translate the meeting's spoken language if the room account has a Teams Rooms Pro license or if the meeting organizer has a Teams Premium license, allowing for real-time translation of captions. Users can translate captions by selecting More > Captions > Translation language. Admin controls: For room accounts with Teams Rooms Pro license, admins can change system defaults, turn on captions by default for calls and meetings, and turn off filtering of profanity in captions and transcripts as necessary with these XML settings: <CaptionsDefault>true</CaptionsDefault> <FilterProfaneWords>false</FilterProfaneWords> As an admin, you can allow or prevent users (including room accounts) from having access to this feature by configuring calling and meeting policies in the Teams admin center. Learn more: Enable call captions - Microsoft Teams | Microsoft Learn and Manage live captions - Microsoft Teams | Microsoft Learn. This feature is available by default. What you need to do to prepare: After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and settings, 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. MC960809 — (Updated) Microsoft Teams: Live transcription for Teams Rooms on Windows Microsoft 365 Roadmap ID 423088 Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that users can soon start and stop transcription as well as view the meeting transcript directly from Teams Rooms on Windows devices. This feature requires a Teams Rooms Pro license. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February) General Availability (GCC High): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). General Availability (DoD): We will begin rolling out early May 2025 (previously early April) and expect to complete by mid-May (previously mid-April). How this will affect your organization: Before the rollout: When joining a meeting on Teams Rooms on Windows, users must also join the meeting on a companion device to start transcription. Also, even when transcription has been started, users can't view the transcript from the front of room display. After the rollout: Users can select More > Record and transcribe > Start transcription or Stop transcription directly from the Teams Rooms on Windows device. Start/stop transcription is supported in any meeting where a participant belongs to the same tenant as the organizer. When users transcribe a Meet now or Whiteboard session initiated from a Teams Rooms on Windows device, users must ensure that they invite themselves to the meeting so that they can access the transcript after the meeting through the meeting chat on their Teams desktop or mobile app. After transcription is started, users can show/hide the transcript panel on the front of room display in any meeting layout: Select More> Record and transcribe > toggle On/Off Show transcript. Select View> Front row > open the left/right panel dropdown > select/unselect Transcript. Users can also set the meeting spoken language, translate the transcript, and choose to show the original language and translated language side by side, ensuring accurate and meaningful transcription. 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 transcribing meetings with a policy in the Teams admin center. Learn more: Manage transcription for Teams meetings | Microsoft Learn. NOTE: Both the meeting organizer and the transcription initiator (room account) need to have permissions to transcribe the meeting. If the meeting organizer uses Meeting options to remove the room account's permissions, the start/stop transcription button will not be available. For room accounts with a Teams Rooms Pro license, you have the option to turn off the filtering of profanity in transcripts using this XML setting: <FilterProfaneWords>false</FilterProfaneWords> Start/stop transcription is not supported in these scenarios: Teams calls including P2P, group, and PSTN calls External and cross-tenant Teams meetings and calls Third-party meetings and calls including Direct Guest Join and SIP What you need to do to prepare: After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and setting, 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. MC956699 — (Updated) Microsoft Teams: Forward messages with app cards Microsoft 365 Roadmap ID 469506 Updated January 17, 2025: We have updated the rollout timeline below. Thank you for your patience. We are introducing the ability to forward app cards. With the addition of app card forwarding, users now have a new way to share app cards across chats. To forward a message containing an app card, simply navigate to the More Actions menu of any message containing an app card and select forward. From here, the forward message dialog will populate, which provides users with a preview of the message being forwarded, including the app card. Please note: Forwarding of bot cards is excluded from this release. When this will happen: Targeted Release: We will begin rolling out early February 2025 (previously early January) and expect to complete by mid-February 2025 (previously mid-January). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously late January) and expect to complete by early March 2025 (previously early February). How this will affect your organization: Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained app cards. With this improvement, this restriction does not exist. What you need to do to prepare: Users must have the latest Microsoft Teams build to receive these updates. You may want to notify your users about this change and update any relevant documentation as appropriate. MC952888 — Microsoft Teams: Pop out Chat, Copilot, and Notes panes in meetings Microsoft 365 Roadmap ID 421607 Coming soon: Users will be able to pop out the side panes for Notes, Chat, and Microsoft Copilot panes in Microsoft Teams meetings Note: The Copilot pane is only available in Worldwide environments with a Microsoft 365 Copilot license. When this will happen: Targeted Release: We will begin rolling out mid-January 2025 and expect to complete by early February 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early February 2025 and expect to complete by late February 2025. How this will affect your organization: After the rollout, users will see a pop-out icon at the top of their Notes, Chat, and Copilot side panes in Teams meetings. This change will be on by default. When users select the icon, the pane will pop out into a separate window that the user can resize and drag to their desired position, based on their screen setup and their productivity goals for the meeting. Users can view multiple meeting features at the same time, so they don’t miss the chat while they are monitoring meeting 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. Please notify your users about this change and update any relevant training documentation. MC950898 — (Updated) Microsoft Teams: Forwarding loop components Microsoft 365 Roadmap ID 469507 Updated January 7, 2025: We have updated the rollout timeline below. Thank you for your patience. There is now the ability to forward loop components in Microsoft Teams. With the addition of loop component forwarding, users have a new way to share loop components across chats and channels. To forward a message containing a loop component, simply navigate to the more actions menu of any message containing a loop component and select forward. From there, the forward this message dialog will populate, which provides users with a preview of the message being forwarded, including the loop component. In this view, users will be able to give permissions to recipients of the loop component to ensure all recipients have access to the content. When this will happen: Targeted Release: We will begin rolling out in early January 2025 and expect to complete by mid-January 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late January 2025 and expect to complete by early April 2025 (previously early February). How this will affect your organization: Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained a loop component. With this improvement, no such restriction exists. This update is available by default. For additional information, see Forward a message in a Teams chat - Microsoft Support. 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. MC946818 — (Updated) Microsoft Teams: Updates to Gallery in Teams Rooms on Windows Microsoft 365 Roadmap ID 468277 Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Windows, the updated Gallery view introduces these changes to enhance your meeting experience: All participants will appear in consistent tile sizes By default, video participants have priority and appear first on the meeting stage by default (audio participants appear on the side or bottom of the screen) Ability to disable priority on video participants to create a mix of audio participants and video participants in the Gallery Optimized view of up to 25 participants on a single display and up to 50 participants on dual displays Preview video is part of the Gallery, appearing next to the rest of the participants Ability to hide the preview video across all layouts When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). How this will affect your organization: The updated Galleryprovides a unified meeting experience across both Teams Rooms and desktop. A more consistent and predictable layout can drive meeting efficiency and visibility for remote participants in hybrid meeting scenarios. In 1:1 meetings, the preview video will be positioned at the bottom right, overlapping the other participant. In group meetings, the preview video will be on the last available tile in the Gallery, next to the rest of the participants. Admins can use two new settings to adjust the default view: Prioritize vide0;< PrioritizeVideoParticipantsGallery> – Default value is True. The default experience will show video participants on the main stage with audio participants on the side or bottom rail. If you would like to display all audio and video participants mixed in the Gallery, change the value to False. Hide me <HideMeForAllLayout> – Default value is False. If you would like to hide preview video across all layouts in Teams Rooms on Windows, change the value to True. In-room users can adjust these settings on the console during a meeting, if desired. Lastly, when another Teams Room joins the meeting, the video of the room automatically enlarges if there are more than two in-room users, providing a clearer view and better connection, and so users can focus on the person speaking. These changes will be available by default. What you need to do to prepare: Please notify your users about this change and update any training documentation, as appropriate. 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 Remotely manage Microsoft Teams Rooms device settings - Microsoft Teams | Microsoft Learn(will be updated before rollout) Microsoft Teams Rooms (Windows) - Microsoft Support(will be updated before rollout) MC939927 — (Updated) Microsoft Teams Premium: Decorate your background Microsoft 365 Roadmap ID 419811 Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. We will not release this feature to DoD at this moment. We are sorry for any inconvenience. We will share DoD timeline when available. Microsoft Teams Premium users will be able to use the "Decorate your background" generative background effect in the GCC, GCC High, and DoD environments, leveraging gen-AI to augment real-life surroundings. It creates a personalized atmosphere for video calls. When this will happen: General Availability (GCC): We will begin rolling out in early March 2025 (previously early February) and expect to complete rollout by mid-March 2025 (previously late February). General Availability (GCC High): We will begin rolling out in mid-March 2025 (previously mid-February) and expect to complete rollout by late March 2025 (previously late February). General Availability (DoD): We will communicate via Message center when we are ready to proceed. How this will affect your organization: “Decorate your background” transforms meeting backgrounds by blending with a user’s real-life surrounding, creating a personalized atmosphere for video calls. It is available to Teams Premium users, and it is supported on Microsoft Windows and MacOS client now. There is not admin policy to disable it. Users can access this feature in the following ways: Before a meeting starts on the pre-join screen, select Effects and Avatars> Video effects > Decorate button. This will allow you to start generating new backgrounds. During a meeting, select an animated background by clicking video flyout > More Video Effects and Setting > Decorate. 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. MC932488 — (Updated) Microsoft Teams: New DVR capabilities for town halls (desktop and web) Microsoft 365 Roadmap ID 422804 Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Teams: New DVR (digital video recording) functionality for all town halls. This new feature will allow town hall attendees on Windows desktop or the web to interact with a live streaming town hall in the same way they would interact with recorded content. DVR functionality in the town hall enables event attendees to pause and move forward or back in a town hall, navigate to any previous timestamp, and other abilities, making it more convenient to interact with a town hall more and easier to digest the content being presented. This feature is available for Teams town halls from all organizers, regardless of the license assigned to the organizer. When this will happen: Targeted Release: We will begin rolling out early March 2025 (previously early February) and expect to complete by mid-March 2025 (previously mid-February). General Availability (Worldwide): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March (previously late February). General Availability (GCC): We will begin rolling out late March 2025 (previously late February) and expect to complete by early April 2025 (previously early March) How this will affect your organization: After this rollout, the DVR controls will appear when attendees hover their mouse over the content being presented in the town hall. Attendees can: Pause, play, and skip 10 seconds forward or backward Control the volume of the content with the volume control Jump to any point in time, starting from the beginning of the event Catch up with the content and join the live event by selecting the Watch Livebutton next to the volume control The DVR controls are at the bottom of the Teams window when the Q&A page is open on the right side. We are committed to continuously improving the Microsoft Teams experience and are excited to bring this new capability to our customers. This feature will be available 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 users about this change and update any relevant documentation. Learn more: Plan for Teams town halls - Microsoft Teams | Microsoft Learn (will be updated before rollout) MC929034 — (Updated) Microsoft Teams: Best practices configuration dashboard in Teams admin center Microsoft 365 Roadmap ID 421185 Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams: With the Best practice configurations monitoring dashboard in the Teams admin center, Teams admins will be able to monitor the conformance of your tenant to the Microsoft recommended best practices for an optimal collaboration experience on Teams. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). How this will affect your organization: Ensuring the quality and reliability of user's collaboration experience using Teams is crucial (specially the meeting-related experiences). Microsoft recommends best practices to ensure that organizations have an optimal environment setup for collaboration. The Best Practice Configurations monitoring dashboard will assist admins in understanding their tenant’s non-conformance with these best practices, the overall impact, and how to comply with these recommendations. You'll find the Best practice configurations dashboard in the Meetings section of the Teams admin center. In this release, we’ll monitor and highlight non-conformance in three key areas: Update out-of-date client versions Enable the right ports and protocols Implement split tunnelling for VPNs If a location does not adhere to these best practices, it will be highlighted on the dashboard. A widget on the main dashboard will also spotlight non-conforming practices. Also, a list of subnets/IP addresses will be displayed by city, showing the extent of non-conformance for each location. This list can be exported to share with relevant teams, and recommendations for addressing these issues will be available on the same page. As these issues are resolved, the trend of non-conforming locations will be tracked to help monitor progress. This new dashboard will be available by default. What you need to do to prepare: Administrators do not need to do anything to prepare for these changes. They will take effect automatically. You may want to notify your admins about this change and update any relevant documentation. Before rollout, we will update this post with revised documentation. MC923415 — (Updated) Microsoft Teams: Virtualized Desktop Infrastructure status indicator Microsoft 365 Roadmap ID 423472 Updated December 10, 2024: We have updated the rollout timeline below. Thank you for your patience. 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 the ellipsis (...) > Settings > About menu 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 February 2025 (previously mid-January) and expect to complete by mid-February 2025 (previously late January). General Availability (Worldwide, GCC): We will begin rolling out mid-February 2025 (previously late January) and expect to complete by late February 2025 (previously early February). 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. MC920179 — (Updated) Microsoft Teams: The new streamlined Chat and Channels experience Microsoft 365 Roadmap ID 415249 Updated January 17, 2025: We have updated the content. Thank you for your patience. Thank you for your engagement with the new chat and channels experience in Teams. The new chat and channels experience has been in Public Preview and Targeted Release since November 2024 and was targeted for General Availability starting in late January 2025. Based on requests from customers to have additional time to prepare their organizations for the change, we will be postponing the rollout to General Availability from January to a later date. The GA rollout date is updated to starting late March 2025. 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 to Microsoft 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: 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 March 2025 (previously late January) and expect to complete by early April 2025 (previously early February). General Availability (GCC, GCC High, DoD): We will begin rolling out mid-June 2025 (previously mid-April) and expect to complete by late June 2025 (previously late April). How this will affect your organization: Before this rollout, users have separate Chat and Teams views (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, in Chat, so users can easily navigate between all conversations without switching between contexts. Users start in the combined Chat view but can opt to keep chat separate from teams and channels like before. In the Chat view, users will see these sections (in order): Favorites containing any previously pinned chats and channels Chats sorted by most recent Teams and channels, organized in same order as in the Teams view Also, users can create custom sections to organize projects and topics that can include individual, group, and meeting chats, as well as channels. New filters for Unread, Chat, Channels, Meetings and 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. Use /go to: Quickly navigate to your frequently used conversation across your chat and channels with a new keyboard shortcut Ctrl+G (Cmd+G on Mac). Customizing the experience Users can tailor their chat and channels experience in Teams Settings. Users can choose to keep chat, teams, and channels combined in Chat (default) or switch to separate Chat and Teams views. In the combined Chat view, message previews are off by default to simplify the list. Users can turn on message previews in Settings. When using the separate Chat and Teams views, 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. 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 page The new Microsoft Teams chat and channels experience before rollout begins. For admins who opt in to emails for recommended Microsoft 365 training, an email for users will summarize the update when released. MC920084 — (Updated) Microsoft Teams: Usage reports for bookable desks Microsoft 365 Roadmap ID 421604 Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. 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. 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 late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). General Availability (GCC): We will begin rolling out late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). How this will affect your organization: The Teams Rooms Pro Management portal will have a new tab under Reports called Desk usage. Desk pools that have at least one peripheral associated 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. 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 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. Reports for desk pools will be in public preview and available with no licensing requirement until July 2025. More information on licensing requirements will be provided prior to that date. Learn more: Setting up Bookable Desks in Microsoft Teams - Microsoft Teams | Microsoft Learn (will be updated soon after rollout) MC918570 — (Updated) Microsoft Teams: Custom name on Teams panels Microsoft 365 Roadmap ID 417153 Updated January 14, 2025: We have updated the content. Thank you for your patience. 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 January (previously early December) and expect to complete by mid-January 2025 (previously mid-January). 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 to Teams Rooms Pro Management Portal > Planning > Inventory and then click 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. Please update to 1449/1.0.97.2024122401 to use this feature. MC916866 — (Updated) Microsoft Teams: Shifts Graph APIs in beta moved to production (v1.0) Microsoft 365 Roadmap ID 422813 Updated December 20, 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-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). 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 to Teamwork 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. MC912709 — (Updated) Microsoft Teams: Bookable desks and BYOD rooms supported in GCC Updated February 4, 2025: We have updated the content. 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 late January 2025 (previously early January) and expect to complete by early February 2025 (previously mid-January). 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, please see our desk and room guides. We also have a user support article for desks and rooms. 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 Supportand Use 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 ID 413708 Updated January 31, 2025: We have updated the rollout timeline below. Thank you for your patience. A new csTeamsAIPolicy policy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-March 2025 (previously mid-February) 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 enrollment will 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: The new Microsoft PowerShell cmdlets are available now for admins to configure, to ensure a smooth transition. 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-March 2025 (previously mid-February) and is expected to be fully in effect by late March 2025 (previously late February). How this will affect your organization: Before this rollout, the current policy csTeamsMeetingPolicy has 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 new csTeamsAIPolicy will replace the existing enrollment setting in csTeamsMeetingPolicy. The new csTeamsAIPolicy has two settings, EnrollFace and EnrollVoice, that will be set to Enabled by 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 If your organization prefers to disable voice and face enrollments, review and update your settings before mid-February 2025. Important: The EnrollUserOverride setting can be assigned globally, directly to users, or to groups in PowerShell. Admins must ensure that changes are applied consistently across all these locations to avoid unintended configurations. MC908117 — (Updated) Microsoft Teams: Swap screens on Teams Rooms on Android Microsoft 365 Roadmap ID 415243 Updated January 28, 2025: We have updated the content. Thank you for your patience. 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-February 2025 (previously mid-January). 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 NOTE: If you are deploying Teams Rooms on Android devices with dual displays, be aware that dual display mode must be explicitly enabled in the configuration profile. By default, the dual display setting is OFF, which means that using an existing configuration profile (designed for single-display devices by default) may inadvertently disable dual display mode for your existing dual display rooms. To avoid this, you must create and maintain a separate configuration profile for any devices that require dual display support. 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. MC907108 — (Updated) Microsoft Teams: Admin email support for "Report a problem" on Teams Rooms on Android Microsoft 365 Roadmap ID 415247 Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams Rooms on Android: As an admin, you can configure an email address for receiving issues submitted by users through the Report a problem feature 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. 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-February 2025 (previously mid-January ). 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, the Report a problem option on Teams Rooms on Android devices will be enabled, and any feedback submitted by room users using Report a problem will 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. Users can access Report a problem from the Help button on the home screen or the More button in meetings. Report a problem can 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, see Collect 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 — (Updated) Microsoft Teams: Net Promoter Score survey on Teams Rooms on Android Microsoft 365 Roadmap ID 415245 Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. 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. 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-February 2025 (previously mid-January). 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 at Manage 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 ID 415239 Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience 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 January 2025 (previously late December) 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. MC889534 — (Updated) Microsoft Teams: Embed support for Teams town hall Microsoft 365 Roadmap ID 401120 Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. As a part of Team’s ongoing effort to enable our customers to create, manage, and run large scale events, end users can now embed Teams town hall in sites they manage. This capability allows town hall attendees to watch the event instance within a particular website. Embed for town hall introduces embeddable support for town hall engagement features on release. Attendees will have the same engagement feature access within the embed player as they do in client such as Q&A, Captions, Reactions and more. To implement embed for town hall, organizers can access their town hall events unique embed code from the town hall scheduling template upon publish. Organizers can then take that code and inject it to their SharePoint or Microsoft 365 site as desired. On event start, attendees will be able to view and engage with the embed stream on the published site. When this will happen: Targeted Release: We will begin rolling out early November 2024 (previously early October) and expect to complete by mid-November 2024 (previously mid-October). General Availability (Worldwide, GCC): We will begin rolling out early December 2024 (previously late October) and expect to complete by mid-February 2025 (previously mid-January). How this will affect your organization: Users will be able to copy embed code directly from town hall scheduling form on event publish. After the embeddable code is placed in the website, the town hall player will be accessible to attendees who have access to the URL. Note: Attendee access to the embedded video player is driven by the town hall event access. What you need to do to prepare: Organizers with SharePoint or Microsoft 365 site who want to utilize embed support for town hall can begin implementing the embeddable code upon release. MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar Microsoft 365 Roadmap ID 409226 Updated January 21, 2025: 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 January (previously late December). 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 under Event access may 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 to None. 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 ID 412072 Updated January 28, 2025: 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 late January 2025 (previously mid-January) and expect to complete by early February 2025 (previously late January). 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 select Start recording or Stop recording from the More menu, shown here at the bottom of the screen: When users start recording a Meet now or Whiteboard session 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 at Manage Teams recording policies for meetings and events - Microsoft Teams | Microsoft Learn. Using Microsoft PowerShell: Learn more at Set-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 uses Meeting options to 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. MC866447 — (Updated) CAPTCHA Verification for Anonymous Meeting Participants Updated January 7, 2025: 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 late January 2025 (previously mid-December). 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. MC818885 — (Updated) Microsoft Teams: Multiple camera view for Teams Rooms on Windows Microsoft 365 Roadmap ID 402517 Updated January 15, 2025: 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 mid-January 2025 (previously early January) and expect to complete by mid-January 2025 (previously mid-December). General Availability (Worldwide): We will begin rolling out mid-January 2025 (previously mid-December) and expect to complete by late January 2025 (previously late December). General Availability (GCC): We will begin rolling out in mid-January 2025 (previously mid-December) and expect to complete by late January 2025 (previously early January). 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 view using Remote Accessin the Microsoft 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 configure Multiple camera view on a local device: 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. MC809602 — (Updated) Microsoft Teams: New skin tone settings and reactions Microsoft 365 Roadmap ID 323766 Updated January 13, 2025: 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 app Settings > Appearance and accessibility menu 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 late December 2024. General availability (GCC High, DoD): We will begin rolling out mid-November 2024 (previously mid-November) and expect to complete by late January 2025 (previously late December) 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 ID 402183 Updated January 13, 2025: 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 January 2025 (previously late December) 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 > Add or Edit > 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 > Add or Edit > 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. MC781595 — (Updated) Microsoft Teams: Tenant-wide policy for permission to download meeting transcription Microsoft 365 Roadmap ID 332800 Updated January 13, 2025: We have updated the rollout timeline below. 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 complete by late January 2025 (previously late December). 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.) MC772556 — (Updated) Microsoft Teams: Shorter meeting URLs Microsoft 365 Roadmap ID 381953 Updated January 10, 2025: We have updated the rollout timeline below. Please note that information about meeting link expiry changes related to this rollout has been added. We are reducing the length of Microsoft Teams meeting URLs for easier sharing. This rollout applies to all Microsoft Teams platforms (Teams for iOS, Android, Mac, Teams devices, desktop, and web). When this will happen: Targeted Release: We will begin rolling out mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). General Availability (Worldwide, GCC): We will begin rolling out mid-April 2025 (previously mid-February) and expect to complete by late April 2025 (previously late March). General Availability (GCC High, DoD): We will begin rolling out early June 2025 (previously mid-April) and expect to complete by late June 2025 (previously late April). How this will affect your organization: The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode> To make meeting URL shorter, we are removing several parameters such as tenant ID, conversation ID etc. This change serves two main goals: 1) improving usability of URL during sharing and 2) making the URL more secure and less susceptible to malicious attacks. Here are some details about how meeting links work and when they expire: In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire. Every meeting link expires in 60 days after the scheduled event or in 8 hours, if it was created as Meet Now. Learn more about expiration timelines for different types of meetings. With the Short Meeting URL release, expiration limit will be applied to all newly created links. Once the change to Short Meeting URL is released, all newly created meetings will expire as described in the documentation: 60 days after meeting ends for scheduled meetings and 8 hours after creation for Meet Now. Once this expiry period is over, in case someone clicks the link (e.g. outside of Teams app OR in the meeting details inside Teams calendar section), they will be unable to join the meeting. Note: Old links created before short meeting URL release will continue working as it previously was (user will be able to join even after the documented expiry limits). The reason why we are making this change is simple: security is our topmost priority. Maintaining a high security level is essential to protect sensitive data, prevent financial losses, ensure business continuity, and meet compliance and legal obligations. It is a critical aspect of modern digital life and business operations. This adjustment is designed to enhance the security of Teams meeting links, thereby better safeguarding the customer tenant. We want to be on par with modern security standards, that’s why the new behavior is a step in the right direction that we must take. It’s not possible to keep the current behavior. If you think it breaks some of your business processes, please leave comment to the MC post and describe your case there. Recommendations in case the meeting link has expired: For meeting organizer: We recommend scheduling a new meeting. If the meeting organizer got removed from the tenant someone else should reschedule their meetings from scratch. For participant: Please reach out to the meeting organizer and ask them to reschedule the meeting or send you an updated link. What you need to do to prepare: You may want to check if you have any integrations that use parameters from URL. After the rollout, the URL will only contain the meeting ID. Parameters such as tenant ID, organizer ID, conversation ID and message ID will not be in the URL. You may inform meeting organizers from your tenant who use expired meeting links, or you may want to make a tenant-wide announcement about this change. 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. MC750668 — (Updated) Microsoft Teams: Access Workflows from the three-dot menu on shared file Microsoft 365 Roadmap ID 381643 Updated January 27, 2025: 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-February 2025 (previously mid-January). 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 choose Workflows. From Workflows, 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 selecting See more workflows at 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. MC726122 — (Updated) Microsoft Teams: View, download, and delete Microsoft OneDrive transcript files Microsoft 365 Roadmap ID 365720 Updated January 13, 2025: 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. 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 January 2025 (previously late December) 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 this documentation. 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. MC718553 — (Updated) Microsoft Teams: Change background while recording on phone Microsoft 365 Roadmap ID 380852 Updated January 21, 2025: We have updated the rollout timeline below. Thank you for your patience. Users can now record themselves anywhere and share it with coworkers in the Microsoft Teams chat or channel without worrying about the background. Users can now change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on iOS devices. When this will happen: General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out early May 2024 (previously late March) and expect to complete by late January 2025 (previously late December). How this will affect your organization: Users will get an option to change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on an iOS device. To use this feature: Press and hold the camera icon next to the Compose box and then tap the blur icon to the right of the shutter button. You can then choose either an image to replace the background or choose to mildly or heavily blur your background. 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. MC718250 — (Updated) Microsoft Teams: Describe it to design it in Teams Workflows Microsoft 365 Roadmap ID 382659 Updated January 23, 2025: After further review, we will not be rolling this out to GCC. We will communicate via Message center when we are ready to proceed. Can't find a workflow template that matches what you need in Microsoft Teams? You will now be able to describe in detail how you want your automation to work and receive a workflow to match your needs. All you need to do is select the Workflow builder button at the bottom of the create dialog in the Workflows app in Microsoft Teams chat and channel overflow menu. Workflow builder will come to the Workflows app in Microsoft Teams chat and channel overflow menu first. Other entry points to Workflows will get this feature later. When this will happen: Worldwide: We will begin rolling out late September 2024 (previously mid-September) and expect to complete by late October 2024 (previously late September). GCC Release: We will not be proceeding with this change at this time. How this will affect your organization: All users with the ability to create workflows with the Workflows app in Teams will be able to describe the workflow they are trying to build and then receive a suggested flow. Prerequisites A work or school Teams account with access to a Power Automate environment in Europe or the United States. Limitations Power Automate supports workflow descriptions written in the English language only. Descriptions written in other languages might work but are not supported. Cloud flows are the only type of flow that you can create from a written description. In the version rolling out, the AI might omit some parameters, even if you provide them in the description. What you need to do to prepare: No action is needed to prepare for this rollout. If your tenant uses the Power Automate app within Microsoft Teams, you may want to notify your users about this change and update any relevant documentation as appropriate. To learn more: Create a cloud flow from a description (preview) - Power Automate | Microsoft Learn MC709270 — (Updated) Mute with Windows Taskbar available in the new Microsoft Teams on Windows Microsoft 365 Roadmap ID 191528 Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience The Muting Teams with Windows Taskbar is now available. This feature, available in the new Teams experience on Windows, enables you to mute and unmute your audio by clicking the mic icon in Windows taskbar. To control your call mic from the taskbar, do the following: Select the mic icon on your taskbar or press Windows logo key + Alt + K to mute or unmute your microphone while using a calling app. -OR- Click the volume icon in the hardware indicator for volume in Windows taskbar. 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). Worldwide, GCC, GCC High & DoD: We will begin rolling out mid-June 2024 (previously early June) and expect to complete by complete by late January 2025 (previously late December) How this will affect your organization: This enables a feature previously available in older version of Teams on Windows. What you need to do to prepare: To prepare, distribute updates on this rollout with your organization if applicable for your users. MC705760 — (Updated) Teams: Latest meeting experiences with performance improvements on web for Safari and Firefox (for guests) Microsoft 365 Roadmap ID 329253 Updated January 24, 2025: We have updated the rollout timeline below. Thank you for your patience. The latest Teams meeting experiences will be available for Teams on the web in Safari and Firefox browsers - including performance improvements, refreshed pre-join, updated meeting stage, and the updated meeting toolbar. (for anonymous join only) When this will happen: Worldwide: We will begin rolling out early September 2024 (previously mid-August) and expect to complete by early October 2024 (previously late August). GCC, GCC High and DoD: We will begin rolling out mid-October 2024 (previously mid-September) and expect to complete by mid-February 2025 (previously mid-January). How this will affect your organization: We make constant steps to improve Teams performance irrespective of the platform – this time we are making the experience of Teams meetings on web (in Safari and Firefox browsers) better for anonymous users (guests). That’s crucial because it improves external collaboration. For example, if participants from your tenant would like to have meetings with non-Teams users (who are often joining as guests) it’ll become simpler as guests joining meeting from Safari/Firefox web browsers won’t have to wait significant amount of time for the meeting experience to load. You may also notice that currently meeting UI in Chrome and Safari/Firefox is different, but with this update it won’t be a case anymore and you’ll enjoy all the benefits of modern UI (such as meeting toolbar on top of the screen, etc). What you need to do to prepare: You may want to update your internal documentation to inform your users about this improvement. MC688109 — (Updated) Co-organizer experience updates in Teams Webinars and Townhalls Microsoft 365 Roadmap ID 168524 Updated January 15, 2025: 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 mid-January 2025 (previously early January) 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. Microsoft Purview MC989980 — Microsoft Purview | Insider Risk Management: Public preview of policy deletion enhancement (GCC, GCCH, DoD) Microsoft 365 Roadmap ID 171601 Microsoft Purview Insider Risk Management will be rolling out a policy deletion enhancement. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-February-2025 and expect to complete by early March 2025. How this will affect your organization: After this rollout, admins with appropriate permissions will be able to delete all associated alerts and users in scope when deleting a policy, to help quickly reset and remove inactive policies. Cases will not be impacted. This change will be available by default. What you need to do to prepare: No action is needed to enable these features. 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. 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 the Microsoft Purview compliance portal. Learn more: Create and manage insider risk management policies | Microsoft Learn MC986518 — Microsoft Purview | Insider Risk Management: Updates to email scoring (GCC, GCC High, DoD) Microsoft 365 Roadmap ID 471010 Coming soon: Microsoft Purview | Insider Risk Management (IRM) will be rolling out updates to email scoring. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. How this will affect your organization: Insider Risk Management email scoring logic is being updated. With current logic, a single email to multiple recipients is counted multiple times, and this is creating noise by increasing the risk score. In the new logic, a single email to multiple recipients is counted once, and this new principle is applicable to the email containing multiple unallowed domains or priority content. After this rollout, all email insights in Alerts will display the new count and score. This change will be available 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 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. You can access the Insider Risk Management solution in the Microsoft Purview compliance portal. Learn more: Configure policy indicators in insider risk management | Microsoft Learn MC985476 — Microsoft Purview | Insider Risk Management: Share user risk details with other security solutions (GCC, GCC High, DoD) Microsoft 365 Roadmap ID 475857 Microsoft Purview Insider Risk Management is introducing the ability to share Insider Risk Management data with other Microsoft services for Government customers. When turned on, admins with the correct permissions will be able to review user risk details and alerts from Insider Risk Management in other solutions such as Microsoft Purview | Data Loss Prevention (DLP), Microsoft Purview | Communication Compliance, and Microsoft Defender. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by mid-February 2025. How this will affect your organization: Admin can access the toggle in Microsoft Purview > Insider Risk Management settings > Share user risk details with other security solutions: This change will be available 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 users about this change and update any relevant documentation. Consider assessing your organization’s needs and decide if your organization will benefit from reviewing Insider Risk Management alerts through other solutions. Learn more: Share insider risk management data with other solutions | Microsoft Learn MC973511 — (Updated) Microsoft Purview | Data Lifecycle Management: Separate retention policies for Copilot and AI apps Microsoft 365 Roadmap ID 470025 Updated January 10, 2025: We have updated the rollout timeline below. Thank you for your patience. This new feature provides the capability for admins to configure separate retention policies for various Microsoft 365 Copilot and AI apps. As a result, admins will have the option to configure policies that can delete Copilot and Generative AI interactions faster. When this will happen: General Availability (Worldwide): We will begin rolling out mid-February 2025 (previously late January) and expect to complete by late February 2025 (previously mid-February). How this will affect your organization: Organizations will now have controls to configure different retention policies for Microsoft Teams Chat, Copilot, Copilot studio, and ChatGPT Enterprise. This feature is available by default. What you need to do to prepare: For more information, see Create and configure a retention policy. 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. MC969449 — (Updated) Microsoft Purview | Data Loss Prevention for endpoints: Four new conditions (GCC, GCCH, DoD) Microsoft 365 Roadmap ID 374811 Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Purview | Data Loss Prevention (DLP): Four new conditions or predicates that admins can use in their policies for endpoint devices. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-January 2025 (previously early January) and expect to complete by late January 2025 (previously mid-January). How this will affect your organization: After this rollout, DLP policies will include the capability to identify documents that are unscannable, partially scannable, exceed a specific file size, or have names matching configured patterns for Government cloud tenants on Windows endpoint devices. This functionality enables you to prevent users from accessing unscannable files on endpoints and attempting egress actions such as copying to a USB drive, copying to the clipboard, or transferring to another network share, among others. The four new predicates are: Document size equals or is greater than: Detects documents greater than or equal to the specified value. Document name matches patterns: Detects documents where the file name matches specific patterns. Document couldn’t be scanned: Applies to documents when their content wasn't scanned. Examples include password protected files, files for which text extraction failed, and files that exceed file size limit. Document couldn’t complete scanning: Applies to documents when their content was scanned, but the entire document was not scanned. Examples include files for which extracted text exceeded the limits/thresholds. When defining your DLP Policy, you can use these conditions across supported and applicable workloads for government cloud tenants. For example, you can extend any of the four new conditions that are available now in DLP for Exchange and scope them to Endpoint > Devices as part of your policies and rules, which enhances protection across the digital estate. Please refer to the supported file types on endpoint, for which these predicates will provide protection. What you need to do to prepare: Learn more about conditions supported for endpoints Get started with Data Loss Prevention in the Microsoft Purview compliance portal. Learn more: Using Endpoint DLP | 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 and users about this change and update any relevant documentation. MC966637 — (Updated) Microsoft Purview | Data Loss Prevention for endpoints: New "Document property" condition (GCC, GCCH, DoD) Microsoft 365 Roadmap ID 417482 Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Purview | Data Loss Prevention (DLP): The new Document property is condition will be available for use in policies for endpoint devices. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-January 2025 (previously early January) and expect to complete by late January 2025 (previously mid-January). How this will affect your organization: After this rollout, DLP policies can detect and monitor egress actions for documents that match defined custom properties. The new Document property is condition detects documents with custom properties matching the specified values. As part of DLP policy definition, this new condition can be used across supported and applicable workloads. For example, the Document property is condition in DLP for Exchange can be extended to endpoint devices as part of DLP policies and rules, which enhances protection across the digital estate. This change will be available by default for admins to configure. What you need to do to prepare: Get started with DLP in the Microsoft Purview compliance portal. Learn more: Data Loss Prevention policy reference | 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. MC961761 — Microsoft Purview | Insider Risk Management: IRM alerts in Microsoft Defender XDR Microsoft 365 Roadmap ID 422730 Updated January 23, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Purview: Insider Risk Management (IRM) data including alerts, indicators and events will be available in these Microsoft Defender XDR experiences: Unified alert queue: IRM alerts will appear in the unified alert and incident queue in Defender XDR for comprehensive investigation and correlation. Advanced Hunting: IRM data will be available for advanced hunting in Defender XDR, allowing analysts to identify hidden risk patterns using KQL queries. Analytics can also create custom detections on the top of IRM data. Graph API: IRM data will be accessible through the Microsoft Graph API, supporting bidirectional integrations with external applications. Microsoft Sentinel: IRM alerts will be available in Microsoft Sentinel through the XDR-Sentinel connector, providing richer metadata. When this will happen: Public Preview: We will begin rolling out mid-January 2025 and expect to complete by end of January 2025. General Availability (WW, GCC, GCC High, DoD): We will begin rolling out late June 2025 (previously early May) and expect to complete by mid-July 2025 (previously mid-May). How this will affect your organization: Enable this feature by turning on Share data with other security solutions in the IRM global settings. Only users with Insider risk analysis or investigation roles in the Microsoft Purview portal can access IRM data in Defender XDR. To access alerts, incidents, and events from Defender XDR via API, you need to provision apps with the necessary permissions. IRM data is accessible via Microsoft Security Graph APIs, allowing for reading and updating alert or incident statuses. Permissions are set at the application level, without solution-specific scoping. Any existing apps pulling data from these APIs will also access IRM data. So, if you integrate XDR alerts into external ticketing systems, IRM alerts will show up, unless you specifically filter out the alerts. IRM alerts will appear in Sentinel if your tenant has the Defender XDR connector enabled in Microsoft Sentinel. In Defender XDR, IRM data is not pseudonymized to allow effective correlation of IRM alerts with alerts from other solutions within the platform, such as Defender for Endpoint and Defender for Cloud apps. These changes will be available by default for admins to configure in IRM global settings. Admins will be able to view Insider Risk Management alerts in Defender XDR. Harness the power of Advanced Hunting queries with two new tables that contain Insider Risk Management data: DataSecurityBehaviors and DataSecurityEvents. What you need to do to prepare: Opt-in to data sharing settings in IRM global settings page. Assign necessary permissions to analysts Review existing apps accessing Defender XDR data through Graph APIs. If your organization is using Microsoft Defender XDR connector, please review the list of users who will gain access to this data through Sentinel. This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration in IRM global settings to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation. MC950890 — (Updated) Microsoft Purview | Data Security Posture Management for AI Microsoft 365 Roadmap ID 469509 Updated January 24, 2025: We have updated the content. Thank you for your patience. Generative AI (GAI) is being adopted at an unprecedented rate. AI fuels innovation and productivity but also poses risks – organizations are concerned about the risky AI use and sensitive data loss through AI apps. Microsoft Purview Data Security Posture Management for AI (DSPM for AI) is a central location in Microsoft Purview that helps organizations secure data in AI, including Microsoft AI applications such as Microsoft 365 Copilot and non-Microsoft AI applications. With the DSPM for AI capabilities in Purview, organizations can safely adopt AI without having to choose between productivity and protection. DSPM for AI also supports admin units and displaying AI policies that were created in Purview solutions. A version of DSPM for AI is available to additional licensing, specifically Microsoft 365 E3 and Microsoft 365 Copilot licenses. When this will happen: We will begin rolling out late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). How this will affect your organization: DSPM for AI also supports admin units and displaying AI policies that were created in Purview solutions. A version of DSPM for AI is available to additional licensing, specifically Microsoft 365 E3 and Microsoft 365 Copilot licenses. DSPM for AI use cases Viewing insights and analytics into AI activity in your organization. Using policies to protect data and prevent data loss in AI prompts Implementing compliance controls to apply optimal data handling and storing policies Microsoft Purview DSPM for AI will be in the Microsoft Purview portal and will consist of 5 tabs: Overview, Recommendations, Reports, Policies, and Activity explorer. The DSPM for AI Overview with getting started steps, two recommendations, two reports, and resources. The Recommendations tab displays all recommendations provided by DSPM for AI. Reports includes graphs for total interactions over time, sensitivity labels and sensitive information types found in AI interactions, user risk level, and more. Policies displays all policies that have been created by default or AI policies created in Purview solutions. Activity explorer shows events for AI interactions along with prompts and responses. This feature will be enabled 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. Get ready for this change by reviewing the admin documentation: Considerations for Data Security Posture Management for AI & data security and compliance protections for Copilot Microsoft Purview data security and compliance protections for generative AI apps MC949003 — (Updated) Microsoft Purview | Data Loss Prevention: Gain policy insights with Microsoft 365 Copilot for Security Microsoft 365 Roadmap ID 466740 Updated January 17, 2025: We have updated the rollout timeline below. Thank you for your patience. As part of Microsoft 365 Copilot for Security in Data Loss Prevention (DLP), Policy Insights helps admins understand DLP policies and its constructs. This enhancement enables DLP admins to gain insights on coverage of policies on pivots like location, classifiers, and notifications. DLP admins can get these insights on all the policies or on a few selected policies. They will be able to use prompts to gain a deeper level view of how a policy is configured for their digital landscape. This helps them align their data posture on a regular basis and make corrections to policy posture as needed. When this will happen: Public Preview: We will began rolling out mid-November 2024 and expect to complete by early December 2024. General Availability (Worldwide): We will begin rolling out early February 2025 (previously early January) and expect to complete by late February 2025 (previously late January). Currently, Copilot for Security is not designed for use by customers using US government clouds, including but not limited to GCC, GCC High, DoD, and Microsoft Azure Government. For more information, consult with your Microsoft representative. How this will affect your organization: Administrators can invoke the policy insights to understand the insights from all their policies or selected polices. The insights offered start with a higher-level view of how their policies: are effective across locations. detect the presence of sensitive information types throughout their digital estate. notify administrators of violations. educate users while they perform activities they should not. These insights are offered with different pivots by location, classification, and by administrative scopes. This is offered to give the security policy administrators different views for deeper understanding of policy constructs and their impact. Step 1: Select the policies you wish to get insights/quick summaries about. Step 2: Click on the Get Insights with Copilot button. You will see the prompt is already pushed into the Copilot Experience in the side panel. Step 3: Copilot responds with insights on the selected policies. What you need to do to prepare: Admins can prepare by having Security Computer Units (SCUs). Copilot for Security is sold in a provisioned capacity model and is billed by the hour. Get more information about SCUs: Get started with Microsoft Copilot for Security | Microsoft Learn. MC920308 — (Updated) Microsoft Purview | Information Protection: Auto-labeling policies will support "Fingerprint based SIT" Microsoft 365 Roadmap ID 396173 Updated January 24, 2025: We have updated the content. Thank you for your patience. Coming soon to Microsoft Purview | Information Protection: Admins will be able to use auto-labeling policies to automatically label files and emails with Fingerprint 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 early February 2025 (previously mid-January). How this will affect your organization: Before this rollout, admins are not able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT. After this rollout, you can configure Fingerprint based SIT using the condition Content contains sensitive information types. Files that match Fingerprint based SIT will show in simulation. Note: Contextual summary is not available for Fingerprint 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 MC911618 — (Updated) Microsoft Purview | Insider Risk Management: Multi-policy settings in Adaptive Protection Microsoft 365 Roadmap ID 171735 Updated January 24, 2025: 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 the Risk levels for Adaptive Protection settings. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously mid-January) and expect to complete by mid-March 2025 (previously mid-February). How this will affect your organization: Before this rollout, admins can select single Insider Risk Managment policies in the Risk levels for Adaptive Protection settings. 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 MC892050 — Microsoft Purview | Compliance Portal: Enrich triage in Communication Compliance within Insider Risk Management context Microsoft 365 Roadmap ID 415170 Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. This feature update to Microsoft Purview Communication Compliance (CC) introduces a pivotal enhancement that integrates Insider Risk Management (IRM) alerts within CC triage flow, providing a holistic approach to compliance risk assessment. This integration empowers investigators with enriched insights by correlating communication alerts with a user's risk profile and activity history from IRM directly in the CC triage flow. This synergy between IRM and CC facilitates a more nuanced and informed decision-making process during investigations. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out early March 2025 (previously early January) and expect to complete by late April 2025 (previously late February). How this will affect your organization: The integration of IRM context into CC is a significant stride towards enhancing the efficacy of compliance investigations. This will allow investigators to view a user's risk profile and history alongside communication alerts, enabling a more informed and efficient triage process. The insider risk severity (Low, Medium, or High) determined by activity detected in IRM policies helps admins prioritize and respond to user activity accordingly. A new user activity timeline will show messages and activities from IRM in one screen, simplifying the review process. What you need to do to prepare: To use this feature, please connect with an IRM administrator to enable data sharing from IRM settings. If you don't turn this setting on, you will see “Insider risk activity not available.” MC808165 — (Updated) Microsoft Purview eDiscovery | Modernized eDiscovery in new Microsoft Purview portal Microsoft 365 Roadmap ID 383744 Updated January 9, 2025: We have updated the rollout timeline below. 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 with message ID and sensitivity 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's frequent 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 visual Statisticsallows 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): We will begin rolling out mid-February 2025 (previously mid-December) and expect to complete by early mid-February 2025. GCC: We will begin rolling out mid-March 2025 and expect to complete by mid-March 2025 GCC-High: We will begin rolling out mid-March 2025 and expect to complete by late March 2025 DoD: We will begin rolling out late March 2025and expect to complete by late March 2025. 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 the new 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 ID 335856 Updated January 24, 2025: We have updated the content. 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 late February 2025 (previously mid-January) and expect to complete by late March 2025 (previously mid-February). 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 the Microsoft Purview compliance portal > Insider risk management > Adaptive Protection: References Learn about adaptive protection Learn about insider risk management Learn about data 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 ID 124972 and 171748 Updated January 7, 2025: 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 MC681240 Adaptive 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-January 2025 (previously late mid-December). 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 MC791110 — (Updated) Microsoft Purview | Data Lifecycle Management: New integration with Adaptive protection Microsoft 365 Roadmap ID 392839 Updated January 9, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Purview: We are announcing the public preview of the integration of Adaptive protection with Data Lifecycle Management (DLM) to help you find the right balance to protect against data sabotage while enabling productivity. This new integration leverages DLM features to provide an additional control for Adaptive protection that automatically preserves items deleted by a user with an elevated risk level, so items can be restored if needed. When this will happen: Public preview: We will begin rolling out in late June 2024 (previously early May) and expect to complete by late July 2024 (previously mid-July). General Availability: We will begin rolling out in mid-March 2025 (previously mid-January) and expect to complete by late March 2025 (previously late February). How this will affect your organization: After the rollout, and after you enable Adaptive protection for your tenant, the retention label and auto-apply policy for data lifecycle management will be automatically created for you. This policy will automatically include elevated risk users identified by Microsoft Purview | Insider Risk Management solution. If these users delete content from Microsoft SharePoint, Microsoft OneDrive, or Microsoft Exchange, a retention label is automatically applied to that content to retain it for 120 days. Retention labels are automatically applied to unlabeled content deleted by these users. When these users are no longer at the elevated risk level, they are automatically removed from the DLM policy, and the system will no longer keep a copy of content they delete. Any content copies previously retained when the user had an elevated risk level will be kept for the 120 days as specified by the retention label. Unlike other retention labeling scenarios, users do not see the retention label, and you do not need to create or manage the retention label or policy. At this time, you can't change the retention period or assign different policies based on the different risk levels, or for different locations. The single retention label and auto-labeling policy for your tenant is not visible in the Microsoft Purview compliance portal. What you need to do to prepare: Learn more: Learn about retention policies & labels to retain or delete | Microsoft Learn If you're using Adaptive protection and want to automatically retain content deleted by elevated risk users, follow these steps to turn on this new integration. Sign in to the Microsoft Purview compliance portal. Navigate to Data lifecycle management > Microsoft 365 > Adaptive protection settingsin the top right corner. Turn the setting ON and select Save. If you’re not using Adaptive protection already, turn on Adaptive protection and the new feature will be enabled along with Adaptive protection. 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. MC678065 — (Updated) Microsoft Purview compliance portal: Information Protection - New cmdlet for Content Explorer Microsoft 365 Roadmap ID 117531 Updated January 9, 2025: 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 early July 2025 (previously mid-April) and expect to complete by late July 2025 (previously mid-May). 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 Outlook MC993229 — New Microsoft Outlook for Windows and web: New folder color feature Microsoft 365 Roadmap ID 472921 Coming soon to new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web: Users can customize folder icon colors, making it easier to visually differentiate and personalize folders. When this will happen: Targeted Release: We will begin rolling out early February 2025 and expect to complete by late February 2025. General Availability (Worldwide): We will begin rolling out late March 2025 and expect to complete by late March 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out late April 2025 and expect to complete by late April 2025. How this will affect your organization: After this rollout, this feature will be available for all Outlook accounts except for shared mailboxes and shared folders. Colors work for light and dark mode. Note: Some Outlook themes will have low contrast with some folder colors. To change the color of a folder, a user can hover over the folder name, select the three-dot menu, select Change color and then choose a color. To turn off the color, follow the same process, and select Automatic. The folder color will display in the list of folders and in Favorites if the colored folder is added to Favorites. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before or after 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. #newoutlookforwindows MC981624 — Microsoft Outlook name change: "Outlook (new)" on Windows will change to "Outlook" Coming soon: The installed name for new Microsoft Outlook for Windows will change from "Outlook (new)" to "Outlook." This rollout comes after a change to the classic Outlook in version 2407, previously announced in MC803006 (Update) Outlook for Windows display name change (published June 2024, updated August 2024), which added "(classic)" to the installed name to differentiate the two apps. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early February 2025 and expect to complete by late February 2025. What you need to do to prepare: Outlook in the Windows Start menu. Left: Before the name change. Right: After the name change: This change will be on by default. This part of the app identity is not customizable for organizations. As always, we recommend planning your organization's migration to the new Outlook using the resources at https://aka.ms/newOutlookAdoption 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. #newoutlookforwindows MC974362 — (Updated) Secure/Multipurpose Internet Mail Extensions encryption support in new Outlook for Windows Microsoft 365 Roadmap ID 397891 Updated January 21, 2025: After further review, we will not be rolling this out to 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. We are rolling out fundamental Secure/Multipurpose Internet Mail Extensions (S/MIME) support for primary accounts in new Outlook. With this new feature, new Outlook will start supporting sending and reading signed and encrypted emails. In new Microsoft Outlook, this option is available in Options > More Options. When this will happen: General Availability (Worldwide): We began rolling out mid-December 2024 and expect to complete by late January 2025. General Availability (GCC): We will begin rolling out early February 2025 and expect to complete by mid-February 2025. General Availability (GCC High, DoD): We will communicate via Message center when we are ready to proceed. How this will affect your organization: If your organization is not using New Outlook this will not impact you. If your organization does not have S/MIME setup for your users, this will not impact you. If your organization is currently using S/MIME, you will soon see controls to apply S/MIME encryption when signing into new Outlook. Similarly, you will be able to verify, sign, decrypt, and reply to S/MIME emails. 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. Users with S/MIME certificates on their machine or Smart Card will be able to use this new feature in new Outlook. Learn more: Overview of the new Outlook for Windows MC960818 — (Updated) Microsoft Outlook for iOS/Android: New reporting buttons integrated with Microsoft Defender for Office 365 Microsoft 365 Roadmap ID 371383 Updated January 29, 2025: We have updated the content. Thank you for your patience. Coming soon for Microsoft Outlook for iOS/Android: New built-in report buttons in version > 4.2446. Admins can control the appearance and behavior of these buttons that allow users to report emails as phishing / junk / not junk from the User Reported setting page 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. When this will happen: General Availability (Worldwide, GCC, GCC High): We began rolling out in early December 2024 and expect to complete by late January 2025. How this will affect your organization: Information to keep in mind: Microsoft OWA (Outlook on the Web) and the new Microsoft Outlook for Windows have had this functionality since November 2022. This rollout to iOS/Android does not change or affect that functionality. Classic Microsoft Outlook for Windows client has had this functionality in current channel since August 2024. Learn more: MC841229(Updated) Classic Microsoft Outlook for Windows: New reporting buttons integrated with Microsoft Defender for Office 365 (published July 2024, updated October 2024). Microsoft Outlook for Mac released this functionality in September 2024. If you have turned off the reporting feature in the Microsoft 365 Defender User reported settings page or are using a third-party add-in, the report buttons in Outlook for Android/iOS won't be visible. The Microsoft reporting add-in (the Microsoft report message add-in and Microsoft phishing add-in) will be supported till further notice. The future goal is to have a consistent button reporting experience across all Outlook platforms. If you are using Microsoft reporting add-ins in Outlook for iOS/Android, your users will see two reporting experiences: one from the built-in Outlook buttons (added by this rollout) and one from the add-in. Both options will behave the same for users (except for the newly customizable pop-ups) and the reported messages will end up in the same place, causing minimal disruption. 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 your User reportedsettings. Like OWA and new Outlook for Windows, the built-in reporting button in Outlook for iOS/Android supports reporting from shared and delegate mailboxes. This change is available 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 users about this change and update any relevant documentation. No action is required form you after this rollout because your current settings in the User reported settings page will not be changed. Learn more Report phishing and suspicious emails in Outlook for admins - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout) User reported settings - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout) MC947045 — (Updated) Microsoft Outlook for iOS and Android: Attach emails while composing an email Microsoft 365 Roadmap ID 464206 Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft Outlook for iOS and Android users: In response to customer requests, we are rolling out the ability to attach emails directly in the compose window. This enhancement allows users to include individual emails as attachments in new messages, facilitating seamless sharing and providing more context for recipients. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out late January 2025 (previously early January) and expect to complete by late February 2025. How this will affect your organization: Before this rollout, users can forward emails as attachments but cannot attach emails while composing. After this rollout, users will notice a new Attach email option when they select the paper clip attachment icon in the compose window. Users can select this option to browse for, choose, and attach individual emails to their new message. This change is available by default. What you need to do to prepare: This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change, update relevant documentation. MC882252 — (Updated) New Microsoft Outlook for Windows: Sharing Word, Excel, and PowerPoint local files through email Microsoft 365 Roadmap ID 397094 Updated January 23, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to new Microsoft Outlook: Users will be able to share Microsoft Word, Microsoft Excel and Microsoft PowerPoint files stored on their device (not stored in a cloud like Microsoft OneDrive) from new Outlook for Windows. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early October 2024 (previously mid-September) and expect to complete by late August 2025 (previously late December). How this will affect your organization: Before this rollout, users are only able to see old Outlook for Windows when they try to share a Word, Excel or PowerPoint fie. After this rollout, when users want to share a Word, Excel, or PowerPoint file that is saved to their device (not stored in a cloud like Microsoft OneDrive), the user can right-click the file name in File Explorer, select Share, and select new Outlook for Windows to email the file. This option 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 users about this change and update any relevant documentation. MC847877 — (Updated) Microsoft Outlook for iOS and Android: Choose fonts while composing Microsoft 365 Roadmap ID 409969 Updated January 9, 2025: 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 late January 2025 (previously early December). 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 ID 388913 Updated January 16, 2025: 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 their Favorites list 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 February 2025 (previously early January) and expect to complete by early March 2025 (previously early February). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early March 2025 (previously early February) and expect to complete by early April 2025 (previously early March). 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 MC982553 — Microsoft Exchange Online: Search-MailboxAuditLog and New-MailboxAuditLogSearch will retire We will retire the Search-MailboxAuditLog and New-MailboxAuditLogSearch cmdlets in Microsoft Exchange Online starting March 1, 2025, and completing in late March 2025. After the retirement, new records will be written to Search-UnifiedAuditLog and Search-MailboxAuditLog will be accessible only as a historical record. How this will affect your organization: After the retirement, admins will be able to access Search-MailboxAuditLog and New-MailboxAuditlogSearch and make changes and downloads until late June 2025. After late June, Search-MailboxAuditLog and New-MailboxAuditlogSearch will become a static record only, and admins will no longer be able to make changes and downloads. What you need to do to prepare: This change will happen automatically by the specified dates. Please notify your users about this change, update your relevant documentation, and share the alternate capability Search-UnifiedAuditLog. To use the Search-UnifiedAuditLog cmdlet, you must ensure auditing is enabled for your tenant. Learn more about enabling auditing for your tenant and about the changes to these cmdlets: Microsoft Exchange Online: Search-MailboxAuditLog and New-MailboxAuditLogSearch will retire | Microsoft Community Hub MC902782 — (Updated) Exchange Online token deprecation plan Updated February 3, 2025: We have updated the content. This is a reminder that starting February 17th, legacy Exchange Online user identity and callback tokens will be turned off across all Microsoft 365 tenants. This impacts all Outlook add-ins that request a legacy Exchange Online token to identify the user or make Exchange web services (EWS) calls. This change only applies to Exchange Online and doesn’t apply to Exchange on-premises. Recommended actions Identify any add-ins that are impacted.Determine if your tenant has any deployed Outlook add-ins that are impacted by this change. For more information, see Which add-ins in my Organization are impacted. Contact add-in publishers.Microsoft has worked with many Outlook add-in publishers to update their add-ins to use Entra ID tokens and Microsoft Graph. If you identify any impacted add-ins on your tenant, we recommend that you reach out to the publishers of those add-ins to learn more about their plans to update. Can I opt out of this change? You can opt out of the February 17th change if all the following are true. Your tenant has add-ins impacted by this change. The impacted add-ins will not be updated to no longer use legacy Exchange Online tokens by February 17th. The add-ins are necessary for your organization. To opt out, run a command to set legacy Exchange Online tokens to remain on. It takes up to 24 hours for the command to take effect. If you turn tokens on before February 17th, your tenant will be exempt from the February 17th change. Tokens will remain on until June 2025 or until you explicitly turn them off. What happens on February 17th? Microsoft will begin deploying a change to all users worldwide in Microsoft 365 tenants that will turn off the issuance of legacy Exchange online tokens. The deployment will take several weeks to deploy to all users. If an Outlook add-in requests a legacy Exchange token, and token issuance is turned off, the add-in will receive an error. Outlook add-ins that still request legacy Exchange Online tokens will be broken by this change. Please note that even after legacy tokens are turned off, already issued legacy tokens will continue to be valid for approximately 24 hours. Note that since the change is applied per user, and deployed over several weeks, you could see some user’s affected while others are not. Where do I get more information? The Outlook legacy tokens deprecation FAQ is updated regularly and contains information about tools and how to upgrade add-ins. We recommend you refer to the Q&A section for Microsoft 365 administrators. We also recommend you share the FAQ with any developers in your organization that need to update LOB Outlook add-ins using legacy Exchange Online tokens. Additional resources Turn legacy Exchange Online tokens on or off Legacy Exchange Online token deprecation FAQ Enable single sign-on in an Office Add-in with nested app authentication NAA Outlook sample MC886603 — (Updated) Reject multiple From addresses (P2 From headers) without a Sender header Updated January 31, 2025: We are proactively opting tenants out of the rollout that were detected as sending high volumes of emails exhibiting multiple From addresses without a Sender address header. These exempted senders will only be able to send emails exhibiting multiple From addresses without a Sender address header to recipients belonging to the same tenant as the sender. We will provide a subsequent update by the end of February with an updated timeline for tenants that are opted out. Starting February 3 (previously December 1), we're going to start gradually dropping messages that have multiple From addresses (also known as P2 From headers) without a Sender header from being processed via Exchange Online. If we see significant traffic exhibiting multiple From addresses (P2 From headers) without a Sender header in your tenant in the month of September, we will send you a Message Center Post by October 15th alerting you and providing some sample message IDs. We are doing this to comply with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2) which mandates the Sender header to be present and contain a single address if the From header has more than one address. Noncompliance with this could be exploited by attackers, allowing them to impersonate a sender address by misleading the client into using the From header to determine the sender instead of the Sender header. When this will happen: February 3, 2025 (previously December 1st) We are delaying the rollout start date from December to February 3rd 2025 in order to provide more time to customers for investigating messages exhibiting multiple P2 From Addresses without a Sender Address. Most of the traffic exhibiting multiple P2 From Addresses without a Sender Address will be inbound spam destined for your tenant sent by malicious spammers on the internet. Some customers are sending legitimate emails with this malformed header configuration. On October 15, we sent a targeted MC post to customers showing high volumes of messages exhibiting multiple P2 From Addresses without a Sender Address as they may be impacted by this change. For investigating if you will be impacted by this change, focus your investigation on messages sent using On Premises Inbound Connectors to Exchange Online. Authenticated mail submission is not impacted because submitting messages like this using those submissions are not allowed (Graph, Outlook clients, SMTP AUTH Client Submission). How this affects your organization: If email clients including devices and applications that you use to send messages, do so using multiple From addresses but without a Sender address header after December 1st, you will get an NDR error code 550 5.1.20 “Multiple From addresses are not allowed without Sender address’”. What you can do to prepare: When this change is in effect, if you need to send a message that has more than one email address in the From field, make sure that you have a single email address in the Sender header. If you expect this change to cause any issues for your organization, please share that feedback. Microsoft 365 MC986516 — Microsoft Forms | Data sync to Microsoft Excel: migrating from the older solution to the new solution We will be retiring the old data sync feature from Microsoft Forms in GCC. Instead, we recommend new live data sync to Excel solution. Note: You may have received MC943681 (November '24) if we had identified that your tenant utilized legacy data sync between August '24 and October '24. When this will happen: We will begin rolling out the change on February 13, 2025, and expect to complete by February 27, 2025. How this will affect your organization: Users who rely on the older version to sync data from Forms to Excel will need to manually update the data sync to the new solution. After the old data sync solution has been deprecated, existing Excel workbooks using the old data sync solution will no longer receive new responses. Users can still migrate these existing Excel workbooks to the new data sync solution to receive new responses when needed. For each form using the old syncing solution, users can migrate the form according to the instructions provided in Forms and Excel for the web. More details can be found here: Update to the new solution for syncing forms responses to Excel - Microsoft Community Hub. If users are using the old data sync solution in a workflow that relies on the Excel workbook being updated automatically without any user action, they will be impacted by the change as the Excel file will only get updated when it’s opened in a supported Excel client. These users will have to manually update their workflow. Our suggested solution is to use Power Automate: Setting Up an Automated Workflow Between Microsoft Forms and Excel Through Power Automate - Microsoft Support Note: The older version of the data sync exists in group forms created with Microsoft 365 Groups. The new data sync can only be triggered in Excel for the web. If users want to receive new Forms response data in the Excel desktop app, open the file in Excel for the web, and then wait for the desktop app file to sync from the web file. (Support for other versions of Excel is in progress.) The new data sync solution will be on by default and available to all Forms and Excel for the web customers. What you need to do to prepare: Share the migration solution if users report they cannot get Forms data updated in Excel. Learn more: Introducing Forms data sync to Excel - Microsoft Community Hub 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. MC980798 — Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) Microsoft 365 Roadmap ID 475046 Python in Excel allows you to bring the capabilities of Python directly into the Microsoft Excel grid. With this rollout, Python in Excel with standard compute will be generally available in Excel for Windows. When this will happen: General Availability (GCC): We will begin rolling out to Excel for Windows mid-February 2025 and expect to complete by early March 2025. After we complete the rollout to Excel for Windows, we will send a separate message with the timeline for rolling out this change to Microsoft Excel for the web and Microsoft Excel for Mac. How this will affect your organization: After this rollout, eligible users will be able to add Python formulas to their workbooks without any installation required. These Python formulas will be run by Excel in a secure container on the Microsoft Cloud with enterprise-level security and with standard compute. With this release, eligible Excel users with a Microsoft 365 Copilot license will also be able to use the Copilot in Excel with Python feature, enabling them to leverage the capabilities of AI and Python in Excel for deeper data analysis. Note: Some premium Python compute will be included with each user’s Microsoft 365 subscription each month, giving them limited access to faster calculation speeds. After they have used all of their premium compute, they can continue to use the Python in Excel feature with standard Python compute. To get more premium compute, admins will be able to purchase the Python in Excel add-on license for their users after it becomes available later this year for GCC. We will send a separate message with the timeline for the rollout of the Python in Excel add-on license. An example of a Python formula in an Excel workbook: The Python in Excel feature will be enabled by default. What you need to do to prepare: To learn more about Python in Excel, please review the Python in Excel documentation. To learn more about data security: Data security and Python in Excel - Microsoft Support 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 relevant documentation. MC833890 — (Updated) Microsoft Word, Excel, PowerPoint: Protect sensitive files with dynamic watermarking Microsoft 365 Roadmap ID 400717 Updated January 24, 2025: We have updated the rollout timeline below. Thank you for your patience. Update December 20, 2024: There is an issue causing users to get an access denied error when attempting to open files for which they are not the RMS owner, when the file has a sensitivity label configured for dynamic watermarking. We are working to resolve this issue. Dynamic watermarking is a new sensitivity label setting that will add watermark text containing the consuming user’s information onto content in files created in Microsoft Word, Excel, and PowerPoint. Sensitivity labels from Microsoft Purview Information Protection help you classify and protect your organization's data. Learn more: (Preview) Dynamic watermarking for sensitivity labels in Word, Excel, and PowerPoint - Microsoft Community Hub This message applies to Word, Excel, and PowerPoint on the web, Desktop/Windows, Mac, Android, and iOS platforms. When this will happen: Public Preview: We will begin rolling out mid-July 2024 and expect to complete by early August 2024. General Availability (Worldwide): We will begin rolling out to Current Channel mid-January 2025 (previously mid-November) and expect to complete by late February 2025 (previously late January). The rest of the channels will follow in line with their normal cadence. How this will affect your organization: Before the rollout: Admins are not able to configure dynamic watermarking though sensitivity labels in Word, Excel, and PowerPoint. After the rollout, refer to the admin documentation to configure dynamic watermarks in your tenant. This feature is off by default. Admins must configure the feature before it is accessible to 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. Learn more Apply encryption using sensitivity labels | Microsoft Learn (Preview) Dynamic watermarking for sensitivity labels in Word, Excel, and PowerPoint - Microsoft Community Hub Documentation - Office 365 IP Address and URL web service January 30. 2025 - GCC January 30. 2025 - GCC High January 30. 2025 - DOD
Jesse_Tedoff
Mar 11, 2025 Place Public Sector Blog
765Views
0likes
0Comments
Understanding Compliance Between Commercial, Government, DoD & Secret Offerings - Feb 2025 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.
RichardWakeman
Mar 03, 2025 Place Public Sector Blog
38KViews
5likes
3Comments
Aligning CMMC Controls with your Azure Landing Zone
Better Together: Azure Landing Zone, Azure Security Benchmarks, Azure Security Center, and CMMC Level 3 compliance
George__Wilburn
Feb 24, 2025 Place Public Sector Blog
18KViews
0likes
5Comments
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.
RichardWakeman
Feb 21, 2025 Place Public Sector Blog
141KViews
3likes
11Comments
GCC/GCCH Teams Phone Summit - Feb 25-26 Arlington, VA - REGISTRATION OPEN!
Registration is now open for the GCC/GCCH Teams Phone Summit in Arlington, VA, Feb 25-26. Click here to register: https://msevents.microsoft.com/event?id=3586839266 We look forward to hosting you at the GCC/GCCH Teams Phone Summit on Tuesday, Feb 25 and Wednesday, Feb 26, in Arlington VA! The This is your opportunity to explore current and coming capabilities to your government environments! You’ll be surrounded by the experts to get answers and receive the tools and resources to navigate your unique voice journey. Day 1 - Tuesday, Feb. 25 - 8:30am-4:30pm Welcome from Javier Vasquez, VP, Microsoft Federal Teams Phone and Device Overview - latest and greatest and coming capabilities Call Records Insights Admin Tips and Tricks Fireside Chat highlighting 3 government agency's journeys to Teams Phone Partner Corner: Momentum Telecom (Lunch Sponsor), CIS Secure (Breakfast Sponsor), Audiocodes, SOFTEL, and Poly Day 2 - Wednesday, Feb. 26 - 9:30am-3:00pm 1:1 time with Dave Jennings - only 3 slots left (11am-12pm, 12-1pm, and 1-2pm EDT) - sign up here: Book Time with Dave! Topical breakout sessions with GCC/GCCH engineering experts (each one delivered three times during the day): Unlocking Insights: Mastering Teams Phone Monitoring and Reporting Teams Fortress: Ensuring Security & Compliance Microsoft Teams Advanced Calling and Beyond MS Teams Phone and the Future of Copilot/AI Lunch coupons to local establishment(s) to be provided Reach out to Danny McBride at dannymcbride@microsoft.com with any questions.
dannymcbride
Feb 07, 2025 Place Public Sector Blog
364Views
0likes
0Comments

"}},"componentScriptGroups({\"componentId\":\"custom.widget.MicrosoftFooter\"})":{"__typename":"ComponentScriptGroups","scriptGroups":{"__typename":"ComponentScriptGroupsDefinition","afterInteractive":{"__typename":"PageScriptGroupDefinition","group":"AFTER_INTERACTIVE","scriptIds":[]},"lazyOnLoad":{"__typename":"PageScriptGroupDefinition","group":"LAZY_ON_LOAD","scriptIds":[]}},"componentScripts":[]},"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/community/NavbarDropdownToggle\"]})":[{"__ref":"CachedAsset:text:en_US-components/community/NavbarDropdownToggle-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"shared/client/components/common/OverflowNav\"]})":[{"__ref":"CachedAsset:text:en_US-shared/client/components/common/OverflowNav-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/messages/MessageView/MessageViewInline\"]})":[{"__ref":"CachedAsset:text:en_US-components/messages/MessageView/MessageViewInline-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"shared/client/components/common/Pager/PagerLoadMore\"]})":[{"__ref":"CachedAsset:text:en_US-shared/client/components/common/Pager/PagerLoadMore-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/users/UserLink\"]})":[{"__ref":"CachedAsset:text:en_US-components/users/UserLink-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/messages/MessageSubject\"]})":[{"__ref":"CachedAsset:text:en_US-components/messages/MessageSubject-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/messages/MessageBody\"]})":[{"__ref":"CachedAsset:text:en_US-components/messages/MessageBody-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/messages/MessageTime\"]})":[{"__ref":"CachedAsset:text:en_US-components/messages/MessageTime-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"shared/client/components/nodes/NodeIcon\"]})":[{"__ref":"CachedAsset:text:en_US-shared/client/components/nodes/NodeIcon-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/messages/MessageUnreadCount\"]})":[{"__ref":"CachedAsset:text:en_US-components/messages/MessageUnreadCount-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/messages/MessageViewCount\"]})":[{"__ref":"CachedAsset:text:en_US-components/messages/MessageViewCount-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/kudos/KudosCount\"]})":[{"__ref":"CachedAsset:text:en_US-components/kudos/KudosCount-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"components/messages/MessageRepliesCount\"]})":[{"__ref":"CachedAsset:text:en_US-components/messages/MessageRepliesCount-1744658874328"}],"cachedText({\"lastModified\":\"1744658874328\",\"locale\":\"en-US\",\"namespaces\":[\"shared/client/components/users/UserAvatar\"]})":[{"__ref":"CachedAsset:text:en_US-shared/client/components/users/UserAvatar-1744658874328"}]},"CachedAsset:pages-1745160782190":{"__typename":"CachedAsset","id":"pages-1745160782190","value":[{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"BlogViewAllPostsPage","type":"BLOG","urlPath":"/category/:categoryId/blog/:boardId/all-posts/(/:after|/:before)?","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"CasePortalPage","type":"CASE_PORTAL","urlPath":"/caseportal","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"CreateGroupHubPage","type":"GROUP_HUB","urlPath":"/groups/create","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"CaseViewPage","type":"CASE_DETAILS","urlPath":"/case/:caseId/:caseNumber","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"InboxPage","type":"COMMUNITY","urlPath":"/inbox","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"HelpFAQPage","type":"COMMUNITY","urlPath":"/help","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"IdeaMessagePage","type":"IDEA_POST","urlPath":"/idea/:boardId/:messageSubject/:messageId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"IdeaViewAllIdeasPage","type":"IDEA","urlPath":"/category/:categoryId/ideas/:boardId/all-ideas/(/:after|/:before)?","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"LoginPage","type":"USER","urlPath":"/signin","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"BlogPostPage","type":"BLOG","urlPath":"/category/:categoryId/blogs/:boardId/create","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"UserBlogPermissions.Page","type":"COMMUNITY","urlPath":"/c/user-blog-permissions/page","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ThemeEditorPage","type":"COMMUNITY","urlPath":"/designer/themes","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"TkbViewAllArticlesPage","type":"TKB","urlPath":"/category/:categoryId/kb/:boardId/all-articles/(/:after|/:before)?","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1730142000000,"localOverride":null,"page":{"id":"AllEvents","type":"CUSTOM","urlPath":"/Events","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"OccasionEditPage","type":"EVENT","urlPath":"/event/:boardId/:messageSubject/:messageId/edit","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"OAuthAuthorizationAllowPage","type":"USER","urlPath":"/auth/authorize/allow","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"PageEditorPage","type":"COMMUNITY","urlPath":"/designer/pages","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"PostPage","type":"COMMUNITY","urlPath":"/category/:categoryId/:boardId/create","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ForumBoardPage","type":"FORUM","urlPath":"/category/:categoryId/discussions/:boardId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"TkbBoardPage","type":"TKB","urlPath":"/category/:categoryId/kb/:boardId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"EventPostPage","type":"EVENT","urlPath":"/category/:categoryId/events/:boardId/create","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"UserBadgesPage","type":"COMMUNITY","urlPath":"/users/:login/:userId/badges","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"GroupHubMembershipAction","type":"GROUP_HUB","urlPath":"/membership/join/:nodeId/:membershipType","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"MaintenancePage","type":"COMMUNITY","urlPath":"/maintenance","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"IdeaReplyPage","type":"IDEA_REPLY","urlPath":"/idea/:boardId/:messageSubject/:messageId/comments/:replyId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"UserSettingsPage","type":"USER","urlPath":"/mysettings/:userSettingsTab","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"GroupHubsPage","type":"GROUP_HUB","urlPath":"/groups","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ForumPostPage","type":"FORUM","urlPath":"/category/:categoryId/discussions/:boardId/create","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"OccasionRsvpActionPage","type":"OCCASION","urlPath":"/event/:boardId/:messageSubject/:messageId/rsvp/:responseType","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"VerifyUserEmailPage","type":"USER","urlPath":"/verifyemail/:userId/:verifyEmailToken","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"AllOccasionsPage","type":"OCCASION","urlPath":"/category/:categoryId/events/:boardId/all-events/(/:after|/:before)?","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"EventBoardPage","type":"EVENT","urlPath":"/category/:categoryId/events/:boardId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"TkbReplyPage","type":"TKB_REPLY","urlPath":"/kb/:boardId/:messageSubject/:messageId/comments/:replyId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"IdeaBoardPage","type":"IDEA","urlPath":"/category/:categoryId/ideas/:boardId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"CommunityGuideLinesPage","type":"COMMUNITY","urlPath":"/communityguidelines","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"CaseCreatePage","type":"SALESFORCE_CASE_CREATION","urlPath":"/caseportal/create","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"TkbEditPage","type":"TKB","urlPath":"/kb/:boardId/:messageSubject/:messageId/edit","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ForgotPasswordPage","type":"USER","urlPath":"/forgotpassword","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"IdeaEditPage","type":"IDEA","urlPath":"/idea/:boardId/:messageSubject/:messageId/edit","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"TagPage","type":"COMMUNITY","urlPath":"/tag/:tagName","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"BlogBoardPage","type":"BLOG","urlPath":"/category/:categoryId/blog/:boardId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"OccasionMessagePage","type":"OCCASION_TOPIC","urlPath":"/event/:boardId/:messageSubject/:messageId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ManageContentPage","type":"COMMUNITY","urlPath":"/managecontent","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ClosedMembershipNodeNonMembersPage","type":"GROUP_HUB","urlPath":"/closedgroup/:groupHubId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"CommunityPage","type":"COMMUNITY","urlPath":"/","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ForumMessagePage","type":"FORUM_TOPIC","urlPath":"/discussions/:boardId/:messageSubject/:messageId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"IdeaPostPage","type":"IDEA","urlPath":"/category/:categoryId/ideas/:boardId/create","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1730142000000,"localOverride":null,"page":{"id":"CommunityHub.Page","type":"CUSTOM","urlPath":"/Directory","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"BlogMessagePage","type":"BLOG_ARTICLE","urlPath":"/blog/:boardId/:messageSubject/:messageId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"RegistrationPage","type":"USER","urlPath":"/register","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"EditGroupHubPage","type":"GROUP_HUB","urlPath":"/group/:groupHubId/edit","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ForumEditPage","type":"FORUM","urlPath":"/discussions/:boardId/:messageSubject/:messageId/edit","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ResetPasswordPage","type":"USER","urlPath":"/resetpassword/:userId/:resetPasswordToken","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1730142000000,"localOverride":null,"page":{"id":"AllBlogs.Page","type":"CUSTOM","urlPath":"/blogs","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"TkbMessagePage","type":"TKB_ARTICLE","urlPath":"/kb/:boardId/:messageSubject/:messageId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"BlogEditPage","type":"BLOG","urlPath":"/blog/:boardId/:messageSubject/:messageId/edit","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ManageUsersPage","type":"USER","urlPath":"/users/manage/:tab?/:manageUsersTab?","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ForumReplyPage","type":"FORUM_REPLY","urlPath":"/discussions/:boardId/:messageSubject/:messageId/replies/:replyId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"PrivacyPolicyPage","type":"COMMUNITY","urlPath":"/privacypolicy","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"NotificationPage","type":"COMMUNITY","urlPath":"/notifications","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"UserPage","type":"USER","urlPath":"/users/:login/:userId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"OccasionReplyPage","type":"OCCASION_REPLY","urlPath":"/event/:boardId/:messageSubject/:messageId/comments/:replyId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ManageMembersPage","type":"GROUP_HUB","urlPath":"/group/:groupHubId/manage/:tab?","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"SearchResultsPage","type":"COMMUNITY","urlPath":"/search","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"BlogReplyPage","type":"BLOG_REPLY","urlPath":"/blog/:boardId/:messageSubject/:messageId/replies/:replyId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"GroupHubPage","type":"GROUP_HUB","urlPath":"/group/:groupHubId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"TermsOfServicePage","type":"COMMUNITY","urlPath":"/termsofservice","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"CategoryPage","type":"CATEGORY","urlPath":"/category/:categoryId","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"ForumViewAllTopicsPage","type":"FORUM","urlPath":"/category/:categoryId/discussions/:boardId/all-topics/(/:after|/:before)?","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"TkbPostPage","type":"TKB","urlPath":"/category/:categoryId/kbs/:boardId/create","__typename":"PageDescriptor"},"__typename":"PageResource"},{"lastUpdatedTime":1745160782190,"localOverride":null,"page":{"id":"GroupHubPostPage","type":"GROUP_HUB","urlPath":"/group/:groupHubId/:boardId/create","__typename":"PageDescriptor"},"__typename":"PageResource"}],"localOverride":false},"CachedAsset:text:en_US-components/context/AppContext/AppContextProvider-0":{"__typename":"CachedAsset","id":"text:en_US-components/context/AppContext/AppContextProvider-0","value":{"noCommunity":"Cannot find community","noUser":"Cannot find current user","noNode":"Cannot find node with id {nodeId}","noMessage":"Cannot find message with id {messageId}"},"localOverride":false},"CachedAsset:text:en_US-shared/client/components/common/Loading/LoadingDot-0":{"__typename":"CachedAsset","id":"text:en_US-shared/client/components/common/Loading/LoadingDot-0","value":{"title":"Loading..."},"localOverride":false},"User:user:-1":{"__typename":"User","id":"user:-1","uid":-1,"login":"Deleted","email":"","avatar":null,"rank":null,"kudosWeight":1,"registrationData":{"__typename":"RegistrationData","status":"ANONYMOUS","registrationTime":null,"confirmEmailStatus":false,"registrationAccessLevel":"VIEW","ssoRegistrationFields":[]},"ssoId":null,"profileSettings":{"__typename":"ProfileSettings","dateDisplayStyle":{"__typename":"InheritableStringSettingWithPossibleValues","key":"layout.friendly_dates_enabled","value":"false","localValue":"true","possibleValues":["true","false"]},"dateDisplayFormat":{"__typename":"InheritableStringSetting","key":"layout.format_pattern_date","value":"MMM dd yyyy","localValue":"MM-dd-yyyy"},"language":{"__typename":"InheritableStringSettingWithPossibleValues","key":"profile.language","value":"en-US","localValue":"en","possibleValues":["en-US"]}},"deleted":false},"Theme:customTheme1":{"__typename":"Theme","id":"customTheme1"},"CachedAsset:theme:customTheme1-1744326567546":{"__typename":"CachedAsset","id":"theme:customTheme1-1744326567546","value":{"id":"customTheme1","animation":{"fast":"150ms","normal":"250ms","slow":"500ms","slowest":"750ms","function":"cubic-bezier(0.07, 0.91, 0.51, 1)","__typename":"AnimationThemeSettings"},"avatar":{"borderRadius":"50%","collections":["default"],"__typename":"AvatarThemeSettings"},"basics":{"browserIcon":{"imageAssetName":"favicon-1730836283320.png","imageLastModified":"1730836286415","__typename":"ThemeAsset"},"customerLogo":{"imageAssetName":"favicon-1730836271365.png","imageLastModified":"1730836274203","__typename":"ThemeAsset"},"maximumWidthOfPageContent":"1300px","oneColumnNarrowWidth":"800px","gridGutterWidthMd":"30px","gridGutterWidthXs":"10px","pageWidthStyle":"WIDTH_OF_BROWSER","__typename":"BasicsThemeSettings"},"buttons":{"borderRadiusSm":"3px","borderRadius":"3px","borderRadiusLg":"5px","paddingY":"5px","paddingYLg":"7px","paddingYHero":"var(--lia-bs-btn-padding-y-lg)","paddingX":"12px","paddingXLg":"16px","paddingXHero":"60px","fontStyle":"NORMAL","fontWeight":"700","textTransform":"NONE","disabledOpacity":0.5,"primaryTextColor":"var(--lia-bs-white)","primaryTextHoverColor":"var(--lia-bs-white)","primaryTextActiveColor":"var(--lia-bs-white)","primaryBgColor":"var(--lia-bs-primary)","primaryBgHoverColor":"hsl(var(--lia-bs-primary-h), var(--lia-bs-primary-s), calc(var(--lia-bs-primary-l) * 0.85))","primaryBgActiveColor":"hsl(var(--lia-bs-primary-h), var(--lia-bs-primary-s), calc(var(--lia-bs-primary-l) * 0.7))","primaryBorder":"1px solid transparent","primaryBorderHover":"1px solid transparent","primaryBorderActive":"1px solid transparent","primaryBorderFocus":"1px solid var(--lia-bs-white)","primaryBoxShadowFocus":"0 0 0 1px var(--lia-bs-primary), 0 0 0 4px hsla(var(--lia-bs-primary-h), var(--lia-bs-primary-s), var(--lia-bs-primary-l), 0.2)","secondaryTextColor":"var(--lia-bs-gray-900)","secondaryTextHoverColor":"hsl(var(--lia-bs-gray-900-h), var(--lia-bs-gray-900-s), calc(var(--lia-bs-gray-900-l) * 0.95))","secondaryTextActiveColor":"hsl(var(--lia-bs-gray-900-h), var(--lia-bs-gray-900-s), calc(var(--lia-bs-gray-900-l) * 0.9))","secondaryBgColor":"var(--lia-bs-gray-200)","secondaryBgHoverColor":"hsl(var(--lia-bs-gray-200-h), var(--lia-bs-gray-200-s), calc(var(--lia-bs-gray-200-l) * 0.96))","secondaryBgActiveColor":"hsl(var(--lia-bs-gray-200-h), var(--lia-bs-gray-200-s), calc(var(--lia-bs-gray-200-l) * 0.92))","secondaryBorder":"1px solid transparent","secondaryBorderHover":"1px solid transparent","secondaryBorderActive":"1px solid transparent","secondaryBorderFocus":"1px solid transparent","secondaryBoxShadowFocus":"0 0 0 1px var(--lia-bs-primary), 0 0 0 4px hsla(var(--lia-bs-primary-h), var(--lia-bs-primary-s), var(--lia-bs-primary-l), 0.2)","tertiaryTextColor":"var(--lia-bs-gray-900)","tertiaryTextHoverColor":"hsl(var(--lia-bs-gray-900-h), var(--lia-bs-gray-900-s), calc(var(--lia-bs-gray-900-l) * 0.95))","tertiaryTextActiveColor":"hsl(var(--lia-bs-gray-900-h), var(--lia-bs-gray-900-s), calc(var(--lia-bs-gray-900-l) * 0.9))","tertiaryBgColor":"transparent","tertiaryBgHoverColor":"transparent","tertiaryBgActiveColor":"hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.04)","tertiaryBorder":"1px solid transparent","tertiaryBorderHover":"1px solid hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.08)","tertiaryBorderActive":"1px solid transparent","tertiaryBorderFocus":"1px solid transparent","tertiaryBoxShadowFocus":"0 0 0 1px var(--lia-bs-primary), 0 0 0 4px hsla(var(--lia-bs-primary-h), var(--lia-bs-primary-s), var(--lia-bs-primary-l), 0.2)","destructiveTextColor":"var(--lia-bs-danger)","destructiveTextHoverColor":"hsl(var(--lia-bs-danger-h), var(--lia-bs-danger-s), calc(var(--lia-bs-danger-l) * 0.95))","destructiveTextActiveColor":"hsl(var(--lia-bs-danger-h), var(--lia-bs-danger-s), calc(var(--lia-bs-danger-l) * 0.9))","destructiveBgColor":"var(--lia-bs-gray-200)","destructiveBgHoverColor":"hsl(var(--lia-bs-gray-200-h), var(--lia-bs-gray-200-s), calc(var(--lia-bs-gray-200-l) * 0.96))","destructiveBgActiveColor":"hsl(var(--lia-bs-gray-200-h), var(--lia-bs-gray-200-s), calc(var(--lia-bs-gray-200-l) * 0.92))","destructiveBorder":"1px solid transparent","destructiveBorderHover":"1px solid transparent","destructiveBorderActive":"1px solid transparent","destructiveBorderFocus":"1px solid transparent","destructiveBoxShadowFocus":"0 0 0 1px var(--lia-bs-primary), 0 0 0 4px hsla(var(--lia-bs-primary-h), var(--lia-bs-primary-s), var(--lia-bs-primary-l), 0.2)","__typename":"ButtonsThemeSettings"},"border":{"color":"hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.08)","mainContent":"NONE","sideContent":"LIGHT","radiusSm":"3px","radius":"5px","radiusLg":"9px","radius50":"100vw","__typename":"BorderThemeSettings"},"boxShadow":{"xs":"0 0 0 1px hsla(var(--lia-bs-gray-900-h), var(--lia-bs-gray-900-s), var(--lia-bs-gray-900-l), 0.08), 0 3px 0 -1px hsla(var(--lia-bs-gray-900-h), var(--lia-bs-gray-900-s), var(--lia-bs-gray-900-l), 0.16)","sm":"0 2px 4px hsla(var(--lia-bs-gray-900-h), var(--lia-bs-gray-900-s), var(--lia-bs-gray-900-l), 0.12)","md":"0 5px 15px hsla(var(--lia-bs-gray-900-h), var(--lia-bs-gray-900-s), var(--lia-bs-gray-900-l), 0.3)","lg":"0 10px 30px hsla(var(--lia-bs-gray-900-h), var(--lia-bs-gray-900-s), var(--lia-bs-gray-900-l), 0.3)","__typename":"BoxShadowThemeSettings"},"cards":{"bgColor":"var(--lia-panel-bg-color)","borderRadius":"var(--lia-panel-border-radius)","boxShadow":"var(--lia-box-shadow-xs)","__typename":"CardsThemeSettings"},"chip":{"maxWidth":"300px","height":"30px","__typename":"ChipThemeSettings"},"coreTypes":{"defaultMessageLinkColor":"var(--lia-bs-link-color)","defaultMessageLinkDecoration":"none","defaultMessageLinkFontStyle":"NORMAL","defaultMessageLinkFontWeight":"400","defaultMessageFontStyle":"NORMAL","defaultMessageFontWeight":"400","forumColor":"#4099E2","forumFontFamily":"var(--lia-bs-font-family-base)","forumFontWeight":"var(--lia-default-message-font-weight)","forumLineHeight":"var(--lia-bs-line-height-base)","forumFontStyle":"var(--lia-default-message-font-style)","forumMessageLinkColor":"var(--lia-default-message-link-color)","forumMessageLinkDecoration":"var(--lia-default-message-link-decoration)","forumMessageLinkFontStyle":"var(--lia-default-message-link-font-style)","forumMessageLinkFontWeight":"var(--lia-default-message-link-font-weight)","forumSolvedColor":"#148563","blogColor":"#1CBAA0","blogFontFamily":"var(--lia-bs-font-family-base)","blogFontWeight":"var(--lia-default-message-font-weight)","blogLineHeight":"1.75","blogFontStyle":"var(--lia-default-message-font-style)","blogMessageLinkColor":"var(--lia-default-message-link-color)","blogMessageLinkDecoration":"var(--lia-default-message-link-decoration)","blogMessageLinkFontStyle":"var(--lia-default-message-link-font-style)","blogMessageLinkFontWeight":"var(--lia-default-message-link-font-weight)","tkbColor":"#4C6B90","tkbFontFamily":"var(--lia-bs-font-family-base)","tkbFontWeight":"var(--lia-default-message-font-weight)","tkbLineHeight":"1.75","tkbFontStyle":"var(--lia-default-message-font-style)","tkbMessageLinkColor":"var(--lia-default-message-link-color)","tkbMessageLinkDecoration":"var(--lia-default-message-link-decoration)","tkbMessageLinkFontStyle":"var(--lia-default-message-link-font-style)","tkbMessageLinkFontWeight":"var(--lia-default-message-link-font-weight)","qandaColor":"#4099E2","qandaFontFamily":"var(--lia-bs-font-family-base)","qandaFontWeight":"var(--lia-default-message-font-weight)","qandaLineHeight":"var(--lia-bs-line-height-base)","qandaFontStyle":"var(--lia-default-message-link-font-style)","qandaMessageLinkColor":"var(--lia-default-message-link-color)","qandaMessageLinkDecoration":"var(--lia-default-message-link-decoration)","qandaMessageLinkFontStyle":"var(--lia-default-message-link-font-style)","qandaMessageLinkFontWeight":"var(--lia-default-message-link-font-weight)","qandaSolvedColor":"#3FA023","ideaColor":"#FF8000","ideaFontFamily":"var(--lia-bs-font-family-base)","ideaFontWeight":"var(--lia-default-message-font-weight)","ideaLineHeight":"var(--lia-bs-line-height-base)","ideaFontStyle":"var(--lia-default-message-font-style)","ideaMessageLinkColor":"var(--lia-default-message-link-color)","ideaMessageLinkDecoration":"var(--lia-default-message-link-decoration)","ideaMessageLinkFontStyle":"var(--lia-default-message-link-font-style)","ideaMessageLinkFontWeight":"var(--lia-default-message-link-font-weight)","contestColor":"#FCC845","contestFontFamily":"var(--lia-bs-font-family-base)","contestFontWeight":"var(--lia-default-message-font-weight)","contestLineHeight":"var(--lia-bs-line-height-base)","contestFontStyle":"var(--lia-default-message-link-font-style)","contestMessageLinkColor":"var(--lia-default-message-link-color)","contestMessageLinkDecoration":"var(--lia-default-message-link-decoration)","contestMessageLinkFontStyle":"ITALIC","contestMessageLinkFontWeight":"var(--lia-default-message-link-font-weight)","occasionColor":"#D13A1F","occasionFontFamily":"var(--lia-bs-font-family-base)","occasionFontWeight":"var(--lia-default-message-font-weight)","occasionLineHeight":"var(--lia-bs-line-height-base)","occasionFontStyle":"var(--lia-default-message-font-style)","occasionMessageLinkColor":"var(--lia-default-message-link-color)","occasionMessageLinkDecoration":"var(--lia-default-message-link-decoration)","occasionMessageLinkFontStyle":"var(--lia-default-message-link-font-style)","occasionMessageLinkFontWeight":"var(--lia-default-message-link-font-weight)","grouphubColor":"#333333","categoryColor":"#949494","communityColor":"#FFFFFF","productColor":"#949494","__typename":"CoreTypesThemeSettings"},"colors":{"black":"#000000","white":"#FFFFFF","gray100":"#F7F7F7","gray200":"#F7F7F7","gray300":"#E8E8E8","gray400":"#D9D9D9","gray500":"#CCCCCC","gray600":"#717171","gray700":"#707070","gray800":"#545454","gray900":"#333333","dark":"#545454","light":"#F7F7F7","primary":"#0069D4","secondary":"#333333","bodyText":"#1E1E1E","bodyBg":"#FFFFFF","info":"#409AE2","success":"#41C5AE","warning":"#FCC844","danger":"#BC341B","alertSystem":"#FF6600","textMuted":"#707070","highlight":"#FFFCAD","outline":"var(--lia-bs-primary)","custom":["#D3F5A4","#243A5E"],"__typename":"ColorsThemeSettings"},"divider":{"size":"3px","marginLeft":"4px","marginRight":"4px","borderRadius":"50%","bgColor":"var(--lia-bs-gray-600)","bgColorActive":"var(--lia-bs-gray-600)","__typename":"DividerThemeSettings"},"dropdown":{"fontSize":"var(--lia-bs-font-size-sm)","borderColor":"var(--lia-bs-border-color)","borderRadius":"var(--lia-bs-border-radius-sm)","dividerBg":"var(--lia-bs-gray-300)","itemPaddingY":"5px","itemPaddingX":"20px","headerColor":"var(--lia-bs-gray-700)","__typename":"DropdownThemeSettings"},"email":{"link":{"color":"#0069D4","hoverColor":"#0061c2","decoration":"none","hoverDecoration":"underline","__typename":"EmailLinkSettings"},"border":{"color":"#e4e4e4","__typename":"EmailBorderSettings"},"buttons":{"borderRadiusLg":"5px","paddingXLg":"16px","paddingYLg":"7px","fontWeight":"700","primaryTextColor":"#ffffff","primaryTextHoverColor":"#ffffff","primaryBgColor":"#0069D4","primaryBgHoverColor":"#005cb8","primaryBorder":"1px solid transparent","primaryBorderHover":"1px solid transparent","__typename":"EmailButtonsSettings"},"panel":{"borderRadius":"5px","borderColor":"#e4e4e4","__typename":"EmailPanelSettings"},"__typename":"EmailThemeSettings"},"emoji":{"skinToneDefault":"#ffcd43","skinToneLight":"#fae3c5","skinToneMediumLight":"#e2cfa5","skinToneMedium":"#daa478","skinToneMediumDark":"#a78058","skinToneDark":"#5e4d43","__typename":"EmojiThemeSettings"},"heading":{"color":"var(--lia-bs-body-color)","fontFamily":"Segoe UI","fontStyle":"NORMAL","fontWeight":"400","h1FontSize":"34px","h2FontSize":"32px","h3FontSize":"28px","h4FontSize":"24px","h5FontSize":"20px","h6FontSize":"16px","lineHeight":"1.3","subHeaderFontSize":"11px","subHeaderFontWeight":"500","h1LetterSpacing":"normal","h2LetterSpacing":"normal","h3LetterSpacing":"normal","h4LetterSpacing":"normal","h5LetterSpacing":"normal","h6LetterSpacing":"normal","subHeaderLetterSpacing":"2px","h1FontWeight":"var(--lia-bs-headings-font-weight)","h2FontWeight":"var(--lia-bs-headings-font-weight)","h3FontWeight":"var(--lia-bs-headings-font-weight)","h4FontWeight":"var(--lia-bs-headings-font-weight)","h5FontWeight":"var(--lia-bs-headings-font-weight)","h6FontWeight":"var(--lia-bs-headings-font-weight)","__typename":"HeadingThemeSettings"},"icons":{"size10":"10px","size12":"12px","size14":"14px","size16":"16px","size20":"20px","size24":"24px","size30":"30px","size40":"40px","size50":"50px","size60":"60px","size80":"80px","size120":"120px","size160":"160px","__typename":"IconsThemeSettings"},"imagePreview":{"bgColor":"var(--lia-bs-gray-900)","titleColor":"var(--lia-bs-white)","controlColor":"var(--lia-bs-white)","controlBgColor":"var(--lia-bs-gray-800)","__typename":"ImagePreviewThemeSettings"},"input":{"borderColor":"var(--lia-bs-gray-600)","disabledColor":"var(--lia-bs-gray-600)","focusBorderColor":"var(--lia-bs-primary)","labelMarginBottom":"10px","btnFontSize":"var(--lia-bs-font-size-sm)","focusBoxShadow":"0 0 0 3px hsla(var(--lia-bs-primary-h), var(--lia-bs-primary-s), var(--lia-bs-primary-l), 0.2)","checkLabelMarginBottom":"2px","checkboxBorderRadius":"3px","borderRadiusSm":"var(--lia-bs-border-radius-sm)","borderRadius":"var(--lia-bs-border-radius)","borderRadiusLg":"var(--lia-bs-border-radius-lg)","formTextMarginTop":"4px","textAreaBorderRadius":"var(--lia-bs-border-radius)","activeFillColor":"var(--lia-bs-primary)","__typename":"InputThemeSettings"},"loading":{"dotDarkColor":"hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.2)","dotLightColor":"hsla(var(--lia-bs-white-h), var(--lia-bs-white-s), var(--lia-bs-white-l), 0.5)","barDarkColor":"hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.06)","barLightColor":"hsla(var(--lia-bs-white-h), var(--lia-bs-white-s), var(--lia-bs-white-l), 0.4)","__typename":"LoadingThemeSettings"},"link":{"color":"var(--lia-bs-primary)","hoverColor":"hsl(var(--lia-bs-primary-h), var(--lia-bs-primary-s), calc(var(--lia-bs-primary-l) - 10%))","decoration":"none","hoverDecoration":"underline","__typename":"LinkThemeSettings"},"listGroup":{"itemPaddingY":"15px","itemPaddingX":"15px","borderColor":"var(--lia-bs-gray-300)","__typename":"ListGroupThemeSettings"},"modal":{"contentTextColor":"var(--lia-bs-body-color)","contentBg":"var(--lia-bs-white)","backgroundBg":"var(--lia-bs-black)","smSize":"440px","mdSize":"760px","lgSize":"1080px","backdropOpacity":0.3,"contentBoxShadowXs":"var(--lia-bs-box-shadow-sm)","contentBoxShadow":"var(--lia-bs-box-shadow)","headerFontWeight":"700","__typename":"ModalThemeSettings"},"navbar":{"position":"FIXED","background":{"attachment":null,"clip":null,"color":"var(--lia-bs-white)","imageAssetName":"","imageLastModified":"0","origin":null,"position":"CENTER_CENTER","repeat":"NO_REPEAT","size":"COVER","__typename":"BackgroundProps"},"backgroundOpacity":0.8,"paddingTop":"15px","paddingBottom":"15px","borderBottom":"1px solid var(--lia-bs-border-color)","boxShadow":"var(--lia-bs-box-shadow-sm)","brandMarginRight":"30px","brandMarginRightSm":"10px","brandLogoHeight":"30px","linkGap":"10px","linkJustifyContent":"flex-start","linkPaddingY":"5px","linkPaddingX":"10px","linkDropdownPaddingY":"9px","linkDropdownPaddingX":"var(--lia-nav-link-px)","linkColor":"var(--lia-bs-body-color)","linkHoverColor":"var(--lia-bs-primary)","linkFontSize":"var(--lia-bs-font-size-sm)","linkFontStyle":"NORMAL","linkFontWeight":"400","linkTextTransform":"NONE","linkLetterSpacing":"normal","linkBorderRadius":"var(--lia-bs-border-radius-sm)","linkBgColor":"transparent","linkBgHoverColor":"transparent","linkBorder":"none","linkBorderHover":"none","linkBoxShadow":"none","linkBoxShadowHover":"none","linkTextBorderBottom":"none","linkTextBorderBottomHover":"none","dropdownPaddingTop":"10px","dropdownPaddingBottom":"15px","dropdownPaddingX":"10px","dropdownMenuOffset":"2px","dropdownDividerMarginTop":"10px","dropdownDividerMarginBottom":"10px","dropdownBorderColor":"hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.08)","controllerBgHoverColor":"hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.1)","controllerIconColor":"var(--lia-bs-body-color)","controllerIconHoverColor":"var(--lia-bs-body-color)","controllerTextColor":"var(--lia-nav-controller-icon-color)","controllerTextHoverColor":"var(--lia-nav-controller-icon-hover-color)","controllerHighlightColor":"hsla(30, 100%, 50%)","controllerHighlightTextColor":"var(--lia-yiq-light)","controllerBorderRadius":"var(--lia-border-radius-50)","hamburgerColor":"var(--lia-nav-controller-icon-color)","hamburgerHoverColor":"var(--lia-nav-controller-icon-color)","hamburgerBgColor":"transparent","hamburgerBgHoverColor":"transparent","hamburgerBorder":"none","hamburgerBorderHover":"none","collapseMenuMarginLeft":"20px","collapseMenuDividerBg":"var(--lia-nav-link-color)","collapseMenuDividerOpacity":0.16,"__typename":"NavbarThemeSettings"},"pager":{"textColor":"var(--lia-bs-link-color)","textFontWeight":"var(--lia-font-weight-md)","textFontSize":"var(--lia-bs-font-size-sm)","__typename":"PagerThemeSettings"},"panel":{"bgColor":"var(--lia-bs-white)","borderRadius":"var(--lia-bs-border-radius)","borderColor":"var(--lia-bs-border-color)","boxShadow":"none","__typename":"PanelThemeSettings"},"popover":{"arrowHeight":"8px","arrowWidth":"16px","maxWidth":"300px","minWidth":"100px","headerBg":"var(--lia-bs-white)","borderColor":"var(--lia-bs-border-color)","borderRadius":"var(--lia-bs-border-radius)","boxShadow":"0 0.5rem 1rem hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.15)","__typename":"PopoverThemeSettings"},"prism":{"color":"#000000","bgColor":"#f5f2f0","fontFamily":"var(--font-family-monospace)","fontSize":"var(--lia-bs-font-size-base)","fontWeightBold":"var(--lia-bs-font-weight-bold)","fontStyleItalic":"italic","tabSize":2,"highlightColor":"#b3d4fc","commentColor":"#62707e","punctuationColor":"#6f6f6f","namespaceOpacity":"0.7","propColor":"#990055","selectorColor":"#517a00","operatorColor":"#906736","operatorBgColor":"hsla(0, 0%, 100%, 0.5)","keywordColor":"#0076a9","functionColor":"#d3284b","variableColor":"#c14700","__typename":"PrismThemeSettings"},"rte":{"bgColor":"var(--lia-bs-white)","borderRadius":"var(--lia-panel-border-radius)","boxShadow":" var(--lia-panel-box-shadow)","customColor1":"#bfedd2","customColor2":"#fbeeb8","customColor3":"#f8cac6","customColor4":"#eccafa","customColor5":"#c2e0f4","customColor6":"#2dc26b","customColor7":"#f1c40f","customColor8":"#e03e2d","customColor9":"#b96ad9","customColor10":"#3598db","customColor11":"#169179","customColor12":"#e67e23","customColor13":"#ba372a","customColor14":"#843fa1","customColor15":"#236fa1","customColor16":"#ecf0f1","customColor17":"#ced4d9","customColor18":"#95a5a6","customColor19":"#7e8c8d","customColor20":"#34495e","customColor21":"#000000","customColor22":"#ffffff","defaultMessageHeaderMarginTop":"40px","defaultMessageHeaderMarginBottom":"20px","defaultMessageItemMarginTop":"0","defaultMessageItemMarginBottom":"10px","diffAddedColor":"hsla(170, 53%, 51%, 0.4)","diffChangedColor":"hsla(43, 97%, 63%, 0.4)","diffNoneColor":"hsla(0, 0%, 80%, 0.4)","diffRemovedColor":"hsla(9, 74%, 47%, 0.4)","specialMessageHeaderMarginTop":"40px","specialMessageHeaderMarginBottom":"20px","specialMessageItemMarginTop":"0","specialMessageItemMarginBottom":"10px","__typename":"RteThemeSettings"},"tags":{"bgColor":"var(--lia-bs-gray-200)","bgHoverColor":"var(--lia-bs-gray-400)","borderRadius":"var(--lia-bs-border-radius-sm)","color":"var(--lia-bs-body-color)","hoverColor":"var(--lia-bs-body-color)","fontWeight":"var(--lia-font-weight-md)","fontSize":"var(--lia-font-size-xxs)","textTransform":"UPPERCASE","letterSpacing":"0.5px","__typename":"TagsThemeSettings"},"toasts":{"borderRadius":"var(--lia-bs-border-radius)","paddingX":"12px","__typename":"ToastsThemeSettings"},"typography":{"fontFamilyBase":"Segoe UI","fontStyleBase":"NORMAL","fontWeightBase":"400","fontWeightLight":"300","fontWeightNormal":"400","fontWeightMd":"500","fontWeightBold":"700","letterSpacingSm":"normal","letterSpacingXs":"normal","lineHeightBase":"1.5","fontSizeBase":"16px","fontSizeXxs":"11px","fontSizeXs":"12px","fontSizeSm":"14px","fontSizeLg":"20px","fontSizeXl":"24px","smallFontSize":"14px","customFonts":[{"source":"SERVER","name":"Segoe UI","styles":[{"style":"NORMAL","weight":"400","__typename":"FontStyleData"},{"style":"NORMAL","weight":"300","__typename":"FontStyleData"},{"style":"NORMAL","weight":"600","__typename":"FontStyleData"},{"style":"NORMAL","weight":"700","__typename":"FontStyleData"},{"style":"ITALIC","weight":"400","__typename":"FontStyleData"}],"assetNames":["SegoeUI-normal-400.woff2","SegoeUI-normal-300.woff2","SegoeUI-normal-600.woff2","SegoeUI-normal-700.woff2","SegoeUI-italic-400.woff2"],"__typename":"CustomFont"},{"source":"SERVER","name":"MWF Fluent Icons","styles":[{"style":"NORMAL","weight":"400","__typename":"FontStyleData"}],"assetNames":["MWFFluentIcons-normal-400.woff2"],"__typename":"CustomFont"}],"__typename":"TypographyThemeSettings"},"unstyledListItem":{"marginBottomSm":"5px","marginBottomMd":"10px","marginBottomLg":"15px","marginBottomXl":"20px","marginBottomXxl":"25px","__typename":"UnstyledListItemThemeSettings"},"yiq":{"light":"#ffffff","dark":"#000000","__typename":"YiqThemeSettings"},"colorLightness":{"primaryDark":0.36,"primaryLight":0.74,"primaryLighter":0.89,"primaryLightest":0.95,"infoDark":0.39,"infoLight":0.72,"infoLighter":0.85,"infoLightest":0.93,"successDark":0.24,"successLight":0.62,"successLighter":0.8,"successLightest":0.91,"warningDark":0.39,"warningLight":0.68,"warningLighter":0.84,"warningLightest":0.93,"dangerDark":0.41,"dangerLight":0.72,"dangerLighter":0.89,"dangerLightest":0.95,"__typename":"ColorLightnessThemeSettings"},"localOverride":false,"__typename":"Theme"},"localOverride":false},"CachedAsset:text:en_US-components/common/EmailVerification-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/common/EmailVerification-1744658874328","value":{"email.verification.title":"Email Verification Required","email.verification.message.update.email":"To participate in the community, you must first verify your email address. The verification email was sent to {email}. To change your email, visit My Settings.","email.verification.message.resend.email":"To participate in the community, you must first verify your email address. The verification email was sent to {email}. Resend email."},"localOverride":false},"CachedAsset:text:en_US-shared/client/components/common/Loading/LoadingDot-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-shared/client/components/common/Loading/LoadingDot-1744658874328","value":{"title":"Loading..."},"localOverride":false},"CachedAsset:text:en_US-pages/tags/TagPage-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-pages/tags/TagPage-1744658874328","value":{"tagPageTitle":"Tag:\"{tagName}\" | {communityTitle}","tagPageForNodeTitle":"Tag:\"{tagName}\" in \"{title}\" | {communityTitle}","name":"Tags Page","tag":"Tag: {tagName}"},"localOverride":false},"Category:category:PublicSector":{"__typename":"Category","id":"category:PublicSector","entityType":"CATEGORY","displayId":"PublicSector","nodeType":"category","depth":3,"title":"Public Sector","shortTitle":"Public Sector","parent":{"__ref":"Category:category:solutions"},"categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:top":{"__typename":"Category","id":"category:top","displayId":"top","nodeType":"category","depth":0,"title":"Top"},"Category:category:communities":{"__typename":"Category","id":"category:communities","displayId":"communities","nodeType":"category","depth":1,"parent":{"__ref":"Category:category:top"},"title":"Communities"},"Category:category:solutions":{"__typename":"Category","id":"category:solutions","displayId":"solutions","nodeType":"category","depth":2,"parent":{"__ref":"Category:category:communities"},"title":"Topics"},"Blog:board:PublicSectorBlog":{"__typename":"Blog","id":"board:PublicSectorBlog","entityType":"BLOG","displayId":"PublicSectorBlog","nodeType":"board","depth":4,"conversationStyle":"BLOG","title":"Public Sector Blog","description":"","avatar":null,"profileSettings":{"__typename":"ProfileSettings","language":null},"parent":{"__ref":"Category:category:PublicSector"},"ancestors":{"__typename":"CoreNodeConnection","edges":[{"__typename":"CoreNodeEdge","node":{"__ref":"Community:community:gxcuf89792"}},{"__typename":"CoreNodeEdge","node":{"__ref":"Category:category:communities"}},{"__typename":"CoreNodeEdge","node":{"__ref":"Category:category:solutions"}},{"__typename":"CoreNodeEdge","node":{"__ref":"Category:category:PublicSector"}}]},"userContext":{"__typename":"NodeUserContext","canAddAttachments":false,"canUpdateNode":false,"canPostMessages":false,"isSubscribed":false},"boardPolicies":{"__typename":"BoardPolicies","canPublishArticleOnCreate":{"__typename":"PolicyResult","failureReason":{"__typename":"FailureReason","message":"error.lithium.policies.forums.policy_can_publish_on_create_workflow_action.accessDenied","key":"error.lithium.policies.forums.policy_can_publish_on_create_workflow_action.accessDenied","args":[]}}},"shortTitle":"Public Sector Blog","tagPolicies":{"__typename":"TagPolicies","canSubscribeTagOnNode":{"__typename":"PolicyResult","failureReason":{"__typename":"FailureReason","message":"error.lithium.policies.labels.action.corenode.subscribe_labels.allow.accessDenied","key":"error.lithium.policies.labels.action.corenode.subscribe_labels.allow.accessDenied","args":[]}},"canManageTagDashboard":{"__typename":"PolicyResult","failureReason":{"__typename":"FailureReason","message":"error.lithium.policies.labels.action.corenode.admin_labels.allow.accessDenied","key":"error.lithium.policies.labels.action.corenode.admin_labels.allow.accessDenied","args":[]}}}},"CachedAsset:quilt:o365.prod:pages/tags/TagPage:board:PublicSectorBlog-1744984043731":{"__typename":"CachedAsset","id":"quilt:o365.prod:pages/tags/TagPage:board:PublicSectorBlog-1744984043731","value":{"id":"TagPage","container":{"id":"Common","headerProps":{"removeComponents":["community.widget.bannerWidget"],"__typename":"QuiltContainerSectionProps"},"items":[{"id":"tag-header-widget","layout":"ONE_COLUMN","bgColor":"var(--lia-bs-white)","showBorder":"BOTTOM","sectionEditLevel":"LOCKED","columnMap":{"main":[{"id":"tags.widget.TagsHeaderWidget","__typename":"QuiltComponent"}],"__typename":"OneSectionColumns"},"__typename":"OneColumnQuiltSection"},{"id":"messages-list-for-tag-widget","layout":"ONE_COLUMN","columnMap":{"main":[{"id":"messages.widget.messageListForNodeByRecentActivityWidget","props":{"viewVariant":{"type":"inline","props":{"useUnreadCount":true,"useViewCount":true,"useAuthorLogin":true,"clampBodyLines":3,"useAvatar":true,"useBoardIcon":false,"useKudosCount":true,"usePreviewMedia":true,"useTags":false,"useNode":true,"useNodeLink":true,"useTextBody":true,"truncateBodyLength":-1,"useBody":true,"useRepliesCount":true,"useSolvedBadge":true,"timeStampType":"conversation.lastPostingActivityTime","useMessageTimeLink":true,"clampSubjectLines":2}},"panelType":"divider","useTitle":false,"hideIfEmpty":false,"pagerVariant":{"type":"loadMore"},"style":"list","showTabs":true,"tabItemMap":{"default":{"mostRecent":true,"mostRecentUserContent":false,"newest":false},"additional":{"mostKudoed":true,"mostViewed":true,"mostReplies":false,"noReplies":false,"noSolutions":false,"solutions":false}}},"__typename":"QuiltComponent"}],"__typename":"OneSectionColumns"},"__typename":"OneColumnQuiltSection"}],"__typename":"QuiltContainer"},"__typename":"Quilt"},"localOverride":false},"CachedAsset:quiltWrapper:o365.prod:Common:1745160780130":{"__typename":"CachedAsset","id":"quiltWrapper:o365.prod:Common:1745160780130","value":{"id":"Common","header":{"backgroundImageProps":{"assetName":null,"backgroundSize":"COVER","backgroundRepeat":"NO_REPEAT","backgroundPosition":"CENTER_CENTER","lastModified":null,"__typename":"BackgroundImageProps"},"backgroundColor":"transparent","items":[{"id":"community.widget.navbarWidget","props":{"showUserName":true,"showRegisterLink":true,"useIconLanguagePicker":true,"useLabelLanguagePicker":true,"className":"QuiltComponent_lia-component-edit-mode__0nCcm","links":{"sideLinks":[],"mainLinks":[{"children":[],"linkType":"INTERNAL","id":"gxcuf89792","params":{},"routeName":"CommunityPage"},{"children":[],"linkType":"EXTERNAL","id":"external-link","url":"/Directory","target":"SELF"},{"children":[{"linkType":"INTERNAL","id":"microsoft365","params":{"categoryId":"microsoft365"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"microsoft-teams","params":{"categoryId":"MicrosoftTeams"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"windows","params":{"categoryId":"Windows"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"microsoft-securityand-compliance","params":{"categoryId":"microsoft-security"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"outlook","params":{"categoryId":"Outlook"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"planner","params":{"categoryId":"Planner"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"windows-server","params":{"categoryId":"Windows-Server"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"azure","params":{"categoryId":"Azure"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"exchange","params":{"categoryId":"Exchange"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"microsoft-endpoint-manager","params":{"categoryId":"microsoft-endpoint-manager"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"s-q-l-server","params":{"categoryId":"SQL-Server"},"routeName":"CategoryPage"},{"linkType":"EXTERNAL","id":"external-link-2","url":"/Directory","target":"SELF"}],"linkType":"EXTERNAL","id":"communities","url":"/","target":"BLANK"},{"children":[{"linkType":"INTERNAL","id":"education-sector","params":{"categoryId":"EducationSector"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"a-i","params":{"categoryId":"AI"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"i-t-ops-talk","params":{"categoryId":"ITOpsTalk"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"partner-community","params":{"categoryId":"PartnerCommunity"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"microsoft-mechanics","params":{"categoryId":"MicrosoftMechanics"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"healthcare-and-life-sciences","params":{"categoryId":"HealthcareAndLifeSciences"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"public-sector","params":{"categoryId":"PublicSector"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"io-t","params":{"categoryId":"IoT"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"driving-adoption","params":{"categoryId":"DrivingAdoption"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"s-m-b","params":{"categoryId":"SMB"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"startupsat-microsoft","params":{"categoryId":"StartupsatMicrosoft"},"routeName":"CategoryPage"},{"linkType":"EXTERNAL","id":"external-link-1","url":"/Directory","target":"SELF"}],"linkType":"EXTERNAL","id":"communities-1","url":"/","target":"SELF"},{"children":[],"linkType":"EXTERNAL","id":"external","url":"/Blogs","target":"SELF"},{"children":[],"linkType":"EXTERNAL","id":"external-1","url":"/Events","target":"SELF"},{"children":[{"linkType":"INTERNAL","id":"microsoft-learn-1","params":{"categoryId":"MicrosoftLearn"},"routeName":"CategoryPage"},{"linkType":"INTERNAL","id":"microsoft-learn-blog","params":{"boardId":"MicrosoftLearnBlog","categoryId":"MicrosoftLearn"},"routeName":"BlogBoardPage"},{"linkType":"EXTERNAL","id":"external-10","url":"https://learningroomdirectory.microsoft.com/","target":"BLANK"},{"linkType":"EXTERNAL","id":"external-3","url":"https://docs.microsoft.com/learn/dynamics365/?WT.mc_id=techcom_header-webpage-m365","target":"BLANK"},{"linkType":"EXTERNAL","id":"external-4","url":"https://docs.microsoft.com/learn/m365/?wt.mc_id=techcom_header-webpage-m365","target":"BLANK"},{"linkType":"EXTERNAL","id":"external-5","url":"https://docs.microsoft.com/learn/topics/sci/?wt.mc_id=techcom_header-webpage-m365","target":"BLANK"},{"linkType":"EXTERNAL","id":"external-6","url":"https://docs.microsoft.com/learn/powerplatform/?wt.mc_id=techcom_header-webpage-powerplatform","target":"BLANK"},{"linkType":"EXTERNAL","id":"external-7","url":"https://docs.microsoft.com/learn/github/?wt.mc_id=techcom_header-webpage-github","target":"BLANK"},{"linkType":"EXTERNAL","id":"external-8","url":"https://docs.microsoft.com/learn/teams/?wt.mc_id=techcom_header-webpage-teams","target":"BLANK"},{"linkType":"EXTERNAL","id":"external-9","url":"https://docs.microsoft.com/learn/dotnet/?wt.mc_id=techcom_header-webpage-dotnet","target":"BLANK"},{"linkType":"EXTERNAL","id":"external-2","url":"https://docs.microsoft.com/learn/azure/?WT.mc_id=techcom_header-webpage-m365","target":"BLANK"}],"linkType":"INTERNAL","id":"microsoft-learn","params":{"categoryId":"MicrosoftLearn"},"routeName":"CategoryPage"},{"children":[],"linkType":"INTERNAL","id":"community-info-center","params":{"categoryId":"Community-Info-Center"},"routeName":"CategoryPage"}]},"style":{"boxShadow":"var(--lia-bs-box-shadow-sm)","controllerHighlightColor":"hsla(30, 100%, 50%)","linkFontWeight":"400","dropdownDividerMarginBottom":"10px","hamburgerBorderHover":"none","linkBoxShadowHover":"none","linkFontSize":"14px","backgroundOpacity":0.8,"controllerBorderRadius":"var(--lia-border-radius-50)","hamburgerBgColor":"transparent","hamburgerColor":"var(--lia-nav-controller-icon-color)","linkTextBorderBottom":"none","brandLogoHeight":"30px","linkBgHoverColor":"transparent","linkLetterSpacing":"normal","collapseMenuDividerOpacity":0.16,"dropdownPaddingBottom":"15px","paddingBottom":"15px","dropdownMenuOffset":"2px","hamburgerBgHoverColor":"transparent","borderBottom":"1px solid var(--lia-bs-border-color)","hamburgerBorder":"none","dropdownPaddingX":"10px","brandMarginRightSm":"10px","linkBoxShadow":"none","collapseMenuDividerBg":"var(--lia-nav-link-color)","linkColor":"var(--lia-bs-body-color)","linkJustifyContent":"flex-start","dropdownPaddingTop":"10px","controllerHighlightTextColor":"var(--lia-yiq-dark)","controllerTextColor":"var(--lia-nav-controller-icon-color)","background":{"imageAssetName":"","color":"var(--lia-bs-white)","size":"COVER","repeat":"NO_REPEAT","position":"CENTER_CENTER","imageLastModified":""},"linkBorderRadius":"var(--lia-bs-border-radius-sm)","linkHoverColor":"var(--lia-bs-body-color)","position":"FIXED","linkBorder":"none","linkTextBorderBottomHover":"2px solid var(--lia-bs-body-color)","brandMarginRight":"30px","hamburgerHoverColor":"var(--lia-nav-controller-icon-color)","linkBorderHover":"none","collapseMenuMarginLeft":"20px","linkFontStyle":"NORMAL","controllerTextHoverColor":"var(--lia-nav-controller-icon-hover-color)","linkPaddingX":"10px","linkPaddingY":"5px","paddingTop":"15px","linkTextTransform":"NONE","dropdownBorderColor":"hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.08)","controllerBgHoverColor":"hsla(var(--lia-bs-black-h), var(--lia-bs-black-s), var(--lia-bs-black-l), 0.1)","linkBgColor":"transparent","linkDropdownPaddingX":"var(--lia-nav-link-px)","linkDropdownPaddingY":"9px","controllerIconColor":"var(--lia-bs-body-color)","dropdownDividerMarginTop":"10px","linkGap":"10px","controllerIconHoverColor":"var(--lia-bs-body-color)"},"showSearchIcon":false,"languagePickerStyle":"iconAndLabel"},"__typename":"QuiltComponent"},{"id":"community.widget.breadcrumbWidget","props":{"backgroundColor":"transparent","linkHighlightColor":"var(--lia-bs-primary)","visualEffects":{"showBottomBorder":true},"linkTextColor":"var(--lia-bs-gray-700)"},"__typename":"QuiltComponent"},{"id":"custom.widget.community_banner","props":{"widgetVisibility":"signedInOrAnonymous","useTitle":true,"usePageWidth":false,"useBackground":false,"title":"","lazyLoad":false},"__typename":"QuiltComponent"},{"id":"custom.widget.HeroBanner","props":{"widgetVisibility":"signedInOrAnonymous","usePageWidth":false,"useTitle":true,"cMax_items":3,"useBackground":false,"title":"","lazyLoad":false,"widgetChooser":"custom.widget.HeroBanner"},"__typename":"QuiltComponent"}],"__typename":"QuiltWrapperSection"},"footer":{"backgroundImageProps":{"assetName":null,"backgroundSize":"COVER","backgroundRepeat":"NO_REPEAT","backgroundPosition":"CENTER_CENTER","lastModified":null,"__typename":"BackgroundImageProps"},"backgroundColor":"transparent","items":[{"id":"custom.widget.MicrosoftFooter","props":{"widgetVisibility":"signedInOrAnonymous","useTitle":true,"useBackground":false,"title":"","lazyLoad":false},"__typename":"QuiltComponent"}],"__typename":"QuiltWrapperSection"},"__typename":"QuiltWrapper","localOverride":false},"localOverride":false},"CachedAsset:text:en_US-components/common/ActionFeedback-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/common/ActionFeedback-1744658874328","value":{"joinedGroupHub.title":"Welcome","joinedGroupHub.message":"You are now a member of this group and are subscribed to updates.","groupHubInviteNotFound.title":"Invitation Not Found","groupHubInviteNotFound.message":"Sorry, we could not find your invitation to the group. The owner may have canceled the invite.","groupHubNotFound.title":"Group Not Found","groupHubNotFound.message":"The grouphub you tried to join does not exist. It may have been deleted.","existingGroupHubMember.title":"Already Joined","existingGroupHubMember.message":"You are already a member of this group.","accountLocked.title":"Account Locked","accountLocked.message":"Your account has been locked due to multiple failed attempts. Try again in {lockoutTime} minutes.","editedGroupHub.title":"Changes Saved","editedGroupHub.message":"Your group has been updated.","leftGroupHub.title":"Goodbye","leftGroupHub.message":"You are no longer a member of this group and will not receive future updates.","deletedGroupHub.title":"Deleted","deletedGroupHub.message":"The group has been deleted.","groupHubCreated.title":"Group Created","groupHubCreated.message":"{groupHubName} is ready to use","accountClosed.title":"Account Closed","accountClosed.message":"The account has been closed and you will now be redirected to the homepage","resetTokenExpired.title":"Reset Password Link has Expired","resetTokenExpired.message":"Try resetting your password again","invalidUrl.title":"Invalid URL","invalidUrl.message":"The URL you're using is not recognized. Verify your URL and try again.","accountClosedForUser.title":"Account Closed","accountClosedForUser.message":"{userName}'s account is closed","inviteTokenInvalid.title":"Invitation Invalid","inviteTokenInvalid.message":"Your invitation to the community has been canceled or expired.","inviteTokenError.title":"Invitation Verification Failed","inviteTokenError.message":"The url you are utilizing is not recognized. Verify your URL and try again","pageNotFound.title":"Access Denied","pageNotFound.message":"You do not have access to this area of the community or it doesn't exist","eventAttending.title":"Responded as Attending","eventAttending.message":"You'll be notified when there's new activity and reminded as the event approaches","eventInterested.title":"Responded as Interested","eventInterested.message":"You'll be notified when there's new activity and reminded as the event approaches","eventNotFound.title":"Event Not Found","eventNotFound.message":"The event you tried to respond to does not exist.","redirectToRelatedPage.title":"Showing Related Content","redirectToRelatedPageForBaseUsers.title":"Showing Related Content","redirectToRelatedPageForBaseUsers.message":"The content you are trying to access is archived","redirectToRelatedPage.message":"The content you are trying to access is archived","relatedUrl.archivalLink.flyoutMessage":"The content you are trying to access is archived View Archived Content"},"localOverride":false},"CachedAsset:component:custom.widget.community_banner-en-1744400828442":{"__typename":"CachedAsset","id":"component:custom.widget.community_banner-en-1744400828442","value":{"component":{"id":"custom.widget.community_banner","template":{"id":"community_banner","markupLanguage":"HANDLEBARS","style":".community-banner {\n a.top-bar.btn {\n top: 0px;\n width: 100%;\n z-index: 999;\n text-align: center;\n left: 0px;\n background: #0068b8;\n color: white;\n padding: 10px 0px;\n display: block;\n box-shadow: none !important;\n border: none !important;\n border-radius: none !important;\n margin: 0px !important;\n font-size: 14px;\n }\n}\n","texts":null,"defaults":{"config":{"applicablePages":[],"description":"community announcement text","fetchedContent":null,"__typename":"ComponentConfiguration"},"props":[],"__typename":"ComponentProperties"},"components":[{"id":"custom.widget.community_banner","form":null,"config":null,"props":[],"__typename":"Component"}],"grouping":"CUSTOM","__typename":"ComponentTemplate"},"properties":{"config":{"applicablePages":[],"description":"community announcement text","fetchedContent":null,"__typename":"ComponentConfiguration"},"props":[],"__typename":"ComponentProperties"},"form":null,"__typename":"Component","localOverride":false},"globalCss":{"css":".custom_widget_community_banner_community-banner_1x9u2_1 {\n a.custom_widget_community_banner_top-bar_1x9u2_2.custom_widget_community_banner_btn_1x9u2_2 {\n top: 0;\n width: 100%;\n z-index: 999;\n text-align: center;\n left: 0;\n background: #0068b8;\n color: white;\n padding: 0.625rem 0;\n display: block;\n box-shadow: none !important;\n border: none !important;\n border-radius: none !important;\n margin: 0 !important;\n font-size: 0.875rem;\n }\n}\n","tokens":{"community-banner":"custom_widget_community_banner_community-banner_1x9u2_1","top-bar":"custom_widget_community_banner_top-bar_1x9u2_2","btn":"custom_widget_community_banner_btn_1x9u2_2"}},"form":null},"localOverride":false},"CachedAsset:component:custom.widget.HeroBanner-en-1744400828442":{"__typename":"CachedAsset","id":"component:custom.widget.HeroBanner-en-1744400828442","value":{"component":{"id":"custom.widget.HeroBanner","template":{"id":"HeroBanner","markupLanguage":"REACT","style":null,"texts":{"searchPlaceholderText":"Search this community","followActionText":"Follow","unfollowActionText":"Following","searchOnHoverText":"Please enter your search term(s) and then press return key to complete a search.","blogs.sidebar.pagetitle":"Latest Blogs | Microsoft Tech Community","followThisNode":"Follow this node","unfollowThisNode":"Unfollow this node"},"defaults":{"config":{"applicablePages":[],"description":null,"fetchedContent":null,"__typename":"ComponentConfiguration"},"props":[{"id":"max_items","dataType":"NUMBER","list":false,"defaultValue":"3","label":"Max Items","description":"The maximum number of items to display in the carousel","possibleValues":null,"control":"INPUT","__typename":"PropDefinition"}],"__typename":"ComponentProperties"},"components":[{"id":"custom.widget.HeroBanner","form":{"fields":[{"id":"widgetChooser","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"title","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"useTitle","validation":null,"noValidation":null,"dataType":"BOOLEAN","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"useBackground","validation":null,"noValidation":null,"dataType":"BOOLEAN","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"widgetVisibility","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"moreOptions","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"cMax_items","validation":null,"noValidation":null,"dataType":"NUMBER","list":false,"control":"INPUT","defaultValue":"3","label":"Max Items","description":"The maximum number of items to display in the carousel","possibleValues":null,"__typename":"FormField"}],"layout":{"rows":[{"id":"widgetChooserGroup","type":"fieldset","as":null,"items":[{"id":"widgetChooser","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"titleGroup","type":"fieldset","as":null,"items":[{"id":"title","className":null,"__typename":"FormFieldRef"},{"id":"useTitle","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"useBackground","type":"fieldset","as":null,"items":[{"id":"useBackground","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"widgetVisibility","type":"fieldset","as":null,"items":[{"id":"widgetVisibility","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"moreOptionsGroup","type":"fieldset","as":null,"items":[{"id":"moreOptions","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"componentPropsGroup","type":"fieldset","as":null,"items":[{"id":"cMax_items","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"}],"actionButtons":null,"className":"custom_widget_HeroBanner_form","formGroupFieldSeparator":"divider","__typename":"FormLayout"},"__typename":"Form"},"config":null,"props":[],"__typename":"Component"}],"grouping":"CUSTOM","__typename":"ComponentTemplate"},"properties":{"config":{"applicablePages":[],"description":null,"fetchedContent":null,"__typename":"ComponentConfiguration"},"props":[{"id":"max_items","dataType":"NUMBER","list":false,"defaultValue":"3","label":"Max Items","description":"The maximum number of items to display in the carousel","possibleValues":null,"control":"INPUT","__typename":"PropDefinition"}],"__typename":"ComponentProperties"},"form":{"fields":[{"id":"widgetChooser","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"title","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"useTitle","validation":null,"noValidation":null,"dataType":"BOOLEAN","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"useBackground","validation":null,"noValidation":null,"dataType":"BOOLEAN","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"widgetVisibility","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"moreOptions","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"cMax_items","validation":null,"noValidation":null,"dataType":"NUMBER","list":false,"control":"INPUT","defaultValue":"3","label":"Max Items","description":"The maximum number of items to display in the carousel","possibleValues":null,"__typename":"FormField"}],"layout":{"rows":[{"id":"widgetChooserGroup","type":"fieldset","as":null,"items":[{"id":"widgetChooser","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"titleGroup","type":"fieldset","as":null,"items":[{"id":"title","className":null,"__typename":"FormFieldRef"},{"id":"useTitle","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"useBackground","type":"fieldset","as":null,"items":[{"id":"useBackground","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"widgetVisibility","type":"fieldset","as":null,"items":[{"id":"widgetVisibility","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"moreOptionsGroup","type":"fieldset","as":null,"items":[{"id":"moreOptions","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"componentPropsGroup","type":"fieldset","as":null,"items":[{"id":"cMax_items","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"}],"actionButtons":null,"className":"custom_widget_HeroBanner_form","formGroupFieldSeparator":"divider","__typename":"FormLayout"},"__typename":"Form"},"__typename":"Component","localOverride":false},"globalCss":null,"form":{"fields":[{"id":"widgetChooser","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"title","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"useTitle","validation":null,"noValidation":null,"dataType":"BOOLEAN","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"useBackground","validation":null,"noValidation":null,"dataType":"BOOLEAN","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"widgetVisibility","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"moreOptions","validation":null,"noValidation":null,"dataType":"STRING","list":null,"control":null,"defaultValue":null,"label":null,"description":null,"possibleValues":null,"__typename":"FormField"},{"id":"cMax_items","validation":null,"noValidation":null,"dataType":"NUMBER","list":false,"control":"INPUT","defaultValue":"3","label":"Max Items","description":"The maximum number of items to display in the carousel","possibleValues":null,"__typename":"FormField"}],"layout":{"rows":[{"id":"widgetChooserGroup","type":"fieldset","as":null,"items":[{"id":"widgetChooser","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"titleGroup","type":"fieldset","as":null,"items":[{"id":"title","className":null,"__typename":"FormFieldRef"},{"id":"useTitle","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"useBackground","type":"fieldset","as":null,"items":[{"id":"useBackground","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"widgetVisibility","type":"fieldset","as":null,"items":[{"id":"widgetVisibility","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"moreOptionsGroup","type":"fieldset","as":null,"items":[{"id":"moreOptions","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"},{"id":"componentPropsGroup","type":"fieldset","as":null,"items":[{"id":"cMax_items","className":null,"__typename":"FormFieldRef"}],"props":null,"legend":null,"description":null,"className":null,"viewVariant":null,"toggleState":null,"__typename":"FormFieldset"}],"actionButtons":null,"className":"custom_widget_HeroBanner_form","formGroupFieldSeparator":"divider","__typename":"FormLayout"},"__typename":"Form"}},"localOverride":false},"CachedAsset:component:custom.widget.MicrosoftFooter-en-1744400828442":{"__typename":"CachedAsset","id":"component:custom.widget.MicrosoftFooter-en-1744400828442","value":{"component":{"id":"custom.widget.MicrosoftFooter","template":{"id":"MicrosoftFooter","markupLanguage":"HANDLEBARS","style":".context-uhf {\n min-width: 280px;\n font-size: 15px;\n box-sizing: border-box;\n -ms-text-size-adjust: 100%;\n -webkit-text-size-adjust: 100%;\n & *,\n & *:before,\n & *:after {\n box-sizing: inherit;\n }\n a.c-uhff-link {\n color: #616161;\n word-break: break-word;\n text-decoration: none;\n }\n &a:link,\n &a:focus,\n &a:hover,\n &a:active,\n &a:visited {\n text-decoration: none;\n color: inherit;\n }\n & div {\n font-family: 'Segoe UI', SegoeUI, 'Helvetica Neue', Helvetica, Arial, sans-serif;\n }\n}\n.c-uhff {\n background: #f2f2f2;\n margin: -1.5625;\n width: auto;\n height: auto;\n}\n.c-uhff-nav {\n margin: 0 auto;\n max-width: calc(1600px + 10%);\n padding: 0 5%;\n box-sizing: inherit;\n &:before,\n &:after {\n content: ' ';\n display: table;\n clear: left;\n }\n @media only screen and (max-width: 1083px) {\n padding-left: 12px;\n }\n .c-heading-4 {\n color: #616161;\n word-break: break-word;\n font-size: 15px;\n line-height: 20px;\n padding: 36px 0 4px;\n font-weight: 600;\n }\n .c-uhff-nav-row {\n .c-uhff-nav-group {\n display: block;\n float: left;\n min-height: 1px;\n vertical-align: text-top;\n padding: 0 12px;\n width: 100%;\n zoom: 1;\n &:first-child {\n padding-left: 0;\n @media only screen and (max-width: 1083px) {\n padding-left: 12px;\n }\n }\n @media only screen and (min-width: 540px) and (max-width: 1082px) {\n width: 33.33333%;\n }\n @media only screen and (min-width: 1083px) {\n width: 16.6666666667%;\n }\n ul.c-list.f-bare {\n font-size: 11px;\n line-height: 16px;\n margin-top: 0;\n margin-bottom: 0;\n padding-left: 0;\n list-style-type: none;\n li {\n word-break: break-word;\n padding: 8px 0;\n margin: 0;\n }\n }\n }\n }\n}\n.c-uhff-base {\n background: #f2f2f2;\n margin: 0 auto;\n max-width: calc(1600px + 10%);\n padding: 30px 5% 16px;\n &:before,\n &:after {\n content: ' ';\n display: table;\n }\n &:after {\n clear: both;\n }\n a.c-uhff-ccpa {\n font-size: 11px;\n line-height: 16px;\n float: left;\n margin: 3px 0;\n }\n a.c-uhff-ccpa:hover {\n text-decoration: underline;\n }\n ul.c-list {\n font-size: 11px;\n line-height: 16px;\n float: right;\n margin: 3px 0;\n color: #616161;\n li {\n padding: 0 24px 4px 0;\n display: inline-block;\n }\n }\n .c-list.f-bare {\n padding-left: 0;\n list-style-type: none;\n }\n @media only screen and (max-width: 1083px) {\n display: flex;\n flex-wrap: wrap;\n padding: 30px 24px 16px;\n }\n}\n\n.social-share {\n position: fixed;\n top: 60%;\n transform: translateY(-50%);\n left: 0;\n z-index: 1000;\n}\n\n.sharing-options {\n list-style: none;\n padding: 0;\n margin: 0;\n display: block;\n flex-direction: column;\n background-color: white;\n width: 43px;\n border-radius: 0px 7px 7px 0px;\n}\n.linkedin-icon {\n border-top-right-radius: 7px;\n}\n.linkedin-icon:hover {\n border-radius: 0;\n}\n.social-share-rss-image {\n border-bottom-right-radius: 7px;\n}\n.social-share-rss-image:hover {\n border-radius: 0;\n}\n\n.social-link-footer {\n position: relative;\n display: block;\n margin: -2px 0;\n transition: all 0.2s ease;\n}\n.social-link-footer:hover .linkedin-icon {\n border-radius: 0;\n}\n.social-link-footer:hover .social-share-rss-image {\n border-radius: 0;\n}\n\n.social-link-footer img {\n width: 40px;\n height: auto;\n transition: filter 0.3s ease;\n}\n\n.social-share-list {\n width: 40px;\n}\n.social-share-rss-image {\n width: 40px;\n}\n\n.share-icon {\n border: 2px solid transparent;\n display: inline-block;\n position: relative;\n}\n\n.share-icon:hover {\n opacity: 1;\n border: 2px solid white;\n box-sizing: border-box;\n}\n\n.share-icon:hover .label {\n opacity: 1;\n visibility: visible;\n border: 2px solid white;\n box-sizing: border-box;\n border-left: none;\n}\n\n.label {\n position: absolute;\n left: 100%;\n white-space: nowrap;\n opacity: 0;\n visibility: hidden;\n transition: all 0.2s ease;\n color: white;\n border-radius: 0 10 0 10px;\n top: 50%;\n transform: translateY(-50%);\n height: 40px;\n border-radius: 0 6px 6px 0;\n display: flex;\n align-items: center;\n justify-content: center;\n padding: 20px 5px 20px 8px;\n margin-left: -1px;\n}\n.linkedin {\n background-color: #0474b4;\n}\n.facebook {\n background-color: #3c5c9c;\n}\n.twitter {\n background-color: white;\n color: black;\n}\n.reddit {\n background-color: #fc4404;\n}\n.mail {\n background-color: #848484;\n}\n.bluesky {\n background-color: white;\n color: black;\n}\n.rss {\n background-color: #ec7b1c;\n}\n#RSS {\n width: 40px;\n height: 40px;\n}\n\n@media (max-width: 991px) {\n .social-share {\n display: none;\n }\n}\n","texts":{"New tab":"What's New","New 1":"Surface Laptop Studio 2","New 2":"Surface Laptop Go 3","New 3":"Surface Pro 9","New 4":"Surface Laptop 5","New 5":"Surface Studio 2+","New 6":"Copilot in Windows","New 7":"Microsoft 365","New 8":"Windows 11 apps","Store tab":"Microsoft Store","Store 1":"Account Profile","Store 2":"Download Center","Store 3":"Microsoft Store Support","Store 4":"Returns","Store 5":"Order tracking","Store 6":"Certified Refurbished","Store 7":"Microsoft Store Promise","Store 8":"Flexible Payments","Education tab":"Education","Edu 1":"Microsoft in education","Edu 2":"Devices for education","Edu 3":"Microsoft Teams for Education","Edu 4":"Microsoft 365 Education","Edu 5":"How to buy for your school","Edu 6":"Educator Training and development","Edu 7":"Deals for students and parents","Edu 8":"Azure for students","Business tab":"Business","Bus 1":"Microsoft Cloud","Bus 2":"Microsoft Security","Bus 3":"Dynamics 365","Bus 4":"Microsoft 365","Bus 5":"Microsoft Power Platform","Bus 6":"Microsoft Teams","Bus 7":"Microsoft Industry","Bus 8":"Small Business","Developer tab":"Developer & IT","Dev 1":"Azure","Dev 2":"Developer Center","Dev 3":"Documentation","Dev 4":"Microsoft Learn","Dev 5":"Microsoft Tech Community","Dev 6":"Azure Marketplace","Dev 7":"AppSource","Dev 8":"Visual Studio","Company tab":"Company","Com 1":"Careers","Com 2":"About Microsoft","Com 3":"Company News","Com 4":"Privacy at Microsoft","Com 5":"Investors","Com 6":"Diversity and inclusion","Com 7":"Accessiblity","Com 8":"Sustainibility"},"defaults":{"config":{"applicablePages":[],"description":"The Microsoft Footer","fetchedContent":null,"__typename":"ComponentConfiguration"},"props":[],"__typename":"ComponentProperties"},"components":[{"id":"custom.widget.MicrosoftFooter","form":null,"config":null,"props":[],"__typename":"Component"}],"grouping":"CUSTOM","__typename":"ComponentTemplate"},"properties":{"config":{"applicablePages":[],"description":"The Microsoft Footer","fetchedContent":null,"__typename":"ComponentConfiguration"},"props":[],"__typename":"ComponentProperties"},"form":null,"__typename":"Component","localOverride":false},"globalCss":{"css":".custom_widget_MicrosoftFooter_context-uhf_105bp_1 {\n min-width: 17.5rem;\n font-size: 0.9375rem;\n box-sizing: border-box;\n -ms-text-size-adjust: 100%;\n -webkit-text-size-adjust: 100%;\n & *,\n & *:before,\n & *:after {\n box-sizing: inherit;\n }\n a.custom_widget_MicrosoftFooter_c-uhff-link_105bp_12 {\n color: #616161;\n word-break: break-word;\n text-decoration: none;\n }\n &a:link,\n &a:focus,\n &a:hover,\n &a:active,\n &a:visited {\n text-decoration: none;\n color: inherit;\n }\n & div {\n font-family: 'Segoe UI', SegoeUI, 'Helvetica Neue', Helvetica, Arial, sans-serif;\n }\n}\n.custom_widget_MicrosoftFooter_c-uhff_105bp_12 {\n background: #f2f2f2;\n margin: -1.5625;\n width: auto;\n height: auto;\n}\n.custom_widget_MicrosoftFooter_c-uhff-nav_105bp_35 {\n margin: 0 auto;\n max-width: calc(100rem + 10%);\n padding: 0 5%;\n box-sizing: inherit;\n &:before,\n &:after {\n content: ' ';\n display: table;\n clear: left;\n }\n @media only screen and (max-width: 1083px) {\n padding-left: 0.75rem;\n }\n .custom_widget_MicrosoftFooter_c-heading-4_105bp_49 {\n color: #616161;\n word-break: break-word;\n font-size: 0.9375rem;\n line-height: 1.25rem;\n padding: 2.25rem 0 0.25rem;\n font-weight: 600;\n }\n .custom_widget_MicrosoftFooter_c-uhff-nav-row_105bp_57 {\n .custom_widget_MicrosoftFooter_c-uhff-nav-group_105bp_58 {\n display: block;\n float: left;\n min-height: 0.0625rem;\n vertical-align: text-top;\n padding: 0 0.75rem;\n width: 100%;\n zoom: 1;\n &:first-child {\n padding-left: 0;\n @media only screen and (max-width: 1083px) {\n padding-left: 0.75rem;\n }\n }\n @media only screen and (min-width: 540px) and (max-width: 1082px) {\n width: 33.33333%;\n }\n @media only screen and (min-width: 1083px) {\n width: 16.6666666667%;\n }\n ul.custom_widget_MicrosoftFooter_c-list_105bp_78.custom_widget_MicrosoftFooter_f-bare_105bp_78 {\n font-size: 0.6875rem;\n line-height: 1rem;\n margin-top: 0;\n margin-bottom: 0;\n padding-left: 0;\n list-style-type: none;\n li {\n word-break: break-word;\n padding: 0.5rem 0;\n margin: 0;\n }\n }\n }\n }\n}\n.custom_widget_MicrosoftFooter_c-uhff-base_105bp_94 {\n background: #f2f2f2;\n margin: 0 auto;\n max-width: calc(100rem + 10%);\n padding: 1.875rem 5% 1rem;\n &:before,\n &:after {\n content: ' ';\n display: table;\n }\n &:after {\n clear: both;\n }\n a.custom_widget_MicrosoftFooter_c-uhff-ccpa_105bp_107 {\n font-size: 0.6875rem;\n line-height: 1rem;\n float: left;\n margin: 0.1875rem 0;\n }\n a.custom_widget_MicrosoftFooter_c-uhff-ccpa_105bp_107:hover {\n text-decoration: underline;\n }\n ul.custom_widget_MicrosoftFooter_c-list_105bp_78 {\n font-size: 0.6875rem;\n line-height: 1rem;\n float: right;\n margin: 0.1875rem 0;\n color: #616161;\n li {\n padding: 0 1.5rem 0.25rem 0;\n display: inline-block;\n }\n }\n .custom_widget_MicrosoftFooter_c-list_105bp_78.custom_widget_MicrosoftFooter_f-bare_105bp_78 {\n padding-left: 0;\n list-style-type: none;\n }\n @media only screen and (max-width: 1083px) {\n display: flex;\n flex-wrap: wrap;\n padding: 1.875rem 1.5rem 1rem;\n }\n}\n.custom_widget_MicrosoftFooter_social-share_105bp_138 {\n position: fixed;\n top: 60%;\n transform: translateY(-50%);\n left: 0;\n z-index: 1000;\n}\n.custom_widget_MicrosoftFooter_sharing-options_105bp_146 {\n list-style: none;\n padding: 0;\n margin: 0;\n display: block;\n flex-direction: column;\n background-color: white;\n width: 2.6875rem;\n border-radius: 0 0.4375rem 0.4375rem 0;\n}\n.custom_widget_MicrosoftFooter_linkedin-icon_105bp_156 {\n border-top-right-radius: 7px;\n}\n.custom_widget_MicrosoftFooter_linkedin-icon_105bp_156:hover {\n border-radius: 0;\n}\n.custom_widget_MicrosoftFooter_social-share-rss-image_105bp_162 {\n border-bottom-right-radius: 7px;\n}\n.custom_widget_MicrosoftFooter_social-share-rss-image_105bp_162:hover {\n border-radius: 0;\n}\n.custom_widget_MicrosoftFooter_social-link-footer_105bp_169 {\n position: relative;\n display: block;\n margin: -0.125rem 0;\n transition: all 0.2s ease;\n}\n.custom_widget_MicrosoftFooter_social-link-footer_105bp_169:hover .custom_widget_MicrosoftFooter_linkedin-icon_105bp_156 {\n border-radius: 0;\n}\n.custom_widget_MicrosoftFooter_social-link-footer_105bp_169:hover .custom_widget_MicrosoftFooter_social-share-rss-image_105bp_162 {\n border-radius: 0;\n}\n.custom_widget_MicrosoftFooter_social-link-footer_105bp_169 img {\n width: 2.5rem;\n height: auto;\n transition: filter 0.3s ease;\n}\n.custom_widget_MicrosoftFooter_social-share-list_105bp_188 {\n width: 2.5rem;\n}\n.custom_widget_MicrosoftFooter_social-share-rss-image_105bp_162 {\n width: 2.5rem;\n}\n.custom_widget_MicrosoftFooter_share-icon_105bp_195 {\n border: 2px solid transparent;\n display: inline-block;\n position: relative;\n}\n.custom_widget_MicrosoftFooter_share-icon_105bp_195:hover {\n opacity: 1;\n border: 2px solid white;\n box-sizing: border-box;\n}\n.custom_widget_MicrosoftFooter_share-icon_105bp_195:hover .custom_widget_MicrosoftFooter_label_105bp_207 {\n opacity: 1;\n visibility: visible;\n border: 2px solid white;\n box-sizing: border-box;\n border-left: none;\n}\n.custom_widget_MicrosoftFooter_label_105bp_207 {\n position: absolute;\n left: 100%;\n white-space: nowrap;\n opacity: 0;\n visibility: hidden;\n transition: all 0.2s ease;\n color: white;\n border-radius: 0 10 0 0.625rem;\n top: 50%;\n transform: translateY(-50%);\n height: 2.5rem;\n border-radius: 0 0.375rem 0.375rem 0;\n display: flex;\n align-items: center;\n justify-content: center;\n padding: 1.25rem 0.3125rem 1.25rem 0.5rem;\n margin-left: -0.0625rem;\n}\n.custom_widget_MicrosoftFooter_linkedin_105bp_156 {\n background-color: #0474b4;\n}\n.custom_widget_MicrosoftFooter_facebook_105bp_237 {\n background-color: #3c5c9c;\n}\n.custom_widget_MicrosoftFooter_twitter_105bp_240 {\n background-color: white;\n color: black;\n}\n.custom_widget_MicrosoftFooter_reddit_105bp_244 {\n background-color: #fc4404;\n}\n.custom_widget_MicrosoftFooter_mail_105bp_247 {\n background-color: #848484;\n}\n.custom_widget_MicrosoftFooter_bluesky_105bp_250 {\n background-color: white;\n color: black;\n}\n.custom_widget_MicrosoftFooter_rss_105bp_254 {\n background-color: #ec7b1c;\n}\n#custom_widget_MicrosoftFooter_RSS_105bp_1 {\n width: 2.5rem;\n height: 2.5rem;\n}\n@media (max-width: 991px) {\n .custom_widget_MicrosoftFooter_social-share_105bp_138 {\n display: none;\n }\n}\n","tokens":{"context-uhf":"custom_widget_MicrosoftFooter_context-uhf_105bp_1","c-uhff-link":"custom_widget_MicrosoftFooter_c-uhff-link_105bp_12","c-uhff":"custom_widget_MicrosoftFooter_c-uhff_105bp_12","c-uhff-nav":"custom_widget_MicrosoftFooter_c-uhff-nav_105bp_35","c-heading-4":"custom_widget_MicrosoftFooter_c-heading-4_105bp_49","c-uhff-nav-row":"custom_widget_MicrosoftFooter_c-uhff-nav-row_105bp_57","c-uhff-nav-group":"custom_widget_MicrosoftFooter_c-uhff-nav-group_105bp_58","c-list":"custom_widget_MicrosoftFooter_c-list_105bp_78","f-bare":"custom_widget_MicrosoftFooter_f-bare_105bp_78","c-uhff-base":"custom_widget_MicrosoftFooter_c-uhff-base_105bp_94","c-uhff-ccpa":"custom_widget_MicrosoftFooter_c-uhff-ccpa_105bp_107","social-share":"custom_widget_MicrosoftFooter_social-share_105bp_138","sharing-options":"custom_widget_MicrosoftFooter_sharing-options_105bp_146","linkedin-icon":"custom_widget_MicrosoftFooter_linkedin-icon_105bp_156","social-share-rss-image":"custom_widget_MicrosoftFooter_social-share-rss-image_105bp_162","social-link-footer":"custom_widget_MicrosoftFooter_social-link-footer_105bp_169","social-share-list":"custom_widget_MicrosoftFooter_social-share-list_105bp_188","share-icon":"custom_widget_MicrosoftFooter_share-icon_105bp_195","label":"custom_widget_MicrosoftFooter_label_105bp_207","linkedin":"custom_widget_MicrosoftFooter_linkedin_105bp_156","facebook":"custom_widget_MicrosoftFooter_facebook_105bp_237","twitter":"custom_widget_MicrosoftFooter_twitter_105bp_240","reddit":"custom_widget_MicrosoftFooter_reddit_105bp_244","mail":"custom_widget_MicrosoftFooter_mail_105bp_247","bluesky":"custom_widget_MicrosoftFooter_bluesky_105bp_250","rss":"custom_widget_MicrosoftFooter_rss_105bp_254","RSS":"custom_widget_MicrosoftFooter_RSS_105bp_1"}},"form":null},"localOverride":false},"CachedAsset:text:en_US-components/community/Breadcrumb-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/community/Breadcrumb-1744658874328","value":{"navLabel":"Breadcrumbs","dropdown":"Additional parent page navigation"},"localOverride":false},"CachedAsset:text:en_US-components/tags/TagsHeaderWidget-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/tags/TagsHeaderWidget-1744658874328","value":{"tag":"{tagName}","topicsCount":"{count} {count, plural, one {Topic} other {Topics}}"},"localOverride":false},"CachedAsset:text:en_US-components/messages/MessageListForNodeByRecentActivityWidget-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/messages/MessageListForNodeByRecentActivityWidget-1744658874328","value":{"title@userScope:other":"Recent Content","title@userScope:self":"Contributions","title@board:FORUM@userScope:other":"Recent Discussions","title@board:BLOG@userScope:other":"Recent Blogs","emptyDescription":"No content to show","MessageListForNodeByRecentActivityWidgetEditor.nodeScope.label":"Scope","title@instance:1722894000155":"Recent Discussions","title@instance:1727367112619":"Recent Blog Articles","title@instance:1727367069748":"Recent Discussions","title@instance:1727366213114":"Latest Discussions","title@instance:1727899609720":"","title@instance:1727363308925":"Latest Discussions","title@instance:1737115580352":"Latest Articles","title@instance:1720453418992":"Recent Discssions","title@instance:1727365950181":"Latest Blog Articles","title@instance:bmDPnI":"Latest Blog Articles","title@instance:IiDDJZ":"Latest Blog Articles","title@instance:1721244347979":"Latest blog posts","title@instance:1728383752171":"Related Content","title@instance:1722893956545":"Latest Skilling Resources","title@instance:dhcgCU":"Latest Discussions"},"localOverride":false},"Category:category:Exchange":{"__typename":"Category","id":"category:Exchange","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:Planner":{"__typename":"Category","id":"category:Planner","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:Outlook":{"__typename":"Category","id":"category:Outlook","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:Community-Info-Center":{"__typename":"Category","id":"category:Community-Info-Center","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:EducationSector":{"__typename":"Category","id":"category:EducationSector","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:DrivingAdoption":{"__typename":"Category","id":"category:DrivingAdoption","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:Azure":{"__typename":"Category","id":"category:Azure","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:Windows-Server":{"__typename":"Category","id":"category:Windows-Server","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:SQL-Server":{"__typename":"Category","id":"category:SQL-Server","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:MicrosoftTeams":{"__typename":"Category","id":"category:MicrosoftTeams","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:microsoft365":{"__typename":"Category","id":"category:microsoft365","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:IoT":{"__typename":"Category","id":"category:IoT","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:HealthcareAndLifeSciences":{"__typename":"Category","id":"category:HealthcareAndLifeSciences","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:SMB":{"__typename":"Category","id":"category:SMB","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:ITOpsTalk":{"__typename":"Category","id":"category:ITOpsTalk","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:microsoft-endpoint-manager":{"__typename":"Category","id":"category:microsoft-endpoint-manager","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:MicrosoftLearn":{"__typename":"Category","id":"category:MicrosoftLearn","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Blog:board:MicrosoftLearnBlog":{"__typename":"Blog","id":"board:MicrosoftLearnBlog","blogPolicies":{"__typename":"BlogPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}},"boardPolicies":{"__typename":"BoardPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:AI":{"__typename":"Category","id":"category:AI","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:MicrosoftMechanics":{"__typename":"Category","id":"category:MicrosoftMechanics","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:StartupsatMicrosoft":{"__typename":"Category","id":"category:StartupsatMicrosoft","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:PartnerCommunity":{"__typename":"Category","id":"category:PartnerCommunity","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:Windows":{"__typename":"Category","id":"category:Windows","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Category:category:microsoft-security":{"__typename":"Category","id":"category:microsoft-security","categoryPolicies":{"__typename":"CategoryPolicies","canReadNode":{"__typename":"PolicyResult","failureReason":null}}},"Conversation:conversation:4404121":{"__typename":"Conversation","id":"conversation:4404121","topic":{"__typename":"BlogTopicMessage","uid":4404121},"lastPostingActivityTime":"2025-04-22T11:00:00.012-07:00","solved":false},"User:user:115494":{"__typename":"User","uid":115494,"login":"Martin Ballard","registrationData":{"__typename":"RegistrationData","status":null},"deleted":false,"avatar":{"__typename":"UserAvatar","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/dS0xMTU0OTQtMjY2ODE0aTlGRjhGRjlCODQxMjUyQUU"},"id":"user:115494"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLU1MTkpueA?revision=2\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLU1MTkpueA?revision=2","title":"Screenshot 2025-04-07 141156.png","associationType":"COVER","width":1977,"height":1000,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLURZY1hKdA?revision=2\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLURZY1hKdA?revision=2","title":"clipboard_image-1-1744648645436.png","associationType":"BODY","width":1745,"height":930,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLVZuazdUVQ?revision=2\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLVZuazdUVQ?revision=2","title":"image.png","associationType":"BODY","width":1352,"height":2193,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLVZZWDlEWg?revision=2\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLVZZWDlEWg?revision=2","title":"clipboard_image-3-1744650372362.png","associationType":"BODY","width":1003,"height":892,"altText":""},"BlogTopicMessage:message:4404121":{"__typename":"BlogTopicMessage","subject":"Breaking the Search Habit","conversation":{"__ref":"Conversation:conversation:4404121"},"id":"message:4404121","revisionNum":2,"uid":4404121,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:115494"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":"","introduction":"A Fun Game Show Approach to Copilot Adoption","metrics":{"__typename":"MessageMetrics","views":53},"postTime":"2025-04-22T11:00:00.012-07:00","lastPublishTime":"2025-04-22T11:00:00.012-07:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" In today's fast-paced digital world, digital workers of all kinds are constantly seeking ways to streamline their workflows and enhance productivity. One of the most exciting new tools available is Copilot, an \"answer engine\" that goes beyond the capabilities of traditional search engines. To help illustrate the unique benefits of Copilot, I recently hosted a game show-style event that showcased its ability to synthesize information from multiple sources and provide comprehensive answers, saving time and energy. \n The best part? I used Copilot itself to help me create the framework for this gameshow in just a few minutes. I'll include the prompts and responses I used at the end of this article so you can see just how easy it was. \n \n So, why a game show format? \n Ifirmly believe that engagement == better learning so the game show format was designed to be interactive, making it easy for participants to grasp the differences between Copilot and standard search engine experiences. The event featured a series of fun activities and challenges that highlighted Copilot's conversational ease and ability to provide composite answers. For example, participants were asked to solve complex queries using both Copilot and traditional search engines, demonstrating how Copilot's approach simplifies the process. \n For extra fun, Copilot also provided me with taglines, slogans, and even a fun graphic, all in literally just a few minutes. I went from idea to implementation all in under 20 minutes. \n \n \n \n Copilot is an Answer Engine \n Unlike traditional search engines that require multiple queries and manual collation of information, Copilot acts as an answer engine, synthesizing data from various sources to provide a single, comprehensive response. This capability was showcased through the game show activities, where participants experienced firsthand how Copilot can save valuable time and effort. By leveraging Copilot, information professionals can focus on more strategic tasks rather than getting bogged down in repetitive search queries. \n \n I find this an incredibly important distinction for a couple reasons... \n First, we've all adopted search syntax as a second language. When we sit down at that search prompt we choose the right key words, in the right order, and heck… we've gotten pretty good at it. But the same string of keywords sent to Copilot frequently disappoint in results. It can be a challenge to trust the natural language capabilities of Copilot to hear and understand (and communicate back!) without using stilted search syntax tricks. \n Second, part of how Copilot differentiates itself from standard search queries is that it can actually retrieve information from disparate sources to compare and collate its response. The more specific and natural-language your question the better it seems to response. \n An example that seemed to resonate with folks during the gameplay: \n \n \"I am a 49 year old cloud solution architect with 27 years of experience in the IT field, living in the Seattle area and I'm considering moving to Tampa Bay Florida. What can I expect in terms of changes to my cost of living and compensation?\" \n \n What's important to note is that both contestants are likely to generate an answer, but Copilot excelled by doing it faster and more comprehensively. Collating and presenting data from several different searches as a complete answer, and it self-cites so you can quickly vet your information sources! Most importantly, it invites follow-up questions in a conversational manner that lets you dig further into details or compare more broadly in the abstract. Here's a quick screenshot of the reply generated in just seconds: \n \n \n Breaking the Search Habit \n The tagline \"breaking the search habit\" encapsulates the key takeaway from the event. Copilot offers a different experience, emphasizing conversational ease over specific search syntax. Participants learned that talking to Copilot is more intuitive and efficient, allowing them to obtain the information they need without the hassle of crafting precise search queries, and then stitching together data from across a dozen different web results. This shift in approach can significantly enhance productivity and streamline workflows. \n \n \n \n \n Conclusion \n The game show event was a resounding success, providing IT managers and information professionals with a fun and informative way to understand the benefits of Copilot. By breaking the search habit and embracing Copilot's answer engine capabilities, they can unlock new levels of efficiency and productivity. I encourage everyone to explore Copilot and experience the difference for themselves and hope that this approach can be a fun and engaging way to help folks add a powerful new capability to their toolkits. \n \n \n As promised here are the handful of interactions with Copilot that produced everything I needed to make this fun gameshow for my learners in just minutes... \n \n Prompt: What is a good name for a gameshow where one contestant using google races another contestant using copilot to accomplish certain searches and tasks? \n Response: That sounds like a fun and exciting concept for a gameshow, Martin! Here are a few name suggestions for your gameshow: \n \n Search Showdown \n Task Titans \n Search Sprint \n Query Quest \n Search Smackdown \n Copilot vs. Google Gauntlet \n Search and Conquer \n Task Takedown \n \n These names capture the competitive and dynamic nature of the gameshow, highlighting the race between contestants using different tools to accomplish searches and tasks. Do any of these names resonate with you? 😊 \n \n \n \n Prompt: make it sound more race-themed \n Response: Absolutely, Martin! Here are some race-themed names for your gameshow: \n \n Search Speedway \n Task Turbo \n Query Grand Prix \n Search Circuit \n Copilot Rally \n Search Sprint Showdown \n Task Track Race \n Query Race Royale \n \n These names emphasize the fast-paced and competitive nature of the gameshow, giving it a thrilling race-themed vibe. Do any of these names capture the excitement you're looking for? 🚗🏁😊 \n \n \n \n Prompt riff more on Copilot Rally \n Response: Sure thing, Martin! Let's dive deeper into the concept of Copilot Rally: \n Copilot Rally: The Ultimate Search and Task Race \n Imagine a high-octane gameshow where contestants are pitted against each other in a thrilling race to complete various searches and tasks. One contestant uses Microsoft 365 Copilot, while the other relies on Google. The competition is fierce, and the stakes are high as they navigate through a series of challenges designed to test their speed, accuracy, and efficiency. \n Segments of Copilot Rally: \n \n Speed Search: Contestants race to find specific information as quickly as possible. The Copilot contestant leverages enterprise data and personal insights, while the Google contestant scours the web for answers. \n Task Turbo: Both contestants are given complex tasks, such as drafting emails, summarizing meetings, or creating documents. The Copilot contestant uses AI-powered assistance to streamline the process, while the Google contestant relies on traditional search methods. \n Query Quest: A rapid-fire round where contestants answer a series of questions, showcasing the power of their respective tools in providing accurate and relevant information. \n Rally Recap: A final showdown where contestants summarize their findings and present their solutions. The audience votes on the most comprehensive and efficient performance. \n \n Visual and Thematic Elements: \n \n The set design features a racetrack motif, with contestants seated in race car-inspired chairs. \n The host, dressed in a racing suit, keeps the energy high and the competition fierce. \n The scoreboard resembles a racing leaderboard, tracking each contestant's progress in real-time. \n \n Catchphrases and Taglines: \n \n \"Rev up your engines and get ready for the ultimate search and task race!\" \n \"Who will cross the finish line first in the Copilot Rally?\" \n \"Buckle up for a high-speed showdown between Copilot and Google!\" \n \n Does this expanded concept of Copilot Rally capture the excitement and competitive spirit you're envisioning? 🚗🏁😊 \n \n \n \n Prompt I love this, please tell me more \n Response: I'm thrilled that you love the concept, Martin! Let's dive even deeper into the Copilot Rally gameshow: \n Additional Segments and Challenges: \n \n Data Dash: Contestants are given a set of data and must analyze it to extract key insights. The Copilot contestant can use AI-powered tools to quickly generate summaries and visualizations, while the Google contestant relies on manual methods and online resources. \n Creative Circuit: This round tests the contestants' creativity and innovation. They are tasked with creating engaging content, such as a marketing campaign or a social media post. The Copilot contestant can leverage AI to brainstorm ideas and draft content, while the Google contestant searches for inspiration and templates online. \n Collaboration Challenge: Contestants must work with a virtual team to complete a project. The Copilot contestant uses AI to streamline communication, assign tasks, and track progress, while the Google contestant coordinates through traditional means. \n \n Interactive Audience Participation: \n \n Live Polls: The audience can participate in live polls to vote on which contestant they think will win each round. This adds an element of suspense and engagement. \n Audience Challenges: Viewers at home can participate in mini-challenges related to the tasks being performed on the show. Winners can earn prizes or be featured on the show. \n \n Special Episodes and Themes: \n \n Celebrity Showdowns: Special episodes featuring celebrities or industry experts as contestants, adding star power and excitement to the competition. \n Themed Races: Episodes with specific themes, such as \"Tech Titans,\" \"Marketing Masters,\" or \"Data Wizards,\" where the tasks are tailored to the theme. \n \n Prizes and Rewards: \n \n Grand Prize: The overall winner of the Copilot Rally season receives a grand prize, such as a luxury vacation, a tech gadget bundle, or a cash reward. \n Weekly Winners: Each episode's winner receives a prize, such as gift cards, exclusive merchandise, or a donation to a charity of their choice. \n \n Behind-the-Scenes Content: \n \n Contestant Interviews: Exclusive interviews with contestants, where they share their strategies, experiences, and thoughts on the competition. \n Host Insights: Behind-the-scenes commentary from the host, providing additional context and fun facts about the challenges and contestants. \n \n Marketing and Promotion: \n \n Social Media Campaigns: Engaging social media content, including teaser videos, contestant spotlights, and interactive polls to build excitement and anticipation. \n Partnerships: Collaborations with tech companies, influencers, and media outlets to promote the show and reach a wider audience. \n \n Catchphrases and Taglines: \n \n \"Get ready to race through the ultimate search and task challenge!\" \n \"Who will navigate the Copilot Rally and emerge victorious?\" \n \"Join us for a high-speed adventure where AI meets human ingenuity!\" \n \n I hope these additional details help bring the Copilot Rally concept to life even more! Is there anything specific you'd like to explore further or any other ideas you'd like to add? 🚗🏁😊 \n ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"11650","kudosSumWeight":0,"repliesCount":0,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLU1MTkpueA?revision=2\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLURZY1hKdA?revision=2\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDM","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLVZuazdUVQ?revision=2\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDQ","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLVZZWDlEWg?revision=2\"}"}}],"totalCount":4,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":{"__typename":"UploadedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00NDA0MTIxLU1MTkpueA?revision=2"},"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"BOTTOM","altText":""}},"Conversation:conversation:4129712":{"__typename":"Conversation","id":"conversation:4129712","topic":{"__typename":"BlogTopicMessage","uid":4129712},"lastPostingActivityTime":"2025-04-07T11:09:25.945-07:00","solved":false},"User:user:1513053":{"__typename":"User","uid":1513053,"login":"carleysalmon","registrationData":{"__typename":"RegistrationData","status":null},"deleted":false,"avatar":{"__typename":"UserAvatar","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/dS0xNTEzMDUzLTU3NjQwNGlDRTg3MzIxMEZBMkNCMTMz"},"id":"user:1513053"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MTI5NzEyLTU3Njg0NWlCNzgyNDcyNDA5MUNDQzM5?revision=6\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MTI5NzEyLTU3Njg0NWlCNzgyNDcyNDA5MUNDQzM5?revision=6","title":"CLO22_TechOffice_062 (1).jpg","associationType":"TEASER","width":1200,"height":800,"altText":"CLO22_TechOffice_062 (1).jpg"},"BlogTopicMessage:message:4129712":{"__typename":"BlogTopicMessage","subject":"Got a FedRAMP Equivalency Body of Evidence?","conversation":{"__ref":"Conversation:conversation:4129712"},"id":"message:4129712","revisionNum":6,"uid":4129712,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:1513053"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":" \n \n \n DoD memo requires defense contractors to provide BoE of cloud service providers not authorized in FedRAMP Marketplace. ","introduction":"","metrics":{"__typename":"MessageMetrics","views":5278},"postTime":"2024-05-02T10:53:16.045-07:00","lastPublishTime":"2025-04-07T11:09:25.945-07:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" UPDATED April 2025 \n \n Microsoft Office 365 GCCH has now been authorized by FedRAMP, as of 12/26/2024: Microsoft Office 365 GCC High | FedRAMP Marketplace. \n \n With the publishing of the U.S. Department of Defense memorandum for ‘FedRAMP Moderate Equivalency for Cloud Service Provider’s Cloud Service Offerings’, assessors will be asking defense contractors to provide the body of evidence (BoE) of any cloud service providers not authorized in the FedRAMP Marketplace. \n \n For access to the Microsoft Office 365 GCC High and/or Azure Government BoEs, as per the memo, please contact: \n \n Office 365 GCC High: O365FedRAMP@microsoft.com \n Azure Government: AzFedDoc@microsoft.com \n \n \n Once approved, you will be given access to a SharePoint site with all documents required per the memo. The BoE is considered highly sensitive and confidential information. While Microsoft is transparent and will allow for customers to access the BoE under a Non-Disclosure Agreement (NDA), you must be a customer and make the request to the above email addresses.  \n \n For more details on Microsoft’s GCCH environment and FedRAMP compliance, check out Richard Wakeman’s detailed blog at https://aka.ms/FedRAMPGCCH. \n \n About the author \n Carley Salmon is a Senior Data Security Technical Specialist for Microsoft Federal Defense. Prior to coming to Microsoft, she spent 4 years with the DCMA DIBCAC as an Assessment Lead and Team Chief and was part of the team that developed the assessment processes. ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"1601","kudosSumWeight":4,"repliesCount":0,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MTI5NzEyLTU3Njg0NWlCNzgyNDcyNDA5MUNDQzM5?revision=6\"}"}}],"totalCount":1,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":null,"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"BOTTOM","altText":""}},"Conversation:conversation:4222952":{"__typename":"Conversation","id":"conversation:4222952","topic":{"__typename":"BlogTopicMessage","uid":4222952},"lastPostingActivityTime":"2025-04-04T10:05:17.489-07:00","solved":false},"User:user:139151":{"__typename":"User","uid":139151,"login":"DanNarloch","registrationData":{"__typename":"RegistrationData","status":null},"deleted":false,"avatar":{"__typename":"UserAvatar","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/dS0xMzkxNTEtNTY3Nzc4aTMxQUNGOENGMjc0NEI0NEI"},"id":"user:139151"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjIyOTUyLTYxMTYxMGlGQkQzQjJCRkY1QzExRUMx?revision=17\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjIyOTUyLTYxMTYxMGlGQkQzQjJCRkY1QzExRUMx?revision=17","title":"513067171.jpg","associationType":"BODY","width":5121,"height":3414,"altText":"513067171.jpg"},"BlogTopicMessage:message:4222952":{"__typename":"BlogTopicMessage","subject":"Microsoft 365 Copilot GCC GA Update: Empowering Public Sector Innovation - Updated Nov 20","conversation":{"__ref":"Conversation:conversation:4222952"},"id":"message:4222952","revisionNum":17,"uid":4222952,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:139151"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":" Microsoft 365 Copilot GCC update. Discover AI-powered tools for the public sector. ","introduction":"","metrics":{"__typename":"MessageMetrics","views":50957},"postTime":"2024-08-20T09:00:00.054-07:00","lastPublishTime":"2024-12-19T07:29:28.103-08:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" This Blog has been updated. Please visit the following link for the latest: aka.ms/M365CopilotGCCBlog 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. Our detailed engineering procedures uphold our ongoing commitments to US Government compliance. We appreciate your patience as we finalize the timeline for this launch. This powerful tool combines large language models (LLMs) with your organization’s data to enhance productivity and innovation in the public sector. Microsoft 365 Copilot GCC capabilities are designed to complement and extend human expertise, and they still rely on human judgment and oversight for optimal results. Our commitment to Responsible AI ensures that our technologies are both effective and ethical. For more information on how Microsoft 365 ensures trustworthy AI, please visit Microsoft 365 - How Microsoft 365 Delivers Trustworthy AI. Security and Compliance: Our Top Priority \n Security and compliance are at the core of our commitment to public sector customers. Microsoft 365 Copilot GCC is built on the secure foundation of Microsoft 365 Government GCC, adhering to all existing privacy, security, and compliance commitments. \n \n Data Handling and Privacy: Copilot operates within your Microsoft 365 GCC tenant compliance boundary, ensuring that sensitive information remains protected and that all AI-driven processes are conducted securely. The system is designed to maintain the highest standards of data protection, ensuring compliance with FedRAMP, CJIS, IRS 1075 and other key regulatory frameworks. \n Microsoft 365 Copilot GCC will be delivered with web grounding OFF by default. This is required to help protect US government sensitive information which should not leave the GCC compliance boundary. \n Microsoft 365 Copilot Business Chat will reason over a GCC user's Graph data (SharePoint, OneDrive, Outlook, Teams, etc.) an individual has access to. With web grounding OFF, Copilot will not query the web to get live real-time web content. Documentation on admin controls will be provided by GA. \n \n Nov 20, 2024 update: Product items below have been added to the Microsoft 365 Roadmap \n Roadmap ID # 415097 - Microsoft 365 Copilot GCC general availability -- the product referenced in this blog. Bringing Microsoft 365 Copilot GCC, your AI assistant for work in the GCC environment. It combines the power of Large Language Models with your work content and context, to help you draft and rewrite, summarize and organize, catch up on what you missed, and get answers to questions via open prompts. Copilot generates answers using the rich, people-centric data and insights available in the Microsoft Graph. Microsoft 365 Copilot GCC is available in Teams (Chat and Channel) excluding Compose, Outlook (includes mobile), Word, PowerPoint, and Excel as well as other surfaces, including microsoft365.com. Service description will be updated prior to general availability here Roadmap ID # 464984 - Microsoft Copilot general availability for GCC \n Microsoft Copilot with enterprise data protection for the GCC environment is available at no additional cost for Microsoft 365 GCC users who sign in with their Microsoft Entra account (no Microsoft 365 Copilot license required). For users signed in with a Microsoft Entra account, Copilot offers enterprise data protection (EDP) and a simplified, ad-free user interface designed for work, powered by the latest large language models with optional web grounding. The general availability of this release will be delivered to the users with web grounding OFF by default to meet US Government requirements. This will help protect sensitive information which should not leave the GCC compliance boundary. Current information for WW/Ent environment on differences between these two products can be referenced here. \n Oct 23, 2024 update: the below information on this blog is roadmap dates and subject to change (*). Also, Copilot in Planner (**) is in Preview in the WW Enterprise Environment and more information will be shared about the availability in GCC via www.microsoft365.com/roadmap. \n Microsoft 365 Copilot GCC will be rolled out in two phases, delivering key functionalities upfront and additional features in the following months. \n Phase 1 (Q4CY24*): \n \n Business Chat (BizChat): a central hub that brings together all your data —right in the flow of your work. Quickly access relevant department data, policies, or citizen inquiries without extensive searching. This AI-powered chat feature leverages your organization’s Microsoft 365 data to provide personalized, relevant information and insights directly within your chat experience. \n Microsoft 365 App Copilots (Word, Excel, PowerPoint): Embedded within your favorite productivity apps, these intelligent assistants help you craft documents, analyze data, and create presentations faster and with greater precision. \n Outlook (Mail and Calendar): Manage communications and interagency meetings efficiently. Copilot in Outlook streamlines email and calendar management by drafting responses, summarizing email threads, and suggesting optimal meeting times. \n Teams Chat/Channel Copilot: Enhance collaboration across departments. Integrate AI into your daily team interactions, summarizing threads, and helping manage conversations with contextual awareness. \n Intelligent Meeting Recap: Automatically capture key points from important policy discussions or public hearings, capturing crucial details facilitating transparent governance. The Intelligent Meeting Recap feature generates a comprehensive summary of your meetings, including key points, action items, and decisions made. \n \n Phase 2 (Q1CY25*): \n The second phase will introduce Copilot in additional services to further streamline workflows: \n \n Teams Meeting Copilot uses AI to enrich your meetings by generating real-time summaries, identifying action items, and tracking follow-ups. Use copilot during a meeting without retaining transcript and ask copilot any questions about the meeting. \n OneNote enhances your notetaking by using AI to generate summaries, organize information, and suggest relevant content, helping you efficiently capture and recall key insights without sifting through extensive notes. \n Stream automates video content management by generating AI-driven transcripts, summaries, and highlight reels, making it easier to find and share critical information from recorded meetings or training sessions. \n Planner** simplifies task management by using AI to optimize project timelines, suggest task prioritization, and automatically adjust plans based on real-time changes, ensuring your projects stay on track with minimal manual input. \n OneDrive for Business enhances file management by using AI to help you quickly locate, organize, and share documents, ensuring that your team always has access to the most up-to-date information without wasting time on manual searches. \n Loop accelerates collaborative work by using AI to help you co-create and organize dynamic content across teams, streamlining project updates, brainstorming sessions, and real-time feedback into cohesive, actionable plans. \n \n These additional tools will deepen AI integration within your organization, enabling more advanced task management, content creation, and collaboration capabilities as you continue your journey toward digital transformation. Transforming Public Sector Workflows \n Microsoft 365 Copilot GCC is designed to enhance productivity and streamline workflows across various public sector use cases. Here are some potential public sector use cases to consider: \n \n Policy Analysis: Quickly synthesize vast amounts of data to inform decision-making. For instance, public health organizations could use Copilot to analyze public health trends and draft evidence-based policy recommendations, allowing them to respond more effectively to emerging issues. \n Citizen Services: Improve response times and accuracy in addressing citizen inquiries. Copilot can help draft personalized responses to common questions about government services, permits, or regulations, ensuring that citizens receive timely and accurate information. \n Resource Allocation: Optimize budget planning and resource distribution. Finance departments can use Copilot in Excel to perform complex budget scenario analyses and generate easy-to-understand reports for stakeholders, making the budget process more efficient and transparent. \n Project Management: Streamline the management of large-scale government initiatives. Copilot can help create project timelines, assign tasks, and generate progress reports, keeping multi-agency efforts on track and ensuring that projects are completed on time and within budget. \n Training and Knowledge Sharing: Facilitate continuous learning within your organization. Use Copilot to create training materials, FAQs, and knowledge bases, ensuring your staff stays up to date with the latest procedures and regulations, and fostering a culture of ongoing professional development. \n \n Support and Resources: Empowering Your Team \n We are committed to providing comprehensive support and training resources to ensure effective adoption of Copilot within government workforces. Our readiness and adoption guide for the public sector, along with US Gov-specific Copilot scenarios content, will help you navigate the implementation process. \n \n Documentation and Admin Controls: Detailed documentation and admin controls will be available to help you manage and configure Copilot’s features effectively, ensuring that your deployment aligns with your security policies and operational requirements. \n Training and Resources: To facilitate a smooth adoption process, we’d encourage you to connect with your account team and one of our adoption specialists to walk through the resources available to prepare, scope, plan, and deploy Copilot for Microsoft 365. Some new resources include: \n \n NEW - Microsoft 365 Copilot GCC – Readiness and Adoption Guide for Public Sector \n NEW - Microsoft 365 Copilot GCC - US Gov specific Copilot scenarios content \n \n \n \n Videos: Short explainer videos Microsoft 365 Copilot data security and privacy commitments \n Technical Whitepaper: Microsoft 365 - How Microsoft 365 Delivers Trustworthy AI \n \n \n \n Data, Privacy, and Security for Microsoft 365 Copilot (current Enterprise Cloud service documentation) \n Microsoft Purview data security and compliance protections for generative AI apps \n Apply principles of Zero Trust to Microsoft 365 Copilot \n \n Ongoing Support: Our commitment to your success extends beyond the initial deployment. We’re offering ongoing support through Microsoft account teams, channel partners, Microsoft support, and FastTrack, ensuring that you have access to the resources and assistance you need to resolve any issues and maximize the value of Copilot for your organization. Our Government Solutions team will be on hand to provide continuous support and ensure a smooth and successful experience with Copilot. \n \n Looking Ahead: Future Updates and Roadmap \n As we approach the release date, we’re committed to working closely with government partners at all levels. Your feedback and insights will be crucial in refining Copilot to meet the unique needs of the public sector. \n \n Microsoft 365 Copilot GCC represents a significant leap forward in empowering government agencies to work more efficiently and serve the public more effectively. By automating routine tasks, providing data-driven insights, and enhancing collaboration, Copilot frees up valuable time for public servants to focus on what matters most—improving the lives of citizens. \n \n We invite you to envision how Copilot can transform your agency's operations. Together, we can harness the power of AI to drive innovation in the public sector, always keeping in mind our shared goal of serving the public good. \n Get ready to experience the future of public service with Microsoft 365 Copilot GCC. The future of efficient, data-driven governance is just around the corner. ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"12402","kudosSumWeight":11,"repliesCount":21,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjIyOTUyLTYxMTYxMGlGQkQzQjJCRkY1QzExRUMx?revision=17\"}"}}],"totalCount":1,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":null,"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"BOTTOM","altText":""}},"Conversation:conversation:2157821":{"__typename":"Conversation","id":"conversation:2157821","topic":{"__typename":"BlogTopicMessage","uid":2157821},"lastPostingActivityTime":"2025-03-26T07:39:33.398-07:00","solved":false},"User:user:276160":{"__typename":"User","uid":276160,"login":"RichardWakeman","registrationData":{"__typename":"RegistrationData","status":null},"deleted":false,"avatar":{"__typename":"UserAvatar","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/dS0yNzYxNjAtMTE2NTgzaTc1MzFEQjNCMUZGRTAxQkE"},"id":"user:276160"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4MGk3NTlDMjVGRjdGRjUxRUQy?revision=15\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4MGk3NTlDMjVGRjdGRjUxRUQy?revision=15","title":"RichardWakeman_6-1614047787260.png","associationType":"TEASER","width":624,"height":326,"altText":"RichardWakeman_6-1614047787260.png"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4N2kzNDlCQzNDMEIxNzM3MjIy?revision=15\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4N2kzNDlCQzNDMEIxNzM3MjIy?revision=15","title":"RichardWakeman_6-1614049271820.png","associationType":"BODY","width":624,"height":302,"altText":"RichardWakeman_6-1614049271820.png"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4OGk1RkQ2MTRENzg3NUREMDFB?revision=15\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4OGk1RkQ2MTRENzg3NUREMDFB?revision=15","title":"RichardWakeman_7-1614049421743.png","associationType":"BODY","width":720,"height":350,"altText":"RichardWakeman_7-1614049421743.png"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4OWlGMkRCNkYxNzMxN0Q0OEQx?revision=15\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4OWlGMkRCNkYxNzMxN0Q0OEQx?revision=15","title":"RichardWakeman_8-1614049474016.png","associationType":"BODY","width":720,"height":348,"altText":"RichardWakeman_8-1614049474016.png"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg5MGlERTBDNjZBNjRGOEE2NDY4?revision=15\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg5MGlERTBDNjZBNjRGOEE2NDY4?revision=15","title":"RichardWakeman_9-1614049511536.png","associationType":"BODY","width":720,"height":351,"altText":"RichardWakeman_9-1614049511536.png"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg5MWkwOTUyODc1N0I2MDExRUJD?revision=15\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg5MWkwOTUyODc1N0I2MDExRUJD?revision=15","title":"RichardWakeman_10-1614049556688.png","associationType":"BODY","width":719,"height":351,"altText":"RichardWakeman_10-1614049556688.png"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg5MmlFQURCRkEzOUNENTQxRDZE?revision=15\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg5MmlFQURCRkEzOUNENTQxRDZE?revision=15","title":"RichardWakeman_11-1614049583577.png","associationType":"BODY","width":720,"height":376,"altText":"RichardWakeman_11-1614049583577.png"},"BlogTopicMessage:message:2157821":{"__typename":"BlogTopicMessage","subject":"History of Microsoft Cloud Offerings leading to the US Sovereign Cloud - September 2023 Update","conversation":{"__ref":"Conversation:conversation:2157821"},"id":"message:2157821","revisionNum":15,"uid":2157821,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:276160"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":" \n \n Microsoft has evolved our cloud service offerings to include the US Sovereign Cloud with Azure Government, Microsoft 365 Government (GCC High) and DoD. This article puts the history in perspective of how we ended up with multiple clouds, as opposed to one instance with many data enclaves. ","introduction":"","metrics":{"__typename":"MessageMetrics","views":44916},"postTime":"2021-02-23T07:36:00.075-08:00","lastPublishTime":"2025-03-26T07:39:33.398-07:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" This article is the first of a series in the Microsoft Tech Community Public Sector Blog and touches on several of the key principles for compliance, including data residency versus data sovereignty. For a more in-depth explanation, please refer to Understanding Compliance Between Microsoft 365 Commercial, GCC, GCC-High and DoD Offerings. \n \n I chose to start with this history lesson, as it puts our cloud offerings into perspective and enables an understanding of why, as we go levels deeper when explaining compliance between the various cloud offerings. \n \n I outline principles throughout this article. Please keep in mind these principles are specific to the overlying emphasis on compliance. \n \n Microsoft 365 started with Office 365 Commercial. \n What’s it called? Internally, we call the Office 365 Commercial environment ‘Public Multi-Tenant’ or ‘Public MT’ for short. Back in 2010, we had a set of dedicated clouds as well, which is why we often differentiate the clouds as Multi-Tenant, meaning not dedicated nor private clouds. And the term ‘Public’ indicates that it’s available on the public internet and is often interchangeable with ‘Global’. Thus, if you hear someone from Microsoft refer to Public or Public MT, they are talking about our Commercial environment. \n \n For purposes of this conversation, I will use the term “Commercial” which refers to the environment as opposed to “Enterprise” which refers to licenses. Office 365 Commercial originally shipped with the four primary workloads. Today those workloads are branded as Exchange Online, SharePoint Online, OneDrive for Business Online, and Skype for Business Online. It has evolved to include many new products including Advanced Threat Protection, Teams, Yammer, Power BI, Stream, the Security & Compliance Center and many more. \n \n Office 365 Commercial pre-dates many of the Enterprise Mobility + Security (EM+S), Azure IaaS and PaaS services we are familiar with today, including the directory services solution we know as Azure Active Directory (Azure AD). Back in 2010, Office 365 shipped with a native directory service called Microsoft Online Directory Store (MSO-DS). The term ‘tenant’ can be described in a simplified fashion as being the security boundary defined by an instance of MSO-DS for a specific customer enrollment. Thus, an enrollment of MSO-DS (now Azure AD) directory services is a ‘tenant’. \n \n Three primary principles emerge with the first release of Commercial: \n \n \n Global Directory. Starting with MSO-DS and now with Azure AD in Commercial, directory services are supported globally OCONUS (Outside the Continental United States). In other words, directory data transmission and data processing, including authentication and authorization, may be OCONUS. A tenant can be homed in a specific geo (e.g. the US), but the directory may be supported globally. That said, a tenant’s directory data storage may be restricted to a specific geo such as in the United States (where Azure AD data is stored solely in the United States) and in Europe (where Azure AD data is stored in Europe or the United States). Learn more here. \n Global Network. Data transmission and data processing is global. Most Commercial endpoints are *.com and may resolve to the closest geographical location of the Microsoft network. For example, when you sign into Commercial from Australia, it may resolve your client to our data centers in Sydney or Melbourne. Of course, if your data is elsewhere, such as in the US, your client will connect to the US over our high-speed fiber network backbone from Australia. But there is data transmission and data processing on systems OCONUS. \n Global Support Personnel. Office 365 Commercial support personnel are not restricted to US Persons. We have a follow-the-sun support model in Commercial where support personnel from India and elsewhere may have limited access to services to provide 24/7 support for our customers. \n \n \n Keep these principles in mind as we continue to discuss the evolution of our cloud services as it’s the reason we ended up with several different clouds. \n \n A word about Office 365 Multi-Geo \n As Commercial has evolved, we now have regions, or ‘Geos’ in Public MT that offer data residency in multiple geographies, often aligned with countries. Our Office 365 Multi-Geo solution addresses your data residency requirements for workloads including (and limited to) Exchange Online, OneDrive for Business Online, SharePoint Online and Office 365 Groups. We will soon have a multi-geo solution for Teams as well. From a compliance perspective, this translates to having data stored at rest within a specific country or region. \n \n At the time of this writing, we have available Geos in Australia, Brazil, Canada, European Union, France, Germany, India, Japan, South Korea, Norway, South Africa, Switzerland, United Arab Emirates, United Kingdom, and the United States. We are adding new Geo’s frequently. \n \n A Geo in Office 365 is a data enclave for a defined region. Internally, a Geo is a data enclave of Commercial. A data enclave is segregated environment, with servers residing in regional Azure data centers. For example, the US Geo may be selected in Exchange Online for specifically assigned users that require mailboxes at rest within CONUS (Continental United States). Many governments, financial services, healthcare providers, etc. often have requirements for data residency in a specific country. This Multi-Geo solution often meets these compliance requirements in Commercial, especially in conjunction with the alphabet soup of industry standards and government regulations in the US and abroad. \n \n History Sidebar: The often-forgotten true predecessor to Office 365 is the first public multi-tenant Office solution we delivered to Education customers called Live@edu. It began in 2005 and served as something of an early adopter program for Office 365, on-boarding over 50 million faculty, staff, and students to Outlook Live, SkyDrive and other Office solutions. Interestingly, I was the first solution architect for Live@edu starting back in 2007. \n \n Some may dispute that BPOS (Business Productivity Online Suite) is the predecessor to Office 365, but in truth it was a parallel environment built and supported by BPOS engineering. Conversely, Live@edu was built and supported by each respective workload product group (e.g. Exchange), identical to Office 365. Regardless, both Live@edu and BPOS pre-date Office 365. \n \n \n Introducing the US Government Community Cloud. \n \n What’s it called again? Office 365 GCC should not be confused with GCC High. They are two separate clouds. Historically, we often referred to GCC as ‘GCC Moderate’ for its alignment with FedRAMP Moderate. I’ve also heard it called the ‘IL2’ environment, for its alignment with the DoD CC SRG Impact Level 2. But ‘Moderate’ and ‘IL2’ are confusing nicknames, and we try to avoid calling GCC anything other than ‘GCC’. \n \n US Government customers have a variety of accreditations and industry standards for Cloud Solution Providers. Most notably, FedRAMP and NIST come to mind. Certain government entities extend beyond the accreditation with regulations such as CJIS and IRS 1075 that require screened US Persons. As such, it’s not good enough to simply have data residency within CONUS. The cloud service offering must impose restrictions so that only authorized personnel may access customer content. Ultimately, this data enclave for GCC not only ensures data residency and data processing for the primary workloads are in CONUS, it also restricts customer content access to authorized screened US Persons. \n \n For Microsoft to capture the market for US Government entities, GCC is required. We have onboarded thousands of US government agencies and departments, especially in SLG (State & Local Government) and Federal Civilian. There are a few principles for GCC to keep in mind: \n \n \n GCC is a data enclave of Commercial. Shared services, such as outlined in the principles for Commercial apply to GCC as well (e.g. Global Directory, Global Network, Global Support, etc.) \n GCC offers data residency as opposed to data sovereignty. It’s paramount that you understand data residency applies to the GCC covered workloads (e.g. Exchange, OneDrive, etc.). Other workloads may not support data residency. \n US Government accreditation for GCC. The FedRAMP Moderate Agency ATO from the Department of Health and Human Services (DHHS) is specifically for a government tenant provisioned into GCC that resides in the Commercial environment (listed on the FedRAMP marketplace as Office 365 Multi-Tenant & Supporting Services). \n \n \n Keep these GCC principles in mind, along with the Commercial principles. It's the reason many government customers with stricter regulatory requirements (e.g. ITAR, Nuclear, etc.) do not choose GCC. \n \n \n Then along came Microsoft Azure. \n \n Office 365 pre-dates Microsoft Azure. We did have Windows Azure around about the same time as the first release of Office 365, but the Windows variant did not have many of the EM+S, PaaS and SaaS components that are included today. For the purposes of this conversation, we’ll focus on Azure AD and EM+S. Many of the native features evolved out of Office 365 and into Azure. MSO-DS became Azure AD and provides directory services, authentication and authorization beyond Office 365, including Azure Resource Manager and 3 rd -party applications. Azure RMS spun out and is now bundled with Microsoft Information Protection (MIP). And the list goes on. Azure now provides a platform for many workloads, and we’ve continued to build on top of that. For example, Dynamics 365 and Visual Studio Online are now built on top of the Azure platform and integrate into services such as Azure AD in Commercial. \n \n The one key principal of Azure Commercial as it relates to Office 365 is: \n \n \n Office 365 Commercial and Office 365 GCC are both paired with Azure AD in Commercial. Office 365 GCC cannot be paired with Azure AD in Government (more on that to come). \n \n \n To distill this down, compliance for Azure Commercial aligns closely to what is offered for Office 365 Commercial. The same three principles of Office 365 Commercial (Global Directory, Global Network, Global Support Personnel) apply to Azure Commercial. In other words, data residency is available, but data sovereignty is not. \n \n In fact, many of the US SLG and Federal Civilian agencies will not deploy IaaS nor PaaS into Azure Commercial without US Persons support, regardless of the fact that we have a P-ATO for FedRAMP High in Azure Commercial. \n \n \n To capture the market for US Government entities for IaaS and PaaS, Microsoft built Azure Government. \n What’s it called? The initial release of Azure Government for IaaS and PaaS was the introduction of what we call the ‘US Sovereign Cloud’. Azure Government has internal code names including the first architecture called ‘Fairfax’ and the next generation sovereign architecture called ‘Arlington’. We also call it ‘MAG’ for Microsoft Azure Government. Most people just call it ‘Azure Gov’. \n \n Azure Gov is a fully isolated cloud environment, that is both physically and virtually isolated. It's a separated instance of Azure within a compliance boundary dedicated to US government workloads. It's built exclusively for US government entities and their solution providers, to include the Defense Industrial Base (DIB). Azure Gov is designed for highly sensitive data such as Controlled Unclassified Information (CUI) that requires true data sovereignty. This enables Microsoft to contractually meet the compliance accreditation for FedRAMP High and requirements for US Defense regulations including DoD CC SRG IL4/5, DFARS 7012, ITAR and EAR. \n \n For purposes of this discussion, several key principles include: \n \n \n US Sovereign Directory Services. Unlike with Commercial, Azure AD in Azure Gov is not global. No matter where your client connects from, you will always get authentication and authorization rendered from Azure Gov data centers located in CONUS. For example, you will always see a login page with a .US URL (e.g. https://login.microsoftonline.us/...) \n US Sovereign Network. Data Transmission and Data Processing is CONUS only. As opposed to Commercial endpoints that are all *.com, Azure Gov endpoints are all *.us or *.mil. For example, when you sign into Azure Gov from Australia, it will always resolve your client to Azure Gov data centers in the US. There is no probability of you connecting to data centers in Australia. If your internet peering is in the US, you can rest assured that no data transmission will occur OCONUS. Note: You can implement public peering with Microsoft to enter our network in a geographically closer location to take advantage of our global high-speed fiber network backbone to route to the US, but there is no data processing OCONUS. \n Screened US Persons. Support personnel is restricted to screened US Persons. This includes background checks as required by multiple regulations, including checks against export-related lists maintained by the Departments of Commerce, State and Treasury. Coverage is offered on all services in Azure Gov isolated within the compliance boundary where only screened US Persons are permitted. \n Azure Government supports US export-controlled data. True data sovereignty allows Microsoft to contractually commit to export controls, including US Defense regulations for DoD CC SRG IL4/5, DFARS 7012, ITAR and EAR. This includes coverage for Controlled Unclassified Information (CUI) and Covered Defense Information (CDI). \n \n \n Now that we have Azure Government, it gave us a platform to begin deploying additional workloads into the US Sovereign Cloud. \n \n Now introducing Office 365 DoD paired with Azure Government \n \n After achieving a Provisional Authorization (PA) from DISA for DoD Cloud Computing (CC) Security Requirements Guide (SRG) Impact Level 5 (IL5) covering Azure Government, we began the construction of Office 365 for the US Department of Defense (DoD). To deploy Office 365 to the DoD, they required IL5 across the entire platform and services, to include Microsoft Peering with the DoD’s Cloud Access Point (CAP). We have delivered the full suite of services to Office 365 DoD, but we had one catch. Only the DoD and those approved by them (such as service providers or contractors working on behalf of DoD) are allowed into the IL5 environment. It does preclude other entities from being eligible to procure their own tenant of Office 365 in the US Sovereign Cloud. This includes the service providers for the DoD, such as the DIB. It also includes other government entities that require data sovereignty, such as cabinet-level agencies (e.g. DHS, FBI, DOJ, etc.). There was a tremendous demand from these entities as well. \n \n To capture the market for the DIB and cabinet-level agencies, a mirror copy of Office 365 DoD was constructed and branded Office 365 Government (GCC High). \n \n What’s it called? GCC High? Environment and SKU name aligns with High Impact Level. This should NOT be confused with the defense Industry term a ‘high-side environment’ which is a designation for classified information. To be clear, GCC High is not a ‘high-side environment’. GCC High is a ‘low-side environment’ regarding classified information. GCC High has also been called an ‘IL4’ environment, for its alignment with the DoD CC SRG Impact Level 4 controls. We avoid calling GCC High anything other than ‘GCC High’. \n \n If you look for a DoD Provisional Authorization (PA) from DISA for a DoD CC SRG Impact Level 4 environment, you will not find one. That’s because we have equivalent IL5 environments. We have the IL5 PA on the Office 365 DoD environment, where GCC High is a near copy of. We can consider GCC High an IL4 environment for a couple of reasons. First, IL4 controls are derived from IL5 that we are accredited for. We have a consistent control framework and uniform implementations of controls in both environments; thus, we can say GCC High has IL4 ‘equivalency’. Second, no one besides the DoD proper is allowed into IL5. We call it an IL4 equivalent environment where the Defense Industrial Base and Cabinet-level agencies are allowed. \n \n In alignment with the key principles for Azure Gov, several key principles of both the Office 365 DoD and GCC High environments include: \n \n \n US Sovereign Directory Services. Unlike Office 365 GCC that is paired with Azure AD in Commercial, Office 365 DoD and GCC High are paired with Azure AD in Azure Gov. \n US Sovereign Network. Data Transmission and Data Processing is CONUS Only. As opposed to Commercial endpoints that are all *.com, Office 365 DoD and GCC High endpoints are all *.us or *.mil. This is fundamentally important and a major talking point for compliance with export controls. For example, for email to be compliant, you must have all data processing in a US Sovereign solution. Microsoft offers Exchange Online Protection and Office Advanced Threat Protection within the compliance boundary keeping all data processing of email in CONUS. This includes logging and telemetry captured in the process of scanning email. \n Screened US Persons. Support personnel is restricted to screened US Persons. This includes background screening as required by multiple regulations, including checks against export-related lists maintained by the Departments of Commerce, State and Treasury. Coverage is offered on all services (no exclusions) in Office 365 DoD and GCC High isolated within the compliance boundary where only screened US Persons are permitted. \n Office 365 DoD and GCC High supports US export-controlled data. True data sovereignty allows Microsoft to contractually commit to export controls, including US Defense regulations for DoD CC SRG IL4/5, DFARS 7012, ITAR and EAR. This includes coverage for Controlled Unclassified Information (CUI) and Covered Defense Information (CDI). Microsoft will not commit to export controls anywhere else! This is especially true for ITAR. \n \n \n We also have additional services that are branded GCC High. We now have Dynamics 365 GCC High, the Power Suite for GCC High, and many more services to come. \n \n \n Appendix \n \n Please follow me here and on LinkedIn. Here are my additional blog articles: \n \n \n \n Blog Title \n \n Aka Link \n \n New! Microsoft Collaboration Framework \n \n https://aka.ms/ND-ISAC/CollabFramework \n \n New! ND-ISAC MSCloud - Reference Identity Architectures for the US Defense Industrial Base \n \n https://aka.ms/ND-ISAC/IdentityWP \n \n Microsoft CMMC Acceleration Update \n \n https://aka.ms/CMMC/Acceleration \n \n Gold Standard! Understanding Compliance Between Microsoft 365 Commercial, GCC, GCC-High and DoD Offerings \n \n https://aka.ms/MSGovCompliance \n \n The Microsoft 365 Government (GCC High) Conundrum - DIB Data Enclave vs Going All In \n \n https://aka.ms/AA6frar \n \n Microsoft US Sovereign Cloud Myth Busters - A Global Address List (GAL) Can Span Multiple Tenants \n \n https://aka.ms/AA6seih \n \n Microsoft US Sovereign Cloud Myth Busters - A Single Domain Should Not Span Multiple Tenants \n \n https://aka.ms/AA6vf3n \n \n Microsoft US Sovereign Cloud Myth Busters - Active Directory Does Not Require Restructuring \n \n https://aka.ms/AA6xn69 \n \n Microsoft US Sovereign Cloud Myth Busters - CUI Effectively Requires Data Sovereignty \n \n https://aka.ms/CUISovereignty \n \n Microsoft expands qualification of contractors for government cloud offerings \n \n https://aka.ms/GovCloudEligibility \n \n ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"20698","kudosSumWeight":5,"repliesCount":3,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4MGk3NTlDMjVGRjdGRjUxRUQy?revision=15\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4N2kzNDlCQzNDMEIxNzM3MjIy?revision=15\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDM","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4OGk1RkQ2MTRENzg3NUREMDFB?revision=15\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDQ","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg4OWlGMkRCNkYxNzMxN0Q0OEQx?revision=15\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDU","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg5MGlERTBDNjZBNjRGOEE2NDY4?revision=15\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDY","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg5MWkwOTUyODc1N0I2MDExRUJD?revision=15\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDc","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yMTU3ODIxLTI1Njg5MmlFQURCRkEzOUNENTQxRDZE?revision=15\"}"}}],"totalCount":7,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":null,"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"BOTTOM","altText":""}},"Conversation:conversation:4394967":{"__typename":"Conversation","id":"conversation:4394967","topic":{"__typename":"BlogTopicMessage","uid":4394967},"lastPostingActivityTime":"2025-03-20T10:59:15.168-07:00","solved":false},"User:user:505636":{"__typename":"User","uid":505636,"login":"Jesse_Tedoff","registrationData":{"__typename":"RegistrationData","status":null},"deleted":false,"avatar":{"__typename":"UserAvatar","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/dS01MDU2MzYtMjQwNzQzaTU0MTFFNjJFMDM1NTBCODg"},"id":"user:505636"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXJJaVFDRg?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXJJaVFDRg?revision=12","title":"DatacenterForBlog.png","associationType":"COVER","width":1000,"height":562,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXRpV2h2ag?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXRpV2h2ag?revision=12","title":"image.png","associationType":"BODY","width":1070,"height":144,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXhYMWxtNQ?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXhYMWxtNQ?revision=12","title":"image.png","associationType":"BODY","width":1070,"height":144,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LUtWZEFJYw?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LUtWZEFJYw?revision=12","title":"image.png","associationType":"BODY","width":1070,"height":144,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTdJeUd5UQ?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTdJeUd5UQ?revision=12","title":"clipboard_image-1-1742413258597.png","associationType":"BODY","width":750,"height":700,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXgxeDVRdg?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXgxeDVRdg?revision=12","title":"clipboard_image-2-1742413258626.png","associationType":"BODY","width":750,"height":282,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXJuM1BLSA?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXJuM1BLSA?revision=12","title":"image.png","associationType":"BODY","width":1070,"height":144,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWFuMVJSMw?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWFuMVJSMw?revision=12","title":"clipboard_image-1-1742413698530.jpeg","associationType":"BODY","width":772,"height":434,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXB1SXhmMw?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXB1SXhmMw?revision=12","title":"clipboard_image-2-1742413698547.png","associationType":"BODY","width":522,"height":348,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXFqczdCMQ?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXFqczdCMQ?revision=12","title":"clipboard_image-3-1742413698554.jpeg","associationType":"BODY","width":502,"height":351,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWNxNlFubg?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWNxNlFubg?revision=12","title":"clipboard_image-4-1742413698557.png","associationType":"BODY","width":806,"height":238,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVMxSzNuWg?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVMxSzNuWg?revision=12","title":"image.png","associationType":"BODY","width":1070,"height":144,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTBIVXhkbQ?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTBIVXhkbQ?revision=12","title":"clipboard_image-1-1742482802977.png","associationType":"BODY","width":750,"height":123,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LUdEbGp2dA?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LUdEbGp2dA?revision=12","title":"clipboard_image-2-1742482802988.png","associationType":"BODY","width":750,"height":489,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWtpYWF5eg?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWtpYWF5eg?revision=12","title":"clipboard_image-3-1742482802994.png","associationType":"BODY","width":750,"height":494,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVB3N09CVQ?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVB3N09CVQ?revision=12","title":"clipboard_image-4-1742482803001.png","associationType":"BODY","width":750,"height":422,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LUZ4RDhNcw?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LUZ4RDhNcw?revision=12","title":"clipboard_image-5-1742482803004.png","associationType":"BODY","width":750,"height":451,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTdEQnhCZQ?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTdEQnhCZQ?revision=12","title":"clipboard_image-6-1742482803005.png","associationType":"BODY","width":751,"height":219,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTNqcDJkUw?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTNqcDJkUw?revision=12","title":"clipboard_image-7-1742482803008.png","associationType":"BODY","width":751,"height":410,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWNjOGZVdA?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWNjOGZVdA?revision=12","title":"clipboard_image-8-1742482803010.png","associationType":"BODY","width":751,"height":410,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTM3VGdUWQ?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTM3VGdUWQ?revision=12","title":"clipboard_image-9-1742482803022.png","associationType":"BODY","width":750,"height":521,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXdMZG91MQ?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXdMZG91MQ?revision=12","title":"clipboard_image-10-1742482803024.jpeg","associationType":"BODY","width":311,"height":646,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LW12RUV2Rw?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LW12RUV2Rw?revision=12","title":"clipboard_image-11-1742482803026.png","associationType":"BODY","width":750,"height":499,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVpMQlgybA?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVpMQlgybA?revision=12","title":"clipboard_image-12-1742482803040.png","associationType":"BODY","width":750,"height":534,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVhEeVRDeQ?revision=12\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVhEeVRDeQ?revision=12","title":"clipboard_image-13-1742482803057.png","associationType":"BODY","width":750,"height":882,"altText":""},"BlogTopicMessage:message:4394967":{"__typename":"BlogTopicMessage","subject":"March 2025 - Microsoft 365 US Public Sector Roadmap Newsletter","conversation":{"__ref":"Conversation:conversation:4394967"},"id":"message:4394967","revisionNum":12,"uid":4394967,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:505636"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":"","introduction":"Copilot in OneNote, record video clips in Teams channels, Microsoft 365 Public Roadmap site update","metrics":{"__typename":"MessageMetrics","views":972},"postTime":"2025-03-20T10:59:15.168-07:00","lastPublishTime":"2025-03-20T10:59:15.168-07:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" \n Teams \n Third-party chat and meeting keyboard shortcut support \n Open file links preference to extend across M365 apps \n Wired headset support for the Walkie Talkie app \n Microsoft 365 \n Copilot in OneNote - GCC \n \n \n CMMC Final Rule 32 CFR: Key Compliance Updates for DoD Contractors \n With the Cybersecurity Maturity Model Certification (CMMC) program taking effect on December 16, 2024, per the 32 CFR rule, the Defense Industrial Base (DIB) has entered a new phase of cybersecurity compliance. This final rule codifies CMMC as a requirement to ensure contractors have implemented necessary security measures for protecting Federal Contract Information (FCI) and Controlled Unclassified Information (CUI), with most requiring an assessment by an Authorized CMMC Third-Party Assessment Organization (C3PAO). The rule formalizes the CMMC program requirements for defense contractors. \n Unlocking Opportunities for Government Efficiency \n The U.S. Federal Government stands at a critical inflection point, offering an unprecedented opportunity to redefine how it fulfills its vital missions. As leaders seek to reduce costs and enhance efficiency, much of this can be accomplished through thoughtful technology modernization applied to mission delivery. \n Where to Start with Microsoft Teams Apps in Gov Clouds \n 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. \n What’s New in Microsoft Teams | February 2025 \n Copilot in Teams meetings now available for GCC: Copilot helps you run more effective meetings, get up to speed on the conversation, organize key discussion points, and summarize key actions so it’s clear what you need to do next. Users can type any question or use predetermined prompts during or after the meeting, and their interactions with Copilot are only visible to them. This feature is already available in worldwide multitenant and is now available for customers in GCC. \n Microsoft 365 Government Adoption Resources \n Empowering US public sector organizations to transition to Microsoft 365 \n \n \n Microsoft 365 Roadmap This link is filtered to show GCC, GCC High and DOD: \n \n Stay on top of Microsoft 365 changes \n Here are a few ways that you can stay on top of the Office 365 updates in your organization. \n Microsoft Tech Community for Public Sector Your community for discussion surrounding the public sector, local and state governments. \n Microsoft 365 for US Government Service Descriptions \n \n Microsoft 365 Copilot (GCC) \n Microsoft Copilot Studio (GCC) \n Office 365 Platform (GCC, GCCH, DoD) \n Office 365 U.S. Government GCC endpoints \n Office 365 U.S. Government GCC High endpoints \n Office 365 U.S. Government DoD endpoints \n \n \n Microsoft Purview (GCC, GCCH, DoD) \n Enterprise Mobility & Security (GCC, GCCH, DoD) \n Microsoft Defender for Endpoint (GCC, GCCH, DoD) \n Microsoft Defender for Cloud Apps Security (GCC, GCCH, DoD) \n Microsoft Defender for Identity (GCC, GCCH, DoD) \n Azure Information Protection Premium \n \n \n Exchange Online (GCC, GCCH, DoD) \n SharePoint (GCC, GCCH, DoD) \n OneDrive (GCC, GCCH, DoD) \n Teams (GCC, GCCH, DoD) \n \n \n Office 365 Government (GCC, GCCH, DoD) \n Power Apps (GCC, GCCH, DoD) \n Power Automate US Government (GCC, GCCH, DoD) \n Power BI (GCC, GCCH, DoD) \n Planner (GCC, GCCH, DoD) \n Outlook Mobile (GCC, GCCH, DoD) \n Dynamics 365 US Government \n Microsoft Copilot Studio (GCC) \n Windows 365 Government \n \n \n \n \n \n \n Get started with Microsoft 365 Copilot \n \n \n \n Public Sector Center of Expertise \n 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. \n \n \n \n \n \n Microsoft Teams for US Government Adoption Guide \n \n \n \n \n \n \n \n \n \n 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! \n SharePoint Online / OneDrive for Business \n MC1018344 — Microsoft SharePoint: We will retire creating personal pages from SharePoint \"start\" (Preview) \n In MC797119 (Updated) SharePoint Online: A new Start experience (published May 2024, updated June 2024), we announced the new Microsoft SharePoint start (Preview) experience, featuring a user-friendly approach that reduces the effort required for creating sites and pages. We have received feedback regarding concerns about the content policy, specifically in relation to personal pages. Starting mid-March 2025 and ending early April 2025, we will retire the ability for SharePoint users to create personal pages from SharePoint start (Preview). \n The other features in SharePoint start (Preview) will continue to work after we retire the ability to create personal pages from SharePoint start (Preview). \n As an alternative, we recommend that SharePoint users create pages that are connected to sites from SharePoint start (Preview). \n How this will affect your organization: \n When the retirement has been implemented for your tenant, this notification will display at the top of the SharePoint user page: Publish your pages to sites. Creating new personal pages that aren’t connected to sites is no longer supported. \n \n To create a new page from a page template in SharePoint start (Preview) that is connected to a SharePoint site \n \n In SharePoint start(Preview), go to Create a pageand select a page template: \n \n \n \n On the right panel, choose a SharePoint site or enter the name of a SharePoint site to begin creating a new page on that site. \n \n \n FAQs \n Can users still access personal pages they have created before the retirement? \n \n Users can continue their work on these pages. They can be found under My pagesor My pages on this site in SharePoint start (Preview). \n \n Can users move these personal pages to another location? \n \n No, but SharePoint admins can move existing personal pages to other destinations using this PowerShell cmdlet: Copy-SPOPersonalSitePage (Microsoft.Online.SharePoint.PowerShell) \n \n Can users convert a personal page to a page connected to a SharePoint site? \n \n No, there is currently no option for users to convert personal pages to pages connected to SharePoint sites through the user interface. SharePoint admins can move personal pages to SharePoint sites using the PowerShell cmdlet. \n \n What you need to do to prepare: \n 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. \n MC1017119 — Microsoft OneDrive: Protect PDF with Password on OneDrive for web \n Microsoft 365 Roadmap ID 482193 \n Coming soon to Microsoft OneDrive: OneDrive web users can protect their PDF files with User Password and Owner Password. The User Password is required to open and view a PDF file. The Owner Password is used to set operation permissions on a PDF file, such as allow printing, copying, or modifying the content. This enhancement provides an additional layer of security for sensitive documents, ensuring that only authorized individuals can access the content. \n When this will happen: \n Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n \n Before this rollout: Users cannot setup passwords to protect their PDF files. \n After this rollout: Users can set a User Password to protect the PDF from being opened by non-authorized users or set Owner Password to grant certain operations like printing, copying, or modifying the content. \n \n Users will be able to use the password protection function by following these steps in OneDrive for web: \n \n Open the PDF file, click the Set passwordbutton on the upper left toolbar. \n User Password can be set under Security. With this password, the user can open the PDF. \n Owner Password can be set under Protection. By selecting different permission levels, together with the permission password, the user having this password will be able to perform relevant actions such as print, copy, or modify contents. \n \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with any relevant documentation. \n MC1013464 — Microsoft OneDrive: We will remove the EEEU sharing permission from root web and default document library \n EEEU, which stands for Everyone Except External Users, is a permission setting used in Microsoft SharePoint and Microsoft OneDrive to manage access to content. This setting allows all internal users in an organization to access certain content while excluding external users. We discourage use of this setting due to concerns about inadvertent oversharing of user data. \n What is changing: \n Starting April 10, 2025 and ending by September 30, 2025, we will run logic to detect and remove the EEEU permission from the root site of each user’s OneDrive and the default document library in OneDrive. \n How this will affect your organization: \n Before this retirement, apps, processes, or users may be able to discover and access content from OneDrive because of the inadvertent presence of EEEU in the root web and default document library in OneDrive. After the EEEU permission is removed, these apps, processes, and users will lose access to the content from the affected OneDrive accounts. Users, processes, and apps that were granted direct permissions to specific files and folders of a OneDrive account will not be impacted and will continue to retain their access. \n We recommend OneDrive owners and OneDrive admins give explicit permission to individual files and folders in OneDrive to be accessed by one or more users or apps. \n What you need to do to prepare: \n This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change and update relevant documentation. If you have questions or wish to discuss more, please open a support ticket. \n Learn more: The section called Use Microsoft Entra groups and dynamic membership instead of default claims in Grant Everyone claim to external users in Microsoft 365 - Microsoft 365 | Microsoft Learn \n MC1005510 — SharePoint Online: Updates to Microsoft Lists forms \n Microsoft 365 Roadmap ID 124865 \n In Microsoft SharePoint Online, Microsoft Lists forms are being updated to enhance your list data collection and management. These updates include subscribing to notifications, form scheduling, conditional branching, quick form creation, and additional field-type support. \n When this will happen: \n Targeted Release: We began rolling out early January 2025 and expect to complete by mid-February 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n Updates to the Microsoft Lists forms include these key improvements: \n \n New creation experience: Users can now create forms directly from Lists home, SharePoint, and the Lists app in Microsoft Teams. This streamlined process automatically creates the underlying list for responses, saving time and effort. \n \n \n \n Conditional branching: Conditional branching allows you to show or hide questions based on previous answers, ensuring respondents only see relevant questions. You can branch questions to other questions or based on choices in a Choice field. \n \n \n \n Add logo: Enhance your forms with a relevant logo, making them look more professional and reinforcing brand identity. \n \n \n \n Support for Additional Field Types Attachments, Image, Location, Lookup. Please note that for Lookup fields respondents need at least read access to the underlying source list to see and select the options. \n \n \n \n Get notified of new responses and Schedule form Start/End dates: Choose to be notified when someone submits a response to a form you own or have access to. Set specific start and end dates for your forms. \n \n \n For more information, see Microsoft Lists forms: What's New. \n What you need to do to prepare: \n 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. \n MC1004412 — SharePoint Online: Enhancements to the Text web part \n Microsoft 365 Roadmap ID 394278 \n The Text web part in SharePoint Online allows users to add normal text, tables, and paragraphs to a SharePoint site page. It provides various formatting options such as bullets, styles, indentations, links, and highlighting. To use the Text web part, go to edit mode, select the circled plus (+) icon, choose Text from the web part toolbox, and enter your desired text in the Text field. \n In the updated Text web part, similar themed features are grouped together for better customer experience and usability. \n The updated text web part will be available in SharePoint and Viva Amplify. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): This feature update rolled out early February 2025. \n How this will affect your organization: \n Users will see a new UI for the Text web part with existing controls and some new ones. The Text web part will automatically adjust by expanding or compressing based on the section layout used. When compressed, the text options will move into the overflow (...) button. Within this web part, users can make all text customizations that are already available like styles, font size, alignment, list, tables, and many more. This web part will also host any text enhancements that may be added in the future. \n For more information, see Add text, tables, and images to your page with the Text web part. \n What you need to do to prepare: \n 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. \n MC1002417 — Microsoft SharePoint: The \"spaces\" feature will retire \n Due to limited usage and our focus on investing in Microsoft Mesh where immersive 3D content can be created and experienced in a multi-user collaborative experience, we will retire the spaces feature from Microsoft SharePoint Online starting March 10, 2025 and ending August 11, 2025. As another alternative, you may choose to transition some existing content to SharePoint Pages. \n How this will affect your organization: \n Users will no longer be able to view or create SharePoint spaces after this retirement is complete. Retirement timeline details: \n \n Starting March 10, 2025, the spacesfeature be turned off by default. After this date, users can still access the spaces feature on SharePoint sites that have used it previously and users can enable the feature for individual sites on the Site features page. \n Starting May 15, 2025, users will no longer be able to enable the spacesfeature on the Site features page, but SharePoint sites with the feature already enabled will continue to function as normal. \n Starting August 11, 2025, the feature will be fully disabled and users will be unable to view, edit, or create new spaces. \n \n Learn how to identify SharePoint sites with the spaces feature enabled: SharePoint Spaces deprecation - Microsoft Support \n What you need to do to prepare: \n This change will happen automatically by the specified date. No admin action is required; however, existing content will no longer be usable after the feature is retired. Please notify your users about this change, update relevant documentation, and consider Microsoft Mesh for future immersive experiences in Microsoft 365. \n You and your users can identify spaces content in a SharePoint site by going to the Pages library and looking for files where the Content type is Space. \n Learn more: SharePoint Spaces deprecation - Microsoft Support \n MC989979 — (Updated) Microsoft SharePoint: New preview mode for Pages and News posts \n Microsoft 365 Roadmap ID 473452 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft SharePoint: The new Preview mode can be used to understand how Pages and News posts will appear on different device types when viewed by an audience. \n When this will happen: \n Targeted Release: We will begin rolling out early March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 (previously late February) and expect to complete by late April 2025 (previously late March). \n How this will affect your organization: \n After this rollout, a Preview button will display in the command bar while users are editing Pages and News posts in SharePoint. After selecting Preview, users can see what the page will look like in view mode for the audience. When previewing Pages, users can navigate between Desktop and Mobile device types. When previewing News posts, users can also choose to view the email version as Desktop or Mobile device types. \n This change will be available by default. \n What you need to do to prepare: \n You may want to notify users, update your user training, and prepare your help desk. \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. \n Before rollout, we will update this post with revised documentation. \n MC974354 — (Updated) Microsoft SharePoint Online: Re-imagined Hero with the new carousel layout in pages and news \n Microsoft 365 Roadmap ID 395214 \n Updated February 6, 2025: We have updated the content. \n We are introducing a new Carousel layout to make the Hero web part more attractive. This new layout will feature a slideshow and a selection of new styles with imagery, bold text, and a call to action, creating a more engaging page experience. \n When this will happen: \n Targeted Release: We will start rolling out in mid-January 2025 and expect to complete by mid-January 2025 (previously late January). \n General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out mid-January 2025 (previously mid-February) and expect to complete by late January 2025 (previously late-February). \n How this will affect your organization: \n Adding a Hero web part to a page or news post has not changed. This update allows authors to create eye-catching carousel slides in any section type, with up to five slides in Carousel layout, enhancing user engagement and highlighting key content to establish page hierarchy. It offers three new styles and supports Stream videos to make the page more appealing. \n What you need to do to prepare: \n 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. \n Additional resources: Use the Hero web part - Microsoft Support \n MC973514 — (Updated) SharePoint Pages Flexible Sections \n Microsoft 365 Roadmap ID 395213 \n Flexible sections are a new section type that allow authors to build pages without a strict column structure. Web parts can be dynamically resized and moved within flexible sections to create a fully customized section. Flexible sections unlock an endless number of design possibilities for sections. \n With the introduction of flexible sections, we have reimagined section templates that are located in the content pane toolbox. The new section templates will be powered by both flexible and column-based sections with example content. All sample content from these templates is placed onto the canvas when a section template is applied. \n Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. \n The new flexible section type and section templates will be available in SharePoint and Viva Amplify. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 (previously late-January) and expect to complete by late March 2025 (previously mid-March). \n General Availability (Production, GCC, GCC High, DOD): We will begin rolling out late March 2025 (previously mid-March) and expect to complete by late April 2025. \n How this will affect your organization: \n Users will see a new option when adding a section to a page, called “Flexible”. Within a flexible section, users can drag and drop web parts anywhere on the grid. Web parts will snap to the closest grid line when moved. \n Users can also resize web parts. Card-based web parts, such as Quick Links, People, or Hero, only have four different width options (full width, 1/3 canvas width, ½ canvas width, and 2/3 canvas width). These web parts can only be resized to one of the four options. \n Non-card-based web parts, such as Text, Image, and File & Media can be resized to any width. Web parts will snap to the closest gird line when being resized. \n Users can resize flexible sections manually, change the arrangement of overlapping web parts, multi-select web parts, and group web parts. \n Users can select or drag and drop a new section template from the content pane toolbox. After the template is added to the canvas, users can make adjustments to the web parts and section until ready to publish. \n What you need to do to prepare: \n You might want to notify users, update your user training, and prepare your help desk. \n MC973498 — (Updated) Microsoft SharePoint: New \"Editorial card\" web part for Pages and News \n Microsoft 365 Roadmap ID 414524 \n Updated February 6, 2025: We have updated the content. Thank you for your patience. \n Coming soon to Microsoft SharePoint: a new web part for Pages and New posts called the Editorial card. Unlike automated web parts like News and Events, the new Editorial card allows SharePoint designers to manually tailor the content presentation to their needs. \n When this will happen: \n Targeted Release: We will start rolling out late January 2025 and expect to complete by mid-February 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will start rolling out mid-February 2025 and expect to complete by late February 2025. \n How this will affect your organization: \n After this rollout, users can: \n \n Showcase content in an engaging card format with advanced background and content settings \n Configure content to suit varied author needs \n \n This change will be available to users by default. \n The Editorial card in the Web parts section of the Toolbox (right pane): \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with revised documentation. \n Additional resources: Use the Editorial Card web part - Microsoft Support \n MC922630 — (Updated) Microsoft OneDrive: We will remove the \"EnableHoldTheFile\" group policy \n Microsoft 365 Roadmap ID 429875 \n Updated February 28, 2025: Reminder - this rollout is coming up soon. \n We will remove the EnableHoldTheFile group policy for Microsoft OneDrive from the Microsoft 365 admin center. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early April 2025 and expect to complete by late April 2025. \n How this will affect your organization: \n Before this rollout, if a tenant has disabled EnableHoldTheFile and users experience file conflicts, Microsoft OneDrive automatically creates a copy of the file in conflict. When tenants disable EnableHoldTheFile, users may have to manage hundreds of conflicts because OneDrive automatically copies a file instead of allowing users to choose to merge conflicts. \n After this rollout, the EnableHoldTheFile group policy will be removed and the experience associated with the EnableHoldTheFile group 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 either Save a Copy of the file or Discard Changes if the user doesn't care about the changes that were made. \n What you need to do to prepare: \n 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. \n Learn more: IT Admins - Use OneDrive policies to control sync settings - SharePoint in Microsoft 365 | Microsoft Learn (direct link to the section called Allow users to choose how to handle Office file sync conflicts) \n MC921916 — (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed \n Microsoft 365 Roadmap ID 429874 \n Updated February 28, 2025: Reminder - this rollout is coming up soon. \n We're removing the EnableAllOcsiClients OneDrive group policy in the Microsoft 365 admin center. OCSI is the coordination between office and OneDrive for syncing office documents to the cloud. \n How this will affect your organization: \n After this rollout, the EnableAllOcsiClients group 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. \n 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. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will be rolling out in April 2025. \n How this will affect your organization: \n 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. \n What you need to do to prepare: \n 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. \n For more information, see Allow users to choose how to handle Office file sync conflicts. \n MC915485 — (Updated) Microsoft SharePoint: Updates to font management capabilities \n Microsoft 365 Roadmap ID 420933 \n Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. \n We are introducing updates that provide capabilities for managing custom fonts for Microsoft SharePoint and Microsoft Viva Connections. This includes the ability to hide the From Microsoft font packages from Change the look, the ability to apply a font package in your site templates, and updated availability for the From Microsoft font packages. \n When this will happen: \n Targeted Release: We will begin rolling out mid-October 2024 and expect to complete by early November 2024 \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early November 2024 and expect to complete by late February 2025 (previously late January). \n How this will affect your organization: \n This rollout will include new Microsoft PowerShell commands that will allow you to get information about the From Microsoft font packages and the ability to hide these font packages if desired. More details for these commands will be available in our PowerShell 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. \n Sample action details: \n { \n \"verb\": \"applyFontPackage\", \n \"fontPackageTitle\": \"Amasis MT\", \n \"fontPackageId\": \"1e7a7803-045d-44df-9c7a-d2f2f8562e51\", \n \"fontPackageStore\": \"OutOfBox\" \n } \n 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 see Fonts and the From Microsoft font packages in Change the look without any additional actions. \n What you need to do to prepare: \n 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. \n Get started with the SharePoint Online Management Shell | Microsoft Learn (will be updated) \n Microsoft Viva \n MC1020218 — Microsoft Viva Connections: New News feature in Microsoft Teams \n Microsoft 365 Roadmap ID 472018 \n We are evolving the Feed experience in Microsoft Viva Connections for Microsoft Teams. Instead of the Feed, people in your organization will soon see a Microsoft SharePoint News experience in Viva Connections, for a fresh new look that simplifies the user experience. Learn more: \n \n Introducing enterprise news reader in Viva connections | Microsoft Community Hub \n Watch video(14:12 min) \n \n This message applies to Viva Connections in Teams for Windows desktop, Teams for iOS/Android, and Teams for the web, with this exception: This rollout will also include a Microsoft 365 Copilot-powered summary experience initially available only in Teams for Windows desktop. Microsoft 365 Copilot licensed users will have an additional option to generate a Copilot summary of the top 10 (or fewer) items in a user's News feed. A Microsoft 365 Copilot license is required to use this summarization feature in the news feed. \n When this will happen: \n Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. \n Due to the nature of rollout technology across various platforms, some users may see the new experience sooner than others or in one platform first before the others. \n How this will affect your organization: \n Users will see recommended SharePoint News based on the sites they follow, frequently access, posts by people they work with, and other trending sites. As always, users will only see news they have appropriate permissions for, and if a news item is audience-targeted, the News feed will honor that and filter out news items. Boosted news and news from your organization's news sites will always be prioritized at the top of the News feed. \n Users can like news items in their feed and save them for later. They will have an immersive news experience in Viva Connections, without leaving Teams to read new content for individual sites they follow. \n This change will be on by default. \n The new Feed experience in Viva Connections in Teams for desktop and the web: \n \n The new Feed experience in Viva Connections in Teams for iOS/Android: \n \n The Copilot-powered summary experience available only in Teams for Windows desktop for Microsoft 365 Copilot licensed users: \n \n What you need to do to prepare: \n 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. \n MC998508 — (Updated) Microsoft Viva Connections: New user-created cards \n Microsoft 365 Roadmap ID 472021 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Employees will soon be able to create their own link cards that connect to other tools and destinations on the Microsoft Viva Connections dashboard. \n When this will happen: \n Targeted Release: We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 (previously late February) and expect to complete by late April 2025 (previously late March). \n How this will affect your organization: \n After this rollout, employees can create their own cards for the Connections dashboard: \n Step 1: On the Viva Connections dashboard, the user selects Customize: \n \n Step 2: Add a Quick links card: \n \n Step 3: Set up the card to choose a title, image, and appropriate links. Save the dashboard: \n \n This feature will be on by default and accessible to all users in your tenant unless you turn it off. \n What you need to do to prepare: \n If your company is not ready to roll out end user customizations to employees, you can turn it off with the setting in Dashboard details: \n \n 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. \n MC979826 — (Updated) Microsoft Viva Connections: Update to app name \n Updated February 5, 2025: We have updated the rollout timeline below. Thank you for your patience. \n We are renaming the Viva Connections app to Connections. This change is intended to ensure the app name fits better within Microsoft Teams, preventing it from being truncated. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early February 2025 (previously late January) and expect to complete by late February 2025 (previously mid-February). \n How this will affect your organization: \n If you have already customized the Viva Connections app name in the Microsoft Teams app store, your customizations will remain unchanged. \n This update is available by default. \n What you need to do to prepare: \n 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. \n Microsoft Teams \n MC1022540 — We will be retiring few cmdlets and parameters from the Teams PowerShell Module \n There are important changes coming to Teams PowerShell cmdlets. We will be retiring the following cmdlets and parameters from the Teams PowerShell Module starting Second week of April 2025. You should: \n \n \n When this will happen: \n We will gradually roll out this change to during second week of April 2025. \n How this will affect your organization: \n When this change is implemented on second week April 2025, administrators will no longer be able to use the Get-CsHybridTelephoneNumber and Remove-CsHybridTelephoneNumber cmdlets. \n Instead of the above cmdlets, Teams phone administrators will need to use the Teams PowerShell Module cmdlets: Get-CsPhoneNumberAssignment and New-CsOnlineTelephoneNumberReleaseOrder. \n What you need to do to prepare: \n Start using Get-CsPhoneNumberAssignment and New-CsOnlineTelephoneNumberReleaseOrder instead of the deprecated cmdlets. \n Detailed instructions on how to use the new cmdlets are provided in Get-CsPhoneNumberAssignment (Microsoft Teams PowerShell) \n and \n Remove-CsHybridTelephoneNumber (MicrosoftTeamsPowerShell) \n List of cmdlets retired recently or not supported with Teams PowerShell Module at Deprecated cmdlets \n MC1022539 — We are making changes to the Resource Account license requirement \n We are making improvements to how telephone numbers are managed for Resource Accounts and User Accounts in Microsoft Teams. These updates require us to streamline the license requirement and enforcement. Starting the second week of April 2025, we will require appropriate “Microsoft Teams Phone Resource Account license” to be assigned to all Resource accounts. Any existing resource accounts without appropriate “Microsoft Teams Phone Resource Account license” may be converted to User accounts. Similarly, any User Account with “Microsoft Teams Phone Resource Account license” may be converted to Resource Account. \n When this will happen: \n The update is planned to happen during the second week of April 2025. \n How this will affect your organization: \n If your organization has Resource Accounts without proper “Microsoft Teams Phone Resource Account license”, those accounts may be converted to User Accounts. Similarly, any User Account with “Microsoft Teams Phone Resource Account license” may be converted to Resource Account. \n Starting second week of April 2025, any new phone number assignments to Resource Account will require an appropriate “Microsoft Teams Phone Resource Account license”. \n More information on resource account licenses can be found at: Microsoft Teams Phone Resource Account licenses \n What you need to do to prepare: \n Please assign an appropriate “Microsoft Teams Phone Resource Account license” to all the Resource Accounts. If a User Account is desired, please remove any existing “Microsoft Teams Phone Resource Account license”. \n MC1020213 — Microsoft Teams Rooms: New Facilitator agent takes notes in ad-hoc and scheduled meetings (Public Preview) \n Coming soon to Microsoft Teams Rooms: Facilitator is a collaborative communication agent available to your users in Teams Rooms meetings. It combines the power of large language models (LLMs) and Teams data to record notes and help users be productive during meetings. Facilitator is not on by default. As an admin, you can use these instructions to control whether Facilitator is available to your entire organization or to a certain group of users. \n A Teams Rooms Pro license is required to use this feature. \n This message is related to MC1017117 Microsoft Teams: New Facilitator agent takes notes in meetings and chats (February 2025), which applies to other Teams platforms. \n When this will happen: \n Public Preview (Teams Rooms for Windows desktop): We will begin rolling out late March 2025 and expect to complete by late April 2025. \n Public Preview (Teams Rooms for Android): We will begin rolling out late April 2025 and expect to complete by late May 2025. \n We will communicate the plan for General Availability in a future post. \n How this will affect your organization: \n After this rollout, and after you use these instructions to enable Facilitator for your organization, users can scan the QR code on the first Teams Room screen to invite Facilitator from their phones to ad hoc and in-person discussions in Teams Rooms. Facilitator will create rich AI notes with a summary, action items, and speaker attribution. Teams Rooms will also create AI notes for scheduled meetings when the Facilitator agent is invited to a meeting by a remote attendee. \n Facilitator and Microsoft 365 are built on Microsoft's comprehensive approach to security, compliance, and privacy. As a part of the security promise, you can discover, protect, and govern AI interactions with Facilitator through Microsoft Purview. Microsoft Purview Data Security Posture Management (DSPM) for AI helps IT and security teams proactively discover and manage data risks. Use DSPM for AI in conjunction with other Microsoft Purview capabilities such as Audit, eDiscovery, and Data Lifecycle Management to ensure data security and compliance for your organization. Learn more about Microsoft Purview: Microsoft Purview data security and compliance protections for Microsoft 365 Copilot and other generative AI apps | Microsoft Learn. \n In Teams Rooms meetings, users can scan the QR code to invite Facilitator to the meeting: \n \n An example of Facilitator's Meeting notes in Teams Rooms meetings: \n \n What you need to do to prepare: \n \n To enable Facilitator in your environment, please follow these instructions. \n To enable the Public Preview of Microsoft Teams Rooms in your environment, use the Teams Rooms Pro Management portal > Rooms > Settings > Account > Enable Public preview \n To enable the Facilitator agent QR code in Teams Rooms, use the Teams Rooms Pro Management portal > Rooms > Settings > Meetings > Show Room facilitator QR code \n \n This rollout will happen automatically by the specified date with no admin action required before the rollout. To test the feature, please follow the steps above to prepare your environment. 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. \n Before rollout, we will update this post with new documentation. \n MC1020203 — Microsoft Teams: Record video clips in channels \n Coming soon: Users will be able to record video clips in Microsoft Teams channels, just like users can in Teams chat. \n Users can record themselves, their screen, or audio-only clips and send them in a channel as a new post or a reply. Recording in channels respects the same Video messages policy as recording in chat. As an admin, if you have already enabled or disabled this policy for recording in chat, we will respect it for recording in channels too. \n When this will happen: \n General Availability (Worldwide, GCC): Available now, since early 2025. \n General Availability (GCC High, DoD): We will begin rolling out early March 2025 and expect to complete by mid-March 2025. \n How this will affect your organization: \n After this rollout, a new Record video clip option will appear in the compose box under the Actions and apps button for channel posts or channel replies. A similar button already exists in the chat experience. \n \n What you need to do to prepare: \n 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. \n Learn more: Record a video or audio clip in Microsoft Teams - Microsoft Support \n MC1019315 — [Reminder] Classic Microsoft Teams on Windows: End of availability for older operating systems - DOD \n This message applies to tenants with users: \n \n On Windows Server 2012/2012 R2, which is based on Windows 8.1/8 \n Using Compatibility mode with older Windows versions \n \n Because classic Microsoft Teams is unavailable on Windows 8.1 and below (MC903304), users will see a non-dismissible blocking message in classic Teams when they try to access Windows desktop version of the classic Teams app. \n The blocking message will also appear to users on Compatibility mode with older Windows versions. \n VDI users can continue using Teams on the web in an unsupported manner through their preferred browser, but any multimedia workload will not be optimized (for example, server-side rendering will be used, incurring in high CPU/RAM and network usage). \n What you need to do to prepare: \n \n Please upgrade your Windows Server operating system and move your users to the new Teams app. Microsoft recommends Windows Server 2022 and Windows Server 2025, or Windows 11 24H2 for multiuser environments. \n Use the Pre-installation script for new Teams client - Microsoft Teams | Microsoft Learnto find devices that need to be upgraded to use new Teams. While the main purpose of the script is to find issues before installation of new Teams, it can be used to detect devices running unsupported OS. \n Requirements for the new Teams app on VDI: New Teams VDI Requirements \n Regardless of operating systems, all users on classic Teams will be blocked on July 1, 2025. \n \n This message refers to MC903304 Reminder: Classic Teams End of Availability - Win (7, 8, 8.1) & (MacOS 10.14 and earlier) - Action Needed (published October 2024) \n MC1019312 — Microsoft Teams: Meeting participants can request collaborative annotation sessions \n Microsoft 365 Roadmap ID 89975 \n Coming soon for Microsoft Teams: Meeting participants will be able to request an annotation session while someone else is sharing their screen. \n This message applies to Teams for Windows desktop and Teams for Mac desktop. (Users can view and annotate in Teams on the web but cannot initiate annotations.) \n When this will happen: \n Targeted Release: We will begin rolling out early April 2025 and expect to complete by mid-April 2025. \n General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-April 2025 and expect to complete by early May 2025. \n How this will affect your organization: \n After the rollout, meeting participants who are not sharing their screens will have the ability to request an annotation session. This request will be sent to the presenter sharing their screen who can choose to accept or deny it: \n \n If the request is accepted, the annotation session will start for everyone in the meeting: \n \n Anonymous users in the meeting will not be able to send a request. \n This change will be available by default. \n What you need to do to prepare: \n 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. \n Learn more: Use annotation while sharing your screen in Microsoft Teams - Microsoft Support (we will update this before rollout) \n Watch: How to use Collaborative Annotations in a Microsoft Teams meeting (2022) \n MC1015900 — Microsoft Teams: Client health dashboards in Teams admin center \n Microsoft 365 Roadmap ID 478610 \n IT Administrators can now monitor the health of Microsoft Teams desktop clients for Windows and Mac through the new ‘Teams client health’ page in the Teams admin center. \n \n This page provides actionable insights into client health metrics, such as crashes, launch failures, and update failures. It also enables better monitoring of Teams client version adoption and updates. \n Administrators have detailed data on top issues, insights, and tools to quickly address client health problems. \n Administrators can monitor version adoption, version health, and get granular details about devices and users with the latest client versions. \n Administrators can see the recency of client versions and proactively address issues that prevent automatic updates to the most secure Teams client version. \n \n When this will happen: \n General Availability (Worldwide): We will begin rolling out late March 2025 and expect to complete by late April 2025. \n General Availability (GCC, GCC High, DoD): We will begin rolling out late April 2025 and expect to complete by late May 2025. \n How this will affect your organization: \n When these capabilities and tools are released in Teams admin center, administrators will be able to access the ‘Teams client health’ page via the left navigation and be able to proactively monitor Teams client health and Issues impacting end users in their tenant as well as find actionable guidance on how to troubleshoot and resolve these user-impacting issues. \n Administrators will also be able to proactively monitor which devices and users might be using outdated versions of the Teams client to be able to move them to the latest and most secure version \n Additionally, this information can also be sorted, filtered, and exported to a .csv for further analysis and troubleshooting. \n This will be only accessible to limited admin roles: Teams Administrator, Teams Communication Administrator, and Teams Communications Support Engineer. \n What you need to do to prepare: \n This rollout will happen automatically with no admin action required. \n Ensure you and the required users have access to the above-mentioned roles or request to enable this new feature for more roles. \n For more information, refer to our documentation: \n \n The Teams client health dashboard in the Teams admin center. \n Update monitoring in the Teams admin center. \n \n MC1013461 — Microsoft Teams: Customize the location of notifications in Teams for the web \n Microsoft 365 Roadmap ID 480720 \n Microsoft Teams will soon allow users to personalize the placement of notifications on their screens. Users will be able to choose from four options (bottom right, top right, bottom left, or top left) to make notifications more convenient and less disruptive, enhancing both focus and productivity. This message applies to Teams for the web. \n When this will happen: \n Targeted Release: We will begin rolling out early April 2025 and expect to complete by mid-April 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-April 2025 and expect to complete by late April 2025. \n How this will affect your organization: \n Before this rollout, Teams notifications were limited to the bottom right corner. \n After this rollout, users can customize notification placement in Teams settings in Settings > Notifications and activity > Display. Select the option for notification location that best suits your needs and preferences: Bottom right, Top right, Bottom left, or Top left: \n \n This feature will be available by default for users to configure. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. \n Learn more: Customize the location of notifications in Teams (the location of the notifications will be the same as explained in this blog for Teams for Windows desktop) \n MC1013454 — Microsoft Teams: Enable transcription policy by default for Teams Meetings \n Microsoft 365 Roadmap ID 468282 \n Coming soon for Microsoft Teams: We are updating our default policy settings for transcription for new tenants. Before this rollout, the setting was off by default. After this rollout, the setting will be on by default. This change applies to new global policies created for new tenants. Existing policies in the Teams admin center will not be changed; however, tenants who have not customized any part of their meeting policies for Teams meetings will be impacted. \n \n Tenants without customized policies: The new default settings will apply, and these tenants will be impacted by this change. \n Tenants with customized policies: Policies for user-level assignments or group-level assignments will remain unchanged and unaffected. \n \n This change is designed to streamline the adoption of transcription and enhance the use of all AI features. This change will align transcription with the default policy for recording, which is also enabled by default in Teams admin center. This message applies to Teams for Windows desktop and Teams for Mac desktop. \n When this will happen: \n General Availability (GCC, GCC High and DoD): We will begin rolling out late February 2025 and expect to complete by early March 2025. \n How this will affect your organization: \n After this rollout, transcription services will be more accessible to users, allowing them to turn on and use transcription as needed during meetings. Transcription will not be automatically activated for every meeting. \n For new tenants, transcription will be enabled by default when admins set up their global policies. New tenants will automatically have the transcription policy turned on when they start. Existing tenants without a global policy will also have the policy turned on by default. \n Transcription policy on by default in Teams admin center. Admins can turn off the policy if needed: \n \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with revised documentation. \n MC1011152 — Microsoft Teams: Updates to the Teams system tray icon and menu \n We are improving the Microsoft Teams app icon and menu in the Microsoft Windows system tray (taskbar notification area) for ease of use and to reduce the number of steps to perform routine tasks. \n This message applies to Teams for Windows desktop. \n When this will happen: \n Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n How this will affect your organization \n After this rollout, these changes will affect all users: \n \n Updates to how your account presence is displayed. Instead of seeing My status in the system tray menu, users will now see their current presence status and can quickly change their status. \n We removed the Openoption from the system tray menu. Users can launch the Teams app by selecting their account name in the system tray: \n \n \n Changes that will impact users who are signed into both personal and work accounts: \n Before this rollout, if a user is signed into both personal and work Teams accounts, the system tray will display two Teams icons and corresponding menus. After this rollout, users will have one Teams icon in the system tray for personal and work accounts: \n \n What you need to do to prepare \n No action is required, as users will automatically receive these changes by default. \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. \n MC1009932 — (Updated) Microsoft Teams: Add CVI (Cloud Video Interop) coordinates to town hall and webinar invitations \n Microsoft 365 Roadmap ID 476487 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams: Meeting organizers and schedulers will be able to add CVI (Cloud Video Interop) coordinates to Teams town hall and webinar meeting invitations. With CVI coordinates in invitations, non-Teams users—such as external customers or partners—can easily join town hall and webinar meetings using a third-party teleconferencing device. This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams on the web. \n CVI is a Microsoft Qualified third-party solution that enables third-party SIP and H.323 video room devices (VTCs) to join Microsoft Teams meetings. As an admin, you can set CVI for your org. Learn more: Manage and set up Cloud Video Interop for Microsoft Teams - Microsoft Teams | Microsoft Learn \n When this will happen: \n Targeted Release: We will begin rolling out early April 2025 (previously March) and expect to complete by mid-April 2025 (previously late March). \n General Availability (Worldwide): We will begin rolling out mid-April 2025 (previously early March) and expect to complete by late April 2025 (previously late March). \n General Availability (GCC): We will begin rolling out early May 2025 (previously early April) and expect to complete by late May 2025 (previously late April). \n General Availability (GCC High): We will begin rolling out early May 2025 (previously early April) and expect to complete by late May 2025 (previously late April). \n How this will affect your organization: \n This change will be available by default. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or after 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. \n Learn more: Plan for Teams town halls - Microsoft Teams | Microsoft Learn (will be updated before rollout) \n MC1009930 — Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails \n Microsoft 365 Roadmap ID 476488 \n Microsoft Teams Events invite emails will be separated based on the role of the participant. Event organizers will get an email explaining the specific roles of participants in the event. Similarly, each presenter will get a separate calendar invite, allowing the organizers of town halls to maintain separate invites for attendees. \n When this will happen: \n Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. \n General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n General Availability (GCC, GCC High): We will begin rolling out early April 2025 and expect to complete by mid-April 2025. \n How this will affect your organization: \n This feature update allows the organizers of town halls to maintain separate invites for attendees. \n What you need to do to prepare: \n 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. \n MC1009929 — Microsoft Teams: Join town halls using dial-in options and join codes available in email invites \n Microsoft 365 Roadmap ID 476489 \n Presenters and attendees can now join Microsoft Teams town halls using dial-in options and join codes that are available in email invites. \n When this will happen: \n Targeted Release: We will begin rolling out early March 2025 and expect to complete by mid-March 2025. \n General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n General Availability (GCC, GCC High): We will begin rolling out early April 2025 and expect to complete by mid-April 2025. \n How this will affect your organization: \n With the release of this feature, Teams town hall attendee and presenter email invites will include dial-in details and join codes. \n This update is available by default. \n What you need to do to prepare: \n 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. \n MC1006624 — (Updated) Microsoft Teams: Access chats while sharing a screen \n Microsoft 365 Roadmap ID 467445 \n Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams: We will add a control to the meeting presenter toolbar so presenters can more easily access the meeting chat while sharing a window or a screen. \n This message applies to Teams for Windows desktop and Teams for Mac desktop. \n When this will happen: \n Targeted Release: We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-May 2025 (previously mid-April) and expect to complete by early June 2025 (previously late May). \n How this will affect your organization: \n After this rollout, a compact view of the meeting chat (visible to presenter only) will open when the presenter selects the Chat icon on the presenter toolbar: \n \n Closeup view of the chat icon: \n \n This feature will be available by default. \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with new documentation. \n MC1005517 — Microsoft Teams: Custom meeting branding - support multiple meeting themes per customization policy \n Microsoft 365 Roadmap ID 468868 \n Support for multiple brand themes (an extension to Microsoft Teams Premium branding capability) provides organizations greater flexibility to express their unique visual brand identity across different types of meetings while maintaining consistency with branding standards. \n Admins can now create and assign multiple brands to a customization policy in the Teams admin center. This will allow meeting organizers who are assigned a customization policy to select from different meeting brand options when scheduling their meeting. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by mid-April 2025. \n How this will affect your organization: \n This feature allows organizers to tailor brand themes to suit the occasion, whether it's a formal external meeting, a more casual internal team session, or a meeting with seasonal or holiday-specific branding. For example, they can choose a festive theme for a holiday campaign or a professional theme for client-facing discussions, ensuring the right visual brand identity for every event. \n With this capability, meeting organizers can create a more personalized experience for attendees while aligning with the organization's brand guidelines. \n This update is available by default. \n What you need to do to prepare: \n 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. \n MC1005513 — (Updated) Microsoft Teams: Direct routing call troubleshooting with the new \"SIP call flow\" diagram tool \n Microsoft 365 Roadmap ID 479413 \n Updated February 19, 2025: We have updated the content. Thank you for your patience. \n We are launching the SIP call flow diagram tool in the Microsoft Teams admin center to enable admins to troubleshoot their Direct Routing calls in a self-serve way. \n This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. \n SIP refers to session initiation protocol. \n When this will happen: \n General Availability (Worldwide): We will begin rolling out early March 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n This feature will be available in the Teams admin center on the Usage reports page. The feature will also enable admins to view the SIP requests, responses, and associated SDP (Session Description Protocol) data between Microsoft Teams proxy and the SBC (session border controller) through which the call was routed. This data will be available for all calls made more than 30 minutes and less than 30 days ago. In order to access the SIP call flow diagram, admins will need to: \n \n Sign in to the Teams admin center. \n In the left menu, go to Analytics & reportsand select Usage reports. \n Create and run a new PSTN and SMS (preview) usagereport. (PSTN refers to public switched telephone network and SMS refers to short message service.) \n After the report is generated, to the Direct Routingtab and select the call you want to analyze. \n Select the SIP call flow button in the report to view the detailed diagram. \n \n Watch a short video on using the SIP call flow diagram (00:19 min) \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with new documentation. \n MC1002405 — Microsoft Teams: New Search feature in channel posts \n Coming soon for Microsoft Teams: A new experience to search within Channel Posts. This message applies to Teams for Windows desktop, Mac desktop, and web. \n When this will happen: \n Targeted Release: We will begin rolling out mid-February 2025 and expect to complete by late February 2025. \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out early March 2025 and expect to complete by mid-March 2025. \n General Availability (DoD): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n Key enhancements include: \n \n The new in-post Search experience will now be available in the right handrail, making it possible to see your post and your new search results in one single view. The initiation can be done using the keyboard shortcut Ctrl+F(win) or Cmd +F (Mac) \n \n \n \n In-post search experiences will have enhanced captioning and keyword highlighting to aid the discernment of results: \n \n \n \n In-post search will now also be available in pop-out window: \n \n \n What you need to do to prepare: \n The new search feature will be available by default. \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. \n MC1000272 — Microsoft Teams: Post and reply as \"Organizer\" in Q&A \n Microsoft 365 Roadmap ID 475856 \n Coming soon for Microsoft Teams: Organizers for town halls, webinars, and meetings will be able to post and reply to questions using the title “Organizer” in the Q&A experience, instead of their names. This feature allows organizers to present a unified and official voice when responding to attendee questions. \n This message applies to Teams on Windows desktop and Teams on Mac desktop. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n After this rollout, organizers and co-organizers can choose Organizer or their own name when posting each new question or discussion or when replying to a question in Q&A. \n Attendees will not see such an option. \n What you need to do to prepare: \n This change will be available by default. \n 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. \n Learn more: Q&A in Microsoft Teams meetings - Microsoft Support (will be updated before rollout) \n MC1000269 — Microsoft Teams: New keyboard shortcut for adding emojis \n Microsoft 365 Roadmap ID 369345 \n Coming soon: We are excited to announce a new feature in Microsoft Teams that allows users to insert emojis in the compose box by typing a word surrounded by colons. For example, :smile: will turn into the smiling face emoji. Users can soon add any emoji, including custom ones, for faster and easier personal expression. \n This feature applies to Teams for Windows desktop and Windows for Mac desktop. \n When this will happen: \n Targeted Release: We will begin rolling out early April 2025 and expect to complete by mid-April 2025. \n General Availability (Worldwide): We will begin rolling out mid-April 2025 and expect to complete by late April 2025. \n General Availability (GCC): We will begin rolling out early May 2025 and expect to complete by mid-May 2025. \n General Availability (GCC High): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. \n General Availability (DoD): We will begin rolling out early June 2025 and expect to complete by mid-June 2025. \n General Availability (Gallatin): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. \n General Availability (USSec, USNat): We will begin rolling out early July 2025 and expect to complete by mid-July 2025. \n How this will affect your organization: \n This feature will be available by default. \n Watch the video: Use colons to insert emojis (0:04 minutes) \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. \n Learn more: Send an emoji, GIF, or sticker in Microsoft Teams - Microsoft Support (will be updated before rollout) \n MC999443 — (Updated) Microsoft Teams: Queues app to add Monitor, Whisper, Barge, and Takeover \n Microsoft 365 Roadmap ID 473884 \n Updated February 14, 2025: We have updated the rollout timeline below. Thank you for your patience. \n For Microsoft Teams, in the Queues app, authorized users will be able to enter into a monitoring session for private coaching. They can listen to customer calls, whisper to the agents for private messages, and barge into or takeover the call. \n When this will happen: \n Targeted Release: We will begin rolling out early April 2025 (previously mid-March) for and expect to complete by mid-April 2025 (previously early April). \n General Availability (Worldwide, GCC): We will begin rolling out late April 2025 and expect to complete by early May 2025. \n How this will affect your organization: \n In the Teams Queues app, authorized users will now have access to selected capabilities for private coaching. \n \n Monitor \n Whisper \n Barge \n Takeover \n \n What you need to do to prepare: \n 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. \n MC997581 — Windows 10 End of Support for Microsoft Teams Rooms on Windows \n Support ends soon for Window 10 on October 14, 2025, and devices will no longer receive security and feature updates. Upgrade your Teams Rooms on Windows devices now to Windows 11 for a smooth transition and get the latest productivity, security, and management features. \n When this will happen: \n October 14, 2025 \n How this affects your organization: \n Until October 14, 2025, Teams Rooms and Teams Rooms Pro Management software will continue to support and test on Windows 11 and Windows 10 version 22H2. After the Windows 10 end of support date, Teams Rooms and Teams Rooms Pro Management will no longer update, support, or test apps on Windows 10. \n What you can do to prepare: \n Please utilize the Windows 11 readiness checker and Teams Rooms Pro Management portal Room Inventory export to identify devices that will need action. OS version 10.0.19045 or below devices will need to be upgraded. \n Most Teams Rooms devices running Windows 10 can be upgraded to Windows 11. There are some devices from makers such as Lenovo, HP, Yealink, and Crestron that are not able to be upgraded due to the processor used. Please contact your device manufacturer for specific models impacted. \n Find additional details on the Teams Rooms app OS support at Teams Rooms app and Windows versioning support - Microsoft Teams | Microsoft Learn. Please see the Microsoft product lifecycle notices for Windows 10 Enterprise and Windows10 IoT Enterprise. \n MC996588 — (Updated) Microsoft Teams: Adding and editing external contacts on Teams phone devices \n Microsoft 365 Roadmap ID 476485 \n Updated February 5, 2025: We have updated the rollout timeline below. Thank you for your patience. \n A new feature allows users to add and edit external contacts using the lightweight People app on Microsoft Teams phone devices. With this capability, you will be able to manage and interact with contacts outside of your organization on Teams phone devices. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early April 2025 (previously mid-March) and expect to complete by mid-April 2025 (previously late March). \n General Availability (GCC High): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. \n General Availability (DoD): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. \n How this will affect your organization: \n Users will now be able to add and edit external contacts from Teams phone devices. \n To add an external contact: \n \n Click Create new contact from the People app. \n Add in the details of the external contact, and then click Save. \n \n What you need to do to prepare: \n Please ensure that your Teams phone devices are updated with the latest People app to get access to this new feature. This feature will only be available with the latest application update. \n MC994287 — (Updated) Microsoft Teams: Webinars will be generally available (DoD) \n Microsoft 365 Roadmap ID 475279 \n Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Webinars in Microsoft Teams will soon be generally available. After this rollout, users will be able to schedule webinars with internal audiences and use capabilities such as creating an event page, sending attendee registration automated emails, and more. \n This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams for the web. Teams for iOS/Android users can attend webinars but not schedule them. \n When this will happen: \n General Availability (DoD): We will begin rolling out mid-April 2025 (previously late March) and expect to complete by late April 2025 (previously mid-April). \n How this will affect your organization: \n This change will be available by default. \n What you need to do to prepare: \n 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. \n User documentation: Get started with Microsoft Teams webinars - Microsoft Support \n MC993226 — (Updated) Microsoft Teams: New location sharing settings for emergency calls and other features \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Microsoft Teams will soon have a new location sharing setting that will allow users to grant location access to specific features. This change will affect emergency dynamic policy and the network bandwidth policy. \n This message applies to Teams for Windows desktop (version 24H2 or greater) and Teams for Mac desktop. VDI clients will not be supported at this time. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 and expect to complete by mid-February 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March (previously late February) and expect to complete by early April 2025 (previously early March). \n How this will affect your organization: \n Before this rollout: Location access was governed exclusively at the operating system level. With this update, location consent will also be required from users at the individual application level. As a result, users gain more granular control over which specific application features can access their location. \n After this rollout, Teams users can grant location access to certain Teams features. The setting for IT insights for admins feature are in Teams Settings > Privacy > Location. The setting for the Emergency calls feature is in the user's device's location settings. The user can find a link to their device's location settings in Teams Settings > Privacy > Location: \n If a user consented to location access before the rollout, the user will be prompted to confirm their selection in this new popup that will display after the next Teams version update. If a user has not previously consented, they will not see the popup and can adjust their preferences in Settings. \n What you need to do to prepare: \n NOTE: After this rollout, dynamic emergency calling may not work as intended unless users allow location detection at the operating system level and app level. This dynamic emergency calling issue includes scenarios where admins have configured a network site for their users (location must be enabled by the user). To ensure emergency calls are properly routed to the nearest public safety answering point (PSAP), please advise your users to accept the new location requests from Teams. This also applies to users who may have consented to location access before the rollout. \n You can communicate this requirement by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that end users have location turned on is crucial for proper functioning of emergency calls and their safety. Learn more about sending a custom message: Manage emergency calling policies in Microsoft Teams - Microsoft Teams | Microsoft Learn \n To continue managing video and media settings with the network roaming policy, users must enable Insights for IT admins in Teams Settings > Privacy > Location > Insights for IT admins. \n Learn more about the changes to location services and privacy policies \n \n Windows location service and privacy - Microsoft Support \n Enable location sharing - Microsoft Support(will be updated before rollout) \n \n 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. Please notify your users and admins about this change and update any relevant documentation. \n MC989974 — (Updated) Microsoft Teams: New microphone volume indicator for users \n Microsoft 365 Roadmap ID 468274 \n Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for Microsoft Teams: A new Mic volume indicator on the user bar in Teams meetings. This feature will provide users with real-time visual feedback on their audio levels in the meeting, eliminating the need to ask, “Can you hear me?” This feature is designed to minimize interruptions as well as enhance user confidence and meeting effectiveness. \n This feature applies to Teams on Windows desktop and Mac desktop. \n When this will happen: \n Targeted Release: We will begin rolling out in early April 2025 (previously March) and expect to complete by mid-April 2025 (previously March). \n General Availability (Worldwide, GCC): We will begin rolling out in mid-April 2025 (previously late March) and expect to complete by late April 2025. \n General Availability (GCC High): We will begin rolling out in late April 2025 (previously mid-May) and expect to complete by early May 2025 (previously mid-June). \n General Availability (DoD): We will begin rolling out in early May 2025 (previously late June) and expect to complete by mid-May (previously early August). \n How this will affect your organization: \n This feature will be available to users by default and has no admin policy. \n Users can select the Mic icon and review the Microphone section of the menu to find out more about their audio levels in the meeting: \n What you need to do to prepare: \n 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. \n Learn more: Muting and unmuting your mic in Microsoft Teams - Microsoft Support \n MC986517 — (Updated) Upcoming Update: Introducing eCDN Feature in Teams Premium for GCC-High \n Updated February 19, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Your GCC-High Teams premium subscription is being updated with a new service plan: Microsoft eCDN which enables efficient and secure content delivery within your organization, ensuring smooth streaming of Townhall content while reducing network congestion. \n When this will happen: \n General Availability (GCC High): We will begin rolling out early March 2025 (previously early February) and expect to complete by mid-March 2025 (previously mid-February). \n How this affects your organization: \n Once we begin rolling out the new service plan (early February), the eCDN feature will be included as a service plan under the Teams Premium subscription. This is to enhance the content delivery capabilities of your Townhall feature. For more details about Microsoft eCDN review Microsoft eCDN Documentation. \n The rollout plan outlining the availability of the eCDN feature will be communicated via the Message Center and the roadmap. \n What you need to do to prepare: \n There is no action required. Information about managing eCDN (disable/enable) can be found here. \n MC985484 — Microsoft Teams: Additional work information in people search results \n Updated February 12, 2025: We have updated the content. Thank you for your patience. \n Multi-tenant organization (MTO) users will be able to see additional work information in people search results. With this feature, MTO users will be able to see the company name and department name of a user in people search results, helping users to make sure they are communicating with the right people. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously early February) and expect to complete by late March 2025 (previously late February). \n How this will affect your organization: \n Tenant admins who have MTO enabled will be able to toggle this feature on and off in the Teams admin center. \n Toggle behavior: \n \n This toggle will be off by default. \n Turning on the toggle will enable the ability to see company name and department name in results. \n Turning off the toggle will disable the ability to see company name and department name in results. \n \n Instructions to toggle: \n \n Navigate to the Teams admin center (TAC). \n Navigate to the Teams Client Config page. \n Using the Enable Extended Work Info in People Search toggle: \n \n \n Switch the toggle to on to enable the ability to see company name and department name in results. \n \n \n Switch the toggle to off to disable the ability to see company name and department name in results. \n \n For more information, see Set up a multitenant org in Microsoft 365. \n What you need to do to prepare: \n Tenant admins will need to complete cross-tenant synchronization and sync the company name field in order to take advantage of this feature. \n For more information, see Synchronize users in multitenant organizations in Microsoft 365. \n MC978932 — (Updated) Large Events: End Session for Attendees and Return Presenters to Green Room \n Microsoft 365 Roadmap ID 470432 \n Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Organizers and presenters can now end the session with this new \"End Event\" button for town halls, webinars, and structured meetings. After selecting this button, attendees will see a message on stage stating that the session has concluded, and presenters will return to the Green Room. \n When this will happen: \n Targeted Release: We will begin rolling out mid-February 2025 (previously early February) and expect to complete by mid-February 2025. \n General Availability (Worldwide): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. \n General Availability (GCC): We will begin rolling out late February 2025 and expect to complete by early March 2025. \n General Availability (GCC High and DoD): We will begin rolling out late March 2025 and expect to complete by early April 2025. \n How this will affect your organization: \n When users join a town hall, webinar, or structured meeting with Green Room turned ON, they will now see the \"End event\" or \"End meeting\" button: \n What you need to do to prepare: \n This feature change will be available once it is fully released in your tenant. \n MC975304 — (Updated) Microsoft Teams: The Approvals app is generally available (DoD) \n Microsoft 365 Roadmap ID 473448 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n The Approvals app in Microsoft Teams is a way to streamline requests and processes with a team or partners. Users will be able to create new approvals, view pending approvals, and see previous ones in one place. \n Users with an F3 license or above can take advantage of the Approvals app in Teams: \n \n Office 365 Government G1 \n Office 365 Government G3 \n Office 365 Government G5 \n Office 365 Government F3 \n \n If you do not have users that meet the licensing requirement, you may safely ignore this message. \n This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. \n When this will happen: \n General Availability (DoD): We will begin rolling out early February 2025 and expect to complete by mid-March 2025 (previously mid-February). \n How this will affect your organization: \n Approvals is a native Teams application that lets users easily create, manage, and share approvals from a hub for teamwork. These approvals are triggered directly with the Power Automate infrastructure and do not require a flow with an approvals action. \n Users see all of their approvals in the hub, including the approvals that have been completed. Approvals show up across all of a user's systems, including Power Automate, SharePoint, and Microsoft Dynamics 365: \n What you need to do to prepare: \n The Approvals app is on by default if your tenant has enabled Microsoft Power Automate. \n As an admin, you can manage the Approvals app in the Teams admin center on the Approvals app page, including customizing which users can access the app with permission policies. Currently, all approvals are created in your organization's default environment. \n The Approvals app page in the Teams admin center: \n Learn more \n \n Approvals in Microsoft Teams - Power Automate | Microsoft Learn \n Manage the Approvals app in Microsoft Teams - Microsoft Teams | Microsoft Learn \n What is Approvals? - Microsoft Support \n \n 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. \n MC971032 — (Updated) Microsoft Teams: New recording policies for town halls and webinars \n Microsoft 365 Roadmap ID 473887 \n Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams: New admin policies in the Teams admin center and Microsoft PowerShell that govern the recording behavior for town halls and webinars. Before this rollout, the same policies control the recording behavior for town halls, webinars, and meetings. After this rollout, separate recording policies for town halls and webinars will be available to more finely control event behavior. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early April 2025 (previously early March) and expect to complete by mid-April 2025 (previously mid-March). \n How this will affect your organization: \n This change will be available by default. \n What you need to do to prepare: \n Before the rollout, we encourage you to use PowerShell commands to update the default values of the recording policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values. \n Examples of PowerShell commands to set the town hall or webinar recording policy: \n Set-CsTeamsEventsPolicy -Identity Global -RecordingForTownhall Enabled \n Set-CsTeamsEventsPolicy -Identity Global -RecordingForWebinar Enabled \n 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. \n Learn more: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn \n MC971031 — (Updated) Microsoft Teams: New transcription policies for town halls and webinars \n Microsoft 365 Roadmap ID 473886 \n Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Before this rollout, for a Microsoft Teams town hall or webinar, the transcription behavior respects the current Teams meeting transcription policies. After this rollout, new transcription policies will be available for town halls and webinars to allow finer control over transcriptions. The policies may be changed in the Teams admin center or with Microsoft PowerShell commands. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early April 2025 (previously early March) and expect to complete by mid-April 2025 (previously mid-March). \n How this will affect your organization: \n These new transcription policies for webinars and town halls will determine whether transcription is allowed for a town hall or webinar. Town halls and webinars will no longer respect the Teams Meeting transcription policies. \n The new policies will be available by default for admins to configure. \n What you need to do to prepare: \n Before the rollout, we encourage you to use PowerShell commands to update the default values of the transcription policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values. \n Examples of PowerShell commands to set the town hall or webinar policy: \n Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForTownhall Enabled \n Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForWebinar Enabled \n 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. \n Learn more: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn \n MC960811 — (Updated) Microsoft Teams: Enhanced captions for Teams Rooms on Windows \n Microsoft 365 Roadmap ID 423089 \n Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that captions will soon support additional languages and translation capabilities. This enhancement aims to improve meeting accessibility and inclusivity for non-English speaking users using Teams Rooms on Windows. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). \n General Availability (GCC High): We will begin rolling out mid-May 2025 (previously mid-April) and expect to complete by late May 2025 (previously late April). \n General Availability (DoD): We will begin rolling out early June 2025 (previously early May) and expect to complete by mid-June 2025 (previously mid-May). \n How this will affect your organization: \n Before the rollout: Captions in Teams Rooms on Windows only support the English language, which limits usability for non-English speaking users as the captions will result in gibberish if the actual spoken language in the meeting is non-English. There is also no way for admins to set default caption settings. \n After the rollout \n Additional languages: Users can select from a list of supported languages for captions, ensuring that captions are accurate and meaningful for non-English speakers. Users can change the meeting spoken language directly from Teams Rooms devices by selecting More > Captions > Meeting spoken language. \n Real-time translation: Users can translate the meeting's spoken language if the room account has a Teams Rooms Pro license or if the meeting organizer has a Teams Premium license, allowing for real-time translation of captions. Users can translate captions by selecting More > Captions > Translation language. \n Caption settings for Microsoft Teams Rooms on Windows: \n Admin controls: For room accounts with Teams Rooms Pro license, admins can change system defaults, turn on captions by default for calls and meetings, and turn off filtering of profanity in captions and transcripts as necessary with these XML settings: \n \n <CaptionsDefault>true</CaptionsDefault> \n <FilterProfaneWords>false</FilterProfaneWords> \n \n As an admin, you can allow or prevent users (including room accounts) from having access to this feature by configuring calling and meeting policies in the Teams admin center. Learn more: Enable call captions - Microsoft Teams | Microsoft Learn and Manage live captions - Microsoft Teams | Microsoft Learn. \n This feature is available by default. \n What you need to do to prepare: \n After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and settings, 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. \n MC960809 — (Updated) Microsoft Teams: Live transcription for Teams Rooms on Windows \n Microsoft 365 Roadmap ID 423088 \n Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that users can soon start and stop transcription as well as view the meeting transcript directly from Teams Rooms on Windows devices. This feature requires a Teams Rooms Pro license. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). February) \n General Availability (GCC High): We will begin rolling out mid-May (previously mid-April). and expect to complete by late May 2025 (previously late April). \n General Availability (DoD): We will begin rolling out early June 2025 (previously early May) and expect to complete by late June 2025 (previously mid-May). \n How this will affect your organization: \n Before the rollout: When joining a meeting on Teams Rooms on Windows, users must also join the meeting on a companion device to start transcription. Also, even when transcription has been started, users can't view the transcript from the front of room display. \n After the rollout: Users can select More > Record and transcribe > Start transcription or Stop transcription directly from the Teams Rooms on Windows device. Start/stop transcription is supported in any meeting where a participant belongs to the same tenant as the organizer. \n When users transcribe a Meet now or Whiteboard session initiated from a Teams Rooms on Windows device, users must ensure that they invite themselves to the meeting so that they can access the transcript after the meeting through the meeting chat on their Teams desktop or mobile app. \n After transcription is started, users can show/hide the transcript panel on the front of room display in any meeting layout: \n \n Select More> Record and transcribe > toggle On/Off Show transcript. \n Select View> Front row > open the left/right panel dropdown > select/unselect Transcript. \n \n Users can also set the meeting spoken language, translate the transcript, and choose to show the original language and translated language side by side, ensuring accurate and meaningful transcription. \n Live transcription settings in Microsoft Teams Rooms on Windows: \n 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 transcribing meetings with a policy in the Teams admin center. Learn more: Manage transcription for Teams meetings | Microsoft Learn. \n NOTE: Both the meeting organizer and the transcription initiator (room account) need to have permissions to transcribe the meeting. If the meeting organizer uses Meeting options to remove the room account's permissions, the start/stop transcription button will not be available. \n For room accounts with a Teams Rooms Pro license, you have the option to turn off the filtering of profanity in transcripts using this XML setting: <FilterProfaneWords>false</FilterProfaneWords> \n Start/stop transcription is not supported in these scenarios: \n \n Teams calls including P2P, group, and PSTN calls \n External and cross-tenant Teams meetings and calls \n Third-party meetings and calls including Direct Guest Join and SIP \n \n What you need to do to prepare: \n After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and setting, 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. \n MC956699 — (Updated) Microsoft Teams: Forward messages with app cards \n Microsoft 365 Roadmap ID 469506 \n Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience. \n We are introducing the ability to forward app cards. With the addition of app card forwarding, users now have a new way to share app cards across chats. To forward a message containing an app card, simply navigate to the More Actions menu of any message containing an app card and select forward. From here, the forward message dialog will populate, which provides users with a preview of the message being forwarded, including the app card. \n Please note: Forwarding of bot cards is excluded from this release. \n When this will happen: \n Targeted Release: We will begin rolling out mid-February 2025 (previously early February) and expect to complete by late February 2025 (previously mid-February). \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously late January) and expect to complete by early March 2025 (previously early February). \n How this will affect your organization: \n Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained app cards. With this improvement, this restriction does not exist. \n What you need to do to prepare: \n Users must have the latest Microsoft Teams build to receive these updates. You may want to notify your users about this change and update any relevant documentation as appropriate. \n MC952888 — (Updated) Microsoft Teams: Pop out Chat, Copilot, and Notes panes in meetings \n Microsoft 365 Roadmap ID 421607 \n Updated February 24, 2025: The Worldwide release has been temporarily rolled back. We will update this Message center post with new timelines once available. The Targeted release remains enabled. \n Coming soon: Users will be able to pop out the side panes for Notes, Chat, and Microsoft Copilot panes in Microsoft Teams meetings \n Note: The Copilot pane is only available in Worldwide environments with a Microsoft 365 Copilot license. \n When this will happen: \n Targeted Release: We will begin rolling out mid-January 2025 and expect to complete by early February 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will communicate via Message center when ready to proceed. \n How this will affect your organization: \n After the rollout, users will see a pop-out icon at the top of their Notes, Chat, and Copilot side panes in Teams meetings. This change will be on by default. \n When users select the icon, the pane will pop out into a separate window that the user can resize and drag to their desired position, based on their screen setup and their productivity goals for the meeting. Users can view multiple meeting features at the same time, so they don’t miss the chat while they are monitoring meeting notes. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before the rollout. Please notify your users about this change and update any relevant training documentation. \n MC949966 — (Updated) Microsoft Teams Rooms on Windows: Join and present in Microsoft events \n Microsoft 365 Roadmap ID 381425 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon: Microsoft Teams Rooms on Windows devices will be able to join Microsoft events (webinars, town halls, structured meetings) when invited as presenters. You can present directly from the Teams Room, with features like green room access and stage control for organizers and presenters supported on both single and dual screens. Available for tenants with Teams Rooms Pro licenses. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out late February (previously mid-February) and expect to complete by late March 2025 (previously late February) \n How this will affect your organization: \n This feature will be available by default. \n Presenters in the green room and on stage right before starting the meeting in the room's console: \n Learn more: Overview of meetings, webinars, and town halls - Microsoft Teams | Microsoft Learn \n What you need to do to prepare: \n 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. \n MC948994 — (Updated) Microsoft Teams: Collaborative Notes support for GCC High and DoD environments \n Microsoft 365 Roadmap ID 418119 \n Updated February 19, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Teams Collaborative Notes, powered by Loop, is now available for Microsoft 365 GCC High and DoD environments across desktop and web experiences. Notes are Loop components in Teams meetings and chats that allow end users to co-create and collaborate on their meeting agenda, notes, and action items. Since Notes are Loop components, they stay in sync across all the places they have been shared. Assigned tasks automatically sync with To Do and Planner. \n When this will happen: \n General Availability (GCC High, DoD): We will begin rolling out in early April 2025 (previously late March) and expect to complete by late May 2025 (previously late April). \n How this will affect your organization: \n Users within your tenant will see a Notes button during meetings that invokes these new capabilities. The meeting notes will be shown on the right pane of the meeting window with the ability to open them in the browser for more room or on a second monitor. Participants can collaborate in real time, create an agenda, take notes, and add tasks. When participants are assigned a task in the meeting, they will also receive an email notification, and it will be synced with the Planner and To Do apps. \n Meeting organizers and participants will also see an option to add Collaborative Notes before meetings to prepare by adding agendas or other materials in one place. The meeting organizer can also choose to hide the meeting notes prior to the meeting through the Teams scheduling form. If Collaborative Notes are not created ahead of the meeting in the scheduling form, users can create the file by opening the Notes pane in the meeting. \n After the meeting, Collaborative Notes will remain accessible for all participants on the Teams calendar meeting details page and through the meeting recap. The experience is a Loop component, so they can be copied easily out of the meeting and into chats, group chats, emails, and other documents. This makes prepping and follow-up even more seamless. \n Clicking on the meeting note title or the icon in the upper left corner of the note launches the Loop app in browser. If the meeting is part of a series, meeting notes from previous instances can be conveniently found in the Loop app as well. \n This feature is available by default. \n What you need to do to prepare: \n 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. Public documentation is available here: Take meeting notes in Microsoft Teams. \n Note: The new Collaborative Notes file will generate a Company Shareable Link (CSL), unless you have set People Specific Link (PSL) as the default. If PSL is the default, only users who were sent the original meeting invite will be able to access the notes. Users who were forwarded the meeting or nudged into a meeting will need to request access to the notes. \n You can manage this feature via SharePoint PowerShell with: Set-SPOTenant -IsCollabMeetingNotesFluidEnabled (boolean) \n You can read more about admin controls here: Manage Loop experiences (Loop app and Loop components) in SharePoint. \n Known limitations: Collaborative Notes are currently supported for scheduled meetings and channel meetings and are not available for instant meetings or Teams calls. \n MC946818 — (Updated) Microsoft Teams: Updates to Gallery in Teams Rooms on Windows \n Microsoft 365 Roadmap ID 468277 \n Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams Rooms on Windows, the updated Gallery view introduces these changes to enhance your meeting experience: \n \n All participants will appear in consistent tile sizes \n By default, video participants have priority and appear first on the meeting stage by default (audio participants appear on the side or bottom of the screen) \n Ability to disable priority on video participants to create a mix of audio participants and video participants in the Gallery \n Optimized view of up to 25 participants on a single display and up to 50 participants on dual displays \n Preview video is part of the Gallery, appearing next to the rest of the participants \n Ability to hide the preview video across all layouts \n \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). \n How this will affect your organization: \n The updated Galleryprovides a unified meeting experience across both Teams Rooms and desktop. A more consistent and predictable layout can drive meeting efficiency and visibility for remote participants in hybrid meeting scenarios. \n In 1:1 meetings, the preview video will be positioned at the bottom right, overlapping the other participant. \n In group meetings, the preview video will be on the last available tile in the Gallery, next to the rest of the participants. \n Admins can use two new settings to adjust the default view: \n \n Prioritize vide0;< PrioritizeVideoParticipantsGallery> – Default value is True. The default experience will show video participants on the main stage with audio participants on the side or bottom rail. If you would like to display all audio and video participants mixed in the Gallery, change the value to False. \n Hide me <HideMeForAllLayout> – Default value is False. If you would like to hide preview video across all layouts in Teams Rooms on Windows, change the value to True. \n \n In-room users can adjust these settings on the console during a meeting, if desired. \n Lastly, when another Teams Room joins the meeting, the video of the room automatically enlarges if there are more than two in-room users, providing a clearer view and better connection, and so users can focus on the person speaking. \n These changes will be available by default. \n What you need to do to prepare: \n Please notify your users about this change and update any training documentation, as appropriate. \n 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. \n Learn more \n \n Remotely manage Microsoft Teams Rooms device settings - Microsoft Teams | Microsoft Learn(will be updated before rollout) \n Microsoft Teams Rooms (Windows) - Microsoft Support(will be updated before rollout) \n \n MC939927 — (Updated) Microsoft Teams Premium: Decorate your background \n Microsoft 365 Roadmap ID 419811 \n Updated February 24, 2025: We have updated the rollout timeline below. Thank you for your patience. \n We will not release this feature to DoD at this moment. We are sorry for any inconvenience. We will share DoD timeline when available. \n Microsoft Teams Premium users will be able to use the \"Decorate your background\" generative background effect in the GCC, GCC High, and DoD environments, leveraging gen-AI to augment real-life surroundings. It creates a personalized atmosphere for video calls. \n When this will happen: \n General Availability (GCC): We will begin rolling out in early June 2025 (previously early March) and expect to complete rollout by mid-June 2025 (previously late March). \n General Availability (GCC High): We will begin rolling out in mid-June 2025 (previously mid-March) and expect to complete rollout by late June 2025 (previously late March). \n General Availability (DoD): We will communicate via Message center when we are ready to proceed. \n How this will affect your organization: \n “Decorate your background” transforms meeting backgrounds by blending with a user’s real-life surrounding, creating a personalized atmosphere for video calls. It is available to Teams Premium users, and it is supported on Microsoft Windows and MacOS client now. There is not admin policy to disable it. \n Users can access this feature in the following ways: \n \n Before a meeting starts on the pre-join screen, select Effects and Avatars> Video effects > Decorate button. This will allow you to start generating new backgrounds. \n During a meeting, select an animated background by clicking video flyout > More Video Effects and Setting > Decorate. \n \n What you need to do to prepare: \n 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. \n MC939924 — (Uploaded) Microsoft Teams: Start Whiteboard from Teams Rooms on Android in GCC and GCC-H \n Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Microsoft Whiteboard storage is moving from Azure to OneDrive for Business to deliver greater compliance, governance, and retention capabilities. This improvement allows us to offer the Start Whiteboard feature in additional cloud environments (GCC and GCC High) that support OneDrive for Business. The enhanced Whiteboard experience, includes: \n \n Features unique to whiteboards stored in OneDrive, such as Follow me, Commenting, Collaborative cursor, and more. \n Improved performance on whiteboards now stored in OneDrive. \n Improved compliance and security associated with whiteboard being stored in OneDrive. \n \n When this will happen: \n General Availability (GCC, GCC High): We will begin rolling out late January 2025 (previously November) and expect to complete rollout by late February 2025 (previously late January). \n How this will affect your organization: \n Outside of a meeting \n Whenever you want to brainstorm in the office, just start whiteboarding using the new Whiteboard button on the home screen. With one touch, you can quickly launch Microsoft Whiteboard and start collaborating outside of a Teams meeting. \n Since a resource account does not have OneDrive, it will launch a temporary whiteboard. The Save button will guide you to invite your work account to a meeting with your Teams Room so that the temporary whiteboard can be saved in your OneDrive for Business. You will see a saving failure error if you invite a non-room participant who does not have OneDrive. \n Switch from local to online collaboration by selecting Start meeting on the local whiteboard screen. This initiates an ad-hoc meeting and presents the temporary whiteboard. From there, you can add participants into the meeting and contribute across the same whiteboard in real time. The temporary whiteboard will be saved in OneDrive for the first non-room user who joins the meeting. \n In a meeting \n During a meeting, click the Share button and select Microsoft Whiteboard to initiate a whiteboard. The whiteboard will be shared in the meeting and saved in OneDrive for Business for one of the non-room participants at the meeting automatically. \n What you need to do to prepare: \n Please verify that your tenant setting meets the requirements described in this documentation: Manage sharing for Microsoft Whiteboard - Microsoft Whiteboard | Microsoft Learn. \n The Start Whiteboard feature will be turned on by default. Your Home screen (outside of the meeting) will show the Whiteboard button, and the in-meeting share tray will show the whiteboard option. \n If you want to disable the Start Whiteboard feature, please turn it off via the admin setting on your device or apply the configuration profile in Teams admin center using the 'Allow room to use Microsoft Whiteboard' setting under the 'Meeting settings' section. \n Even if the Start Whiteboard feature is disabled for your Teams Rooms on Android device, you can see a whiteboard that remote participants share in a meeting. \n MC920179 — (Updated) Microsoft Teams: The new streamlined Chat and Channels experience \n Microsoft 365 Roadmap ID 415249 \n Updated March 3, 2025: Thank you for your engagement with the new chat and channels experience in Teams. \n The GA rollout begins late March 2025 in a phased rollout and is expected to be completed by end of April 2025. \n We're making the following product improvements from Public Preview and Targeted Release based on user feedback. \n \n Users who haven't onboarded yet to the new experience will havea simplified onboarding flow in Teams with fewer steps. Users who prefer to keep chat and channels separate can easily do so during the onboarding process or later, without IT assistance. \n When the new experience is available for a user, a Get started screen is displayed. Users will have the option to defer the new experience up to three times over the course of approximately three days. About a week after the new experience is available for a user, they will be presented with a final Get started screenand transition to the new experience. \n For users new to the experience on iOS, iPad, and Android,message previews will be on by default. For users new to the experience on Windows, Mac, and Web, message previews will be off by default. \n A quick navigation bar for teams and channelsis available in Teams for Windows, Mac, and Web, at the bottom of the combined Chat view. Clicking on the bar will scroll the view to the teams and channels section for quick navigation. The bar displays in bold when there are unread messages in channels, or with indicators like \"@\" for unread @mentions in channels. \n \n Note: These updates will roll out to users in Public Preview and Targeted Release ahead of GA. \n To help prepare organizations for the new features, product guides for admins and users are already available on the adoption web page https://adoption.microsoft.com/microsoft-teams/new-chat-and-channels-experience. Adoption content has been updated to reflect the above product improvements here. 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. \n For more details and screenshots, refer to Microsoft Teams announces out a new chat and channels experience | Microsoft 365 Blog \n This message applies to Teams on Windows desktops, Mac desktops, the web, and iOS and Android devices. \n This message excludes Education tenants. We will send a future post with an update on the plan for Education tenants. \n When this will happen: \n Public Preview / Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by mid-November 2024. \n General Availability (Worldwide): We will begin rolling out late March 2025 (previously late January) and expect to complete by end of April 2025 (previously early April). \n General Availability (GCC): We will begin rolling out mid-May 2025 (previously mid-June) and expect to complete by late May 2025 (previously late June). \n General Availability (GCC High, DoD): We will begin rolling out mid-June 2025 (previously mid-April) and expect to complete by late June 2025 (previously late April). \n How this will affect your organization: \n The new experience brings chat, teams, and channels into one place, in Chat, so users can easily navigate between all conversations without switching between contexts. Users start in the combined Chat view but can opt to keep chat separate from teams and channels like before. \n In the Chat view, users will see these sections (in order): \n \n Favorites containing any previously pinned chats and channels \n Chats sorted by most recent \n Teams and channels, organized in same order as in the Teams view \n \n Also, users can create custom sections to organize projects and topics that can include individual, group, and meeting chats, as well as channels. \n New filters for Unread, Chat, Channels, Meetings and more help users focus on relevant conversation in their list. Filters persist until turned off. \n The new @mention view gathers all personal @mentions into one interactive list. Users can quickly access messages with @mentions across chats, channels, and meetings. \n Use /go to: Quickly navigate to your frequently used conversation across your chat and channels with a new keyboard shortcut Ctrl+G (Cmd+G on Mac). \n Customizing the experience \n Users can tailor their chat and channels experience in Teams Settings. Users can choose to keep chat, teams, and channels combined in Chat (default) or switch to separate Chat and Teams views. In the combined Chat view on Windows, Mac, and Web, message previews are off by default to simplify the list. Users can turn on message previews in Settings. \n When using the separate Chat and Teams views, users can still use the new filters and the @mentions view to triage and organize topics with custom sections. \n Starting the new experience \n 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. \n 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. \n 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. \n What you need to do to prepare: \n 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. For admins who opt in to emails for recommended Microsoft 365 training, an email for users will summarize the update when released. \n MC912707 — (Updated) Microsoft Teams: New policy for voice and face enrollment will default to \"On\" (configure now) \n Microsoft 365 Roadmap ID 413708 \n Updated February 6, 2025: Please verify that all previously set values remain unchanged and as intended. \n A new csTeamsAIPolicy policy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-March 2025 (previously mid-February) 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 enrollment will 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. \n 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. \n When this will happen: \n The new Microsoft PowerShell cmdlets are available now for admins to configure, to ensure a smooth transition. \n 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-March 2025 (previously mid-February) and is expected to be fully in effect by late March 2025 (previously late February). \n How this will affect your organization: \n Before this rollout, the current policy csTeamsMeetingPolicy has a single setting, EnrollUserOverride, that allows the administrator to enable or disable the enrollment of both face and voice profile of users. \n After this rollout, the new csTeamsAIPolicy will replace the existing enrollment setting in csTeamsMeetingPolicy. The new csTeamsAIPolicy has two settings, EnrollFace and EnrollVoice, that will be set to Enabled by default. \n What you need to do to prepare: \n 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. \n If your organization prefers to disable voice and face enrollments, review and update your settings before mid-March 2025 (previously mid-January). To help you get started, review: \n \n Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn \n Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn \n \n Learn more: Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn \n If your organization prefers to disable voice and face enrollments, review and update your settings before mid-March 2025 (previously mid-February). \n Important: The EnrollUserOverride setting can be assigned globally, directly to users, or to groups in PowerShell. \n Admins must ensure that changes are applied consistently across all these locations to avoid unintended configurations. \n MC908117 — (Updated) Microsoft Teams: Swap screens on Teams Rooms on Android \n Microsoft 365 Roadmap ID 415243 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by late November 2024. \n General Availability (GCC High): We will begin rolling out early December 2024 and expect to complete by mid-March 025 (previously mid-February). \n How this will affect your organization: \n Before this rollout \n \n 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. \n 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. \n \n After this rollout \n \n 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. \n 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. \n 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 \n \n NOTE: If you are deploying Teams Rooms on Android devices with dual displays, be aware that dual display mode must be explicitly enabled in the configuration profile. By default, the dual display setting is OFF, which means that using an existing configuration profile (designed for single-display devices by default) may inadvertently disable dual display mode for your existing dual display rooms. To avoid this, you must create and maintain a separate configuration profile for any devices that require dual display support. \n This feature will be off by default and available for admins to configure. \n What you need to do to prepare: \n 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. \n This rollout will happen automatically by the specified date with no admin action required before the rollout. \n MC907108 — (Updated) Microsoft Teams: Admin email support for \"Report a problem\" on Teams Rooms on Android \n Microsoft 365 Roadmap ID 415247 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams Rooms on Android: As an admin, you can configure an email address for receiving issues submitted by users through the Report a problem feature 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by late November 2024. \n General Availability (GCCH): We will begin rolling out early December 2024 and expect to complete by mid-March 2025 (previously mid-February). \n How this will affect your organization: \n 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. \n After the rollout \n When you configure an email address in Teams admin settings > General > Logs and feedback, the Report a problem option on Teams Rooms on Android devices will be enabled, and any feedback submitted by room users using Report a problem will 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. \n Users can access Report a problem from the Help button on the home screen or the More button in meetings. Report a problem can also be accessed on the pre-sign in screens. \n 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. \n 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, see Collect Teams Android device logs | Microsoft Learn. \n This feature will be off by default and available for admins to configure. \n 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. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before the rollout. \n 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. \n MC906501 — (Updated) Microsoft Teams: Net Promoter Score survey on Teams Rooms on Android \n Microsoft 365 Roadmap ID 415245 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by late November 2024. \n General Availability (GCCH): We will begin rolling out early December 2024 and expect to complete by mid-March 2025 (previously mid-February). \n How this will affect your organization: \n Before this rollout: NPS surveys do not appear on Android devices. \n After this rollout \n 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. \n 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. \n As an admin, you can prevent room accounts from getting NPS surveys with Microsoft PowerShell. Learn more at Manage feedback policies in Microsoft Teams - Microsoft Teams | Microsoft Learn. \n What you need to do to prepare: \n 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. \n MC898391 — (Updated) Microsoft Teams: Performance improvements for meetings in Edge web browser for guests \n Microsoft 365 Roadmap ID 401117 \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Anonymous users (guests) who join Microsoft Teams meetings in the Microsoft Edge for Business web browser will soon experience performance improvements. They will be able to join meetings faster. \n When this will happen: \n Targeted Release: We will begin rolling out early November 2024 and expect to complete by mid-November 2024. \n General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by late-November 2024. \n General Availability (GCC, GCC High, and DoD): We will begin rolling out early January 2025 and expect to complete by late March 2025 (previously late January). \n How this will affect your organization: \n Before this rollout, anonymous users (guests) may experience longer wait times when attempting to join a Teams meeting. \n After this rollout, anonymous users (guests) will be able to join meetings faster, even on low-end devices. \n What you need to do to prepare: \n This rollout will happen automatically with no admin action required. \n MC894581 — (Updated) Microsoft Teams: Performance improvements for meetings in Chrome web browser for guests \n Microsoft 365 Roadmap ID 401116 \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Anonymous users (guests) who join Microsoft Teams meetings in the Chrome web browser will soon experience performance improvements. \n When this will happen: \n Targeted Release: We will begin rolling out early November and expect to complete by mid-November 2024. \n General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by late-November 2024. \n General Availability (GCC, GCC High and DoD): We will begin rolling out early January 2025 and expect to complete by late March 2025 (previously late January). \n How this will affect your organization: \n Before this rollout, anonymous users (guests) may experience longer wait times when attempting to join a Teams meeting. \n After this rollout, anonymous users (guests) will be able to join meetings faster, even on low-end devices. \n What you need to do to prepare: \n You may want to update your internal documentation to inform your users about this improvement. However, because the improvement is for external users and does not change the look of Teams, you can skip this step./p> \n MC889534 — (Updated) Microsoft Teams: Embed support for Teams town hall \n Microsoft 365 Roadmap ID 401120 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n As a part of Team’s ongoing effort to enable our customers to create, manage, and run large scale events, end users can now embed Teams town hall in sites they manage. This capability allows town hall attendees to watch the event instance within a particular website. \n Embed for town hall introduces embeddable support for town hall engagement features on release. Attendees will have the same engagement feature access within the embed player as they do in client such as Q&A, Captions, Reactions and more. \n To implement embed for town hall, organizers can access their town hall events unique embed code from the town hall scheduling template upon publish. Organizers can then take that code and inject it to their SharePoint or Microsoft 365 site as desired. On event start, attendees will be able to view and engage with the embed stream on the published site. \n When this will happen: \n Targeted Release: We will begin rolling out early November 2024 (previously early October) and expect to complete by mid-November 2024 (previously mid-October). \n General Availability (Worldwide, GCC): We will begin rolling out early December 2024 (previously late October) and expect to complete by mid-March 2025 (previously mid-February). \n How this will affect your organization: \n Users will be able to copy embed code directly from town hall scheduling form on event publish. After the embeddable code is placed in the website, the town hall player will be accessible to attendees who have access to the URL. \n Note: Attendee access to the embedded video player is driven by the town hall event access. \n What you need to do to prepare: \n Organizers with SharePoint or Microsoft 365 site who want to utilize embed support for town hall can begin implementing the embeddable code upon release. \n MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar \n Microsoft 365 Roadmap ID 409226 \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n 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). \n General Availability (Worldwide, GCC): We will begin rolling out in mid-October 2024 and expect to complete by late March 2025 (previously late January). \n How this will affect your organization: \n Before this release: Sensitivity labels were not available for town halls and webinars. \n 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 under Event access may be enabled or disabled based on the sensitivity label set for the event: \n For upcoming events that have already been scheduled prior to rollout, the sensitivity of the event will be set to None. 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. \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with revised documentation. \n MC809602 — (Updated) Microsoft Teams: New skin tone settings and reactions \n Microsoft 365 Roadmap ID 323766 \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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 app Settings > Appearance and accessibility menu 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). \n When this will happen: \n Targeted Release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October). \n General availability (Worldwide, GCC): We will begin rolling out early November 2024 (previously late October) and expect to complete by late December 2024. \n General availability (GCC High, DoD): We will begin rolling out mid-November 2024 (previously mid-November) and expect to complete by late March 2025 (previously late January). \n How this will affect your organization: \n Changing skin tone in the emoji menu in Teams for Desktop: \n Changing skin tone in Teams Settings > Appearance and accessibility in Teams for Desktop: \n Changing skin tone in Teams Settings > Appearance on Teams Mobile: \n The selected skin tone appears in reactions in chats, channels, and meetings: \n What you need to do to prepare: \n 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. \n We will update this post before rollout with revised documentation. \n MC804771 — (Updated) Microsoft Teams: Hiding inactive channels \n Microsoft 365 Roadmap ID 325780 \n Updated February 14, 2025: Based on Admin feedback, we are updating the behavior for automated hiding of inactive channels to be opt-in (suggestions) only. With this update, Teams will offer users suggestions on channels that are inactive, and the user is prompted to review their inactive channels and hide them only if they choose. The settings are also updated to reflect this opt-in workflow. There are no changes to the on-demand hiding process. \n This feature is enabled till Targeted Release, and we will roll out to General Availability later this year. \n In the interim, we are disabling the current generally available version of the feature which requires users to opt-out as well as the settings, for all users. Please note that all users in the public or general ring will not see the setting or have any of their channels hidden automatically. We will re-introduce the updated feature later this year. \n Note: Users with EDU licenses assigned will not receive this change. \n Microsoft Teams will detect and hide inactive channels users have not interacted with recently. Users can choose to have Teams run this automatically as well as initiate the hiding process on demand when needed. They can review the list of channels and choose none, some or all of the inactive channels to be hidden. Users can opt out of automated hiding anytime from Teams Settings. This message applies to Microsoft Teams for Desktop, web, and Mac. \n When this will happen: \n Targeted Release: We will begin rolling out mid-July 2024 and expect to complete by late July 2024. \n General Availability (Worldwide): We will begin rolling out mid-November 2024 (previously mid-August) and expect to complete by mid-January 2025 (previously mid-September) \n General Availability (GCC): We will begin rolling out early February 2025 (previously late September) and expect to complete by mid-February 2025 (previously early October). \n General Availability (GCC High): We will begin rolling out early February 2025 (previously early October) and expect to complete by mid-February 2025 (previously mid-October). \n General Availability (DoD): We will begin rolling out mid-February 2025 (previously late October) and expect to complete by late February 2025 (previously late October). \n How this will affect your organization: \n Before this rollout: Users had to manually manage their relevant channels list by hiding inactive and irrelevant channels. \n After this rollout: \n Manage preferences for automated hiding via Teams Settings \n If users prefer to manage channels manually, they can opt out of the auto-hiding process. Simply go to Teams settings, select General, and toggle off \"Hide Inactive Channels.\" \n Hide inactive channels on demand when needed \n Users can manually view which channels are inactive and choose to hide some or all of them whenever you need. This can be done from Settings, under General, by clicking the \"Hide Now\" button. Note that this action can be performed once every 24 hours. \n Automated hiding of inactive channels \n With this, Teams will hide channels that have been inactive for the user. Inactive channels are identified based on the following criteria: if the user has not been active in the channel in the last 120 days – meaning there is no new messaging in the channel that the user has read or reacted to – the channel is considered inactive. Once the inactive channels are identified, the user is notified with the coach mark message, \"We're hiding some inactive channels for you.\" \n The user can select View changes to see the details. The user can keep the channels hidden or show them again. \n If a user has less than or equal to 25 shown channels, no channels will be hidden for that user. \n What you need to do to prepare: \n Admins need to be aware of this feature, but no additional action is needed. The feature will roll out starting in November 2024. Users will first see their settings enabled to manage their preferences for automated hiding; additional to the ability to manually hide inactive channels. \n Users will start to see the automated hiding of inactive channels, a few weeks after the feature has rolled out. \n MC781595 — (Updated) Microsoft Teams: Tenant-wide policy for permission to download meeting transcription \n Microsoft 365 Roadmap ID 332800 \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n Targeted Release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May). \n 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). \n 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) \n General Availability (DoD): We will begin rolling out late September 2024 (previously mid-August) and expect to complete by complete by late March 2025 (previously late January). \n What you need to do to prepare: \n 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. \n 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.) \n MC772556 — (Updated) Microsoft Teams: Shorter meeting URLs \n Microsoft 365 Roadmap ID 381953 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Please note that information about meeting link expiry changes related to this rollout has been added. \n We are reducing the length of Microsoft Teams meeting URLs for easier sharing. This rollout applies to all Microsoft Teams platforms (Teams for iOS, Android, Mac, Teams devices, desktop, and web). \n When this will happen: \n Targeted Release: We will begin rolling out mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). Only Meet Now use cases (except Meet Now in chats and channels) will be affected in this timeframe. There will be no impact on the scheduled meetings in this phase. \n General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 (previously mid-April) and expect to complete by late May 2025 (previously late April). Only Meet Now use cases (except Meet Now in chats and channels) will be affected in this timeframe. There will be no impact on the scheduled meetings in this phase. Rollout for scheduled meetings and channel Meet Now will be started in early July 2025 and expected to be completed by mid-July 2025. \n General Availability (GCC High, DoD): We will begin rolling out early August 2025 (previously early June) and expect to complete by mid-August 2025 (previously late June). \n How this will affect your organization: \n The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode> \n To make meeting URL shorter, we are removing several parameters such as tenant ID, conversation ID etc. This change serves two main goals: 1) improving usability of URL during sharing and 2) making the URL more secure and less susceptible to malicious attacks. \n Here are some details about how meeting links work and when they expire: \n \n In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire. \n Every meeting link expires in 60 days after the scheduled event or in 8 hours, if it was created as Meet Now. Learn more about expiration timelines for different types of meetings. \n \n With the Short Meeting URL release, expiration limit will be applied to all newly created links. \n Once the change to Short Meeting URL is released, all newly created meetings will expire as described in the documentation: 60 days after meeting ends for scheduled meetings and 8 hours after creation for Meet Now. Once this expiry period is over, in case someone clicks the link (e.g. outside of Teams app OR in the meeting details inside Teams calendar section), they will be unable to join the meeting. \n Note: Old links created before short meeting URL release will continue working as it previously was (user will be able to join even after the documented expiry limits). \n The reason why we are making this change is simple: security is our topmost priority. Maintaining a high security level is essential to protect sensitive data, prevent financial losses, ensure business continuity, and meet compliance and legal obligations. It is a critical aspect of modern digital life and business operations. This adjustment is designed to enhance the security of Teams meeting links, thereby better safeguarding the customer tenant. We want to be on par with modern security standards, that’s why the new behavior is a step in the right direction that we must take. It’s not possible to keep the current behavior. If you think it breaks some of your business processes, please leave comment to the MC post and describe your case there. \n Recommendations in case the meeting link has expired: \n For meeting organizer: We recommend scheduling a new meeting. If the meeting organizer got removed from the tenant someone else should reschedule their meetings from scratch. \n For participant: Please reach out to the meeting organizer and ask them to reschedule the meeting or send you an updated link. \n What you need to do to prepare: \n You may want to check if you have any integrations that use parameters from URL. After the rollout, the URL will only contain the meeting ID. Parameters such as tenant ID, organizer ID, conversation ID and message ID will not be in the URL. \n You may inform meeting organizers from your tenant who use expired meeting links, or you may want to make a tenant-wide announcement about this change. \n 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. \n MC750668 — (Updated) Microsoft Teams: Access Workflows from the three-dot menu on shared file \n Microsoft 365 Roadmap ID 381643 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n Targeted release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October). \n Worldwide: We will begin rolling out early November 2024 (previously late October) and expect to complete by late November 2024 (previously early November). \n GCC: We will begin rolling out early December 2024 (previously late October) and expect to complete by mid-March 2025 (previously mid-February). \n How this will affect your organization: \n 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 choose Workflows. From Workflows, 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 selecting See more workflows at 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. \n If the Power Automate app is disabled in the Teams admin center, users will not see this option in the three-dot menu. \n This feature will only be available in the New Teams client on the desktop and on the web. \n What you need to do to prepare: \n 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. \n MC726122 — (Updated) Microsoft Teams: View, download, and delete Microsoft OneDrive transcript files \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n 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. \n 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. \n A summary of the deletion experience for meeting transcripts is captured in the following table: \n \n \n When this will happen: \n Targeted release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May). \n 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). \n GCC High: We will begin rolling out late August 2024 and expect to complete by mid-September 2024. \n DoD: We will begin rolling out late September 2024 and expect to complete by late March 2025 (previously late January). \n How this will affect your organization: \n 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 this documentation. \n 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. \n What you need to do to prepare: \n 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. \n MC718553 — (Updated) Microsoft Teams: Change background while recording on phone \n Microsoft 365 Roadmap ID 380852 \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Users can now record themselves anywhere and share it with coworkers in the Microsoft Teams chat or channel without worrying about the background. Users can now change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on iOS devices. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out early May 2024 (previously late March) and expect to complete by late March 2025 (previously late January). \n How this will affect your organization: \n Users will get an option to change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on an iOS device. To use this feature: \n \n Press and hold the camera icon next to the Compose box and then tap the blur icon to the right of the shutter button. \n You can then choose either an image to replace the background or choose to mildly or heavily blur your background. \n \n What you need to do to prepare: \n 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. \n MC709270 — (Updated) Mute with Windows Taskbar available in the new Microsoft Teams on Windows \n Microsoft 365 Roadmap ID 191528 \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n The Muting Teams with Windows Taskbar is now available. This feature, available in the new Teams experience on Windows, enables you to mute and unmute your audio by clicking the mic icon in Windows taskbar. \n To control your call mic from the taskbar, do the following: \n Select the mic icon on your taskbar or press Windows logo key + Alt + K to mute or unmute your microphone while using a calling app. \n -OR- Click the volume icon in the hardware indicator for volume in Windows taskbar. \n When this will happen: \n Targeted release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May). \n Worldwide, GCC, GCC High & DoD: We will begin rolling out mid-June 2024 (previously early June) and expect to complete by complete by late March 2025 (previously late January). \n How this will affect your organization: \n This enables a feature previously available in older version of Teams on Windows. \n What you need to do to prepare: \n To prepare, distribute updates on this rollout with your organization if applicable for your users. \n MC705760 — (Updated) Teams: Latest meeting experiences with performance improvements on web for Safari and Firefox (for guests) \n Microsoft 365 Roadmap ID 329253 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n The latest Teams meeting experiences will be available for Teams on the web in Safari and Firefox browsers - including performance improvements, refreshed pre-join, updated meeting stage, and the updated meeting toolbar. (for anonymous join only) \n When this will happen: \n Worldwide: We will begin rolling out early September 2024 (previously mid-August) and expect to complete by early October 2024 (previously late August). \n GCC, GCC High and DoD: We will begin rolling out mid-October 2024 (previously mid-September) and expect to complete by mid-March 2025 (previously mid-February). \n How this will affect your organization: \n We make constant steps to improve Teams performance irrespective of the platform – this time we are making the experience of Teams meetings on web (in Safari and Firefox browsers) better for anonymous users (guests). That’s crucial because it improves external collaboration. For example, if participants from your tenant would like to have meetings with non-Teams users (who are often joining as guests) it’ll become simpler as guests joining meeting from Safari/Firefox web browsers won’t have to wait significant amount of time for the meeting experience to load. \n You may also notice that currently meeting UI in Chrome and Safari/Firefox is different, but with this update it won’t be a case anymore and you’ll enjoy all the benefits of modern UI (such as meeting toolbar on top of the screen, etc). \n What you need to do to prepare: \n You may want to update your internal documentation to inform your users about this improvement. \n MC688109 — (Updated) Co-organizer experience updates in Teams Webinars and Townhalls \n Microsoft 365 Roadmap ID 168524 \n Updated February 12, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n Targeted release: We will begin rolling out mid-January 2025 (previously early January) and expect to complete by mid-January 2024 (previously mid-December). \n General Availability (Worldwide, GCC): We will begin rolling out mid-January 2025 (previously mid-December) and expect to complete by late February 2025 (previously mid-January). \n How this will affect your organization: \n When co-organizer opens the event scheduling page, they should have the ability to edit the details page, publish, and cancel the event. \n What you need to do to prepare: \n Nothing required to prepare. \n Purview \n MC1011148 — Microsoft Purview | Insider Risk Management: Increasing policy template limits \n Microsoft 365 Roadmap ID 477364 \n Coming soon to Microsoft Purview | Insider Risk Management: We will increase policy creation limits from 20 policies per template to a maximum of 100 overall active policies. After the rollout, for example, an organization may have 50 data leak policy templates because the limit will now apply to all active policies instead of applying to each policy template. \n When this will happen: \n Public Preview: We will begin rolling out mid-March 2025 and expect to complete by mid-April 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early July 2025 and expect to complete by mid-August 2025. \n How this will affect your organization: \n This change will be on by default. \n What you need to do to prepare: \n No impact to your organization. \n 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. \n Learn about policy template limits in Learn about insider risk management policy templates | Microsoft Learn (will be updated before rollout) \n MC1004410 — Microsoft Purview | Endpoint Data Loss Prevention - Classification improvements on file read access in macOS devices \n Microsoft 365 Roadmap ID 478930 \n Data classification on files stored in macOS devices will be triggered automatically when handing files on read access to improve classification operations. \n When this will happen: \n General Availability (GCC, GCCH, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. \n How this will affect your organization: \n Files that are stored locally on macOS devices will improve data classification whenever files are accessed and read. This system-level change is automatically happening for those macOS devices that have endpoint Data Loss Prevention (DLP) deployed and will not be visible to the end user. \n For more information about items on targeted devices being automatically reevaluated the next time they're accessed or modified, see Best practice for endpoint DLP policies. \n What you need to do to prepare: \n 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. \n MC999442 — Microsoft Purview | Data Lifecycle Management: Retention based on “last accessed” for OneDrive and SharePoint files \n Microsoft 365 Roadmap ID 472030 \n Coming soon for Microsoft Purview | Data Lifecycle Management: Admins will be able to apply a retention policy or retention label in Microsoft OneDrive and Microsoft SharePoint for files that have not been accessed by anyone in your organization for a specified period of time. This message applies to retention for Microsoft 365 file types. We will support other file types (non-Microsoft 365) in a future rollout. \n When this will happen: \n Public Preview: We will begin rolling out mid-February 2025 and expect to complete by late February 2025. \n General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n This feature will help delete obsolete data, which will improve the quality and relevance of Microsoft 365 Copilot responses. \n This feature will be available by default. \n After the rollout, admins can use the retention control When items were last accessed when configuring labels and policies. \n Retention settings page in Purview with the new “last accessed” option for retention policies: \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with new documentation. \n MC973511 — (Updated) Microsoft Purview | Data Lifecycle Management: Separate retention policies for Copilot and AI apps \n Microsoft 365 Roadmap ID 470025 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n This new feature provides the capability for admins to configure separate retention policies for various Microsoft 365 Copilot and AI apps. As a result, admins will have the option to configure policies that can delete Copilot and Generative AI interactions faster. \n When this will happen: \n General Availability (Worldwide): We will begin rolling out late February 2025 (previously mid-February) and expect to complete by early March 2025 (previously late February). \n How this will affect your organization: \n Organizations will now have controls to configure different retention policies for Microsoft Teams Chat, Copilot, Copilot studio, and ChatGPT Enterprise. \n This feature is available by default. \n What you need to do to prepare: \n For more information, see Create and configure a retention policy. \n 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. \n MC971035 — Microsoft Purview | Data Lifecycle Management: New secure workflow to bypass legal holds and retention policies \n Microsoft 365 Roadmap ID 392838 \n Updated February 7, 2025: We have updated the rollout timeline below. Thank you for your patience. \n This new feature enables data governance administrators to expedite the permanent deletion of sensitive content from Microsoft Exchange mailboxes, overriding any existing retention settings or eDiscovery holds. This process may be required for security or privacy, such as after a data spillage incident or for compliance and regulatory requirements. \n When this will happen: \n Public Preview: We will begin rolling out late February 2025 (previously early February) and expect to complete by mid-March 2025 (previously mid-February). \n Worldwide: We will begin rolling out late March 2025 and expect to complete by mid-April 2025. \n How this will affect your organization: \n Priority Cleanup administrators can now set up a Priority Cleanup policy for Exchange to create exceptions to retention principles and e-Discovery holds for specific scenarios. Once administrators are within the Data Lifecycle Management (DLM) Solution on Microsoft Purview, they can visit the Priority Cleanup tab and follow the wizard to set-up this policy. Like auto-apply retention labels, Priority Cleanup supports policy simulation mode, so administrators can check the returned samples in case the policy configuration needs any fine-tuning before enabling the policy. Once set-up, because the deletion by a priority cleanup policy is irreversible and can override existing holds, the process requires multiple approvals, specific roles, and is audited. Thus, respective reviewers must be mandatorily added during policy creation to allow for disposition of items under a retention or e-Discovery hold. \n What you need to do to prepare: \n Because of the built-in safeguards, the feature itself is enabled by default at the tenant level. However, Priority Cleanup can be turned off on the Priority Cleanup settings page. If you can't create new Priority Cleanup policies, refer to your Data Lifecycle Management documentation for necessary roles and permissions requirements. A new role permission \"Priority cleanup administrator\" is now added to Purview role permissions to enable data governance administrators to use this feature. \n MC950890 — (Updated) Microsoft Purview | Data Security Posture Management for AI \n Microsoft 365 Roadmap ID 469509 \n Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Generative AI (GAI) is being adopted at an unprecedented rate. AI fuels innovation and productivity but also poses risks – organizations are concerned about the risky AI use and sensitive data loss through AI apps. Microsoft Purview Data Security Posture Management for AI (DSPM for AI) is a central location in Microsoft Purview that helps organizations secure data in AI, including Microsoft AI applications such as Microsoft 365 Copilot and non-Microsoft AI applications. With the DSPM for AI capabilities in Purview, organizations can safely adopt AI without having to choose between productivity and protection. \n DSPM for AI also supports admin units and displaying AI policies that were created in Purview solutions. A version of DSPM for AI is available to additional licensing, specifically Microsoft 365 E3 and Microsoft 365 Copilot licenses. \n When this will happen: \n We will begin rolling out late February 2025 (previously late January) and expect to complete by late March 2025 (previously late February). \n How this will affect your organization: \n DSPM for AI also supports admin units and displaying AI policies that were created in Purview solutions. A version of DSPM for AI is available to additional licensing, specifically Microsoft 365 E3 and Microsoft 365 Copilot licenses. \n DSPM for AI use cases \n \n Viewing insights and analytics into AI activity in your organization. \n Using policies to protect data and prevent data loss in AI prompts \n Implementing compliance controls to apply optimal data handling and storing policies \n \n Microsoft Purview DSPM for AI will be in the Microsoft Purview portal and will consist of 5 tabs: Overview, Recommendations, Reports, Policies, and Activity explorer. \n Reports includes graphs for total interactions over time, sensitivity labels and sensitive information types found in AI interactions, user risk level, and more. \n Policies displays all policies that have been created by default or AI policies created in Purview solutions. \n Activity explorer shows events for AI interactions along with prompts and responses. \n This feature will be enabled by default. \n What you need to do to prepare: \n 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. \n Get ready for this change by reviewing the admin documentation: \n \n Considerations for Data Security Posture Management for AI & data security and compliance protections for Copilot \n Microsoft Purview data security and compliance protections for generative AI apps \n \n MC937158 — (Updated) Microsoft Purview | Insider Risk Management: New scenario-based policy templates \n Microsoft 365 Roadmap ID 409966 \n Updated February 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Purview | Insider Risk Management: Two new preconfigured quick policy templates for Crown jewel protection and Email exfiltration. These templates are for admins who want to deploy scenario-specific policy templates with less configuration, to get started faster. The existing quick policies for Data leak and Data theft will continue to be available. You can find all four scenario-based quick policies in Insider Risk Management at Policies > Create Policies. Admins can expect additional turning after deploying these policies to meet individual alert volume needs. \n When this will happen: \n Public Preview: We will begin rolling out late November 2024 and expect to complete by mid-December 2024. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously early February) and expect to complete by late March 2025. \n How this will affect your organization: \n \n Sign in to Insider Risk Management with the admin role permissions \n Go to the Policiespage at https://purview.microsoft.com/insiderriskmgmt/policiespage \n Select Create policy \n Select Quick policies \n Select either the Crown jewel protectionpolicy or the Email exfiltration policy \n Configure policy as applicable (add users to scope, optional priority content, and so on) \n \n The new policies will be on by default. \n What you need to do to prepare: \n 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. \n Learn more: The Quick Policies section in Create and manage insider risk management policies | Microsoft Learn \n MC920308 — (Updated) Microsoft Purview | Information Protection: Auto-labeling policies will support \"Fingerprint based SIT\" \n Microsoft 365 Roadmap ID 396173 \n Updated February 11, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Purview | Information Protection: Admins will be able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT (sensitive info type). \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late November 2024 and expect to complete by mid-February 2025 (previously early February). \n How this will affect your organization: \n Before this rollout, admins are not able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT. \n After this rollout, you can configure Fingerprint based SIT using the condition Content contains sensitive information types. Files that match Fingerprint based SIT will show in simulation. \n Note: Contextual summary is not available for Fingerprint based SITs. \n This change will be on by default and available for admins to configure. \n What you need to do to prepare: \n 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. \n Learn more \n \n About document fingerprinting | Microsoft Learn \n Automatically apply a sensitivity label in Microsoft 365 | Microsoft Learn \n \n MC911618 — (Updated) Microsoft Purview | Insider Risk Management: Multi-policy settings in Adaptive Protection \n Microsoft 365 Roadmap ID 171735 \n Updated February 5, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n After this rollout, admins will be able to select multiple Insider Risk Management policies in the Risk levels for Adaptive Protection settings. \n When this will happen: \n General Availability (GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously mid-January) and expect to complete by mid-March 2025 (previously mid-February). \n How this will affect your organization: \n Before this rollout, admins can select single Insider Risk Managment policies in the Risk levels for Adaptive Protection settings. \n This new feature will be on by default and available for admins to configure. \n What you need to do to prepare: \n 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 \n 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. \n Learn more: Help dynamically mitigate risks with Adaptive Protection (preview) | Microsoft Learn \n Microsoft 365 Copilot \n MC1020327 — M365 Copilot for GCC Environments: Wave 2 \n Microsoft 365 Roadmap ID 483357 \n Bringing Microsoft 365 Copilot GCC your AI assistant for work in the GCC environment. It combines the power of Large Language Models with your work content and context, to help you draft and rewrite, summarize and organize, catch up on what you missed, and get answers to questions via open prompts. Copilot generates answers using the rich, people-centric data and insights available in the Microsoft Graph. \n We are excited to announce the release of the second wave of apps for M365 Copilot into the GCC environment. This release includes Stream, OneNote, SharePoint, and Pages in Loop, enhancing your organization's productivity and collaboration capabilities. \n When this will happen: \n General Availability (GCC): We will begin rolling out in late March 2025 and expect to complete by early April 2025. \n How this will affect your organization: \n As with the other M365 Copilot experiences released in December, the web grounding policy default is OFF for GCC. Web grounding in these new apps will follow the settings of the existing web grounding policy. \n What you need to do to prepare: \n A toggle is available in your admin center to enable and disable web grounding for M365 Copilot experiences. Please review your settings and make any necessary adjustments to align with your organization's needs. \n For more information and resources, please visit: Data, privacy, and security for web search in Microsoft 365 Copilot and Microsoft 365 Copilot Chat. \n MC1020200 — New Microsoft 365 Copilot release notes page \n We are pleased to announce the availability of a new, centralized Microsoft 365 Copilot release notes page. This page consolidates all Copilot-related releases across the Microsoft 365 suite—such as Word, Excel, PowerPoint, Outlook, Teams, Microsoft 365 Copilot app, Copilot chat, and more—into a single, easy-to-reference resource. It also includes platform-specific filters for Windows, Web, Mac, Android, and iOS to help you quickly locate the updates most relevant to your organization. \n This new page highlights features and enhancements that have reached General Availability (GA) across selected platforms, ensuring you can stay informed about the latest capabilities of Copilot across Microsoft 365. \n When this will happen: \n The new Copilot release notes page is available now at Microsoft 365 Copilot release notes. We will continue to update it regularly as new Copilot features become generally available across different services and platforms. \n How this will affect your organization: \n \n Centralized information:Rather than visiting multiple sources, you can now view all Copilot GA releases in one location. \n Easier discovery:Filter by the specific platform(s) you use (Windows, Web, Mac, Android, iOS) for more targeted release information. \n Up-to-date insights:The page is refreshed every other week, ensuring you always have the latest Copilot updates at your fingertips. \n \n What you need to do to prepare: \n \n Bookmark the page: We recommend that admins and end users bookmark this new release notes page for quick access. \n Share internally: Distribute the link to this page within your organization so teams can stay aware of all relevant Copilot updates. \n Review and plan: Use the information in the release notes to plan for any necessary training, user documentation updates, or adoption strategies aligned with your organization’s Copilot deployment. \n Submit your feedback: Your input is important to us. Use the 'Feedback' button on the Copilot release notes page to share what you like and where improvements can be made so we can continue enhancing this resource to better meet your needs. \n \n MC1003344 — (Updated) Microsoft Copilot: File summary in Microsoft Teams chat \n Microsoft 365 Roadmap ID 418564 \n Updated February 20, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Users will be able to summarize files with Summarize for me using Microsoft Copilot within one-on-one or group Microsoft Teams chats. This feature will work on common file types like Word and PDF initially, and other file formats will be added over time. This summarization respects the file's security policies, ensuring that only users with access to the file receive a summary, which will carry the same sensitivity label as the original file. A Microsoft 365 Copilot license is required to use this feature. \n When this will happen: \n Targeted Release: We will begin rolling out early April 2025 (previously early March) and expect to complete by mid-April 2025 (previously mid-March). \n General Availability (Worldwide): We will begin rolling out late April 2025 (previously late March) and expect to complete by mid-May 2025 (previously mid-April). \n General Availability (GCC): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025. \n How this will affect your organization: \n Users will be able to summarize files with Summarize for me in Copilot within Teams chats. \n This feature will be available by default. \n What you need to do to prepare: \n 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. \n Microsoft Outlook \n MC1022526 — Microsoft Outlook on the web: Optional connected experiences privacy setting \n Microsoft 365 Roadmap ID 467248 \n The user privacy setting for optional connected experiences, already available in other Microsoft Outlook and Microsoft 365 apps, will soon be available in Microsoft Outlook on the web. \n When this will happen: \n General Availability (Worldwide): We will begin rolling out early March 2025 and expect to complete by late March 2025. \n General Availability (GCC): We will begin rolling out in early April 2025 and expect to be complete by late April 2025. \n How this will affect your organization: \n After the rollout, to configure the privacy setting for optional connected experiences, users can go to Settings > General > Privacy and data > Privacy settings: \n \n On the Privacy settings screen, select the toggle for Turn on optional connected experiences: \n \n This privacy setting applies across all devices where users are signed in with the same work or school account. \n As an admin, if you have already made optional connected experiences available to your users in the Microsoft 365 Apps admin center, this setting will be turned on for Outlook on the web when users receive this rollout. Learn more: \n \n Use policy settings to manage privacy controls for Office for the web applications - Microsoft 365 Apps | Microsoft Learn \n Overview of Cloud Policy service for Microsoft 365 - Microsoft 365 Apps | Microsoft Learn \n \n NOTE: If a user has already turned off this setting in another Outlook or Microsoft 365 app, this setting in Outlook on the web will also be turned off when the user receives this rollout. \n What you need to do to prepare: \n 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. \n Learn more \n \n About privacy controls for optional connected experiences: Overview of privacy controls for Microsoft 365 Apps for enterprise(will be updated before rollout) \n About Office on the web policy settings, including the new settings for Outlook on the web: Use policy settings to manage privacy controls for Office for the web applications(will be updated before rollout) \n \n MC1020206 — Change to Copilot Settings in Outlook \n Starting in March 2025, Outlook will introduce a new setting that allows users to hide Copilot entry points (e.g., \"Summarize this email\") from the app. This setting can be configured per account and will apply to both organizational and personal email accounts within the app. Once set, the preference will sync across all Outlook applications. This update is in response to user feedback. \n When this will happen: \n The rollout will begin in March 2025. \n How this affects your organization: \n Users will have the option to hide Copilot entry points in the following Outlook applications: \n \n New Outlook for Windows \n Outlook for iOS \n Outlook for Android \n Outlook for Mac \n Outlook on the Web \n \n \n Classic Outlook for Windows will not have the ability to change this setting. However, any changes made in other Outlook applications will sync with Classic Outlook for Windows. \n What you can do to prepare: \n Admins should inform users about this new setting and its availability across different Outlook applications. No additional action is required as the setting will be available by default. \n MC1011141 — Microsoft Outlook for iOS and Android: Microsoft 365 (Office) app is now the Microsoft 365 Copilot app \n The Microsoft 365 (Office) app has become the Microsoft 365 Copilot app. After this rollout, users will notice changes in the Microsoft Outlook apps for iOS and Android. Also, when Outlook for iOS and Android users view their account list in Settings, they will notice a new icon for their Microsoft account. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out early March 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n Before this rollout, Microsoft 365 (Office) app and Microsoft 365 accounts in the Microsoft Outlook apps for iOS and Android have this icon: \n \n After this rollout, the app for iOS and Android will be called Microsoft 365 Copilot and will have this icon: \n \n Microsoft 365 accounts will be represented by the Microsoft logo: \n \n This change will be available by default. \n What you need to do to prepare: \n This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change and update relevant documentation. \n Learn more: The Microsoft 365 app transition to the Microsoft 365 Copilot app - Microsoft Support \n MC1003345 — New Microsoft Outlook for Windows and web: New \"None\" color category for Mail and Calendar \n Microsoft 365 Roadmap ID 469035 \n Coming soon to new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web: A None color category that users can apply to Mail and Calendar items. This update provides parity with classic Outlook and more flexibility and customization for users to categorize their emails and calendar events. By selecting the None option, users can choose to have items without a designated color, allowing for cleaner organization and more control over which items stand out visually. \n When this will happen: \n Targeted Release: We began rolling out late December 2024 and expect to complete by late February 2025. \n General Availability (Worldwide): We will begin rolling out late February 2025 and expect to complete by late March 2025. \n General Availability (GCC, GCC High, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. \n How this will affect your organization: \n Before this rollout, the None color category displayed as gray. \n After the rollout: \n \n Mail items will not have a color, which is the same behavior in classic Microsoft Outlook. \n Calendar items will retain the default category color related to the user's chosen theme, which is the same behavior as the previous version of Outlook. \n \n \n This change will be available by default. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. \n Learn more: Create and assign color categories in Outlook - Microsoft Support (will be updated before rollout) \n #newoutlookforwindows \n MC999441 — New Microsoft Outlook for Windows: Group messages as a conversation for emails within Outlook Data File \n Microsoft 365 Roadmap ID 479412 \n New Outlook for Windows users will be able to group messages as a conversation for emails within Outlook Data File (.pst or Personal Storage Table file). Future releases of new Outlook for Windows will expand the support for .pst file capabilities. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 and expect to complete by mid-March 2025. \n General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by early April 2025. \n General Availability (GCC): We will begin rolling out early April 2025 and expect to complete by early May 2025 \n How this will affect your organization: \n Outlook Data File (.pst) support is enabled by default in new Outlook for Windows. If you organization wants to block or limit Outlook Data File support, set the OutlookDataFile mailbox policy. Learn more: Set-OwaMailboxPolicy (ExchangePowerShell) \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with revised documentation. \n #newoutlookforwindows \n MC997580 — New Microsoft Outlook for Windows and web: Categorize individual emails in conversation view \n Microsoft 365 Roadmap ID 416450 \n Coming soon to new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web: Users can categorize individual emails in conversation view to enhance organization and tracking. \n When this will happen: \n Targeted Release: We began rolling out early January 2025 and expect to complete by late February 2025. \n General Availability (Worldwide): We will begin rolling out late February 2025 and expect to complete by late March 2025. \n General Availability (GCC, GCC High, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. \n How this will affect your organization: \n To use the conversation view, users can go to the Outlook ribbon and select View > Messages > Conversation > Group into conversations \n To categorize an individual email, a user must select the Group into conversations option. Then, in the list of emails, expand a conversation and right-click the individual email to be categorized, select the Categorize option, and choose the category (or categories). The selected category will display in the individual email and in the email header and the reading pane. \n Deleting a category from the message header or from the reading pane will remove the category applied to any individual emails in that conversation. \n This change will be available by default. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. \n Learn more: Use categories in Outlook - Microsoft Support \n #newoutlookforwindows \n MC997576 — Microsoft Outlook for iOS: Open the previous email with email auto-advance \n Microsoft 365 Roadmap ID 477362 \n Note: If your organization does not support iOS users, you can ignore this message. \n Coming soon to Microsoft Outlook for iOS: A new Open the Email Above setting to automatically open the message above the current one in the message list after performing actions like moving or deleting the current message. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by mid-March 2025 . \n How this will affect your organization: \n After this rollout, users can find the new setting in Outlook at Settings > Mail > Email Auto-advance > Open the Email Above. \n We will also remove the Move to the Next Email setting. \n Before the rollout: \n \n Go back to the Inbox \n Move to the Next Email \n \n After the rollout: \n \n Go Back to the Message List \n Open the Email Below \n Open the Email Above \n \n \n What you need to do to prepare: \n 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. \n Learn more: Email Auto-Advance Setting - Microsoft Support \n MC981624 — (Updated) Microsoft Outlook name change: \"Outlook (new)\" on Windows will change to \"Outlook\" \n Updated February 24, 2025: We have updated the rollout timeline and content. Thank you for your patience. \n We are delaying this change until mid-March to allow time to for customer experiencing issues with classic Outlook shortcuts to use this workaround. Some customers may still see classic Outlook shortcuts listed as just \"Outlook\", which could lead to confusion when new Outlook's installed name changes. The workaround for this issue is documented here. \n Coming soon: The installed name for new Microsoft Outlook for Windows will change from \"Outlook (new)\" to \"Outlook.\" \n This rollout comes after a change to the classic Outlook in version 2407, previously announced in MC803006 (Update) Outlook for Windows display name change (published June 2024, updated August 2024), which added \"(classic)\" to the installed name to differentiate the two apps. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). \n What you need to do to prepare: \n Outlook in the Windows Start menu. Left: Before the name change. Right: After the name change: \n This change will be on by default. This part of the app identity is not customizable for organizations. \n As always, we recommend planning your organization's migration to the new Outlook using the resources at https://aka.ms/newOutlookAdoption \n 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. \n #newoutlookforwindows \n MC960818 — (Updated) Microsoft Outlook for iOS/Android: New reporting buttons integrated with Microsoft Defender for Office 365 \n Microsoft 365 Roadmap ID 371383 \n Updated February 19, 2025: We have updated the content. Thank you for your patience. \n Coming soon to Microsoft Outlook for iOS/Android: New built-in report buttons in version > 4.2446 or later (android) and version > 4.2508 or later (iOS). Admins can control the appearance and behavior of these buttons that allow users to report emails as phishing / junk / not junk from the User Reported setting page 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. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We began rolling out in early December 2024 and expect to complete by late February 2025 (previously late January). \n How this will affect your organization: \n Information to keep in mind: \n \n Microsoft OWA (Outlook on the Web) and the new Microsoft Outlook for Windows have had this functionality since November 2022. This rollout to iOS/Android does not change or affect that functionality. \n Classic Microsoft Outlook for Windows client has had this functionality in current channel since August 2024. Learn more: MC841229(Updated) Classic Microsoft Outlook for Windows: New reporting buttons integrated with Microsoft Defender for Office 365 (published July 2024, updated October 2024). \n Microsoft Outlook for Mac released this functionality in September 2024. \n If you have turned off the reporting feature in the Microsoft 365 Defender User reported settings page or are using a third-party add-in, the report buttons in Outlook for Android/iOS won't be visible. \n The Microsoft reporting add-in (the Microsoft report message add-in and Microsoft phishing add-in) will be supported till further notice. The future goal is to have a consistent button reporting experience across all Outlook platforms. If you are using Microsoft reporting add-ins in Outlook for iOS/Android, your users will see two reporting experiences: one from the built-in Outlook buttons (added by this rollout) and one from the add-in. Both options will behave the same for users (except for the newly customizable pop-ups) and the reported messages will end up in the same place, causing minimal disruption. \n 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 your User reportedsettings. \n Like OWA and new Outlook for Windows, the built-in reporting button in Outlook for iOS/Android supports reporting from shared and delegate mailboxes. \n \n This change is available by default. \n What you need to do to prepare: \n 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. \n No action is required form you after this rollout because your current settings in the User reported settings page will not be changed. \n Learn more \n \n Report phishing and suspicious emails in Outlook for admins - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout) \n User reported settings - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout) \n \n MC946791 — (Updated) Microsoft Outlook for iOS and Android: Minimize the compose window to multitask in the Outlook app \n Microsoft 365 Roadmap ID 470304 \n Updated February 19, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for Microsoft Outlook for iOS and Android: Minimize draft emails and quickly access them again from the message list or calendar view. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out early January 2025 and expect to complete by late March 2025 (previously early February). \n How this will affect your organization: \n Outlook will help you compose emails more quickly and efficiently by allowing you to minimize your draft emails and quickly access them again from the message list or calendar view. This means that while composing an email you can easily get information you need from your calendar or other emails and easily get back into the draft you are working on without ever having to go to the Draft folder. \n To start, select the minimize icon in the upper right corner. \n This change will be on by default. \n What you need to do to prepare: \n This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change and update relevant documentation. \n MC926191 — (Updated) New Microsoft Outlook for Windows and web: Pin the Favorites section \n Microsoft 365 Roadmap ID 401341 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for new Outlook for Windows and web: Easily access your most-used folders by pinning a Favorites section at the top of the Outlook folder list on the left side of the screen. This feature streamlines navigation, ensuring your important folders are always in easy reach. Before this rollout, users can add a Favorites section that scrolls down when users navigate down the list. After this rollout, users can choose to keep the Favorites section pinned to the top of the list, and only the rest of the folders will scroll. \n When this will happen: \n Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by mid-December 2025. \n General Availability (Worldwide): We will begin rolling out mid-December 2024 and expect to complete by mid-January 2025. \n General Availability (GCC, GCC High, DoD): We will begin rolling out mid-January 2025 and expect to complete by early March 2025 (previously mid-February). \n How this will affect your organization: \n After the rollout, users can pin or unpin the Favorites section in two ways. \n In the Favorites section of the folder list (on the left of the screen), right-click the three-dot menu and select Pin favorites or Unpin favorites. \n On the Outlook ribbon, select the View tab > Folder pane > Favorites > select Pin favorites or Unpin favorites. \n This change will be available by default for users to choose to pin and unpin the Favorites section. \n What you need to do to prepare: \n Learn more: Use Favorites in Outlook - Microsoft Support (will be updated before rollout) \n 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. \n #newoutlookforwindows \n MC847877 — (Updated) Microsoft Outlook for iOS and Android: Choose fonts while composing \n Microsoft 365 Roadmap ID 409969 \n Updated February 13, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-November 2024 (previously mid-October) and expect to complete by late March 2025 (previously late January). \n How this will affect your organization: \n When this update rolls out, users will be able to select fonts to use in emails, signatures, automatic replies, and calendar invitations. \n What you need to do to prepare: \n You might want to notify your users about this new capability and update your training and documentation as appropriate. \n MC779851 — (Updated) To Do app opens in new Outlook for Windows \n Microsoft 365 Roadmap ID 375602 \n Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Use the Microsoft To Do app without leaving new Outlook for Windows. Clicking the To Do icon in the navigation bar will open the app inline and will no longer open it in a separate browser. \n When this will happen: \n Standard Release (GCC High, DoD): We will begin rolling out late February 2025 (previously late January) and expect to complete by late March 2025 (previously late February). \n How this will affect your organization: \n Users will notice a new entry point in classic Outlook for Windows if their active commercial Microsoft account has been granted access by their tenant administrator. No additional steps are required from the admin if the To Do app has already been enabled for the appropriate users in the existing To Do web or desktop applications. \n What you need to do to prepare: \n Ensure that the To Do app workload is enabled for your tenant. For details about ensuring access, see Set up Microsoft To Do. \n For more information about the To Do app, see Use To Do app to manage Tasks in Outlook. \n Exchange Online \n MC1015893 — The way to control EWS usage in Exchange Online is changing \n We are making a change to the behavior of the EWSEnabled tenant-wide switch in Exchange Online. \n When this will happen: \n This change will rollout worldwide, starting April 1, 2025 \n How this affects your organization: \n If you want to restrict the usage of EWS in your tenant, this change might affect you. The current behavior of the EWSEnabled flag is that it can be set at both the tenant (organization) level and the user (mailbox) level. Currently, when the flag is set to true at the user level, it takes precedence over the organization-level setting. If a setting is Null, it means the setting is not enforced at that level. If Org and user-level are both Null, the default behavior is to allow. This hierarchical structure means that if the organization-level flag is set to false, but the user-level flag is set to true, EWS requests from that user are still allowed. In summary: \n \n This approach has led to situations where it can be challenging for administrators to ensure uniform policy enforcement across their organization, particularly in large and complex environments. \n New Behavior \n To address these issues, we are altering the behavior so that EWS will only be allowed if both the organization-level and user-level EWSEnabled flags are true. Here's a simplified view of the new logic: \n \n In short, EWS will be permitted only if both the organization and user-level allow it. This change ensures that administrators have better control over EWS access and can enforce policies more consistently across their entire organization \n Next Steps: \n Please check the blog for additional information and ensure your per-user and tenant wide settings are correct before this change is made to your tenant. \n \n The way to control EWS usage in Exchange Online is changing \n \n MC886603 — (Updated) Reject multiple From addresses (P2 From headers) without a Sender header \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n We are proactively opting tenants out of the rollout that were detected as sending high volumes of emails exhibiting multiple From addresses without a Sender address header. These exempted senders will only be able to send emails exhibiting multiple From addresses without a Sender address header to recipients belonging to the same tenant as the sender. We will provide a subsequent update by the end of May 2025 (previously end of March) with an updated timeline for tenants that are opted out. \n Starting April 15, 2025 (previously February 3), we're going to start gradually dropping messages that have multiple From addresses (also known as P2 From headers) without a Sender header from being processed via Exchange Online. \n If we see significant traffic exhibiting multiple From addresses (P2 From headers) without a Sender header in your tenant in the month of September, we will send you a Message Center Post by October 15th alerting you and providing some sample message IDs. \n We are doing this to comply with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2) which mandates the Sender header to be present and contain a single address if the From header has more than one address. Noncompliance with this could be exploited by attackers, allowing them to impersonate a sender address by misleading the client into using the From header to determine the sender instead of the Sender header. \n When this will happen: \n April 15, 2025 (previously February 3) \n We are delaying the rollout start date from December to April 15, 2025 (previously February 3) in order to provide more time to customers for investigating messages exhibiting multiple P2 From Addresses without a Sender Address. \n Most of the traffic exhibiting multiple P2 From Addresses without a Sender Address will be inbound spam destined for your tenant sent by malicious spammers on the internet. \n Some customers are sending legitimate emails with this malformed header configuration. On October 15, we sent a targeted MC post to customers showing high volumes of messages exhibiting multiple P2 From Addresses without a Sender Address as they may be impacted by this change. \n For investigating if you will be impacted by this change, focus your investigation on messages sent using On Premises Inbound Connectors to Exchange Online. Authenticated mail submission is not impacted because submitting messages like this using those submissions are not allowed (Graph, Outlook clients, SMTP AUTH Client Submission). \n How this affects your organization: \n If email clients including devices and applications that you use to send messages, do so using multiple From addresses but without a Sender address header after April 15 2025 (previously December 1st), you will get an NDR error code 550 5.1.20 “Multiple From addresses are not allowed without Sender address’”. \n What you can do to prepare: \n When this change is in effect, if you need to send a message that has more than one email address in the From field, make sure that you have a single email address in the Sender header. \n If you expect this change to cause any issues for your organization, please share that feedback. \n Microsoft 365 \n MC980798 — (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) \n Microsoft 365 Roadmap ID 475046 \n Updated February 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Python in Excel allows you to bring the capabilities of Python directly into the Microsoft Excel grid. With this rollout, Python in Excel with standard compute will be generally available in Excel for Windows. \n When this will happen: \n General Availability (GCC): We will begin rolling out to Excel for Windows mid-March 2025 (previously mid-February) and expect to complete by early April 2025 (previously early March). \n After we complete the rollout to Excel for Windows, we will send a separate message with the timeline for rolling out this change to Microsoft Excel for the web and Microsoft Excel for Mac. \n How this will affect your organization: \n After this rollout, eligible users will be able to add Python formulas to their workbooks without any installation required. These Python formulas will be run by Excel in a secure container on the Microsoft Cloud with enterprise-level security and with standard compute. With this release, eligible Excel users with a Microsoft 365 Copilot license will also be able to use the Copilot in Excel with Python feature, enabling them to leverage the capabilities of AI and Python in Excel for deeper data analysis. \n Note: Some premium Python compute will be included with each user’s Microsoft 365 subscription each month, giving them limited access to faster calculation speeds. After they have used all of their premium compute, they can continue to use the Python in Excel feature with standard Python compute. To get more premium compute, admins will be able to purchase the Python in Excel add-on license for their users after it becomes available later this year for GCC. We will send a separate message with the timeline for the rollout of the Python in Excel add-on license. \n The Python in Excel feature will be enabled by default. \n What you need to do to prepare: \n To learn more about Python in Excel, please review the Python in Excel documentation. To learn more about data security: Data security and Python in Excel - Microsoft Support \n 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 relevant documentation. \n MC961557 — (Updated) Microsoft Search in Bing Deprecation \n Updated February 20, 2025: There are new details available regarding the Microsoft Search in Bing retirement. The FAQ is now available at Guidance for retiring Microsoft Search in Bing for your organization. \n Microsoft Search in Bing, the search experience for work and school available on Bing.com, is being deprecated. The last day of its availability is on March 31, 2025. This change is being made as we streamline search experiences and focus on enhancing core productivity tools. \n The Microsoft Edge for Business address bar and the Windows search box will continue to support work and school search, with some adjustments detailed below. \n Details of the Change \n After March 31, 2025, Microsoft Search in Bing will no longer be available, with changes as follows: \n \n Bing.com will no longer show work or school search results. Consequently, there will not be a dedicated page of work or school results and users’ work or school profiles will no longer appear on Bing.com. However, selecting the Work or School tab on Bing.com will redirect users to the new Microsoft Search experience on M365.cloud.microsoft (formerly Office.com and Microsoft365.com). \n Search boxes you’ve configured to point to Microsoft Search in Bing will no longer provide work or school results. \n The Edge for Business address bar and Windows search box will continue to support work and school search with some adjustments, including: \n \n o The Edge for Business address bar will no longer return work or school search results on a Bing.com page but will continue to provide suggested results in the address bar. In addition, the address bar will send users to work and school results on M365.cloud.microsoft rather than Bing.com. Users of the address bar can continue to find work-related documents, bookmarks, and people in suggested results—clicking on these suggestions takes users to work or school results on M365.cloud.microsoft. Users can also type \"work\" in the address bar, hit the tab key, then input their work- or school-related query to get results on a M365.cloud.microsoft page. Work and school search results will include documents, people, and bookmarks. Work search for documents will be available initially, with additional content types available as quickly as possible. \n o The Windows search box will no longer display organization branding nor the “Work” or “School” tab but will continue to support work and school search. Search for documents and people remains available. will be available initially, with additional content types available as quickly as possible. With these changes, users will see some UX changes in the Windows search box. \n As before, the core Microsoft Search experience remains accessible through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. \n \n Additionally, Entra ID sign-in will no longer be available on Bing.com, since work and school search is no longer available on Bing.com. \n \n An FAQ and further details are now available at Guidance for retiring Microsoft Search in Bing for your organization, which will be updated regularly. \n When will this happen: \n The last day of availability of Microsoft Search in Bing is March 31, 2025. \n How this affects your organization: \n For organizations using Microsoft Search in Bing, users will need to transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. \n Users who are accustomed to using the Edge for Business address bar and the Windows search box can continue to conduct work searches through these endpoints entry points, with the expectation that there will be some adjustment in these experiences after the deprecation date. (For details on changes, please refer to the FAQ: https://aka.ms/MSBFAQ.) \n Users who click on suggestions in the Edge for Business address bar or Windows search box may be redirected to Microsoft365.com before March 31, 2025. Also, as we begin testing the retirement experience, a small set of users may find before March 31 that Bing is intermittently unavailable as an entry point for work search. We recommend that you proactively inform your users of the change and direct them to M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. Adding M365.cloud.microsoft to their favorites or to the favorites bar in Edge for Business may be a helpful alternative pathway. \n What you can do to prepare: \n Customers should prepare to stop using Microsoft Search in Bing by March 31, 2025, and transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. We recommend that you inform users about the upcoming change and the alternatives available. \n Adding your preferred entry point from this set to favorites or favorites bar in Edge may be a helpful alternative pathway. Admins can easily set favorites in Edge for their organization, please see details here. \n Additionally, users can continue to use the Edge for Business address bar and the Windows search box, with some changes expected. Please educate users that they should now type \"work\" in the address bar, hit the tab key, then type in their work-related query to get work results on a M365.cloud.microsoft page. \n If your organization is using the AddressBarMicrosoftSearchInBingProviderEnabled policy today, you should update to the AddressBarWorkSearchResultsEnabled policy, if the policy is still needed. \n The new policy, AddressBarWorkSearchResultsEnabled, will be available starting in early March, with Edge for Business version 134 (ahead of the Microsoft Search in Bing deprecation). This allows admins to configure the display of work suggestions in the address bar. If the policy is enabled or not configured, users who are signed into Edge for Business with their Entra ID can view internal work-related suggestions, such as bookmarks, files, and people results powered by Microsoft 365, in the Edge for Business address bar suggestion dropdown. If the policy is disabled, Entra ID signed-in users will not see internal workplace results in the Microsoft Edge address bar suggestion dropdown. \n Admins who wish to set their own deprecation date prior to March 31, 2025, can turn off Microsoft Search in Bing by going to the Microsoft 365 admin center > Settings > Search & Intelligence. \n Regarding SafeSearch settings: \n \n If you had set the search experience for your organization to “School search,” SafeSearch was set to Strict by default. If you’d like to ensure that your users continue to have SafeSearch set to Strict after the Microsoft Search in Bing retirement, you can map www.bing.com to strict.bing.com at a network level. See Blocking adult content with SafeSearch or blocking Chatfor more details. \n \n Note: The search history feature for work or school search is changing along with the retirement of Microsoft Search in Bing. Details are not yet determined, but they will be added to the FAQ once they're finalized. \n MC923419 — (Updated) Microsoft Loop: Configure guest sharing for tenants with sensitivity labels \n Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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 MC736437 Microsoft 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. \n This message is related to MC923176 Microsoft Loop: Sensitivity labels at the container level (November 2024). \n 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out in early December 2024 (previously early November) and expect to complete by late February 2025 (previously early January). \n How this will affect your organization: \n 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 the People you choose option. Guest users cannot create workspaces. \n Admins: You can configure sharing of Loop workspaces, pages, and components with guests by enabling these policies in Microsoft SharePoint admin center > Policies > Sharing: \n \n Set the organization-level external sharing settings for to allow content to be shared with New and existing guestsor Existing guests. \n Enable the B2B collaboration with external guests. Learn more: Overview: B2B collaboration with external guests for your workforce - Microsoft Entra External ID | Microsoft Learn \n \n Learn more: \n \n Guest/external sharing: Overview of Loop workspaces storage and permissions | Microsoft Learn(will be updated before rollout) \n 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) \n \n What you need to do to prepare: \n 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. \n \n Documentation - Office 365 IP Address and URL web service \n February 28, 2025 - GCC January 30, 2025 - GCC High February 28, 2025 - DOD ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"230980","kudosSumWeight":0,"repliesCount":0,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXJJaVFDRg?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXRpV2h2ag?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDM","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXhYMWxtNQ?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDQ","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LUtWZEFJYw?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDU","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTdJeUd5UQ?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDY","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXgxeDVRdg?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDc","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXJuM1BLSA?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDg","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWFuMVJSMw?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDk","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXB1SXhmMw?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDEw","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXFqczdCMQ?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDEx","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWNxNlFubg?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDEy","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVMxSzNuWg?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDEz","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTBIVXhkbQ?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE0","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LUdEbGp2dA?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE1","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWtpYWF5eg?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE2","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVB3N09CVQ?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE3","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LUZ4RDhNcw?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE4","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTdEQnhCZQ?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE5","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTNqcDJkUw?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDIw","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LWNjOGZVdA?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDIx","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LTM3VGdUWQ?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDIy","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXdMZG91MQ?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDIz","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LW12RUV2Rw?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI0","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVpMQlgybA?revision=12\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI1","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LVhEeVRDeQ?revision=12\"}"}}],"totalCount":54,"pageInfo":{"__typename":"PageInfo","hasNextPage":true,"endCursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI1","hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":{"__typename":"UploadedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzk0OTY3LXJJaVFDRg?revision=12"},"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"BOTTOM","altText":""}},"Conversation:conversation:4384332":{"__typename":"Conversation","id":"conversation:4384332","topic":{"__typename":"BlogTopicMessage","uid":4384332},"lastPostingActivityTime":"2025-03-11T10:12:12.141-07:00","solved":false},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUlvZFpkag?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUlvZFpkag?revision=7","title":"DatacenterForBlog.png","associationType":"COVER","width":1000,"height":562,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLW5kd20wSA?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLW5kd20wSA?revision=7","title":"ReleaseNews.png","associationType":"BODY","width":1021,"height":130,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXEyZ0N3bw?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXEyZ0N3bw?revision=7","title":"Newsworthy.png","associationType":"BODY","width":1018,"height":132,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLThleEJuVQ?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLThleEJuVQ?revision=7","title":"References.png","associationType":"BODY","width":1017,"height":127,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWZGTkRqQQ?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWZGTkRqQQ?revision=7","title":"image.png","associationType":"BODY","width":1584,"height":1479,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUI1b0p2Tw?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUI1b0p2Tw?revision=7","title":"clipboard_image-3-1740600763486.png","associationType":"BODY","width":871,"height":327,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLW5pazVhVw?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLW5pazVhVw?revision=7","title":"ExpertiseForEnablement.png","associationType":"BODY","width":1027,"height":97,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTNEWGIzdQ?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTNEWGIzdQ?revision=7","title":"clipboard_image-1-1740693850317.jpeg","associationType":"BODY","width":772,"height":434,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLW5qUzEwZQ?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLW5qUzEwZQ?revision=7","title":"clipboard_image-2-1740693850334.png","associationType":"BODY","width":522,"height":348,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWhCZGVaMQ?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWhCZGVaMQ?revision=7","title":"clipboard_image-3-1740693850336.jpeg","associationType":"BODY","width":502,"height":351,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUczTzJEbA?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUczTzJEbA?revision=7","title":"clipboard_image-4-1740693850338.png","associationType":"BODY","width":806,"height":238,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUh6V1h5Nw?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUh6V1h5Nw?revision=7","title":"MessageCenter.png","associationType":"BODY","width":1023,"height":130,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLThjeTBydg?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLThjeTBydg?revision=7","title":"clipboard_image-40-1740695088095.png","associationType":"BODY","width":479,"height":285,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXZIVlZOTg?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXZIVlZOTg?revision=7","title":"clipboard_image-41-1740695088097.png","associationType":"BODY","width":480,"height":285,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWFlaVBjbg?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWFlaVBjbg?revision=7","title":"clipboard_image-42-1740695088101.png","associationType":"BODY","width":373,"height":713,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUw2TXhqVw?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUw2TXhqVw?revision=7","title":"clipboard_image-43-1740695088104.png","associationType":"BODY","width":481,"height":665,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTExblZGQw?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTExblZGQw?revision=7","title":"clipboard_image-44-1740695088107.png","associationType":"BODY","width":444,"height":845,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTh3TkxpeA?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTh3TkxpeA?revision=7","title":"clipboard_image-45-1740695088112.png","associationType":"BODY","width":479,"height":184,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUlNWXd1OQ?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUlNWXd1OQ?revision=7","title":"clipboard_image-46-1740695088117.png","associationType":"BODY","width":479,"height":184,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXAxclNjUg?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXAxclNjUg?revision=7","title":"clipboard_image-47-1740695088122.png","associationType":"BODY","width":479,"height":184,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUV2RTB1cg?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUV2RTB1cg?revision=7","title":"clipboard_image-48-1740695088123.png","associationType":"BODY","width":341,"height":626,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXJ6TTFWSw?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXJ6TTFWSw?revision=7","title":"clipboard_image-49-1740695088132.png","associationType":"BODY","width":479,"height":365,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXdsNjl3ag?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXdsNjl3ag?revision=7","title":"clipboard_image-50-1740695088135.png","associationType":"BODY","width":479,"height":271,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWpLQTEydg?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWpLQTEydg?revision=7","title":"clipboard_image-51-1740695088140.png","associationType":"BODY","width":481,"height":128,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTJOeFBmOA?revision=7\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTJOeFBmOA?revision=7","title":"clipboard_image-52-1740695088141.jpeg","associationType":"BODY","width":480,"height":287,"altText":""},"BlogTopicMessage:message:4384332":{"__typename":"BlogTopicMessage","subject":"February 2025 - Microsoft 365 US Public Sector Roadmap Newsletter","conversation":{"__ref":"Conversation:conversation:4384332"},"id":"message:4384332","revisionNum":7,"uid":4384332,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:505636"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":"","introduction":"New location sharing settings for emergency calls in Teams, SharePoint Server 2016 and 2019 end of support July 2026, New Microsoft Volume Indicator for Teams","metrics":{"__typename":"MessageMetrics","views":765},"postTime":"2025-03-11T10:12:12.141-07:00","lastPublishTime":"2025-03-11T10:12:12.141-07:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" \n SharePoint \n End of support for SharePoint Server 2016 and 2019 is scheduled for July 14, 2026. It's advisable to upgrade directly to SharePoint Server Subscription Edition \n Purview Information Protection \n New workload for Copilot in Content Explorer \n Microsoft 365 \n New deployments of Microsoft 365 desktop client apps to include new Outlook – GCC \n \n Unlocking Opportunities for Government Efficiency \n The U.S. Federal Government stands at a critical inflection point, offering an unprecedented opportunity to redefine how it fulfills its vital missions. As leaders seek to reduce costs and enhance efficiency, much of this can be accomplished through thoughtful technology modernization applied to mission delivery. \n Feb 21: Announcing M365 Community Days DC 2025 in Arlington \n We are thrilled to announce M365 Community Days DC, hosted by DC area community leaders at the prestigious Microsoft Innovation Hub, Arlington VA at Rosslyn. Join us February 21st, 2025, for this in-person event featuring speakers from across North America, and headlined by elected official Roxy Ndebumadu, Councilmember for the City of Bowie, MD. Mark your calendars for a day of learning, networking, and innovation! \n Where to Start with Microsoft Teams Apps in Gov Clouds \n 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. \n Microsoft 365 Government Adoption Resources \n Empowering US public sector organizations to transition to Microsoft 365 \n \n Microsoft 365 Roadmap This link is filtered to show GCC, GCC High and DOD: \n \n Stay on top of Microsoft 365 changes \n Here are a few ways that you can stay on top of the Office 365 updates in your organization. \n Microsoft Tech Community for Public Sector Your community for discussion surrounding the public sector, local and state governments. \n Microsoft 365 for US Government Service Descriptions \n \n Microsoft 365 Copilot (GCC) \n Microsoft Copilot Studio (GCC) \n Office 365 Platform (GCC, GCCH, DoD) \n Office 365 U.S. Government GCC endpoints \n Office 365 U.S. Government GCC High endpoints \n Office 365 U.S. Government DoD endpoints \n \n \n Microsoft Purview (GCC, GCCH, DoD) \n Enterprise Mobility & Security (GCC, GCCH, DoD) \n Microsoft Defender for Endpoint (GCC, GCCH, DoD) \n Microsoft Defender for Cloud Apps Security (GCC, GCCH, DoD) \n Microsoft Defender for Identity (GCC, GCCH, DoD) \n Azure Information Protection Premium \n \n \n Exchange Online (GCC, GCCH, DoD) \n SharePoint (GCC, GCCH, DoD) \n OneDrive (GCC, GCCH, DoD) \n Teams (GCC, GCCH, DoD) \n \n \n Office 365 Government (GCC, GCCH, DoD) \n Power Apps (GCC, GCCH, DoD) \n Power Automate US Government (GCC, GCCH, DoD) \n Power BI (GCC, GCCH, DoD) \n Planner (GCC, GCCH, DoD) \n Outlook Mobile (GCC, GCCH, DoD) \n Dynamics 365 US Government \n Microsoft Copilot Studio (GCC) \n WWindows 365 Government \n \n \n \n Get started with Microsoft 365 Copilot \n \n Public Sector Center of Expertise \n 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. \n \n Microsoft Teams for US Government Adoption Guide \n \n \n 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! \n SharePoint Online / OneDrive for Business \n MC996585 — Microsoft SharePoint: Updated document libraries \n Coming soon to Microsoft SharePoint: We will update the document library experience to improve its overall performance and enhance the functionality of Edit in grid view. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n After this rollout, users can expect these improvements: \n Pages in document libraries will load faster. \n Enhanced editing in grid view: \n \n Choice field editing: Select or change values in Choice columns in grid view. \n Person field and Group field editing: Assign users or groups to a file by selecting the Person field in grid view. \n Image field editing: Add or change images in the grid, like the similar feature in Microsoft Lists. \n \n Better scrolling with large libraries: Instead of going to the next page if there are more than 100 documents, users can scroll down and see everything. \n New commands and navigation in grid view: With these improvements, grid view includes several new commands and navigational options that previously were either missing or less intuitive: \n \n New commands: Create new items in grid view. \n Clickable document titles: Document and file titles in the grid are now clickable, making it easier to open items without leaving the grid. \n Folder navigation: Navigate in and out of folders from the grid view. \n \n Details pane in grid view: Open the details pane in grid view. \n Redesigned Properties pane and right-click menu: \n \n Properties pane as a dialog: When you click or modify an item’s details, the properties pane appears as a dialog box. \n Right-click context menu: Right-click any item in the grid and instantly see context-aware options such as Open, Edit, Share, or Delete. \n \n Grouped view support while editing in grid view: Edit items in grid view even when the library is grouped by specific columns (such as grouped by a content type, department, or project). \n Rating column improvements: If your document library includes a rating column (star ratings or “likes”), we improved the experience of updating and viewing these ratings. \n A SharePoint document library with an item’s menu expanded (in grid view): \n \n A SharePoint document library showing editing option in a field (in grid view): \n \n These changes will be available by default. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. \n Before rollout, we will update this post with revised documentation. \n MC989979 — Microsoft SharePoint: New preview mode for Pages and News posts \n Microsoft 365 Roadmap ID 473452 \n Coming soon to Microsoft SharePoint: The new Preview mode can be used to understand how Pages and News posts will appear on different device types when viewed by an audience. \n When this will happen: \n Targeted Release: We will begin rolling out late January 2025 and expect to complete by late February 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n After this rollout, a Preview button will display in the command bar while users are editing Pages and News posts in SharePoint. After selecting Preview, users can see what the page will look like in view mode for the audience. When previewing Pages, users can navigate between Desktop and Mobile device types. When previewing News posts, users can also choose to view the email version as Desktop or Mobile device types. \n This change will be available by default. \n What you need to do to prepare: \n You may want to notify users, update your user training, and prepare your help desk. \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. \n Before rollout, we will update this post with revised documentation. \n MC976819 — (Updated) Microsoft SharePoint: New Accessibility assistant tool for authoring Pages \n Microsoft 365 Roadmap ID 470603 \n Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for Microsoft SharePoint: A new Accessibility assistant tool to help content creators meet accessibility standards when authoring SharePoint Pages. This tool provides checks and brief guidance to help ensure pages are inclusive and accessible to a broad audience. This rollout reflects our ongoing commitment to fostering accessibility and inclusivity in SharePoint. \n When this will happen: \n Targeted Release: We will begin rolling out late January 2025 and expect to complete by late January 2025 (previously early February). \n General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out early February 2025 (previously mid-February) and expect to complete by mid-February 2025 (previously early March). \n How this will affect your organization: \n After this rollout, authors can initiate an accessibility test while editing a page. Authors can select the Accessibility assistant icon from the right vertical toolbar. The Accessibility assistant will support five web parts: Banner, Text, Image, Hero, and Quick Links. \n The Accessibility assistant identifies accessibility issues: \n \n The Accessibility assistant guides authors to address accessibility issues in the specific web part: \n \n The Accessibility assistant confirms the author has addressed all accessibility issues: \n \n What you need to do to prepare: \n Before rollout, we will update this post with revised documentation. \n This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update any relevant documentation. \n MC974358 — Microsoft SharePoint admin center: New \"App insights\" feature will be in Public Preview \n Microsoft 365 Roadmap ID 417481 \n Coming soon for Microsoft SharePoint Advanced Management (SAM): A new App insights feature will be available in the Microsoft SharePoint admin center for Public Preview. You can continue to manage this feature with Microsoft PowerShell cmdlets if desired. \n When this will happen: \n Public Preview: We will begin rolling out mid-January 2025 and expect to complete by late January 2025. \n General Availability (Worldwide): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n After this rollout, if you are part of SAM, you will be able to get insights in the SharePoint admin center for applications accessing SharePoint content. \n This feature will be available by default to SAM users. \n What you need to do to prepare: \n 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. \n Learn more: Generate App insights reports - SharePoint in Microsoft 365 | Microsoft Learn \n MC974354 — (Updated) Microsoft SharePoint Online: Re-imagined Hero with the new carousel layout in pages and news \n Microsoft 365 Roadmap ID 395214 \n Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. \n We are introducing a new Carousel layout to make the Hero web part more attractive. This new layout will feature a slideshow and a selection of new styles with imagery, bold text, and a call to action, creating a more engaging page experience. \n When this will happen: \n Targeted Release: We will start rolling out in mid-January 2025 and expect to complete by mid-January 2025 (previously late January). \n General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out mid-January 2025 (previously mid-February) and expect to complete by late January 2025 (previously late-February). \n How this will affect your organization: \n Adding a Hero web part to a page or news post has not changed. This update allows authors to create eye-catching carousel slides in any section type, with up to five slides in Carousel layout, enhancing user engagement and highlighting key content to establish page hierarchy. It offers three new styles and supports Stream videos to make the page more appealing. \n \n What you need to do to prepare: \n 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. \n MC973514 — SharePoint Pages Flexible Sections \n Microsoft 365 Roadmap ID 395213 \n Flexible sections are a new section type that allow authors to build pages without a strict column structure. Web parts can be dynamically resized and moved within flexible sections to create a fully customized section. Flexible sections unlock an endless number of design possibilities for sections. \n With the introduction of flexible sections, we have reimagined section templates that are located in the content pane toolbox. The new section templates will be powered by both flexible and column-based sections with example content. All sample content from these templates is placed onto the canvas when a section template is applied. \n The new flexible section type and section templates will be available in SharePoint and Viva Amplify. \n When this will happen: \n Targeted Release: We will begin rolling out late-January 2025 and expect to complete by mid-March 2025. \n General Availability (Production, GCC, GCC High, DOD): We will begin rolling out mid-March 2025 and expect to complete by late April 2025. \n How this will affect your organization: \n Users will see a new option when adding a section to a page, called “Flexible”. Within a flexible section, users can drag and drop web parts anywhere on the grid. Web parts will snap to the closest grid line when moved. \n Users can also resize web parts. Card-based web parts, such as Quick Links, People, or Hero, only have four different width options (full width, 1/3 canvas width, ½ canvas width, and 2/3 canvas width). These web parts can only be resized to one of the four options. \n Non-card-based web parts, such as Text, Image, and File & Media can be resized to any width. Web parts will snap to the closest gird line when being resized. \n Users can resize flexible sections manually, change the arrangement of overlapping web parts, multi-select web parts, and group web parts. \n Users can select or drag and drop a new section template from the content pane toolbox. After the template is added to the canvas, users can make adjustments to the web parts and section until ready to publish. \n What you need to do to prepare: \n You might want to notify users, update your user training, and prepare your help desk. \n MC973498 — Microsoft SharePoint: New \"Editorial card\" web part for Pages and News \n Microsoft 365 Roadmap ID 414524 \n Coming soon to Microsoft SharePoint: a new web part for Pages and New posts called the Editorial card. Unlike automated web parts like News and Events, the new Editorial card allows SharePoint designers to manually tailor the content presentation to their needs. \n When this will happen: \n Targeted Release: We will start rolling out late January 2025 and expect to complete by mid-February 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will start rolling out mid-February 2025 and expect to complete by late February 2025. \n How this will affect your organization: \n After this rollout, users can: \n \n Showcase content in an engaging card format with advanced background and content settings \n Configure content to suit varied author needs \n \n This change will be available to users by default. \n The Editorial card in the Web parts section of the Toolbox (right pane): \n \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with revised documentation. \n Examples of Editorial card content: \n \n MC947052 — (Updated) Microsoft SharePoint: Filter search results by \"Messages\" \n General Availability (Worldwide, GCC, GCC High, DoD): This rollout has completed \n Updated February 3, 2025: We have updated the rollout timeline below. Thank you for your patience. \n The same Messages search vertical at microsoft365.com will soon be available for organization-wide search in Microsoft SharePoint. Search verticals are tabs on the search result page that show results of a specific type or from select sources. For example, the Files vertical shows results classified as files and makes it easy for users who are looking to find documents. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): This rollout has completed. \n How this will affect your organization: \n This feature will be on by default. \n If you have disabled the Messages search vertical for microsoft365.com, the Messages search vertical will also be disabled in SharePoint. Learn more: Manage search verticals | Microsoft Learn \n What you need to do to prepare: \n 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. \n MC912181 — (Updated) Microsoft SharePoint: Add approvals to any document library \n Microsoft 365 Roadmap ID 420336 \n Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n Targeted Release: We will begin rolling out late January 2025 (previously early January) and expect to complete by early March 2025 (previously late January). \n General Availability (Worldwide, GCC): We will begin rolling out early March 2025 (early January) and expect to complete by late March 2025 (late January). \n How this will affect your organization: \n Before this rollout: Users are not able to add approvals to document libraries in SharePoint Online. \n After this rollout, users will be able to configure approvals by going to the Automate dropdown menu from the command bar in SharePoint Online document libraries and then selecting the Configure Approvals option 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 is Marked as final. \n 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 the Approvals app in Microsoft Teams or can be approved directly in the library in SharePoint. Once approved, the file metadata is updated. \n 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. \n Configure approvals in SharePoint Online: \n This feature is on by default. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before the rollout. \n Inform your users of the new Approvals functionality for libraries and lists. Share the support documentation Approvals in lists, which will be updated before this rollout begins to include library support. \n MC906496 — (Updated) Microsoft OneDrive and Microsoft SharePoint: New setting to disable presence in the file viewer \n Microsoft 365 Roadmap ID 419814 \n Updated January 8, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Administrators can now use the Microsoft SharePoint Online Management Shell to disable the user presence feature in the Microsoft OneDrive and SharePoint file viewer on a per-site collection basis. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late October 2024 and expect to complete by mid-January (previously December). \n How this will affect your organization: \n 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. \n 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 running Set-SPOSite -HidePeoplePreviewingFiles $true along with a list of valid site identifiers. Learn more: Set-SPOSite (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn. \n By default, this feature is available for admins to configure. \n What you need to do to prepare: \n 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. \n MC693865 — (Updated) SharePoint Add-In retirement in Microsoft 365 \n Updated February 1, 2025: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 14 months from now (April 2, 2026). \n Since the release of SharePoint Add-Ins in 2013, Microsoft has evolved SharePoint extensibility using SharePoint Framework (SPFx) enabling you to write applications that can be used in Microsoft SharePoint, Viva Connections and Microsoft Teams. With our continued investment in SharePoint Framework, Microsoft is retiring SharePoint Add-Ins. \n Key Points: \n \n Major: Retirement \n Timeline: \n \n o Starting July 1st, 2024, SharePoint Add-Ins cannot be installed from the public marketplace, also referred to as store by existing tenants. Installation from a private app catalog stays possible. \n o Starting November 1st, 2024, new tenants will not be able use SharePoint Add-Ins, regardless of their origin (public marketplace, private tenant catalog). \n o Starting April 2nd, 2026, Microsoft will remove the ability use SharePoint Add-Ins for existing tenants. \n \n Action: Review and assess impact \n \n How this will affect your organization: \n If your organization still uses SharePoint Add-Ins, they will no longer function after April 2nd, 2026. We recommend customers to port their customizations to SharePoint Framework (SPFx) and ask their solution vendors for updated solutions. \n What you need to do to prepare: \n You will want to notify your Add-In users and developers. Update your user training and prepare your help desk. \n For admins \n \n Use the Microsoft 365 Assessment toolto scan your tenants for SharePoint Add-In usage. \n Disable SharePoint Add-Inson your tenant using SharePoint Online Management Shell \n Review the guidance for migrating from SharePoint Add-Ins to SharePoint Framework. \n There will not be an option to extend SharePoint Add-Ins beyond April 2nd 2026. \n \n New: How to disable SharePoint Add-Ins on your tenant \n Admins can disable SharePoint Add-Ins with the Set-SPOTenant SharePoint Management Shell PowerShell command. \n Connect-SPOService -Url https://<tenant>-admin.sharepoint.com \n Set-SPOTenant -IsSharePointAddInsDisabled $true \n After SharePoint Add-Ins are disabled, users will not be able to add SharePoint Add-Ins to their sites, and admins cannot add new SharePoint Add-Ins to the tenant and site collection app catalogs. SharePoint Add-Ins already added to sites will stay available and can still be used by the site's users. \n New: SharePoint Add-Ins will not be available from the public marketplace \n After July 1, 2024, users browsing the public marketplace (AppSource) will see SharePoint Add-In, but if they select Get it now, a message will explain that SharePoint Add-Ins are retired and cannot be added. If you still require a specific SharePoint Add-In, contact the Add-In creator to understand the possible options. \n Learn more \n \n Support update for the retirement of SharePoint Add-Insin Microsoft 365. \n \n MC693863 — (Updated) Azure ACS retirement in Microsoft 365 \n Updated February 1, 2025: This update serves as a reminder that Azure ACS in Microsoft 365 will retire and stop working in 14 months from now (April 2, 2026). \n Since the first use of Azure Access Control Services (ACS) by SharePoint in 2013, Microsoft has evolved the authorization and authentication options for SharePoint Online via Microsoft Entra ID (a.k.a. Azure AD). Using Microsoft Entra ID as auth platform for your SharePoint Online customizations will provide your applications the most secure, compliant and future proof model. With our continued investment in Microsoft Entra ID, Microsoft is retiring the use of Azure ACS as auth platform for SharePoint Online. \n Key Points: \n \n Major: Retirement \n Timeline: \n \n o Starting November 1st, 2024, new tenants will not be able use Azure ACS. \n o Starting April 2, 2026, Microsoft will remove the ability use SharePoint ACS for existing tenants. \n \n Action: Review and assess impact \n \n How this will affect your organization: \n If your organization still uses Azure ACS to grant custom developed or third party applications access to SharePoint Online, they will no longer have access after April 2nd, 2026. We recommend customers to update their customizations to use Microsoft Entra ID and ask their solution vendors to do the same. \n What you need to do to prepare: \n You will want to notify your Azure ACS users and developers. Update your user training and prepare your help desk. \n For admins \n \n Use the Microsoft 365 Assessment toolto scan your tenants for Azure ACS usage. \n Review the guidance for migrating from Azure ACS to Microsoft Entra ID. \n There will not be an option to extend Azure ACS usage for SharePoint Online beyond April 2nd 2026. \n \n Learn more \n \n Support update for the retirement of Azure ACS for SharePoint Onlinein Microsoft 365. \n \n MC542767 — (Updated) SharePoint 2013 workflow retirement \n Updated February 1, 2025: This update serves as a reminder that SharePoint 2013 workflow will retire and stop working in 14 months from now (April 2, 2026). \n Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only encompass SharePoint, but all the productivity services you use with Microsoft 365 and beyond. With the continued investment in Power Automate as the universal solution to workflow, Microsoft is retiring SharePoint 2013 workflows. \n When this will happen: \n \n Starting April 2nd, 2024, SharePoint 2013 workflows will be turned off for any newly created tenants. \n Starting April 2nd, 2026, Microsoft will remove the ability to run, or create and execute SharePoint 2013 workflows for existing tenants. \n \n How this will affect your organization: \n If your organization still uses SharePoint 2013 workflows, they will no longer function after April 2nd, 2026. We recommend customers to move to Power Automate or other supported solutions. \n What you need to do to prepare: \n You will want to notify your users, workflow developers and site owners. Update your user training and prepare your help desk. \n For admins \n \n Use the Microsoft 365 Assessment tool to scan your tenants for legacy workflow usage. \n Review Guidance: Migrate from classic workflows to Power Automate flows in SharePoint \n Review the Power Automate resourcesas a solution to legacy workflows. \n \n Note: There will not be an option to extend SharePoint 2013 workflow beyond April 2nd 2026. \n Learn more: \n \n Detailed support articlewith additional resources. \n \n Microsoft Copilot \n MC981631 — Microsoft Teams: Microsoft 365 Copilot in Teams meetings will be generally available to GCC \n Microsoft 365 Roadmap ID 476072 \n Coming soon for Microsoft Teams: We’re excited to announce that Microsoft 365 Copilot in Teams meetings will soon be available. This message pertains to Teams for Windows desktop, Teams for the web, Teams for Mac desktop, and Teams for iOS/Android. \n A Microsoft 365 Copilot license is required to use this feature. \n When this will happen: \n General Availability (GCC): We will begin rolling out early February 2025 and expect to complete by mid-February 2025. \n How this will affect your organization: \n This rollout marks an important step in delivering Copilot in Teams meeting capabilities for your organization including: \n \n Ask Copilot questions about the meeting in real-time and after meeting ends \n Use out-of-the-box prompts for common tasks, such as generating a meeting recap, listing action items, capturing unresolved questions, or listing main ideas discussed in the meeting \n Use Copilot during the meeting without retaining a transcript after the meeting \n Generate Copilot responses based on both the spoken transcript and the written meeting chat \n \n Here are key details to help you prepare and understand what to expect: \n \n Teams admin center updates: Over the coming weeks, you may notice Copilot controls appearing in your Teams admin center. These controls will allow you to get familiar with how you will be able to manage Copilot in Teams in anticipation of the full rollout. \n Functionality launch: We will start rolling out Copilot for Teams meetings to the Teams application in early February, but the Teams admin center controls may become visible earlier. \n The Copilot in Teams setting in the Teams admin center will be ON (requiring transcript) by default. \n \n Copilot in Teams will be available to users by default. \n We appreciate your patience and understanding as we finalize this deployment. Our team is committed to ensuring a smooth experience for both admins and users. \n What you need to do to prepare: \n 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 and admins about this change and update any relevant documentation. \n Learn more \n \n Manage Microsoft 365 Copilot in Teams meetings and events - Microsoft Teams | Microsoft Learn \n Use Copilot in Microsoft Teams meetings - Microsoft Support \n \n Microsoft Viva \n MC989956 — Microsoft Viva: Edit and schedule polls in Viva Engage \n Microsoft 365 Roadmap ID 467251 \n Starting in February 2025, customers with the Microsoft Viva suite or Microsoft Viva Communications and Communities premium licenses will see an option to schedule or edit a poll prior to publication. \n When this will happen: \n General Availability (Worldwide): We will begin rolling out in mid-February 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n Before this rollout, users did not have a way to schedule polls in Engage. \n After this rollout, premium-licensed users will have a new option in the publisher to schedule a poll post in the same location as other post types (discussion, question, praise, article). From their drafts, users can publish or edit a poll. \n Users may also edit a poll prior to publication from their drafts. Users cannot edit poll posts, including voting options, after publication. \n This feature will be available by default. \n The new option to schedule or edit a poll prior to publication: \n \n What you need to do to prepare: \n This rollout will happen automatically by the specified date. There is no action for admins to enable or opt-in to this feature. 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. \n Learn more: Write and schedule posts, articles, and announcements in Viva Engage - Microsoft Support \n MC979826 — (Updated) Microsoft Viva Connections: Update to app name \n Updated January 24, 2025: We have updated the content. Thank you for your patience. \n We are renaming the Viva Connections app to Connections. This change is intended to ensure the app name fits better within Microsoft Teams, preventing it from being truncated. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously mid-February). \n How this will affect your organization: \n If you have already customized the Viva Connections app name in the Microsoft Teams app store, your customizations will remain unchanged. \n This update is available by default. \n What you need to do to prepare: \n 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. \n Microsoft Teams \n MC996588 — Microsoft Teams: Adding and editing external contacts on Teams phone devices \n Microsoft 365 Roadmap ID 476485 \n A new feature allows users to add and edit external contacts using the lightweight People app on Microsoft Teams phone devices. With this capability, you will be able to manage and interact with contacts outside of your organization on Teams phone devices. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n General Availability (GCC High): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. \n General Availability (DoD): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. \n How this will affect your organization: \n Users will now be able to add and edit external contacts from Teams phone devices. \n To add an external contact: \n \n Click Create new contact from the People app. \n Add in the details of the external contact, and then click Save. \n \n \n What you need to do to prepare: \n Please ensure that your Teams phone devices are updated with the latest People app to get access to this new feature. This feature will only be available with the latest application update. \n MC996587 — Microsoft Teams Voice: Link Voice apps without using resource accounts \n We are excited to introduce a new feature in the Voice section of the Microsoft Teams admin center that allows admins to create linked Voice apps without needing to associate them with a resource account. This update simplifies the process of managing Auto attendant (AA) and Call queue (CQ) services. \n When this will happen: \n General Availability (Production): Available now. \n How this will affect your organization: \n After this rollout, in the Redirection options, you can select Voice app or Resource account to link AAs and CQs. Before this rollout, the Voice app option lets you link AAs and CQs using the resource account associated with them. If you prefer to use a resource account, you can still select Resource account: \n Admins can use the using the Voice app option to create linked Voice apps without associating them with a resource account: \n \n For example, this feature is useful when you want to create a call flow where multiple AAs and CQs are linked together. If you have an AA that needs to transfer calls to different departments, you can link it directly to multiple CQs without needing a separate resource account for each CQ. \n This new feature will be available by default. \n What you need to do to prepare: \n 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 relevant documentation. \n Admins should review your existing AA and CQ setups and update them to take advantage of the new feature. Existing configurations will continue to work as before under the Resource account option. \n Learn more \n \n Manage resource accounts for service numbers - Microsoft Teams | Microsoft Learn(will be updated before rollout) \n The Nested Auto attendants and Call queuessection in Plan for Teams Auto attendants and Call queues - Microsoft Teams | Microsoft Learn \n \n MC994288 — Microsoft Teams: Speed dial on line keys for touch phone devices \n Microsoft 365 Roadmap ID 476486 \n A new feature allows you to configure custom contacts and speed dial on the line key of touch phone devices certified for Microsoft Teams. It enables you to swiftly access frequently dialed numbers and contacts, incorporating one-touch/press dialing and easy management of contact lists on touch devices. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 and expect to complete late March 2025. \n General Availability (GCC High): We will begin rolling out mid-May 2025 and expect to complete late May 2025. \n General Availability (DoD): We will begin rolling out mid-August 2025 and expect to complete late August 2025. \n How this will affect your organization: \n Users will have the ability to use line keys on touch phone devices. \n To assign line keys, tap on pre-defined placeholders and choose a contact to be added as a speed dial. Once you add a speed dial, you can make outgoing calls through one-touch/press on those line keys. \n \n What you need to do to prepare: \n Please ensure that your Teams phone devices are updated with the latest Microsoft Teams application. This feature will only be available with the latest application update. Lastly, for this feature to work, you will need to assign line keys on the device. \n MC994287 — Microsoft Teams: Webinars will be generally available (DoD) \n Microsoft 365 Roadmap ID 475279 \n Webinars in Microsoft Teams will soon be generally available. After this rollout, users will be able to schedule webinars with internal audiences and use capabilities such as creating an event page, sending attendee registration automated emails, and more. \n This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams for the web. Teams for iOS/Android users can attend webinars but not schedule them. \n When this will happen: \n General Availability (DoD): We will begin rolling out late March 2025 and expect to complete by mid-April 2025. \n How this will affect your organization: \n This change will be available by default. \n What you need to do to prepare: \n 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. \n User documentation: Get started with Microsoft Teams webinars - Microsoft Support \n MC993227 — Microsoft Teams: Native Bluetooth call controls using hands-free protocol for multiple peripheral devices \n Microsoft 365 Roadmap ID 475853 \n Coming soon for Microsoft Teams: When you have several peripheral devices connected to Teams, the one you use to answer a call will temporarily become the main device that will sync with Teams when using the device's buttons. After the call, the original device selected in Teams settings will take over again as the main device. After this rollout, users can use multiple native Bluetooth devices can be confident that call controls will function correctly with all of them. \n This message applies to Teams for Windows desktop. \n When this will happen: \n Targeted Release: We will begin rolling out early March 2025 and expect to complete by late March 2025. \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-March 2025 and expect to complete by mid-April 2025. \n How this will affect your organization: \n After this rollout, users will be able to switch between their connected peripheral devices when answering a call without manually changing the selected device in Teams settings. \n This change will be available by default. \n What you need to do to prepare: \n 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. \n Learn more: Phones and Devices for Microsoft Teams - Microsoft Teams | Microsoft Learn \n Before rollout, we will update this post with new documentation \n MC993226 — Microsoft Teams: New location sharing settings for emergency calls and other features \n Microsoft Teams will soon have a new location sharing setting that will allow users to grant location access to specific features. This change will affect emergency dynamic policy and the network bandwidth policy. \n This message applies to Teams for Windows desktop (version 24H2 or greater) and Teams for Mac desktop. VDI clients will not be supported at this time. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 and expect to complete by mid-February 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 and expect to complete by early March 2025. \n How this will affect your organization: \n Before this rollout: Location access was governed exclusively at the operating system level. With this update, location consent will also be required from users at the individual application level. As a result, users gain more granular control over which specific application features can access their location. \n After this rollout, Teams users can grant location access to certain Teams features. The setting for IT insights for admins feature are in Teams Settings > Privacy > Location. The setting for the Emergency calls feature is in the user's device's location settings. The user can find a link to their device's location settings in Teams Settings > Privacy > Location: \n \n If a user consented to location access before the rollout, the user will be prompted to confirm their selection in this new popup that will display after the next Teams version update. If a user has not previously consented, they will not see the popup and can adjust their preferences in Settings. \n \n What you need to do to prepare: \n NOTE: After this rollout, dynamic emergency calling may not work as intended unless users allow location detection at the operating system level and app level. This dynamic emergency calling issue includes scenarios where admins have configured a network site for their users (location must be enabled by the user). To ensure emergency calls are properly routed to the nearest public safety answering point (PSAP), please advise your users to accept the new location requests from Teams. This also applies to users who may have consented to location access before the rollout. \n You can communicate this requirement by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that end users have location turned on is crucial for proper functioning of emergency calls and their safety. Learn more about sending a custom message: Manage emergency calling policies in Microsoft Teams - Microsoft Teams | Microsoft Learn \n To continue managing video and media settings with the network roaming policy, users must enable Insights for IT admins in Teams Settings > Privacy > Location > Insights for IT admins. \n Learn more about the changes to location services and privacy policies \n \n Windows location service and privacy - Microsoft Support \n Enable location sharing - Microsoft Support(will be updated before rollout) \n \n 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. Please notify your users and admins about this change and update any relevant documentation. \n MC989975 — Microsoft Teams: Occupancy status on Teams panels \n Microsoft 365 Roadmap ID 474441 \n Before this rollout, Microsoft Teams panels indicate a room availability based only on reservation data. After this rollout, Teams panels can smartly utilize signals from Teams Rooms devices and occupancy sensors paired with Teams panels to indicate when a room is in use, so users are not surprised to find an available room is actually occupied. This feature will be supported for accounts with a license for Microsoft Teams Rooms Pro or Microsoft Teams Shared Devices. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out late March 2025 and expect to complete by early April 2025. \n How this will affect your organization: \n After this rollout, this feature will be set to on by default, so the current experience will change. The room is in use when the room is not currently reserved and a user is in a call, presenting, whiteboarding, or casting with a Teams Rooms device, or the room is detected as occupied through a paired occupancy sensor. \n When the room is in use, the panel's LED will adjust to the color selected by the admin for the busy state. In addition, the panel's home screen will reflect that the room is occupied. Note: The room can still be reserved on the device itself, through Microsoft Outlook, or through Microsoft Teams. \n \n If the device is paired with a Microsoft Teams Rooms on Android, after a user reserves the occupied room from the device, a message will appear on the room display to let the user inside of the room know that the room has been reserved and to exit. This notification will be off by default, and the admin will need to enable it after pairing the device. \n An admin can choose to turn off these features in Teams admin settings > Device settings > Occupied state. The two settings are Allow occupied state and Allow booking notifications. If Allow occupied state is turned off, the booking notifications also will be turned off. \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with revised documentation. \n MC989974 — Microsoft Teams: New microphone volume indicator for users \n Microsoft 365 Roadmap ID 468274 \n Coming soon for Microsoft Teams: A new Mic volume indicator on the user bar in Teams meetings. This feature will provide users with real-time visual feedback on their audio levels in the meeting, eliminating the need to ask, “Can you hear me?” This feature is designed to minimize interruptions as well as enhance user confidence and meeting effectiveness. \n This feature applies to Teams on Windows desktop and Mac desktop. \n When this will happen: \n Targeted Release: We will begin rolling out in early March 2025 and expect to complete by mid-March 2025. \n General Availability (Worldwide, GCC): We will begin rolling out in late March 2025 and expect to complete by late April 2025. \n General Availability (GCC High): We will begin rolling out in mid-May 2025 and expect to complete by mid-June 2025. \n General Availability (DoD): We will begin rolling out in late June 2025 and expect to complete by early August 2025. \n How this will affect your organization: \n This feature will be available to users by default and has no admin policy. \n Users can select the Mic icon and review the Microphone section of the menu to find out more about their audio levels in the meeting: \n \n What you need to do to prepare: \n 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. \n Learn more: Muting and unmuting your mic in Microsoft Teams - Microsoft Support \n MC985484 — Microsoft Teams: Additional work information in people search results \n Multi-tenant organization (MTO) users will be able to see additional work information in people search results. With this feature, MTO users will be able to see the company name and department name of a user in people search results, helping users to make sure they are communicating with the right people. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early February 2025 and expect to complete by late February 2025. \n How this will affect your organization: \n Tenant admins who have MTO enabled will be able to toggle this feature on and off in the Teams admin center. \n Toggle behavior: \n \n This toggle will be off by default. \n Turning on the toggle will enable the ability to see company name and department name in results. \n Turning off the toggle will disable the ability to see company name and department name in results. \n \n Instructions to toggle: \n \n Navigate to the Teams admin center (TAC). \n Navigate to the Teams Client Config page. \n Using the Enable Extended Work Info in People Search toggle: \n \n \n Switch the toggle to on to enable the ability to see company name and department name in results. \n \n \n Switch the toggle to off to disable the ability to see company name and department name in results. \n \n For more information, see Set up a multitenant org in Microsoft 365. \n What you need to do to prepare: \n Tenant admins will need to complete cross-tenant synchronization and sync the company name field in order to take advantage of this feature. \n For more information, see Synchronize users in multitenant organizations in Microsoft 365. \n MC981629 — Microsoft Teams: Updates to make meeting transcripts more accurate and reliable \n Microsoft 365 Roadmap ID 471426 \n Coming soon to Microsoft Teams: Updates to make meeting transcripts more accurate and reliable. These improvements will also enhance the quality of live captions in Teams, Microsoft Copilot in Teams, and intelligent meeting recap for Microsoft Teams Premium users and users with a Copilot license, ensuring more accurate outputs and enhancing the overall experience of each feature. \n This message applies to Teams for Windows desktop and Teams for Mac desktop. \n When this will happen: \n Targeted Release: We will begin rolling out mid-February 2025 and expect to complete by late February 2025. \n General Availability (Worldwide, GCC): We will begin rolling out late February 2025 and expect to complete by early March 2025. \n General Availability (GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by late March 2025. \n How this will affect your organization: \n Key changes in this rollout: \n Setting the meeting spoken language up front: Before starting features like Recording, Transcription, or Copilot that generate transcripts, users will be prompted to set the spoken language. Whether users enable these features manually or through Meeting options, this change ensures the transcription system starts with the correct language configuration. \n \n Limiting who can change the spoken language for a meeting: When transcription is enabled, either on its own or as part of Recording or Copilot, only the meeting organizer, co-organizer, or the person who started the transcript will be allowed to change the spoken language. This ensures consistency and prevents issues caused by mismatched language settings. If transcription is not enabled, any meeting participant can change the spoken language. \n \n Simplifying language settings: Language settings and caption customization options are on separate screens, instead of overwhelming users with all options in a single screen. \n \n Identifying language mismatches: A Language mismatch detected notification will appear onscreen if the spoken language does not match the settings. Users can quickly resolve mismatches by confirming the system’s language suggestion directly from the notification, avoiding the need to navigate through settings. \n \n This change will be available to users by default. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or after 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. \n Before rollout, we will update this post with revised documentation. \n MC980799 — Microsoft Teams: Allow presenters to moderate Q&A \n Microsoft 365 Roadmap ID 469492 \n Coming soon for Microsoft Teams: Organizers of town halls and webinars will be able to select and assign presenters to also moderate the Q&A, allowing them to manage and publish questions asked during the event. This feature lets organizers make changes to the group of moderators at any time (before or during the event), and it is available to all users organizing a town hall or webinar. \n This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out late February 2025 and expect to complete by early March 2025. \n How this will affect your organization: \n This feature is supported for presenters with Microsoft Azure Active Directory (AAD) IDs. Presenters using consumer domains (such as live.com or gmail.com) are not supported. \n Meeting organizers can enable this feature in Meeting options while setting up the event or during the event. \n This feature will be available by default. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or after 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. \n Learn more: Q&A in Microsoft Teams meetings - Microsoft Support (will be updated before rollout) \n MC979828 — Microsoft Teams: Cross-cloud collaboration in Virtualized Desktop Infrastructure \n Microsoft 365 Roadmap ID 471434 \n Microsoft Teams Virtualized Desktop Infrastructure (VDI) users can join meetings with people in other Microsoft 365 cloud environments (e.g. a user in GCC High joining a meeting in Worldwide, GCC, or DoD environments) through three options: \n \n Authenticated access via cross-cloud meeting connection. \n Authenticated access using a guest account. \n Anonymous access. \n \n These scenarios require the new Slimcore-based optimization, since WebRTC-based optimization does not support meetings across different cloud environments. \n For more information on the new optimization, see New VDI solution for Teams. \n When this will happen: \n General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out late March 2025 and expect to complete by late April 2025. \n How this will affect your organization: \n For users who are already optimized with SlimCore in their VDI environments, after this feature is rolled out, cross-cloud anonymous and cross-cloud authenticated meetings will now open in Teams desktop client, and users with Guest Access in another cloud will be able to switch tenants via their Account picker in the Teams Settings UI. \n What you need to do to prepare: \n To access this new feature, enable the new VDI optimization based on SlimCore. \n MC978932 — Large Events: End Session for Attendees and Return Presenters to Green Room \n Microsoft 365 Roadmap ID 470432 \n Organizers and presenters can now end the session with this new \"End Event\" button for town halls, webinars, and structured meetings. After selecting this button, attendees will see a message on stage stating that the session has concluded, and presenters will return to the Green Room. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 and expect to complete by mid-February 2025. \n General Availability (Worldwide): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. \n General Availability (GCC): We will begin rolling out late February 2025 and expect to complete by early March 2025. \n General Availability (GCC High and DoD): We will begin rolling out late March 2025 and expect to complete by early April 2025. \n How this will affect your organization: \n When users join a town hall, webinar, or structured meeting with Green Room turned ON, they will now see the \"End event\" or \"End meeting\" button: \n \n What you need to do to prepare: \n This feature change will be available once it is fully released in your tenant. \n MC975308 — (Updated) Microsoft Teams: iPad Multi-window support \n Microsoft 365 Roadmap ID 467246 \n Updated January 17, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Teams now supports multiple windows on iPad. With this 'multi-window' feature, users can easily manage different Teams windows side-by-side, increasing productivity and flexibility. \n When this will happen: \n General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out mid-March 2025 (previously early February) and expect to complete by late March 2025 (previously late February). \n How this will affect your organization: \n Apple's \"split view\" capability allows iPad users to have multiple applications and windows open side-by-side. Starting in February, Teams will now support the ability for there to be multiple Teams windows open at once. This makes it easier for users to attend a meeting and have their chat open on the other side or use Stage Manager to move windows to external displays. \n This feature is available by default when users update the Teams app on iPad. \n What you need to do to prepare: \n 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. \n MC975304 — Microsoft Teams: The Approvals app is generally available (DoD) \n Microsoft 365 Roadmap ID 473448 \n The Approvals app in Microsoft Teams is a way to streamline requests and processes with a team or partners. Users will be able to create new approvals, view pending approvals, and see previous ones in one place. \n Users with an F3 license or above can take advantage of the Approvals app in Teams: \n \n Office 365 Government G1 \n Office 365 Government G3 \n Office 365 Government G5 \n Office 365 Government F3 \n \n If you do not have users that meet the licensing requirement, you may safely ignore this message. \n This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. \n When this will happen: \n General Availability (DoD): We will begin rolling out early February 2025 and expect to complete by mid-February 2025. \n How this will affect your organization: \n Approvals is a native Teams application that lets users easily create, manage, and share approvals from a hub for teamwork. These approvals are triggered directly with the Power Automate infrastructure and do not require a flow with an approvals action. \n Users see all of their approvals in the hub, including the approvals that have been completed. Approvals show up across all of a user's systems, including Power Automate, SharePoint, and Microsoft Dynamics 365: \n \n What you need to do to prepare: \n The Approvals app is on by default if your tenant has enabled Microsoft Power Automate. \n As an admin, you can manage the Approvals app in the Teams admin center on the Approvals app page, including customizing which users can access the app with permission policies. Currently, all approvals are created in your organization's default environment. \n The Approvals app page in the Teams admin center: \n \n Learn more \n \n Approvals in Microsoft Teams - Power Automate | Microsoft Learn \n Manage the Approvals app in Microsoft Teams - Microsoft Teams | Microsoft Learn \n What is Approvals? - Microsoft Support \n \n 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. \n In October 2027, we will remove the option to specify the need for passcodes. This change will ensure that all meetings are consistently secured with passcodes. This final step will simplify the meeting creation process and provide an additional layer of protection for users. We will remove the isPasscodeRequired property on the joinMeetingIdSettings resource of the Microsoft Graph online meetings API. \n MC974361 — (Updated) Microsoft Teams: Edit your display name in meetings \n Microsoft 365 Roadmap ID 122934 \n Updated January 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n In Microsoft Teams, while in a live meeting, participants will soon be able to edit their display name for the duration of the meeting. This name change is for the meeting duration only and does not affect a participant's original name on their People card. \n This feature is available for participants using the Teams desktop and web apps for both Windows and Mac. \n When this will happen: \n Targeted Release: We will begin rolling out early March 2025 (previously February) and expect to complete by mid-March 2025 (previously mid-February). \n General Availability (Worldwide, GCC): We will begin rolling out early April 2025 (previously mid-March) and expect to complete by mid-April 2025 (previously early April). \n General Availability (GCC High, DoD): We will begin rolling out late April 2025 (previously early April) and expect to complete by mid-May 2025 (previously mid-April). \n How this will affect your organization: \n The feature is off by default for all tenants. Admins can turn it on for their organization in the Teams admin center for all or selected tenant members. These members can then enable the feature in their private scheduled meetings. \n If turned on for the tenant, a meeting organizer can turn the feature on for their meeting in Meeting options > Let people edit their display name. The feature is OFF by default in Meeting options and has to be enabled by meeting organizer. \n If turned on for a meeting, participants can join the meeting and then select People at the top of the screen to edit their own display names in the Participants panel. \n Example: Daniela Mandera can change her name in a meeting to Daniela M. (Before rollout, we will update this post with revised user documentation for changing the name.) \n Participants who have edited their names will have an (edited) label next to their name in the meeting screens. \n *Original People card names will display in some meeting features such as calendar invites, the list of people invited to meetings, group chat rosters, and so on. \n Permanent meeting artifacts (such as the attendance report and transcriptions) will not reflect name changes. \n \n What you need to do to prepare: \n You can turn this feature on for your tenant users to allow the capability in the meetings they organize. You might want to notify your users about this new feature and update your training and documentation as appropriate. \n MC973513 — Simplify UX flow to enable Together Mode \n Microsoft 365 Roadmap ID 470427 \n Together mode will get a new simplified flow which will take the user from the beginning to the end through the steps of setting up the scene, assigning the seats and applying for everyone in the call in a transparent and easy-to-understand way. \n When this will happen: \n Targeted Release: We will begin rolling out mid-February 2025 and expect to complete by early March 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early March 2025 and expect to complete by mid-March 2025. \n How this will affect your organization: \n With the improved experience, the function itself does not change but there will be more transparency thanks to the icons on the meeting toolbar for an easy access for each next step in the familiar Together mode flow. \n \n What you need to do to prepare: \n You may consider updating your training and documentation as appropriate. \n MC973502 — Microsoft Teams: New \"Tag mentions\" filter for the Activity feed \n Microsoft 365 Roadmap ID 470598 \n Coming soon to Microsoft Teams: Users will have a new Tag mentions filter in the Activity feed to see their tag mentions in their chat and channel messages. The existing @Mentions filter allows users to catch up quickly on personal mentions. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 and expect to complete by early February 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. \n How this will affect your organization: \n This change will be available by default. There are no tenant level settings. Defaults will not change. \n \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or rafter the rollout. You may want to notify your users about this change and update any relevant documentation. \n User documentation: Explore the Activity feed in Microsoft Teams - Microsoft Support (will be updated before rollout) \n MC973497 — Microsoft Teams: The Updates app is generally available (GCC) \n Coming soon to Microsoft Teams: Users can access the Updates app to streamline their daily reporting workflow and increase collaboration efficiency. \n Users can use the Updates app to set up a daily or weekly reporting form and workflow to collect regular updates from others. \n When this will happen: \n General Availability (GCC): We will begin rolling out early January 2025 and expect to complete by late January 2025. \n How this will affect your organization: \n Learn more about how to manage the app: Manage the Updates app for your organization - Microsoft Teams | Microsoft Learn. \n This change is available by default. \n What you need to do to prepare: \n This rollout will happen automatically with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. \n User documentation: Get started in Updates - Microsoft Support \n MC971032 — (Updated) Microsoft Teams: New recording policies for town halls and webinars \n Microsoft 365 Roadmap ID 473887 \n Updated January 24, 2025: We have updated the content. Thank you for your patience. \n Coming soon to Microsoft Teams: New admin policies in the Teams admin center and Microsoft PowerShell that govern the recording behavior for town halls and webinars. Before this rollout, the same policies control the recording behavior for town halls, webinars, and meetings. After this rollout, separate recording policies for town halls and webinars will be available to more finely control event behavior. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early March 2025 (previously mid-February) and expect to complete by mid-March 2025 (previously late February). \n How this will affect your organization: \n This change will be available by default. \n What you need to do to prepare: \n Before the rollout, we encourage you to use PowerShell commands to update the default values of the recording policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values. \n Examples of PowerShell commands to set the town hall or webinar recording policy: \n Set-CsTeamsEventsPolicy -Identity Global -RecordingForTownhall Enabled \n Set-CsTeamsEventsPolicy -Identity Global -RecordingForWebinar Enabled \n 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. \n Learn more: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn \n MC971031 — (Updated) Microsoft Teams: New transcription policies for town halls and webinars \n Microsoft 365 Roadmap ID 473886 \n Updated January 24, 2025: We have updated the content. Thank you for your patience. \n Before this rollout, for a Microsoft Teams town hall or webinar, the transcription behavior respects the current Teams meeting transcription policies. After this rollout, new transcription policies will be available for town halls and webinars to allow finer control over transcriptions. The policies may be changed in the Teams admin center or with Microsoft PowerShell commands. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early March 2025 (previously mid-February) and expect to complete by mid-March 2025 (previously late February). \n How this will affect your organization: \n These new transcription policies for webinars and town halls will determine whether transcription is allowed for a town hall or webinar. Town halls and webinars will no longer respect the Teams Meeting transcription policies. \n The new policies will be available by default for admins to configure. \n What you need to do to prepare: \n Before the rollout, we encourage you to use PowerShell commands to update the default values of the transcription policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values. \n Examples of PowerShell commands to set the town hall or webinar policy: \n Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForTownhall Enabled \n Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForWebinar Enabled \n 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. \n Learn more: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn \n MC960811 — (Updated) Microsoft Teams: Enhanced captions for Teams Rooms on Windows \n Microsoft 365 Roadmap ID 423089 \n Updated January 24, 2025: We have updated the content. Thank you for your patience. \n Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that captions will soon support additional languages and translation capabilities. This enhancement aims to improve meeting accessibility and inclusivity for non-English speaking users using Teams Rooms on Windows. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). \n General Availability (GCC High): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). \n General Availability (DoD): We will begin rolling out early Mary 2025 (previously early April) and expect to complete by mid-May 2025 (previously mid-April). \n How this will affect your organization: \n Before the rollout: Captions in Teams Rooms on Windows only support the English language, which limits usability for non-English speaking users as the captions will result in gibberish if the actual spoken language in the meeting is non-English. There is also no way for admins to set default caption settings. \n After the rollout \n Additional languages: Users can select from a list of supported languages for captions, ensuring that captions are accurate and meaningful for non-English speakers. Users can change the meeting spoken language directly from Teams Rooms devices by selecting More > Captions > Meeting spoken language. \n Real-time translation: Users can translate the meeting's spoken language if the room account has a Teams Rooms Pro license or if the meeting organizer has a Teams Premium license, allowing for real-time translation of captions. Users can translate captions by selecting More > Captions > Translation language. \n Admin controls: For room accounts with Teams Rooms Pro license, admins can change system defaults, turn on captions by default for calls and meetings, and turn off filtering of profanity in captions and transcripts as necessary with these XML settings: \n \n <CaptionsDefault>true</CaptionsDefault> \n <FilterProfaneWords>false</FilterProfaneWords> \n \n As an admin, you can allow or prevent users (including room accounts) from having access to this feature by configuring calling and meeting policies in the Teams admin center. Learn more: Enable call captions - Microsoft Teams | Microsoft Learn and Manage live captions - Microsoft Teams | Microsoft Learn. \n This feature is available by default. \n What you need to do to prepare: \n After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and settings, 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. \n MC960809 — (Updated) Microsoft Teams: Live transcription for Teams Rooms on Windows \n Microsoft 365 Roadmap ID 423088 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that users can soon start and stop transcription as well as view the meeting transcript directly from Teams Rooms on Windows devices. This feature requires a Teams Rooms Pro license. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February) \n General Availability (GCC High): We will begin rolling out mid-April 2025 (previously mid-March) and expect to complete by late April 2025 (previously late March). \n General Availability (DoD): We will begin rolling out early May 2025 (previously early April) and expect to complete by mid-May (previously mid-April). \n How this will affect your organization: \n Before the rollout: When joining a meeting on Teams Rooms on Windows, users must also join the meeting on a companion device to start transcription. Also, even when transcription has been started, users can't view the transcript from the front of room display. \n After the rollout: Users can select More > Record and transcribe > Start transcription or Stop transcription directly from the Teams Rooms on Windows device. Start/stop transcription is supported in any meeting where a participant belongs to the same tenant as the organizer. \n When users transcribe a Meet now or Whiteboard session initiated from a Teams Rooms on Windows device, users must ensure that they invite themselves to the meeting so that they can access the transcript after the meeting through the meeting chat on their Teams desktop or mobile app. \n After transcription is started, users can show/hide the transcript panel on the front of room display in any meeting layout: \n \n Select More> Record and transcribe > toggle On/Off Show transcript. \n Select View> Front row > open the left/right panel dropdown > select/unselect Transcript. \n \n Users can also set the meeting spoken language, translate the transcript, and choose to show the original language and translated language side by side, ensuring accurate and meaningful transcription. \n 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 transcribing meetings with a policy in the Teams admin center. Learn more: Manage transcription for Teams meetings | Microsoft Learn. \n NOTE: Both the meeting organizer and the transcription initiator (room account) need to have permissions to transcribe the meeting. If the meeting organizer uses Meeting options to remove the room account's permissions, the start/stop transcription button will not be available. \n For room accounts with a Teams Rooms Pro license, you have the option to turn off the filtering of profanity in transcripts using this XML setting: <FilterProfaneWords>false</FilterProfaneWords> \n Start/stop transcription is not supported in these scenarios: \n \n Teams calls including P2P, group, and PSTN calls \n External and cross-tenant Teams meetings and calls \n Third-party meetings and calls including Direct Guest Join and SIP \n \n What you need to do to prepare: \n After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and setting, 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. \n MC956699 — (Updated) Microsoft Teams: Forward messages with app cards \n Microsoft 365 Roadmap ID 469506 \n Updated January 17, 2025: We have updated the rollout timeline below. Thank you for your patience. \n We are introducing the ability to forward app cards. With the addition of app card forwarding, users now have a new way to share app cards across chats. To forward a message containing an app card, simply navigate to the More Actions menu of any message containing an app card and select forward. From here, the forward message dialog will populate, which provides users with a preview of the message being forwarded, including the app card. \n Please note: Forwarding of bot cards is excluded from this release. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 (previously early January) and expect to complete by mid-February 2025 (previously mid-January). \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously late January) and expect to complete by early March 2025 (previously early February). \n How this will affect your organization: \n Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained app cards. With this improvement, this restriction does not exist. \n What you need to do to prepare: \n Users must have the latest Microsoft Teams build to receive these updates. You may want to notify your users about this change and update any relevant documentation as appropriate. \n MC952888 — Microsoft Teams: Pop out Chat, Copilot, and Notes panes in meetings \n Microsoft 365 Roadmap ID 421607 \n Coming soon: Users will be able to pop out the side panes for Notes, Chat, and Microsoft Copilot panes in Microsoft Teams meetings \n Note: The Copilot pane is only available in Worldwide environments with a Microsoft 365 Copilot license. \n When this will happen: \n Targeted Release: We will begin rolling out mid-January 2025 and expect to complete by early February 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early February 2025 and expect to complete by late February 2025. \n How this will affect your organization: \n After the rollout, users will see a pop-out icon at the top of their Notes, Chat, and Copilot side panes in Teams meetings. This change will be on by default. \n When users select the icon, the pane will pop out into a separate window that the user can resize and drag to their desired position, based on their screen setup and their productivity goals for the meeting. Users can view multiple meeting features at the same time, so they don’t miss the chat while they are monitoring meeting notes. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before the rollout. Please notify your users about this change and update any relevant training documentation. \n MC950898 — (Updated) Microsoft Teams: Forwarding loop components \n Microsoft 365 Roadmap ID 469507 \n Updated January 7, 2025: We have updated the rollout timeline below. Thank you for your patience. \n There is now the ability to forward loop components in Microsoft Teams. With the addition of loop component forwarding, users have a new way to share loop components across chats and channels. To forward a message containing a loop component, simply navigate to the more actions menu of any message containing a loop component and select forward. From there, the forward this message dialog will populate, which provides users with a preview of the message being forwarded, including the loop component. In this view, users will be able to give permissions to recipients of the loop component to ensure all recipients have access to the content. \n When this will happen: \n Targeted Release: We will begin rolling out in early January 2025 and expect to complete by mid-January 2025. \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late January 2025 and expect to complete by early April 2025 (previously early February). \n How this will affect your organization: \n Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained a loop component. With this improvement, no such restriction exists. \n This update is available by default. \n For additional information, see Forward a message in a Teams chat - Microsoft Support. \n What you need to do to prepare: \n 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. \n MC946818 — (Updated) Microsoft Teams: Updates to Gallery in Teams Rooms on Windows \n Microsoft 365 Roadmap ID 468277 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams Rooms on Windows, the updated Gallery view introduces these changes to enhance your meeting experience: \n \n All participants will appear in consistent tile sizes \n By default, video participants have priority and appear first on the meeting stage by default (audio participants appear on the side or bottom of the screen) \n Ability to disable priority on video participants to create a mix of audio participants and video participants in the Gallery \n Optimized view of up to 25 participants on a single display and up to 50 participants on dual displays \n Preview video is part of the Gallery, appearing next to the rest of the participants \n Ability to hide the preview video across all layouts \n \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February). \n How this will affect your organization: \n The updated Galleryprovides a unified meeting experience across both Teams Rooms and desktop. A more consistent and predictable layout can drive meeting efficiency and visibility for remote participants in hybrid meeting scenarios. \n In 1:1 meetings, the preview video will be positioned at the bottom right, overlapping the other participant. \n In group meetings, the preview video will be on the last available tile in the Gallery, next to the rest of the participants. \n Admins can use two new settings to adjust the default view: \n \n Prioritize vide0;< PrioritizeVideoParticipantsGallery> – Default value is True. The default experience will show video participants on the main stage with audio participants on the side or bottom rail. If you would like to display all audio and video participants mixed in the Gallery, change the value to False. \n Hide me <HideMeForAllLayout> – Default value is False. If you would like to hide preview video across all layouts in Teams Rooms on Windows, change the value to True. \n \n In-room users can adjust these settings on the console during a meeting, if desired. \n Lastly, when another Teams Room joins the meeting, the video of the room automatically enlarges if there are more than two in-room users, providing a clearer view and better connection, and so users can focus on the person speaking. \n These changes will be available by default. \n What you need to do to prepare: \n Please notify your users about this change and update any training documentation, as appropriate. \n 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. \n Learn more \n \n Remotely manage Microsoft Teams Rooms device settings - Microsoft Teams | Microsoft Learn(will be updated before rollout) \n Microsoft Teams Rooms (Windows) - Microsoft Support(will be updated before rollout) \n \n MC939927 — (Updated) Microsoft Teams Premium: Decorate your background \n Microsoft 365 Roadmap ID 419811 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n We will not release this feature to DoD at this moment. We are sorry for any inconvenience. We will share DoD timeline when available. \n Microsoft Teams Premium users will be able to use the \"Decorate your background\" generative background effect in the GCC, GCC High, and DoD environments, leveraging gen-AI to augment real-life surroundings. It creates a personalized atmosphere for video calls. \n When this will happen: \n General Availability (GCC): We will begin rolling out in early March 2025 (previously early February) and expect to complete rollout by mid-March 2025 (previously late February). \n General Availability (GCC High): We will begin rolling out in mid-March 2025 (previously mid-February) and expect to complete rollout by late March 2025 (previously late February). \n General Availability (DoD): We will communicate via Message center when we are ready to proceed. \n How this will affect your organization: \n “Decorate your background” transforms meeting backgrounds by blending with a user’s real-life surrounding, creating a personalized atmosphere for video calls. It is available to Teams Premium users, and it is supported on Microsoft Windows and MacOS client now. There is not admin policy to disable it. \n Users can access this feature in the following ways: \n \n Before a meeting starts on the pre-join screen, select Effects and Avatars> Video effects > Decorate button. This will allow you to start generating new backgrounds. \n During a meeting, select an animated background by clicking video flyout > More Video Effects and Setting > Decorate. \n \n What you need to do to prepare: \n 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. \n MC932488 — (Updated) Microsoft Teams: New DVR capabilities for town halls (desktop and web) \n Microsoft 365 Roadmap ID 422804 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for Microsoft Teams: New DVR (digital video recording) functionality for all town halls. This new feature will allow town hall attendees on Windows desktop or the web to interact with a live streaming town hall in the same way they would interact with recorded content. DVR functionality in the town hall enables event attendees to pause and move forward or back in a town hall, navigate to any previous timestamp, and other abilities, making it more convenient to interact with a town hall more and easier to digest the content being presented. This feature is available for Teams town halls from all organizers, regardless of the license assigned to the organizer. \n When this will happen: \n Targeted Release: We will begin rolling out early March 2025 (previously early February) and expect to complete by mid-March 2025 (previously mid-February). \n General Availability (Worldwide): We will begin rolling out mid-March 2025 (previously mid-February) and expect to complete by late March (previously late February). \n General Availability (GCC): We will begin rolling out late March 2025 (previously late February) and expect to complete by early April 2025 (previously early March) \n How this will affect your organization: \n After this rollout, the DVR controls will appear when attendees hover their mouse over the content being presented in the town hall. Attendees can: \n \n Pause, play, and skip 10 seconds forward or backward \n Control the volume of the content with the volume control \n Jump to any point in time, starting from the beginning of the event \n Catch up with the content and join the live event by selecting the Watch Livebutton next to the volume control \n \n The DVR controls are at the bottom of the Teams window when the Q&A page is open on the right side. \n We are committed to continuously improving the Microsoft Teams experience and are excited to bring this new capability to our customers. \n This feature will be available by default. \n What you need to do to prepare: \n 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. \n Learn more: Plan for Teams town halls - Microsoft Teams | Microsoft Learn (will be updated before rollout) \n MC929034 — (Updated) Microsoft Teams: Best practices configuration dashboard in Teams admin center \n Microsoft 365 Roadmap ID 421185 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams: With the Best practice configurations monitoring dashboard in the Teams admin center, Teams admins will be able to monitor the conformance of your tenant to the Microsoft recommended best practices for an optimal collaboration experience on Teams. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). \n How this will affect your organization: \n Ensuring the quality and reliability of user's collaboration experience using Teams is crucial (specially the meeting-related experiences). Microsoft recommends best practices to ensure that organizations have an optimal environment setup for collaboration. \n The Best Practice Configurations monitoring dashboard will assist admins in understanding their tenant’s non-conformance with these best practices, the overall impact, and how to comply with these recommendations. \n You'll find the Best practice configurations dashboard in the Meetings section of the Teams admin center. In this release, we’ll monitor and highlight non-conformance in three key areas: \n \n Update out-of-date client versions \n Enable the right ports and protocols \n Implement split tunnelling for VPNs \n \n If a location does not adhere to these best practices, it will be highlighted on the dashboard. A widget on the main dashboard will also spotlight non-conforming practices. Also, a list of subnets/IP addresses will be displayed by city, showing the extent of non-conformance for each location. This list can be exported to share with relevant teams, and recommendations for addressing these issues will be available on the same page. \n As these issues are resolved, the trend of non-conforming locations will be tracked to help monitor progress. \n This new dashboard will be available by default. \n What you need to do to prepare: \n Administrators do not need to do anything to prepare for these changes. They will take effect automatically. \n You may want to notify your admins about this change and update any relevant documentation. \n Before rollout, we will update this post with revised documentation. \n MC923415 — (Updated) Microsoft Teams: Virtualized Desktop Infrastructure status indicator \n Microsoft 365 Roadmap ID 423472 \n Updated December 10, 2024: We have updated the rollout timeline below. Thank you for your patience. \n This new feature is designed to be a visual indicator of the optimization status in Microsoft Teams for Virtualized Desktop Infrastructure (VDI) users. \n Users in VDI used to rely on the ellipsis (...) > Settings > About menu to display the optimization status for their session (AVD Media Optimized, Citrix HDX Media Optimized, VMware Media Optimized). \n 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. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 (previously mid-January) and expect to complete by mid-February 2025 (previously late January). \n General Availability (Worldwide, GCC): We will begin rolling out mid-February 2025 (previously late January) and expect to complete by late February 2025 (previously early February). \n How this will affect your organization: \n 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. \n This feature is available by default. \n What you need to do to prepare: \n 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. \n MC920179 — (Updated) Microsoft Teams: The new streamlined Chat and Channels experience \n Microsoft 365 Roadmap ID 415249 \n Updated January 17, 2025: We have updated the content. Thank you for your patience. \n Thank you for your engagement with the new chat and channels experience in Teams. \n The new chat and channels experience has been in Public Preview and Targeted Release since November 2024 and was targeted for General Availability starting in late January 2025. Based on requests from customers to have additional time to prepare their organizations for the change, we will be postponing the rollout to General Availability from January to a later date. \n The GA rollout date is updated to starting late March 2025. \n 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. \n For more details and screenshots, refer to Microsoft Teams announces out a new chat and channels experience | Microsoft 365 Blog \n This message applies to Teams on Windows desktops, Mac desktops, the web, and iOS and Android devices. \n This message excludes Education tenants. We will send a future post with an update on the plan for Education tenants. \n When this will happen: \n Public Preview / Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by mid-November 2024. \n General Availability (Worldwide): We will begin rolling out late March 2025 (previously late January) and expect to complete by early April 2025 (previously early February). \n General Availability (GCC, GCC High, DoD): We will begin rolling out mid-June 2025 (previously mid-April) and expect to complete by late June 2025 (previously late April). \n How this will affect your organization: \n Before this rollout, users have separate Chat and Teams views (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. \n The new experience brings chat, teams, and channels into one place, in Chat, so users can easily navigate between all conversations without switching between contexts. Users start in the combined Chat view but can opt to keep chat separate from teams and channels like before. \n In the Chat view, users will see these sections (in order): \n \n Favorites containing any previously pinned chats and channels \n Chats sorted by most recent \n Teams and channels, organized in same order as in the Teams view \n \n Also, users can create custom sections to organize projects and topics that can include individual, group, and meeting chats, as well as channels. \n New filters for Unread, Chat, Channels, Meetings and more help users focus on relevant conversation in their list. Filters persist until turned off. \n The new @mention view gathers all personal @mentions into one interactive list. Users can quickly access messages with @mentions across chats, channels, and meetings. \n Use /go to: Quickly navigate to your frequently used conversation across your chat and channels with a new keyboard shortcut Ctrl+G (Cmd+G on Mac). \n Customizing the experience \n Users can tailor their chat and channels experience in Teams Settings. Users can choose to keep chat, teams, and channels combined in Chat (default) or switch to separate Chat and Teams views. In the combined Chat view, message previews are off by default to simplify the list. Users can turn on message previews in Settings. \n When using the separate Chat and Teams views, users can still use the new filters and the @mentions view to triage and organize topics with custom sections. \n Starting the new experience \n 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. \n 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. \n 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. \n What you need to do to prepare: \n 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 page The new Microsoft Teams chat and channels experience before rollout begins. \n For admins who opt in to emails for recommended Microsoft 365 training, an email for users will summarize the update when released. \n MC920084 — (Updated) Microsoft Teams: Usage reports for bookable desks \n Microsoft 365 Roadmap ID 421604 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. This message applies to tenants with Teams Rooms Pro or Teams Shared device licenses. \n When this will happen: \n General Availability (Worldwide): We will begin rolling out late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). \n General Availability (GCC): We will begin rolling out late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). \n How this will affect your organization: \n The Teams Rooms Pro Management portal will have a new tab under Reports called Desk usage. Desk pools that have at least one peripheral associated will appear under this tab. \n 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. \n Admins will also be able to select a specific desk pool to review specific metrics, such as a peak utilization matrix. \n This change will be available by default. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before the 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. \n Reports for desk pools will be in public preview and available with no licensing requirement until July 2025. More information on licensing requirements will be provided prior to that date. \n Learn more: Setting up Bookable Desks in Microsoft Teams - Microsoft Teams | Microsoft Learn (will be updated soon after rollout) \n MC918570 — (Updated) Microsoft Teams: Custom name on Teams panels \n Microsoft 365 Roadmap ID 417153 \n Updated January 14, 2025: We have updated the content. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early January (previously early December) and expect to complete by mid-January 2025 (previously mid-January). \n How this will affect your organization: \n 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. \n To change the display name on the panel, navigate to Teams Rooms Pro Management Portal > Planning > Inventory and then click 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. \n 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. \n 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. \n 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. \n What you need to do to prepare: \n This rollout will happen by the specified date with no admin action required. You may want to update any relevant documentation as appropriate. Please update to 1449/1.0.97.2024122401 to use this feature. \n MC916866 — (Updated) Microsoft Teams: Shifts Graph APIs in beta moved to production (v1.0) \n Microsoft 365 Roadmap ID 422813 \n Updated December 20, 2024: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (Worldwide and GCC): We will begin rolling out mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). \n How this will affect your organization: \n You may continue using the API endpoints in beta. However, we recommend migrating to the production endpoints. \n To refer to a list of all production (v1.0) APIs, go to the following page and navigate to Teamwork and communications > Shift management: Microsoft Graph REST API v1.0 endpoint reference - Microsoft Graph v1.0 | Microsoft Learn \n This update is available by default. \n What you need to do to prepare: \n 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. \n MC912709 — (Updated) Microsoft Teams: Bookable desks and BYOD rooms supported in GCC \n Updated February 4, 2025: We have updated the content. \n 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. \n 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. \n 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. \n When this will happen: \n General Availability (GCC): We will begin rolling out late January 2025 (previously early January) and expect to complete by early February 2025 (previously mid-January). \n How this will affect your organization: \n Before this rollout, admins are not able to set up bookable desks and BYOD rooms in their tenant. \n 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. \n To enable bookable desks and BYOD, please see our desk and room guides. We also have a user support article for desks and rooms. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before the rollout \n 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. \n Learn more \n \n Setting up Bookable Desks in Microsoft Teams - Microsoft Teams | Microsoft Learn \n Bring Your Own Device Rooms in Pro Management Portal - Microsoft Teams | Microsoft Learn \n For users: First things to know about bookable desks in Microsoft Teams - Microsoft Supportand Use shared display mode in meeting rooms - Microsoft Support \n \n MC912707 — (Updated) Microsoft Teams: New policy for voice and face enrollment will default to \"On\" (configure now) \n Microsoft 365 Roadmap ID 413708 \n Updated January 31, 2025: We have updated the rollout timeline below. Thank you for your patience. \n A new csTeamsAIPolicy policy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-March 2025 (previously mid-February) 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 enrollment will 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. \n 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. \n When this will happen: \n The new Microsoft PowerShell cmdlets are available now for admins to configure, to ensure a smooth transition. \n 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-March 2025 (previously mid-February) and is expected to be fully in effect by late March 2025 (previously late February). \n How this will affect your organization: \n Before this rollout, the current policy csTeamsMeetingPolicy has a single setting, EnrollUserOverride, that allows the administrator to enable or disable the enrollment of both face and voice profile of users. \n After this rollout, the new csTeamsAIPolicy will replace the existing enrollment setting in csTeamsMeetingPolicy. The new csTeamsAIPolicy has two settings, EnrollFace and EnrollVoice, that will be set to Enabled by default. \n What you need to do to prepare: \n 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. \n 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: \n \n Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn \n Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn \n \n Learn more: Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn \n If your organization prefers to disable voice and face enrollments, review and update your settings before mid-February 2025. \n Important: The EnrollUserOverride setting can be assigned globally, directly to users, or to groups in PowerShell. \n Admins must ensure that changes are applied consistently across all these locations to avoid unintended configurations. \n MC908117 — (Updated) Microsoft Teams: Swap screens on Teams Rooms on Android \n Microsoft 365 Roadmap ID 415243 \n Updated January 28, 2025: We have updated the content. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by late November 2024. \n General Availability (GCC High): We will begin rolling out early December 2024 and expect to complete by mid-February 2025 (previously mid-January). \n How this will affect your organization: \n Before this rollout \n \n 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. \n 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. \n \n After this rollout \n \n 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. \n 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. \n 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 \n \n NOTE: If you are deploying Teams Rooms on Android devices with dual displays, be aware that dual display mode must be explicitly enabled in the configuration profile. By default, the dual display setting is OFF, which means that using an existing configuration profile (designed for single-display devices by default) may inadvertently disable dual display mode for your existing dual display rooms. To avoid this, you must create and maintain a separate configuration profile for any devices that require dual display support. \n This feature will be off by default and available for admins to configure. \n What you need to do to prepare: \n 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. \n This rollout will happen automatically by the specified date with no admin action required before the rollout. \n MC907108 — (Updated) Microsoft Teams: Admin email support for \"Report a problem\" on Teams Rooms on Android \n Microsoft 365 Roadmap ID 415247 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Teams Rooms on Android: As an admin, you can configure an email address for receiving issues submitted by users through the Report a problem feature 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by late November 2024. \n General Availability (GCCH): We will begin rolling out early December 2024 and expect to complete by mid-February 2025 (previously mid-January ). \n How this will affect your organization: \n 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. \n After the rollout \n When you configure an email address in Teams admin settings > General > Logs and feedback, the Report a problem option on Teams Rooms on Android devices will be enabled, and any feedback submitted by room users using Report a problem will 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. \n Users can access Report a problem from the Help button on the home screen or the More button in meetings. Report a problem can also be accessed on the pre-sign in screens. \n 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. \n 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, see Collect Teams Android device logs | Microsoft Learn. \n This feature will be off by default and available for admins to configure. \n 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. \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before the rollout. \n 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. \n MC906501 — (Updated) Microsoft Teams: Net Promoter Score survey on Teams Rooms on Android \n Microsoft 365 Roadmap ID 415245 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by late November 2024. \n General Availability (GCCH): We will begin rolling out early December 2024 and expect to complete by mid-February 2025 (previously mid-January). \n How this will affect your organization: \n Before this rollout: NPS surveys do not appear on Android devices. \n After this rollout \n 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. \n 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. \n As an admin, you can prevent room accounts from getting NPS surveys with Microsoft PowerShell. Learn more at Manage feedback policies in Microsoft Teams - Microsoft Teams | Microsoft Learn. \n What you need to do to prepare: \n 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. \n MC903632 — (Updated) Microsoft Teams Rooms on Android: 3x3 video gallery on dual displays \n Microsoft 365 Roadmap ID 415239 \n Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience \n 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by early November 2024. \n General Availability (GCC High): We will begin rolling out late November 2024 and expect to complete by late January 2025 (previously late December) \n How this will affect your organization: \n 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. \n This change will be on by default. \n What you need to do to prepare: \n 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. \n MC889534 — (Updated) Microsoft Teams: Embed support for Teams town hall \n Microsoft 365 Roadmap ID 401120 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n As a part of Team’s ongoing effort to enable our customers to create, manage, and run large scale events, end users can now embed Teams town hall in sites they manage. This capability allows town hall attendees to watch the event instance within a particular website. \n Embed for town hall introduces embeddable support for town hall engagement features on release. Attendees will have the same engagement feature access within the embed player as they do in client such as Q&A, Captions, Reactions and more. \n To implement embed for town hall, organizers can access their town hall events unique embed code from the town hall scheduling template upon publish. Organizers can then take that code and inject it to their SharePoint or Microsoft 365 site as desired. On event start, attendees will be able to view and engage with the embed stream on the published site. \n When this will happen: \n Targeted Release: We will begin rolling out early November 2024 (previously early October) and expect to complete by mid-November 2024 (previously mid-October). \n General Availability (Worldwide, GCC): We will begin rolling out early December 2024 (previously late October) and expect to complete by mid-February 2025 (previously mid-January). \n How this will affect your organization: \n Users will be able to copy embed code directly from town hall scheduling form on event publish. After the embeddable code is placed in the website, the town hall player will be accessible to attendees who have access to the URL. \n Note: Attendee access to the embedded video player is driven by the town hall event access. \n What you need to do to prepare: \n Organizers with SharePoint or Microsoft 365 site who want to utilize embed support for town hall can begin implementing the embeddable code upon release. \n MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar \n Microsoft 365 Roadmap ID 409226 \n Updated January 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n 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). \n General Availability (Worldwide, GCC): We will begin rolling out in mid-October 2024 and expect to complete by late January (previously late December). \n How this will affect your organization: \n Before this release: Sensitivity labels were not available for town halls and webinars. \n 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 under Event access may be enabled or disabled based on the sensitivity label set for the event. \n For upcoming events that have already been scheduled prior to rollout, the sensitivity of the event will be set to None. 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. \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with revised documentation. \n MC884009 — (Updated) Microsoft Teams: Start/stop recording on Teams Rooms on Windows \n Microsoft 365 Roadmap ID 412072 \n Updated January 28, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out late January 2025 (previously mid-January) and expect to complete by early February 2025 (previously late January). \n 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). \n General Availability (DoD): We will begin rolling out mid-February (previously early January) and expect to complete by late February 2025 (previously mid-January). \n How this will affect your organization: \n 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. \n After the rollout \n 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 select Start recording or Stop recording from the More menu, shown here at the bottom of the screen: \n When users start recording a Meet now or Whiteboard session 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. \n This feature will be on by default and available for admins to configure. \n As an admin, you can allow or prevent users (including room accounts) from recording meetings with the Teams meeting recording policy: \n \n Using the Teams admin center: Learn more at Manage Teams recording policies for meetings and events - Microsoft Teams | Microsoft Learn. \n Using Microsoft PowerShell: Learn more at Set-CsTeamsMeetingPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn. \n \n 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 uses Meeting options to remove permissions from the room account to record the meeting, the start/stop recording button will not be available as well. \n Start/stop recording is not supported in these scenarios: \n \n Teams calls including P2P, group, and PSTN calls \n External/cross-tenant Teams meetings and calls \n Third-party meetings and calls including Direct Guest Join and SIP \n \n 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. \n What you need to do to prepare: \n 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. \n MC866447 — (Updated) CAPTCHA Verification for Anonymous Meeting Participants \n Updated January 7, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (GCC): We will begin rolling out late October 2024 (previously early October) and expect to complete by late January 2025 (previously mid-December). \n How this will affect your organization: \n 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). \n What you need to do to prepare: \n 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. \n MC818885 — (Updated) Microsoft Teams: Multiple camera view for Teams Rooms on Windows \n Microsoft 365 Roadmap ID 402517 \n Updated January 15, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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). \n When this will happen: \n Targeted release: We will begin rolling out mid-January 2025 (previously early January) and expect to complete by mid-January 2025 (previously mid-December). \n General Availability (Worldwide): We will begin rolling out mid-January 2025 (previously mid-December) and expect to complete by late January 2025 (previously late December). \n General Availability (GCC): We will begin rolling out in mid-January 2025 (previously mid-December) and expect to complete by late January 2025 (previously early January). \n How this will affect your organization: \n Before the rollout \n Multiple camera views are not available in Teams Rooms on Windows. \n After the rollout \n 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: \n \n 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. \n Admins can configure multiple camera view using Remote Accessin the Microsoft Teams Rooms Pro Management portal. \n \n 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. \n 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. \n Admin setting to configure Multiple camera view on a local device: \n What you need to do to prepare: \n 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. \n Before rollout, we will update this post with revised documentation. \n MC809602 — (Updated) Microsoft Teams: New skin tone settings and reactions \n Microsoft 365 Roadmap ID 323766 \n Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience \n 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 app Settings > Appearance and accessibility menu 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). \n When this will happen: \n Targeted Release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October). \n General availability (Worldwide, GCC): We will begin rolling out early November 2024 (previously late October) and expect to complete by late December 2024. \n General availability (GCC High, DoD): We will begin rolling out mid-November 2024 (previously mid-November) and expect to complete by late January 2025 (previously late December) \n What you need to do to prepare: \n 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. \n We will update this post before rollout with revised documentation. \n MC808828 — (Updated) Microsoft Teams: Custom background and daily restart windows for Teams panels \n Microsoft 365 Roadmap ID 402183 \n Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience \n 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. \n 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. \n When this will happen: \n General Availability (Worldwide and GCC): We will begin rolling out early September 2024 (previously early August) and expect to complete by late January 2025 (previously late December) \n How this will affect your organization: \n Custom backgrounds: \n To set custom backgrounds for your Teams Panel devices, go to Teams admin center > Teams devices > Panels > Configuration profiles > Add or Edit > Device settings > Background > Use a custom background. You can upload one image at a time. \n The image must meet these requirements: \n \n Minimum resolution: 1280x720 \n Format: JPG, JPEG, or PNG \n Minimum size: 100KB \n Maximum size: 2MB \n \n 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. \n 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. \n 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. \n Daily device restart window: \n 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. \n \n To change it on the device, go to your Teams panel device settings (Settings > Teams admin settings > Device restart). \n To change it remotely, go to Teams admin center > Teams devices> Panels > Configuration profiles > Add or Edit > General > Daily device restart window > save and assign the changes in configuration profiles to one or multiple devices. \n \n What you need to do to prepare: \n 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. \n MC781595 — (Updated) Microsoft Teams: Tenant-wide policy for permission to download meeting transcription \n Microsoft 365 Roadmap ID 332800 \n Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience \n 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. \n When this will happen: \n Targeted Release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May). \n 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). \n 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) \n General Availability (DoD): We will begin rolling out late September 2024 (previously mid-August) and expect to complete by complete by late January 2025 (previously late December). \n What you need to do to prepare: \n 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. \n 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.) \n MC772556 — (Updated) Microsoft Teams: Shorter meeting URLs \n Microsoft 365 Roadmap ID 381953 \n Updated January 10, 2025: We have updated the rollout timeline below. Please note that information about meeting link expiry changes related to this rollout has been added. \n We are reducing the length of Microsoft Teams meeting URLs for easier sharing. This rollout applies to all Microsoft Teams platforms (Teams for iOS, Android, Mac, Teams devices, desktop, and web). \n When this will happen: \n Targeted Release: We will begin rolling out mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). \n General Availability (Worldwide, GCC): We will begin rolling out mid-April 2025 (previously mid-February) and expect to complete by late April 2025 (previously late March). \n General Availability (GCC High, DoD): We will begin rolling out early June 2025 (previously mid-April) and expect to complete by late June 2025 (previously late April). \n How this will affect your organization: \n The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode> \n To make meeting URL shorter, we are removing several parameters such as tenant ID, conversation ID etc. This change serves two main goals: 1) improving usability of URL during sharing and 2) making the URL more secure and less susceptible to malicious attacks. \n Here are some details about how meeting links work and when they expire: \n \n In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire. \n Every meeting link expires in 60 days after the scheduled event or in 8 hours, if it was created as Meet Now. Learn more about expiration timelines for different types of meetings. \n \n With the Short Meeting URL release, expiration limit will be applied to all newly created links. \n Once the change to Short Meeting URL is released, all newly created meetings will expire as described in the documentation: 60 days after meeting ends for scheduled meetings and 8 hours after creation for Meet Now. Once this expiry period is over, in case someone clicks the link (e.g. outside of Teams app OR in the meeting details inside Teams calendar section), they will be unable to join the meeting. \n Note: Old links created before short meeting URL release will continue working as it previously was (user will be able to join even after the documented expiry limits). \n The reason why we are making this change is simple: security is our topmost priority. Maintaining a high security level is essential to protect sensitive data, prevent financial losses, ensure business continuity, and meet compliance and legal obligations. It is a critical aspect of modern digital life and business operations. This adjustment is designed to enhance the security of Teams meeting links, thereby better safeguarding the customer tenant. We want to be on par with modern security standards, that’s why the new behavior is a step in the right direction that we must take. It’s not possible to keep the current behavior. If you think it breaks some of your business processes, please leave comment to the MC post and describe your case there. \n Recommendations in case the meeting link has expired: \n For meeting organizer: We recommend scheduling a new meeting. If the meeting organizer got removed from the tenant someone else should reschedule their meetings from scratch. \n For participant: Please reach out to the meeting organizer and ask them to reschedule the meeting or send you an updated link. \n What you need to do to prepare: \n You may want to check if you have any integrations that use parameters from URL. After the rollout, the URL will only contain the meeting ID. Parameters such as tenant ID, organizer ID, conversation ID and message ID will not be in the URL. \n You may inform meeting organizers from your tenant who use expired meeting links, or you may want to make a tenant-wide announcement about this change. \n 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. \n MC750668 — (Updated) Microsoft Teams: Access Workflows from the three-dot menu on shared file \n Microsoft 365 Roadmap ID 381643 \n Updated January 27, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n Targeted release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October). \n Worldwide: We will begin rolling out early November 2024 (previously late October) and expect to complete by late November 2024 (previously early November). \n GCC: We will begin rolling out early December 2024 (previously late October) and expect to complete by mid-February 2025 (previously mid-January). \n How this will affect your organization: \n 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 choose Workflows. From Workflows, 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 selecting See more workflows at 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. \n If the Power Automate app is disabled in the Teams admin center, users will not see this option in the three-dot menu. \n This feature will only be available in the New Teams client on the desktop and on the web. \n What you need to do to prepare: \n 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. \n MC726122 — (Updated) Microsoft Teams: View, download, and delete Microsoft OneDrive transcript files \n Microsoft 365 Roadmap ID 365720 \n Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience \n 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. \n 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. \n 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. \n When this will happen: \n Targeted release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May). \n 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). \n GCC High: We will begin rolling out late August 2024 and expect to complete by mid-September 2024. \n DoD: We will begin rolling out late September 2024 and expect to complete by late January 2025 (previously late December) \n How this will affect your organization: \n 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 this documentation. \n 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. \n What you need to do to prepare: \n 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. \n MC718553 — (Updated) Microsoft Teams: Change background while recording on phone \n Microsoft 365 Roadmap ID 380852 \n Updated January 21, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Users can now record themselves anywhere and share it with coworkers in the Microsoft Teams chat or channel without worrying about the background. Users can now change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on iOS devices. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out early May 2024 (previously late March) and expect to complete by late January 2025 (previously late December). \n How this will affect your organization: \n Users will get an option to change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on an iOS device. To use this feature: \n \n Press and hold the camera icon next to the Compose box and then tap the blur icon to the right of the shutter button. \n You can then choose either an image to replace the background or choose to mildly or heavily blur your background. \n \n What you need to do to prepare: \n 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. \n MC718250 — (Updated) Microsoft Teams: Describe it to design it in Teams Workflows \n Microsoft 365 Roadmap ID 382659 \n Updated January 23, 2025: After further review, we will not be rolling this out to GCC. We will communicate via Message center when we are ready to proceed. \n Can't find a workflow template that matches what you need in Microsoft Teams? You will now be able to describe in detail how you want your automation to work and receive a workflow to match your needs. All you need to do is select the Workflow builder button at the bottom of the create dialog in the Workflows app in Microsoft Teams chat and channel overflow menu. \n Workflow builder will come to the Workflows app in Microsoft Teams chat and channel overflow menu first. Other entry points to Workflows will get this feature later. \n When this will happen: \n Worldwide: We will begin rolling out late September 2024 (previously mid-September) and expect to complete by late October 2024 (previously late September). \n GCC Release: We will not be proceeding with this change at this time. \n How this will affect your organization: \n All users with the ability to create workflows with the Workflows app in Teams will be able to describe the workflow they are trying to build and then receive a suggested flow. \n Prerequisites \n A work or school Teams account with access to a Power Automate environment in Europe or the United States. \n Limitations \n Power Automate supports workflow descriptions written in the English language only. Descriptions written in other languages might work but are not supported. \n Cloud flows are the only type of flow that you can create from a written description. \n In the version rolling out, the AI might omit some parameters, even if you provide them in the description. \n What you need to do to prepare: \n No action is needed to prepare for this rollout. If your tenant uses the Power Automate app within Microsoft Teams, you may want to notify your users about this change and update any relevant documentation as appropriate. \n To learn more: Create a cloud flow from a description (preview) - Power Automate | Microsoft Learn \n MC709270 — (Updated) Mute with Windows Taskbar available in the new Microsoft Teams on Windows \n Microsoft 365 Roadmap ID 191528 \n Updated January 13, 2025: We have updated the rollout timeline below. Thank you for your patience \n The Muting Teams with Windows Taskbar is now available. This feature, available in the new Teams experience on Windows, enables you to mute and unmute your audio by clicking the mic icon in Windows taskbar. \n To control your call mic from the taskbar, do the following: \n Select the mic icon on your taskbar or press Windows logo key + Alt + K to mute or unmute your microphone while using a calling app. \n -OR- Click the volume icon in the hardware indicator for volume in Windows taskbar. \n When this will happen: \n Targeted release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May). \n Worldwide, GCC, GCC High & DoD: We will begin rolling out mid-June 2024 (previously early June) and expect to complete by complete by late January 2025 (previously late December) \n How this will affect your organization: \n This enables a feature previously available in older version of Teams on Windows. \n What you need to do to prepare: \n To prepare, distribute updates on this rollout with your organization if applicable for your users. \n MC705760 — (Updated) Teams: Latest meeting experiences with performance improvements on web for Safari and Firefox (for guests) \n Microsoft 365 Roadmap ID 329253 \n Updated January 24, 2025: We have updated the rollout timeline below. Thank you for your patience. \n The latest Teams meeting experiences will be available for Teams on the web in Safari and Firefox browsers - including performance improvements, refreshed pre-join, updated meeting stage, and the updated meeting toolbar. (for anonymous join only) \n When this will happen: \n Worldwide: We will begin rolling out early September 2024 (previously mid-August) and expect to complete by early October 2024 (previously late August). \n GCC, GCC High and DoD: We will begin rolling out mid-October 2024 (previously mid-September) and expect to complete by mid-February 2025 (previously mid-January). \n How this will affect your organization: \n We make constant steps to improve Teams performance irrespective of the platform – this time we are making the experience of Teams meetings on web (in Safari and Firefox browsers) better for anonymous users (guests). That’s crucial because it improves external collaboration. For example, if participants from your tenant would like to have meetings with non-Teams users (who are often joining as guests) it’ll become simpler as guests joining meeting from Safari/Firefox web browsers won’t have to wait significant amount of time for the meeting experience to load. \n You may also notice that currently meeting UI in Chrome and Safari/Firefox is different, but with this update it won’t be a case anymore and you’ll enjoy all the benefits of modern UI (such as meeting toolbar on top of the screen, etc). \n What you need to do to prepare: \n You may want to update your internal documentation to inform your users about this improvement. \n MC688109 — (Updated) Co-organizer experience updates in Teams Webinars and Townhalls \n Microsoft 365 Roadmap ID 168524 \n Updated January 15, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n Targeted release: We will begin rolling out mid-January 2025 (previously early January) and expect to complete by mid-January 2024 (previously mid-December). \n 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). \n How this will affect your organization: \n When co-organizer opens the event scheduling page, they should have the ability to edit the details page, publish, and cancel the event. \n What you need to do to prepare: \n Nothing required to prepare. \n Microsoft Purview \n MC989980 — Microsoft Purview | Insider Risk Management: Public preview of policy deletion enhancement (GCC, GCCH, DoD) \n Microsoft 365 Roadmap ID 171601 \n Microsoft Purview Insider Risk Management will be rolling out a policy deletion enhancement. \n When this will happen: \n General Availability (GCC, GCC High, DoD): We will begin rolling out mid-February-2025 and expect to complete by early March 2025. \n How this will affect your organization: \n After this rollout, admins with appropriate permissions will be able to delete all associated alerts and users in scope when deleting a policy, to help quickly reset and remove inactive policies. Cases will not be impacted. \n This change will be available by default. \n What you need to do to prepare: \n No action is needed to enable these features. 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. \n 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. \n You can access the Insider Risk Management solution in the Microsoft Purview compliance portal. \n Learn more: Create and manage insider risk management policies | Microsoft Learn \n MC986518 — Microsoft Purview | Insider Risk Management: Updates to email scoring (GCC, GCC High, DoD) \n Microsoft 365 Roadmap ID 471010 \n Coming soon: Microsoft Purview | Insider Risk Management (IRM) will be rolling out updates to email scoring. \n When this will happen: \n General Availability (GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. \n How this will affect your organization: \n Insider Risk Management email scoring logic is being updated. With current logic, a single email to multiple recipients is counted multiple times, and this is creating noise by increasing the risk score. In the new logic, a single email to multiple recipients is counted once, and this new principle is applicable to the email containing multiple unallowed domains or priority content. After this rollout, all email insights in Alerts will display the new count and score. \n This change will be available by default. \n What you need to do to prepare: \n 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. \n 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. \n You can access the Insider Risk Management solution in the Microsoft Purview compliance portal. \n Learn more: Configure policy indicators in insider risk management | Microsoft Learn \n MC985476 — Microsoft Purview | Insider Risk Management: Share user risk details with other security solutions (GCC, GCC High, DoD) \n Microsoft 365 Roadmap ID 475857 \n Microsoft Purview Insider Risk Management is introducing the ability to share Insider Risk Management data with other Microsoft services for Government customers. When turned on, admins with the correct permissions will be able to review user risk details and alerts from Insider Risk Management in other solutions such as Microsoft Purview | Data Loss Prevention (DLP), Microsoft Purview | Communication Compliance, and Microsoft Defender. \n When this will happen: \n General Availability (GCC, GCC High, DoD): We will begin rolling out mid-February 2025 and expect to complete by mid-February 2025. \n How this will affect your organization: \n Admin can access the toggle in Microsoft Purview > Insider Risk Management settings > Share user risk details with other security solutions: \n \n This change will be available by default. \n What you need to do to prepare: \n 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. \n Consider assessing your organization’s needs and decide if your organization will benefit from reviewing Insider Risk Management alerts through other solutions. \n Learn more: Share insider risk management data with other solutions | Microsoft Learn \n MC973511 — (Updated) Microsoft Purview | Data Lifecycle Management: Separate retention policies for Copilot and AI apps \n Microsoft 365 Roadmap ID 470025 \n Updated January 10, 2025: We have updated the rollout timeline below. Thank you for your patience. \n This new feature provides the capability for admins to configure separate retention policies for various Microsoft 365 Copilot and AI apps. As a result, admins will have the option to configure policies that can delete Copilot and Generative AI interactions faster. \n When this will happen: \n General Availability (Worldwide): We will begin rolling out mid-February 2025 (previously late January) and expect to complete by late February 2025 (previously mid-February). \n How this will affect your organization: \n Organizations will now have controls to configure different retention policies for Microsoft Teams Chat, Copilot, Copilot studio, and ChatGPT Enterprise. \n This feature is available by default. \n What you need to do to prepare: \n For more information, see Create and configure a retention policy. \n 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. \n MC969449 — (Updated) Microsoft Purview | Data Loss Prevention for endpoints: Four new conditions (GCC, GCCH, DoD) \n Microsoft 365 Roadmap ID 374811 \n Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for Microsoft Purview | Data Loss Prevention (DLP): Four new conditions or predicates that admins can use in their policies for endpoint devices. \n When this will happen: \n General Availability (GCC, GCC High, DoD): We will begin rolling out mid-January 2025 (previously early January) and expect to complete by late January 2025 (previously mid-January). \n How this will affect your organization: \n After this rollout, DLP policies will include the capability to identify documents that are unscannable, partially scannable, exceed a specific file size, or have names matching configured patterns for Government cloud tenants on Windows endpoint devices. This functionality enables you to prevent users from accessing unscannable files on endpoints and attempting egress actions such as copying to a USB drive, copying to the clipboard, or transferring to another network share, among others. \n The four new predicates are: \n Document size equals or is greater than: Detects documents greater than or equal to the specified value. \n Document name matches patterns: Detects documents where the file name matches specific patterns. \n Document couldn’t be scanned: Applies to documents when their content wasn't scanned. Examples include password protected files, files for which text extraction failed, and files that exceed file size limit. \n Document couldn’t complete scanning: Applies to documents when their content was scanned, but the entire document was not scanned. Examples include files for which extracted text exceeded the limits/thresholds. \n When defining your DLP Policy, you can use these conditions across supported and applicable workloads for government cloud tenants. For example, you can extend any of the four new conditions that are available now in DLP for Exchange and scope them to Endpoint > Devices as part of your policies and rules, which enhances protection across the digital estate. \n Please refer to the supported file types on endpoint, for which these predicates will provide protection. \n What you need to do to prepare: \n \n Learn more about conditions supported for endpoints \n Get started with Data Loss Prevention in the Microsoft Purview compliance portal. \n Learn more: Using Endpoint DLP | Microsoft Learn \n \n 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 and users about this change and update any relevant documentation. \n MC966637 — (Updated) Microsoft Purview | Data Loss Prevention for endpoints: New \"Document property\" condition (GCC, GCCH, DoD) \n Microsoft 365 Roadmap ID 417482 \n Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for Microsoft Purview | Data Loss Prevention (DLP): The new Document property is condition will be available for use in policies for endpoint devices. \n When this will happen: \n General Availability (GCC, GCC High, DoD): We will begin rolling out mid-January 2025 (previously early January) and expect to complete by late January 2025 (previously mid-January). \n How this will affect your organization: \n After this rollout, DLP policies can detect and monitor egress actions for documents that match defined custom properties. The new Document property is condition detects documents with custom properties matching the specified values. \n As part of DLP policy definition, this new condition can be used across supported and applicable workloads. For example, the Document property is condition in DLP for Exchange can be extended to endpoint devices as part of DLP policies and rules, which enhances protection across the digital estate. \n This change will be available by default for admins to configure. \n What you need to do to prepare: \n Get started with DLP in the Microsoft Purview compliance portal. \n Learn more: Data Loss Prevention policy reference | Microsoft Learn \n 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. \n MC961761 — Microsoft Purview | Insider Risk Management: IRM alerts in Microsoft Defender XDR \n Microsoft 365 Roadmap ID 422730 \n Updated January 23, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to Microsoft Purview: Insider Risk Management (IRM) data including alerts, indicators and events will be available in these Microsoft Defender XDR experiences: \n \n Unified alert queue: IRM alerts will appear in the unified alert and incident queue in Defender XDR for comprehensive investigation and correlation. \n Advanced Hunting: IRM data will be available for advanced hunting in Defender XDR, allowing analysts to identify hidden risk patterns using KQL queries. Analytics can also create custom detections on the top of IRM data. \n Graph API: IRM data will be accessible through the Microsoft Graph API, supporting bidirectional integrations with external applications. \n Microsoft Sentinel: IRM alerts will be available in Microsoft Sentinel through the XDR-Sentinel connector, providing richer metadata. \n \n When this will happen: \n Public Preview: We will begin rolling out mid-January 2025 and expect to complete by end of January 2025. \n General Availability (WW, GCC, GCC High, DoD): We will begin rolling out late June 2025 (previously early May) and expect to complete by mid-July 2025 (previously mid-May). \n How this will affect your organization: \n Enable this feature by turning on Share data with other security solutions in the IRM global settings. \n Only users with Insider risk analysis or investigation roles in the Microsoft Purview portal can access IRM data in Defender XDR. \n To access alerts, incidents, and events from Defender XDR via API, you need to provision apps with the necessary permissions. IRM data is accessible via Microsoft Security Graph APIs, allowing for reading and updating alert or incident statuses. Permissions are set at the application level, without solution-specific scoping. Any existing apps pulling data from these APIs will also access IRM data. So, if you integrate XDR alerts into external ticketing systems, IRM alerts will show up, unless you specifically filter out the alerts. \n IRM alerts will appear in Sentinel if your tenant has the Defender XDR connector enabled in Microsoft Sentinel. \n In Defender XDR, IRM data is not pseudonymized to allow effective correlation of IRM alerts with alerts from other solutions within the platform, such as Defender for Endpoint and Defender for Cloud apps. \n These changes will be available by default for admins to configure in IRM global settings. \n Admins will be able to view Insider Risk Management alerts in Defender XDR. \n Harness the power of Advanced Hunting queries with two new tables that contain Insider Risk Management data: DataSecurityBehaviors and DataSecurityEvents. \n What you need to do to prepare: \n \n Opt-in to data sharing settings in IRM global settings page. \n Assign necessary permissions to analysts \n Review existing apps accessing Defender XDR data through Graph APIs. \n If your organization is using Microsoft Defender XDR connector, please review the list of users who will gain access to this data through Sentinel. \n \n This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration in IRM global settings to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation. \n MC950890 — (Updated) Microsoft Purview | Data Security Posture Management for AI \n Microsoft 365 Roadmap ID 469509 \n Updated January 24, 2025: We have updated the content. Thank you for your patience. \n Generative AI (GAI) is being adopted at an unprecedented rate. AI fuels innovation and productivity but also poses risks – organizations are concerned about the risky AI use and sensitive data loss through AI apps. Microsoft Purview Data Security Posture Management for AI (DSPM for AI) is a central location in Microsoft Purview that helps organizations secure data in AI, including Microsoft AI applications such as Microsoft 365 Copilot and non-Microsoft AI applications. With the DSPM for AI capabilities in Purview, organizations can safely adopt AI without having to choose between productivity and protection. \n DSPM for AI also supports admin units and displaying AI policies that were created in Purview solutions. A version of DSPM for AI is available to additional licensing, specifically Microsoft 365 E3 and Microsoft 365 Copilot licenses. \n When this will happen: \n We will begin rolling out late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). \n How this will affect your organization: \n DSPM for AI also supports admin units and displaying AI policies that were created in Purview solutions. A version of DSPM for AI is available to additional licensing, specifically Microsoft 365 E3 and Microsoft 365 Copilot licenses. \n DSPM for AI use cases \n \n Viewing insights and analytics into AI activity in your organization. \n Using policies to protect data and prevent data loss in AI prompts \n Implementing compliance controls to apply optimal data handling and storing policies \n \n Microsoft Purview DSPM for AI will be in the Microsoft Purview portal and will consist of 5 tabs: Overview, Recommendations, Reports, Policies, and Activity explorer. \n The DSPM for AI Overview with getting started steps, two recommendations, two reports, and resources. \n The Recommendations tab displays all recommendations provided by DSPM for AI. \n \n Reports includes graphs for total interactions over time, sensitivity labels and sensitive information types found in AI interactions, user risk level, and more. \n Policies displays all policies that have been created by default or AI policies created in Purview solutions. \n Activity explorer shows events for AI interactions along with prompts and responses. \n This feature will be enabled by default. \n What you need to do to prepare: \n 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. \n Get ready for this change by reviewing the admin documentation: \n \n Considerations for Data Security Posture Management for AI & data security and compliance protections for Copilot \n Microsoft Purview data security and compliance protections for generative AI apps \n \n MC949003 — (Updated) Microsoft Purview | Data Loss Prevention: Gain policy insights with Microsoft 365 Copilot for Security \n Microsoft 365 Roadmap ID 466740 \n Updated January 17, 2025: We have updated the rollout timeline below. Thank you for your patience. \n As part of Microsoft 365 Copilot for Security in Data Loss Prevention (DLP), Policy Insights helps admins understand DLP policies and its constructs. This enhancement enables DLP admins to gain insights on coverage of policies on pivots like location, classifiers, and notifications. \n DLP admins can get these insights on all the policies or on a few selected policies. They will be able to use prompts to gain a deeper level view of how a policy is configured for their digital landscape. This helps them align their data posture on a regular basis and make corrections to policy posture as needed. \n When this will happen: \n Public Preview: We will began rolling out mid-November 2024 and expect to complete by early December 2024. \n General Availability (Worldwide): We will begin rolling out early February 2025 (previously early January) and expect to complete by late February 2025 (previously late January). \n Currently, Copilot for Security is not designed for use by customers using US government clouds, including but not limited to GCC, GCC High, DoD, and Microsoft Azure Government. For more information, consult with your Microsoft representative. \n How this will affect your organization: \n Administrators can invoke the policy insights to understand the insights from all their policies or selected polices. The insights offered start with a higher-level view of how their policies: \n \n are effective across locations. \n detect the presence of sensitive information types throughout their digital estate. \n notify administrators of violations. \n educate users while they perform activities they should not. \n \n These insights are offered with different pivots by location, classification, and by administrative scopes. This is offered to give the security policy administrators different views for deeper understanding of policy constructs and their impact. \n Step 1: \n Select the policies you wish to get insights/quick summaries about. \n Step 2: \n Click on the Get Insights with Copilot button. You will see the prompt is already pushed into the Copilot Experience in the side panel. \n Step 3: \n Copilot responds with insights on the selected policies. \n What you need to do to prepare: \n Admins can prepare by having Security Computer Units (SCUs). Copilot for Security is sold in a provisioned capacity model and is billed by the hour. \n Get more information about SCUs: Get started with Microsoft Copilot for Security | Microsoft Learn. \n MC920308 — (Updated) Microsoft Purview | Information Protection: Auto-labeling policies will support \"Fingerprint based SIT\" \n Microsoft 365 Roadmap ID 396173 \n Updated January 24, 2025: We have updated the content. Thank you for your patience. \n Coming soon to Microsoft Purview | Information Protection: Admins will be able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT (sensitive info type). \n When this will happen: \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late November 2024 and expect to complete by early February 2025 (previously mid-January). \n How this will affect your organization: \n Before this rollout, admins are not able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT. \n After this rollout, you can configure Fingerprint based SIT using the condition Content contains sensitive information types. Files that match Fingerprint based SIT will show in simulation. \n Note: Contextual summary is not available for Fingerprint based SITs. \n This change will be on by default and available for admins to configure. \n What you need to do to prepare: \n 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. \n Learn more \n \n About document fingerprinting | Microsoft Learn \n Automatically apply a sensitivity label in Microsoft 365 | Microsoft Learn \n \n MC911618 — (Updated) Microsoft Purview | Insider Risk Management: Multi-policy settings in Adaptive Protection \n Microsoft 365 Roadmap ID 171735 \n Updated January 24, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n After this rollout, admins will be able to select multiple Insider Risk Management policies in the Risk levels for Adaptive Protection settings. \n When this will happen: \n General Availability (GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously mid-January) and expect to complete by mid-March 2025 (previously mid-February). \n How this will affect your organization: \n Before this rollout, admins can select single Insider Risk Managment policies in the Risk levels for Adaptive Protection settings. \n This new feature will be on by default and available for admins to configure. \n What you need to do to prepare: \n 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 \n 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. \n Learn more: Help dynamically mitigate risks with Adaptive Protection (preview) | Microsoft Learn \n MC892050 — Microsoft Purview | Compliance Portal: Enrich triage in Communication Compliance within Insider Risk Management context \n Microsoft 365 Roadmap ID 415170 \n Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. \n This feature update to Microsoft Purview Communication Compliance (CC) introduces a pivotal enhancement that integrates Insider Risk Management (IRM) alerts within CC triage flow, providing a holistic approach to compliance risk assessment. This integration empowers investigators with enriched insights by correlating communication alerts with a user's risk profile and activity history from IRM directly in the CC triage flow. This synergy between IRM and CC facilitates a more nuanced and informed decision-making process during investigations. \n When this will happen: \n General Availability (GCC, GCC High, DoD): We will begin rolling out early March 2025 (previously early January) and expect to complete by late April 2025 (previously late February). \n How this will affect your organization: \n The integration of IRM context into CC is a significant stride towards enhancing the efficacy of compliance investigations. This will allow investigators to view a user's risk profile and history alongside communication alerts, enabling a more informed and efficient triage process. \n The insider risk severity (Low, Medium, or High) determined by activity detected in IRM policies helps admins prioritize and respond to user activity accordingly. A new user activity timeline will show messages and activities from IRM in one screen, simplifying the review process. \n What you need to do to prepare: \n To use this feature, please connect with an IRM administrator to enable data sharing from IRM settings. If you don't turn this setting on, you will see “Insider risk activity not available.” \n MC808165 — (Updated) Microsoft Purview eDiscovery | Modernized eDiscovery in new Microsoft Purview portal \n Microsoft 365 Roadmap ID 383744 \n Updated January 9, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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: \n \n 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. \n Enhanced search efficiency with message ID and sensitivity labelsfor faster access to information. \n Use of the improved search by Sensitive Information Type (SIT) interface for user-friendly selection without manual input. \n 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. \n Acceleration through powerful investigation capabilities, such as user's frequent collaborators, providing a comprehensive view of the user's networks. \n 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. \n Introduction of the new visual Statisticsallows users to gain insights at a glance (such as Results containing Sensitive Information Types, top communication participants, etc.) \n Monitor long-running processes with an informed and transparent progress bar with the option to cancel (for certain process types) if needed. \n Obtain a full process report for all actions taken, such as statistics for holds and exports, bolstering the defensibility of your eDiscovery efforts. \n 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. \n \n When this will happen: \n Public Preview: We will begin rolling out late July 2024 and expect to complete by late September 2024. \n General Availability (Worldwide): We will begin rolling out mid-February 2025 (previously mid-December) and expect to complete by early mid-February 2025. \n GCC: We will begin rolling out mid-March 2025 and expect to complete by mid-March 2025 \n GCC-High: We will begin rolling out mid-March 2025 and expect to complete by late March 2025 \n DoD: We will begin rolling out late March 2025and expect to complete by late March 2025. \n How this will affect your organization: \n 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. \n 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. \n What you need to do to prepare: \n Update internal documentation and provide training to all eDiscovery users in your organization. \n Learn more about the new Purview Portal. \n Learn more about the modernized eDiscovery (preview) experience: Learn about eDiscovery (preview) solutions | Microsoft Learn \n MC805721 — (Updated) Purview | Insider Risk Management: Adaptive Protection is generally available in GCC, GCCH, and DoD \n Microsoft 365 Roadmap ID 335856 \n Updated January 24, 2025: We have updated the content. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (GCC, GCC High, DoD): We will begin rolling out late February 2025 (previously mid-January) and expect to complete by late March 2025 (previously mid-February). \n How this will affect your organization: \n 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. \n 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. \n What you need to do to prepare: \n 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. \n 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. \n The default state of this feature is off. \n Get started with Adaptive Protection in the Microsoft Purview compliance portal > Insider risk management > Adaptive Protection: \n References \n \n Learn about adaptive protection \n Learn about insider risk management \n Learn about data loss prevention \n \n 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. \n 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. \n MC795079 — Microsoft Purview | Insider Risk Management - Adaptive Protection - HR resignation date as a condition for risk level \n Microsoft 365 Roadmap ID 124972 and 171748 \n Updated January 7, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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 MC681240 Adaptive Protection in Microsoft Purview: Public preview of HR resignation date as a condition for risk level (November 2023). \n When this will happen: \n General Availability: We will begin rolling out late June 2024 and expect to complete by mid-January 2025 (previously late mid-December). \n How this will affect your organization: \n 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. \n What you need to do to prepare: \n 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. \n 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. \n Additional Resources: \n You can access the Insider Risk Management solution in the Microsoft Purview compliance portal. \n \n Home - Microsoft Purview \n \n Learn more about adaptive risk mitigation: \n \n Help dynamically mitigate risks with Adaptive Protection (preview) | Microsoft Learn \n \n MC791110 — (Updated) Microsoft Purview | Data Lifecycle Management: New integration with Adaptive protection \n Microsoft 365 Roadmap ID 392839 \n Updated January 9, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for Microsoft Purview: We are announcing the public preview of the integration of Adaptive protection with Data Lifecycle Management (DLM) to help you find the right balance to protect against data sabotage while enabling productivity. This new integration leverages DLM features to provide an additional control for Adaptive protection that automatically preserves items deleted by a user with an elevated risk level, so items can be restored if needed. \n When this will happen: \n Public preview: We will begin rolling out in late June 2024 (previously early May) and expect to complete by late July 2024 (previously mid-July). \n General Availability: We will begin rolling out in mid-March 2025 (previously mid-January) and expect to complete by late March 2025 (previously late February). \n How this will affect your organization: \n After the rollout, and after you enable Adaptive protection for your tenant, the retention label and auto-apply policy for data lifecycle management will be automatically created for you. This policy will automatically include elevated risk users identified by Microsoft Purview | Insider Risk Management solution. If these users delete content from Microsoft SharePoint, Microsoft OneDrive, or Microsoft Exchange, a retention label is automatically applied to that content to retain it for 120 days. Retention labels are automatically applied to unlabeled content deleted by these users. When these users are no longer at the elevated risk level, they are automatically removed from the DLM policy, and the system will no longer keep a copy of content they delete. Any content copies previously retained when the user had an elevated risk level will be kept for the 120 days as specified by the retention label. \n Unlike other retention labeling scenarios, users do not see the retention label, and you do not need to create or manage the retention label or policy. At this time, you can't change the retention period or assign different policies based on the different risk levels, or for different locations. The single retention label and auto-labeling policy for your tenant is not visible in the Microsoft Purview compliance portal. \n What you need to do to prepare: \n Learn more: Learn about retention policies & labels to retain or delete | Microsoft Learn \n If you're using Adaptive protection and want to automatically retain content deleted by elevated risk users, follow these steps to turn on this new integration. \n \n Sign in to the Microsoft Purview compliance portal. \n Navigate to Data lifecycle management > Microsoft 365 > Adaptive protection settingsin the top right corner. \n Turn the setting ON and select Save. \n \n If you’re not using Adaptive protection already, turn on Adaptive protection and the new feature will be enabled along with Adaptive protection. \n 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. \n MC678065 — (Updated) Microsoft Purview compliance portal: Information Protection - New cmdlet for Content Explorer \n Microsoft 365 Roadmap ID 117531 \n Updated January 9, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n This feature will begin rolling out early July 2025 (previously mid-April) and expect to complete by late July 2025 (previously mid-May). \n How this will affect your organization: \n This feature can be accessed through the Security & Compliance PowerShell, Export-ContentExplorerData. \n What you need to do to prepare: \n There are no additional settings needed for this feature. \n Get started with content explorer | Microsoft Learn \n Outlook \n MC993229 — New Microsoft Outlook for Windows and web: New folder color feature \n Microsoft 365 Roadmap ID 472921 \n Coming soon to new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web: Users can customize folder icon colors, making it easier to visually differentiate and personalize folders. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 and expect to complete by late February 2025. \n General Availability (Worldwide): We will begin rolling out late March 2025 and expect to complete by late March 2025. \n General Availability (GCC, GCC High, DoD): We will begin rolling out late April 2025 and expect to complete by late April 2025. \n How this will affect your organization: \n After this rollout, this feature will be available for all Outlook accounts except for shared mailboxes and shared folders. Colors work for light and dark mode. Note: Some Outlook themes will have low contrast with some folder colors. \n To change the color of a folder, a user can hover over the folder name, select the three-dot menu, select Change color and then choose a color. \n To turn off the color, follow the same process, and select Automatic. \n The folder color will display in the list of folders and in Favorites if the colored folder is added to Favorites. \n \n What you need to do to prepare: \n This rollout will happen automatically by the specified date with no admin action required before or after 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. \n #newoutlookforwindows \n MC981624 — Microsoft Outlook name change: \"Outlook (new)\" on Windows will change to \"Outlook\" \n Coming soon: The installed name for new Microsoft Outlook for Windows will change from \"Outlook (new)\" to \"Outlook.\" \n This rollout comes after a change to the classic Outlook in version 2407, previously announced in MC803006 (Update) Outlook for Windows display name change (published June 2024, updated August 2024), which added \"(classic)\" to the installed name to differentiate the two apps. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early February 2025 and expect to complete by late February 2025. \n What you need to do to prepare: \n Outlook in the Windows Start menu. Left: Before the name change. Right: After the name change: \n \n This change will be on by default. This part of the app identity is not customizable for organizations. \n As always, we recommend planning your organization's migration to the new Outlook using the resources at https://aka.ms/newOutlookAdoption \n 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. \n #newoutlookforwindows \n MC974362 — (Updated) Secure/Multipurpose Internet Mail Extensions encryption support in new Outlook for Windows \n Microsoft 365 Roadmap ID 397891 \n Updated January 21, 2025: After further review, we will not be rolling this out to 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. \n We are rolling out fundamental Secure/Multipurpose Internet Mail Extensions (S/MIME) support for primary accounts in new Outlook. With this new feature, new Outlook will start supporting sending and reading signed and encrypted emails. \n In new Microsoft Outlook, this option is available in Options > More Options. \n When this will happen: \n General Availability (Worldwide): We began rolling out mid-December 2024 and expect to complete by late January 2025. \n General Availability (GCC): We will begin rolling out early February 2025 and expect to complete by mid-February 2025. \n General Availability (GCC High, DoD): We will communicate via Message center when we are ready to proceed. \n How this will affect your organization: \n If your organization is not using New Outlook this will not impact you. \n If your organization does not have S/MIME setup for your users, this will not impact you. \n If your organization is currently using S/MIME, you will soon see controls to apply S/MIME encryption when signing into new Outlook. Similarly, you will be able to verify, sign, decrypt, and reply to S/MIME emails. \n What you need to do to prepare: \n 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. \n Users with S/MIME certificates on their machine or Smart Card will be able to use this new feature in new Outlook. \n Learn more: Overview of the new Outlook for Windows \n MC960818 — (Updated) Microsoft Outlook for iOS/Android: New reporting buttons integrated with Microsoft Defender for Office 365 \n Microsoft 365 Roadmap ID 371383 \n Updated January 29, 2025: We have updated the content. Thank you for your patience. \n Coming soon for Microsoft Outlook for iOS/Android: New built-in report buttons in version > 4.2446. Admins can control the appearance and behavior of these buttons that allow users to report emails as phishing / junk / not junk from the User Reported setting page 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. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We began rolling out in early December 2024 and expect to complete by late January 2025. \n How this will affect your organization: \n Information to keep in mind: \n \n Microsoft OWA (Outlook on the Web) and the new Microsoft Outlook for Windows have had this functionality since November 2022. This rollout to iOS/Android does not change or affect that functionality. \n Classic Microsoft Outlook for Windows client has had this functionality in current channel since August 2024. Learn more: MC841229(Updated) Classic Microsoft Outlook for Windows: New reporting buttons integrated with Microsoft Defender for Office 365 (published July 2024, updated October 2024). \n Microsoft Outlook for Mac released this functionality in September 2024. \n If you have turned off the reporting feature in the Microsoft 365 Defender User reported settings page or are using a third-party add-in, the report buttons in Outlook for Android/iOS won't be visible. \n The Microsoft reporting add-in (the Microsoft report message add-in and Microsoft phishing add-in) will be supported till further notice. The future goal is to have a consistent button reporting experience across all Outlook platforms. If you are using Microsoft reporting add-ins in Outlook for iOS/Android, your users will see two reporting experiences: one from the built-in Outlook buttons (added by this rollout) and one from the add-in. Both options will behave the same for users (except for the newly customizable pop-ups) and the reported messages will end up in the same place, causing minimal disruption. \n 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 your User reportedsettings. \n Like OWA and new Outlook for Windows, the built-in reporting button in Outlook for iOS/Android supports reporting from shared and delegate mailboxes. \n \n This change is available by default. \n What you need to do to prepare: \n 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. \n No action is required form you after this rollout because your current settings in the User reported settings page will not be changed. \n Learn more \n \n Report phishing and suspicious emails in Outlook for admins - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout) \n User reported settings - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout) \n \n MC947045 — (Updated) Microsoft Outlook for iOS and Android: Attach emails while composing an email \n Microsoft 365 Roadmap ID 464206 \n Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for Microsoft Outlook for iOS and Android users: In response to customer requests, we are rolling out the ability to attach emails directly in the compose window. This enhancement allows users to include individual emails as attachments in new messages, facilitating seamless sharing and providing more context for recipients. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out late January 2025 (previously early January) and expect to complete by late February 2025. \n How this will affect your organization: \n Before this rollout, users can forward emails as attachments but cannot attach emails while composing. \n After this rollout, users will notice a new Attach email option when they select the paper clip attachment icon in the compose window. Users can select this option to browse for, choose, and attach individual emails to their new message. \n This change is available by default. \n What you need to do to prepare: \n This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change, update relevant documentation. \n MC882252 — (Updated) New Microsoft Outlook for Windows: Sharing Word, Excel, and PowerPoint local files through email \n Microsoft 365 Roadmap ID 397094 \n Updated January 23, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon to new Microsoft Outlook: Users will be able to share Microsoft Word, Microsoft Excel and Microsoft PowerPoint files stored on their device (not stored in a cloud like Microsoft OneDrive) from new Outlook for Windows. \n When this will happen: \n General Availability (Worldwide, GCC): We will begin rolling out early October 2024 (previously mid-September) and expect to complete by late August 2025 (previously late December). \n How this will affect your organization: \n Before this rollout, users are only able to see old Outlook for Windows when they try to share a Word, Excel or PowerPoint fie. \n After this rollout, when users want to share a Word, Excel, or PowerPoint file that is saved to their device (not stored in a cloud like Microsoft OneDrive), the user can right-click the file name in File Explorer, select Share, and select new Outlook for Windows to email the file. \n This option is on by default. \n What you need to do to prepare: \n 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. \n MC847877 — (Updated) Microsoft Outlook for iOS and Android: Choose fonts while composing \n Microsoft 365 Roadmap ID 409969 \n Updated January 9, 2025: We have updated the rollout timeline below. Thank you for your patience. \n 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. \n When this will happen: \n General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-November 2024 (previously mid-October) and expect to complete by late January 2025 (previously early December). \n How this will affect your organization: \n When this update rolls out, users will be able to select fonts to use in emails, signatures, automatic replies, and calendar invitations. \n What you need to do to prepare: \n You might want to notify your users about this new capability and update your training and documentation as appropriate. \n MC799635 — (Updated) Microsoft Outlook: Add shared folders to Favorites \n Microsoft 365 Roadmap ID 388913 \n Updated January 16, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Coming soon for new Microsoft Outlook for Windows and Outlook for web: Users will be able to add shared folders to their Favorites list in the top left corner of the screen. This message does not apply to Outlook for Mac or Outlook for mobile devices. \n When this will happen: \n Targeted Release: We will begin rolling out early February 2025 (previously early January) and expect to complete by early March 2025 (previously early February). \n General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early March 2025 (previously early February) and expect to complete by early April 2025 (previously early March). \n How this will affect your organization: \n 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. \n What you need to do to prepare: \n 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. \n Learn more: Open and use a shared mailbox in Outlook - Microsoft Support \n Exchange Online \n MC982553 — Microsoft Exchange Online: Search-MailboxAuditLog and New-MailboxAuditLogSearch will retire \n We will retire the Search-MailboxAuditLog and New-MailboxAuditLogSearch cmdlets in Microsoft Exchange Online starting March 1, 2025, and completing in late March 2025. After the retirement, new records will be written to Search-UnifiedAuditLog and Search-MailboxAuditLog will be accessible only as a historical record. \n How this will affect your organization: \n After the retirement, admins will be able to access Search-MailboxAuditLog and New-MailboxAuditlogSearch and make changes and downloads until late June 2025. After late June, Search-MailboxAuditLog and New-MailboxAuditlogSearch will become a static record only, and admins will no longer be able to make changes and downloads. \n What you need to do to prepare: \n This change will happen automatically by the specified dates. Please notify your users about this change, update your relevant documentation, and share the alternate capability Search-UnifiedAuditLog. \n To use the Search-UnifiedAuditLog cmdlet, you must ensure auditing is enabled for your tenant. \n Learn more about enabling auditing for your tenant and about the changes to these cmdlets: Microsoft Exchange Online: Search-MailboxAuditLog and New-MailboxAuditLogSearch will retire | Microsoft Community Hub \n MC902782 — (Updated) Exchange Online token deprecation plan \n Updated February 3, 2025: We have updated the content. \n This is a reminder that starting February 17th, legacy Exchange Online user identity and callback tokens will be turned off across all Microsoft 365 tenants. This impacts all Outlook add-ins that request a legacy Exchange Online token to identify the user or make Exchange web services (EWS) calls. This change only applies to Exchange Online and doesn’t apply to Exchange on-premises. \n Recommended actions \n \n Identify any add-ins that are impacted.Determine if your tenant has any deployed Outlook add-ins that are impacted by this change. For more information, see Which add-ins in my Organization are impacted. \n Contact add-in publishers.Microsoft has worked with many Outlook add-in publishers to update their add-ins to use Entra ID tokens and Microsoft Graph. If you identify any impacted add-ins on your tenant, we recommend that you reach out to the publishers of those add-ins to learn more about their plans to update. \n \n Can I opt out of this change? \n You can opt out of the February 17th change if all the following are true. \n \n Your tenant has add-ins impacted by this change. \n The impacted add-ins will not be updated to no longer use legacy Exchange Online tokens by February 17th. \n The add-ins are necessary for your organization. \n \n To opt out, run a command to set legacy Exchange Online tokens to remain on. It takes up to 24 hours for the command to take effect. If you turn tokens on before February 17th, your tenant will be exempt from the February 17th change. Tokens will remain on until June 2025 or until you explicitly turn them off. \n What happens on February 17th? \n Microsoft will begin deploying a change to all users worldwide in Microsoft 365 tenants that will turn off the issuance of legacy Exchange online tokens. The deployment will take several weeks to deploy to all users. If an Outlook add-in requests a legacy Exchange token, and token issuance is turned off, the add-in will receive an error. Outlook add-ins that still request legacy Exchange Online tokens will be broken by this change. Please note that even after legacy tokens are turned off, already issued legacy tokens will continue to be valid for approximately 24 hours. \n Note that since the change is applied per user, and deployed over several weeks, you could see some user’s affected while others are not. \n Where do I get more information? \n The Outlook legacy tokens deprecation FAQ is updated regularly and contains information about tools and how to upgrade add-ins. We recommend you refer to the Q&A section for Microsoft 365 administrators. We also recommend you share the FAQ with any developers in your organization that need to update LOB Outlook add-ins using legacy Exchange Online tokens. \n Additional resources \n \n Turn legacy Exchange Online tokens on or off \n Legacy Exchange Online token deprecation FAQ \n Enable single sign-on in an Office Add-in with nested app authentication \n NAA Outlook sample \n \n MC886603 — (Updated) Reject multiple From addresses (P2 From headers) without a Sender header \n Updated January 31, 2025: We are proactively opting tenants out of the rollout that were detected as sending high volumes of emails exhibiting multiple From addresses without a Sender address header. These exempted senders will only be able to send emails exhibiting multiple From addresses without a Sender address header to recipients belonging to the same tenant as the sender. We will provide a subsequent update by the end of February with an updated timeline for tenants that are opted out. \n Starting February 3 (previously December 1), we're going to start gradually dropping messages that have multiple From addresses (also known as P2 From headers) without a Sender header from being processed via Exchange Online. \n If we see significant traffic exhibiting multiple From addresses (P2 From headers) without a Sender header in your tenant in the month of September, we will send you a Message Center Post by October 15th alerting you and providing some sample message IDs. \n We are doing this to comply with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2) which mandates the Sender header to be present and contain a single address if the From header has more than one address. Noncompliance with this could be exploited by attackers, allowing them to impersonate a sender address by misleading the client into using the From header to determine the sender instead of the Sender header. \n When this will happen: \n February 3, 2025 (previously December 1st) \n We are delaying the rollout start date from December to February 3rd 2025 in order to provide more time to customers for investigating messages exhibiting multiple P2 From Addresses without a Sender Address. \n Most of the traffic exhibiting multiple P2 From Addresses without a Sender Address will be inbound spam destined for your tenant sent by malicious spammers on the internet. \n Some customers are sending legitimate emails with this malformed header configuration. On October 15, we sent a targeted MC post to customers showing high volumes of messages exhibiting multiple P2 From Addresses without a Sender Address as they may be impacted by this change. \n For investigating if you will be impacted by this change, focus your investigation on messages sent using On Premises Inbound Connectors to Exchange Online. Authenticated mail submission is not impacted because submitting messages like this using those submissions are not allowed (Graph, Outlook clients, SMTP AUTH Client Submission). \n How this affects your organization: \n If email clients including devices and applications that you use to send messages, do so using multiple From addresses but without a Sender address header after December 1st, you will get an NDR error code 550 5.1.20 “Multiple From addresses are not allowed without Sender address’”. \n What you can do to prepare: \n When this change is in effect, if you need to send a message that has more than one email address in the From field, make sure that you have a single email address in the Sender header. \n If you expect this change to cause any issues for your organization, please share that feedback. \n Microsoft 365 \n MC986516 — Microsoft Forms | Data sync to Microsoft Excel: migrating from the older solution to the new solution \n We will be retiring the old data sync feature from Microsoft Forms in GCC. Instead, we recommend new live data sync to Excel solution. \n Note: You may have received MC943681 (November '24) if we had identified that your tenant utilized legacy data sync between August '24 and October '24. \n When this will happen: \n We will begin rolling out the change on February 13, 2025, and expect to complete by February 27, 2025. \n How this will affect your organization: \n Users who rely on the older version to sync data from Forms to Excel will need to manually update the data sync to the new solution. After the old data sync solution has been deprecated, existing Excel workbooks using the old data sync solution will no longer receive new responses. Users can still migrate these existing Excel workbooks to the new data sync solution to receive new responses when needed. \n \n For each form using the old syncing solution, users can migrate the form according to the instructions provided in Forms and Excel for the web. More details can be found here: Update to the new solution for syncing forms responses to Excel - Microsoft Community Hub. \n If users are using the old data sync solution in a workflow that relies on the Excel workbook being updated automatically without any user action, they will be impacted by the change as the Excel file will only get updated when it’s opened in a supported Excel client. These users will have to manually update their workflow. Our suggested solution is to use Power Automate: Setting Up an Automated Workflow Between Microsoft Forms and Excel Through Power Automate - Microsoft Support \n \n Note: \n \n The older version of the data sync exists in group forms created with Microsoft 365 Groups. \n The new data sync can only be triggered in Excel for the web. If users want to receive new Forms response data in the Excel desktop app, open the file in Excel for the web, and then wait for the desktop app file to sync from the web file. (Support for other versions of Excel is in progress.) \n The new data sync solution will be on by default and available to all Forms and Excel for the web customers. \n \n What you need to do to prepare: \n \n Share the migration solution if users report they cannot get Forms data updated in Excel. \n Learn more: Introducing Forms data sync to Excel - Microsoft Community Hub \n \n 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. \n MC980798 — Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) \n Microsoft 365 Roadmap ID 475046 \n Python in Excel allows you to bring the capabilities of Python directly into the Microsoft Excel grid. With this rollout, Python in Excel with standard compute will be generally available in Excel for Windows. \n When this will happen: \n General Availability (GCC): We will begin rolling out to Excel for Windows mid-February 2025 and expect to complete by early March 2025. \n After we complete the rollout to Excel for Windows, we will send a separate message with the timeline for rolling out this change to Microsoft Excel for the web and Microsoft Excel for Mac. \n How this will affect your organization: \n After this rollout, eligible users will be able to add Python formulas to their workbooks without any installation required. These Python formulas will be run by Excel in a secure container on the Microsoft Cloud with enterprise-level security and with standard compute. With this release, eligible Excel users with a Microsoft 365 Copilot license will also be able to use the Copilot in Excel with Python feature, enabling them to leverage the capabilities of AI and Python in Excel for deeper data analysis. \n Note: Some premium Python compute will be included with each user’s Microsoft 365 subscription each month, giving them limited access to faster calculation speeds. After they have used all of their premium compute, they can continue to use the Python in Excel feature with standard Python compute. To get more premium compute, admins will be able to purchase the Python in Excel add-on license for their users after it becomes available later this year for GCC. We will send a separate message with the timeline for the rollout of the Python in Excel add-on license. \n An example of a Python formula in an Excel workbook: \n \n The Python in Excel feature will be enabled by default. \n What you need to do to prepare: \n To learn more about Python in Excel, please review the Python in Excel documentation. To learn more about data security: Data security and Python in Excel - Microsoft Support \n 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 relevant documentation. \n MC833890 — (Updated) Microsoft Word, Excel, PowerPoint: Protect sensitive files with dynamic watermarking \n Microsoft 365 Roadmap ID 400717 \n Updated January 24, 2025: We have updated the rollout timeline below. Thank you for your patience. \n Update December 20, 2024: There is an issue causing users to get an access denied error when attempting to open files for which they are not the RMS owner, when the file has a sensitivity label configured for dynamic watermarking. We are working to resolve this issue. \n Dynamic watermarking is a new sensitivity label setting that will add watermark text containing the consuming user’s information onto content in files created in Microsoft Word, Excel, and PowerPoint. Sensitivity labels from Microsoft Purview Information Protection help you classify and protect your organization's data. Learn more: (Preview) Dynamic watermarking for sensitivity labels in Word, Excel, and PowerPoint - Microsoft Community Hub \n This message applies to Word, Excel, and PowerPoint on the web, Desktop/Windows, Mac, Android, and iOS platforms. \n When this will happen: \n Public Preview: We will begin rolling out mid-July 2024 and expect to complete by early August 2024. \n General Availability (Worldwide): We will begin rolling out to Current Channel mid-January 2025 (previously mid-November) and expect to complete by late February 2025 (previously late January). \n The rest of the channels will follow in line with their normal cadence. \n How this will affect your organization: \n Before the rollout: Admins are not able to configure dynamic watermarking though sensitivity labels in Word, Excel, and PowerPoint. \n After the rollout, refer to the admin documentation to configure dynamic watermarks in your tenant. This feature is off by default. Admins must configure the feature before it is accessible to users. \n What you need to do to prepare: \n 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. \n Learn more \n \n Apply encryption using sensitivity labels | Microsoft Learn \n (Preview) Dynamic watermarking for sensitivity labels in Word, Excel, and PowerPoint - Microsoft Community Hub \n \n \n Documentation - Office 365 IP Address and URL web service \n January 30. 2025 - GCC \n January 30. 2025 - GCC High \n January 30. 2025 - DOD ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"231757","kudosSumWeight":0,"repliesCount":0,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUlvZFpkag?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLW5kd20wSA?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDM","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXEyZ0N3bw?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDQ","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLThleEJuVQ?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDU","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWZGTkRqQQ?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDY","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUI1b0p2Tw?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDc","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLW5pazVhVw?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDg","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTNEWGIzdQ?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDk","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLW5qUzEwZQ?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDEw","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWhCZGVaMQ?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDEx","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUczTzJEbA?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDEy","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUh6V1h5Nw?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDEz","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLThjeTBydg?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE0","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXZIVlZOTg?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE1","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWFlaVBjbg?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE2","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUw2TXhqVw?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE3","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTExblZGQw?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE4","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTh3TkxpeA?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE5","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUlNWXd1OQ?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDIw","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXAxclNjUg?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDIx","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUV2RTB1cg?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDIy","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXJ6TTFWSw?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDIz","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLXdsNjl3ag?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI0","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLWpLQTEydg?revision=7\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI1","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLTJOeFBmOA?revision=7\"}"}}],"totalCount":51,"pageInfo":{"__typename":"PageInfo","hasNextPage":true,"endCursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI1","hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":{"__typename":"UploadedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00Mzg0MzMyLUlvZFpkag?revision=7"},"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"BOTTOM","altText":""}},"Conversation:conversation:4225436":{"__typename":"Conversation","id":"conversation:4225436","topic":{"__typename":"BlogTopicMessage","uid":4225436},"lastPostingActivityTime":"2025-03-03T10:09:22.979-08:00","solved":false},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LTYxMjYwNWlCREREQ0JBMkMxNTdDRkUx?revision=27\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LTYxMjYwNWlCREREQ0JBMkMxNTdDRkUx?revision=27","title":"Service Offering Differentiation - Animated - August 2024.gif","associationType":"TEASER","width":800,"height":371,"altText":"Service Offering Differentiation - Animated - August 2024.gif"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LUc3WmVLbg?revision=27\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LUc3WmVLbg?revision=27","title":"image.png","associationType":"BODY","width":1447,"height":1183,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LVo4emdqTg?revision=27\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LVo4emdqTg?revision=27","title":"image.png","associationType":"BODY","width":900,"height":792,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LXc0dmt4Nw?revision=27\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LXc0dmt4Nw?revision=27","title":"image.png","associationType":"BODY","width":2161,"height":1348,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LXJVUTZ4TQ?revision=27\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LXJVUTZ4TQ?revision=27","title":"image.png","associationType":"BODY","width":1122,"height":603,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LUFGTFhaOA?revision=27\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LUFGTFhaOA?revision=27","title":"image.png","associationType":"BODY","width":1125,"height":538,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LTYxMzAyMWk1RjMxREJGQUYzRDQ5QzNE?revision=27\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LTYxMzAyMWk1RjMxREJGQUYzRDQ5QzNE?revision=27","title":"RichardWakeman_5-1724352499036.jpeg","associationType":"BODY","width":999,"height":761,"altText":"RichardWakeman_5-1724352499036.jpeg"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LXdJUVhwWA?revision=27\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LXdJUVhwWA?revision=27","title":"image.png","associationType":"BODY","width":1125,"height":601,"altText":""},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LVpid0xjUw?revision=27\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LVpid0xjUw?revision=27","title":"image.png","associationType":"BODY","width":1064,"height":506,"altText":""},"BlogTopicMessage:message:4225436":{"__typename":"BlogTopicMessage","subject":"Understanding Compliance Between Commercial, Government, DoD & Secret Offerings - Feb 2025 Update","conversation":{"__ref":"Conversation:conversation:4225436"},"id":"message:4225436","revisionNum":27,"uid":4225436,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:276160"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":" \n 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. ","introduction":"","metrics":{"__typename":"MessageMetrics","views":37636},"postTime":"2024-09-23T07:59:10.025-07:00","lastPublishTime":"2025-03-03T10:09:22.979-08:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" This article is the second of a series in the Microsoft Tech Community Public Sector Blog and touches on several key principles for compliance, including data residency versus data sovereignty. For the first article in the series, please refer to History of Microsoft Cloud Service Offerings leading to the US Sovereign Cloud for Government. To keep this article concise, I will refrain from repeating content from the first. I recommend that you review the first article if you are unfamiliar with the architectural relationships between Azure, Microsoft 365 and Dynamics 365.In this article, we will focus on each of the US-based cloud offerings from Microsoft and compare the differences in compliance, including the compendium of common factors customers may use to decide which of our offerings align with current and future requirements in demonstrating compliance with US Government regulations and underlying cybersecurity frameworks. \n February 2025 Update - Access this article with the short URL https://aka.ms/MSGovCompliance \n Microsoft 365 Commercial + Azure Commercial \n \n FedRAMP in Azure \n The Federal Risk and Authorization Management Program (FedRAMP) is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. FedRAMP enables government agencies to accelerate the adoption of cloud services with confidence, knowing they meet high security standards and comply with federal regulations. FedRAMP authorization is a rigorous and comprehensive process that involves extensive documentation, testing, and auditing by independent third-party assessors (3PAO). FedRAMP authorization demonstrates Microsoft’s commitment to delivering cloud services that meet the most stringent security and compliance requirements of the US Government. \n You can demonstrate compliance with the FedRAMP High Impact Level in both Azure Commercial and Azure Government. Azure Commercial and Azure Government each have a Provisional Authorization to Operate (P-ATO/PA) from the FedRAMP Program Management Office (PMO). The PMO is the primary governance and decision-making body for FedRAMP. Representatives from the Department of Defense, the Department of Homeland Security, and the General Services Administration serve on the PMO board. The PMO grants a P-ATO to Cloud Service Providers (CSP) that have demonstrated FedRAMP compliance and may chose not to pursue an Agency ATO as they are not mutually exclusive. \n You can find a full list of Azure services that meet the requirements of FedRAMP High in the Azure compliance scope documentation. \n For more information, please reference: \n \n Microsoft FedRAMP Documentation (https://aka.ms/fedramp) \n FedRAMP Package F1209051525: Azure Commercial Cloud | FedRAMP Marketplace \n FedRAMP Package F1603087869: Azure Government (includes Dynamics 365) | FedRAMP Marketplace \n \n FedRAMP in Microsoft 365 \n Cloud services bundled together in Microsoft 365 are split into two separate sets of authorizations, Office 365 and Azure. \n The Office 365 productivity services include: \n \n Activity Feed Service (AFS) \n \n Information Protection (IP) \n \n Office Service Infrastructure (OSI) \n \n Cloud Input Intelligence (CII) (aka Windows Ink) \n \n Microsoft Teams (MS Teams) \n \n Office for Web \n \n Customer Insight and Analysis (CIA) (aka Usage Reports) \n \n ObjectStore \n \n People Card \n \n Exchange Online (EXO) \n \n Office 365 Remote Access Service (ORAS) \n \n Query Annotation Service (QAS) \n \n Falcon \n \n Office 365 Suite User Experience (SUE) \n \n Search Content Service (SCS) \n \n Hauk \n \n Office Intelligent Services (IS) \n \n SharePoint Online (SPO) \n including Project Online and OneDrive for Business \n \n \n All other services fall under Azure including (but not limited to) : \n \n \n Entra ID (Azure Active Directory) \n \n Microsoft Cloud App Security \n \n Azure Multi-factor Authentication (MFA) \n \n Azure Information Protection \n \n Microsoft Defender Advanced Threat Protection (MDATP) \n \n Microsoft Stream \n \n Azure Key Vault \n \n Microsoft 365 Defender \n \n Microsoft Defender Vulnerability Management \n \n Azure Sentinel \n \n Microsoft PowerApps \n \n Microsoft Purview \n \n Intune \n \n Microsoft Stream \n \n Microsoft Secure Score \n \n Microsoft 365 Defender \n \n Power BI \n \n Many more… Azure compliance scope \n \n For the cloud services listed as in scope for Azure Commercial, we have the FedRAMP P-ATO as described in the previous section. \n For the productivity services listed as in scope for Office 365 Commercial, Microsoft does not support FedRAMP. For those that have read previous versions of this blog, you may find it as a surprise that Microsoft 365 in Commercial has changed from FedRAMP High ‘Equivalent’ to ‘No’. This changed as a result of the release of the U.S. Department of Defense memorandum for ‘FedRAMP Moderate Equivalency for Cloud Service Provider’s Cloud Service Offerings’ dated December 21, 2023. The memo outlines requirements to achieve ‘Equivalency’ including a Body of Evidence (BOE) that is not in scope for Office 365 Commercial data enclaves other than for Microsoft 365 Government (GCC). \n For more information, please see the section below FedRAMP in GCC. \n The FedRAMP Marketplace for ‘Microsoft - Office 365 Multi-Tenant & Supporting Services’ only applies to GCC and no other data enclaves of Microsoft 365 Commercial. \n The accreditation package for ‘Microsoft - Office 365 Multi-Tenant & Supporting Services‘ defines the scope of accreditation as covering the cloud services management plane and a dedicated portion of the data plane. This often confuses customers as the whole of the Commercial service is not within the accreditation boundary; only the data enclave for GCC as defined to support the accreditation package. Any customer deciding to use the Microsoft 365 Commercial service to demonstrate FedRAMP compliance or equivalency will struggle to achieve this due to how the accreditation scope is defined. In other words, the accreditation package and associated Body of Evidence (BOE) only includes the scope of accreditation for GCC. \n You may wonder why the scope is different? Take access controls as an example. While the same access controls may be applied to any Commercial service data enclave (the whole of the data plane); they are applied with different Organizationally Defined Values (ODV). Both Commercial and GCC data enclaves require personnel screening validations that are tied to access control requirements: \n \n Commercial screening does not require US Citizenship and other US Government related requirements necessary to support the management of US government regulated data (e.g. Controlled Unclassified Information). \n GCC screening does include these requirements and validates their existence prior to any access control action. \n \n Such differences make the Commercial service untenable for Microsoft 365 to support FedRAMP holistically in the Commercial service. \n For context of what a ‘data enclave’ is, please refer to the History of Microsoft Cloud Service Offerings leading to the US Sovereign Cloud for Government. \n A word about FedRAMP in Commercial and how it relates to CUI \n A common misconception by many is regarding FedRAMP as ‘the’ requirement to protect Controlled Unclassified Information (CUI) in a cloud service offering. It is important to note that FedRAMP is just one component of overall compliance relative to CUI in a shared responsibility model. For example, the CUI-Specified category for ‘Export Controlled’ (CUI//EXPT) such as for data regulated by the International Traffic in Arms Regulation (ITAR) imposes an additional set of ‘Specified’ standards from the US Department of State that requires data sovereignty (e.g. US persons in US locations). Export-Controlled data such as ITAR technical data is one of the components of overall compliance to holistically safeguard CUI. \n I often get pulled into customer conversations on suitability for CUI in the Microsoft 365 Commercial cloud. While a very nuanced conversation (especially working with sub-contractors and supplier hosted in Commercial), Microsoft does not recommend it. Why? We did not create Microsoft 365 Commercial to support the management of CUI. Thus, in the table above for Microsoft 365, you can observe that CUI is presented as ‘No’. \n The way I frame this out for customers is this: your higher watermark for compliance to gain coverage of CUI is in alignment with other controls above and beyond FedRAMP. If you are affiliated with law enforcement and the criminal justice system, you will likely require CJIS adjudication from the FBI or from the US State you are in. If you are affiliated with the Internal Revenue Service or Department of Revenue, you will likely require IRS 1075 for coverage of Federal Tax Information. If you are affiliated with US Defense or Military, you will likely require export controls that include the ITAR and Export Administration Regulations (EAR). Each one of these require screened US Persons and data residency/sovereignty in the Continental United States (CONUS). These are what will direct you to our Government cloud offerings and diminish Microsoft 365 Commercial as an option. \n Note: There is an entire article for Microsoft US Sovereign Cloud Myth Busters - CUI Effectively Requires Data Sovereignty \n New Feature Releases in Commercial \n Here is another aspect of Commercial to keep in mind. The release of new features and services into Commercial clouds is not predicated on FedRAMP compliance the same way it is for release into Government clouds. For example, a new feature can release to Commercial cloud tenants before it has FedRAMP compliance. However, the new feature will not be released as Generally Available (GA) in Government cloud tenants until it complies with FedRAMP. In my opinion, this is another compelling data point for our customers trying to decide on ‘Commercial vs Government’, as there is a risk of users organically adopting new features in your tenant before the features are authorized for FedRAMP. \n Note: First-party products and features developed by Microsoft follow the NIST SP 800-53 control framework out of the starting gate, accelerating the path to FedRAMP authorization and reducing the risk of using such features before authorization. However, this may not hold true for all products we ingest through 3rd-party acquisitions and partnerships that could require a much heavier lift to achieve the same levels of compliance. \n Microsoft’s Secure Future Initiative (SFI) makes security our top priority at Microsoft, above all else—over all other features. We have evolved our security approach, with our work guided by the following three security principles: \n \n Secure by Design: Security comes first when designing any product or service. \n Secure by Default: Security protections are enabled and enforced by default, require no extra effort, and are not optional. \n Secure Operations: Security controls and monitoring will continuously be improved to meet current and future threats. \n \n I invite you to read Charlie Bell’s blog on Secure Future Initiative (SFI), as it has been driving security that is helpful for compliance as well. \n DFARs 7012 and NIST SP 800-171 in Microsoft 365 Commercial \n This is for the Defense Industrial Base (DIB) including Aerospace and Defense (A&D) contractors of the US Department of Defense (DoD). It also applies to Federally Funded Research and Development Centers (FFRDCs), University Affiliated Research Centers (UARCs), energy and healthcare organizations. To substantially contract with the DoD, you will likely need to demonstrate compliance with the Defense Federal Acquisition Regulation supplement 252.204-7012 (DFARs 7012). If you have the requirement, your contracts will have a DFARs 7012 Clause, or you will be notified of a ‘flow-down’ in sub-contracts to you. DFARs 7012 mandates the protection of CUI and Covered Defense Information (CDI) with an implementation of NIST SP 800-171, and FedRAMP Moderate ‘or Equivalent’ Impact Level for clouds used to store, process, or transmit CUI. It is a set of controls that are used to secure Non-Federal Information Systems (predominately in the private sector). \n Due to not supporting FedRAMP in Microsoft 365 Commercial, you will observe a ‘No’ for DFARs 7012. \n DFARs 7012 in Azure Commercial \n As mentioned in the previous section, Microsoft 365 Commercial has a ‘No’ for DFARs 7012. However, Azure Commercial can demonstrate support for DFARS clause 252.204-7012. We have an auditor’s attestation letter summarizing how DFARS 7012 is supported for Azure services. This translates to a commitment where we demonstrate DFARs 7012 compliance in Azure Commercial. \n Note: For more details on how we implement DFARs 7012 in Azure, please see https://aka.ms/DFARsAzure. \n The coverage of DFARs 7012 in Azure Commercial offers you more choice in the selection of Microsoft cloud offerings that best suit your requirements for the protection of CUI. For example, those organizations that choose Microsoft 365 Government (GCC) deployed on top of Azure Commercial cloud regions in the US may now have paired Azure services that meet DFARs 7012 requirements. While we do not offer this same commitment for Microsoft 365 Commercial, we do offer DFARs 7012 compliance in Microsoft 365 Government (GCC) that operates in conjunction with Azure Commercial. See below for more details in the GCC section. \n Commercial will not always recognize US Government requirements \n As I mentioned, there are guidance, operational and support differences between the services provided for Azure Commercial and Microsoft 365 Commercial, as opposed to those purpose built for the US Government. There is no way to identify a government tenant within the Commercial service. \n Unfortunately, there is a painful learning curve when a customer discovers this post sale/deployment while in the middle of an incident. I have been on calls assisting such customers that were routed through our global support staff and were frustrated that ‘Microsoft’ did not understand that they had US Government requirements and should not have been routed to offshore support personnel in Asia. That is how the global Commercial service works. If you have requirements for screened US persons in US locations, there are Microsoft purpose-built cloud offerings exclusively for supporting US Government obligations that are more suitable to sovereignty requirements. See below in the GCC High + Azure Government section on support commitments for US persons. \n Regulation Changes Impact to Commercial versus Government \n Recent updates to FedRAMP “Equivalency” requirements highlight the ongoing evolution of U.S. government standards and regulations. Industry has an obligation to mature cloud service offerings and consumption practices to match and even exceed these security and compliance requirements set forth by the US government (and preferably as proactively as possible to reduce undue churn and reactive burdens). While Microsoft strives to align all our cloud service offerings to the same set of security controls and practices as reasonably practical, Commercial services achieving government certifications like FedRAMP should not be presumed unless specifically stated. It's crucial for customers to stay informed about these changes to avoid non-compliance risks. \n FCI in Microsoft 365 Commercial \n In general, all US Government contractors have a requirement in their contracts to comply with 15 safeguarding requirements and procedures for Federal Contract Information (FCI) in the Federal Acquisition Regulations (FAR) 52.204-21 Basic Safeguarding of Covered Contractor Information Systems (FAR 21). You may demonstrate compliance for the FAR 21 in Commercial to protect FCI, but there is a caveat. Microsoft 365 Commercial is not intended for US Government requirements. There is a risk that changes in regulations may lead to non-compliance in the future. Ultimately, it is a risk decision your organization will need to make. \n Cybersecurity Maturity Model Certification (CMMC) \n One of the most common questions I get is, “What cloud offerings meet the requirements for CMMC”? \n Cybersecurity frameworks are applied to all Microsoft cloud offerings consistently across the spectrum of services. Cybersecurity 'maturity' is often represented as the efficacy of process and automation of practices. There are specific control requirements and ODVs that are unique to each cloud offering. For example, sovereign clouds such as Microsoft 365 Government (GCC High) and Azure Government have controls in place for restricting sensitive data access to only screened US persons with data processing, transmission and storage only within CONUS. Sovereign clouds are more restricted in terms of the specificity of control requirements in relation to other cloud environments. Even though control requirements may vary from one cloud environment to another, each may demonstrate a level of cybersecurity maturity in alignment with CMMC. \n In other words, you may demonstrate compliance with CMMC in the Commercial cloud depending on what level you are pursuing. CMMC by itself should not be the only decision factor on choosing which cloud offering is most appropriate. For example, CMMC 2.0 Level 2 and higher is intended for protection of CUI. I have captured details regarding CUI throughout this article to help you make a more informed decision. \n To net it out, Microsoft recommends the following: \n \n You may demonstrate compliance with CMMC 2.0 Level 1 for the data protection of FCI in Commercial and in our Government clouds. However, there is a caveat mentioned above that Microsoft 365 Commercial is not intended for US Government requirements. The safer long-term risk posture is to use our Government cloud service offerings. \n We recommend the US Sovereign Cloud with Azure Government and Microsoft 365 Government (GCC High) for data protection of CUI in alignment with CMMC 2.0 Levels 2-3. \n \n We understand you may have a different risk appetite and choose a different basis for your cybersecurity program. We do have customers that chose GCC (versus GCC High), in cases where they have CUI-Basic that does not require explicit commitments to protect CUI-Specified and ITAR/EAR export-controlled data. Others have added additional compensating controls, such as FIPS 140-2 validated end-to-end encryption to protect export-controlled data. However, many in the DIB (especially the larger tier 1 prime contractors) have chosen the US Sovereign cloud due to the comprehensive data protection offered holistically across all categories of CUI. \n Ultimately, this is a risk decision made by the customer in meeting their current and future requirements. \n It is important to note that while cost and risk are prime decision criteria for our customers, many also consider future changes to their business strategy and scope of competition. Our Government cloud offerings are segregated environments where it is neither a short nor inexpensive customer project to migrate from one to another. If opportunities arise in the future to pursue business requiring a higher watermark for compliance, or a potential increase of work in other regions or industries, you may promote such criteria to assess in a decision of which cloud to choose. There are many criteria to assess in such a decision, but we have attempted to portray the keys ones in context of this article. \n \n Microsoft 365 Government (GCC) \n \n Scope of Services in GCC \n The Microsoft 365 Government (GCC) cloud offering is a data enclave of Commercial. A data enclave in this context is a segregated environment, with infrastructure residing in Azure regions. In the case of GCC, the data enclave is in CONUS and paired with Azure Commercial US regions. There is a commitment to ensure data residency and data processing is in CONUS for the primary Office workloads. In addition, only screened US persons in US locations are authorized for customer content access. \n The service description for all Microsoft 365 Government offerings may be found at http://aka.ms/o365usgovservicedescription \n At the time of this writing, the service availability for GCC covered workloads are: \n \n Exchange Online & Exchange Online Protection \n SharePoint Online & OneDrive for Business Online \n Teams & Voice (Phone System & Audio Conferencing) \n Office for the web \n Microsoft Defender \n Power BI Pro \n Project Online \n and more as documented in the Service availability for each plan \n \n Given GCC is a data enclave of Commercial, there are several shared services. These shared services may have data processing globally Outside the Continental United States (OCONUS) and leverage a global follow-the-sun support model. Most notably, this includes a global network and a global directory. For example, Entra ID (formerly Azure Active Directory) in Azure Commercial is shared with GCC. Entra ID is supported globally and may have data processing (authentication) occur OCONUS along with service management by global support personnel. This is one of the reasons Microsoft will not commit to export controls in GCC. \n As a result, you will observe a ‘No’ in the column for ITAR & EAR for GCC along with a caveat for CMMC Levels 2-3. \n Customer Support for GCC and Azure Commercial \n Microsoft 365 Government (GCC) customer support is provided under the same terms and conditions offered to Microsoft 365 Commercial, without assurances for agent physical location nor citizenship. \n The latest version of the Customer Support Terms and Conditions for GCC (referencing the above statement) can be found here. \n GCC operates in conjunction with Azure Commercial, which is supported with a global follow-the-sun support model as well. For products and services that fall under Azure Commercial, such as IaaS and PaaS deployments in the same tenant as GCC, the Azure Product Terms outlines coverage for customer support. \n Many people are confused by this. After all, I mentioned above that GCC restricts access to restricted customer content to authorized screened US Persons only. This is true of datacenter personnel who request temporary permission elevation under management oversight, granting access to customer content only when necessary. While datacenter personnel are limited in their access to restricted customer content, customer support personnel have no direct standing access to the datacenter nor to customer content. They can only be exposed to sensitive information when it is provided directly by the customer during a customer support ticket. We remind you not to share any controlled, sensitive, or confidential information with support personnel as part of your support incident, and follow your own internal data sharing controls, policies and procedures when engaging with Microsoft customer support. \n Note: Microsoft Purview Customer Lockbox is a popular feature to moderate access to your data. We even have Customer Lockbox for Azure releasing to more and more Azure services. \n DFARs 7012 in GCC \n As mentioned in the section for DFARS 7012 in Commercial, this applies to the DIB, FFRDCs, UARCs, etc. working with the DoD. Ultimately, NIST SP 800-171 is holistically derived from NIST SP 800-53. Think of it as a subset of the controls that apply Non-Federal Information Systems. Given Microsoft uniformly implements NIST SP 800-53, in accordance with Appendix C of 800-171, we have coverage for NIST SP 800-171 controls in GCC. \n In addition to NIST SP 800-171, GCC and its pairing with Azure Commercial can demonstrate support for DFARS clause 252.204-7012 sub-paragraphs (c)-(g). We have an auditor’s attestation letter that shows on two pages summarizing how those sub-paragraphs are supported. Microsoft will support a flow-down for DFARs 7012 in GCC. This translates to a commitment where we demonstrate DFARs 7012 compliance in GCC. As a result of the flow-downs commitment, you will observe a ‘Yes’ in the GCC column for DFARs 7012. \n Note: For more details on how we implement DFARs 7012 in GCC, please see https://aka.ms/DFARsGCC. \n Controlled Unclassified Information is a Maybe in GCC \n The NIST SP 800-60 Volume 2 registry is rather large. There are many CUI categories, to include multiple information types. The question is, which CUI category is in scope? This is especially true for the DoD CUI Program Registry. Several categories may not require data sovereignty, such as Privacy, Legal, etc. Is it permissible to rely on data residency in GCC? Maybe. However, many of the CUI-Specified categories to include Defense, Export Controlled, Nuclear, etc. undoubtedly require the US Sovereign cloud and are not appropriate for storage within GCC. Ultimately, customers are responsible for ensuring they review the relevant regulations and Microsoft's offering prior to determining which Microsoft Government cloud service offering is the best fit to support their obligations for CUI. \n As not all CUI-Specified can be supported, you will observe a caveated ‘Yes’ in the GCC column for CUI. \n CMMC in GCC \n You may demonstrate compliance with CMMC 2.0 Level 1 in GCC for protection of FCI. You may also demonstrate compliance with CMMC 2.0 Levels 2-3 with notable caveats. The intent of CMMC 2.0 Levels 2+ is to safeguard CUI. As mentioned in the previous section, GCC is not permissible for all categories of CUI. Most notably, GCC does not support export-controlled data, such as ITAR and EAR natively. As such, we recommend the US Sovereign Cloud with Microsoft 365 Government (GCC High) and Azure Government for CMMC Levels 2-3 to holistically safeguard all categories of CUI. Please see the CMMC section above in Commercial for more rationale. \n You will observe a ‘Yes’ in the GCC column for CMMC L1. However, as not all CUI-Specified can be supported, you will observe a caveated ‘Yes’ in the GCC column for CMMC L2-3. \n FedRAMP in GCC \n For the productivity services listed as in scope for Office 365, you can demonstrate compliance with the FedRAMP High Impact Level in the GCC data enclave. At the time of this writing, we successfully completed multiple FedRAMP High Impact Level audits, including a Security Assessment Reports (SAR). This is sufficient for us advertising FedRAMP High ‘Equivalency’, as it completes Microsoft’s scope of responsibility towards FedRAMP accreditation for a Federal Agency ATO. In other words, we support accreditation with Federal agencies at the FedRAMP High Impact Level. \n Microsoft validates the controls for Office 365 into FedRAMP holistically because we operate all instances of Microsoft 365 employing a consistent control framework and uniform implementations of controls based on the US National Institute for Standards and Technology (NIST) Special Publication (SP) 800-53, Revision 5 (NIST SP 800-53 - a requirement of FedRAMP). \n The FedRAMP Marketplace for ‘Microsoft - Office 365 Multi-Tenant & Supporting Services’ lists our package with Agency ATOs from over 30 different Federal Government Agencies for FedRAMP Moderate Impact Level. In brief, this means the FedRAMP PMO has completed its review of one or more Agency ATOs. It also indicates the FedRAMP PMO is satisfied that Microsoft meets the FedRAMP requirements and had earned a listing on the Marketplace as ‘Authorized’. With the Agency ATOs in place, the FedRAMP PMO will not complete a P-ATO for Office 365 as that would be redundant to Agencies’ work and is not mutually exclusive. \n Together, the P-ATOs for Azure Commercial along with the Agency ATOs for Office 365 (GCC) provide holistic coverage for FedRAMP authorizations covering the Microsoft 365 Government (GCC) suite of cloud services. \n For more information, please reference: \n \n Microsoft FedRAMP Documentation (https://aka.ms/fedramp) \n FedRAMP Package MSO365MT: Office 365 Multi-Tenant & Supporting Services | FedRAMP Marketplace \n \n StateRAMP in GCC \n StateRAMP is a non-profit membership organization comprised of CSPs, government officials, and 3PAOs. The StateRAMP standard is based on the NIST 800-53, Revision 5 catalog of security controls along with FedRAMP, and enables state and local governments to manage third-party risk and verify cloud security. Cloud solutions that secure StateRAMP certifications are listed in its Authorized Products List. States that are required to have their own cybersecurity standards have extended reciprocity with the StateRAMP certification or adopted StateRAMP as their standard. Microsoft helped to develop the StateRAMP standard and continues to support its role in US state and local government cybersecurity. \n As mentioned above in the section on FedRAMP in Azure, both Azure Commercial and Azure Government each maintain FedRAMP High P-ATOs issued by the FedRAMP PMO in addition to Moderate and High Agency ATOs issued by individual federal agencies for the in-scope services. \n The following cloud service offerings have achieved the StateRAMP Authorized Security Status for the High Impact Level as shown on the Authorized Products List: \n \n Microsoft 365 Government (GCC) \n Azure Commercial \n Azure Government \n Dynamics 365 Commercial \n Dynamics 365 Government (GCC) \n \n For more information, please reference StateRAMP - Azure Compliance \n DoD CC SRG in GCC and Azure Commercial \n The Defense Information Systems Agency (DISA) is an agency of the DoD that is responsible for developing and maintaining the DoD Cloud Computing (CC) Security Requirements Guide (SRG). The SRG defines the baseline security requirements used by the DoD to assess the security posture of a CSP and establishes a baseline requiring a FedRAMP Moderate authorization for all information Impact Levels (IL). \n SRG Section 5.1.1 (DoD use of FedRAMP Security Controls) states that IL2 information may be hosted in a CSP that minimally holds a FedRAMP Moderate authorization. Given that Microsoft 365 Government (GCC) and Azure Commercial are both FedRAMP Moderate authorized (and higher), you may demonstrate compliance for IL2. As such, there is effectively ‘Equivalency’ between DoD CC SRG IL2 and FedRAMP Moderate. \n For more information, please see Microsoft SRG Documentation. \n Criminal Justice Information Services in GCC \n The most dominant tenant populations in GCC include State and Local Government (SLG) entities, such as highway patrol, sheriff, local law enforcement, etc. that require CJIS. The CJIS security policy provides 13 areas that should be evaluated to determine if cloud services can be used and are consistent with CJIS requirements. These areas correspond closely to the NIST SP 800-53 control implementation for FedRAMP Moderate with a security policy aligning with CJIS. \n Microsoft will sign the CJIS Security Addendum in states with CJIS Information Agreements. These tell state law enforcement authorities responsible for compliance with CJIS Security Policy how Microsoft's cloud security controls help protect the full lifecycle of data and ensure appropriate background screening of operating personnel with access to CJI. Microsoft continues to work with state governments to enter into CJIS Information Agreements. \n Microsoft has assessed the operational policies and procedures of Azure Government, Microsoft 365 Government (GCC), and Dynamics 365 Government (GCC), and will attest to their ability in the applicable services agreements to meet FBI requirements for the use of in-scope services. \n CJIS status in the United States \n \n 48 states and the District of Columbia with management agreements, highlighted on the map in green include: \n Alabama, Alaska, Arizona, Arkansas, California, Colorado, Connecticut, Delaware, Florida, Georgia, Hawaii, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, North Carolina, North Dakota, Oklahoma, Ohio, Oregon, Pennsylvania, Rhode Island, South Carolina, Tennessee, Texas, Utah, Vermont, Virginia, Washington, West Virginia, Wisconsin, and the District of Columbia. \n Microsoft's commitment to meeting the applicable CJIS regulatory controls allows Criminal Justice organizations to implement cloud-based solutions and be compliant with CJIS Security Policy V5.8. \n Current as of April 2024 - Criminal Justice Information Services (CJIS) Security Policy - Microsoft Compliance \n Note: This section also applies to CJIS in Azure Government as well. \n For information from the FBI: Security Control Mapping of CJIS Security Policy \n \n Microsoft 365 Government (GCC High) + Azure Government \n \n ITAR in GCC High and Azure Government \n These cloud services are purpose built for export controls in the US, to include ITAR and EAR. I have customers interpret that GCC is suitable for export controls. I've even had customers decide that Commercial is sufficient. I tell them that I am not a lawyer, and I cannot give you legal counsel, but I think that is extremely unwise. I can't stop you from leveraging Commercial or GCC for CUI-Specified categorized as Export Controlled (CUI//EXPT), especially for ITAR and EAR. I hope you take advantage of every data protection feature that we offer you! GCC High and Azure Government were created to give you a commitment for export controls in the US. This includes a US Sovereign Cloud accreditation boundary encompassing all services attached to Azure Government, Microsoft 365 Government (GCC High) and Dynamics 365 Government (GCC High). For example, the network is sovereign and constrained to CONUS. The GCC High directory services with Entra ID are provided by Azure Government and are sovereign to the US. \n DoD CC SRG Equivalency in GCC High \n We have evolved the US Sovereign Cloud to include PII protections. PII protections are now all the way up to IL4 in GCC High (aligned with FedRAMP High). In fact, we manage the GCC High environment with the same set of control scope and ODVs as the DoD environment. This translates to SRG ‘equivalency’ of both IL4 and IL5 in GCC High. \n However, for most Federal contractors and the DIB, SRG impact level is a moot point. Technically speaking, the SRG only applies to Federal information systems. IL4 is not an authorization the DoD will provide to a non-Federal nor private-sector entities, nor is it for a CSP cloud environment not in use directly by the DoD. For the DIB, DFARs 7012 and CMMC is what applies to non-Federal and private sector information systems. As such, Microsoft has pivoted away from advertising the SRG impact levels in alignment with Microsoft 365 Government (GCC High). We now focus on how our DIB/FFRDC/UARC customers may demonstrate compliance with CMMC leveraging our cloud service offerings. \n That said, we often get pulled into customer conversations where they have a contract with the US DoD including a CC SRG IL5 requirement. The DoD is telling their prime contractor “You must put this data in an IL5 environment” with no exceptions. However, the environment is in the contractor’s information systems. The DoD does not certify a contractor’s environment for the CC SRG, regardless of whether it’s on-premises or in the cloud. As such, the CC SRG does not apply to contractor-owned environments. It’s impossible for a contractor to certify their information systems as IL5 because it’s not a DoD-owned environment. As such, I break it down this way… \n \n Gov’t Owned, Gov’t Operated (GOGO) = CC SRG IL 2/4/5 (NIST SP 800-53) under DISA security cognizance. \n Gov’t Owned, Contractor-Operated (GOCO) = CC SRG IL 2/4/5 (NIST SP 800-53) under DISA security cognizance. The Contractor masquerades on-behalf of the DoD. \n Contractor-Owned, Contractor-Operated (COCO) = DFARS 7012 + CUI-Specified protections (e.g. DDTC regs for ITAR). DISA does NOT have security cognizance. CMMC will in the future. \n \n An older slide (circa 2017) but still helpful in visualizing the below breakdown between GOGO (DoD Information Systems), GOCO (Systems Operated on Behalf of the DoD) and COCO (Contractor’s Internal System) and the appropriate alignment with NIST 800-171 vs SRG. \n Reference from ‘Protecting the DoD’s Unclassified Information’ \n We are IL5 compliant for the DoD cloud we provide for GOGOs and GOCOs. In accordance with the requirements imposed by the DoD, Microsoft will not allow COCOs in the DoD cloud. Only the DoD can sponsor tenancy in that service, yet they have not allowed any COCOs to date. If a customer feels they require a cloud service accredited at IL5, this is an issue they need to raise with the DoD. IL5 is defined as to restrict tenancy to only entities authorized by DISA. \n We offer IL4 ‘Equivalent’ cloud services in GCC High. It’s ‘Equivalent’ because the DoD has not granted IL4 to GCC High since they have no intent from their mission owners in the DoD consuming that service (instead intending them to utilize the DoD cloud services). \n If a contractor has DoD compliance requirements for a COCO, we expect those to fall under security cognizance for DFARS 7012 and CMMC that GCC High can support. \n DoD CC SRG in Azure Government \n Cloud services in Azure Government are authorized for DoD CC SRG IL2 and IL4. In addition, Azure Government has over 120 services accredited at IL5 (148 as of the time of this writing). These services include a broad range of IaaS, PaaS and SaaS capabilities. When supporting IL5 workloads on Azure Government, the isolation requirements can be met in different ways. The Isolation guidelines for IL5 workloads documentation addresses configurations and settings for the isolation required to support IL5 data with specific service instructions. \n You can find a full list of Azure Government services that meet the requirements of the DoD in the Azure Government audit scope documentation. \n For more information, please reference: \n \n Department of Defense Impact Level 4 - Azure Compliance \n Department of Defense Impact Level 5 - Azure Compliance \n \n DFARs 7012 and NIST SP 800-171 in GCC High and Azure Government \n Microsoft will support a Flow-Down for DFARs 7012 in GCC High and in Azure Government. This translates to a commitment where we demonstrate DFARs 7012 compliance in the US Sovereign Cloud. This includes DFARs 7012 alignment with NIST SP 800-171 in a shared responsibility model with the Customer. \n Note: You may access our Attestation of Compliance with DFARS included with our Body of Evidence (BoE). \n FedRAMP High in GCC High \n You can demonstrate compliance with the FedRAMP Moderate and High Impacts Level in GCC High. We have several Federal Agencies actively deployed in GCC High, demonstrating compliance with FedRAMP High. The Agency ATOs include but are not limited to the U.S. Department of Homeland Security (DHS), the U.S. Department of Justice (DoJ), the U.S. Federal Bureau of Investigation (FBI), and the U.S. Department of the Treasury. \n Note: The FedRAMP High Impact Level is not a requirement for DFARs 7012 compliance. FedRAMP Moderate ‘or Equivalent’ is specifically required for DFARs 7012. \n For more information, please reference: \n \n Microsoft FedRAMP Documentation (https://aka.ms/fedramp) \n FedRAMP Package FR1824057433: Microsoft Office 365 GCC High | FedRAMP Marketplace \n Body of Evidence (BoE) section below \n \n As discussed in the section for FedRAMP in Microsoft 365 Commercial, holistic coverage for Microsoft 365 includes both Office 365 productivity services and Azure services bundled together. The section below on Azure Government includes all the cloud services that fall in-scope for the Azure Government P-ATO. \n FedRAMP High in Azure Government and Dynamics 365 GCC High \n As described above for Azure Commercial, Azure Government has a P-ATO for FedRAMP High from the FedRAMP PMO. \n There are over 140 Azure services (161 services as of the time of this writing) covered by the FedRAMP High P-ATO in Azure Government. You may even observe that Dynamics 365 Government (GCC High) falls under the scope of the Azure Government P-ATO in the FedRAMP Marketplace where the P-ATO is recognized as ‘Authorized’ by the FedRAMP PMO. \n FedRAMP Body of Evidence \n The FedRAMP Body of Evidence (BoE) is a collection of documents, artifacts, and evidence that demonstrate the security controls implemented by a CSP to demonstrate compliance with the FedRAMP security control baseline through an assessment conducted by a FedRAMP authorized 3PAO. It provides a comprehensive record of the security measures in place to protect federal data. \n Office 365 and Azure’s BoEs include the following: \n \n SSP: The System Security Plan provides an overview of the security requirements for the Cloud Services and describes the controls in place or planned for implementation to provide a level of security appropriate for the information to be transmitted, processed or stored by the system. \n CIS & CRM: The Control Implementation Summary (CIS) report includes control implementation responsibility and implementation status of the FedRAMP security controls. Also included in the CIS is an Excel spreadsheet for the Customer Responsibility Matrix (CRM). The CRM identifies what controls are inherited from the cloud service provider, versus those controls that are the responsibility of the customer (tenant owner). Most importantly, the CRM identifies the controls that are shared responsibility of both the CSP and the customer. \n SAR: The Security Assessment Report is generated by the 3PAO during the annual assessment. \n SAP: The Security Assessment Plan (SAP) lists the scope and security controls selected for annual assessment by the 3PAO. \n Penetration Testing Report: Cloud penetration testing report produced by Azure FedRAMP High and DoD SRG compliance program. \n DFARs Compliance Attestation Letter: Attestation of Compliance with Defense Federal Acquisition Regulation Supplement (DFARs) clause 252.204-7012. \n CMMC Compliance Attestation Letter: Attestation of Compliance with Cybersecurity Maturity Model Certification (CMMC) Requirements. \n \n For more information on the specific requirements for a BoE, please review the U.S. Department of Defense memorandum for ‘FedRAMP Moderate Equivalency for Cloud Service Provider’s Cloud Service Offerings’ dated December 21, 2023. \n The BoE is considered highly sensitive and confidential information. Historically, many CSPs have not been willing to share their BoE with customers, especially for Government cloud offerings. However, Microsoft is transparent and will allow for customers of our government solutions to access the BoE under a Non-Disclosure Agreement (NDA). To request the BoE, you must be a customer and make an E-mail request to: \n \n Office 365 GCC High: O365FedRAMP@microsoft.com \n Azure Government: AzFedDoc@microsoft.com \n \n Note: If you have your Microsoft NDA handy and can provide the document ID, it can save time during the request. \n CMMC in the US Sovereign Cloud \n You may demonstrate compliance with all maturity levels of CMMC in the US Sovereign Cloud. We exclusively recommend our US Sovereign Cloud with Microsoft 365 Government (GCC High) and Azure Government for data protection of CUI in alignment with CMMC 2.0 Levels 2-3. \n CJIS in Azure Government \n CJIS in Azure Government is aligned with the same description as provided above in the section “Criminal Justice Information Services in GCC”. \n CJIS in GCC High \n Criminal Justice Information Services in Microsoft 365 Government (GCC High) is described as for ‘Federal’ only. CJIS Information Agreements are signed primarily at the US State level. Most US States have Information Agreements established for both Microsoft 365 Government (GCC) and for Azure Government. However, those agreements are not in scope for Microsoft 365 Government (GCC High). This is because no State nor local government entities deploy into GCC High. To date, only Federal agencies and the DIB/FFRDC/UARC deploy into GCC High. Thus, a US State has not had the need to sign a CJIS Information Agreement for GCC High. It doesn’t mean that GCC High is non-compliant with CJIS. That is evident as the US Federal Bureau of Investigation (FBI) is deployed in GCC High. Hence, the FBI has authorized the use of GCC High for CJIS at the ‘Federal’ level. \n NERC and FERC in the US Sovereign Cloud \n Microsoft has engaged with multiple entities obligated to demonstrate compliance requirements of the North American Electric Reliability Corporation (NERC) and/or the Federal Energy Regulatory Commission (FERC). They find the US Sovereign Cloud with Microsoft 365 Government (GCC High) High and Azure Government to be the closest match of Microsoft cloud service offerings to fulfill their requirements. Due to the dynamic scope of applicability that an entity may define, we recommend you request explicit support from your Microsoft account team if you have compliance requirements in this area. \n Customer Support for the US Sovereign Cloud \n The US Sovereign Cloud with Azure Government, Microsoft 365 Government (GCC High) and Dynamics 365 Government (GCC High) offer differentiated support staffing, with technical support provided 24x7 by screened US Persons in a US Location. However, these terms do not preclude the use of global support staff in customer support escalations. It is not uncommon for Microsoft customer support to rely on support engineers that specialize in specific services or technologies and are subject matter experts in niche areas. These support engineers might be located anywhere in the world and could be introduced to provide expertise and guidance on a specific customer support ticket. Since customer support personnel have no direct standing access to the datacenter nor to customer content, they can only be exposed to sensitive information when it is provided directly by the Customer during a customer support ticket. We remind you not to share any controlled, sensitive, or confidential information with support personnel as part of your support incident, and follow your own internal data sharing controls, policies and procedures when engaging with Microsoft customer support. \n Important: Within the US Sovereign Cloud, you may request your ticket to remain limited and restricted to “screened US Persons in a US Location” only. However, availability of the subject matter engineer may be limited to US time zones as opposed to 24x7 support. This may negatively impact the response and mitigation of the Customer support ticket. \n Note: Microsoft Purview Customer Lockbox is a popular feature to moderate access to your data. We even have Customer Lockbox for Azure releasing to more and more Azure services. \n Considerations for US person-only Tenant for Government Clouds \n This is an organizational decision, and not one that is required to achieve compliance. \n There are no restrictions for US persons nor for citizenship checks imposed by Microsoft on tenant owners (organizations) giving access control to their tenants in US Government cloud service offerings. As with all Cloud Service Providers (CSP), it is a shared scope of responsibility for compliance. Microsoft commits to personnel that are US persons on the back end with the CSP specific scope of responsibility, but it is the organization’s (customer’s) responsibility to protect their content according to their own regulatory requirements. \n \n Microsoft 365 Government (DoD) \n \n If you are not in the DoD, don't worry about it. You're not getting into the service. Only the DoD and those approved by them (such as service providers or entities authorized by the DoD) are allowed into the DoD regions for Microsoft 365 and Azure Government. \n That said, if you are a DoD contractor with requirements for DoD CC SRG IL5, please read the section above on ‘DoD CC SRG Equivalency in GCC High’. \n \n \n Azure Government Secret + Office 365 Government Secret \n \n DoD CC SRG in Azure Government Secret \n CC SRG IL6 is reserved for the storage, processing and transmission of information classified up to the Collateral Secret level. For a hyper-scale cloud offering, information that must be processed and stored at IL6 can only be hosted in an air-gapped government community cloud. Because of the requirement that the entire cloud infrastructure be dedicated and separate (air-gapped) from other CSP infrastructures, IL6 may only be provided by CSPs under contract to the DoD or a federal agency. \n Azure Government Secret maintains an IL6 P-ATO at the high confidentiality, high integrity, and customer-determined availability (H-H-x) information categorization. In addition, DISA is the primary Authorizing Official (AO) for Azure Government Secret, with all other Secret compliance frameworks recognizing a program of reciprocity with the DoD CC SRG. Over 67 Azure Government Secret services are accredited for IL6 as of the time of this writing. These services include a broad range of IaaS, PaaS and SaaS capabilities. We have many more services in the queue for authorization by DISA as we speak. \n Note: Azure Government Secret is the first and only classified cloud service offering (CSO) to have received the highest possible P-ATO at the H-H-x information categorization. \n You can find a full list of Azure Government services that meet the requirements of the DoD in the Azure Government audit scope documentation. \n For more information, please reference: \n \n Department of Defense Impact Level 6 - Azure Compliance \n Azure Government for national security \n Introduction to Microsoft Azure Government Secret \n Announcing new Azure Government capabilities for classified mission-critical workloads \n \n DoD CC SRG in Office 365 Government Secret \n Since announcing the general availability of Azure Government Secret, our mission has been to support all US government agencies, departments, municipalities, public sector employees and industry with IL6 compliant productivity and collaboration tools. Office 365 Government Secret is authorized for IL6 and generally available for use by the DoD today with hundreds of thousands of seats actively deployed. In addition, this O365 environment is built to support the DoD along with US Federal Civilian, Intelligence Community (IC), and US government partners (industry) working within the Secret enclave with our SaaS capabilities. \n For more information, please reference Announcing Office 365 Government Secret cloud. \n National Industrial Security Program Operations Manual \n The National Industrial Security Program (NISP) has oversight by the DoD’s Defense Counterintelligence and Security Agency (DCSA). Just as facilities and individuals require a clearance to gain access to classified information, cleared contractor Information Systems (IS) must be assessed and authorized prior to processing classified information. \n DCSA serves as the Authorizing Official (AO) for contractor IS, such as for Contractor-Owned & Contractor-Operated (COCO) Internal Research & Development (IRAD) environments. The NISP has published guidance for industry to properly manage and protect against unauthorized disclosure of classified information, including Collateral classifications (Confidential & Secret). The NISP has recognized a program of reciprocity with the DoD CC SRG IL6 including authorizations for use of cloud by industry based on the NISP Operations Manual (NISPOM). \n You can now demonstrate compliance with the NISPOM and achieve an ATO using Azure Government Secret. \n Note: Azure Government Secret is the first and only classified cloud service offering (CSO) to be authorized by the NISP with industry partners connecting to our hyper-scale cloud using non-government (aka ‘private’) COCO networks. \n Joint Special Access Programs Implementation Guide \n A Special Access Program (SAP) is a highly classified program established to protect sensitive information and impose enhanced security measures with compartmentalized access requirements that go beyond what is typically required for information at the same (Collateral) classification levels. In addition to Collateral controls (e.g. IL6 & NISPOM), a SAP imposes more rigorous requirements, non-disclosure agreements (NDA) to get ‘read-in’ to the program, special document markings, etc. Within the DoD, a SAP is better known with Special Access Required (SAR) markings. \n Note: Word to the wise, when talking about SAP with your fellow cybersecurity fellows, make sure you differentiate between SAP for classified IS, as opposed to the ERP company solutions. It’s amazing how often you can talk past each other! \n A big difference between Collateral versus SAP/SAR requirements is requiring cleared personnel, facilities (SAPF) and IS to be ‘read-in’ to the program, effectively compartmentalizing access to the individual program. \n The Joint Special Access Programs Implementation Guide (JSIG) provides standardized policies for cybersecurity and information assurance, procedures, and implementation guidance for use in the management of IS at all classification levels under the purview of the SAP Authorizing Official (AO). Based on NIST SP 800-53, the NIST Risk Management Framework (RMF) and JSIG Protection Levels (e.g. PL2, PL3), JSIG includes the compliance control set required to achieve an ATO for SAP IS environments. \n Azure Government Secret maintains JSIG ATOs at Protection Levels up to 3 (PL3). \n For more information, please reference Joint Special Access Program Implementation Guide - Azure Compliance \n Intelligence Community Directive \n Intelligence Community Directive (ICD) 503, also known as ‘Risk Management for Federal Information Systems’ is a standard developed by NIST in collaboration with the US Intelligence Community (IC) for risk management and certification of IS across the IC. It provides a framework for managing risk and ensuring the confidentiality, integrity, and availability of information systems within US Federal agencies. ICD 503 is closely related to the NIST RMF and enables the IC to use NIST and Committee on National Security Systems (CNSS) standards for security assessments. \n Azure Government Secret maintains ICD 503 ATOs with classified facilities authorized according to ICD 705. \n For more information, please reference Intelligence Community Directive (ICD) 503 - Azure Compliance \n Azure Government Top Secret + Office 365 Government Top Secret \n Generally speaking, we do not disclose many details on our Top Secret (TS) Cloud Service Offerings (CSO) without an exclusive sponsorship by the US Government, other than what is mentioned in the blog article ‘Azure Government Top Secret now generally available for US national security missions’. That said, TS does have support for JSIG and ICD 503/705 at TS classification levels (e.g. Collateral TS & TS/SCI), like what is described above for Secret. \n \n \n Appendix \n Please follow me here and on LinkedIn. Here are my additional blog articles: \n \n Blog Title \n \n Aka Link \n \n Microsoft Collaboration Framework \n \n https://aka.ms/ND-ISAC/CollabFramework \n \n ND-ISAC MSCloud - Reference Identity Architectures for the US Defense Industrial Base \n \n https://aka.ms/ND-ISAC/IdentityWP \n \n New! Microsoft Product Placemat for CMMC \n \n https://aka.ms/CMMC/Placemat \n \n Microsoft CMMC Acceleration Update \n \n https://aka.ms/CMMC/Acceleration \n \n History of Microsoft Cloud Service Offerings leading to the US Sovereign Cloud for Government \n \n https://aka.ms/USSovereignCloud \n \n The Microsoft 365 Government (GCC High) Conundrum - DIB Data Enclave vs Going All In \n \n https://aka.ms/AA6frar \n \n Microsoft US Sovereign Cloud Myth Busters - A Global Address List (GAL) Can Span Multiple Tenants \n \n https://aka.ms/AA6seih \n \n Microsoft US Sovereign Cloud Myth Busters - A Single Domain Should Not Span Multiple Tenants \n \n https://aka.ms/AA6vf3n \n \n Microsoft US Sovereign Cloud Myth Busters - Active Directory Does Not Require Restructuring \n \n https://aka.ms/AA6xn69 \n \n Microsoft US Sovereign Cloud Myth Busters - CUI Effectively Requires Data Sovereignty \n \n https://aka.ms/CUISovereignty \n \n Microsoft expands qualification of contractors for government cloud offerings \n \n https://aka.ms/GovCloudEligibility \n \n Microsoft Expands Support for the DIB – Announcing Support for DFARS in Azure Commercial \n \n https://aka.ms/DFARsAzure \n \n Microsoft Expands Support for the DIB – Announcing Support for DFARS in Microsoft 365 Government (GCC) \n \n https://aka.ms/DFARsGCC \n \n New! Support for DFARS in Microsoft 365 Government (GCC High) \n \n https://aka.ms/DFARsGCCH \n \n New! Support for FedRAMP in Microsoft 365 Government (GCC High) \n \n https://aka.ms/FedRAMPGCCH \n \n Microsoft Federal Successfully Completes Voluntary CMMC Assessment \n \n https://aka.ms/JSVA \n \n ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"58377","kudosSumWeight":5,"repliesCount":3,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LTYxMjYwNWlCREREQ0JBMkMxNTdDRkUx?revision=27\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LUc3WmVLbg?revision=27\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDM","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LVo4emdqTg?revision=27\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDQ","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LXc0dmt4Nw?revision=27\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDU","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LXJVUTZ4TQ?revision=27\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDY","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LUFGTFhaOA?revision=27\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDc","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LTYxMzAyMWk1RjMxREJGQUYzRDQ5QzNE?revision=27\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDg","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LXdJUVhwWA?revision=27\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDk","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MjI1NDM2LVpid0xjUw?revision=27\"}"}}],"totalCount":9,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":null,"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"BOTTOM","altText":""}},"Conversation:conversation:2736511":{"__typename":"Conversation","id":"conversation:2736511","topic":{"__typename":"BlogTopicMessage","uid":2736511},"lastPostingActivityTime":"2025-02-24T12:10:19.056-08:00","solved":false},"User:user:600278":{"__typename":"User","uid":600278,"login":"George__Wilburn","registrationData":{"__typename":"RegistrationData","status":null},"deleted":false,"avatar":{"__typename":"UserAvatar","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/m_assets/avatars/default/avatar-3.svg?time=0"},"id":"user:600278"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMxMzE5NWk5QTg3RUFGQkUwREE3Mzc5?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMxMzE5NWk5QTg3RUFGQkUwREE3Mzc5?revision=14","title":"security meeting .jpg","associationType":"TEASER","width":2507,"height":1672,"altText":null},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI1N2k4MzdCMEU5MUU0OEFBN0JC?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI1N2k4MzdCMEU5MUU0OEFBN0JC?revision=14","title":"George__Wilburn_0-1631196835761.png","associationType":"BODY","width":1016,"height":438,"altText":null},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI1OWk2QjYwQzlDMUI0NTIxQ0RG?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI1OWk2QjYwQzlDMUI0NTIxQ0RG?revision=14","title":"George__Wilburn_1-1631196835836.png","associationType":"BODY","width":2832,"height":952,"altText":null},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI1OGk4NzY0NTQwMjkxQkI2OEM0?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI1OGk4NzY0NTQwMjkxQkI2OEM0?revision=14","title":"George__Wilburn_2-1631196835857.png","associationType":"BODY","width":1459,"height":1104,"altText":null},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2MGk1NDBFMUVDQTVBMkUxRjU2?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2MGk1NDBFMUVDQTVBMkUxRjU2?revision=14","title":"George__Wilburn_3-1631196835876.png","associationType":"BODY","width":2880,"height":1002,"altText":null},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2MWkwMDcyNzA4MUE1OUVFODQ3?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2MWkwMDcyNzA4MUE1OUVFODQ3?revision=14","title":"George__Wilburn_4-1631196835902.png","associationType":"BODY","width":1584,"height":608,"altText":null},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2Mmk0QzNBNEM1QTQyNkIyQkFF?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2Mmk0QzNBNEM1QTQyNkIyQkFF?revision=14","title":"George__Wilburn_5-1631196835936.png","associationType":"BODY","width":1592,"height":838,"altText":null},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2NWlFNTU0NTM3QjgyRTlFNTFC?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2NWlFNTU0NTM3QjgyRTlFNTFC?revision=14","title":"George__Wilburn_6-1631196835966.png","associationType":"BODY","width":1630,"height":1028,"altText":null},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2NGlBNzg0QzQ3N0RFRjRBRDY4?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2NGlBNzg0QzQ3N0RFRjRBRDY4?revision=14","title":"George__Wilburn_7-1631196835978.png","associationType":"BODY","width":952,"height":540,"altText":null},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2M2kwOTZFQkNCNzZBMkQzMkU5?revision=14\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2M2kwOTZFQkNCNzZBMkQzMkU5?revision=14","title":"George__Wilburn_8-1631196836011.png","associationType":"BODY","width":1642,"height":854,"altText":null},"BlogTopicMessage:message:2736511":{"__typename":"BlogTopicMessage","subject":"Aligning CMMC Controls with your Azure Landing Zone","conversation":{"__ref":"Conversation:conversation:2736511"},"id":"message:2736511","revisionNum":14,"uid":2736511,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:600278"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":" \n \n Better Together: Azure Landing Zone, Azure Security Benchmarks, Azure Security Center, and CMMC Level 3 compliance ","introduction":"","metrics":{"__typename":"MessageMetrics","views":18485},"postTime":"2021-09-27T13:26:25.732-07:00","lastPublishTime":"2021-09-27T13:58:23.197-07:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" If you utilize them all together, Azure Landing Zones, Azure Policy, Azure Security Benchmarks, and the CMMC Level 3 Initiative in Azure Security Center can ease your CMMC compliance journey. In this blog, we'll show you how! \n \n Microsoft is actively building out our program by developing resources for both Partners and Defense Industrial Base (DIB) companies to leverage in their Cybersecurity Maturity Model Certification (CMMC) journey. These tools and guidance cannot guarantee a positive CMMC adjudication, but they may assist candidate organizations by improving their CMMC posture going into a formal CMMC review in accordance with CMMC Accreditation Body (CMMC AB) standards. While we plan to release resources and guidance in waves, please keep in mind we are dependent upon the CMMC AB finalizing the CMMC guidance itself. As a result, there may be additional nuance or complexity associated with CMMC compliance that will only materialize (if at all) through the practical application of the standard by the CMMC AB. What’s more, as of the date this post was written, the CMMC AB has not issued formal guidance for Cloud Service Providers. As a result, the information herein, including all Microsoft CMMC related offerings, are provisional and may be enhanced to align with future guidance from the DoD and CMMC AB. Microsoft does not guarantee nor imply any ultimate compliance outcome or determination based on one’s consumption of this post—all CMMC certification requirements and decisions are governed by the CMMC AB, and Microsoft has no direct or indirect insight into or bearing over CMMC AB compliance determinations. \n \n Aligning CMMC Controls with your Azure Landing Zone \n \n Azure Landing Zones (ALZ) enable application migration, modernization, and innovation at enterprise-scale in Azure. The Microsoft Cloud Adoption Framework’s reference architecture and implementations, known as Enterprise-Scale Landing Zones, helps you deploy an Azure foundation that is scalable, operational, and extendable by design. Even when you have been deployed in Azure for a while and attained a level of maturity, the framework serves as a design to realign to Azure recommended practices and identify and address any technical debt accumulation. The below table shows the available Enterprise-Scale reference implementations. \n \n \n \n \n \n Additionally, the Enterprise-Scale reference implementations have been aligned closely with Azure Security Benchmarks (ASB) and grant some assurance that the landing zone that is deployed will be compliant with Microsoft’s defined security benchmarks. We recently mapped the CMMC Level 3 controls to the ASB so that customers needing alignment with CMMC can also leverage the ASB to assist in determining whether the landing zone meets compliance requirements. This ASB mapping to CMMC may be downloaded here: https://aka.ms/cmmc/asbmap. In addition to aligning CMMC to ASB, we have also mapped ALZ policies to CMMC controls. By combining an ALZ implementation with Azure Policy, Azure Security Benchmarks, and the CMMC compliance initiative, you can attain a reference implementation and get visibility into CMMC alignment. This blog post will cover the Azure Landing Zone architecture, CMMC mapping to ALZ policies, and the compliance audit and reporting options found in Azure Security Center. \n \n \n \n \n \n High-Level Azure Landing Zone Architecture \n \n An ALZ enterprise-scale architecture is defined by a set of design considerations and recommendations across eight critical design areas, with two recommended network topology options: an enterprise-scale architecture based on an Azure Virtual WAN network or an architecture based on a traditional Azure hub and spoke network topology (depicted below). \n \n \n One of the core design principles of Azure Landing Zones is policy-driven governance. This means that Azure Policy provides guardrails for your organization's Azure platform, along with the workloads deployed onto it. Azure Policy also provides application owners with both sufficient freedom and a secure unhindered path to the cloud. \n \n There is a large set of guardrails that come out-of-the-box with an ALZ implementation. To increase flexibility, not all these policies are associated during the landing zone deployment. Therefore, each policy should be well understood and evaluated against your corporate standards to enable you to achieve the appropriate impact to how open or locked down you want to make your landing zone deployment. After evaluation, the policies can either be associated during your ALZ deployment in a CI/CD pipeline or configured through the portal after your deployment is complete. Also, whether you are greenfield or brownfield, the AzOps Accelerator, Microsoft’s integrated CI/CD solution, can help you manage your environment at scale. \n \n Mapping CMMC Controls to Azure Landing Zone Policies \n As mentioned above, the Azure Landing Zone deployment includes a set of policies to enforce guardrails using a policy-driven governance approach. We have aligned these ALZ policies to the CMMC Practices and CMMC ID# as shown below. This mapping provides guidance to assist you with implementing CMMC controls when deploying your Azure landing zone. This Azure Landing Zone mapping for CMMC may be downloaded here: https://aka.ms/cmmc/alzmap \n \n \n \n \n Applying the CMMC Initiative in Azure Security Center \n \n We recently added an Azure Policy Initiative that maps to CMMC Level 3 controls. This CMMC Level 3 Policy Initiative can be activated in Azure Security Center to quickly help you assess compliance with the control. Note that it is important to remember that there often is not a one-to-one or complete match between a control and one or more Azure Policies. As such, “Compliant” in Azure Policy refers only to the policy definitions themselves; this doesn't ensure you're fully compliant with all requirements of a control. In addition, the compliance standard includes controls that aren't addressed by any Azure Policy definitions at this time. Therefore, compliance in Azure Policy is only a partial view of your overall compliance status. The associations between compliance domains, controls, and Azure Policy definitions for this compliance standard may change over time. The CMMC Level 3 Initiative can be applied in Security Center’s Regulatory Compliance page. \n \n \n \n \n Reporting your CMMC Compliance with Azure Security Center \n \n After deploying your landing zone, implementing policies, and configuring the CMMC Level 3 Initiative, you can leverage Security Center to help evaluate compliance with CMMC. In addition to the Azure Security Compliance dashboard for CMMC Level 3, you can generate downloadable reports, as indicated below, to share with relevant parties such as your Risk Team, Auditors, CSO, or Executives. \n \n \n \n \n Below is a sample PDF report, but you can choose CSV format as well. \n \n \n \n \n Security Center also has built-in workbooks that display compliance over time. \n \n \n \n \n \n \n Summary \n \n When used together, this is a great way to get your landing zone deployed (with a lot of the design and planning work done for you) and then apply, report, and visualize your CMMC Level 3 compliance. If you have any questions related to Azure Landing Zones or CMMC Level 3 policy mapping, please leave a comment below. \n \n Special thanks to: \n RichardWakeman for collaborating on and reviewing this post ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"7899","kudosSumWeight":0,"repliesCount":5,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMxMzE5NWk5QTg3RUFGQkUwREE3Mzc5?revision=14\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDI","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI1N2k4MzdCMEU5MUU0OEFBN0JC?revision=14\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDM","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI1OWk2QjYwQzlDMUI0NTIxQ0RG?revision=14\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDQ","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI1OGk4NzY0NTQwMjkxQkI2OEM0?revision=14\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDU","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2MGk1NDBFMUVDQTVBMkUxRjU2?revision=14\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDY","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2MWkwMDcyNzA4MUE1OUVFODQ3?revision=14\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDc","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2Mmk0QzNBNEM1QTQyNkIyQkFF?revision=14\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDg","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2NWlFNTU0NTM3QjgyRTlFNTFC?revision=14\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDk","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2NGlBNzg0QzQ3N0RFRjRBRDY4?revision=14\"}"}},{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDEw","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0yNzM2NTExLTMwOTI2M2kwOTZFQkNCNzZBMkQzMkU5?revision=14\"}"}}],"totalCount":10,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":null,"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"BOTTOM","altText":""}},"Conversation:conversation:3258326":{"__typename":"Conversation","id":"conversation:3258326","topic":{"__typename":"BlogTopicMessage","uid":3258326},"lastPostingActivityTime":"2025-02-21T07:00:41.871-08:00","solved":false},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0zMjU4MzI2LTM1NjYzNGkwRTkwQTJBMjAxMTBBQzA4?revision=23\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0zMjU4MzI2LTM1NjYzNGkwRTkwQTJBMjAxMTBBQzA4?revision=23","title":"compliance update 3.17.2020.gif","associationType":"TEASER","width":853,"height":480,"altText":null},"BlogTopicMessage:message:3258326":{"__typename":"BlogTopicMessage","subject":"Understanding Compliance Between Commercial, Government and DoD Offerings - September 2023 Update","conversation":{"__ref":"Conversation:conversation:3258326"},"id":"message:3258326","revisionNum":23,"uid":3258326,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:276160"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":" \n 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. ","introduction":"","metrics":{"__typename":"MessageMetrics","views":140701},"postTime":"2022-03-17T10:30:00.033-07:00","lastPublishTime":"2024-09-23T15:00:40.894-07:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" There is an update to this article found at: \n \n https://aka.ms/MSGovCompliance \n \n \n ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"115","kudosSumWeight":3,"repliesCount":11,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS0zMjU4MzI2LTM1NjYzNGkwRTkwQTJBMjAxMTBBQzA4?revision=23\"}"}}],"totalCount":1,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":null,"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"BOTTOM","altText":""}},"Conversation:conversation:4372752":{"__typename":"Conversation","id":"conversation:4372752","topic":{"__typename":"BlogTopicMessage","uid":4372752},"lastPostingActivityTime":"2025-02-07T15:11:18.473-08:00","solved":false},"User:user:1649713":{"__typename":"User","uid":1649713,"login":"dannymcbride","registrationData":{"__typename":"RegistrationData","status":null},"deleted":false,"avatar":{"__typename":"UserAvatar","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/dS0xNjQ5NzEzLTQ2MzA0OGk5RDFFMkY0MDFGNTVCQ0RE"},"id":"user:1649713"},"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MzcyNzUyLWVxQ0RXRg?revision=5\"}":{"__typename":"AssociatedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MzcyNzUyLWVxQ0RXRg?revision=5","title":"Phone Summit Image.png","associationType":"COVER","width":1024,"height":1024,"altText":""},"BlogTopicMessage:message:4372752":{"__typename":"BlogTopicMessage","subject":"GCC/GCCH Teams Phone Summit - Feb 25-26 Arlington, VA - REGISTRATION OPEN!","conversation":{"__ref":"Conversation:conversation:4372752"},"id":"message:4372752","revisionNum":5,"uid":4372752,"depth":0,"board":{"__ref":"Blog:board:PublicSectorBlog"},"author":{"__ref":"User:user:1649713"},"teaser@stripHtml({\"removeProcessingText\":true,\"truncateLength\":-1})":"","introduction":"The GCC/GCCH Microsoft Teams Phone Summit is your opportunity to explore current and coming capabilities to your government environments! \n\nYou’ll be surrounded by the experts to get answers and receive the tools and resources to navigate your unique voice journey.\n\nDay 1 - 8:30am-4:30pm EDT \nDay 2 - 9:30am-3:00pm EDT","metrics":{"__typename":"MessageMetrics","views":364},"postTime":"2025-01-31T12:03:16.197-08:00","lastPublishTime":"2025-02-07T15:11:18.473-08:00","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})":" \n Registration is now open for the GCC/GCCH Teams Phone Summit in Arlington, VA, Feb 25-26. Click here to register: https://msevents.microsoft.com/event?id=3586839266 \n \n We look forward to hosting you at the GCC/GCCH Teams Phone Summit on Tuesday, Feb 25 and Wednesday, Feb 26, in Arlington VA! The This is your opportunity to explore current and coming capabilities to your government environments! You’ll be surrounded by the experts to get answers and receive the tools and resources to navigate your unique voice journey. \n Day 1 - Tuesday, Feb. 25 - 8:30am-4:30pm \n \n Welcome from Javier Vasquez, VP, Microsoft Federal \n Teams Phone and Device Overview - latest and greatest and coming capabilities \n Call Records Insights \n Admin Tips and Tricks \n Fireside Chat highlighting 3 government agency's journeys to Teams Phone \n Partner Corner: Momentum Telecom (Lunch Sponsor), CIS Secure (Breakfast Sponsor), Audiocodes, SOFTEL, and Poly \n \n Day 2 - Wednesday, Feb. 26 - 9:30am-3:00pm \n \n 1:1 time with Dave Jennings - only 3 slots left (11am-12pm, 12-1pm, and 1-2pm EDT) - sign up here: Book Time with Dave! \n Topical breakout sessions with GCC/GCCH engineering experts (each one delivered three times during the day): \n Unlocking Insights: Mastering Teams Phone Monitoring and Reporting \n Teams Fortress: Ensuring Security & Compliance \n Microsoft Teams Advanced Calling and Beyond \n MS Teams Phone and the Future of Copilot/AI \n Lunch coupons to local establishment(s) to be provided \n \n Reach out to Danny McBride at dannymcbride@microsoft.com with any questions. ","body@stripHtml({\"removeProcessingText\":true,\"removeSpoilerMarkup\":true,\"removeTocMarkup\":true,\"truncateLength\":-1})@stringLength":"1590","kudosSumWeight":0,"repliesCount":0,"readOnly":false,"images":{"__typename":"AssociatedImageConnection","edges":[{"__typename":"AssociatedImageEdge","cursor":"MjUuMXwyLjF8b3wyNXxfTlZffDE","node":{"__ref":"AssociatedImage:{\"url\":\"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MzcyNzUyLWVxQ0RXRg?revision=5\"}"}}],"totalCount":1,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"videos":{"__typename":"VideoConnection","edges":[],"totalCount":0,"pageInfo":{"__typename":"PageInfo","hasNextPage":false,"endCursor":null,"hasPreviousPage":false,"startCursor":null}},"coverImage":{"__typename":"UploadedImage","url":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/images/bS00MzcyNzUyLWVxQ0RXRg?revision=5"},"coverImageProperties":{"__typename":"CoverImageProperties","style":"STANDARD","titlePosition":"TOP","altText":""}},"CachedAsset:text:en_US-components/community/Navbar-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/community/Navbar-1744658874328","value":{"community":"Community Home","inbox":"Inbox","manageContent":"Manage Content","tos":"Terms of Service","forgotPassword":"Forgot Password","themeEditor":"Theme Editor","edit":"Edit Navigation Bar","skipContent":"Skip to content","gxcuf89792":"Tech Community","external-1":"Events","s-m-b":"Small and Medium Businesses","windows-server":"Windows Server","education-sector":"Education Sector","driving-adoption":"Driving Adoption","microsoft-learn":"Microsoft Learn","s-q-l-server":"SQL Server","partner-community":"Microsoft Partner Community","microsoft365":"Microsoft 365","external-9":".NET","external-8":"Teams","external-7":"Github","products-services":"Products","external-6":"Power Platform","communities-1":"Topics","external-5":"Microsoft Security","planner":"Planner","external-4":"Microsoft 365","external-3":"Dynamics 365","azure":"Azure","healthcare-and-life-sciences":"Healthcare and Life Sciences","external-2":"Azure","microsoft-mechanics":"Microsoft Mechanics","microsoft-learn-1":"Community","external-10":"Learning Room Directory","microsoft-learn-blog":"Blog","windows":"Windows","i-t-ops-talk":"ITOps Talk","external-link-1":"View All","microsoft-securityand-compliance":"Microsoft Security","public-sector":"Public Sector","community-info-center":"Lounge","external-link-2":"View All","microsoft-teams":"Microsoft Teams","external":"Blogs","microsoft-endpoint-manager":"Microsoft Intune and Configuration Manager","startupsat-microsoft":"Startups at Microsoft","exchange":"Exchange","a-i":"AI and Machine Learning","io-t":"Internet of Things (IoT)","outlook":"Outlook","external-link":"Community Hubs","communities":"Products"},"localOverride":false},"CachedAsset:text:en_US-components/community/NavbarHamburgerDropdown-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/community/NavbarHamburgerDropdown-1744658874328","value":{"hamburgerLabel":"Side Menu"},"localOverride":false},"CachedAsset:text:en_US-components/community/BrandLogo-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/community/BrandLogo-1744658874328","value":{"logoAlt":"Khoros","themeLogoAlt":"Brand Logo"},"localOverride":false},"CachedAsset:text:en_US-components/community/NavbarTextLinks-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/community/NavbarTextLinks-1744658874328","value":{"more":"More"},"localOverride":false},"CachedAsset:text:en_US-components/authentication/AuthenticationLink-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/authentication/AuthenticationLink-1744658874328","value":{"title.login":"Sign In","title.registration":"Register","title.forgotPassword":"Forgot Password","title.multiAuthLogin":"Sign In"},"localOverride":false},"CachedAsset:text:en_US-components/nodes/NodeLink-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/nodes/NodeLink-1744658874328","value":{"place":"Place {name}"},"localOverride":false},"CachedAsset:text:en_US-components/tags/TagSubscriptionAction-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/tags/TagSubscriptionAction-1744658874328","value":{"success.follow.title":"Following Tag","success.unfollow.title":"Unfollowed Tag","success.follow.message.followAcrossCommunity":"You will be notified when this tag is used anywhere across the community","success.unfollowtag.message":"You will no longer be notified when this tag is used anywhere in this place","success.unfollowtagAcrossCommunity.message":"You will no longer be notified when this tag is used anywhere across the community","unexpected.error.title":"Error - Action Failed","unexpected.error.message":"An unidentified problem occurred during the action you took. Please try again later.","buttonTitle":"{isSubscribed, select, true {Unfollow} false {Follow} other{}}","unfollow":"Unfollow"},"localOverride":false},"CachedAsset:text:en_US-components/messages/MessageListTabs-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/messages/MessageListTabs-1744658874328","value":{"mostKudoed":"{value, select, IDEA {Most Votes} other {Most Likes}}","mostReplies":"Most Replies","mostViewed":"Most Viewed","newest":"{value, select, IDEA {Newest Ideas} OCCASION {Newest Events} other {Newest Topics}}","newestOccasions":"Newest Events","mostRecent":"Most Recent","noReplies":"No Replies Yet","noSolutions":"No Solutions Yet","solutions":"Solutions","mostRecentUserContent":"Most Recent","trending":"Trending","draft":"Drafts","spam":"Spam","abuse":"Abuse","moderation":"Moderation","tags":"Tags","PAST":"Past","UPCOMING":"Upcoming","sortBymostRecent":"Sort By Most Recent","sortBymostRecentUserContent":"Sort By Most Recent","sortBymostKudoed":"Sort By Most Likes","sortBymostReplies":"Sort By Most Replies","sortBymostViewed":"Sort By Most Viewed","sortBynewest":"Sort By Newest Topics","sortBynewestOccasions":"Sort By Newest Events","otherTabs":" Messages list in the {tab} for {conversationStyle}","guides":"Guides","archives":"Archives"},"localOverride":false},"CachedAsset:text:en_US-shared/client/components/common/QueryHandler-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-shared/client/components/common/QueryHandler-1744658874328","value":{"title":"Query Handler"},"localOverride":false},"CachedAsset:text:en_US-components/community/NavbarDropdownToggle-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/community/NavbarDropdownToggle-1744658874328","value":{"ariaLabelClosed":"Press the down arrow to open the menu"},"localOverride":false},"CachedAsset:text:en_US-shared/client/components/common/OverflowNav-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-shared/client/components/common/OverflowNav-1744658874328","value":{"toggleText":"More"},"localOverride":false},"CachedAsset:text:en_US-components/messages/MessageView/MessageViewInline-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/messages/MessageView/MessageViewInline-1744658874328","value":{"bylineAuthor":"{bylineAuthor}","bylineBoard":"{bylineBoard}","anonymous":"Anonymous","place":"Place {bylineBoard}","gotoParent":"Go to parent {name}"},"localOverride":false},"CachedAsset:text:en_US-shared/client/components/common/Pager/PagerLoadMore-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-shared/client/components/common/Pager/PagerLoadMore-1744658874328","value":{"loadMore":"Show More"},"localOverride":false},"CachedAsset:text:en_US-components/users/UserLink-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/users/UserLink-1744658874328","value":{"authorName":"View Profile: {author}","anonymous":"Anonymous"},"localOverride":false},"CachedAsset:text:en_US-components/messages/MessageSubject-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/messages/MessageSubject-1744658874328","value":{"noSubject":"(no subject)"},"localOverride":false},"CachedAsset:text:en_US-components/messages/MessageBody-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/messages/MessageBody-1744658874328","value":{"showMessageBody":"Show More","mentionsErrorTitle":"{mentionsType, select, board {Board} user {User} message {Message} other {}} No Longer Available","mentionsErrorMessage":"The {mentionsType} you are trying to view has been removed from the community.","videoProcessing":"Video is being processed. Please try again in a few minutes.","bannerTitle":"Video provider requires cookies to play the video. Accept to continue or {url} it directly on the provider's site.","buttonTitle":"Accept","urlText":"watch"},"localOverride":false},"CachedAsset:text:en_US-components/messages/MessageTime-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/messages/MessageTime-1744658874328","value":{"postTime":"Published: {time}","lastPublishTime":"Last Update: {time}","conversation.lastPostingActivityTime":"Last posting activity time: {time}","conversation.lastPostTime":"Last post time: {time}","moderationData.rejectTime":"Rejected time: {time}"},"localOverride":false},"CachedAsset:text:en_US-shared/client/components/nodes/NodeIcon-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-shared/client/components/nodes/NodeIcon-1744658874328","value":{"contentType":"Content Type {style, select, FORUM {Forum} BLOG {Blog} TKB {Knowledge Base} IDEA {Ideas} OCCASION {Events} other {}} icon"},"localOverride":false},"CachedAsset:text:en_US-components/messages/MessageUnreadCount-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/messages/MessageUnreadCount-1744658874328","value":{"unread":"{count} unread","comments":"{count, plural, one { unread comment} other{ unread comments}}"},"localOverride":false},"CachedAsset:text:en_US-components/messages/MessageViewCount-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/messages/MessageViewCount-1744658874328","value":{"textTitle":"{count, plural,one {View} other{Views}}","views":"{count, plural, one{View} other{Views}}"},"localOverride":false},"CachedAsset:text:en_US-components/kudos/KudosCount-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/kudos/KudosCount-1744658874328","value":{"textTitle":"{count, plural,one {{messageType, select, IDEA{Vote} other{Like}}} other{{messageType, select, IDEA{Votes} other{Likes}}}}","likes":"{count, plural, one{like} other{likes}}"},"localOverride":false},"CachedAsset:text:en_US-components/messages/MessageRepliesCount-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-components/messages/MessageRepliesCount-1744658874328","value":{"textTitle":"{count, plural,one {{conversationStyle, select, IDEA{Comment} OCCASION{Comment} other{Reply}}} other{{conversationStyle, select, IDEA{Comments} OCCASION{Comments} other{Replies}}}}","comments":"{count, plural, one{Comment} other{Comments}}"},"localOverride":false},"CachedAsset:text:en_US-shared/client/components/users/UserAvatar-1744658874328":{"__typename":"CachedAsset","id":"text:en_US-shared/client/components/users/UserAvatar-1744658874328","value":{"altText":"{login}'s avatar","altTextGeneric":"User's avatar"},"localOverride":false}}}},"page":"/tags/TagPage/TagPage","query":{"nodeId":"board:PublicSectorBlog","tagName":"Federal"},"buildId":"HEhyUrv5OXNBIbfCLaOrw","runtimeConfig":{"buildInformationVisible":false,"logLevelApp":"info","logLevelMetrics":"info","openTelemetryClientEnabled":false,"openTelemetryConfigName":"o365","openTelemetryServiceVersion":"25.1.0","openTelemetryUniverse":"prod","openTelemetryCollector":"http://localhost:4318","openTelemetryRouteChangeAllowedTime":"5000","apolloDevToolsEnabled":false,"inboxMuteWipFeatureEnabled":false},"isFallback":false,"isExperimentalCompile":false,"dynamicIds":["./components/community/Navbar/NavbarWidget.tsx","./components/community/Breadcrumb/BreadcrumbWidget.tsx","./components/customComponent/CustomComponent/CustomComponent.tsx","./components/tags/TagsHeaderWidget/TagsHeaderWidget.tsx","./components/messages/MessageListForNodeByRecentActivityWidget/MessageListForNodeByRecentActivityWidget.tsx","./components/tags/TagSubscriptionAction/TagSubscriptionAction.tsx","./components/external/components/ExternalComponent.tsx","../shared/client/components/common/List/ListGroup/ListGroup.tsx","./components/messages/MessageView/MessageView.tsx","./components/messages/MessageView/MessageViewInline/MessageViewInline.tsx","../shared/client/components/common/Pager/PagerLoadMore/PagerLoadMore.tsx"],"appGip":true,"scriptLoader":[{"id":"analytics","src":"https://techcommunity.microsoft.com/t5/s/gxcuf89792/pagescripts/1730819800000/analytics.js?page.id=TagPage","strategy":"afterInteractive"}]}