AI for Personalized Government Services: Building Trust and Inclusivity in Cities
Cities today are under unprecedented pressure. Residents expect services that are fast, accessible, and tailored to their needs, yet many local governments still rely on fragmented systems and manual processes that create long queues and frustration. In a digital-first society, these gaps are no longer acceptable. Artificial intelligence (AI) offers a transformative opportunity to close them, enabling governments to deliver personalized, proactive, and inclusive citizen experiences. On December 4, Smart Cities World Connect will host a Trend Report Panel Discussion bringing together city leaders, technology experts, and public sector innovators to explore how AI can reshape the citizen experience. This virtual event will highlight practical strategies for responsible AI adoption and showcase lessons from pioneering cities worldwide. Register today: Trend Report Panel Discussion (4 Dec) Why AI Matters for Cities Urban populations are growing, budgets remain tight, and climate and social pressures are mounting. Against this backdrop, AI is emerging as a critical enabler for smarter governance. By integrating AI into service delivery, cities can: Support improved wait times through AI-powered assistants and multilingual agents. Deliver proactive services using unified data and predictive analytics. Ensure equity by extending digital access to underserved communities. Build trust through transparent governance and responsible AI deployment. These capabilities are no longer theoretical. Cities from Abu Dhabi to Singapore are already embedding AI into core operations—modernizing citizen portals, automating case management, and using digital twins to plan with foresight. The panel will explore five essential areas for AI-driven transformation: 1. Smarter Citizen Engagement AI-powered virtual assistants and chatbots can handle routine inquiries, guide residents through complex processes, and provide real-time updates—across multiple languages and platforms. This not only reduces queues but also makes services more inclusive for diverse communities. 2. Proactive, Personalized Services Unified data platforms and predictive analytics allow governments to anticipate citizen needs, whether it’s notifying residents about benefit eligibility or streamlining license renewals. By moving from reactive to proactive service delivery, cities can improve satisfaction and reduce backlogs. 3. Equity at the Core Efficiency must never come at the expense of fairness. AI-enabled systems should be designed to reach underserved populations, bridging the digital divide and ensuring that innovation benefits all residents, not just the most connected. 4. Governance and Trust Responsible AI adoption requires robust frameworks for transparency, data protection, and ethical oversight. Cities must implement clear governance models, conduct algorithmic audits, and engage communities in co-design to maintain public trust. 5. Practical Steps for Integration From piloting high-impact use cases to building cross-department governance and investing in workforce training, the discussion will outline actionable steps for scaling AI responsibly. Partnerships with industry and academia will also play a vital role in accelerating adoption. Lessons from Frontier Cities Several global examples illustrate what’s possible: Manchester City Council is advancing smart urban living through AI-driven planning and operations, using integrated data platforms and predictive analytics to optimize city services, improve sustainability, and enhance citizen engagement across transport, housing, and community programs Abu Dhabi’s TAMM platform, powered by Microsoft Azure OpenAI, delivers nearly 950 government services through a single digital hub, simplifying processes and enabling personalized interactions. Singapore’s Virtual Singapore project uses AI and digital twins to simulate urban scenarios, helping planners make evidence-based decisions on mobility, safety, and climate resilience. Bangkok’s Traffy Fondue civic platform leverages AI to categorize citizen reports and route them to the right department, reducing administrative overhead and improving response times. These cases demonstrate that AI is not just a tool for efficiency, it’s a catalyst for inclusion, resilience, and trust. What Attendees Will Gain By joining the December 4 session, city leaders will leave with: A clear understanding of AI’s transformative potential for improving citizen satisfaction and reducing service backlogs. Real-world examples of successful deployments in citizen portals, case management, and service automation. Insights into ethical and regulatory considerations critical to building trust in personalized government services. Guidance on preparing organizations to adopt and scale AI effectively. Looking Ahead Cities that thrive in the coming decade will be those that combine strategic vision with disciplined, trustworthy use of technology. AI can help governments deliver services that are smarter, more inclusive, and more responsive to the needs of every resident, but success depends on strong governance, cross-sector collaboration, and a commitment to equity. To learn more and register for the Trend Report Panel Discussion on December 4.Join Microsoft at IACP 2025: Empower public safety operations with trusted AI
The International Association of Chiefs of Police (IACP) Annual Conference and Exposition is the premier global event for law enforcement leaders, bringing together more than 16,000 public safety professionals. This year, IACP 2025 takes place October 18–22 at the Colorado Convention Center in Denver, and Microsoft is proud to be part of the conversation. As your trusted partner in public safety innovation, we invite you to connect with us at booth #362 to discover how Microsoft and our ecosystem of partners are helping agencies modernize operations, improve decision-making, and build safer communities through trusted AI. Microsoft’s presence at IACP 2025 centers around three key pillars that reflect the evolving needs of law enforcement and public safety agencies: Empower the government workforce Streamline workflows with secure AI copilots, enhance collaboration across departments, and boost efficiency with intuitive digital tools. Enable AI-driven decision making Accelerate officer workflows with real-time insights and unify data to support faster, more informed decisions. Transform emergency response Modernize communications, integrate systems for real-time situational awareness, and automate operations to improve coordination and outcomes. Experience Innovation Firsthand At booth #362, attendees can explore hands-on demos of Microsoft solutions including Microsoft 365 Copilot, Researcher and Analyst agents, and Copilot Studio agents tailored for first responders. These tools are designed to help agencies work smarter, respond faster, and serve communities more effectively. You’ll also have the opportunity to connect with our partners, Altia, DisasterTech, Insight, Pimloc, Remark, Revelen.AI, Triangula, and Zencos who are showcasing their solutions that support officer workflows, evidence management, reporting, and analytics. Don’t miss the Emergency Response Platform vehicle demo, supported by Darley, Dejero, and 3AM which highlights how AI and real-time data can transform field operations and emergency response at the tactical edge. Attend Our Thought Leadership Session Join us for a featured education session in the Leadership Track: Is "Technology Sharing" the Key to Law Enforcement Innovation? 📅 Saturday, October 18 🕤 9:30 – 10:30 AM MT 📍 Room 505/506 This session explores how collaborative platforms and shared technology models can reduce costs, accelerate deployment, and improve outcomes across jurisdictions, offering a blueprint for scalable innovation. Let’s Connect We’d love to meet with you one-on-one to discuss your agency’s goals and challenges. Request a meeting with a Microsoft expert to explore how AI and cloud technologies can support your mission. Visit Microsoft at booth #362 to explore AI-powered public safety solutions and skilling opportunities. Together, we can build safer, more resilient communities through innovation.July 2025 - Microsoft 365 US Public Sector Roadmap Newsletter
Exchange Exchange Server Subscription Edition (SE) is now released and available Discover the Future of AI in Government Are you ready to explore the transformative power of artificial intelligence in the public sector? Join us as we delve into the key themes discussed in the recent seminar, "Microsoft AI for Government," led by Jason Payne, Chief Technology Officer for Microsoft Federal. What’s New in Microsoft 365 Copilot for Government | Microsoft Community Hub The AI-powered capabilities of Microsoft 365 Copilot are expanding across government environments. Whether you’re in GCC, GCC High, or DoD, here’s what you need to know about upcoming availability, what’s changing, and how to prepare. What’s New in Microsoft Teams | June 2026 New Microsoft Teams Chat and channels experience in GCC, Meeting notes powered by Loop now available for Microsoft 365 GCC High and DoD, Meeting inherits label from shared files - GCC [Premium] 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 Public Roadmap This link is filtered to show GCC, GCC High and DOD specific items. For more general information uncheck the boxes under “Cloud Instance”. Stay on top of Microsoft 365 changes Here are a few ways that you can stay on top of the Office 365 updates in your organization. Microsoft Tech Community for Public Sector Your community for discussion surrounding the public sector, local and state governments. Microsoft 365 for US Government Service Descriptions 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! Microsoft 365 Copilot MC1099688 — Microsoft PowerPoint: Use Microsoft 365 Copilot to rephrase text with natural language prompts Microsoft 365 Roadmap ID 494831, Microsoft 365 Roadmap ID 494832 and Microsoft 365 Roadmap ID 494833 Microsoft PowerPoint is introducing a new capability that enables users to rephrase or rewrite text using natural language instructions via Microsoft 365 Copilot. This enhancement allows for more tailored and expressive content creation directly in PowerPoint. A Microsoft 365 Copilot license is required to access this feature. This message refers to PowerPoint for Windows desktop, PowerPoint for Mac desktop, and PowerPoint for the web. When this will happen: General Availability (Worldwide): We will begin rolling out early July 2025 and expect to complete by late July 2025. General Availability (GCC): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. How this will affect your organization: After this rollout, users will see a new option under the existing Copilot rewrite dropdown menu in textboxes. This feature introduces a prompt box where users can enter natural language instructions to rephrase or replace selected text. This feature will be on by default. No changes to existing permissions or settings are required. 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. Learn more: The section called Using the PowerPoint Rewrite Feature in Elevate your presentation game with Copilot's text rewrite feature in PowerPoint - Microsoft Support (will be updated before rollout) MC1098924 — Microsoft 365 Copilot Chat for DoD customers Microsoft 365 Roadmap ID 494511 Beginning late July 2025, Microsoft 365 Copilot Chat (“Copilot Chat”) will be available by default at no additional cost for Entra account users in the DoD cloud with an eligible Microsoft 365 subscription: Microsoft 365 F1, F3, G3, or G5 Office 365 F1, F3, G3, or G5 Copilot Chat will be available by default from the web. It will also be available and pinned by default in the Microsoft 365 Copilot app (web), Teams (web, desktop), and Outlook (web). If Copilot Chat availability for any of these entry points changes, we will inform you. Web grounding in Copilot Chat will be off by default unless you have explicitly enabled web grounding using the “Allow web search in Copilot” Cloud Policy in the Microsoft 365 Admin Center. Note: This only applies to DoD. Copilot Chat will be available for GCC in June 2025 (please refer to MC1036580 for more information). Availability for GCC-H will be communicated later. When this will happen: General Availability (DoD): We will begin rolling out late July 2025. How this will affect your organization: Users will be able to access Copilot Chat in the Microsoft 365 Copilot app (web), Outlook (web), and Teams (desktop, web). Copilot Chat offers: Secure, enterprise-ready AI chat powered by models like GPT-4o. o Note: Web grounding will be off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” Cloud Policy. When web grounding is off, Copilot will only use the LLM pre-trained data to provide a response. IT controls for data governance, including enterprise data protection (EDP). Note: Agents will not be available initially. Agent availability will be communicated later. What you need to do to prepare: Once Copilot Chat rolls out and is available in your tenant, you will be able to manage access to it across entry points. To block access to Copilot Chat, refer to the documentation: Removing access to Copilot Chat. To block access from the web, and in the Microsoft 365 Copilot app and Outlook, refer to Step 2. To block access in Teams, refer to Step 3. Note: Since Copilot Chat will be pinned by default in the Microsoft 365 Copilot app, Outlook, and Teams once available, you do not need to implement Step 1. Additionally, Copilot Chat will not be available initially through the Microsoft Edge sidebar, so you do not need to implement Step 4. Web grounding in Copilot Chat is off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” Cloud Policy. To manage web grounding in Copilot Chat, please refer to our documentation here. To help your organization get the most out of the new Microsoft 365 Copilot Chat, we have updated the Copilot Success Kit and added the new Copilot Chat and Agent Starter Kit. This includes: Copilot Chat user training guideto help your users get started with Copilot Chat and understand how to access it. Copilot Chat and agent IT set up and controls guideto plan, deploy, manage, and measure Microsoft 365 Copilot Chat in your organization. User engagement templatesin a variety of formats—including email and Teams—that you can leverage to communicate updates and new features to your users. Note: You can customize these assets to remove content about agents since agents are not initially available. Please also refer to documentation for Copilot Chat here: Overview of Microsoft 365 Copilot Chat MC1094046 — Copilot in 1:1 and group calls on Teams phone devices Microsoft 365 Roadmap ID 495453 We’re introducing Copilot support for 1:1 and group calls on Teams certified phone devices, bringing real-time AI assistance directly into your calling experience. With this update, users can interact with Copilot during calls to generate call notes, recap conversations, and identify action items using prompt suggestions. This feature enhances productivity and ensures key information is captured during the call. Copilot is supported on both touch and non-touch Teams phone devices, with concise, device-optimized responses. Please note post-call summaries are not included in this release. When this will happen: General Availability (Worldwide) will begin in mid-July 2025 and is expected to complete by end of July 2025. How this affects your organization: Once available, users with eligible Teams phone devices and the appropriate licensing will be able to use Copilot during 1:1 and group calls. This feature is on by default for supported devices, provided the necessary policies are in place. To enable this experience: Devices must be updated to the latest Teams phone application. Users must have a Copilot license. Transcription must be enabled by admins (policy) and users (settings). What you can do to prepare: Admins should: Ensure Teams phone devices are updated to the latest version. Confirm that transcription policies are enabled in the Teams admin center. Communicate to users that they must enable transcription in their personal settings. Compliance considerations: Alters processing/storage of existing customer data Yes (transcription and in-call Copilot interactions) Introduces/modifies AI/ML capabilities with customer data Yes New end-user interaction with generative AI Yes Impacts Purview capabilities (DLP, labels, audit, etc.) Maybe (dependent on transcription and Copilot usage) Modifies user access/export/deletion of personal data (GDPR) Maybe (if Copilot-generated content is retained) MC1090693 — Create a meeting from an email thread with Copilot Microsoft 365 Roadmap ID 494154 Copilot now makes it easier to schedule meetings directly from email conversations. With the new Schedule with Copilot option, Copilot analyzes the email thread and automatically creates a meeting invitation—pre-filling the title, agenda, and attaching the email thread. Attendees from the email are added to the invite, and you can quickly review, edit, and send. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out on early July 2025 and expect to complete by late August 2025. How this will affect your organization: Once available, users will see a new Schedule with Copilot option in supported email threads. This feature streamlines meeting creation by reducing manual steps and improving consistency in meeting details. 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. MC1090692 — (Updated) Prepare for your on-the-go meeting with Copilot Microsoft 365 Roadmap ID 494845 Updated June 12, 2025: We have updated the timeline below. Thank you for your patience. Copilot is expanding its capabilities to mobile, helping users prepare for meetings while on the move. With this update, Copilot can quickly summarize key meeting-related content—such as emails, documents, action items, and previous meeting recaps—so users arrive informed and ready. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out on early July 2025 and expect to complete by late July 2025. How this will affect your organization: Mobile users will benefit from faster, more contextual meeting preparation. By surfacing relevant insights and tasks directly on their mobile device, users can stay productive and informed even when away from their desks. 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. MC1084034 — (Updated) Intelligent Recap Access for Multi-tenant Organization Microsoft 365 Roadmap ID 488298 Updated June 23, 2025: We have updated the timeline below. Thank you for your patience. Copilot users in a business-to-business multi-tenant organization set up can now view the intelligent meeting recap after the meeting from the resource tenant where the meeting was hosted. When this will happen: Targeted release: We will begin rolling out early August 2025 and expect to complete by mid-August 2025. General Availability: We will begin rolling out mid-August 2025 and expect to complete by late August 2025. How this will affect your organization: The new capability empowers users in multi-tenant setup to access meeting recap post meeting. What you need to do to prepare: No action required for either admin or users. Any Copilot users configured as a business-to-business user in a multi-tenant organization will have the capability after the launch. For additional information on B2B muti-tenant: Overview: B2B collaboration with external guests for your workforce MC1074972 — (Updated) Microsoft SharePoint: New web part for FAQs powered by Microsoft 365 Copilot Microsoft 365 Roadmap ID 482198 Updated June 6, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft SharePoint: A new web part for FAQs, to help assist content owners keep their content fresh and relevant. Powered by Microsoft 365 Copilot, this new web part can help content owner easily curate FAQ by working with agents and connected grounding data. Copilot license requirements: Reading: All readers can view FAQ web part content without a Copilot license. Creating & Editing: A Copilot license is necessary for creating and editing content using Copilot features. This feature requires a SharePoint license and a Microsoft 365 Copilot license. When this will happen: Targeted Release: We will begin rolling out late June 2025 (previously early June) and expect to complete by late June 2025 (previously mid-June). General Availability (Worldwide, GCC): We will begin rolling out early July 2025 (previously late June) and expect to complete by mid-July 2025 (previously early July). How this will affect your organization: After this rollout, authors can add the web part for FAQs directly to pages or news posts during editing. By selecting one or more grounding source files, AI will automatically generate FAQ content, reducing the time and effort needed for manual creation of FAQs. The web part currently supports FAQ types such as Event, Product, and Policy, with the option for authors to provide additional descriptions to guide more targeted content generation. FAQs created using the web part can be indexed for search and shared via email, making it easier to distribute consistent, up-to-date information to your organization. This change 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. Before rollout, we will update this post with new documentation. MC1068898 — (Updated) GCC: Designer Skills in Chat for PowerPoint and Word Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. We are excited to announce the release of Designer image skills in M365 Copilot to the GCC environment. This release includes the ability to generate images, add license free stock images or add enterprise images from a connected SharePoint organizational asset library (OAL). These features will be accessed through chat, in both PowerPoint and Word. When this will happen: General Availability (GCC): We will begin rolling out in late June 2025 (previously late May) and expect to complete by late June 2025 (previously late May). How this will affect your organization: These skills will be available to your organization by default in both PowerPoint and Word chat. What you need to do to prepare: You may consider updating your training and documentation as appropriate. This feature can be managed via the Office Cloud Policy Service. MC1068268 — (Updated) Account Switcher for Copilot Tab on iOS and Android Microsoft 365 Roadmap ID 490213 Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. You can now switch between accounts on the Copilot chat tab on iOS and Android. Simply swipe left to open the left-navigation and select from the list of supported accounts. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out in early July 2025 (previously early June) and expect to complete by late July 2025 (previously late June). How this will affect your organization: Currently, users are only able to access the Copilot Chat tab with their default account or privacy, even if they have other accounts that support Copilot. With account-switching on iOS and Android, users will be able to access Copilot Chat from other accounts that support Copilot, enabling them to access their chat history and graph data associated with those accounts. 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. MC1052912 — (Updated) Microsoft Teams - Copilot Summary for Transferred Calls Microsoft 365 Roadmap ID 484123 Updated July 1, 2025: We have updated the content. Thank you for your patience. Copilot enabled users will now be able to share the summary of the call from within the transfer panel and the context will be shown in the toast notification and within the call. This feature requires a Copilot license to be enabled. When this will happen: Targeted Release: We will begin rolling out early June 2025 and expect to complete by mid-June 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-June 2025 and expect to complete by early July 2025 (previously late June). How this will affect your organization: Once available and if transcribe is enabled, users will be able to share a summary or a call from the transfer panel. What you need to do to prepare: You may consider updating your training and documentation. No admin configuration required other than allowing users to transcribe their calls. MC1045226 — (Updated) Microsoft Teams: Speaker recognition and attribution in Teams Rooms on Android Microsoft 365 Roadmap ID 480715 Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. You can now use speaker recognition, transcript attribution, and AI capabilities in Teams Rooms on Android. Intelligent speaker functionalities are brought to existing speakers via the cloud. This feature identifies and attributes people in live transcripts, utilizing a unique voice profile for each participant enabling intelligent recaps and maximum value from Microsoft 365 Copilot and Teams Premium in meetings. Users can easily and securely enroll voices via Teams Settings. This feature requires a Teams Rooms Pro license. Users can enroll voices in the Teams Desktop. Learn more: Set up your digital voice profile When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 and expect to complete by late June 2025 (previously late May). How this will affect your organization: With speaker recognition, Teams Rooms on Android can identify speakers during live transcription in shared meeting rooms, ensuring clear and precise voice capture for every participant. This allows you to track who said what during the meeting through intelligent meeting recap and Copilot. What you need to do to prepare: While this functionality is still off by default, if you have already turned it on, be aware that it will enable this feature even for hardware that did not previously support it. To use this new capability, you need to first setup the right policies through PowerShell. For additional information about how to set the right policies, see Manage voice recognition technology controls for an Intelligent Speaker.Participants can set up a voice profile in minutes using the Teams Desktop application. Each person gets a unique voice signature, stored securely in your organization's tenant in the Microsoft Cloud to ensure that every contribution is accurately captured in every meeting, helping you to have a more productive meeting experience. For information about how to enable face and voice enrollment for your organization, see Overview of voice and face enrollment. MC1040542 — (Updated) Microsoft 365 Copilot and Microsoft 365 Copilot Chat: Increased transparency for web queries (GCC) Microsoft 365 Roadmap ID 483965 Updated June 5, 2025: We have updated the timeline below. Thank you for your patience. Users with licenses for Microsoft 365 Copilot and Microsoft 365 Copilot Chat will soon be able to see the exact web search queries used by Copilot to generate its response with relevant web data. Users will see this feature if you enable web search. Before this rollout, Copilot provided a list of websites that it used to generate its response. After this rollout, a user will also be able to review the exact queries sent by Copilot, which will enhance the user's awareness of how Copilot sourced the websites used to generate its response. Learn more: Introducing greater transparency and control for web search queries in Microsoft 365 Copilot and Microsoft 365 Copilot Chat | Microsoft Community Hub This feature will be available for both Web and Work chats in Microsoft 365 Copilot and in Microsoft 365 Copilot Chat. For more information on Microsoft 365 Copilot Chat availability, please refer to MC1036580 Microsoft 365 Copilot Chat for GCC customers (published March 2025). A Microsoft 365 Copilot license or an eligible Microsoft 365 license for Microsoft 365 Copilot Chat is required. When this will happen: General Availability (GCC): We will begin rolling out early June 2025 (previously mid-May) and expect to complete by late June 2025 (previously late May). How this will affect your organization: This feature will be available by default if you have enabled web search. Learn more about managing web search in Copilot for your organization 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. . MC1020213 — (Updated) Microsoft Teams Rooms: New Facilitator agent takes notes in ad-hoc and scheduled meetings (Public Preview) Updated June 4, 2025: We have updated the timeline below. Thank you for your patience. 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 June 2025 (previously late April) and expect to complete by late July 2025 (previously late May). 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. 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. Sharepoint Online MC1098935 — Microsoft SharePoint: Header and Footer enhancements Microsoft 365 Roadmap ID 489225 We’re updating the Microsoft SharePoint site header and footer to deliver a more modern, customizable, and brand-aligned experience. This visual enhancement introduces new options for customizing the header, footer, and navigation links—empowering site owners to better reflect their organization’s identity and create more engaging, connected SharePoint sites. When this will happen: Targeted Release: We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (Worldwide, GCC): We will begin rolling out late July 2025 and expect to complete by mid-August 2025. General Availability (GCC High, DoD): We will start rolling out mid-August 2025 and expect to complete by late August 2025. How this will affect your organization: These updates will enhance the visual consistency and usability of SharePoint sites, making it easier to deliver visually compelling, on-brand experiences across your organization. For site viewers: The command bar will be hidden in View mode for a cleaner, more immersive experience. Teaching tips will help users locate previously available command bar buttons in the header. For site owners: New design flexibility will include: Set an image as the header or footer background and customize the overlay color. Change fonts for the site title, navigation links, footer name, and footer links using a set of predefined font families. Adjust footer alignment, including support for left alignment. This change will be on by default. After this rollout, site admins can customize the header background under the new Design tab in the Header configuration panel: Site viewers will have a cleaner, more immersive experience with the command bar hidden in View mode. 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. Before rollout, we will update this post with new documentation. MC1094051 — (Updated) Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries Updated June 24, 2025: We will not be proceeding with this change at this time. Thank you for your patience. We are evaluating the retirement of the SharePoint Framework (SPFx) Field Customizers feature from SharePoint Lists and Document Libraries. In many cases, we recommend alternatives like using Column Formatters and disabling SPFx Field customizers. This would help with better performance with modern experience that is continuously updated. When this will happen: We are currently assessing the timelines and will update this post as plans progress. You can be assured that it will be communicated well in advance, with ample time to manage transition effectively. How this affects your organization: There is no impact to your organization as of now. In future depending on updated timelines, SharePoint Lists or Document Libraries with SPFx Field Customizers may get affected: Field Customizers will no longer render custom code. Column data will display using the default rendering based on column type. Other SPFx extensions, such as Command Set Customizersand Application Customizers, will continue to function as expected. We recommend transitioning to Column Formatting for visual customizations where possible. For scenarios requiring third-party code execution, continue using Command Set Customizers or Application Customizers. What you can do to prepare:: Review your current use of Field Customizers and begin planning your transition. Additional information: Support update for SharePoint framework field customizers in lists and document libraries MC1088170 — Microsoft SharePoint: Estimated read time for News posts Microsoft 365 Roadmap ID 491024 We will add an estimated read time to Microsoft SharePoint News posts to help users better manage their time and engagement. This message applies to SharePoint News on the web and the Microsoft Viva Connections app in Microsoft Teams for Windows desktop, Teams for the web, and Teams for Android and iOS. When this will happen: Targeted Release: We will begin rolling out early June 2025 and expect to complete by mid-June 2025. General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: After this rollout, SharePoint News posts will display an estimated read time. This will appear in the banner web part of each news item: The feature is on by default. Authors can toggle it on or off in the settings panel of the banner web part: 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 your relevant documentation. Learn more: Create and share news on your SharePoint sites - Microsoft Support (will be updated before rollout) MC1072408 — (Updated) Microsoft SharePoint: Storage insights will be included in Microsoft 365 admin center usage reports Microsoft 365 Roadmap ID 482200 Updated June 24, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for the Microsoft SharePoint usage report in the Microsoft 365 admin center: A new Storage tab will provide a high-level view of your overall SharePoint quota consumption and recommended actions for storage management. Note: This report is available to non-Education tenants. Education tenants should refer to their pooled storage report. Learn more about viewing the pooled storage report: Pooled storage management - M365 Education | Microsoft Learn When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-May 2025 and expect to complete by late June 2025 (previously mid-June). How this will affect your organization: The SharePoint storage report provides an overview of your tenant’s storage profile across multiple geographies. It will help you understand your tenant’s storage growth trend and make informed decisions on when to buy more storage or clean up usage. The report will include suggestions for optimizing storage, such as setting file history limits, archiving inactive sites, and creating site lifecycle management policies. Also, banner notifications will appear when your tenant is approaching or over the storage quota. To start using the SharePoint storage report: In the Microsoft 365 admin center, go to Reports > Usage page From the homepage dashboard, under Reports,select SharePoint. Select the Storage tab. The new Storage tab on the SharePoint storage report in the Microsoft 365 admin center: What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Learn more: Microsoft 365 Reports in the admin center – SharePoint storage - Microsoft 365 admin | Microsoft Learn MC1055557 — (Updated) SharePoint Online: Content Security Policy Control in Tenant Administration Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. SharePoint Online Tenant Administrators can now allow script sources for modern pages in SharePoint sites. This feature is particularly useful in scenarios where modern pages have custom code that loads scripts (e.g., TypeScript code) from external sources like a content delivery network (CDN). SharePoint will now report to administrators where sources that have not been allowed are loaded from, providing a way for administrators to identify those sources and take action. Tenant Administrators can also enforce browsers to only load scripts from allowed sources. This behavior can be enabled using SharePoint Online Management Shell. When this will happen: Targeted Release: We will begin rolling out on late March 2025 and expect to complete by early April 2025. General Availability (Worldwide): We will begin rolling out on late April 2025 and expect to complete by late April 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out on late April 2025 and expect to complete by late June 2025 (previously early June). How this will affect your organization: Tenant Administrators will have the option to control and govern where custom code loads scripts and, if needed, enforce browsers to only load scripts from trusted sources. A new "Trusted script sources" page will give administrators control over which source can be trusted to load scripts. What you need to do to prepare: This rollout will happen automatically with no admin action required. MC921752 — (Updated) Retirement of the SharePoint SendEmail API Updated June 5, 2025: As a reminder from the post announced on October 31st, 2024, we will be retiring the Utility.SendEmail API on October 31st, 2025. In addition, you are now able to identify usage of the API via the Purview audit logs in the admin center As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center. Open Audit to search for activities. Select a date range to run the audit search for (recommend running it for at least 90 days) Put the following text, “SendEmailApiInvoked” into the “Activities – operation names” textbox and click search. The request will be queued, and results will be available once processed. Click on the results and review each of the items. Use the UserAgent and ApplicationDisplayName to help identify the caller. NOTE: If the ApplicationDisplayName = “Workflow” then the items will be unaffected by this API retirement but will follow the SharePoint 2013 Workflow retirement. We will be retiring the Utility.SendEmail API from SharePoint. The SP.Utilities.Utility.SendEmail could be used to send emails from custom applications or processes within SharePoint Online, including Power Automate, and custom workflows. From custom code the API can be referenced via REST as (“/_api/SP.Utilities.Utility.SendEmail”) while for CSOM, it would be “Utility.SendEmail” with more information on the original implementation at Utility.SendEmail method for CSOM. When this will happen: October 31, 2025 How this will affect your organization: Any components, custom code, or Power Automate connections that utilize the SP.Utilities.Utility.SendEmail API, should be updated before the end of life date. The API will stop providing services on the retirement date and will no longer send any email requests from that date. What you need to do to prepare: Migrate any custom code, power automate, processes or policies running within SharePoint Online that have been configured to send email using the SP.Utilities.Utility.SendEmail API. The following are recommended or alternative approaches: Use Microsoft Graph to send email using the user: SendMail API (Part of the Outlook mail workload) Automate creating, sending, and processing messages Customizations through Power Automate may also utilize the Outlook connector and utilize “Send an email” within the Actions. Overview of using Outlook and Power Automate Learn more: Retirement of the SharePoint SendEmail API Automate creating, sending, and processing messages Overview of using Outlook and Power Automate Learn about the Microsoft Purview portal | Microsoft Learn OneDrive for Business MC1089315 — Resharing to external users required after enabling Microsoft SharePoint integration with Microsoft Entra B2B Updated June 26, 2025: We have updated the content. Thank you for your patience. As part of our ongoing efforts to enhance security, we are making a critical change to how Microsoft SharePoint and Microsoft OneDrive integrate with Microsoft Entra B2B. This change affects how external users access previously shared content. When this will happen: Effective July 1, 2025, external users will no longer be able to access files, folders, or sites using links that were shared via SharePoint One Time Passcode (OTP) before your organization enabled Microsoft SharePoint and OneDrive integration with Microsoft Entra B2B. How this will affect your organization: All users in every tenant that has already enabled or in future, will enable SharePoint integration with Entra B2B are impacted. Your external users will lose access to all the files, folders and sites shared via SharePoint One Time Passcode (OTP) before enabling this integration. To give access again, resharing is required. After the integration is enabled, external sharing will use Microsoft Entra B2B Invitation Manager. Learn more: B2B Invitation Redemption - Microsoft Entra External ID | Microsoft Learn External users attempting to use older links will encounter an error message "Sorry, something went wrong. This organization has updated its guest access settings. To access this item, please contact the person who shared it with you and ask them to reshare it with you. Impact to end users: External users will lose access to content shared before your tenant enabled SharePoint integration with Entra B2B. To restore access, users must reshare the file, folder, or site with the intended external collaborators. If the original sender is unavailable or lacks permission, another authorized user must reshare the content. No changes are required to the sharing process—users can continue to share content as they always have. What you need to do to prepare: Notify your users: Inform your users who collaborate externally that previously shared links will no longer work. Update internal documentation: Adjust training materials and helpdesk scripts to reflect this change. Learn more: Microsoft Entra B2B integration for SharePoint & OneDrive - SharePoint in Microsoft 365 | Microsoft Learn MC1079736 — (Updated) Microsoft SharePoint and Microsoft OneDrive: Apply watermark to PDFs Microsoft 365 Roadmap ID 485796 Updated June 26, 2025: We have updated the timeline below. Thank you for your patience. Microsoft OneDrive and Microsoft SharePoint for web will soon let users add text or images as watermarks to PDF documents. Users can place the watermark in front of their content and choose the desired location and angle for the watermark. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late June 2025 (previously mid-June) and expect to complete by mid-July 2025 (previously early July). How this will affect your organization: To add text as a watermark: Open a PDF stored in OneDrive or SharePoint and then select Edit at the top right of the screen. Select Watermark from the top menu, enter your text, customize the formatting and color, and place the watermark in the desired position. Choose from nine positions: top left, top center, top right, middle left, middle center, middle right, bottom left, bottom center, and bottom right. Text formatting options include bold, italic, color, size, transparency, and rotation. Preview changes on the right side of the screen, and then select Applyto save changes. To add an image as a watermark: From the Watermarkdialog box, select Picture to insert an image as a watermark. Adjust scale, transparency, and rotation if desired. Set the image in the desired position. Choose from nine positions: top left, top center, top right, middle left, middle center, middle right, bottom left, bottom center, and bottom right. Preview changes on the right side of the screen, and then select Applyto save. To edit an existing watermark: Select Watermark from the top menu, and then select the watermark to edit. Follow the same steps for adding text or images to modify text or images in the watermark. To add another watermark, select Add new under the Watermark toolbar. To remove a watermark: Select Watermarkfrom the top menu, and then select the watermark to remove. Select the Removebutton at the bottom of the screen. FAQs Can I modify watermarks using other PDF tools? Watermarks added in OneDrive or SharePoint will be visible in other PDF tools but cannot be edited or removed with third-party tools. Does applying a watermark change my original PDF? Yes, applying a watermark will change your PDF document. The watermark is superimposed on the PDF content. Users can easily remove any watermark applied in OneDrive or SharePoint. What you need to do to prepare: Note: Some users may see this feature before other users in your organization. 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. Before rollout, we will update this post with new documentation. MC1077863 — (Updated) Microsoft OneDrive and Microsoft SharePoint: Use the table of contents in a PDF to navigate Microsoft 365 Roadmap ID 486859 Updated June 27, 2025: We have updated the timeline below. Thank you for your patience. Microsoft OneDrive for the web and Microsoft SharePoint Online will be able to display a table of contents if a PDF already has one. Users can select an item in the table of contents to jump directly to the location of that item in the PDF. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-July 2025 (previously mid-June) and expect to complete by early August 2025 (early July). How this will affect your organization: Open a PDF in OneDrive for the web or in SharePoint. If your PDF contains a table of contents, it will show up on the left side of your screen. Select any line item to jump directly to the page To close the table of contents, select the X in the top right of the panel. Select the View the table of contentsicon in the top left of the panel to open it again. This feature will be on by default. What you need to do to prepare: Note: Some users may see this feature before other users within your organization. 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. Microsoft Viva MC1102792 — Microsoft Viva Amplify and SharePoint News: Videos will play in Microsoft Outlook instead of web browser Coming soon: Videos embedded using the Stream webpart in Microsoft Viva Amplify publications and Microsoft SharePoint News pages will play inline in emails in new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web. Users will be able to watch videos in Outlook without leaving Outlook to watch videos that open in a web browser. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early July 2025 and expect to complete by early September 2025. How this will affect your organization: This feature will be on by default. Learn more about admin controls for this feature in the Limiting who can use the feature section of Embed and play back videos in Outlook and Loop | Microsoft Learn 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 your relevant documentation. Learn more Embed and play back videos in Outlook and Loop | Microsoft Learn How to insert Stream videos in Loop and Outlook - Microsoft Support #newoutlookforwindows MC1096224 — (Updated) Microsoft Viva Engage: Microsoft Yammer JavaScript SDK will retire Updated June 30, 2025: We have updated the content and rollout timeline below. Thank you for your patience. As communicated previously in Embracing a Fully Modern Viva Engage Experience | Microsoft Community Hub (April 2025) and MC1048615 (updated) Announcing the retirement of legacy Yammer application platform (April 2025), we will retire the Microsoft Yammer JavaScript SDK on July 31st. This SDK enables developers to call Yammer APIs from custom applications and websites. As part of our ongoing efforts to modernize and streamline the developer experience, we are removing access to the hosted SDK assets that support client-side integrations. Please note that no extensions will be provided post July 31st, 2025 to support Yammer SDK assets. Customer must transition to alternatives mentioned on this post. After this retirement, these SDK assets will return a 404 error when requested: https://c64.assets-yammer.com/assets/platform_js_sdk.js https://canary-azure.assets-yammer.com/assets/releases/stable/yam-platform-sdk-page-bootstrap-4e1320deb0f28de220d7.js Any applications or websites relying on these scripts will break. Developers will see 404 errors in browser consoles, and SDK methods will no longer function. The impact on end users will vary depending on how the SDK is integrated into your custom solutions. What you can do to prepare:: Remove dependencies on the Yammer JavaScript SDK as soon as possible. Use alternatives such as the Yammer REST APIs or Viva Engage APIs available via Microsoft Graph. If you have downloaded and deployed the SDK assets with your application (an unsupported scenario), ensure they are removed from your deployment. MC1048615 — (Updated) Announcing the retirement of legacy Yammer application platform Updated June 23, 2025: We have updated the content below. Thank you for your patience. In CY25Q3, the legacy Yammer application platform will be retired, along with the oAuth2 authentication flow via these applications. If planning to use Yammer APIs in your tenant, follow this guide to authenticate using Entra (AAD) tokens. Customers will need to migrate existing applications to use Entra (AAD) tokens to remove all reliance on legacy Yammer application registrations. Additionally, we will retire the Microsoft Yammer JavaScript SDK starting June 30, 2025, and ending by late July 2025. This SDK enables developers to call Yammer APIs from custom applications and websites. As part of our efforts to modernize and streamline the developer experience, we are removing access to the hosted SDK assets that support client-side integrations. Applications or websites relying on these scripts will break, and developers will see 404 errors in browser consoles When this will happen: Worldwide: All user experience for registering and using Yammer applications will be retired by the end of June 2025. Yammer JavaScript SDK will be retired starting June 30, 2025, with access to hosted SDK assets ending by late July 2025. After this date, the following scripts will return 404 errors: https://c64.assets-yammer.com/assets/platform_js_sdk.js https://canary-azure.assets-yammer.com/assets/releases/stable/yam-platform-sdk-page-bootstrap-4e132 How this will affect your organization: The impact depends on your use of legacy Yammer applications. Organizations with custom applications or partners developing applications may be more impacted than those using out-of-the-box features of Viva Engage. Admins should review usage of legacy Yammer applications with relevant stakeholders. No impact if your organization does not use Yammer APIs or uses Entra applications to call Yammer APIs. This is the recommended method to authenticate when using Yammer APIs. Learn more. No changes are expected to the functionality of Yammer APIs. For CORS (Cross-Origin Resource Sharing) support, Yammer app creations may be allowed as an exception, following the JavaScript app guidance in the documentation. When opening a support case to request legacy Yammer application registration for CORS issue, information on usage will be required. Approval or denial will depend on the details of the request. You may be directed to use a modern alternative, and guidance will be provided in the response to your support request. Any applications using the Yammer JavaScript SDK will stop functioning once SDK assets are removed. What you need to do to prepare: Review your usage of custom and partner applications which connect to Viva Engage (Yammer). Identify any requirements for legacy Yammer application registration and use a modern alternative when available. If planning to use Yammer APIs in your tenant, follow this guide to authenticate using Entra (AAD) tokens. We recommend migrating existing applications to use Entra (AAD) tokens as soon as possible to remove all reliance on legacy Yammer application registrations. Remove dependencies on the Yammer JavaScript SDK as soon as possible. Use alternatives such as the Yammer REST APIs or Viva Engage APIs available via Microsoft Graph. If you have downloaded and deployed the SDK assets with your application (an unsupported scenario), ensure they are removed from your deployment. Microsoft Teams MC1107491 — Microsoft Teams: Compact notification size for users Microsoft 365 Roadmap ID 496175 We’re introducing a new compact toast notification size in Microsoft Teams for Windows. This update gives users the option to reduce the visual footprint of notifications, offering a cleaner, more minimalist experience that helps reduce screen clutter and distractions. When this will happen: Targeted Release: Rolling out early July 2025, expected to complete by mid-July 2025. General Availability (Worldwide): Rolling out mid-July 2025, expected to complete by late July 2025. General Availability (GCC, GCC High, DoD): Rolling out late July 2025, expected to complete by late July 2025. How this will affect your organization: After this rollout, Windows users will be able to choose between the standard and compact toast notification sizes in Teams by navigating to: Settings > Notifications > Choose Compact This feature is off by default and must be enabled by the user. It is designed to improve focus and reduce screen clutter, especially in high-notification environments. What you need to do to prepare: No admin action is required. The feature will be available to all users once their Teams client updates to the supported build. There are no admin controls for this feature. You may consider notifying your users about this new option to help them tailor their notification experience. MC1106873 — Microsoft Teams | Virtual Desktop Infrastructure (VDI) and Citrix: New Plugin for SlimCore-based Optimization Microsoft 365 Roadmap ID 375418 We’re introducing a new plugin for Microsoft Teams in Citrix Virtual Desktop Infrastructure (VDI) environments. This update delivers improved performance and a streamlined user experience through a new SlimCore-based optimization architecture (VDI 2.0). The plugin (version 2025.14.1.8) introduces a new MSIX packaging model and simplifies permission prompts for users. When this will happen: Targeted Release: We will begin rolling out early July 2025 and expect to complete by late July 2025. General Availability (Worldwide, GCC): We will begin rolling out late July 2025 and expect to complete by early August 2025. General Availability (GCC High, DoD): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. How this will affect your organization: This change introduces a new plugin and packaging model for Teams VDI optimization with the SlimCore media engine: Users will see a one-time permission prompt for microphone and camera access when launching Teams with the new plugin. Once granted, they will not be prompted again after future updates. A new app entry, Microsoft Teams VDI Optimizer, will appear under Settings > Apps > Installed apps. Previous entries for "Microsoft Teams VDI" will be automatically cleaned up after a certain period of time. IT admins must update AppLocker, Windows Defender Application Control (WDAC), and Group Policy settings to accommodate: - New run location for MsTeamsVdi.exe. - New package family names: Microsoft.Teams.SlimCoreVdiHost.win-x64_8wekyb3d8bbwe Microsoft.Teams.SlimCoreVdiFwk.win-x64._8wekyb3d8bbwe Visual representation of the new Slimcore-based Microsoft Teams VDI plugin architecture, highlighting the separation into Host and Framework MSIX packages: What you need to do to prepare: For managed devices: Review and update AppLocker/WDAC policies and the BlockNonAdminUserInstall GPO to allow the new SlimCore Host and Framework packages For Bring Your Own Device (BYOD) devices: No action is required if restrictive policies are not in place. The Citrix Workspace app can update the plugin automatically without admin privileges. Alternatively, download the new pluginto install manually. Learn more: Microsoft Teams - Classic Teams for Virtualized Desktop Infrastructure | Microsoft Learn MC1104311 — Microsoft Teams: Usability and privacy improvements for live captions and transcripts in meetings Microsoft 365 Roadmap ID 495454 We’ve made several usability improvements to enhance live captions and live transcripts in Microsoft Teams — making meetings more intuitive, less distracting, and more privacy-conscious. First, live captions will be scrollable, allowing users to review the meeting conversation without interrupting the live view. To help protect sensitive content and support compliance with data handling policies, copying text from live captions is now disabled by default. This ensures captions remain a real-time experience, reducing the risk of content being copied and shared out of context. Second, the Live transcript panel will no longer open automatically for the user who starts recording, which also triggers transcription in the background. Before this rollout, this panel only auto-opens for the person who initiates recording or transcription — not for other participants — but this can be distracting and isn’t always relevant to the user's intent. After this rollout, the Live transcript panel will remain closed unless manually opened or the user explicitly starts transcription. This gives users more control over their meeting layout and helps avoid unnecessary screen changes during important discussions. Third, when transcription is enabled, users who attempt to open the Live transcript panel will now see a banner suggesting they switch to live captions instead. This helps guide users to the most appropriate feature for following the conversation in real time, improving comprehension and reducing confusion. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. When this will happen: Targeted Release: We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (GCC High): We will begin rolling out late July 2025 and expect to complete by early August 2025. General Availability (DoD): We will begin rolling out early August 2025 and expect to complete by mid-August 2025. How this will affect your organization: These updates improve usability, privacy, and accessibility in Teams meetings. Users gain more flexibility with captions and fewer disruptions from auto-opening panels. Disabling caption copying supports compliance by minimizing accidental data sharing. The in-product banner helps guide users to the best experience for real-time engagement. The message "You can't copy the selected text" will appear if a user tries to copy live captions after this rollout: What you need to do to prepare: No admin action is required. This feature has no admin controls. These changes will roll out automatically and will be available by default. To support awareness and adoption: Inform users about scrollable captions and changes to the Live transcriptpanel. Update training materials, if applicable. If your organization previously relied on copying captions, note that live transcripts remain the official source of meeting content. Learn more Use live captions in Microsoft Teams meetings - Microsoft Support(will be updated before rollout) Manage chat for sensitive Teams meetings - Microsoft Teams | Microsoft Learn(will be updated to remove live caption information) Compliance considerations: These changes do not alter how customer data is stored or processed. However, disabling caption copying by default helps protect sensitive content during meetings and supports compliance with internal policies. Live transcripts are unaffected and remain accessible via standard Microsoft 365 compliance tools (such as Microsoft Purview eDiscovery, Microsoft Purview Data Loss Prevention, and DLP retention). MC1104306 — Microsoft Teams: Users can save chats and channel messages for later Microsoft 365 Roadmap ID 496369 We're introducing a new user feature in Microsoft Teams that allows individuals to save any message—whether it's a post, reply, or chat—and access it later from the Saved view in their Chat or Teams list. Clicking a saved message will open the full conversation in the right pane, enabling users to review or respond directly. This helps users quickly return to important information without scrolling through long threads. 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: Targeted Release: We will begin rolling out early August 2025 and expect to complete by mid-August 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late August 2025 and expect to complete by early September 2025. How this will affect your organization: After this rollout, users will be able to save their messages and recall them later to support their personal workflows: Users can go to the three-dot menu for a message and select Save this message: The saved message will display in the user's Saved messages list in their Chat and Teams lists: What you need to do to prepare: No admin action needed and no admin controls exist. This feature will be available by default. This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your admins and/or users about this change and update internal documentation. Before rollout, we will update this post with new documentation. Compliance considerations: Does the change alter how existing customer data is processed, stored, or accessed (e.g. documents, emails, chats, etc.)? Yes. Saving a message creates a copy of the original message. If the original message is deleted, the saved copy will also be deleted in accordance with existing retention policies. No admin action is required, but an existing retention policy must be in place. MC1103605 — Microsoft Teams admin center: Additional monitoring scenarios in Best Practice Configurations dashboard Microsoft 365 Roadmap ID 492982 We’re expanding the Best practice configurations dashboard in the Microsoft Teams admin center to include additional monitoring scenarios. This dashboard helps Teams administrators assess how well their tenant aligns with Microsoft’s recommended best practices for optimal collaboration—particularly for meeting experiences. This message applies to Teams for Windows desktop, Teams for the web, and Teams for Mac. When this will happen: General Availability (Worldwide and GCC): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. How this will affect your organization: The Best practice configurations dashboard helps ensure a high-quality Teams experience by identifying areas where your network setup may not align with Microsoft’s recommendations. In this release, the dashboard will monitor three additional scenarios: Bypass local proxy Bypass cloud proxy DNS resolution failures Non-conformant locations will be highlighted on the dashboard and summarized in a widget on the main page. Admins will also see a breakdown by city and subnet/IP address, with export options for sharing insights with relevant teams. Only locations with significant non-conformance will be shown, to reduce noise. As issues are resolved, the dashboard will track trends to help monitor progress over time. After this rollout, visit the Meetings section of the Teams admin center to view the updated dashboard. Use the export and recommended remediations to collaborate with your networking teams and address any flagged issues. This feature will be available by default for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your admins and/or users about this change and update internal documentation. Learn more: Best practice configurations dashboard for Microsoft Teams meetings - Microsoft Teams | Microsoft Learn MC1103603 — Microsoft Teams Phones: Configure line keys in Teams admin center for streamlined device management Microsoft 365 Roadmap ID 493320 We’re introducing a new capability in the Microsoft Teams admin center (TAC) that allows IT admins to configure line keys on Microsoft Teams-certified phone devices. This enhancement simplifies setup and management by enabling assignment of line keys to contact types such as speed dials, call queues, and shared lines—supporting both personal and common area phone (CAP) scenarios. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (GCC High): We will begin rolling out mid-September 2025 and expect to complete by late September 2025. General Availability (DoD): We will begin rolling out mid-November 2025 and expect to complete by late November 2025. How this will affect your organization: After this rollout, admins can assign line keys in the Teams admin center in two ways: Using a generic configuration section (device-agnostic) Using device model-specific templates Important: For common area phones, line key assignment will be managed exclusively through the Teams admin center. Personal phones will continue to support line key assignment both on the device and via the Teams admin center. To ensure successful configuration, users must allow admin overrides in device settings. This feature will be available by default on Teams phone devices running the latest application version and visible in the Teams admin center. It enhances consistency and control across Teams-certified phones, especially in shared environments. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins and/or users about this change and update internal documentation. Compliance considerations: Does the change store new customer data? Yes. MC1098931 — Microsoft Teams admin center: Apply only configured settings from configuration profiles for Teams Android devices Microsoft 365 Roadmap ID 313800 We’re introducing an improvement to configuration profiles in the Microsoft Teams admin center for Android devices. Admins will now have more granular control—only explicitly configured settings in a profile will be applied to devices, preventing unintended changes. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (GCC High): We will begin rolling out early August 2025 and expect to complete by mid-August 2025. General Availability (DoD): We will begin rolling out early September 2025 and expect to complete by mid-September 2025. How this will affect your organization: Before this rollout, assigning a configuration profile applies all settings—including those left unconfigured—with default values. This sometimes causes unintended changes (such as language or time zone). After this rollout: Only settings explicitly configured in the profile will be applied. Settings left as Not configuredwill remain unchanged on the device. This change simplifies bulk management and reduces the risk of overwriting regional or OEM-specific defaults. The new configuration profile experience will be available by default for admins to configure, as follows: Create a configuration profile Go to Teams Devices >[device type]> Configuration profiles and select Add. By default, all settings will display as Not configured. Enter a name for the profile and optionally add a friendly description. Configure the settings you want for the profile and select Review changes. In the Review configured settings pop-up, compare and confirm before saving. Select Save. Assign a configuration profile Go to Teams Devices> [device type Select one or more devices, and then select Assign configuration. If any selected devices are from OEMs that don’t yet support this feature, you will see a warning in the Assign a configuration pane: Note: Many OEMs have already implemented support for this feature. We are working with the remaining OEMs to enable it over the next few months. We will publish full OEM support details in the public documentation after the release begins. In the Assign a configurationpane, search for the configuration profile to assign to the selected devices. Select Apply. Edit a configuration profile Go to Teams Devices >[device type] > Configuration profiles. Select the configuration profile you want to edit. Configure the desired settings and select Review changes. Review and confirm the settings in the pop-up, then select Save. If the profile was already assigned to devices, changes will be applied automatically. If the profile was not already assigned, assign the updated profile to devices as needed. Reassign a configuration profile To reassign a configuration profile to the existing assigned devices, without making any changes to settings Go to Teams Devices >[device type] > Configuration profiles. Select the configuration profile you want to reassign. At the bottom of the configuration profile, a Reassign button will appear if the profile was assigned to a device Select Reassign, review the configured settings, and then select Save. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before or after the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins and/or users about this change and update internal documentation. Learn more: The Use configuration profiles section in Manage devices in Microsoft Teams - Microsoft Teams | Microsoft Learn (will be updated before rollout) MC1098172 — Microsoft Teams: New feature suggests contacts for call transfers on Teams Phone devices Microsoft 365 Roadmap ID 495457 To streamline the call transfer experience on Microsoft Teams Phone devices, we’re introducing intelligent suggestions for call transfer targets. With this feature, your organization can reduce clicks and save time with intelligent call transfer suggestions. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (GCC High): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. General Availability (DoD): We will begin rolling out early September 2025 and expect to complete by mid-September 2025. How this will affect your organization: After this rollout, the intelligent suggestions will provide relevant contacts based on a user’s recent call activity and their group associations, reducing the number of steps needed to complete a transfer and improving in-call efficiency. Users on Teams phone devices will see a new Suggested Call Transfer Targets section, ranked above speed dial entries along with group contacts. These suggestions are based on recent call history and update asynchronously when users access their call history and their group associations. Both touch and non-touch devices are supported. Sections for suggestions, speed dial, and groups are collapsible and expanded by default. When a user initiates a search, these sections are hidden to prioritize search results. This feature is on 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. Review your current configuration to assess the impact on your organization. You may want to notify your admins and/or users about this change and update internal documentation. Device requirements: Ensure all Teams phone devices are updated to the latest application version to receive this feature. Learn more: Microsoft Teams | Teams devices management apps. Compliance considerations: Does the change alter how existing customer data is processed, stored, or accessed? Yes, it uses call history to generate suggestions. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? Yes, it uses intelligent suggestions based on call history. MC1094074 — Microsoft Teams | New feature: Shared spaces insights in the Pro Management portal Microsoft 365 Roadmap ID 493318 We’re introducing a new Shared Spaces Insights page in the Teams Rooms Pro Management portal. This feature provides IT admins with detailed utilization insights for shared spaces, starting with Teams Rooms. It includes time-series data visualizations and filtering options such as location, business hours, days of the week, and date ranges—making it easier to understand how meeting spaces are being used across your organization. Learn more: Microsoft Teams Rooms Pro Management Portal | Microsoft Learn. When this will happen: Public Preview: Rolling out in July 2025 and expected to complete within the same month. General Availability (Worldwide, GCC): Also rolling out in July 2025, with completion expected by the end of the month. How this will affect your organization: The new Shared Spaces Insights feature will help IT admins optimize space planning and improve meeting room utilization. This feature will be on by default for tenants with a Teams Rooms Pro license. What you need to do to prepare: Access Shared Spaces Insights and ensure that your tenant has at least one Teams Rooms Pro or Premium license assigned. To ensure Teams Rooms on Android devices are visible in the Shared Spaces Insights page, update them to Admin Agent version 1.0.0.202412110504 or newer. Devices updated to the required Admin Agent version on or before May 6, 2025 will begin reporting utilization metrics starting May 6, 2025. Devices updated after May 6, 2025 will begin reporting utilization metrics only going forward after the Admin Agent version is upgraded to 1.0.0.202412110504 or newer. Please allow 24 to 48 hours for the utilization metrics to populate. Devices running older versions of the Admin Agent will not appear in the Shared Spaces Insights dashboard until they are updated. No additional configuration is required. Before rollout, we will update this post with new screenshots. Compliance considerations: Does the change alter how existing customer data is processed, stored, or accessed? Yes - It uses calendar and occupancy data from Teams Rooms. MC1094047 — Custom Ringtone Behavior and Ringtones for Assigned Line Keys Roadmap ID 495451 We’re introducing new customization options for Teams-certified phone devices that enhance how users manage incoming calls. With this update, users can personalize the behavior and ringtone for each assigned line key—choosing from ring only, ring with flash, or flash only. Unique ringtones can also be assigned per line key, making it easier to identify calls at a glance. This feature is supported across touch, non-touch, and sidecar devices, giving users more control over their call experience. End users will be able to configure these settings directly on their devices. Admin-level controls are planned for a future release. When this will happen: Worldwide/GCC Clouds: Rolling out from mid-July 2025 through end of July 2025 GCCH Clouds: Rolling out from mid-August 2025 through end of August 2025 DoD Clouds: Rolling out from early September 2025 through mid-September 2025 How this affects your organization: Users with Teams-certified phone devices will be able to customize how each line key alerts them, improving call management and reducing missed or misidentified calls. This feature is on by default for users with the latest Teams phone application update. No admin action is required at this time. What you can do to prepare:: Ensure that Teams phone devices in your organization are updated to the latest application version to enable this functionality. Communicate this enhancement to your users and help desk teams so they are aware of the new customization options. MC1093230 — Action Recommended: Script To Uninstall Classic Teams Action Recommended: Script To Uninstall Classic Teams If you have already migrated to New Teams, you can use the following script to uninstall Classic Teams: Uninstall Script for Classic Teams. Note that Classic Teams will be unavailable to use in 19 days. We recommend reviewing the documentation to ensure proper deployment across your environment. To avoid disruption, please ensure all users are fully migrated to the new Teams experience. Learn more: Pre-installation script for new Teams client - Microsoft Teams | Microsoft Learn The Prerequisites for target computerssection of Bulk deploy the new Microsoft Teams desktop client - Microsoft Teams | Microsoft Learn Script to Uninstallation Classic Teams Download New Teams MC1092431 — (Updated) Microsoft Teams Premium: Branding will extend to town halls and webinars Updated June 25, 2025: We have updated the timeline below. Thank you for your patience. We’re expanding the availability of Microsoft Teams Premium branding to include town halls and webinars. This enhancement enables organizers to deliver polished, on-brand experiences across more event types—strengthening brand affinity and engagement from the moment attendees join. This feature requires a Teams Premium license. 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, GCC High, DoD): We began rolling out late May 2025 and expect to complete by early July 2025 (previously mid-June). How this will affect your organization: After this rollout, if your organization has configured branding in the Teams admin center, it will automatically apply to: Town halls Webinars Regular meetings (already supported) Branded elements will appear on the pre-join screen and during the meeting experience, including: Organization logo Custom background image Brand hex color Organizers with a Teams Premium license can disable branding for individual events via Meeting Options in the scheduling form. 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. Review your current branding configuration in the Teams admin center to assess the impact on your organization. You may want to notify your admins and/or users about this change and update internal documentation. Learn more: An overview of customizations for meetings in Microsoft Teams - Microsoft Teams | Microsoft Learn MC1090696 — (Updated) Microsoft Teams: Teams Rooms Pro Management portal will be generally available (DoD) Microsoft 365 Roadmap ID 493323 Updated June 23, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams Rooms Pro: The Teams Pro Management service and portal will be generally available. You will be able to use the remote device management and analytics features of the solution while meeting high security and privacy standards. When this will happen: General Availability (DoD): We will begin rolling out early August 2025 and expect to complete by mid-August 2025. How this will affect your organization: After this rollout, you will be able to access the Pro Management Portal in your organization at https://devices.dod.teams.microsoft.us/ The new portal 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. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update your relevant documentation. Please follow the set up process detailed in Enroll a Teams Room device into Pro Management - Microsoft Teams | Microsoft Learn MC1090689 — (Updated) Microsoft Teams: Enhanced peripheral data in Pro Management portal reports for BYOD spaces Microsoft 365 Roadmap ID 493319 Updated June 16, 2025: We have updated the timeline below. Thank you for your patience. We’re adding new peripheral health reporting capabilities to the Pro Management portal, enabling admins to proactively monitor device issues in bring your own device (BYOD) rooms and desks. These reports help identify when peripherals are faulty, missing, moved, or undetectable by a PC—allowing admins to take action before users report problems. Reports for rooms require a Teams Shared Devices license. Desk reporting is currently in public preview. When this will happen: General Availability (Worldwide and GCC): Rollout will begin in early September 2025 (previously early July) and is expected to complete by late September 2025 (previously late July). How this affects your organization: Admins can now use peripheral status data to detect hardware issues in BYOD rooms and desks before they impact users. This proactive monitoring can reduce support tickets and improve meeting space reliability. Reports for rooms require a Teams Shared Devices license. Reports for desks are available in public preview and do not yet require a license. What you can do to prepare:: To ensure accurate peripheral status reporting: Use multiple peripherals in each room or desk setup. The system compares expected device pairings (e.g., if Peripheral A and B are usually connected together, but A is missing, it will be flagged). Simplify connectivity for users by using a single cable solution to connect all peripherals. Ensure rooms and desks are bookable and have associated peripherals—this enables the Teams desktop client to send the necessary telemetry. Peripheral association can be done manually or automatically. Compliance considerations: Does the change alter how existing customer data is processed, stored, or accessed? Maybe (device telemetry is used for reporting) MC1090688 — Teams Town hall screen management privileges in Teams Rooms on Windows Microsoft 365 Roadmap ID 490050 We're introducing enhanced presenter capabilities for Teams Rooms on Windows in Microsoft Teams Town Halls. When a Teams Room is assigned as a co-organizer or presenter, it can now start or end the event, manage what attendees see, and promote attendees to presenters. This update helps ensure a smoother, more organized event experience—especially in large-scale or hybrid meetings. This feature is available with Teams Rooms Pro. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late June 2025 and expect to complete by early July 2025. General Availability (GCC High): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (DoD): We will begin rolling out late July 2025 and expect to complete by early August 2025. How this will affect your organization: Organizers of Teams Town Halls can now assign a Teams Room on Windows as a co-organizer or presenter, enabling it to manage key aspects of the event. This includes controlling the attendee view, starting or ending the session, and promoting attendees to presenters. These capabilities can help streamline event management and reduce the need for manual intervention by remote producers. This feature is available only with Teams Rooms Pro and is on by default once deployed. What you need to do to prepare: Review your current event workflows and determine if Teams Rooms should be included as co-organizers or presenters in Town Halls. Update internal training materials and documentation to reflect the new capabilities. Ensure Teams Rooms Pro licensing is in place for rooms you plan to use with this feature. Learn more: Overview of meetings, webinars, and town halls MC1088732 — Microsoft Teams: Important updates for Android-based Teams devices – Authentication changes coming soon If your organization does not manage one or more certified Microsoft Teams Android devices, you can safely ignore this message. Your organization manages one or more certified Microsoft Teams Android devices, such as Teams Phone devices, Teams Panels, Teams Displays, and Teams Rooms on Android (MTRA). To enhance security capabilities such as Continuous Access Evaluation and IP-based conditional access enforcement, Microsoft is transitioning these devices to modern, secure authentication using Entra ID (AAD) based tokens. These changes will impact how devices authenticate to Teams services. This update provides key dates, required versions, and important cautions—especially for tenants using Teams Displays. How this will affect your organization: Once your devices are updated to the app versions listed below, end users will see no change in their Teams experience, while admins will have enhanced security capabilities such as Continuous Access Evaluation and IP-based conditional access enforcement. These updates are required to maintain connectivity and support secure authentication. Minimum required app versions for modern authentication: Teams Phones: 1449/1.0.94.2025020301 Teams Rooms on Android (MTRA): 1449/1.0.96.2025020302 Teams Panels: 1449/1.0.97.2025020502 Teams Displays: To be released When this will happen: July 31, 2025: Devices on supported app versions will automatically switch to modern authentication. Devices on unsupported app versions will continue to work with legacy authentication. NOTE:Teams Displays will be excluded from this milestone. September 30, 2025: All MTR-A devices on minimum app versions will be leveraging modern authentication. Admins should ensure updating their apps to suggested versions by this date. December 31, 2025: All authenticated traffic must use modern authentication. Ensure all Teams Android devices are updated to the versions listed above as soon as they are available and before December 31, 2025, to avoid service disruption. What you need to do to prepare: Ensure all Teams Android devices are updated to the versions in this message as soon as they are available and before December 31, 2025, to avoid service disruption. MC1088177 — Microsoft Teams Rooms Pro: New AI assistant for admins in the Teams Rooms Pro Management portal Microsoft 365 Roadmap ID 489821 Coming soon for Microsoft Teams Rooms Pro: As an admin, you will be able to save time and effort by using the new AI-powered assistant in the Teams Rooms Pro Management portal that can answer data retrieval questions specific to your organization's inventory. This new chatbot can also answer "how to" product questions related to Teams meetings spaces and management solutions. Important note: This LLM chatbot provides information and cannot perform actions. The chatbot is not part of Microsoft 365 Copilot and a Microsoft 365 Copilot license is not required. A Teams Room Pro license is required to access this AI assistant. General Availability (Worldwide): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: After this rollout, admins with full permissions to the Pro Management Portal can access this AI assistant from the sparkle icon in the top right corner of any Pro Management Portal the top of the screen: Watch this feature in action (21 seconds) This feature 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. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update your relevant documentation. Before rollout, we will update this post with new documentation. MC1077865 — Updated: Microsoft Teams: Introducing the Network Strength Indicator Microsoft 365 Roadmap ID 414513 Updated June 10, 2025: We have updated the timeline below. Thank you for your patience. To improve meeting clarity and reduce confusion caused by connectivity issues, we’re adding a new Network Strength Indicator. When this will happen: Targeted Release: We will begin rolling out late August 2025 and expect to complete by early September 2025. General Availability (Worldwide, GCC): We will begin rolling out early September 2025 and expect to complete by mid-September 2025. How this will affect your organization: This feature will display your current network quality using a simple 3-bar system: Good (3 bars), Poor (2 bars), and Bad (1 bar). When your connection is limited, we’ll suggest actions to help conserve bandwidth and maintain meeting performance. You’ll also be able to see when other participants are experiencing poor or bad network conditions, providing better context for disruptions in the meeting. What you need to do to prepare: You may consider updating your training and documentation as appropriate. MC1069562 — (Updated) Microsoft Teams: Block a user from your organization (GCC High, DoD) Microsoft 365 Roadmap ID 489455 Updated June 25, 2025: We have updated the timeline below. Thank you for your patience. The delete API (removeallaccessforuser API) does not stop a malicious user from resending a Microsoft Teams message to the same victim. To help prevent this, we will roll out a block user feature in the Microsoft Teams admin center that will allow the admin to block the malicious user from sending a new message. We will use a feature similar to the allow/block list in federation identity credentials to block the malicious user from the entire organization. When this will happen: General Availability (GCC High, DoD): We will begin rolling out late July 2025 and expect to complete by late August 2025. How this will affect your organization: After this rollout, admins can set up a list of users who are blocked from collaborating with their organization. If a user is added to the block list, the users in the organization will not be able to have 1:1 and group chats with the blocked users. If chats already exist before a user is added to the block list, the blocked user will be removed from the chat. This feature will be off by default. If you wish to use this feature, go to the Microsoft Teams admin center > Users > External access to turn on this feature and add users to the block list. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. Learn more: The Block external users section of IT Admins - Manage external meetings and chat with people and organizations using Microsoft identities - Microsoft Teams | Microsoft Learn MC1069555 — (Updated) Microsoft Teams: Send messages to attendees in the meeting lobby with Lobby chat Microsoft 365 Roadmap ID 480716 Updated June 12, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams: Meeting organizers will be able to send one-way messages to attendees in the meeting lobby using the Lobby chat. The Lobby chat is intended to optimize the lobby experience for all participants, ensuring that organizers are better equipped to run external meetings and external attendees are well informed about the meeting when it begins. This feature is on by default and admins can choose to disable it in the Teams admin center (TAC). This message applies to Teams on Desktop, Mac, Web iOS and Android will be released shortly When this will happen: Targeted Release: We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late June 2025 and expect to complete by mid-July 2025. How this will affect your organization: Admin controls: After this rollout, the policy for Lobby chat will be on by default in the TAC. Admins can enable or disable Lobby chat with a meeting policy in the TAC. Under Meeting policies > Global (Org-wide default) > Meeting engagement, admins will find a new toggle option for Organizers can chat with lobby participant. When the option is enabled, participants who can't bypass the lobby due to meeting policy will be able to view messages sent by the organizer in a Lobby chat. To enable this policy, Meeting chat in the TAC must be set to On for everyone or On for everyone but anonymous users. Meeting organizer experience: When someone joins the lobby, the meeting organizer will see a new Lobby tab in their Chat experience. The meeting organizer will be able to send one-way messages to attendees in the lobby in the Lobby tab Lobby attendee experience: When the meeting organizer sends a message to the lobby, a new Lobby chat panel will open in the right panel of the pre-join screen and display the message. Lobby attendees cannot reply to these messages 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. For tenants where Meeting chat in the TAC is set to On for everyone or On for everyone but anonymous users, admins should assess the impact of the Lobby chat feature and update meeting policy settings as needed to suit their organization's requirements. MC1066937 — (Updated) New Queues app service plan (Teams Premium) Microsoft 365 Roadmap ID 490056 Updated June 27, 2025: We have updated the content. Thank you for your patience. Microsoft Teams: Your Office 365 subscription is being updated with a new service plan: Queues app for Microsoft Teams. Powered by Teams Phone, the Queues app enables team members to make and receive customer calls without having to leave Teams, with tailored experiences for users and leads that are designed for efficiency in call handling and resolution. How this will affect your organization Once we begin rolling out the new service plan (mid-June 2025), Queues app will be listed as a service plan under the Teams Premium license. This is to prepare for the GCCH and DOD release of the New Voice Applications Settings for Authorized Users for Microsoft Teams (early August 2025). The rollout plan outlining the availability of the New Voice Applications Settings for Authorized Users will be communicated via the Message Center and the roadmap. What you need to do to prepare You may consider updating your training and documentation as appropriate. Admins: Manage voice applications policies in Microsoft Teams - Microsoft Teams | Microsoft Learn MC1056268 — (Updated) Microsoft Teams Premium: Ultra-low latency (ULL) attendee experience for town halls Microsoft 365 Roadmap ID 486535 Updated June 26, 2025: We have updated the timeline below. Thank you for your patience. Before this rollout, Microsoft Teams town hall attendees typically watch the presentation with a 20-30 second delay. After this rollout, with ultra-low latency (ULL), attendees will be able to view and participate in a town hall at a much lower latency than before, ensuring they are in sync with content being shared by presenters and organizers. This feature is available for town hall organizers with a Teams Premium license. This feature will only be available for tenants who use the Microsoft eCDN (Enterprise Content Delivery Network) or who do not have an eCDN provider. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS and Android. When this will happen: Targeted Release: We will begin rolling out mid-August 2025 and expect to complete by late August 2025. General Availability (Worldwide): We will begin rolling out late August 2025 and expect to complete by early-September 2025. General Availability (GCC): We will begin rolling out late August 2025 and expect to complete by early September 2025. How this will affect your organization: This change will be on by default for attendees in town halls scheduled by Teams Premium organizers. What you need to do to prepare: This rollout will happen automatically by the specified dates 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 new documentation. MC1045226 — (Updated) Microsoft Teams: Speaker recognition and attribution in Teams Rooms on Android Microsoft 365 Roadmap ID 480715 Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. You can now use speaker recognition, transcript attribution, and AI capabilities in Teams Rooms on Android. Intelligent speaker functionalities are brought to existing speakers via the cloud. This feature identifies and attributes people in live transcripts, utilizing a unique voice profile for each participant enabling intelligent recaps and maximum value from Microsoft 365 Copilot and Teams Premium in meetings. Users can easily and securely enroll voices via Teams Settings. This feature requires a Teams Rooms Pro license. Users can enroll voices in the Teams Desktop. Learn more: Set up your digital voice profile When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 and expect to complete by late June 2025 (previously late May). How this will affect your organization: With speaker recognition, Teams Rooms on Android can identify speakers during live transcription in shared meeting rooms, ensuring clear and precise voice capture for every participant. This allows you to track who said what during the meeting through intelligent meeting recap and Copilot. What you need to do to prepare: While this functionality is still off by default, if you have already turned it on, be aware that it will enable this feature even for hardware that did not previously support it. To use this new capability, you need to first setup the right policies through PowerShell. For additional information about how to set the right policies, see Manage voice recognition technology controls for an Intelligent Speaker.Participants can set up a voice profile in minutes using the Teams Desktop application. Each person gets a unique voice signature, stored securely in your organization's tenant in the Microsoft Cloud to ensure that every contribution is accurately captured in every meeting, helping you to have a more productive meeting experience. For information about how to enable face and voice enrollment for your organization, see Overview of voice and face enrollment. MC1045219 — (Updated) Microsoft Teams: Room Recommender Microsoft 365 Roadmap ID 482191 Updated June 25, 2025: We have updated the timeline below. Thank you for your patience. With this rollout, if no room is booked for the meeting, an AI-generated room suggestion will be sent in the meeting chat an hour before the meeting start time when two or more attendees are co-located in the same building, making in-person collaboration easier. The room suggestion will consider location of participants, room availability, and capacity to find the best space. You can reserve the suggested room with just one click and update the invite for everyone. The organizer must have a Teams premium license for this experience to occur, which is on Teams mobile on iOS. #MicrosoftPlaces When this will happen: General Availability (Worldwide): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. How this will affect your organization: This will be a default on feature. For a room suggestion to be generated, a meeting must have: Between two to seven attendees with at least two attendees that are co-located Teams meeting link Organizer has Teams premium No room is already booked for the meeting No external attendees Not an all-day event Room suggestions will be generated in buildings where at least two attendees, who haven’t declined the meeting, share the same work location. For instance, if a meeting has four attendees, with two in Building X and two in Building Y, suggestions for both buildings will be sent. Distribution lists are not considered. If a meeting is moved, canceled, or the suggested room becomes unavailable, the card will update dynamically upon clicking ‘Reserve’. 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 team about this change and update any relevant documentation. We recommend making sure that your rooms are properly added to Places directory with a building associated. MC1043271 — (Updated) Microsoft Teams in VDI: User uploaded custom background images for the new VDI solution Microsoft 365 Roadmap ID 410366 Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. With this new feature, users on the new VDI solution for Teams (SlimCore based) can now replace their background entirely with any image they want by uploading it through the "Video effects and Settings" option. This is currently supported for Azure Virtual Desktops, Windows 365 and Citrix, when connecting from a Windows endpoint. 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): We will begin rolling out mid-April 2025 and expect to complete by late April 2025. General Availability (GCCH, DOD): We will begin rolling out early May 2025 and expect to complete by late June 2025 (previously late May). How this will affect your organization: Users need to upload the background via Teams button 'Add New' (although the file can reside on the user's device, and Teams would then rely on Client Drive Mapping / Drive Redirection in that case). The file is subsequently uploaded to the user's OneDrive folder, fetched by SlimCore on the endpoint, and stored in the user's profile on the endpoint (e.g. for Azure Virtual Desktops or Windows 365: AppData\Local\Microsoft\TeamsVDI\avd-tfw-\downloads) What you need to do to prepare: Make sure you are using the new VDI solution based on SlimCore, see here for more details. MC1019312 — (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions Microsoft 365 Roadmap ID 89975 Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. 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 August 2025 and expect to complete by mid-August 2025. General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-August2025 and expect to complete by late August 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 — (Updated) Microsoft Teams: Client health dashboards in Teams admin center Microsoft 365 Roadmap ID 478610 Updated June 4, 2025: We have updated the timeline below. Thank you for your patience. 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 April 2025 (previously late March) and expect to complete by early May 2025 (previously late April). General Availability (GCC, GCC High, DoD): We will begin rolling out late April 2025 and expect to complete by mid-June 2025 (previously late May). 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 — (Updated) Microsoft Teams: Customize the location of notifications in Teams for the web Microsoft 365 Roadmap ID 480720 Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. 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 June 2025 (previously late May). 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) MC1000269 — (Updated) Microsoft Teams: New keyboard shortcut for adding emojis Microsoft 365 Roadmap ID 369345 Updated June 27, 2025: We have updated the timeline below. Thank you for your patience. 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, 😄 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 June 2025 and expect to complete by mid-June 2025. General Availability (Worldwide): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (GCC): We will begin rolling out late July 2025 and expect to complete by early August 2025. General Availability (GCC High): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. General Availability (DoD): We will begin rolling out early September 2025 and expect to complete by mid-September 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) MC994287 — (Updated) Microsoft Teams: Webinars will be generally available (DoD) Microsoft 365 Roadmap ID 475279 Updated June 13, 2025: We have updated the 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-May 2025 and expect to complete by late June 2025 (previously late May). 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 June 12, 2025: We have updated the timeline below. Thank you for your patience. Microsoft is updating its policies regarding the sharing of user location data to enhance privacy, improve data security, and ensure compliance with evolving regulatory standards. To enhance transparency and user control, Teams is introducing a new location consent experience that gives users the choice of when and how Teams can use their location data (specifically SSID & BSSID). Please refer to the public documentation that will be published shortly. 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 mid-April 2025 (previously late March) and expect to complete by mid-April 2025 (previously late March). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late April 2025 (previously mid-April) and expect to complete by late July 2025 (previously late May). How this will affect your organization: All new and existing Teams for Work users within your organization will be prompted to specify if they want to keep location detection on for emergency calls only, or if they consent to allowing location access used for IT Admin Insights or troubleshooting ex via tooling such as Call Quality Dashboard or Network and Locations matching via BSSID for emergency calling location. Important Note - The new Teams location consent flow does not apply to fully managed devices where users are restricted from user granted location access. You can expect current policies to continue working as expected, and users will not be prompted with any of the new location consent dialogs. The new Teams location consent changes will impact the following Teams features: Emergency Calling Location Based Routing Network and Locations matching via BSSID Call Quality Dashboard For all new Teams for Work users, they will first be prompted with an operating system level consent dialog, requesting location permission granting. Existing Teams for Work users who had previously accepted or denied operating system level consent for location will not see this dialog a second time. If location access isallowed, dynamic emergency calling policies will work as configured, and users enabled for Location Based Routing will be able to make and receive PSTN calls. If location access isdisallowed, several Teams Call Quality Dashboard metrics will be impacted, and Network and Location matching via BSSID from dynamic emergency calling policies will not work. Users can still manually add their physical address for emergency calls via the Teams Calls app if an admin has enabled ExternalLookupMode for their users. Immediately after consenting to allow location access at the operating system level (or for those who had previously consented to location access), both new and existing Teams for Work users will be presented with a new Teams app level location permission dialog. Users must choose between "Allow all," which grants Teams full location access used for emergency calls and for IT Admin insights and troubleshooting, or "Keep emergency only," which restricts location usage to emergency calling purposes. It is important to note only end users who are configured for a dynamic emergency calling policy will see this version of the dialog. Users without ExternalLookUpMode enabled will see a slightly different version of this in-app consent dialog that excludes emergency calling. Users can modify their operating system or app level location detection preferences at any time via Teams settings under Privacy > Location. On fully managed devices, these settings will be ON by default and can only be disabled via the OS level location setting. What you need to do to prepare: Please educate your users on these selections and what works best for your tenant. If you regularly use the Call Quality Dashboard or leverage Network and Location matching via BSSID, you may want to recommend that users allow location access for those options, otherwise a user’s location data will no longer flow through to these services. For emergency calling, you can communicate these changes 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 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) WiFi Access Location changes – 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. Please notify your users and admins about this change and update any relevant documentation. MC966633 — (Updated) Microsoft Teams: Meeting recap can be shared as a link Microsoft 365 Roadmap ID 471430 Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Coming soon to Microsoft Teams: Meeting participants will be able to share a link to the Meeting recap from the meeting thumbnail in chat and the Recap tab, making it easier to reference and share Meeting recap insights with others. Meeting participants can share the meeting recap link with anyone in their organization. Users who don't have access to the recording or transcript must request access before they can access the Meeting recap. This message applies to Teams for Windows desktop and Teams for Mac desktop. 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): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (GCC High): We will begin rolling out late March 2025 and expect to complete late June 2025 (previously late May). 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. You may want to notify your users about this change and update any relevant documentation. Learn more: Meeting recap in Microsoft Teams - Microsoft Support (will be updated before rollout) MC956699 — (Updated) Microsoft Teams: Forward messages with app cards Microsoft 365 Roadmap ID 469506 Updated June 13, 2025: We have updated the 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 late June 2025 (previously late May). 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 June 23, 2025: We have updated the timeline below. Thank you for your patience. 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): Meeting pane pop-out for Notes, Chat, and Copilot panes will start rolling out in late June 2025 and complete by early July 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. MC948994 — (Updated) Microsoft Teams: Collaborative Notes support for GCC High and DoD environments Microsoft 365 Roadmap ID 418119 Updated June 4, 2025: We have updated the timeline below. Thank you for your patience. Teams Collaborative Notes (powered by Loop), and Loop components in chat and channels, is now available for Microsoft 365 GCC High and DoD environments across desktop and web experiences. Users can create components in meetings to collaborate on their meeting agenda, notes, and action items, create components in compose, share with others and edit inline in Chats and Channels to collaborate synchronously on ideas without leaving the context of Teams. No matter where people are editing, the component will always show the latest updates. You can also share Loop components between chats, channels, and meetings as well as the rest of M365 where Loop is supported. When this will happen: General Availability (GCC High): We will begin rolling out in early June 2025 and expect to complete by late June 2025. General Availability (DoD): We will begin rolling out in early August 2025 and expect to complete by late August 2025. 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 Loop Components will generate a Company Shareable Link (CSL), unless you have set People Specific Link (PSL) as the default. If PSL is the default, only specific users who were sent the original component invite will be able to access the component. Users who were forwarded the meeting or nudged into a meeting will need to request access to the components. Known issues: Users external to an organization will not be able to view or edit the Loop component. Loop meeting notes will generate a Company Shareable Link (CSL) regardless of your organization’s default sharing link type if you use the Teams New Calendar. You can manage this in Teams Calendar and Loop components in chats and channels by following the instructions here. You can manage this in Teams New Calendar by following the instructions here. Known limitations: Collaborative Notes are currently supported for scheduled meetings and channel meetings and are not available for instant meetings or Teams calls. MC939927 — (Updated) Microsoft Teams Premium: Decorate your background Microsoft 365 Roadmap ID 419811 Updated June 11, 2025: We have updated the 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 mid-September 2025 and expect to complete rollout by late September 2025. General Availability (GCC High): We will begin rolling out in late September 2025 and expect to complete rollout by early October 2025. 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. MC898391 — (Updated) Microsoft Teams: Performance improvements for meetings in Edge web browser for guests Microsoft 365 Roadmap ID 401117 Updated June 13, 2025: We have updated the 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 June 2025 (previously late May). 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 June 13, 2025: We have updated the 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 June 2025 (previously late May). 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. MC718553 — (Updated) Microsoft Teams: Change background while recording on phone Microsoft 365 Roadmap ID 380852 Updated June 13, 2025: We have updated the 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 June 2025 (previously late May.) 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. Purview MC1105009 — Microsoft Purview compliance portal: eDiscovery - Review set query report Microsoft 365 Roadmap ID 171751 and 384871 We’re introducing a new capability in the Microsoft Purview portal’s eDiscovery (Premium) experience that allows you to generate and download hit-by-term query reports directly from a review set. This enhancement helps you quickly assess keyword performance and query effectiveness using KQL. When this will happen: General Availability (Worldwide, GCC, GCCH, DoD): Rollout will begin in early July 2025 and is expected to complete by the end of July 2025. How this affects your organization: This update does not change your current eDiscovery workflows. However, when using the new eDiscovery experience in Microsoft Purview, you’ll now see a Query report option within each review set. This feature enables you to: Paste in a KQL-based compound query to generate a hit-by-term report. View keyword performance metrics such as hit count, hit percentage, and data volume. Download the report as a .csv file. Quickly review items with hits in a single view. Note: This feature is only available in the new eDiscovery (Premium) experience and is not supported in the classic experience. What you can do to prepare:: Review your current eDiscovery workflows and determine if this reporting capability can enhance your review process. Update internal documentation or training materials as needed. Compliance considerations: Alters admin monitoring/reporting for compliance: Yes - The new report provides enhanced visibility into keyword/query performance, supporting compliance monitoring. MC1105008 — Microsoft Purview compliance portal: Modern eDiscovery additional enhancements Microsoft 365 Roadmap ID 494160 We’re introducing several enhancements to the modernized eDiscovery interface in Microsoft Purview to streamline workflows, improve usability, and provide greater administrative control. These updates include: Ability to delete searches Ability to delete exports created from searches Auto-population of the custodian field in review sets and exports Advanced indexing improvements, including indexing all Exchange items with attachments in scope A new tenant-level premium feature toggle to control eDiscovery case license toggle value during case creation. A new analytics process report for deeper insights into review set analytics (e.g., deduplication) Expanded search condition builder with support for logical operators (AND, OR, NEAR) in the keywords field Export packages to include user input export name for easier association with the export process Bulk import of data sources These updates are designed to enhance the eDiscovery experience by offering more flexible, powerful tools and reducing administrative overhead. When this will happen: General Availability (Worldwide/GCC/GCCH/DoD): Rollout will begin in late June 2025 and is expected to complete by the end of August 2025. How this will affect your organization: The tenant-level premium toggle sets the default value for newly created cases, giving admins centralized control over premium settings without affecting existing cases. The ability to delete searches and direct exports introduces a change in lifecycle management, which may impact audit trails or collaboration workflows. Logical operators in the search condition builder will enhance query precision but may require updates to search strategies. Advanced indexing improvements will improve content discoverability, especially in complex or high-volume cases. What you can do to prepare:: Review and update internal documentation, training materials, and workflows to reflect these changes. Ensure your teams are aware of the new search and direct export deletion capability and its implications for audit and collaboration. Update search guidance to incorporate logical operators for more effective query construction. Evaluate how the new analytics report and indexing enhancements can support your review and prioritization processes. Compliance considerations: Alters how existing customer data is processed, stored, or accessed: Yes - Advanced indexing improvement may affect how data is processed and accessed within eDiscovery. Modifies or disables Purview capabilities (eDiscovery, audit logging, etc.): Yes - The ability to delete searches and direct exports directly impact eDiscovery workflows and may affect audit logging. Alters how admins monitor/report on compliance activities: Yes - The new tenant level license toggle affects how admin control the use of eDiscovery premium features in their eDiscovery workflow. Modifies how users access/export/delete/correct personal data (GDPR DSR): Maybe - The ability to delete searches and direct exports could affect how personal data is retained or accessed, depending on organizational policies and configurations. MC1102779 — Microsoft Purview | Data Loss Prevention: New RBAC role for downloading Endpoint evidence (GCC, GCC High, DoD) Microsoft 365 Roadmap ID 495831 Coming soon to Microsoft Purview | Data Loss Prevention (DLP): We're introducing a new role-based access control (RBAC) role called Data Classification Content Download. When evidence collection is turned on from Endpoint DLP settings, this role lets admins download endpoint-related evidence files from activity explorer and DLP alerts in the Purview portal and Microsoft Defender XDR portal. When this will happen: General Availability (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: By default, the new role be included in the following built-in role groups: Data Security Management Information Protection Information Protection Investigators Users in these groups will be able to download Endpoint DLP evidence. To view evidence (without downloading), the existing Data Classification Content Viewer role remains sufficient. After this rollout, DLP investigators assigned to any role group (custom or default) without the role Data Classification Content Download role will be unable to download the endpoint DLP evidence and will encounter the error message, “You need the role Data Classification Content Download to download the evidence": After rollout, users in custom or other default role groups will not be able to download Endpoint DLP evidence unless the new role is explicitly assigned. This change does not affect the ability to preview evidence. For more information on the roles and role groups in Microsoft Purview refer to Roles and role groups in Microsoft Defender for Office 365 and Microsoft Purview - Microsoft Defender for Office 365 | Microsoft Learn If users encounter the error You need the role Data Classification Content Download to download the evidence, take the following steps: Existing user in built-in role group: Add the new role using to the built-in role group using in the section called Add users or groups to a Microsoft Purview built-in role groupin Permissions in the Microsoft Purview portal | Microsoft Learn Existing user in custom role group:Add the new role to the built-in role group using the section called Update a custom Microsoft Purview role group in Permissions in the Microsoft Purview portal | Microsoft Learn New user: Add the user to a role group that includes the new role or create one using the section called Create a Microsoft Purview role groupin Permissions in the Microsoft Purview portal | Microsoft Learn What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins and/or users about this change and update internal documentation. MC1102776 — Microsoft Purview | Insider Risk Management: New alerts for email exfiltration to personal accounts Microsoft 365 Roadmap ID 495001 Coming soon for Microsoft Purview | Insider Risk Management: Two new indicators will help detect potential data exfiltration via email. These indicators enhance visibility into risky user behavior and support stronger data protection policies. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. How this will affect your organization: After this rollout, two new email indicators will be available in Insider Risk Management: Sending email with attachments to free public domains: Detects when users send business-sensitive data to domains like Gmail, Yahoo, etc. Sending email with attachments to self: Detects when users email sensitive data to their own personal accounts. These indicators are off by default and must be enabled by admins in the Insider Risk Management settings. Once enabled, they can be used in existing or new policies, including the data leaks or data theft templates. This feature supports proactive detection of insider risks and helps organizations strengthen their data loss prevention strategies. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins and/or users about this change and update internal documentation. Enable the new indicators in the Microsoft Purview compliance portal. Learn more: Configure policy indicators in insider risk management | Microsoft Learn 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. MC1077858 — (Updated) Teams Meeting Audit Events in GCC Microsoft 365 Roadmap ID 491010 Updated June 12, 2025: We have updated the timeline below. Thank you for your patience. We're expanding auditing capabilities in Microsoft Teams for GCC customers. Teams Audit Events for Meetings—including MeetingDetail and MeetingParticipantDetail—will soon be available in Microsoft Purview. This enhancement provides administrators with deeper visibility into meeting activity, supporting ompliance, investigations, and operational oversight. When this will happen: General Availability (GCC): Rollout will begin in late June 2025 (previously early June) and is expected to complete by late July 2025 (previously late June). How this will affect your organization: With this update, Teams meeting activities in GCC tenants will be audit logged in the Microsoft Purview portal. MeetingDetaillogs include meeting start/end times, subject, and organizer information. MeetingParticipantDetaillogs include participant join/leave times, roles, and status changes. These logs enhance your ability to monitor meeting usage and investigate user activity. What you need to do to prepare: No action is required if Audit logging is already enabled in your tenant. Admins can access and analyze these logs in the Microsoft Purview portal using search, filter, and export capabilities. MC1059679 — (Updated) Microsoft Purview | Insider Risk Management: Policy tuning analysis for priority content only policies Microsoft 365 Roadmap ID 378409 Updated June 26, 2025: We have updated the content. Thank you for your patience. In Microsoft Purview | Insider Risk Management (IRM), policy tuning analysis provides admins with a real-time prediction of the number of users in a tenant that could potentially match a given set of policy conditions. After this rollout, policy tuning analysis will support insider risk policies that are scoped for priority content. MC786326 (about the preview for this feature that started in May 2024). When this will happen: General Availability (WW, GCC, GCC High, DoD): We will begin rolling out late June 2025 (previously mid-June) and expect to complete by late July 2025 (previously mid-July). How this will affect your organization: After this rollout, admins can use real-time analytics for policies scoped for priority content to help predict the number of users that could potentially match a given set of policy conditions. This feature enables admins to quickly adjust the selection of indicators and thresholds of activity occurrence so they can efficiently translate their insider risk strategies into pragmatic controls and keep from having too few or too many alerts. In IRM, Navigate to Settings > Insider Risk Management > Analytics,turn on Analytics, and then select Save. Create/edit a policy scoped to all users in the organization. When you get to Content to prioritizein the policy wizard, select the priority content types you want to prioritize. Select the items for each priority content type as applicable. On the scoring page, select Get alerts only for activity that includes priority content. Configure the rest of the policy as applicable and save it. 1-2 days after the policy is saved, edit the policy again and navigate to the indicator thresholds page where insights on user activity containing the scoped priority content for each indicator will be visible under Choose your own thresholds. 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. This change will be available by default for admins to configure. To use this feature, admins will need to enable Analytics in Insider risk management > Settings. After Analytics is enabled and insights are populated, admins will be able to see real-time predictions in policies scoped to all users/groups and scored only for priority content. 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 MC1036579 — (Update) Microsoft Purview | Data Loss Prevention: A new Diagnostics experience in the new portal Microsoft 365 Roadmap ID 469504 Updated June 25, 2025: Following further evaluation, we will be rolling back this feature. We appreciate your continued patience. Coming soon for Microsoft Purview : Admins will be able to view and manage Diagnostics in the new Purview portal. The new diagnostics will help users check the configuration. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-August 2025 (previously early May) and expect to complete by late August 2025 (previously mid-June). How this will affect your organization: Admins can find the new experience at: Purview portal> Information Protection > Diagnostics Purview portal> Data Loss Prevention > Diagnostics The PowerShell cmdlets will continue to be available after this rollout. This new experience will be on 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. 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. MC1024388 — (Updated) Microsoft Purview compliance portal: Modern eDiscovery enhancements Microsoft 365 Roadmap ID 482558 Updated June 4, 2025: We have updated the timeline below. Thank you for your patience. We are excited to announce several enhancements to the recently launched modernized eDiscovery experience. These updates include: Case Level Data Source View: Users can now access the case level data source view, which allows them to add data sources to the current case. These sources can be utilized in any searches or holds within the case. Enhanced Search and Hold Capabilities: Users will have the ability to duplicate a search, create a search from an existing hold, or create a hold from an existing search within the current case. Retry Failed Locations: The search statistics view now includes the option to retry failed locations, providing a more comprehensive search estimate. Detailed Process Reports: We are adding information related to compliance boundaries, case/export/search names, and decryption settings into the relevant process report CSVs. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by late June 2025 (previously late May). How this will affect your organization: eDiscovery users will start to see the relevant enhancements in the product, so internal documentation updates may be needed. What you need to do to prepare: Evaluate how this feature will impact your organization’s eDiscovery process and, if needed, modify your internal documents accordingly. For more information, see Learn about eDiscovery solutions | Microsoft Learn. MC973511 — (Updated) Microsoft Purview | Data Lifecycle Management: Separate retention policies for Copilot and AI apps Microsoft 365 Roadmap ID 470025 Updated June 16, 2025: We have updated the 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: Public preview: We will begin rolling out late May 2025 (previously late April) and expect to complete by early June 2025 (previously early May). General Availability (Worldwide): We will begin rolling out mid-September 2025 (previously late June) and expect to complete by late September 2025 (previously early July). 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. MC961761 — (Updated) Microsoft Purview | Insider Risk Management: IRM alerts in Microsoft Defender XDR Microsoft 365 Roadmap ID 422730 Updated July 1, 2025: We have updated the 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 August 2025 (previously late June) and expect to complete by mid-September 2025 (previously mid-July). 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. Defender for Office 365 MC1105005 — Defender for Office 365 Overview dashboard We’re introducing a new Overview dashboard designed to help customers better understand how our product protects their organizational environment and digital assets. When this will happen: Global rollout will begin in early July 2025 and is expected to complete by late July 2025. How this will affect your organization: This new dashboard provides a centralized view of how effectively our product is securing your environment. It highlights: Key protection metrics and insights Opportunities to enhance security posture Comparative insights that demonstrate our product’s strengths relative to non-Microsoft security solutions Figure one: Efficacy, Threat detections, and Optimization Figure two: Risky allows Figure three: Compare solutions Figure four: Insights This feature will be available by default and does not require any configuration. What you can do to prepare: No action is required, but we recommend that admins: Review the dashboard once available to familiarize themselves with the insights Update internal training or documentation as needed This message is for awareness only. MC1088729 — Microsoft Defender for Office 365: Two new data tables in Advanced hunting (preview) Coming soon for Microsoft Defender for Office 365: We are excited to announce the new CampaignInfo and FileMaliciousContentInfo data tables in Advanced hunting under Email & collaboration schema. When this will happen: Public Preview: We will begin rolling out early June 2025 and expect to complete by late June 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early July 2025 and expect to complete by late July 2025. How this will affect your organization: The new tables will be available by default. SOC teams will be able to see two new data tables in Defender > Advanced hunting > Email & collaboration schema. CampaignInfo The CampaignInfo table in the Advanced hunting schema contains information about email campaigns identified by Defender for Office 365. The table will have this schema to help the security teams to investigate threats targeting their users and organization: FileMaliciousContentInfo The FileMaliciousContentInfo table in the Advanced hunting schema contains information about files that were identified as malicious by Defender for Office 365 in Microsoft SharePoint Online, Microsoft OneDrive, and Microsoft Teams. The table will have this schema to help the security teams to investigate threats targeting their users and organization: Here are a few sample queries to get you started: //Emails sent as part of phishing campaigns CampaignInfo | where Timestamp > ago(7d) | where CampaignType has "Phish" | project NetworkMessageId, RecipientEmailAddress, CampaignName, CampaignId, CampaignType | join (EmailEvents | where Timestamp > ago(7d)) on NetworkMessageId, RecipientEmailAddress | project Timestamp, NetworkMessageId, Subject, SenderMailFromAddress, RecipientEmailAddress, LatestDeliveryLocation, LatestDeliveryAction, CampaignId, CampaignName, CampaignType //Files identified as Malware modified in last 1 day FileMaliciousContentInfo | where ThreatTypes == "Malware" | where LastModifiedTime > ago(1d) What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update your relevant documentation. After the Public Preview rollout, we will update this post with new documentation. MC1080684 — Microsoft Defender for Office 365: Introducing the new Take action wizard for Threat Explorer (GCC, GCC High, DoD) Microsoft 365 Roadmap ID 488094 Updated June 4, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Defender for Office 365: We will introduce a new Take action wizard to help security operations team members perform multiple response actions at once from Threat Explorer. Many security analyst teams use Explorer, Summary panel and Email entity to execute bulk email remediation actions. This new experience will enable more effective, smooth, and efficient remediation of threats. When this will happen: General Availability (GCC): We will begin rolling out starting early June 2025 and expect to complete by early July 2025. General Availability (GCC High): We will begin rolling out early June 2025 and expect to complete by mid-July 2025. General Availability (DoD): We will begin rolling out mid-June 2025 and expect to complete late July 2025. How this will affect your organization: After the rollout of the new Take action wizard, you can perform multiple actions such as purging emails, inline submissions, triggering investigations, and Tenant Allow/Block List actions on up to 100 messages. Also, you will be able to initiate tenant-level actions to block URLs or file directly from Threat Explorer. You can also use the new wizard to perform bulk email remediation for more than 100 messages, but only one action can be executed at a time, such as triggering an email purge. Also, actions like tenant level block and submissions are not permitted for selections over 100. NOTE: Some actions will not be available in the wizard based on the current location of the message. If there is a conflict, the new experience provides more options, including the ability to turn choices on/off as desired to take proper action. Enhancements to the Email entity page and the Email summary panel: Step 1: Sign into the Microsoft 365 Defender portal. Step 2: Go to Threat Explorer > Email & Collaborations and select the emails that require action. Step 3: Select the Take action wizard. (Before this rollout, the next step was to choose from the Message actions menu. We removed this menu.) Step 4: This will open a new panel. Some actions will be grayed out depending on the latest delivery location of the message. Step 5: Tenant Allow/Block List actions are under Submissions, so when you select I’ve confirmed as threat, you will see a new Tenant Allow/Block List panel where you can choose multiple entities to block. Step 6: Choose the target entities. Step 7: Review the actions you have chosen and then submit. Step 8: You can access email purge remediation actions in the action center. What you need to do to prepare: A Search and Purge role is required to initiate email purge actions from the Email entity page. To initiate Tenant Allow/Block List actions from Explorer and summary panel and Email entity, please assign the necessary Exchange Online permission role as explained in Allow or block files using the Tenant Allow/Block List - Microsoft Defender for Office 365 | Microsoft Learn Learn more about the Search and Purge role: Microsoft Defender for Office 365 permissions in the Microsoft Defender portal - Microsoft Defender for Office 365 | Microsoft Learn This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins or users about this change and update any relevant documentation. MC1048617 — (Updated) Introducing new Advanced Hunting Tables to hunt on Teams messages and URLs Microsoft 365 Roadmap ID 487411 Updated June 5, 2025: We have updated the timeline below. Thank you for your patience. We are happy to introduce three new Advaned Hunting tables designed to facilitate hunting of Teams messages containing URLs within your organization. The MessageEvents table enabled hunting across Teams messages containing URLs within your tenant. This includes both, known malicious messages blocked immediately after delivery and messages with no malicious content. Each message is uniquely identified by the TeamsMessageId, which can be utilized to establish joins across tables. As there is only a single copy of each message, even in instances of delivery to multiple recipients, only one instance of the message will be accessible for viewing in Advanced Hunting. The MessagePostDeliveryEvents table provides the capability to analyze Teams messages containing URLs within your tenant, that have been identified as malicious after message delivery. If you have Zero-hour Auto Purge (ZAP) enabled for Teams, messages blocked post-delivery will be observable within this table. Each message is uniquely identified by the TeamsMessageId. The MessageURLInfo table support the ability to hunt across URLs embedded within Teams messages in your organization. The tables can be found under the Email & Collaboration in Advanced Hunting. When this will happen: Public Preview (Worldwide): We will begin rolling out late April 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out in early July 2025 (previously late May) and expect to complete by mid-August 2025 (previously mid-June). How this will affect your organization: You will now have the ability to hunt on Teams messages from Advanced Hunting. What you need to do to prepare: No additional action will be needed to prepare for this rollout. The new hunting tables will be available in your tenant and can be viewed with the right security permissions. More information on these new tables can be found here: MessageEvents: MessageEvents table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn MessagePostDeliveryEvents: MessagePostDeliveryEvents table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn MessageURLInfo: MessageUrlInfo table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn MC918563 — Microsoft Exchange Online Protection (Defender for Office 365): Monitor action in Safe attachments policy will retire Updated June 4, 2025: We have updated the timeline below. Thank you for your patience. We will retire the Monitor action in the Safe attachments policy in Microsoft Exchange Online Protection (Microsoft Defender for Office 365) starting early July 2025 (previously late March) and ending by late August 2025 (previously late May). How this will affect your organization: A Safe attachments policy provides an additional layer of protection against malicious content (attachments) in emails by analyzing attachment content and behavior in a sandbox environment. This policy provides four actions: Off, Monitor, Block, and Dynamic delivery. We made the Monitor action available for customers who wanted a Safe attachments policy to process attachments, deliver the emails (without blocking malicious attachments), and track what happened with attachments identified as malicious. Customers used reports to see detections from the Monitor action in the policy. As part of this retirement, if your organization has Safe attachments policies set to the Monitor action, we will automatically change the action in from Monitor to Block. We will not change the policy's recipients, status, or priority. After retirement, the Monitor option will not be available in the Safe Attachments policy page in the Defender security portal or the corresponding Microsoft PowerShell cmdlet. Before retirement, you can find the Monitor action in Defender > Email & collaboration > Policies & rules > Threat policies > Safe attachments > choose a policy or create a new policy > Edit settings (or Settings if creating a new policy). We will also retire Redirect messages with detected attachments, because this option only supports the Monitor action). After the retirement, the only actions in the Safe attachments policy will be Off, Block, and Dynamic delivery. What you need to do to prepare: Before the retirement, review your Safe attachments policies and take appropriate action if your organization has Safe attachments policies set to the Monitor action. We recommend changing the action from Monitor to Block. Alternatively, if you still need to run Safe attachment policy in audit mode, we recommend using Evaluation mode. Learn more about Evaluation mode. You can also review detections by Evaluation mode policies using the Threat Protection Status report. Learn more: The Safe Attachment policy settings section of Safe Attachments - Microsoft Defender for Office 365 | Microsoft Learn Outlook MC1104315 — New Microsoft Outlook for Windows: Drag and drop files between accounts as attachments Microsoft 365 Roadmap ID 493289 We're introducing a new drag-and-drop capability in the new Microsoft Outlook for Windows. This feature will users to drag emails and files from one personal or enterprise account and drop them into another personal or enterprise account as attachments—streamlining cross-account workflows and improving productivity. When this will happen: Targeted Release: We will begin rolling out mid-July 2025 and expect to complete by mid-August 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-September 2025 and expect to complete by mid-October 2025. How this will affect your organization: Before this rollout, users are not able to drag emails and files from one account to another. After this rollout, users from organizations with the ItemsToOtherAccountsEnabled parameter set to TRUE in the OWAMailboxPolicy will be able to: Drag and drop emails and files from one mailbox into a draft in another mailbox as attachments. Attach content from Shared Mailboxes or Shared Folders into another mailbox. To enhance security, users will see a confirmation prompt before completing the drag-and-drop action: This confirmation does not appear when attaching files from a Shared Mailbox. This feature respects your existing OWAMailboxPolicy settings and does not change any defaults. What you need to do to prepare: This rollout will happen automatically by the specified dates. Review your current OWAMailboxPolicy settings, particularly the ItemsToOtherAccountsEnabled parameter, to determine if you would like to enable or disable this feature after roll out occurs. No change to your existing ItemsToOtherAccountsEnabled configuration will occur with this rollout. You may want to notify your admins and/or users about this change and update internal documentation. Learn more about the ItemsToOtherAccountsEnabled parameter in Set-OwaMailboxPolicy (ExchangePowerShell) | Microsoft Learn #newoutlookforwindows MC1104309 — New Microsoft Outlook for Windows: Export from mailbox to PST Coming soon for new Microsoft Outlook for Windows: Users will be able to export an entire mailbox (emails, calendars, and contacts) or a specific mailbox folder to a .pst file. This feature is associated with Microsoft 365 Roadmap ID 485737(Worldwide audience) and Microsoft 365 Roadmap ID 485738 (GCC audience). Users will be able to schedule an export of an entire mailbox (emails, calendars, and contacts) or a specific mailbox folder to a .pst file. This feature is associated with Microsoft 365 Roadmap ID 485743(Worldwide audience) and Microsoft 365 Roadmap ID 485744 (GCC audience). When this will happen: Ability to export an entire mailbox (Roadmap ID 485737 for Worldwide and Microsoft 365 Roadmap ID 485738 for GCC): Targeted Release: Available now. General Availability (Worldwide): We will begin rolling out mid-July 2025 and expect to complete by mid-August 2025. General Availability (GCC): We will begin rolling out late August 2025 and expect to complete by early September 2025. Ability to schedule an export of an entire mailbox (Roadmap ID 485743 for Worldwide and Microsoft 365 Roadmap ID 485744 for GCC): Targeted Release: We will begin rolling out early July 2025 and expect to complete by late July 2025. General Availability (Worldwide): We will begin rolling out early August 2025 and expect to complete by early September 2025. General Availability (GCC): We will begin rolling out late September 2025 and expect to complete by early October 2025. How this will affect your organization: Before this rollout, Outlook Data File (.pst) support is enabled by default in new Outlook for Windows, and this default state will persist after the rollout. If you want to block or limit Outlook Data File support for your organization, set the OutlookDataFile mailbox policy. Learn more: Set-OwaMailboxPolicy (ExchangePowerShell) | Microsoft Learn NOTE: The group policy used to control Outlook Data File (.pst) in classic Microsoft Outlook for Windows desktop is not the correct mechanism for controlling Outlook Data Files in new Outlook for Windows. You must set the OutlookDataFile mailbox policy to control this file type in new Outlook for Windows. What you need to do to prepare: This rollout will happen automatically by the specified date. Review the OutlookDataFile mailbox policy to ensure it is set to align with your organization’s desired behavior. You may also want to notify your users about this change and update any relevant documentation. Learn more: Open and find items in an Outlook Data File (.pst) - Microsoft Support (will be updated before rollout) #newoutlookforwindows #pstfilesupport MC1098932 — Microsoft Outlook for Mac desktop: Retiring the admin preference to switch to legacy Outlook Beginning mid-August 2025, the New Outlook for Mac will become the default experience for users in the Current Channel (version 16.100 and later). As part of this change, the admin preference key EnableNewOutlook—which previously allowed control over the default toggle state—will be retired. Users will no longer be able to switch back to Legacy Outlook starting with version 16.102 in mid-October 2025. This update reflects our commitment to delivering a modern, performant, and reliable Outlook experience. When this will happen: Legacy Outlook toggle admin perference i.e. EnableNewOutlook retired: Mid-August 2025 (version 16.100 and later) Users can no longer switch to legacy Outlook: Mid-October (version 16.102 and later) How this affects your organization: The New Outlook for Mac will be the default experience for all users in the Current Channel. The EnableNewOutlook admin configuration key will no longer be honored in configuration profiles. The New Outlook is built on Microsoft’s modern sync technology and offers: Improved performance and reliability Enhanced support for modern collaboration features A consistent cross-platform experience It also supports key enterprise capabilities including: On-premises support Online Archive Shared Mailboxes and Calendars Delegation Some features not yet available in New Outlook include: AppleScript Import/Export Public Folders For the latest feature availability, please refer to the Microsoft 365 Roadmap. What you can do to prepare:: Notify users that New Outlook will become the default. Update training materials and internal documentation to reflect the new experience. For questions or support, users can go to Help > Contact Support in Outlook for Mac. For tenant-level questions or to tailor communications, please use your Message Center submission workflow or contact your Microsoft account team. More information: End of support for legacy Outlook for Mac MC1085132 — (Updated) Microsoft Outlook for Android: Users can apply categories to emails Microsoft 365 Roadmap ID 493945 Updated June 26, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Outlook for Android: Users will be able to assign categories to emails and remove categories they have previously assigned to their emails. They will also be able to view categories in the message list and reading pane. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late June 2025 (previously mid-June) and expect to complete by late July 2025 (previously mid-July). With this feature, users will be able to add or remove categories on emails using conversation actions in the reading pane, using multiselect through long press in the message list, and as a new swipe action. Users will also be able to filter the message list by category. Finally, users will be able to see assigned categories on their emails in both the message list and the reading pane. This new feature will be available by default for users to apply. 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 your documentation to prepare your help desk. MC1041465 — (Updated) New Microsoft Outlook for Windows and Outlook on the web: Optimized hover actions in the message list Microsoft 365 Roadmap ID 429868 Updated July 1, 2025: We have updated the timeline below. Thank you for your patience. In new Outlook for Windows and Outlook on the web, the hover actions in the message list will be moved to the Sender/From column to be more space-efficient and minimize unnecessary mouse travel for users with their Reading Pane set to Hide or Bottom. The large width occupied by the DateTime Received column will thus be reduced. For all users, a one-time shortcut to change/set your hover actions will be provided. After the changes to the hover actions, the first action will be replaced by a quick button (gear button) to change/set your hover actions. After that button has been triggered once, it will disappear, and your hover action settings will kick in fully. When this will happen: Targeted Release: We will begin rolling out mid-July 2025 (previously late June) and expect to complete by mid-August 2025 (previously late July). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-September 2025 (previously late July) and expect to complete by late September 2025 (previously early August). How this will affect your organization: For new Outlook for Windows and Outlook on the web, hover actions in the message list will be moved to the Sender/From column to reduce the large width occupied by the DateTime Received column. 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. #newoutlookforwindows MC1041456 — (Updated) New Microsoft Outlook and Outlook for the web: New setting to enable two-click view for encrypted emails Microsoft 365 Roadmap ID 483883 Updated June 11, 2025: We have updated the content. Thank you for your patience. New Outlook for Windows desktop, Outlook for the web, Outlook iOS and Outlook Android will soon support a two-click view for encrypted emails, which requires user confirmation before allowing access to encrypted emails. As an admin, you can enable the two-click feature for your users. When this will happen: General Availability (Worldwide): We will begin rolling out early 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 late May 2025. General Availability (Worldwide, GCC): For Android and iOS, we will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: With this two-click feature enabled, users will be required to select View message for every encrypted email, and then the email will render. This feature ensures that users deliberately access encrypted email content, reducing the risk of accidental exposure, especially in unsecured environments like public spaces or during screen sharing. Admins can find the TwoClickMailPreviewEnabled setting in the Microsoft Azure directory. This setting is a Boolean type with default = 0, which means the experience is disabled by default. To enable the feature for all users in your tenant, set value = 1. Alternatively, you can access and set the value for this setting using the Microsoft PowerShell cmdlet Set-OrganizationConfiguration in the Microsoft Exchange Online PowerShell. Learn more: Exchange Online PowerShell | Microsoft Learn By default, the two-click setting is off. What you need to do to prepare: No action is required from admins unless you want to enable this feature. This rollout will happen automatically by the specified dates 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 plan to enable this feature. #newoutlookforwindows MC1022526 — (Updated) Microsoft Outlook on the web: Optional connected experiences privacy setting Microsoft 365 Roadmap ID 467248 Updated June 4, 2025: We have updated the timeline below. Thank you for your patience. 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 June 2025 (previously late May). 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) MC917748 — (Updated) Microsoft Teams and Microsoft Outlook: Name pronunciation on the profile card Microsoft 365 Roadmap ID 420329 Updated June 24, 2025: The phased roll out to GA began last week at 10%. If enabled on admin center, the name pronunciation feature should show on Teams and Outlook web, Teams Desktop and New Outlook. Roll out to 100% Production is expected by the end of June. We will be starting roll out of the feature to Production on Tuesday 13th May 2025. The roll out should take a week and a half to complete to 100%. Admins who have toggled the feature ON should expect the feature to be available on the Profile card for users to record. " Updated April 29, 2025: We have now shipped the admin control, the name pronunciation feature is OFF by default so admins will need to toggle it ON. The instructions in this support document explain how to turn the feature on. Important! Starting from April 29, 2025, if you haven't turned the name pronunciation feature ON, any existing recordings on profile cards will be deleted. Your users will need to re-record their name pronunciation. The admin toggle for Name Pronunciation is rolling out to Production starting this week. Admins will be required to configure in the admin center to avoid loss of data. Instructions to configure are in this support article. Please expect the admin toggle in the admin center starting the week of April 14th through April 18th, 2025. We will be shipping to preview without the admin toggle however an admin toggle will be available before general availability. If there are concerns or your organisation wants to opt out, please raise an incident to address this. Coming soon to Microsoft Outlook and Microsoft Teams: A name pronunciation feature on the profile card in Microsoft Teams and Microsoft Outlook. This new feature helps promote diversity by giving working colleagues relevant information about each other. Names are a crucial part of a person’s identity. The incorrect pronunciation of a person’s name can lead to anxiety and offense in some cases. Correctly pronouncing a person’s name helps to create an inclusive environment. Pronunciation data is stored in each user's mailbox until the user deletes the recording. Learn more: Data Residency for Exchange Online - Microsoft 365 Enterprise | Microsoft Learn This message applies to Teams for Windows desktop, Teams for Mac desktop, new Outlook for Windows desktop, and new Outlook for web. When this will happen: Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by late November 2024. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 (previously mid-January) and expect to complete by early June 2025 (previously mid-May). How this will affect your organization: After this rollout, users can record and share the correct pronunciation of their name on their profile card. With a click, users can play and listen to name pronunciations recorded by their colleagues. To open a profile card in Outlook, double-click a name in the To or From field in any sent or received email. To open your profile card in Teams, select your profile photo in the upper right corner of the screen, and then select your name. To listen to a colleague's recorded pronunciation, select the speaker icon on their profile card. To record the pronunciation of a name, open your profile card in Outlook or Teams, and select the microphone icon. What you need to do to prepare: This feature is off by default. As an admin, you can enable the feature in Microsoft Graph using these instructions: namePronunciationSettings resource type - Microsoft Graph beta | Microsoft Learn Before rollout, we will update this post with revised documentation. You may want to notify your users about this change and update any relevant documentation. #newoutlookforwindows MC847877 — (Updated) Microsoft Outlook for iOS and Android: Choose fonts while composing Microsoft 365 Roadmap ID 409969 Updated June 4, 2025: We have updated the 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 June 2025 (previously late May). 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. MC714520 — (Updated) Apps for the web: Grid view for tasks in Microsoft To Do web version and To Do inside Microsoft Outlook Microsoft 365 Roadmap ID 381749 Updated June 17, 2025: We have updated the timeline below. Thank you for your patience. In Microsoft 365 apps for the web, users can see their tasks in a grid view and can update details inline in To Do on web and To Do app inside Microsoft Outlook. When this will happen: General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out late April 2024 (previously early April) and expect to complete by early July 2025 (previously late May). How this will affect your organization: When users open To Do on web within Microsoft Outlook, they will see their tasks in a tabular format or grid. They can continue to have the list view if preferred. What you need to do to prepare: There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate. Exchange Online MC1084635 — (Updated) Event Updates visible in email Microsoft 365 Roadmap ID 491018 Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. If an organizer updates an event that you have been invited to, you will now see Event Updated in the email and the updated location if applicable. When this will happen: General Availability (Worldwide): We will begin rolling out on late June 2025 (previously early June) and expect to complete by late July 2025. General Availability (GCC): We will begin rolling out on late June 2025 (previously early June) and expect to complete by late July 2025. General Availability (GCC High): We will begin rolling out on late June 2025 (previously early June) and expect to complete by late July 2025. General Availability (DoD): We will begin rolling out on late June 2025 (previously early June) and expect to complete by late July 2025. How this will affect your organization: Users will now understand that their event is being updated when receiving event related emails, when applicable. If the user has already RSVP’d to an event, and the organizer makes an update to the title, subject, or location, the email update will show “Event Updated” and the updated location (if applicable). Previously, the email update would show the event time and not explain that the event has been updated. This feature will not affect events that the user has not responded to and will not affect event updates where the organizer changes the time. 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. MC787382 — (Updated) Exchange Online to introduce External Recipient Rate Limit Updated June 25, 2025: We have updated the content. Thank you for your patience. Important update regarding the cloud hosted Mailbox External Recipient Rate Limit: In order to reduce the impact on customers, Microsoft has again decided to delay the rollout of the cloud hosted Mailbox External Recipient Rate Limit (MERRL) by ~six months. The MERRL will go into enforcement in April 2026 for trial tenants and new tenants if the tenant is provisioned on/after April 1st, 2026. In April 2026, the Exchange Admin Center Report will be available for tenant admins to review Sender mailbox data on external recipient volume. In October 2026, the MERRL will go into enforcement for all cloud hosted mailboxes in the WWMT environment including existing tenants. Please refer to the ACS email documentation (Prepare an email communication resource for Azure Communication Services - An Azure Communication Services concept article | Microsoft Learn) or reach out to your Microsoft account team for further support in this journey. Please note: We have made the decision to not proceed with this change for DoD, GCC, or GCC High organizations at this time. We will communicate via Message center when we are ready to proceed. The External Recipient Rate Limit will only apply to WWMT/Production. Please refer to the ACS email documentation (Prepare an email communication resource for Azure Communication Services - An Azure Communication Services concept article | Microsoft Learn) or reach out to your Microsoft account team for further support in this journey. ________________________________________ Today, we are announcing that, beginning in April 2026 (previously October 2025), Exchange Online will begin enforcing an external recipient rate limit of 2000 recipients in 24 hours. Exchange Online does not support bulk or high-volume transactional email. We have not enforced limiting of bulk email until now, but we plan on doing so with the introduction of an External Recipient Rate (ERR) limit. The ERR limit is being introduced to help reduce unfair usage and abuse of Exchange Online resources. When this will happen: The new ERR limit will be introduced in 2 phases: Phase 1 - Starting April 1, 2026, (previously October 2025) the limit will apply to cloud-hosted mailboxes of trial tenants and all tenants created after this date. Phase 2 – Starting October 1, 2026, (previously April 2026) we will start applying the limit to cloud-hosted mailboxes of existing tenants. How this will affect your organization: Exchange Online enforces a Recipient Rate limit of 10000 recipients for cloud-hosted mailboxes. The 2000 ERR limit will become a sublimit within this 10000 Recipient Rate limit. There is no change to the Recipient Rate limit, and both of these will be rolling limits for 24-hour windows. You can send to up to 2,000 external recipients in a 24-hour period, and if you max out the external recipient rate limit then you will still be able to send to up to 8,000 internal recipients in that same period. If you don't send to any external recipients in a 24-hour period, you can send to up to 10,000 internal recipients. For example: You use a cloud-hosted mailbox to send to 1,000 external recipients and 2,000 internal recipients at 6:00AM on Day 1, for a total of 3,000 recipients. You then send to another 1,000 external recipients at 8:00AM on Day 1. Because you sent to 2,000 external recipients, you will be blocked from sending to external recipients until 6:00AM on Day 2. During this period, you are able to send to up to 6,000 internal recipients, but for this example, let's assume that you don't. At 6:00AM on Day 2, the 1,000 external recipients and 2,000 internal recipients sent at 6:00AM on Day 1 will no longer count toward the 24-hour limit calculation. Thus, from 6:00-8:00AM on Day 2, you can send to up to 9,000 total recipients (e.g., 9,000 internal or 8,000 internal plus 1,000 external). If you don't send to any internal or external recipients during this period, then at 8:00AM on Day 2 you can again send to 10,000 recipients total with up to 2,000 of them being external recipients. What you need to do to prepare: If you have a cloud-hosted mailbox that needs to exceed the ERR limit, you can move to Azure Communication Services for Email, which is designed specifically for high volume email sent to recipients external to your tenant. Microsoft 365 MC1103604 — Microsoft 365 admin center: new scenarios enabling in Microsoft 365 Monitoring Microsoft 365 Roadmap ID 496176 We’re enhancing Microsoft Entra monitoring in the Microsoft 365 admin center’s Service Health Dashboard with additional organization-level telemetry. These updates will help tenant admins better assess service health and confirm issue impact more effectively. When this will happen: General Availability (Worldwide): We will begin rolling out on early July 2025 and expect to complete by early July 2025. How this will affect your organization: Tenant admins will gain access to expanded telemetry for Microsoft Entra monitoring scenarios. This enhancement provides deeper visibility into service health issues, enabling faster impact validation and improved incident response. This feature is available by default and does not require any configuration. What you can do to prepare:: We recommend that tenant admins familiarize themselves with the existing monitoring scenarios in the Microsoft 365 admin center by navigating to the Service Health Dashboard > Monitoring tab. Compliance considerations: Compliance monitoring/reporting: Yes - Provides enhanced visibility for compliance-related monitoring through improved telemetry. MC1098965 — Optional Connected Experiences (OCE) Settings in US Government Clouds We’re reaching out to inform you of a change impacting Optional connected experiences (OCE) for some of our services and recommended actions to remediate impact if you are affected. OCE are cloud-based services accessible through Microsoft 365 client applications. For more information on OCE, please see the “Overview of Optional Connected Experiences” section at the end of this communication. These services operate outside the FedRAMP accreditation boundary, which means they may involve the transmission, processing, or storage of customer data outside of the proper accreditation boundary. Until recently, administrators had to rely on a number of different admin policies and system configuration controls to restrict or allow access to OCEs. However, we recently began moving to the Cloud Policy Service, which allows admins to take advantage of Cloud Policy Service capabilities to provide more flexible, comprehensive, and centralized OCE management. While we were in the process of testing the Cloud Policy service prior to its release, a change was made on June 12 which unintentionally affected Production customers. This Cloud Policy update disables OCE by default. This may have disrupted users’ experience if your organization previously had OCE enabled. Specifically, users who had access to OCE features would have seen their access removed as the policy updates rolled out. We had previously communicated in MC1091439 that this change would occur on June 20, 2025, to give admins time to prepare for the change in OCE policy defaults. What actions do I need to take? If your tenant was impacted by this change and you wish to re-enable access to OCE features, please use Cloud Policy service to configure the OCE policy for your organization. As the preferred and primary method for managing access to OCE features, Cloud Policy ensures your configurations are consistently applied. Since it takes precedence over legacy OCE administrator controls, prioritizing Cloud Policy helps guarantee that your intended settings are enforced to meet organizational requirements. Below are the basic steps for creating a policy configuration. Sign in to the Microsoft 365 Apps admin centerusing the appropriate URL below. If you're using the admin center for the first time, review the terms. Then, select Accept. Links to the admin center differ by environment and are as follows: o GCCH: https://config.office365.us o DOD: https://config.apps.mil Under Customization, select Policy Management. On the Policy configurationspage, select Create. On the Start with the basicspage, enter a name (required) and a description (optional), then select Next. On the Choose the scopepage, determine whether the policy configuration applies to all users, specific groups, or to users who anonymously access documents using Office for the web. If the policy configuration applies to specific groups, you can now add multiple groups to a single policy configuration for more flexible targeting. To add groups, select Add Groups and choose the relevant groups. Adding multiple groups to a single policy configuration allows for the same group to be included in multiple policy configurations, facilitating a more streamlined and efficient policy management process. After making your selection, choose Next. On the Configure Settingspage, select the “Allow the use of additional optional connected experiences in Office” policy. In the Configuration Setting dropdown, select either enabled or disabled. After making your selections, selectNext to review your selections. Then select Create to create the policy configuration. Please note that the change to the OCE Policy will be picked up by clients over the next few days based on user action and client caching behavior. Overview of Optional Connected Experiences Optional connected experiences are cloud-backed services available to users when using Microsoft Office. Examples include creating a map chart in Excel or inserting an online picture into a Word document, both relying on services provided by Microsoft Bing. These services are not covered by your organization’s commercial agreement with Microsoft. Instead, they are offered directly to users and governed by the Microsoft Services Agreement. In some cases, third-party content or functionality may be provided through these experiences, and additional terms may apply. Some optional connected experiences might not be available in Office for the web applications but are available in other versions of Office, such as the desktop version on a device running Windows. Additionally, not all OCE features available to commercial Microsoft 365 tenants are available in U.S. Government Cloud environments. For more information, see Overview of optional connected experiences in Office. Cloud Policy Service & Optional Connected Experience information Overview of Cloud Policy service for Microsoft 365: Overview of Cloud Policy service for Microsoft 365 - Microsoft 365 Apps | Microsoft Learn Overview of optional connected experiences in Office: Overview of optional connected experiences in Office - Microsoft 365 Apps | Microsoft Learn Overview of Optional connected experiences in Teams: Teams Optional Connected Experiences - Microsoft Teams | Microsoft Learn MC1094117 — Optional Connected Experiences (OCE) Settings in US Government Clouds We’re reaching out to inform you of a recent change and actions required to configure optional connected experiences (OCE) in U.S. Government cloud environments. OCE are cloud-based services accessible through Microsoft 365 client applications. These services operate outside the FedRAMP accreditation boundary, which means they may involve the transmission, processing, or storage of customer data outside of the proper accreditation boundary. The Cloud Policy service received an update on June 12, 2025. As of this update, all OCE features are now disabled by default unless the OCE policy is specifically configured within the Cloud Policy service. This change overrides any previous configurations made using legacy OCE administrator controls. Organizations who chose to allow use of Optional Connected Experiences can enable this policy using the Cloud Policy service. What actions do I need to take? Use Cloud Policy service to configure the OCE policy across your organization. As the preferred and primary method for managing access to OCE features, Cloud Policy ensures your configurations are consistently applied. Since it takes precedence over legacy OCE administrator controls, prioritizing Cloud Policy helps guarantee that your intended settings are enforced to meet organizational requirements. Below are the basic steps for creating a policy configuration. Sign in to the Microsoft 365 Apps admin center. If you're using the admin center for the first time, review the terms. Then, select Accept. Under Customization, select Policy Management. On the Policy configurations page, select Create. On the Start with the basics page, enter a name (required) and a description (optional), then select Next. On the Choose the scope page, determine whether the policy configuration applies to all users, specific groups, or to users who anonymously access documents using Office for the web. If the policy configuration applies to specific groups, you can now add multiple groups to a single policy configuration for more flexible targeting. To add groups, select Add Groups and choose the relevant groups. Adding multiple groups to a single policy configuration allows for the same group to be included in multiple policy configurations, facilitating a more streamlined and efficient policy management process. After making your selection, choose Next. On the Configure Settings page, select the “Allow the use of additional optional connected experiences in Office” policy. In the Configuration Setting dropdown, select either enabled or disabled. After making your selections, select Next to review your selections. Then select Create to create the policy configuration. Overview of Optional Connected Experiences Optional connected experiences are cloud-backed services available to users when using Microsoft Office. Examples include creating a map chart in Excel or inserting an online picture into a Word document, both relying on services provided by Microsoft Bing. These services are not covered by your organization’s commercial agreement with Microsoft. Instead, they are offered directly to users and governed by the Microsoft Services Agreement. In some cases, third-party content or functionality may be provided through these experiences, and additional terms may apply. Some optional connected experiences might not be available in Office for the web applications but are available in other versions of Office, such as the desktop version on a device running Windows. Additionally, not all OCE features available to commercial Microsoft 365 tenants are available in U.S. Government Cloud environments. For more information, see Overview of optional connected experiences in Office. Cloud Policy Service & Optional Connected Experience information Overview of Cloud Policy service for Microsoft 365: Overview of Cloud Policy service for Microsoft 365 - Microsoft 365 Apps | Microsoft Learn Overview of optional connected experiences in Office: Overview of optional connected experiences in Office - Microsoft 365 Apps | Microsoft Learn MC1091449 — Microsoft Excel: Python in Excel add-on license will be generally available (GCC) The Python in Excel add-on license gives users premium Python compute for faster calculation times for more powerful data analysis. With this release, admins can purchase the Python in Excel add-on license for users in their organization. This feature is available for Microsoft Excel for Windows desktop, Excel for Mac desktop, and Excel for the web. When this will happen: General Availability (GCC): We will begin rolling out early July 2025 and expect to complete in early July 2025. How this will affect your organization: Python in Excel allows you to bring the capabilities of Python directly into the Excel grid by giving users the ability to add Python formulas to their workbooks without any installation required. These Python formulas are run by Excel in a secure container on the Microsoft Cloud with enterprise-level security as a compliant Microsoft 365 connected experience. Note: Some premium Python compute will be included with a user’s Microsoft 365 subscription each month, giving them access to faster calculation speeds. After they have used all their included premium compute, they can continue to use the Python in Excel feature with standard Python compute. If you would like users in your organization to get access to more premium compute, you can purchase and assign them a Python in Excel add-on license in the Microsoft admin center. Learn more: Buy and manage add-ons in the Microsoft 365 admin center | Microsoft Learn What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current Excel usage and determine which users may benefit from additional premium compute. You may want to notify your admins and/or users about this change and update internal documentation. To learn more about Python in Excel, please review the Python in Excel documentation For more information on additional admin controls for the Python in Excel feature, visit Data Security and Python in Excel As an admin, you maintain visibility and control over the Python in Excel add-on licenses in your tenant. You can view purchased licenses in the Microsoft 365 admin center. Learn more: Buy and manage add-ons in the Microsoft 365 admin center | Microsoft Learn MC1091439 — Optional Connected Experiences (OCE) Settings in US Government Clouds We’re reaching out to inform you of an upcoming change and actions required to configure optional connected experiences (OCE) in U.S. Government cloud environments. OCE are cloud-based services accessible through Microsoft 365 client applications. These services operate outside the FedRAMP accreditation boundary, which means they may involve the transmission, processing, or storage of customer data outside of the proper accreditation boundary. The legacy OCE administrator controls. To ensure uninterrupted access and consistent configuration, organizations should begin managing OCE features using Cloud Policy as soon as it becomes available. What actions do I need to take? Once Cloud Policy becomes available, use it to configure OCE settings across your organization. As the preferred and primary method for managing access to OCE features, Cloud Policy ensures your configurations are consistently applied. Since it takes precedence over legacy OCE administrator controls, prioritizing Cloud Policy helps guarantee that your intended settings are enforced to meet organizational requirements. Below are the basic steps for creating a policy configuration. Sign in to the Microsoft 365 Apps admin center. If you're using the admin center for the first time, review the terms. Then, select Accept. span>US Government Community (GCC) High customers can access the Microsoft 365 Apps admin center at config.office365.us Department of Defense (DoD) customers can access the Microsoft 365 Apps admin center at config.apps.mil Under Customization, select Policy Management. On the Policy configurations page, select Create. On the Start with the basics page, enter a name (required) and a description (optional), then select Next. On the Choose the scope page, determine whether the policy configuration applies to all users, specific groups, or to users who anonymously access documents using Office for the web. If the policy configuration applies to specific groups, you can now add multiple groups to a single policy configuration for more flexible targeting. To add groups, select Add Groups and choose the relevant groups. Adding multiple groups to a single policy configuration allows for the same group to be included in multiple policy configurations, facilitating a more streamlined and efficient policy management process. After making your selection, choose Next. On the Configure Settings page, select the “Allow the use of additional optional connected experiences in Office” policy. In the Configuration Setting dropdown, select either enabled or disabled. After making your selections, select Next to review your selections. Then select Create to create the policy configuration. Overview of Optional Connected Experiences Optional connected experiences are cloud-backed services available to users when using Microsoft Office. Examples include creating a map chart in Excel or inserting an online picture into a Word document, both relying on services provided by Microsoft Bing. These services are not covered by your organization’s commercial agreement with Microsoft. Instead, they are offered directly to users and governed by the Microsoft Services Agreement. In some cases, third-party content or functionality may be provided through these experiences, and additional terms may apply. Some optional connected experiences might not be available in Office for the web applications but are available in other versions of Office, such as the desktop version on a device running Windows. Additionally, not all OCE features available to commercial Microsoft 365 tenants are available in U.S. Government Cloud environments. For more information, see Overview of optional connected experiences in Office. Cloud Policy Service & Optional Connected Experience information Overview of Cloud Policy service for Microsoft 365: Overview of Cloud Policy service for Microsoft 365 - Microsoft 365 Apps | Microsoft Learn Overview of optional connected experiences in Office: Overview of optional connected experiences in Office - Microsoft 365 Apps | Microsoft Learn MC1081598 — (Updated) Microsoft 365 web app: Name update to “Microsoft 365 Copilot” and updated UI Microsoft 365 Roadmap ID 494998 Updated July 1, 2025: We have updated the timeline below. Thank you for your patience. Beginning late July 2025 (previously late June), the Microsoft 365 app will update to the Microsoft 365 Copilot app, including a refreshed navigation pane and simplified UI. These updates apply to the web endpoint only, accessible from: https://www.ohome.apps.mil Please refer to MC1051092 for previously communicated updates for the Microsoft 365 app that these updates will build on. When this will happen: General Availability (DoD, web only): We will begin rolling out late July 2025 (previously late June) and expect to complete by early August 2025 (previously early July). How this will affect your organization: All users will see the new app name, Microsoft 365 Copilot, and a refreshed UI. The individual user experience in the Microsoft 365 Copilot app will vary based on if a user has a Microsoft 365 Copilot license. The Microsoft 365 Copilot license will be available for DoD in late June 2025. Refreshed Navigation Pane – The left navigation pane will include essential modules like Search, Create, and Apps. Users can pin and unpin apps to customize their workspace. Search – With this update, Search replaces the Home module. Search will have a refreshed UI, displaying key files in dedicated sections for easier access and a search bar to help them quickly find what they need. Includes the updates listed above along with additional specific modules for users with a Microsoft 365 Copilot license: Chat – Chat has been streamlined for a simplified experience with an updated collapsable left navigation page for quick access to chat history and Copilot pages. The input box will be located in the center of the UI with prompt suggestions below it. Users will have access to Work chat to reason over their files and web search (grounding) in Work chat will be off by default. A dedicated Web chat will become available later and will be communicated separately. Notebooks – Copilot can ground on the contents of a user’s notebook, to give them more relevant, contextualized responses based on prompts. Users can gather information from chats, meetings, pages, and files, as well as organize and store important documents, notes, and tasks. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. Admins can manage the Microsoft 365 Copilot app for users with a Microsoft 365 Copilot license with the following controls. MC1060472 — (Updated) The new Microsoft Planner for the web (GCC High) Microsoft 365 Roadmap ID 49058 Updated June 12, 2025: We have updated the timeline. Thank you for your patience. The new Microsoft Planner for the web brings together the simplicity of Microsoft To Do, the collaboration of Planner, and the power of Project for the web into a simple, scalable solution that spans individual task management to professional project management. With this rollout, we will update the existing web version of Planner to the new Planner. A Microsoft 365 license is required to use the new Planner. A Project Plan 3 license, Project Plan 5 license, or a premium Planner trial license is required to create premium plans. When this will happen: General Availability (GCC High): We will begin rolling out mid-July 2025 (previously mid-May) and expect to complete by mid-August 2025 (previously mid-June). How this will affect your organization: As part of our efforts to simplify Planner, these existing features are not available in the new Planner due to low usage: Charts for pinned plans in Planner Hub While you were awaynotifications Activity log of a task’s creation, assignments, and completion date in the task comments Links to group members, Microsoft Outlook conversations, and Microsoft OneNote notebook (you can still access these links in Outlook) Menu option to Leave plan Suggested attachments Charts view and Schedule view on the Assigned to me page Lastly, after the new Planner for the web is rolled out, users can still access Project for the web. For this rollout, we will merge notification settings in the new Planner and Project for the web. Users will see identical notification options in the two apps, and the settings they choose will be reflected across both apps. Until a user reviews their notification settings, we will maintain what the user had set before the notifications are merged. What you need to do to prepare: The new Planner is on by default for users with the required licenses. 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. Please review our Planner blog announcementto update any internal documentation. We will update Planner help documentation in the coming weeks. Supporting adoption resources: The new Microsoft Planner. MC1056996 — (Updated) Microsoft Excel: Extending support for Insights Services (GCC High, DoD) Microsoft 365 Roadmap ID 488142 Updated June 25, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Excel: Support for the Analyze Data feature, which will be found on the Data tab This message applies to Excel for Windows desktop, Excel for Mac desktop, and Excel for the web. When this will happen: General Availability (GCC High, DoD): We will begin rolling out late August 2025 (previously late June) and expect to complete by late September 2025 (previously late August). How this will affect your organization: Analyze Data can generate charts and graphs that may provide insights and answer questions you may have about your data: 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 or after the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Analyze Data in Excel - Microsoft Support MC1051087 — (Updated) Microsoft 365 web app: Updated experience (GCC High) Updated June 5, 2025: We have updated the timeline below. Thank you for your patience. Coming soon: An updated experience for the Microsoft 365 web app at https://www.office365.us When this will happen: General Availability (GCC High): We will begin rolling out mid-June 2025 (previously late May). How this will affect your organization: This rollout includes these key changes: Microsoft 365 apps that were pinned to the left navigation will be available in the Apps tab. Profile and Settings buttons will move from the top right to the bottom left corner. New content types and templates will be added to the Create tab. Search bar will move from the top header to the Home tab. Organization branding will be removed along with the top header. This change will be on by default. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. MC1047236 — (Updated) Cloud Policy Service available to GCC-H and DoD customers Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. The Cloud policy service will begin rolling out for Microsoft 365 GCC-H and DoD customers late June 2025. The Cloud Policy service allows Microsoft 365 administrators to configure policies for Microsoft 365 apps and assign these policies using Microsoft 365 or Entra ID groups. When this will happen: General Availability (GCC High): We will begin rolling out late June 2025 (previously early June) and expect to complete by late June 2025 (previously early June). General Availability (DoD): We will begin rolling out late June 2025 (previously early June) and expect to complete by late June 2025 (previously early June). How this will affect your organization: Once configured, these policies are automatically enforced as users sign in and use Microsoft 365 apps and services. The initial release will support policies for Microsoft 365 Apps for enterprise on Windows and future updates will bring support for additional applications and platforms. What you need to do to prepare: Review online documentation and implement as appropriate for your organization. For additional information about the Cloud Policy service, refer to Overview of the Cloud Policy service for Microsoft 365 Apps for enterprise. MC1041965 — (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for the web (GCC) Microsoft 365 Roadmap ID 485764 Updated June 27, 2025: We have updated the 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 the web. MC980798 (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) (published January 2025, updated February 2025). When this will happen: General Availability (GCC): We will begin rolling out to Excel for the web late June 2025 (previously mid-June) and expect to complete by mid-July 2025 (previously mid-May). 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 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. Documentation - Office 365 IP Address and URL web service June 30, 2025 - GCC April 30, 2025 - GCC High April 30, 2025 - DODUnderstanding Compliance Between Commercial, Government, DoD & Secret Offerings - July 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.History of Microsoft Cloud Offerings leading to the US Sovereign Cloud - July 2025 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.June 2025 - Microsoft 365 US Public Sector Roadmap Newsletter
Outlook Updated behavior for switching back from new Outlook to classic Outlook - GCC Microsoft 365 Copilot Microsoft 365 Copilot service plan diagnostic tool and service plans | Microsoft Learn - GCC Discover the Future of AI in Government Are you ready to explore the transformative power of artificial intelligence in the public sector? Join us as we delve into the key themes discussed in the recent seminar, "Microsoft AI for Government," led by Jason Payne, Chief Technology Officer for Microsoft Federal. What’s New in Microsoft 365 Copilot for Government | Microsoft Community Hub The AI-powered capabilities of Microsoft 365 Copilot are expanding across government environments. Whether you’re in GCC, GCC High, or DoD, here’s what you need to know about upcoming availability, what’s changing, and how to prepare. What’s New in Microsoft Teams | April 2025 Brand impersonation phishing protection first launched for commercial users in January, and now is available for the GCC, GCC-H, and DoD audiences. VDI users can join optimized meetings with people in other Microsoft 365 cloud environments (e.g., a user in GCC-H joining a meeting in commercial, GCC, or DOD) through three options: authenticated access via cross-cloud meeting connection, authenticated access using a guest account, or anonymous access. These scenarios require Slimcore-based optimization. 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) 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 MC1087628 — Microsoft Lists: Mobile app for iOS will retire (GCC High, DoD) We will retire the iOS mobile app for Microsoft Lists. We recommend users switch to the Microsoft Lists mobile browser experience, which offers more functionality and continues to be updated with latest improvements. When this will happen: Late June 2025: An information banner will display in the app to inform users about the upcoming retirement of the app and recommend they switch to the mobile web experience. Mid-September 2025: New users will not be able to install the mobile app. Mid-November 2025: The app will no longer be visible for new users to download from the Apple App Store. Existing app users will get an error when opening the app. How this will affect your organization: Users will no longer be able to install the app or use the installed app after the retirement. Existing user data and information will not be affected by this retirement and will continue to be available through either through Microsoft Lists for Windows desktop or the mobile browser. To access Lists in a mobile browser, users can go to their SharePoint root site, which is typically https://[organization-name].sharepoint.com (for example, https://contoso.sharepoint.com) and then tap the Microsoft Suite navigation icon in the top left corner. If Lists is not in the list of apps, the user can select More apps from the bottom right corner and then tap Lists. Left: Lists in a mobile browser. Right: Accessing Lists on a mobile browser through SharePoint: What you need to do to prepare: This change will happen automatically by the specified dates with no admin action required. Please notify your users about this change and recommend the suggested alternative. Learn more: Get started with the Microsoft Lists mobile app - Microsoft Support (will be updated before retirement) MC1072889 — SharePoint Alerts retirement Microsoft is retiring the SharePoint Alerts feature to streamline and modernize user notifications. With Power Automate, organizations can benefit from an enhanced, versatile solution that goes beyond traditional alerts, offering seamless integration across Microsoft 365 services and more. Key Points Major: Retirement Timeline: o Starting from July 2025, the creation of new SharePoint Alerts will be gradually turned off for newly onboarding tenants. o Starting from September 2025, the creation of new SharePoint Alerts will be gradually turned off for all tenants. o Starting from October 2025, the SharePoint Alert expiration feature will be gradually activated. Once activated, any SharePoint Alert will have a validity of 30 days starting from its first run, then it will expire. Users can self-service re-enable expired SharePoint Alerts and extend their expiration for another 30 days. Re-enabling and extending SharePoint Alerts can be done by using the “Manage my alerts” list/library menu item, opening the SharePoint Alert to update, extending its expiration date and clicking OK. For more details refer to this support article. o Starting July 2026, Microsoft will remove the ability to use SharePoint Alerts, existing SharePoint Alerts cannot be extended anymore and will not work anymore. Action: Review and assess impact How this will affect your organization If your organization still uses SharePoint Alerts, they will no longer function from July 2026 onwards. We recommend customers to port their SharePoint Alerts to the Power Automate platform or alternatively create a SharePoint Rule. What you need to do to prepare It’s recommended to update your user training content and prepare your help desk to support your organization with this retirement. SharePoint Alerts users will be notified of this feature retirement via banners in both the relevant SharePoint Online page and Alert emails and users can self-service extend the alerts they deem required. For admins: Optionally use the Microsoft 365 Assessment tool to scan your tenants for SharePoint Alerts. Review the documentation on using Power Automate with SharePoint Online. Review the documentation on using SharePoint Rules. Note: There will not be an option to extend SharePoint Alerts beyond July 2026. Learn more: Detailed support article with additional resources. MC1072408 — (Updated) Microsoft SharePoint: Storage insights will be included in Microsoft 365 admin center usage reports Microsoft 365 Roadmap ID 482200 Updated May 29, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for the Microsoft SharePoint usage report in the Microsoft 365 admin center: A new Storage tab will provide a high-level view of your overall SharePoint quota consumption and recommended actions for storage management. Note: This report is available to non-Education tenants. Education tenants should refer to their pooled storage report. Learn more about viewing the pooled storage report: Pooled storage management - M365 Education | Microsoft Learn When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025 (previously late May). How this will affect your organization: The SharePoint storage report provides an overview of your tenant’s storage profile across multiple geographies. It will help you understand your tenant’s storage growth trend and make informed decisions on when to buy more storage or clean up usage. The report will include suggestions for optimizing storage, such as setting file history limits, archiving inactive sites, and creating site lifecycle management policies. Also, banner notifications will appear when your tenant is approaching or over the storage quota. To start using the SharePoint storage report: In the Microsoft 365 admin center, go to Reports > Usage page From the homepage dashboard, under Reports, select SharePoint. Select the Storage tab. The new Storage tab on the SharePoint storage report in the Microsoft 365 admin center: What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Learn more: Microsoft 365 Reports in the admin center – SharePoint storage - Microsoft 365 admin | Microsoft Learn MC1069560 — Modern SharePoint: New Template gallery and 50+ out-of-the-box page templates Microsoft 365 Roadmap ID 490565 Coming soon to Microsoft SharePoint: We will roll out Modern SharePoint page templates, a new feature designed to streamline content creation and elevate the visual consistency across your organization’s SharePoint pages or news posts. This rollout will introduce a centralized Template gallery that enables users to effortlessly discover, preview, and apply both Microsoft-provided and customer created site-specific templates. With over 50 new out-of-the-box (OOB) templates, this feature empowers users to build high-quality, aesthetically pleasing on-brand pages with ease. When this will happen: Targeted Release: We will begin rolling out at mid-June 2025 and expect to complete by late June 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early July 2025 and expect to complete by late July 2025. How this will affect your organization: With the introduction of the Template gallery, SharePoint users will have a dedicated experience to: Access both Saved on this site (templates created by customer on this site) and From Microsoft (OOB templates provided by Microsoft) in one centralized location: the new Template gallery. Browse and preview templates with ease before applying them to new pages. Leverage 50+ new OOB templates that are aesthetically pleasing, professionally designed, and easy to use—ideal for common scenarios such as status updates, event announcements, team introductions, and more. This will drive improved content quality, enhanced branding consistency, and faster page creation for your organization, ultimately driving higher user engagement. This change will be on 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. No action is required to enable this feature. However, we recommend the following to maximize its value: Inform your SharePoint site authors of the new Template gallery experience. Encourage content authors to explore the new OOB templates to reduce time spent on page creation while maintaining visual consistency. Before rollout, we will update this post with new documentation. Thank you for being a valued Microsoft 365 customer and for your continued partnership in making SharePoint better for everyone. MC1066155 — Microsoft SharePoint Online: [Important update] Enabling a new Public Content Delivery Network (CDN) domain Microsoft 365 Roadmap ID 489230 Coming soon: We will migrate the hosting of Microsoft SharePoint Online assets to a new content delivery network (CDN) service, Microsoft Azure Front Door (AFD). When this will happen: General Availability (Worldwide): We will begin rolling out early June 2025 and expect to complete by late July 2025. How this will affect your organization: As part of this migration, we will introduce a new public CDN domain, public-cdn.sharepointonline.com. To ensure your SharePoint Online (SPO) sites and pages are fully prepared, please review these guidelines: Add the new domain to your network allow list: If you enable domain-based allow lists in your network configurations, please ensure that the new domain public-cdn.sharepointonline.com is also included. Avoid hardcoding CDN URLs: To ensure seamless integration and for future proofing, please refrain from hardcoding the CDN URLs in your applications and scripts. Do not block the old domain: The old CDN domain publiccdn.sharepointonline.com is still in use. Please continue to allow access to the existing CDN domain until further notification from us. What you need to do to prepare: Review your current configuration to assess the impact on your organization. This rollout will happen automatically by the specified dates with no other admin action required before the rollout. We appreciate your cooperation and understanding as we work to enhance the performance and reliability of SharePoint Online. If you have questions or need further assistance, please do not hesitate to reach out to our support team. Thank you for your attention to this important update. Learn more about CDN for SPO: Use Office 365 Content Delivery Network (CDN) with SharePoint Online - Microsoft 365 Enterprise | Microsoft Learn MC1055557 — (Updated) SharePoint Online: Content Security Policy Control in Tenant Administration Updated May 21, 2025: We have updated the content Thank you for your patience. SharePoint Online Tenant Administrators can now allow script sources for modern pages in SharePoint sites. This feature is particularly useful in scenarios where modern pages have custom code that loads scripts (e.g., TypeScript code) from external sources like a content delivery network (CDN). SharePoint will now report to administrators where sources that have not been allowed are loaded from, providing a way for administrators to identify those sources and take action. Tenant Administrators can also enforce browsers to only load scripts from allowed sources. This behavior can be enabled using SharePoint Online Management Shell. When this will happen: Targeted Release: We will begin rolling out on late March 2025 and expect to complete by early April 2025. General Availability (Worldwide): We will begin rolling out on late April 2025 and expect to complete by late April 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out on late April 2025 and expect to complete by early June 2025 (previously mid-May). How this will affect your organization: Tenant Administrators will have the option to control and govern where custom code loads scripts and, if needed, enforce browsers to only load scripts from trusted sources. A new "Trusted script sources" page will give administrators control over which source can be trusted to load scripts. What you need to do to prepare: This rollout will happen automatically with no admin action required. MC1055555 — (Updated) Microsoft SharePoint Online: We will remove retired DISCO and WSDL web pages Updated May 22, 2025: We have updated the content. Thank you for your patience. ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We recommend using Microsoft Graph for remote operations where possible. We will remove these pages from Microsoft SharePoint Online starting mid-August 2025 and ending in mid-September 2025. Please refer to the following information regarding the DISCO and WSDL endpoints These endpoints were originally designed for use with development tools from the early 2000s and were never a preferred or widely adopted method for generating proxy classes in SharePoint development. These endpoints are not tenant-specific and are not associated with any individual tenant’s configuration or ownership. Usage across the SharePoint Online service is extremely rare. In fact, most of these endpoints show zero usage. These endpoints were primarily used in legacy development scenarios and are not required for modern SharePoint development practices. If your organization has an internal development team, we recommend consulting with them to confirm whether these endpoints are in use. However, it is extremely unlikely that they are being used in any current development workflows. Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online - Microsoft 365 Developer Blog MC1024394 — (Updated) Microsoft SharePoint: New card animation feature for Pages, News, and Microsoft Viva Amplify Microsoft 365 Roadmap ID 481510 Updated May 20, 2025: We have updated the content. Thank you for your patience. When this will happen: Coming soon for Microsoft SharePoint: Cards can be animated for some web parts (Editorial cards, Quick Links, and People) in SharePoint Pages, News, and Microsoft Viva Amplify. We previously incorrectly indicated that Images web part was supported for this feature. Targeted Release: We will begin rolling early April 2025 (previously out late-April) and expect to complete by early May 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-April 2025 (previously early May) and expect to complete by early May 2025 (previously late May). How this will affect your organization: This feature will be enabled by default for new cards created after the feature is released. Users can disable card animation in the web part property pane. To add animation to existing web parts, users can enable the setting in the web part property pane. To preview the card animation, view the published page or use Preview mode. Pages and web parts created before this rollout are not impacted by this change. 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. MC974358 — (Updated) Microsoft SharePoint admin center: New "App insights" feature will be in Public Preview Microsoft 365 Roadmap ID 417481 Updated May 20, 2025: We have updated the timeline below. Thank you for your patience. 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 early July 2025 (previously mid-May) and expect to complete by late July 2025 (previously late May). 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 licenses. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. 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 MC792601 — SharePoint Framework domain isolated web parts retirement Updated June 2, 2025: This update serves as a reminder that SharePoint Framework domain isolated web parts will retire and stop working in 10 months from now (April 2, 2026). After careful consideration and extensive review of usage data and feedback Microsoft has decided to retire the domain isolated web parts feature in the SharePoint Framework (SPFx). When will this happen: Starting April 2, 2025, domain isolated web parts will be turned off for any newly created tenants. Starting April 2, 2026, Microsoft will remove the ability to use domain isolated web parts for existing tenants. How this will affect your organization: If your organization still uses domain isolated web parts, after the change has rolled out these will render an error message and stop functioning. We recommend customers to update the impacted web parts as regular web parts and redeploy them. What you need to do to prepare: To understand whether you have installed domain isolated web parts and granted permissions you can verify if the SharePoint admin center API access page contains permissions listed under the Isolated grouping. If you see permissions listed under Isolated then you can use the instructions described on the domain isolated web part retirement page to discover the solutions, their domain isolated web parts and where those web parts are used. This resource will also contain the needed steps to update the web parts to not use domain isolation. Note: There will not be an option to extend domain isolated web parts beyond April 2, 2026. Learn more: Domain isolated web part retirement page Retirement announcement blog post MC693865 — (Updated) SharePoint Add-In retirement in Microsoft 365 Updated June 2, 2025: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 10 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 tool to scan your tenants for SharePoint Add-In usage. Disable SharePoint Add-Ins on 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-Ins in Microsoft 365. MC693863 — (Updated) Azure ACS retirement in Microsoft 365 Updated June 2, 2025: This update serves as a reminder that Azure ACS in Microsoft 365 will retire and stop working in 10 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 tool to 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 Online in Microsoft 365. MC542767 — (Updated) SharePoint 2013 workflow retirement Updated June 2, 2025: This update serves as a reminder that SharePoint 2013 workflow will retire and stop working in 10 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 resources as 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 article with additional resources. OneDrive for Business MC1079736 — Microsoft SharePoint and Microsoft OneDrive: Apply watermark to PDFs Microsoft 365 Roadmap ID 485796 Microsoft OneDrive and Microsoft SharePoint for web will soon let users add text or images as watermarks to PDF documents. Users can place the watermark in front of their content and choose the desired location and angle for the watermark. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-June 2025 and expect to complete by early July 2025. How this will affect your organization: To add text as a watermark: Open a PDF stored in OneDrive or SharePoint and then select Edit at the top right of the screen. Select Watermark from the top menu, enter your text, customize the formatting and color, and place the watermark in the desired position. Choose from nine positions: top left, top center, top right, middle left, middle center, middle right, bottom left, bottom center, and bottom right. Text formatting options include bold, italic, color, size, transparency, and rotation. Preview changes on the right side of the screen, and then select Apply to save changes. To add an image as a watermark: From the Watermark dialog box, select Picture to insert an image as a watermark. Adjust scale, transparency, and rotation if desired. Set the image in the desired position. Choose from nine positions: top left, top center, top right, middle left, middle center, middle right, bottom left, bottom center, and bottom right. Preview changes on the right side of the screen, and then select Apply to save. To edit an existing watermark: Select Watermark from the top menu, and then select the watermark to edit. Follow the same steps for adding text or images to modify text or images in the watermark. To add another watermark, select Add new under the Watermark toolbar. To remove a watermark: Select Watermark from the top menu, and then select the watermark to remove. Select the Remove button at the bottom of the screen. FAQs Can I modify watermarks using other PDF tools? Watermarks added in OneDrive or SharePoint will be visible in other PDF tools but cannot be edited or removed with third-party tools. Does applying a watermark change my original PDF? Yes, applying a watermark will change your PDF document. The watermark is superimposed on the PDF content. Users can easily remove any watermark applied in OneDrive or SharePoint. What you need to do to prepare: Note: Some users may see this feature before other users in your organization. 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. Before rollout, we will update this post with new documentation. MC1078765 — Microsoft OneDrive: New "View and upload" permission for Anyone links to folders Microsoft 365 Roadmap ID 485801 Coming soon: If desired, admins will be able to configure View and upload as a permission option for Anyone links to folders in Microsoft OneDrive. After this rollout, tenants will be able to restrict Anyone links for folders to view only while still enabling the Request files functionality. When this will happen: Targeted Release: We will begin rolling out early June 2025 and expect to complete by late June 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late June 2025 and expect to complete by early August 2025. How this will affect your organization: This feature offers admins more granular control over content access, ensures compliance with internal data policies, helps enable external sharing, and helps administrators maintain a higher level of data governance. This feature is off by default and will not impact existing settings. After this rollout, admins can enable the new View and upload option with Microsoft PowerShell: Set-SPOTenant (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn or in the Microsoft SharePoint admin center by going to Policies > Sharing: Before this rollout: When an admin sets Anyone links for folders to View, edit, and upload in PowerShell or the SharePoint admin center, the user can set folders to Can edit or Can view and can use the Request files feature for the folder. To comply with internal data policies or to have greater information control, an admin may choose to restrict the Anyone links for folders to View. With this setting, users are limited to Can view folder links, but the Request files feature is not available. After this rollout: Admins can set Anyone links for folders to View and upload. With this setting, users can only set folders to Anyone can view links (Can view or Can't download) and continue to access the Request files feature. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Learn more The Advanced settings for Anyone links section in Manage sharing settings for SharePoint and OneDrive in Microsoft 365 - SharePoint in Microsoft 365 | Microsoft Learn Set-SPOTenant (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn MC1077863 — Microsoft OneDrive and Microsoft SharePoint: Use the table of contents in a PDF to navigate Microsoft 365 Roadmap ID 486859 Microsoft OneDrive for the web and Microsoft SharePoint Online will be able to display a table of contents if a PDF already has one. Users can select an item in the table of contents to jump directly to the location of that item in the PDF. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-June 2025 and expect to complete by early July 2025. How this will affect your organization: Open a PDF in OneDrive for the web or in SharePoint. If your PDF contains a table of contents, it will show up on the left side of your screen: Select any line item to jump directly to the page To close the table of contents, select the X in the top right of the panel. Select the View the table of contents icon in the top left of the panel to open it again: This feature will be on by default. What you need to do to prepare: Note: Some users may see this feature before other users within your organization. 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. MC1061109 — (Updated) Microsoft SharePoint and Microsoft OneDrive: New PDF compression feature Microsoft 365 Roadmap ID 487440 Updated May 30, 2025: We have updated the timeline below. Thank you for your patience. Coming soon: Users will be able to use the new Compress feature to reduce the file sizes of PDFs stored on Microsoft OneDrive for the web or Microsoft SharePoint. Users can choose from three different compression levels. When this will happen: Targeted Release: We will begin rolling out early July 2025 (previously late April) and expect to complete by late July 2025 (previously early May). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late July 2025 (previously late May) and expect to complete by early August 2025 (previously early June). How this will affect your organization: To compress PDF files for a smaller size: Open a PDF in OneDrive for the web (in SharePoint, go to the document library and choose Preview): Select the Compress button at the top of the screen. Select a compression level and then select Save a copy to save the compressed file. A progress notification will appear at the bottom of the screen. After the compression is complete, select Open from the notification to view the compressed file. FAQ What is the quality and subsampling for each compression level? We offer three levels of image compression. All use lossy compression and chroma subsampling to reduce file sizes while maintaining visual quality. The options are: Light compression: Apply 4:2:0 color subsampling and reduce 25% of image pixels. Medium compression: Apply 4:2:0 color subsampling and reduce 50% of image pixels. Heavy compression: Apply 4:2:0 color subsampling and reduce 75% of image pixels. Users can compress one PDF at a time. The original file must be smaller than 300 MB. This feature is on by default. What you need to do to prepare: Note: Some users may see this feature before other users in your organization. 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. Before rollout, we will update this post with new documentation. MC1017119 — (Updated) SharePoint: OneDrive and SharePoint – Protect PDF with password Microsoft 365 Roadmap ID 482193 Updated May 29, 2025: We have updated the content. Thank you for your patience. SharePoint and OneDrive users can now secure their PDF files by adding protection that restricts unauthorized access through OneDrive Web. This feature allows you to set an open password, which is required to access the PDF, or an owner password, which sets permissions for actions such as printing or editing the document. This ensures your files remain secure and only accessible to authorized individuals When this will happen: Targeted Release: We will begin rolling out early July 2025 (previously mid-May) and expect to complete by mid-July 2025 (previously late May). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-July 2025 (previously late May) and expect to complete by late July 2025 (previously early June). 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. To set up an open password: Open a PDF you have saved in OneDrive or SharePoint document library, Click the lock icon located at the top left of the screen 3.Under Security, enter matching passwords. Click Save as to password protect this document, Choose the location where you want to save the file and click Save here. A notification will appear at the bottom of the screen, indicating that a new file has been successfully saved. To set up an owner password: Open a PDF you have saved in OneDrive or SharePoint document library, Click the lock icon located at the top left of the screen, Under Protection, check the Grant permissions box. Under Grant permission, check the box for the permissions you want to allow on this document. Type matching owner passwords and then click Save as to set permissions for this document, Choose the location where you want to save the file and click Save here, A notification will appear at the bottom of the screen, indicating that a new file has been successfully saved. 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. FAQ Will password protection overwrite my current PDF? No, we currently only allow the "Save as" option, so the original PDF will remain intact. Can I see the same permission set on the same PDF document using other apps? Yes, users are able to view the same permission settings, and the same restrictions are applied when they view the PDF within OneDrive and SharePoint. What you need to do to prepare: Note: Some users may see this feature before other users within your organization. Microsoft Planner MC1072394 — Microsoft Planner being added Planner premium subscriptions. To support the move to Planner for the web and Planner in Teams (MC1068905), Planner is being added to subscriptions that include access to Project for the web and Project in Teams. On or after June 11th, 2025, the Planner service plans Microsoft Planner (PROJECTWORKMANAGEMENT) for all environments (except GCC) Office 365 Planner for Government (PROJECTWORKMANAGEMENT_GOV) for GCC will be added to the following subscriptions: Planner Plan 1 (including GCC and GCCH counterparts) Planner and Project Plan 3 (including faculty, student, GCC and GCCH counterparts) Planner and Project Plan 5 (including faculty, student, GCC and GCCH counterparts) Subscriptions that include Dynamics Project Operations and Dynamics Project Operations Attach like Dynamics 365 Plan 1 Enterprise Edition The Planner service plans directly support the infrastructure required to run Microsoft Planner and Planner premium. After June 30th, Planner premium email notification will require Planner to be enabled in your organization and email notifications settings can be managed only through Planner web. How this affects your organization: If your organization already has a subscription that includes Planner and it is enabled, there will be no impact to you. On or after June 11th, 2025, the service plans will be “on” by default for the subscriptions referenced above and Microsoft Planner will be available in your organization. On or after June 30th, Planner premium email notifications will require Planner to be enabled for your organization to continue to work. Email notification settings can be managed only through Planner web. Wha you can do to prepare: Review the documentation on the Microsoft Planner service if your organization doesn't use Microsoft Planner today Microsoft Planner for admins - Microsoft Planner | Microsoft Learn. MC1072390 — Planner - New service plan to M365 users A new service plan is being added to the Microsoft 365 and Office 365 suites which enables additional capabilities to interact with premium plans in Planner. Microsoft 365 and Office 365 users can now edit shared premium plans, enabling them to collaborate more seamlessly with premium licensed users. These users can access any capabilities where Microsoft Planner basic and premium plans overlap. For example, the user could edit task name, assign tasks to others, and change the priority and start date of a task. Any non-overlapping fields, such as dependencies or custom fields, would still require a premium license to edit. The new service plan will be added to the following licenses: Microsoft 365 F3 and Office 365 F3 Office 365 E1 Microsoft 365 for business Microsoft E3 and Office 365 E3 Microsoft E5 and Office 365 E5 This change is applicable only for premium plans created in Planner web, Planner in teams and Project for the web in default environment. For premium plans created in non-default environments, there is no change in the capabilities. Refer to this link for more details - Office 365 User access to Project for the web and Roadmap When this will happen: This update will be applicable from mid-June 2025. How this will affect your organization: With this update, Microsoft 365 users in your organization can now edit premium plans shared with them. What you need to do to prepare: You may consider updating your training and documentation as appropriate. MC1068905 — Microsoft Project for the web and Project in Teams will retire and redirect to Planner for the web and Planner in Teams The new Microsoft Planner for the web (https://planner.cloud.microsoft) brings together the simplicity of Microsoft To Do, the collaboration of Planner, and the advanced capabilities of Microsoft Project into one platform. Planner for the web offers a comprehensive and scalable solution, whether users are managing individual tasks or overseeing professional-grade projects. All users with an existing Project for the web license will have access to Planner. (A Microsoft Teams license is also required to use Planner in Teams.) Starting early August 2025, we will retire Project for the web and will redirect its users to Planner for the web and Planner for Teams, for a smooth transition. Premium plans from Project for the web automatically will be available in Planner, ensuring users experience a seamless migration without losing any data. We will add these capabilities to Planner before the redirect goes into effect: Users will be able view and manage non-default environment plans in Planner. We will rename Project Power app to Planner power app (and the button to open the plan in Project will be replaced with a button to open the plan in Planner). Project settings in the Microsoft 365 admin center will move to the Planner page in the admin center. Tenants with only Project licenses will be able to access basic plan functionality in Planner. We will roll out the new Planner to GCC High. User experience in Project and Roadmap for the web and Teams When launching Project for the web or Roadmap for the web, users will see a page directing them to open Planner for the web, they will not be able to dismiss this screen or use Project or Roadmap for the web. Existing Project tabs in Teams will no longer open the associated project, and instead will show users a page to inform them to re-pin their tab using the Planner tab for Teams Existing Roadmap tabs in Teams will no longer open the associated roadmap, and instead will show a page directing users to the Planner app in Teams Users will no longer have access to view or create Roadmaps in Project for the web, but their Roadmap data will remain in Dataverse We will remove the Project tab and Roadmap tab apps from the Teams app store. When this will happen: For Worldwide: We will begin rolling out early August 2025 and expect to complete by mid-August 2025. For GCC: We will begin rolling out mid-August 2025 and expect to complete by late August 2025. For GCC High: We will begin rolling out late August 2025 and expect to complete by mid-September 2025. How this will affect your organization: Due to low usage and our efforts to simplify the user experience, these Project for the web features are not available in Planner: Users will need to migrate their existing Roadmaps to Portfolios because Planner does not support opening roadmaps. Learn more about migrating Roadmaps to Portfolios: Manage multiple plans with portfolios in Microsoft Planner - Microsoft Support Portfolios in Planner do not support adding rows for Microsoft Azure DevOps or Microsoft Project Online Import MPP is not available in Planner. Learn more about how to use the Project Power App to import projects from Microsoft Project for Windows desktop: Move your project from Project desktop to Project Power Apps - Microsoft Support Users are not able to pin Portfolios as a Teams tab What you need to do to prepare: This retirement will happen automatically by the specified dates with no admin action required before or after the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users and update any internal documentation to reflect these changes. Migrate existing Roadmap data to Portfolios in Planner before the redirect rollout date. Inform your users to proactively re-pin your Projects in Teams tabs using the Planner in Teams tabs Start using Planner in your organization today to minimize disruption when the redirect is rolled out Supporting adoption resources: The new Microsoft Planner MC1068901 — The New Microsoft Planner for the web will be generally available (DoD) Microsoft 365 Roadmap ID 490569 Coming soon: The new Microsoft Planner for the web brings together the simplicity of Microsoft To Do and the collaboration of Planner, into a simple, scalable solution, whether users are managing individual tasks or collaborative projects. In this rollout, we will update the existing web version of Planner to the new Planner for the web. A Microsoft 365 license is required to use the new Planner. Planner Premium will not be available. When this will happen: General Availability (DoD): We will begin rolling out late July 2025 and expect to complete by late August 2025. How this will affect your organization: The new Planner for the web: As part of our efforts to simplify Planner, these existing features are not available in the new Planner due to low usage: Charts for pinned plans in Planner Hub While you were away notifications Activity log of a task’s creation, assignments, and completion date in the task comments Links to group members, Microsoft Outlook conversations, and Microsoft OneNote notebooks (you can still access these links in Outlook) Menu option to Leave plan Suggested attachments Charts view and Schedule view on the Assigned to me page What you need to do to prepare: The new Planner is on by default for users with the required Microsoft 365 license. 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. Please review our public documentation and update any internal documentation. Learn more We will update Planner help documentation before rollout. Supporting adoption resources: The new Microsoft Planner Get ready for the new Microsoft Planner for the web Microsoft Viva MC973514 — (Updated) SharePoint Pages Flexible Sections Microsoft 365 Roadmap ID 395213 Updated May 7, 2025: We have updated the timeline below. Thank you for your patience. When this will happen: 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. 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 May 2025 (previously late April). 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. MC859867 — (Updated) Microsoft Viva Engage: Engage classic Highlights web part in SharePoint is retiring Updated: May 9, 2025: Last reminder for the deprecation - As previously communicated in our last Message Center post update, the classic version of the Highlights web part is being retired on June 1st, 2025. Kindly perform any required migrations before this deadline if your SharePoint sites use the deprecated web part. Additionally, based on customer feedback, we've now provided a script that helps admins identify the SharePoint sites in your tenant that have the deprecated Highlights web part. You can access the script in the same guide previously shared in this MC post - Migrate classic feeds in SharePoint to the Viva Engage Conversations web part | Microsoft Learn. Please note that after June 1st, users will no longer be able to access Viva Engage content through the classic Highlights web part. Please follow the instructions in this Message Center post to complete any required migrations at the earliest. We appreciate your cooperation in ensuring a smooth transition for your users. We will be retiring the Microsoft Viva Engage classic version of Highlights web part in SharePoint (referred to as the classic SharePoint web part in this message) on March 31, 2025 (previously January 31). Instead, we recommend migrating to the modern Viva Engage Conversations web part in SharePoint, where we will continue to invest our development resources. Note: The other two Viva Engage web parts (Highlights web part and Conversations web part) in SharePoint will not be impacted as part of this retirement. We recommend that tenants using classic SharePoint web part upgrade to the modern Conversations web part to enable a safer and more engaging user experience. How this will affect your organization: You are receiving this message because our reporting indicates one or more users in your organization are using the classic SharePoint web part. Starting March 31, 2025 (previously January 31), users in your Viva Engage network will no longer be able to successfully access Viva Engage content through this integration. Please use this guide to migrate to the modern version before March 31, 2025 (previously January 31): Migrate classic feeds in SharePoint to the Viva Engage Conversations web part | Microsoft Learn What you need to do to prepare: We recommend that you migrate to the modern Conversations web part, notify your users about this change and update documentation as appropriate. Microsoft Teams MC1087565 — Microsoft Teams: LEAP will transition to Microsoft Unified On July 1, 2025, the Microsoft 365 Live Event Assistance Program (LEAP) will transition from a complimentary preview offer to a paid service provided by Microsoft Unified that will be known as Teams Events Hosting Assistance. We are also pleased to inform you that we will be expanding our services to include Microsoft Teams Events Advanced Production Services, which will provide production and broadcasting services for town halls, webinars, and events. To learn more and benefit from these services, please contact your account management team. We are committed to ensuring that your transition is smooth and successful. MC1085581 — Microsoft Teams admin center: New Teams Reader role We’re excited to announce the rollout of a new built-in role-based access control (RBAC) role in the Microsoft Teams admin center called Teams Reader. This role is designed to provide read-only access across all* pages in the Teams admin center, enabling secure visibility without the risk of unintended changes. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early June 2025 and expect to complete by late June 2025. General Availability (GCC High, DoD): We will begin rolling out early July 2025 and expect to complete by late July 2025. How this will affect your organization: The new Teams Reader role is ideal for scenarios where visibility into Teams admin settings is required without granting edit permissions. The new role can read everything* that the Teams admin can manage but not update anything. *Role limitations No access to view Teams management (will be added soon; we will update this post when available) No access to Meetings & Calls details of users (will be added soon; we will update this post when available) No access to Notifications & Rules management (will be added soon; we will update this post when available) No access to Frontline worker deployment management No access to the Collaboration activity dashboard Global admins can perform assign/unassign operations for the new RBAC role from the Microsoft Entra admin center or Microsoft 365 admin center. This new role will be available to be assigned to Administrative units as well from the Entra admin center or the Microsoft 365 admin center. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. Notify your Global admins about the availability of this new role. Update internal documentation and training materials to reflect the new role and its capabilities. Learn more: Use Microsoft Teams administrator roles to manage Teams - Microsoft Teams | Microsoft Learn (will be updated before rollout) MC1084033 — Microsoft Teams Townhall in DoD (Premium) Microsoft 365 Roadmap ID 489812 Ability to host Teams townhall coming soon. When this will happen: General Availability (DoD): We will begin rolling out late June 2025 and expect to complete early September 2025. How this will affect your organization: Once available, set up and host large scale events across a DoD organization with the familiar Teams app you use for meetings using town hall. Town hall capabilities include a new meeting template, capacity for up to 20k attendees, green room, the ability to manage what attendees see, RTMP-in, live translated captions, and more. What you need to do to prepare: You may consider updating your training and documentation as appropriate. MC1084032 — Microsoft Teams: Users can add multiple emoji reactions to each chat or channel message Microsoft 365 Roadmap ID 491468 In Microsoft Teams, users will soon be able to add multiple emoji reactions to a single message. Before this rollout, each user can only add one emoji to each chat or channel post. After this rollout, users can select and add multiple emojis—including custom emojis—to the same 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: Targeted Release: We will begin rolling out early June 2025 and expect to complete by mid-June 2025. General Availability (Worldwide): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (GCC, GCC High): We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (DoD): We will begin rolling out early August 2025 and expect to complete by mid-August 2025. How this will affect your organization: After this rollout, a user who adds an emoji to a message will find a new More reactions button where the user can select and add additional emojis: Reactions are displayed in order of popularity, while ensuring that each user’s own reactions are always visible. To maintain clarity and prevent clutter, emojis are limited to 20 reactions per user per message: When there are too many reactions to show, users can hover over the number (+6 in this image) to see all reactions: What you need to do to prepare: This feature will be enabled by default and the rollout will happen automatically by the specified dates with no admin action required before the rollout. We recommend these steps: Inform users of the updated behavior to avoid confusion when they notice multiple reactions per message. If your organization uses custom emojis, note that custom emojis are supported as part of this feature. No changes to current admin settings or messaging policies are required. Learn more: Send an emoji, GIF, or sticker in Microsoft Teams - Microsoft Support (will be updated before rollout) MC1080690 — Microsoft Teams: New bilateral chat policy for restricting external group chats to a maximum of two organizations Microsoft 365 Roadmap ID 490566 Bilateral chat policy is a new type of policy for restricting external group chats in Microsoft Teams to maximum of two organizations. This policy will be available for admins to set up and apply to users and groups where external access policies are already set up. After the policy is enabled, automatically enforced compliance controls will prohibit users from creating or adding users from more than two organizations to external group chats. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams on the web, and Teams for iOS/Android. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early June 2025 and expect to complete by late June 2025. How this will affect your organization: Admins will be able to set up bilateral chat policy in the Teams admin center or Microsoft PowerShell. Learn more: Set up a bilateral chat policy - Microsoft Teams | Microsoft Learn After external access and the bilateral chat policy is set up, users with the policy can be in external group chats only with a maximum of two organizations. The user is also removed from existing external group chats with more than two organizations. This policy doesn't apply to meetings, meeting chats, or channels. This policy is available by default for admins to configure. Adding user to an external group chat that violates bilateral chat policy: Creating an external group chat that violates bilateral chat policy: What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. To set up a bilateral chat policy, you must first set up and enable external access. Learn more: Set up a bilateral chat policy - Microsoft Teams | Microsoft Learn MC1077865 — Microsoft Teams: Introducing the Network Strength Indicator Microsoft 365 Roadmap ID 414513 To improve meeting clarity and reduce confusion caused by connectivity issues, we’re adding a new Network Strength Indicator. When this will happen: Targeted Release: We will begin rolling out early July 2025 and expect to complete by late July 2025. General Availability (Worldwide, GCC): We will begin rolling out early August 2025 and expect to complete by early September 2025. How this will affect your organization: This feature will display your current network quality using a simple 3-bar system: Good (3 bars), Poor (2 bars), and Bad (1 bar). When your connection is limited, we’ll suggest actions to help conserve bandwidth and maintain meeting performance. You’ll also be able to see when other participants are experiencing poor or bad network conditions, providing better context for disruptions in the meeting. What you need to do to prepare: You may consider updating your training and documentation as appropriate. MC1075916 — Microsoft Teams: Set New Ringtones in Teams Mobile Microsoft 365 Roadmap ID 491438 Microsoft Teams Mobile (iOS and Android) will soon allow users to customize and select different sounds for various types of calls, helping you better manage your alerts and distinguish between different incoming communications. For users with Microsoft Teams Phone, this also includes calls for forwarded and delegated calls. Users can find these settings under Teams Settings > Calling > Choose a ringtone. The ringtone is set on a per-device basis, meaning the ringtone a user selects will apply only to that specific device. This also includes support for a new tone, “Beep” which will play a beep sound every 5 seconds for the duration of the call ringing. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early June 2025 and expect to complete by mid-June 2025. How this will affect your organization: Users can now set new ringtones for their calls within the call Settings. What you need to do to prepare: You may consider updating your training and documentation as appropriate. MC1075913 — Call Waiting Beep Enabled on Desktop and Mobile Microsoft 365 Roadmap ID 491472 Call Waiting Beep is a phone feature that provides a less intrusive tone when a user is in a call and a second call comes in to let the user know there is an incoming call when they are busy. A beep tone will play every 5 seconds for the duration of an incoming call ringing. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early June 2025 and expect to complete by mid-June 2025. How this will affect your organization: To enable this experience on Desktop, users must turn on the Setting within the Teams Settings > Notifications and activity > Play sounds while I’m busy or in a meeting. On Teams Mobile app client, Call Waiting Beep is the default experience. When a user is in a Teams Call and is receiving a second incoming call, they will receive this functionality. Call Waiting Beep will be supported on IOS and Android devices. What you need to do to prepare: You may consider updating your training and documentation as appropriate. MC1070855 — Microsoft Teams: Call quality reports for Bring Your Own Device (BYOD) rooms in the Pro Management portal Microsoft 365 Roadmap ID 486830 As with Microsoft Teams Rooms, admins can now access detailed call quality reports for BYOD rooms with associated peripherals in the Pro Management portal. These reports include call history and session details that help diagnose network, audio, and video issues. Reports in the Pro Management portal requires a Teams Shared Devices license for the room. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out in early June 2025 and expect to complete in mid-June 2025 How this will affect your organization: This report can be used to understand when call quality is poor in rooms, as well as analyze the cause of that poor quality. Diagnosing issues with call quality can lead to substantive increases in meeting room experience for your users as well as a reduction in tickets and/or complaints about meeting rooms. What you need to do to prepare: We recommend that you discuss this new capability with your room management teams and plan for how to use the new quality reports to best serve your users and improve their experience in Teams Rooms. This report can be used to understand when call quality is poor in rooms, as well as analyze the cause of that poor quality. We also recommend a regularly scheduled frequent check of room health to ensure your team is on top of any issues before they turn into tickets or complaints from users or executives. You can be both proactive and reactive to room issues in this way. MC1070854 — Microsoft Teams: Unified attachment flow on Teams Mobile Microsoft 365 Roadmap ID 488091 Introducing a new content picker for Teams Mobile Android. Attach any type of content, whether files or media, from the paperclip icon in the compose overflow menu. Our unified attach flow makes it easy and intuitive to attach content from any source location. When this will happen: General Availability (Worldwide): We will begin rolling out on Android early June 2025 and expect to complete by late June 2025. General Availability (GCC, GCC High, DoD) We will begin rollout on Android late June 2025 and expect to complete by early July 2025 How this will affect your organization: Users will see an improved content attach flow in the Teams Android app. 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. MC1069562 — Microsoft Teams: Block a user from your organization (GCC High, DoD) Microsoft 365 Roadmap ID 489455 The delete API (removeallaccessforuser API) does not stop a malicious user from resending a Microsoft Teams message to the same victim. To help prevent this, we will roll out a block user feature in the Microsoft Teams admin center that will allow the admin to block the malicious user from sending a new message. We will use a feature similar to the allow/block list in federation identity credentials to block the malicious user from the entire organization. When this will happen: General Availability (GCC High, DoD): We will begin rolling out late June 2025 and expect to complete by late June 2025. How this will affect your organization: After this rollout, admins can set up a list of users who are blocked from collaborating with their organization. If a user is added to the block list, the users in the organization will not be able to have 1:1 and group chats with the blocked users. If chats already exist before a user is added to the block list, the blocked user will be removed from the chat. This feature will be off by default. If you wish to use this feature, go to the Microsoft Teams admin center > Users > External access to turn on this feature and add users to the block list. Turning on block user: Adding users to block list: The finalized block list: What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. Learn more: The Block external users section of IT Admins - Manage external meetings and chat with people and organizations using Microsoft identities - Microsoft Teams | Microsoft Learn MC1069556 — (Updated) Microsoft Planner: New Planner app for Microsoft Teams will be generally available (GCCH, DoD) Microsoft 365 Roadmap ID 490568 Updated May 30, 2025: We have updated the timeline below. Thank you for your patience. Coming soon: The new Microsoft Planner app for Microsoft Teams is a single, unified work management experience that brings together the simplicity of Microsoft To Do and the collaboration of Planner into a single, simple solution that offers individual task management and enterprise work management. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. Planner Basic is available to all customers with a Microsoft 365 license. Premium features in Planner require a Planner Premium license. Planner Premium will be available in GCCH but not DoD. When this will happen: General Availability (GCC High): We will begin rolling out early July 2025 and expect to complete by late July 2025. General Availability (DoD): We will begin rolling out late August 2025 and expect to complete by late September 2025. How this will affect your organization: This rollout includes transforming the existing Tasks by Planner app and the To Do app in Teams into the new Planner app, which will maintain all existing app functionality and add new options and features to help users be more productive. How this will affect your organization: We will update the app name for the Tasks by Planner app and the To Do app in Teams to Planner. If your organization does not have a Microsoft 365 license, users must use the To Do app to create new lists. If your organization purchases at least one Microsoft 365 license, users can access the full functionality of Planner. For GCC High only, Planner in Teams will maintain all existing functionality of the Tasks app while adding support to access all plans created in Microsoft Project for the web and capabilities of Project for the web. The new Planner app for Teams: These capabilities will not be available as part of the initial rollout. We will announce the timeline for the availability of these features in a future Message Center post: Microsoft Copilot for Microsoft 365 in Planner Tasks in Premium Plans appearing in the Assigned to me view in My Tasks This update is 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. Please review the public documentation and update any internal documentation to reflect the new Planner app. Learn more The new Microsoft Planner: A unified experience bringing together to-dos, tasks, plans and projects | Microsoft Community Hub Manage the Planner app for your organization in Microsoft Teams MC1069555 — (Updated) Microsoft Teams: Send messages to attendees in the meeting lobby with Lobby chat Microsoft 365 Roadmap ID 480716 Updated May 30, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams: Meeting organizers will be able to send one-way messages to attendees in the meeting lobby using the Lobby chat. The Lobby chat is intended to optimize the lobby experience for all participants, ensuring that organizers are better equipped to run external meetings and external attendees are well informed about the meeting when it begins. This feature is on by default and admins can choose to disable it in the Teams admin center (TAC). This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams for iOS/Android. When this will happen: Targeted Release: We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late June 2025 and expect to complete by mid-July 2025. How this will affect your organization: Admin controls: After this rollout, the policy for Lobby chat will be on by default in the TAC. Admins can enable or disable Lobby chat with a meeting policy in the TAC. Under Meeting policies > Global (Org-wide default) > Meeting engagement, admins will find a new toggle option for Organizers can chat with lobby participant. When the option is enabled, participants who can't bypass the lobby due to meeting policy will be able to view messages sent by the organizer in a Lobby chat. To enable this policy, Meeting chat in the TAC must be set to On for everyone or On for everyone but anonymous users. Meeting organizer experience: When someone joins the lobby, the meeting organizer will see a new Lobby tab in their Chat experience (meeting chat, one-on-one chat, or group chats). The meeting organizer will be able to send one-way messages to attendees in the lobby in the Lobby tab: Lobby attendee experience: When the meeting organizer sends a message to the lobby, a new Lobby chat panel will open in the right panel of the pre-join screen and display the message. Lobby attendees cannot reply to these messages: 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. For tenants where Meeting chat in the TAC is set to On for everyone or On for everyone but anonymous users, admins should assess the impact of the Lobby chat feature and update meeting policy settings as needed to suit their organization's requirements. MC1068906 — (Updated) Microsoft Teams: Microsoft 365 Copilot for phone without transcription Microsoft 365 Roadmap ID 482745 Updated May 30, 2025: We have updated the timeline below. Thank you for your patience. We are releasing a new feature that enables users to leverage Copilot's capabilities during live call sessions without retaining transcripts or an audio recording afterward. This ensures that users can benefit from Copilot during sensitive conversations where a persistent record is not desired. Post-call Copilot functions, such as recap, will not be available after the call concludes. When this will happen: Targeted release: We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. How this will affect your organization: Users who have transcription turned off will be now able to use Copilot. What you need to do to prepare: Admin settings will be made available as part of the Calling policy to allow admins to configure the setting for their users. More details to follow. MC1066937 — New Queues app service plan (Teams Premium) Microsoft 365 Roadmap ID 490056 Microsoft Teams: Your Office 365 subscription is being updated with a new service plan: Queues app for Microsoft Teams. Powered by Teams Phone, the Queues app enables team members to make and receive customer calls without having to leave Teams, with tailored experiences for users and leads that are designed for efficiency in call handling and resolution. How this will affect your organization Once we begin rolling out the new service plan (mid-June 2025), Queues app will be listed as a service plan under the Teams Premium license. This is to prepare for the GCCH and DOD release of the New Voice Applications Settings for Authorized Users for Microsoft Teams (early July 2025). The rollout plan outlining the availability of the New Voice Applications Settings for Authorized Users will be communicated via the Message Center and the roadmap. What you need to do to prepare You may consider updating your training and documentation as appropriate. Admins: Manage voice applications policies in Microsoft Teams - Microsoft Teams | Microsoft Learn MC1066157 — Microsoft Teams: Android Open Source Project (AOSP) - Device Management auto updates Android devices with Microsoft Teams will be commencing auto updates for firmware in order to migrate to Microsoft Intune Android Open Source Project (AOSP) device management. Unlike other firmware updates, these firmware updates cannot be paused. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out mid-May 2025 and expect to complete by late August 2025. How this will affect your organization: Devices will receive the firmware auto updates following the phases set in Teams admin center: Validation: 0-15 days General: 16-45 days (default) Final: 45-60 days What you need to do to prepare: Please verify that all prerequisites for AOSP device management migration are completed for your organization to ensure a smooth process. Your devices may sign out during migration if the prerequisites are not carried out properly. Please see the blog for further details and the full schedule of auto updates for your devices: Moving Teams Android Devices to AOSP Device Management. There will be no exceptions to delay the auto updates further. MC1062452 — (Updated) Microsoft Teams: Join as attendees in Microsoft events from Teams Rooms on Windows Microsoft 365 Roadmap ID 484125 Updated May 16, 2025: We have updated the timeline below. Thank you for your patience. Microsoft Teams Rooms on Windows can now join Microsoft events (webinars, town halls, structured meetings) as attendees. You can attend directly from the invited Teams Room with the same features that attendees have for all events. This is available only in Teams Rooms Pro. When this will happen: General Availability (Worldwide): We will begin rolling out late May 2025 (previously mid-May) and expect to complete by late May 2025. General Availability (GCC): We will begin rolling out late May 2025 and expect to complete by mid-June 2025. General Availability (GCC High): We will begin rolling out late June 2025 and expect to complete by mid-July 2025. General Availability (DoD): We plan begin rolling out late August 2025 and expect to complete by mid-September 2025. How this will affect your organization: Recently we announced official support with Teams Rooms on Windows devices as a presenter in Teams Townhall & Webinars ensuring an optimal experience for every event. Starting from app version 5.2.115.0, Teams Town halls and Webinars are exclusively available in rooms with a Teams Rooms Pro license. Today, Teams Rooms on Windows with a Pro license can now join events as attendees, making it easier to schedule watch parties for your organization and enjoy an official supported experience. Please note that joining events from Teams Rooms with a non-Pro license will not be supported. This feature will be enabled 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. MC1059675 — (Updated) Microsoft Teams: Pop out live captions and Real-Time Text (RTT) in Teams meetings Microsoft 365 Roadmap ID 484113 Updated May 15, 2025: We have updated the timeline below. Thank you for your patience. We’re introducing the ability to pop out live captions (including live translated captions) and Real-Time Text (RTT) in Microsoft Teams meetings and calls. This new functionality gives users more flexibility and control over how they view text-based communication during meetings, supporting both accessibility and multitasking needs. When this will happen: Targeted Release: We will begin rolling out mid-June 2025 (previously early May) and expect to complete by late June 2025 (previously mid-May). General Availability (Worldwide, GCC): We will begin rolling out late June 2025 (previously early May) and expect to complete by mid-July 2025 (previously mid-May). General Availability (GCCH): We will begin rolling out mid-July 2025 (previously early June) and expect to complete by late July 2025 (previously mid-June). General Availability (DoD): We will begin rolling out early August 2025 (previously early July) and expect to complete by mid-August 2025 (previously mid-July). How this will affect your organization: After the rollout, users will see a pop-out icon on the live captions and RTT interface during meetings and calls. This feature will be on by default. When popped out, captions and RTT will open in separate windows that users can drag, resize, and position anywhere on their screen. This allows users to customize their meeting layout and view captions or RTT in a way that works best for their workflow or accessibility needs. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required. Please notify your users about this change and update any relevant training materials or documentation to reflect the new pop-out experience for captions and RTT. MC1059674 — (Updated) Microsoft Teams: Real-Time Text (RTT) in Teams meetings and calls Microsoft 365 Roadmap ID 484119 We’re introducing Real-Time Text (RTT) support in Microsoft Teams meetings and calls, available on both desktop and mobile platforms. RTT is an accessible communication method that transmits text character by character as it is typed, enabling more immediate and responsive text-based conversations. This enhancement supports inclusivity by providing an alternative communication channel for users who are deaf or hard of hearing, neurodiverse, or have speech-related disabilities. When this will happen: Targeted Release: We will begin rolling out early May and expect to complete by mid-May. General Availability (Worldwide, GCC): We will begin rolling out early May and expect to complete by mid-May. General Availability (GCCH): We will begin rolling out early June and expect to complete by mid-June. General Availability (DoD): We will begin rolling out early July and expect to complete by mid-July. How this will affect your organization: Once this feature is enabled by your organization, users will be able to turn on Real-Time Text (RTT) during Teams meetings and calls. To access it, go to the meeting toolbar, select More > Speech and language > Enable RTT. When RTT is turned on, it will be enabled for everyone in the meeting. As you type, your message will instantly appear on the screen - letter by letter - so others can read it in real time. This creates a faster and more natural way to communicate through text, especially compared to standard chat. RTT is designed to improve accessibility and also supports users who prefer typing instead of speaking. It can be used together with other features like captions or chat to create a more inclusive and flexible meeting experience. Note: Once RTT is turned on in a meeting, it stays on for the rest of the meeting and cannot be turned off unless everyone leaves and rejoins. What you need to do to prepare: This rollout will happen automatically, and no admin action is required. The RTT policy is enabled by default at the tenant level. We recommend informing your users about this new feature, especially those who may benefit from enhanced accessibility options. You may also want to update any internal documentation or training materials to include guidance on how to use RTT in Teams meetings and calls. MC1059673 — Microsoft Teams: Expanded and enhanced peripheral auto-association support for Bring Your Own Device (BYOD) spaces Microsoft 365 Roadmap ID 486693 Updated June 3, 2025: Included additional details for feature capabilities Additional room and desk peripherals, including docking stations and webcams, are supported in BYOD spaces (including bookable desks), enabling users to seamlessly connect and utilize audio and video peripherals for a better experience. Admins get an expanded view and insightful reports for peripherals associated with Bring Your Own Device (BYOD) spaces in the Pro Management portal. When this will happen: Targeted Release: We will begin rolling out early June 2025 and expect to complete in mid-June 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: Docking stations and webcams will now begin to appear in the Pro Management portal inventory device page, crowdsourced from the Teams desktop app. These peripherals can then be manually or automatically associated to BYOD rooms or bookable desks to automate and improve BYOD/Desk UX and provide admin insights into room UX quality. BYOD auto association will begin to receive signals and auto-associate these new peripherals to BYOD rooms. This process automatically builds a full view of your inventory for you, including what peripherals are currently located in which BYOD rooms. Auto-association for desks is coming soon. As a result, BYOD and Bookable Desks end user experiences will automatically activate for any user who plugs in a peripheral associated to a BYOD room or desk. These user experiences are designed to adapt the Teams desktop client to solve common user issues in rooms and desks, and includes but is not limited to the following features: (Rooms) Auto-select Room AV peripherals so that users don't accidentally use their laptop speaker and mic in a meeting room. (Rooms) Shared display mode to protect confidential information and present clean output without meeting controls or presenter's notes to the room display. (Rooms) Speaker Attribution so transcript (and Microsoft 365 Copilot) know who is speaking in your meeting. (Rooms) Disable voice isolation so others in the room can be heard. (Rooms) Room Node in participant roster. (Desks) Auto-book a desk upon peripheral plug in. (Desks) Automatically update user's work location if user has consented (Desks) Notification if a seat is taken (Rooms & Desks) Usage Reports What you need to do to prepare: Inform your users about the experiences that will be automatically activated for them when they plug in to a peripheral that has been associated to a room or a desk. These changes are to make their meeting room and desk experiences better. If you do not want end user experiences to automatically activate for a user, please refer to the admin documentation for BYOD rooms or desks. If you do not want peripherals to auto associate to rooms, automatically building your inventory for you, please disable this in settings for the Pro management portal. MC1057717 — (Updated) Microsoft Teams Phones: Users can assign shared lines, call queues, and call transfer key to line keys Microsoft 365 Roadmap ID 486829 Updated June 2, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams Phone devices: We are excited to announce the upcoming availability of shared line, collaborative delegation, call queues and call transfers on line keys on Teams certified phone devices. Line keys on phone devices address the pain point of navigating through multiple menus to manager calls, offering enhanced call management where users can manage multiple calls effectively, increased productivity and improved user experience. For shared line and collaborative delegation, this feature will enable you to assign shared lines/collaborative delegation lines to a line key and view the boss/delegates and members of the group (in case of collaborative delegation) along with their presence on Teams Phone devices. This feature allows delegates to pick up calls on behalf of the boss or members of the group (in case of collaborative delegation) by pressing the line key and join active calls. Also, users will be able to assign the transfer action to the line key, enabling them to transfer active calls to specific contacts by pressing that line key. Lastly, after assigning call queues to the line key users can view the status of call queue whether busy or available and receive calls by pressing line key. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late May 2025 (previously mid-May) and expect to complete by late June 2025 (previously late May). General Availability (GCC High, DoD): We will begin rolling out late June 2025 (previously mid-June) and expect to complete by late July 2025 (previously late June). How this will affect your organization: This change will be on 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. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. To access the new features, ensure that your Teams phone devices are updated with the latest application. These features will only be available with the latest application update. Learn more: Set up line keys on your Microsoft Teams phone - Microsoft Support Before rollout, we will update this post with new documentation. MC1056268 — (Updated) Microsoft Teams Premium: Ultra-low latency (ULL) attendee experience for town halls Microsoft 365 Roadmap ID 486535 Updated May 29, 2025: We have updated the content. Thank you for your patience. Before this rollout, Microsoft Teams town hall attendees typically watch the presentation with a 20-30 second delay. After this rollout, with ultra-low latency (ULL), attendees will be able to view and participate in a town hall at a much lower latency than before, ensuring they are in sync with content being shared by presenters and organizers. This feature is available for town hall organizers with a Teams Premium license. This feature will only be available for tenants who use the Microsoft eCDN (Enterprise Content Delivery Network) or who do not have an eCDN provider. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS and Android. When this will happen: Targeted Release: We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (Worldwide): We will begin rolling out early August 2025 and expect to complete by mid-August 2025. General Availability (GCC): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. How this will affect your organization: This change will be on by default for attendees in town halls scheduled by Teams Premium organizers. What you need to do to prepare: This rollout will happen automatically by the specified dates 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 new documentation. MC1052166 — (Updated) Microsoft Teams: Slide Control for PowerPoint presenters Microsoft 365 Roadmap ID 484844 Updated May 13, 2025: We have updated the timeline below. Thank you for your patience. A new Slide Control feature allows presenters in both meetings and events to share control of their Microsoft PowerPoint presentations. Users with control will be able to move the slides forward and backward for all users in the meeting, making it easy for each speaker to directly control their content. When this will happen: Targeted Release: We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (Worldwide): We will begin rolling out late July 2025 and expect to complete by early August 2025. General Availability (GCC): We will begin rolling out late July 2025 and expect to complete by mid-August 2025. General Availability (GCC High): We will begin rolling out mid-August 2025 and expect to complete by late August 2025. General Availability (DoD): We will begin rolling out early September 2025 and expect to complete by mid-September 2025. How this will affect your organization: On release, Slide Control will be enabled for all internal users in the tenant and disabled for all external users. What you need to do to prepare: Before release, decide what feature scope you'd like to apply within your tenant, meaning which type of users are allowed to use the new Slide Control feature. Note: Slide Control only allows for presenters to share control of their slides with the users they choose; users cannot request control themselves. MC1052162 — Microsoft Teams: Now available - new policy setting for Speaker Attribution in BYOD scenarios - Enabled ON by default Microsoft 365 Roadmap ID 488301 Updated April 29, 2025: We have updated the title, timeline, and content. Thank you for your patience. Available now: The new SpeakerAttributionBYOD setting is now available in csTeamsAIPolicy for Microsoft Teams Premium users. This gives IT admins more control over speaker attribution when users join meetings from personal (BYOD) devices. Admins can now configure this setting using PowerShell. If no action is taken, it will be enabled by default starting in early June 2025. NOTE: If you are a Microsoft Teams customer (not a Microsoft Teams Premium customer), we are sending this message to you because this new setting will take effect automatically for any user assigned a Microsoft Teams Premium or Microsoft 365 Copilot license—even if your organization previously didn’t have these licenses. Therefore, we recommend all organizations review this message, regardless of your organization’s current license status. This setting allows organizations to manage how speaker attribution is used in meetings where users join via personal devices, helping enhance the in-meeting and post-meeting experience with features like speaker labels (Speaker 1, Speaker 2, etc.) and Microsoft 365 Copilot in shared spaces. To access Copilot features, a Microsoft 365 Copilot license is required. This message applies to Teams for Windows desktop and Teams for Mac desktop. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. How this will affect your organization: Previously, speaker attribution was managed using the RoomAttributeUserOverrideparameter in CsTeamsMeetingPolicy. Going forward, SpeakerAttributionBYOD in csTeamsAIPolicy will determine whether attribution is used when users join from BYOD scenarios. What you need to do to prepare: The new setting is available now, and admins can begin configuring it using PowerShell based on their organization's preferences. If no action is taken, the setting will be enabled by default during the rollout in June 2025. If you prefer to modify the setting before the rollout begins, you can do so at any time starting now. Learn more Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn MC1045219 — (Updated) Microsoft Teams: Room Recommender Microsoft 365 Roadmap ID 482191 Updated May 28, 2025: We have updated the timeline below. Thank you for your patience. With this rollout, if no room is booked for the meeting, an AI-generated room suggestion will be sent in the meeting chat an hour before the meeting start time when two or more attendees are co-located in the same building, making in-person collaboration easier. The room suggestion will consider location of participants, room availability, and capacity to find the best space. You can reserve the suggested room with just one click and update the invite for everyone. The organizer must have a Teams premium license for this experience to occur, which is on Teams mobile on iOS. #MicrosoftPlaces When this will happen: General Availability (Worldwide): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. How this will affect your organization: This will be a default on feature. For a room suggestion to be generated, a meeting must have: Between two to seven attendees with at least two attendees that are co-located Teams meeting link Organizer has Teams premium No room is already booked for the meeting No external attendees Not an all-day event Room suggestions will be generated in buildings where at least two attendees, who haven’t declined the meeting, share the same work location. For instance, if a meeting has four attendees, with two in Building X and two in Building Y, suggestions for both buildings will be sent. Distribution lists are not considered. If a meeting is moved, canceled, or the suggested room becomes unavailable, the card will update dynamically upon clicking ‘Reserve’. 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 team about this change and update any relevant documentation. We recommend making sure that your rooms are properly added to Places directory with a building associated. MC1045217 — (Updated) Microsoft Teams Phone: Copilot-generated summaries for call transfers on Android devices Microsoft 365 Roadmap ID 475855 Updated June 2, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams Phone on Android devices: Copilot-generated summaries for call transfer. This feature is designed to streamline call transfers by providing agents receiving transferred calls with a Copilot summary of the call. This summary includes key details such as caller information, call reason, prior actions, and next steps. It supports Consult and Blind transfers to help ensure effective communication and improve efficiency. A Microsoft 365 Copilot license is required to use this feature. Learn more: License options for Microsoft 365 Copilot | Microsoft Learn When is this rolling out General Availability (Worldwide, GCC): We will begin rolling out late May 2025 (previously mid-May) and expect to complete by late June 2025 (previously late May). How this will affect your organization: Copilot-generated summaries for call transfer are visible to the person to whom the call is being transferred: These new features will be available by default. What do I need to prepare Please ensure that your Teams phone devices are updated with the latest application to get access to the new features described in this message. These features will be available only with the latest application update. Prerequisite to use these new features: Admins must enable Transcription in Calling policies for both transferor and transferee. This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. MC1045213 — (Updated) Microsoft Teams: New Chat and channels experience (GCC High, DoD) Microsoft 365 Roadmap ID 485706 Updated May 21, 2025: We have updated the timeline below. Thank you for your patience. The new, streamlined chat and channels experience makes it easier to stay on top of what matters most and organize your digital workspace. Catch up on chat, channels and teams in one place, create custom sections to organize conversations by topics, use filters to triage messages and more. 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, Teams on Mac desktops, Teams on the web, and Teams on 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: General Availability (GCC High): We will begin rolling out mid-July 2025 (was mid-June) and expect to complete by late July 2025. (was early July) General Availability (DoD): We will begin rolling out late July 2025 (was late June) and expect to complete by early August 2025. (was mid-July). 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. A quick navigation bar for teams and channels is 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. Use /goto: 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. About a week after the new experience is available for a user, they will be presented with a final Get started screen and transition to the new experience. 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 are available on the adoption web page. MC1041960 — (Updated) Microsoft Teams: Standard and Basic licensed Teams rooms on Windows in the Teams admin center portal Microsoft 365 Roadmap ID 482539 Updated May 15, 2025: We have updated the timeline below. Thank you for your patience. We will be transitioning all Teams Rooms on Windows devices, irrespective of their licenses, to the Teams Rooms Pro management portal to meet users' needs for a one-stop destination to configure, monitor, and manage Teams rooms devices. This change delivers a unified device management and admin portal experience. Users currently using the Teams admin center (TAC) will have device management functionalities within the Teams Rooms Pro Management portal. Teams Rooms on Windows devices will not be available in Teams admin center after June 1, 2025. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out late May 2025 (previously May 1) and expect to complete in late June 2025 (previously early May). How this will affect your organization: All Teams Rooms on Windows devices with Standard or Basic licenses will be visible in the Teams Rooms Pro management portal at https://portal.rooms.microsoft.com. Organizations that have never used the Teams Rooms Pro management portal will need to add additional URLs found in Enroll a Teams Room in the Pro management portal. Those with Teams or Teams Device administrator roles will be able to access the Teams Rooms Pro management portal and see their devices after May 1, 2025. Users with Basic and Standard Teams Rooms licenses will have device management functionalities within the Teams Rooms Pro Management portal. They will not, however, have access to the full suite of device management and space analytics features available with a Teams Rooms Pro license. What you need to do to prepare: For those that have used only Teams admin center and are unfamiliar with the capabilities of Teams Rooms Pro Management, we encourage you to view the short videos on Teams Rooms Pro Management - YouTube and product documentation Microsoft Teams Rooms Pro management. MC1041451 — (Updated) Microsoft Teams for iOS/Android: New location sharing settings for emergency calls and more Updated June 3, 2025: We have updated the timeline below. Thank you for your patience. This message applies to Microsoft Teams for iOS/Android. Microsoft is updating its policies regarding the sharing of user location data to enhance privacy, improve data security, and ensure compliance with evolving regulatory standards. To enhance transparency and user control, Teams will introduce a new location consent experience that gives users the choice of when and how Teams can use their location data [specifically, the SSID (service set identifier) and the BSSID (basic service set identifier)]. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early June 2025 (previously mid-May) and expect to complete by late May (previously early May). General Availability (GCC High, DoD): We will begin rolling out late May 2025 (previously early May) and expect to complete by mid-June 2025 (previously early June). How this will affect your organization: All new and existing Teams for Work users in your organization will be prompted to specify if they want to keep location detection on for emergency calls only or if they consent to allowing location access used for IT Admin Insights, for troubleshooting (with a tool such as the Call Quality Dashboard) or for Network and Location matching through BSSID for emergency calling location. NOTE: The new Teams location consent flow does not apply to fully managed devices where users are restricted from user-granted location access. You can expect current policies for managed devices to continue working as expected, and users will not receive the new location consent prompts. The new Teams location consent changes will impact these Teams features: Emergency calling Location-based routing Network and Location matching through BSSID Call Quality Dashboard This change will be available by default. All new Teams for Work users on iOS and Android will first be prompted to allow location permission at the operating system level. Existing Teams for Work users who previously accepted or denied location permission at the operating system level will not see this prompt a second time. If a user allows location access, dynamic emergency calling policies will work as configured, and users enabled for Location Based Routing will be able to make and receive PSTN calls. If a user disallows location access, several Teams Call Quality Dashboard metrics will be impacted, and Network and Location matching through BSSID from dynamic emergency calling policies will not work. Users can still manually add their physical address for emergency calls in the Teams Calls app if an admin has enabled ExternalLocationLookupMode for their users. Immediately after users consent to allow location access at the operating system level (and for users who previously consented to location access), both new and existing Teams for Work users will be prompted to allow location access at the Teams app level. At the Teams level, users must choose between Allow all, which grants Teams full location access (that can be used for emergency calls, IT Admin Insights, or troubleshooting), or Allow emergency only, which restricts location usage to emergency calling. NOTE: Only users who are configured for a dynamic emergency calling policy through ExternalLocationLookUpMode will see this version of the dialog. Users without ExternalLocationLookUpMode enabled will see a slightly different version of this consent prompt that excludes emergency calling. Users can modify their location detection preferences at the operating system level or app level at any time in Teams Settings > Privacy > Location. On fully managed devices, these settings will be on by default and can only be disabled at the operating system level. What you need to do to prepare: We recommend that you educate your users on these selections and what works best for your tenant. If you regularly use the Call Quality Dashboard or leverage Network and Location matching through BSSID, you may want to recommend that users allow location access for those options, or user location data will no longer flow to these services. For emergency calling, you can communicate these changes by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that 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 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) Changes to API behavior for Wi-Fi access and location - Win32 apps | Microsoft Learn User location consent experience in Microsoft Teams - Microsoft Teams | Microsoft Learn For more detailed information and how this will affect each user in your organization, please refer to the public documentation that will be updated here shortly. Before rollout, we will update this post with links to new documentation. This rollout will happen automatically by the specified dates 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. MC1028320 — (Updated) Microsoft Teams: Teams Rooms Pro Management portal will be generally available (GCC High) Microsoft 365 Roadmap ID 482187 Updated May 16, 2025: We have updated the timeline below. Thank you for your patience. March 27, 2025: We have updated the URL below to show as intended. Thank you for your feedback. NOTE: This message applies to customers with Microsoft Teams Rooms Pro licenses. If you don't have this license, you can ignore this message. After this rollout, admins will have access to the Teams Rooms Pro Management service and portal at https://devices.gov.teams.microsoft.us,where you can use remote device management and analytics features while maintaining high security and privacy standards. When this will happen: General Availability (GCC High): We will begin rolling out late May 2025 (previously early May) and expect to complete by late June 2025 (previously mid-May). How this will affect your organization: This portal will be available by default for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. Learn more: Microsoft Teams Rooms Pro management - Microsoft Teams | Microsoft Learn (will be updated before rollout begins) MC1020218 — (Updated) Microsoft Viva Connections: New News feature in Microsoft Teams Microsoft 365 Roadmap ID 472018 Updated May 20, 2025: The rollout of the feature on Viva Connections in Teams mobile will now be completed by end June 2025. The feature is generally available on Viva Connections in Teams desktop and Teams web platforms. 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 June 2025 (previously late May). 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. 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. MC1019312 — (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions Microsoft 365 Roadmap ID 89975 Updated May 23, 2025: We have updated the timeline below. Thank you for your patience. 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 July 2025 and expect to complete by mid-July 2025. General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-July 2025 and expect to complete by late July 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. 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) MC1013461 — (Updated) Microsoft Teams: Customize the location of notifications in Teams for the web Microsoft 365 Roadmap ID 480720 Updated May 12, 2025: We have updated the timeline below. Thank you for your patience. 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 May 2025 (previously late April). 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) MC1011152 — (Updated) Microsoft Teams: Updates to the Teams system tray icon and menu Updated May 7, 2025: We have updated the timeline below. Thank you for your patience. 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 May 2025 (previously late April). 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 Open option 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 May 16, 2025: We have updated the 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 mid-May 2025 (previously early May) and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (GCC): We will begin rolling out early June 2025 and expect to complete by late June 2025. General Availability (GCC High): We will begin rolling out early June and expect to complete by late June 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 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 — (Updated) Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails Microsoft 365 Roadmap ID 476488 Updated May 28, 2025: We have updated the timeline below. Thank you for your patience. 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 October 2025 and expect to complete by mid-October 2025. General Availability (Worldwide): We will begin rolling out early November 2025 and expect to complete by late November 2025. General Availability (GCC, GCC High): We will begin rolling out early December 2025 and expect to complete by early January 2026. 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 — (Updated) Microsoft Teams: Join town halls using dial-in options and join codes Microsoft 365 Roadmap ID 476489 Updated May 16, 2025: We have updated the timeline below. Thank you for your patience. April 11, 2025: There was an error previously published that we have corrected. Previously we mentioned that the Microsoft Teams town halls dial-in options would be available to attendees and presenters, and that it would appear as separate email invited. This is not correct. Presenters and Organizers can now, with this update, join a Teams town hall using the dial-in options and code displayed on the Event Scheduling page after publishing. This code should only be used for Organizers and Presenters, not attendees. Presenters and attendees can now join Microsoft Teams town halls using dial-in options and join codes. When this will happen: Targeted Release: We will begin rolling out mid-May 2025 (previously early May) and expect to complete by late May 2025 (previously mid-May). General Availability (Worldwide): We will begin rolling out late May 2025 (previously mid-May) and expect to complete by late May 2025. General Availability (GCC, GCC High): We will begin rolling out early June 2025 and expect to complete by late June 2025. How this will affect your organization: With the release of this feature, Teams town hall presenters and organizers may join a Town hall using the dial-in option. Teams town hall does not support dial-in Attendees at this time. 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. MC999443 — (Updated) Microsoft Teams: Queues app to add Monitor, Whisper, Barge, and Takeover Microsoft 365 Roadmap ID 473884 Updated May 15, 2025: We have updated the timeline below. Thank you for your patience. When this will happen: 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. 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 late May 2025 (previously early May). 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. MC996588 — (Updated) Microsoft Teams: Adding and editing external contacts on Teams phone devices Microsoft 365 Roadmap ID 476485 Updated June 2, 2025: We have updated the 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, GCC High): We will begin rolling out late May 2025 (previously mid-May) and expect to complete by late June 2025 (previously late May). 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. MC989975 — (Updated) Microsoft Teams: Occupancy status on Teams panels Microsoft 365 Roadmap ID 474441 Updated May 19, 2025: We have updated the content. Thank you for your patience. 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): We will begin rolling out late April 2025 (previously early April) and expect to complete by late May 2025 (previously late April). General Availability (GCC): We will begin rolling out early September 2025 and expect to complete by mid-September 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 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 — (Updated) Microsoft Teams: New microphone volume indicator for users Microsoft 365 Roadmap ID 468274 Updated June 2, 2025: We have updated the 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-June 2025 (previously mid-May). 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 MC974361 — (Updated) Microsoft Teams: Edit your display name in meetings Microsoft 365 Roadmap ID 122934 Updated June 2, 2025: We have updated the 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-June 2025 (previously mid-May). 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. MC973502 — (Updated) Microsoft Teams: New "Tag mentions" filter for the Activity feed Microsoft 365 Roadmap ID 470598 Updated May 12, 2025: We have updated the timeline below. Thank you for your patience. 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 May 2025 (previously late April). 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) MC966633 — (Updated) Microsoft Teams: Meeting recap can be shared as a link Microsoft 365 Roadmap ID 471430 Updated May 9, 2025: We have updated the timeline below. Thank you for your patience. Coming soon to Microsoft Teams: Meeting participants will be able to share a link to the Meeting recap from the meeting thumbnail in chat and the Recap tab, making it easier to reference and share Meeting recap insights with others. Meeting participants can share the meeting recap link with anyone in their organization. Users who don't have access to the recording or transcript must request access before they can access the Meeting recap. This message applies to Teams for Windows desktop and Teams for Mac desktop. 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): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (GCC High): We will begin rolling out late March 2025 and expect to complete 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. You may want to notify your users about this change and update any relevant documentation. Learn more: Meeting recap in Microsoft Teams - Microsoft Support (will be updated before rollout) MC956699 — (Updated) Microsoft Teams: Forward messages with app cards Microsoft 365 Roadmap ID 469506 Updated May 8, 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 late May 2025 (previously late April). 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. MC950898 — (Updated) Microsoft Teams: Forwarding loop components Microsoft 365 Roadmap ID 469507 Updated May 28, 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 DoD can safely disregard this message. 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): 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. MC942831 — (Updated) Microsoft Teams Phones: Remotely manage contacts in Teams admin center Microsoft 365 Roadmap ID 81379 Updated May 30, 2025: We have updated the timeline below. Thank you for your patience. Coming soon to the Microsoft Teams admin center: Admins will be able to remotely manage contacts to ensure crucial contacts are available for users on their Teams Phone devices. This feature is only available for common area phones. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out this feature in mid-July 2025 and expect to complete by late July 2025. General Availability (GCC High): We will begin rolling out this feature in late August 2025 and expect to complete by early September 2025. General Availability (DoD): We will begin rolling out this feature in late September 2025 and expect to complete by early October 2025. How this will affect your organization: IT admins can access the Manage contacts feature from Teams admin center > Teams Devices > Phones > Common area phones. Select the applicable devices and then select Manage contacts. In the right panel, use the Search box to search for and select contacts to add to selected devices. You can upload a CSV file for contacts not found through Search. Newly added contacts will be synchronized to the Calls app and People app on the Teams phones devices under the group name Company contacts within 24 hours. For any device, admins can review or delete the added contacts from the Manage contacts right panel. Track the progress and status of contact operations with the Activity log in the Teams phone inventory. 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. If you have questions or need further assistance regarding this feature, please reach out to our support team. Before rollout, we will update this post with revised documentation. MC942829 — (Updated) Microsoft Teams admin center: Activity log for Teams Phone device management Microsoft 365 Roadmap ID 420326 Updated May 30, 2025: We have updated the timeline below. Thank you for your patience. We’re excited to announce the rollout of a new feature in the Teams admin center: Activity log for Teams Phone device management. This feature empowers Teams administrators to actively monitor and track device operations, providing greater control over remote operations on Teams devices. Updated December 3, 2024: We have updated the rollout timeline below. Thank you for your patience. Currently, the Activity log supports only the remote management of contacts on Teams Phones; however, we’re working to expand this feature to other device types and additional operation categories. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out this feature in mid-July 2025 and expect to complete by late September 2025. How this will affect your organization: Admins can access the new Activity log by navigating to the Teams admin center > Teams Devices > Phones > Activity log Because only remote management of contacts for Teams Phones is currently supported, admins will be able to track operations such as Add contacts or Delete contacts and details like created time, impacted users, operation status, and more. By selecting an operation name, admins can view status updates at a granular level for each device involved in that operation. The Activity log 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. If you have questions or need further assistance regarding this feature, please reach out to our support team. Before rollout, we will update this post with revised documentation. MC908115 — (Updated) Microsoft Teams: Meeting organizers can turn off copying of captions, transcript and recap Microsoft 365 Roadmap ID 416072 Updated May 12, 2025: We have updated the timeline below. Thank you for your patience. Coming soon: Meeting organizers with eligible licenses will have a Meeting option control called Turn off copying and forwarding of meeting chat, live captions, and transcript. When this control is enabled, meeting participants won’t be able to copy the meeting chat, live captions, live transcript, or any insights generated from intelligent meeting recap. This message applies to tenants with Teams Premium licenses on Teams for Windows desktop, Mac desktop, Teams on the web, and Teams for Android/iOS. Please note that the updated meeting option doesn’t apply to sales insights in Recap and the scenarios outside Teams (e.g., transcript on Stream) with this release. When this will happen: Targeted Release: We will begin rolling out early January 2025 (previously early December) and expect to complete by mid-January 2025 (previously mid-December). General Availability (Worldwide, GCC): We will begin rolling out mid-January 2025 (previously mid-December) and expect to complete by early mid-February 2025 (previously early January). General Availability (GCC High, DOD): We will begin rolling out mid-March 2025 (previously early February) and expect to complete by late May 2025 (previously late April). Note: Only applicable for live captions and transcript. How this will affect your organization: Before this rollout: Meeting organizers have a control in Meeting options for Turn off copying or forwarding of meeting chat. After this rollout: The Turn off copying or forwarding of meeting chat control in Meeting options will become the Turn off copying and forwarding of meeting chat, live captions, and transcripts control, which allows meeting organizers to prevent meeting participants from copying meeting chat, live captions, transcripts, and AI-generated insights in the meeting recap. Forwarding and sharing messages to Outlook will also be disabled. This updated control is available by default for meeting organizers to enable. What you need to do to prepare: No admin action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation. Before rollout, we will update this post with revised documentation. MC898391 — (Updated) Microsoft Teams: Performance improvements for meetings in Edge web browser for guests Microsoft 365 Roadmap ID 401117 Updated May 9, 2025: We have updated the 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 May 2025 (previously late April). 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 May 9, 2025: We have updated the 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 May 2025 (previously late April). 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> MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar Microsoft 365 Roadmap ID 409226 Updated May 12, 2025: We have updated the 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 May 2025 (previously late April). 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. MC718553 — (Updated) Microsoft Teams: Change background while recording on phone Microsoft 365 Roadmap ID 380852 Updated May 9, 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 May 2025 (previously late April). 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 May 19, 2025: After further review, we were not able to rollout to DoD. 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: We will begin rolling out mid-June 2024 (previously early June) and expect to complete by complete by late May 2025 (previously late April). 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 June 2, 2025: We have updated the 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-June 2025 (previously mid-April). 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. MC704035 — (Updated) Microsoft Teams: Integrate Chat notification with Meeting RSVP status Microsoft 365 Roadmap ID 161739 Updated May 28, 2025: We have updated the timeline below. Thank you for your patience. Microsoft Teams users will soon be able to control how they get notified in meeting chats through RSVP to their meetings. When they decline a meeting, they will not receive notifications or see the chats in chat list; when they accept a meeting, they will receive notification for all new messages. This release of Microsoft Teams Meeting ID will be rolling out across Microsoft Teams Desktop, Mobile and Web and will provide an additional way for users to control their chat list by selecting which meetings they want to receive message updates from. When this will happen: Targeted Release: will begin rolling out early April 2025 (previously mid-March) and expect to complete by mid-April 2025 (previously late March). General Availability (Worldwide): will begin rolling out late April 2025 and expect to complete by early May. General Availability (GCC): will begin rolling out late April 2025 and expect to complete by mid-May 2025. General Availability (GCC High): will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (DoD): will begin rolling out early June 2025 and expect to complete by mid-June 2025. How this will affect your organization: You will not receive notifications or see chats from meetings you declined. You will be able to set how you want to be notified for meetings you RSVP with Accept or Tentative from Microsoft Teams settings. What you need to do to prepare: You might want to notify your users about this new capability to control meeting chat notifications by RSVP to meetings. MC695487 — (Updated) Contact Unification across Outlook and Teams Updated May 7, 2025: We have updated the timeline below. Thank you for your patience. Today, users can see Outlook contacts created with their Entra ID (AAD) account in Teams, but contacts created in Teams are not available in Outlook. To provide a consistent experience we are making changes to allow Teams contacts, created with a user's Entra ID (AAD) account, to be visible in Outlook as well. Upcoming changes to contacts in Teams and Outlook: Currently, Teams and Outlook maintain separate contact lists for enterprise users. Based on your feedback, we plan to introduce a unified contact experience, ensuring a consistent contacts experience across Outlook and Teams. In future, changes to contacts in users’ organization (Entra ID) account in Teams will reflect in Outlook and vice versa. What's Happened so far: We have completed one round of migration of all Teams contacts to Outlook in January 2024. As a result, users may see more contacts in Outlook, namely those created in Teams and potentially Skype for Business contacts (if enabled). Existing Outlook contacts may also be enriched with additional details from corresponding Teams contacts. Teams users can see Outlook contacts but cannot edit them inside Teams. What's Coming: Users will gradually upgrade to the new unified experience from December 2024. The new experience will be enabled for each user across all endpoints (Desktop, Mobile, Devices etc.) simultaneously. Once the new experience is enabled for a user, they will see same set of contacts in Outlook and Teams. Any change in Outlook will reflect in Teams and vice versa. All Teams contact changes (creations and edits) made since January will be included in the unified store. During creations, a small set of users may see duplicate contacts in the unified store. To help users navigate the transition, category label ‘Teams Conflict’ will be applied to duplicate contacts. This label will help users see any conflicts (duplicates or inconsistencies) that need their attention. When this will happen: This activity is expected to be completed for all active users by June 2025 tentatively (previously April). Once this activity is complete, users will work with a single contact list across Teams and Outlook. How this will affect your organization Once this change is complete, users will be able to see created contacts across both Outlook and Teams and vice versa. What you need to do to prepare Action Required: Update your organisation documentation and training materials to reflect the upcoming changes for the new unified contact experience. You may consider updating your training and documentation as appropriate. If users wish to retain a snapshot of their existing contacts in Outlook, please encourage users to back-up their existing contacts using the export capability in Outlook. MC688109 — (Updated) Co-organizer experience updates in Teams Webinars and Townhalls Microsoft 365 Roadmap ID 168524 Updated May 28, 2025: We have updated the 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 2025 (previously mid-December). General Availability (Worldwide, GCC): We will begin rolling out mid-November 2025 (previously mid-January 2025) and expect to complete by late November 2025. (previously late December 2025). 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 MC1087105 — Microsoft Purview | Endpoint Data Loss Prevention: Advanced label-based protection for all files on devices Microsoft 365 Roadmap ID 487859 Coming soon for Microsoft Purview | Endpoint Data Loss Prevention (DLP): This rollout will allow DLP customers use Microsoft Purview Information Protection to apply sensitivity labels to protect non-Office/PDF files, without impacting user productivity. This feature is supported only on Windows devices. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late June 2025 and expect to complete by late July 2025. How this will affect your organization: There is no change to your organization current’s use of labels on non-Office files and PDF files. This feature will be available by default but requires enablement by admins in the Purview portal at Data Loss Prevention settings > Endpoint DLP settings > Advanced label-based protection for all files on devices: 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 about label protection on devices: Advanced label-based protection for all files on devices Before rollout, we will update this post with new documentation. MC1087100 — Microsoft Purview | Endpoint Data Loss Prevention: Pause and Resume support for printer scenarios (GCC, GCCH, DoD) Microsoft 365 Roadmap ID 486369 Coming soon for Microsoft Purview | Endpoint Data Loss Prevention (DLP): Pause and Resume support for printer scenarios for customers trying to override a DLP soft warning policy tip when submitting a print job. Before this rollout, the user must reinitiate the print job for the intended result. After this rollout, the override will be stored temporarily, and the print job will execute. This rollout is a fix for the Block with override action described in Create and deploy a data loss prevention policy | Microsoft Learn. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late May 2025 and expect to complete by early June 2025. How this will affect your organization: This feature should reduce clicks for users and lessen frequency of alerts. After this rollout, when a print job is blocked by a policy, a user will see this pop-up notice. After the user enters the Business justification, the justification will be stored, and the content will print: This change will be available by default. What you need to do to prepare: Identify Endpoint DLP policies to test after rollout to ensure the new experience is in place. 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. MC1085582 — Microsoft Purview | Data Loss Prevention: True file types detected in Microsoft Exchange Online DLP (preview) Microsoft 365 Roadmap ID 493291 Coming soon for Microsoft Purview | Data Loss Prevention for Microsoft Exchange Online: Before this rollout, Exchange Online relies only on the file extension (such as .docx and .pdf) to identify the type of an attachment but this approach can be bypassed if a file is renamed with a misleading extension. To address this, we’re enhancing our detection logic to go beyond just the visible file extension. After this rollout, even if a file’s extension is altered, Exchange will evaluate the actual content of the file to determine its true type. This ensures that policies based on file type (such as File extension is…) will remain effective and secure, even when attachments are renamed or disguised. This improvement provides you with a more robust and reliable way to enforce compliance and security rules around file sharing. When this will happen: Public Preview: We will begin rolling out mid-July 2025 and expect to complete by late August 2025. General Availability (Worldwide): We will begin rolling out late August 2025 and expect to complete by late September 2025. General Availability (GCC, GCC High): We will begin rolling out late August 2025 and expect to complete by mid-October 2025. How this will affect your organization: After this rollout, you can configure rules in the Purview portal based on the true file type using the File Extension is predicate in Data Loss Prevention for Exchange Online, and then you will start to see seeing the relevant details for rule matches in all the experiences, such as Alerts and Activity explorer. To set up this feature for Exchange, go to Data Loss Prevention > Policy Settings > Create rule and use the File extension is condition: How the configured rule appears in other Purview experiences. For example, in Incident reports: How the configured rule appears in Alerts: How the configured rule appears in Activity explorer: This feature will be available by default for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. If you are already using the File Extension is predicate in Data Loss Prevention for Exchange Online, be prepared to see increase in number of detections for these predicates because we will validate these predicates for both visible and the true file extensions after this rollout. Learn more: New-DlpComplianceRule (ExchangePowerShell) | Microsoft Learn MC1077858 — Teams Meeting Audit Events in GCC Microsoft 365 Roadmap ID 491010 We're expanding auditing capabilities in Microsoft Teams for GCC customers. Teams Audit Events for Meetings—including MeetingDetail and MeetingParticipantDetail—will soon be available in Microsoft Purview. This enhancement provides administrators with deeper visibility into meeting activity, supporting compliance, investigations, and operational oversight. When this will happen: General Availability (GCC): Rollout will begin in early June 2025 and is expected to complete by late June 2025. How this will affect your organization: With this update, Teams meeting activities in GCC tenants will be audit logged in the Microsoft Purview portal. MeetingDetail logs include meeting start/end times, subject, and organizer information. MeetingParticipantDetail logs include participant join/leave times, roles, and status changes. These logs enhance your ability to monitor meeting usage and investigate user activity. What you need to do to prepare: No action is required if Audit logging is already enabled in your tenant. Admins can access and analyze these logs in the Microsoft Purview portal using search, filter, and export capabilities. MC1075907 — Microsoft Purview | Insider Risk Management: Updated user scoping features in policies Microsoft 365 Roadmap ID 412942 Microsoft Purview | Insider Risk Management will roll out enhancements to user scoping features in policies, When this will happen: General Availability (Worldwide): We will begin rolling out late June 2025 and expect to complete by early July 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out early October 2025 and expect to complete by early November 2025. How this will affect your organization: After this rollout, Insider Risk Management admins with appropriate permissions can select combinations of users, groups, and adaptive scopes to include or exclude from Insider Risk Management policies in the Microsoft Purview portal at New insider risk policy > Users and groups > Exclusions (optional): 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. Review your current configuration to assess the impact on 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. Learn more about creating policies in Microsoft Purview Insider Risk Management MC1070851 — Microsoft Purview | Data Loss Prevention: Scoping policies for devices and device groups in Endpoint (GCC, GCCH, DoD) Microsoft 365 Roadmap ID 491011 In Microsoft Purview, before this rollout, you can create an Endpoint Data Loss Prevention (DLP) policy and assign it to specific users or user groups. After this rollout, you will be able to create and assign policy based on both users and machines. You can use this feature to achieve different policies for same user on different devices. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: This feature will not impact your organization unless you use the feature in your policy. The feature will be available by default 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 admins about this change and update any relevant documentation. To use this feature, you must have one of these builds installed: Windows 10: December 10, 2024—KB5048652 (OS Builds 19044.5247 and 19045.5247) - Microsoft Support Windows 11 22H2: November 21, 2024—KB5046732 (OS Builds 22621.4541 and 22631.4541) Preview - Microsoft Support Windows 11 24H2: December 10, 2024—KB5048667 (OS Build 26100.2605) - Microsoft Support These prerequisites may be updated when we release this feature. Please follow our public document for the latest prerequisite information. Learn more Configure endpoint DLP settings | Microsoft Learn The section called Prepare your Windows devices in Onboard Windows devices into Microsoft 365 overview | Microsoft Learn (will be updated before rollout) MC1068263 — Microsoft Purview compliance portal: Endpoint Data Loss Prevention: New "Full URL" field in activity explorer Microsoft 365 Roadmap ID 471445 Coming soon to Microsoft Purview | Endpoint Data Loss Prevention (DLP): We will show the full path of a target domain instead of just the domain name in activity explorer. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out early May 2025 and expect to complete by late May 2025. How this will affect your organization: After this rollout, in cloud egress events (File copied to cloud), you will soon be able to find out exactly where the data is moving with the new Full URL field in Activity Explorer. This change will be on by default. What you need to do to prepare: Enable the Full URL toggle in Endpoint Data Loss Prevention Settings. Go to Endpoint Data Loss Prevention Settings > Browser and domain restrictions to sensitive data > File copied to cloud > Turn on Full URL. Look for the rule matches in activity explorer for a new or existing DLP policy that monitors cloud egress. Find the Full URL in the event details pane. This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins about this change and update any relevant documentation. MC1068262 — Microsoft Purview compliance portal: Endpoint Data Loss Prevention: Full file evidence for restricted apps Microsoft 365 Roadmap ID 479757 Coming soon for Microsoft Purview: Endpoint Data Loss Prevention: The existing full file evidence feature supports activities like Cloud egress, paste to supported browser, copy to USB, Network share, RDP, and Bluetooth app. With this rollout, we will expand full file evidence feature to restricted or unallowed apps. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out early May 2025 and expect to complete by late May 2025. How this will affect your organization: After the rollout, the Purview admin can follow these steps to enable full file evidence collection for restricted or unallowed apps: Step 1: Enable evidence collection for new or existing restricted apps or app groups in Endpoint DLP Settings. Step 2: Enable evidence collection for unallowed apps in new or existing policies: Configure rule condition. Select the restricted app group under File activities for apps in restricted app groups with the right enforcement mode OR select Access by restricted apps with right enforcement mode. Under Collect original file as evidence for all selected file activities on Endpoint, enable Access by restricted apps. This change will be available by default for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins about this change and update any relevant documentation. Learn more: The section called Configure your DLP Policy in Get started with collecting files that match data loss prevention policies from devices | Microsoft Learn MC1066147 — Microsoft Purview | Insider Risk Management: Downgrade or remove sensitivity label (GCC, GCC High, DoD) Microsoft 365 Roadmap ID 473431 Coming soon for Microsoft Purview | Insider Risk Management: We will enhance these existing Microsoft Office 365 indicators: Downgrading sensitivity labels applied to SharePoint files Removing sensitivity labels from SharePoint files When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out early May 2025 and expect to complete by late May 2025. How this will affect your organization: Before this rollout, IRM only captures sensitivity label changes on the Microsoft SharePoint web app. After this rollout, IRM will capture sensitivity label changes (downgrade or remove) when performed on Microsoft OneDrive, Microsoft Azure Information Protection, or endpoints (SharePoint files opened in an Office app or any sensitivity label change on the local files on a user's device). Also, we will rename the indicators: Downgrading sensitivity labels applied to SharePoint files will become Downgrading sensitivity labels applied to files Removing sensitivity labels from SharePoint files will become Removing sensitivity labels from files In Activity explorer, events that occurred before this rollout for these indicators will continue to show Labels of sensitive files on SharePoint downgraded or Label of sensitive files removed on SharePoint. Events that occur after the rollout will be shown as Labels of sensitive files downgraded or Labels of sensitive files removed. No action is needed to enable these features. This feature will be on by default. The renamed indicators in the IRM policy wizard: Example of a new event for Downgrading sensitivity labels applied to files as shown in Activity explorer: 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. MC1058262 — (Updated) Microsoft Purview | Insider Risk Management: Enhancements to global exclusions in IRM settings Microsoft 365 Roadmap ID 486826 and Roadmap ID 483485 Updated May 8, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Purview | Insider Risk Management (IRM): Enhancements to IRM exclusions to reduce alert noise. When this will happen: Public Preview: We began rolling out mid-April 2025 and expect to complete by late April 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early June 2025 (previously late April) and expect to complete by late June 2025 (previously early May). How this will affect your organization: Customer can use this feature to tune down the noise Keyword logic update for email: An email will be excluded from scoring only when all the attachments match the keyword exclusions or email subject matches the keyword exclusions. This will be helpful to reduce the email signature noise that commonly contains keyword "image." Keyword exclusions on both target and source file paths: For signals like File copied to removable media, keyword exclusions apply on both target and source file paths. File path exclusions for removable media: We will start supporting file path exclusions for removable media. Exclusion support for browser: Domain exclusions will be supported for browsing indicators. These enhancements will be available by default for admins to configure. What you need to do to prepare: To get the most out of this feature, admins need to update the exclusion settings at IRM Settings > Global exclusions. This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. 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. MC1046161 — Microsoft Purview | Data Loss Prevention: New inline protection controls for AI apps in Microsoft Edge for Business Microsoft 365 Roadmap ID 486368 Updated May 15, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Purview | Data Loss Prevention (DLP): We will introduce new inline protection capabilities for Microsoft Edge for Business that prevent data leakage for the various ways that users interact with sensitive data in the browser, including typing text directly into a web application or sending a prompt to a generative AI app. Inline protection is built natively into Edge for Business, meaning it can be enabled even without deploying Endpoint DLP, and the inline protection complements existing Endpoint DLP protections for uploading or pasting sensitive content to the browser. This capability will be available starting with several top consumer generative AI apps (ChatGPT, Google Gemini, and DeepSeek), and will expand to support a growing list of unmanaged apps over time. Learn more in our blog: Building layered protection: New Microsoft Purview data security controls for the browser & network | Microsoft Community Hub When this will happen: Public Preview: We will begin rolling out late May 2025 (previously early April) and expect to complete by early June 2025 (previously late April). We will update this message when the plan for General Availability is finalized. How this will affect your organization: After this rollout, admins can block prompts typed by users containing sensitive data, starting with ChatGPT, Google Gemini, and DeepSeek. Inline protection can also leverage Adaptive Protection policy conditions for activities in generative AI apps. This rollout enables data security admins to tailor the level of enforcement to the risk level of the user interacting with the data, minimizing disruption to day-to-day AI usage. This change will be available by default for Admins to configure in Purview. Features aren't activated 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. Review your current configuration to assess the impact on your organization. We recommended informing Security admins and Edge admins at your organization about this change to DLP features. You may want to update any relevant documentation. MC1036579 — (Update) Microsoft Purview | Data Loss Prevention: A new Diagnostics experience in the new portal Microsoft 365 Roadmap ID 469504 Updated May 14, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Purview | Data Loss Prevention: Admins will be able to view and manage Diagnostics in the new Purview portal. Before this rollout, diagnostics are only available through Microsoft PowerShell cmdlets. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out early May 2025 (previously mid-April) and expect to complete by mid-June 2025 (previously late May). How this will affect your organization: Admins can find the new experience at: Purview portal > Information Protection > Diagnostics Purview portal > Data Loss Prevention > Diagnostics The PowerShell cmdlets will continue to be available after this rollout. This new experience will be on 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. 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. MC1034582 — Microsoft Purview compliance portal: Endpoint Data Loss Prevention: "Paste to browser" prevention on macOS devices Microsoft 365 Roadmap ID 483491 Updated June 3, 2025: We have updated the timeline below. Thank you for your patience. Microsoft Purview | Endpoint Data Loss Prevention (DLP) will soon add support for restricting users from pasting sensitive content into web browsers on macOS devices using Microsoft Edge, Safari, Chrome, and Firefox. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late June 2025 (previously mid-May) and expect to complete by mid-July 2025 (previously early June). How this will affect your organization: After this rollout, if you have already configured DLP policies to prevent users in your organization from pasting sensitive content into a supported web browser on a Windows device, the policies will automatically apply to a supported web browser on macOS devices also. 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. 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: Learn about Endpoint data loss prevention | Microsoft Learn MC1034577 — (Updated) Microsoft Purview compliance portal: Endpoint Data Loss Prevention: Full file evidence parity for macOS Microsoft 365 Roadmap ID 483492 Updated May 8, 2025: We have updated the timeline below. Thank you for your patience. Microsoft Purview | Endpoint Data Loss Prevention (DLP) will soon add support for copying an item that matches a DLP policy from onboarded macOS devices to a Microsoft Azure storage account. This rollout creates full file evidence parity for macOS. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late May 2025 (previously late April) and expect to complete by late June 2025 (previously late May). How this will affect your organization: After this rollout, if you have already configured DLP policies for users in your organization to collect file evidence in Azure storage to protect Windows devices, the policies will automatically apply to macOS devices also. 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. 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: Learn about collecting files that match DLP policies from devices | Microsoft Learn MC1026220 — (Updated) Microsoft Purview | Endpoint Data Loss Prevention: Support for Just-in-time protection on MacOS devices Microsoft 365 Roadmap ID 483354 Updated May 7, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Purview | Endpoint Data Loss Prevention (DLP): You will be able to use just-in-time (JIT) protection to block all egress activities on monitored files while waiting for policy evaluation to successfully complete. This message applies to macOS devices. For any organizations that have already configured DLP settings with JIT to protect Windows device, the policies will automatically apply to macOS devices also. When JIT protection is enabled, and while policy evaluation is processing, Endpoint DLP blocks all egress activities for each user whose account is in the selected scope. Endpoint DLP audits the egress activities for all user accounts that have been excluded (via the Exclude setting) or are otherwise not in scope. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late March 2025 and expect to complete by late May 2025 (previously late April). How this will affect your organization: This feature will be available by default for admins to configure. If your organization has already enabled JIT on your Windows device, your macOS devices will start getting the same protection. What you need to do to prepare: No change is required to your existing DLP settings. This rollout will happen automatically by the specified dates 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 on macOS devices about this change and update any relevant documentation. Learn more: Using Endpoint DLP Just-in-time protection | Microsoft Learn MC1024388 — (Updated) Microsoft Purview compliance portal: Modern eDiscovery enhancements Microsoft 365 Roadmap ID 482558 Updated May 7, 2025: We have updated the timeline below. Thank you for your patience. We are excited to announce several enhancements to the recently launched modernized eDiscovery experience. These updates include: Case Level Data Source View: Users can now access the case level data source view, which allows them to add data sources to the current case. These sources can be utilized in any searches or holds within the case. Enhanced Search and Hold Capabilities: Users will have the ability to duplicate a search, create a search from an existing hold, or create a hold from an existing search within the current case. Retry Failed Locations: The search statistics view now includes the option to retry failed locations, providing a more comprehensive search estimate. Detailed Process Reports: We are adding information related to compliance boundaries, case/export/search names, and decryption settings into the relevant process report CSVs. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-March 2025 and expect to complete by late May 2025 (previously late April). How this will affect your organization: eDiscovery users will start to see the relevant enhancements in the product, so internal documentation updates may be needed. What you need to do to prepare: Evaluate how this feature will impact your organization’s eDiscovery process and, if needed, modify your internal documents accordingly. For more information, see Learn about eDiscovery solutions | Microsoft Learn. Defender XDR MC1080684 — Microsoft Defender for Office 365: Introducing the new Take action wizard for Threat Explorer (GCC, GCC High, DoD) Microsoft 365 Roadmap ID 488094 Coming soon for Microsoft Defender for Office 365: We will introduce a new Take action wizard to help security operations team members perform multiple response actions at once from Threat Explorer. Many security analyst teams use Explorer, Summary panel and Email entity to execute bulk email remediation actions. This new experience will enable more effective, smooth, and efficient remediation of threats. When this will happen: General Availability (GCC): We will begin rolling out late May 2025 and expect to complete by early July 2025. General Availability (GCC High): We will begin rolling out early June 2025 and expect to complete by mid-July 2025. General Availability (DoD): We will begin rolling out mid-June 2025 and expect to complete late July 2025. How this will affect your organization: After the rollout of the new Take action wizard, you can perform multiple actions such as purging emails, inline submissions, triggering investigations, and Tenant Allow/Block List actions on up to 100 messages. Also, you will be able to initiate tenant-level actions to block URLs or file directly from Threat Explorer. You can also use the new wizard to perform bulk email remediation for more than 100 messages, but only one action can be executed at a time, such as triggering an email purge. Also, actions like tenant level block and submissions are not permitted for selections over 100. NOTE: Some actions will not be available in the wizard based on the current location of the message. If there is a conflict, the new experience provides more options, including the ability to turn choices on/off as desired to take proper action. Enhancements to the Email entity page and the Email summary panel: Step 1: Sign into the Microsoft 365 Defender portal. Step 2: Go to Threat Explorer > Email & Collaborations and select the emails that require action. Step 3: Select the Take action wizard. (Before this rollout, the next step was to choose from the Message actions menu. We removed this menu.) Step 4: This will open a new panel. Some actions will be grayed out depending on the latest delivery location of the message. Step 5: Tenant Allow/Block List actions are under Submissions, so when you select I’ve confirmed as threat, you will see a new Tenant Allow/Block List panel where you can choose multiple entities to block. Step 6: Choose the target entities. Step 7: Review the actions you have chosen and then submit. Step 8: You can access email purge remediation actions in the action center. What you need to do to prepare: A Search and Purge role is required to initiate email purge actions from the Email entity page. To initiate Tenant Allow/Block List actions from Explorer and summary panel and Email entity, please assign the necessary Exchange Online permission role as explained in Allow or block files using the Tenant Allow/Block List - Microsoft Defender for Office 365 | Microsoft Learn Learn more about the Search and Purge role: Microsoft Defender for Office 365 permissions in the Microsoft Defender portal - Microsoft Defender for Office 365 | Microsoft Learn This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your admins or users about this change and update any relevant documentation. Microsoft 365 Copilot MC1085134 — Microsoft Copilot Pages: New file extension for Copilot pages Microsoft 365 Roadmap ID 494834 Coming soon: A new .page file extension for Microsoft Copilot Pages. This new file extension will continue to support admin toggles, sensitivity labels, data loss prevention, multi-geo storage, Microsoft Purview eDiscovery, version history, export, audit logs, and data subject requests. The functionality and support for the .page file extension will be identical to the existing .loop file extension. The only difference is the file extension name and file icon. A Microsoft 365 Copilot license or a Microsoft 365 license is required to access this feature. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late June 2025 and expect to complete by late July 2025. How this will affect your organization: After this rollout, users searching for Copilot pages will see these files with the new .page extension and the new file icon. For a comprehensive list of features supported, refer to: Summary table of admin management, governance, lifecycle, and compliance capabilities based on experience The new file icon for .page: This change will be on by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change. Related Post: MC1056992 / Pages created in Microsoft 365 Copilot Chat will open in Microsoft 365 Copilot app (published April 2025) Learn more about admin controls for Pages: Copilot pages for IT Admins - Sep 2024 update | Microsoft Community Hub MC1084034 — Intelligent Recap Access for Multi-tenant Organization Microsoft 365 Roadmap ID 488298 Copilot users in a business-to-business multi-tenant organization set up can now view the intelligent meeting recap after the meeting from the resource tenant where the meeting was hosted. When this will happen: Public Preview: We will begin rolling out early-July 2025 and expect to complete by mid-July 2025. General Availability: We will begin rolling out mid-July 2025 and expect to complete by late-July 2025. How this will affect your organization: The new capability empowers users in multi-tenant setup to access meeting recap post meeting. What you need to do to prepare: No action required for either admin or users. Any Copilot users configured as a business-to-business user in a multi-tenant organization will have the capability after the launch. For additional information on B2B muti-tenant: Overview: B2B collaboration with external guests for your workforce MC1074972 — (Updated) Microsoft SharePoint: New web part for FAQs powered by Microsoft 365 Copilot Microsoft 365 Roadmap ID 482198 Updated May 20, 2025: We have updated the content. Thank you for your patience. Coming soon for Microsoft SharePoint: A new web part for FAQs, to help content owners keep their content fresh and relevant. Powered by Microsoft 365 Copilot, this new web part automatically curates FAQ content by working with agents and connected grounding data. With a human-in-the-loop approach, it ensures information stays accurate, relevant, and trustworthy, making it easier for all page visitors to find the answers they need. Copilot license requirements: Reading: All readers can view FAQ web part content without a Copilot license. Creating & Editing: A Copilot license is necessary for creating and editing content using Copilot features. This feature requires a SharePoint license and a Microsoft 365 Copilot license. When this will happen: Targeted Release: We will begin rolling out early June 2025 and expect to complete by mid-June 2025. General Availability (Worldwide, GCC): We will begin rolling out late June 2025 and expect to complete by early July 2025. How this will affect your organization: After this rollout, authors can add the web part for FAQs directly to pages or news posts during editing: By selecting one or more grounding source files, AI will automatically generate FAQ content, reducing the time and effort needed for manual creation of FAQs. The web part currently supports FAQ types such as Event, Product, and Policy, with the option for authors to provide additional descriptions to guide more targeted content generation. FAQs created using the web part can be indexed for search and shared via email, making it easier to distribute consistent, up-to-date information to your organization. This change 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. Before rollout, we will update this post with new documentation. MC1073094 — Microsoft Outlook: Summarize email attachments with Copilot Microsoft 365 Roadmap ID 475249 Soon, users will be able to summarize PDF, Microsoft Word (.docx), and Microsoft PowerPoint (.pptx) email attachments with Copilot in Outlook. The new feature will be available in Microsoft Outlook for the web, the new Microsoft Outlook for Windows desktop, Microsoft Outlook for Android/iOS, and the new Microsoft Outlook for Mac desktop. A Microsoft 365 Copilot license is required to access this feature. When this will happen: General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late July 2025. General Availability (GCC): We will begin rolling out mid-June 2025 and expect to complete by late August 2025. How this will affect your organization: After this rollout, users will be able to pick a classic attachment from the email thread and summarize it with Copilot by selecting Summarize in the attachment's three-dot context menu or in the attachment's Preview, or by selecting Summarize a file in the Summary by Copilot card. The Copilot summary will display below the existing email summary inside the Summary by Copilot card: We do not support encrypted files or files protected by Microsoft Information Protection (MIP). This feature will be available by default for users with a Copilot license, but this feature will respect the Copilot control toggle setting in Outlook. Users who have turned off this toggle will not see this feature. What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Learn more: Summarize an email thread with Copilot in Outlook - Microsoft Support (will be updated before rollout) #newoutlookforwindows MC1070847 — Sharing with Copilot summary - Now supporting PowerPoint, Excel, PDFs, Images, .txt, and protected files Microsoft 365 Roadmap ID 490156 We’re excited to announce two major enhancements to sharing files with Copilot Summary: Broader file types and endpoint support: Sharing with Copilot summary now supports more file types, including PowerPoint web, Excel web, PDF, images, and text (.txt) files, across OneDrive web, SharePoint Document Library, and M365 File Previewer. Support for protected files: Files labeled as protected or confidential can now be summarized. This is especially valuable for customers that apply a default sensitive label to all documents, enabling them to use this feature while keeping data protected at all times. These enhancements represent a significant step forward in broadening access to capabilities and making sharing more collaborative and impactful in daily collaboration. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025. How this affects your organization: When sharing Word, Excel, PowerPoint, PDF, image (.png, .jpeg), or text (.txt) files via the web, users will have the option to generate a file summary by clicking the Copilot button inside the share dialog. The generated summary will be automatically included in the share notification email sent to the intended recipients. What you can do to prepare: You may consider updating your training and documentation as appropriate. MC1068906 — (Updated) Microsoft Teams: Microsoft 365 Copilot for phone without transcription Microsoft 365 Roadmap ID 482745 Updated May 30, 2025: We have updated the timeline below. Thank you for your patience. We are releasing a new feature that enables users to leverage Copilot's capabilities during live call sessions without retaining transcripts or an audio recording afterward. This ensures that users can benefit from Copilot during sensitive conversations where a persistent record is not desired. Post-call Copilot functions, such as recap, will not be available after the call concludes. When this will happen: Targeted release: We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. How this will affect your organization: Users who have transcription turned off will be now able to use Copilot. What you need to do to prepare: Admin settings will be made available as part of the Calling policy to allow admins to configure the setting for their users. More details to follow. MC1068268 — Account Switcher for Copilot Tab on iOS and Android Microsoft 365 Roadmap ID 490213 You can now switch between accounts on the Copilot chat tab on iOS and Android. Simply swipe left to open the left-navigation and select from the list of supported accounts. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out in early June 2025 and expect to complete by late June 2025. How this will affect your organization: Currently, users are only able to access the Copilot Chat tab with their default account or privacy, even if they have other accounts that support Copilot. With account-switching on iOS and Android, users will be able to access Copilot Chat from other accounts that support Copilot, enabling them to access their chat history and graph data associated with those accounts. iOS: Android: 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. MC1056264 — (Updated) Microsoft PowerPoint: Reference a TXT file when creating a presentation with Microsoft 365 Copilot Microsoft 365 Roadmap ID 488795, Roadmap ID 488796, and Roadmap ID 488794 Updated May 14, 2025: We have updated the timeline below. Thank you for your patience. April 18, 2025: After further review we have decided not to proceed with GCC at this time. We also have updated the rollout timeline below. We apologize for any inconvenience When creating a presentation in Copilot for Microsoft PowerPoint, users will be able to reference TXT files in addition to Microsoft Word files. A Microsoft 365 Copilot license is required to use this feature. This message applies to PowerPoint for Windows desktop, PowerPoint for Mac desktop, and PowerPoint on the web. When this will happen: General Availability (Worldwide): We will begin rolling out mid-May 2025 (previously early May) and expect to complete by late May 2025 (previously mid-May). How this will affect your organization: After this rollout, users can see TXT files when searching for files that Copilot can use to create a presentation. Select the Copilot icon from the PowerPoint ribbon, choose Create a presentation from [file], and search for TXT files by file name or paste the URL of your TXT file from Microsoft OneDrive or Microsoft SharePoint. This feature 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. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Learn more: Create a new presentation with Copilot in PowerPoint - Microsoft Support (will be updated before rollout) MC1036580 — (Updated) Microsoft 365 Copilot Chat for GCC customers Microsoft 365 Roadmap ID 464984 Updated May 12, 2025: We are currently preparing for availability and would like to share more details regarding timing. We now expect Copilot Chat to begin rolling out in early June 2025 and expect to complete the rollout by the end of June. Thank you for your patience and we will continue to share any further updates as we can. Microsoft 365 Copilot Chat (“Copilot Chat”) will be available by default at no additional cost for Entra account users with an eligible Microsoft 365 subscription: Microsoft 365 F1, F3, G3, or G5 Office 365 F1, F3, G3, or G5 Copilot Chat will be available by default from the web. It will also be available and pinned by default in the Microsoft 365 Copilot app (web, desktop), Teams (web, desktop), and Outlook (web, desktop). If Copilot Chat availability for any of these entry points changes, we will inform you. Web grounding in Copilot Chat will be off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy. Note: This only applies to GCC cloud. Copilot Chat availability for GCC High and DoD will be communicated later. When this will happen: General Availability (GCC): We will begin rolling out early June 2025 (previously mid-May). How this will affect your organization: Users will be able to access Copilot Chat from the web, and in the Microsoft 365 Copilot app, Outlook, and Teams. Copilot Chat offers: Secure, enterprise-ready AI chat powered by models like GPT-4o. o Note: Web grounding will be off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy. When web grounding is off, users will be alerted via a notification in the UI and Copilot will only use the LLM to provide a response. IT controls for data governance, including enterprise data protection. Note: Agents will not be available initially. Agent availability will be communicated later. What you need to do to prepare: Once Copilot Chat rolls out and is available in your tenant, you will be able to manage user access across entry points. To block access to Copilot Chat, refer to the documentation: Removing access to Copilot Chat. To block access from the web, and in the Microsoft 365 Copilot app and Outlook, refer to Step 2. To block access in Teams, refer to Step 3. Note: As Copilot Chat will be pinned by default in the Microsoft 365 Copilot app, Outlook, and Teams once available, you do not need to implement Step 1. Additionally, Copilot Chat will not be available initially through the Microsoft Edge sidebar, so you do not need to implement Step 4. Web grounding in Copilot Chat is off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy. To manage web grounding in Copilot Chat, please refer to our documentation here. To help your organization get the most out of the Microsoft 365 Copilot Chat, we have updated the Copilot Success Kit and added the new Copilot Chat and Agent Starter Kit. This includes: Copilot Chat user training guide to help your users get started with Copilot Chat and understand how to access it. Copilot Chat and agent IT set up and controls guide to plan, deploy, manage, and measure Microsoft 365 Copilot Chat in your organization. User engagement templates in a variety of formats—including email, Viva Engage, and Teams—that you can leverage to communicate updates and new features to your users. Note: You can customize these assets to remove content about agents since agents are not available initially. Please also refer to documentation for Copilot Chat here: Overview of Microsoft 365 Copilot Chat MC1020218 — (Updated) Microsoft Viva Connections: New News feature in Microsoft Teams Microsoft 365 Roadmap ID 472018 Updated May 20, 2025: The rollout of the feature on Viva Connections in Teams mobile will now be completed by end June 2025. The feature is generally available on Viva Connections in Teams desktop and Teams web platforms. 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 June 2025 (previously late May). 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. 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. MC1003344 — (Updated) Microsoft Copilot: File summary in Microsoft Teams chat Microsoft 365 Roadmap ID 418564 Updated May 13, 2025: We have updated the 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 July 2025 and expect to complete by mid-July 2025. General Availability (Worldwide): We will begin rolling out late July 2025 and expect to complete by early August 2025. General Availability (GCC): We will begin rolling out late July 2025 and expect to complete by early August 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. Outlook MC1085132 — Microsoft Outlook for Android: Users can apply categories to emails Microsoft 365 Roadmap ID 493945 Coming soon for Microsoft Outlook for Android: Users will be able to assign categories to emails and remove categories they have previously assigned to their emails. They will also be able to view categories in the message list and reading pane. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-June 2025 and expect to complete by mid-July 2025. With this feature, users will be able to add or remove categories on emails using conversation actions in the reading pane, using multiselect through long press in the message list, and as a new swipe action. Users will also be able to filter the message list by category. Finally, users will be able to see assigned categories on their emails in both the message list (left) and the reading pane (right): This new feature will be available by default for users to apply. 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 your documentation to prepare your help desk. MC1084640 — Microsoft Outlook for iOS/Android: New formatting options for composing emails Microsoft 365 Roadmap ID 411581 In response to feedback from you, our customers, we will add support for even more formatting options when composing in the Microsoft Outlook apps for iOS or Android. Users will be able to choose font size, set a default font, as well as clearing and painting formatting. As admins, you will have new options for configuring default formatting settings for the users in your organization. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out early June 2025 and expect to complete by early July 2025. How this will affect your organization: Users will have an option to update font size (left and center) and will be able to access to format painter and format eraser (right) from the formatting toolbar while composing: Users will be able to set a default font and size in the app settings using this sequence (left to right): The new options will be available by default. Organizational admins can manage default settings for users in your organization with an app configuration setting from your mobile application management solution such as Microsoft Intune. Learn more: Deploying Outlook for iOS and Android app configuration settings in Exchange Online | Microsoft Learn 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. MC1079737 — New Microsoft Outlook for Windows: Add custom sounds for new mail notifications, mail reactions, and Calendar reminders Microsoft 365 Roadmap ID 491019 Coming soon to the new Microsoft Outlook for Windows desktop: In the Notification settings, users will be able to add a custom sound for new mail notifications, mail reactions, and Calendar notifications (also known as Calendar reminders). When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late June and expect to complete by late July 2025. How this will affect your organization: The setting will be available by default. Users can find the three new options in Outlook Settings. For new mail notifications: Settings > General > Notifications > Mail > New mail > Play sound: For mail reactions: Settings > General > Notifications > Mail > Reactions > Play sound: For Calendar notifications: Settings > General > Notifications > Calendar > Event Reminders > Play sound: 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. #newoutlookforwindows MC1072411 — (Updated) Microsoft Outlook for iOS: Updated conversation actions Microsoft 365 Roadmap ID 492627 Updated June 3, 2025: We have updated the timeline below. Thank you for your patience. Note: If your organization does not support iOS, you can safely ignore this message. Before this rollout, when viewing an email message, a user can access the available conversation actions in Microsoft Outlook for iOS in the top right corner of the screen. After this rollout, these actions will be at the bottom of the screen. The user will be able to customize the order and placement of the actions to suit their needs. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will gradually begin rolling out early June 2025 (previously early July) and expect to complete by early January 2026. How this will affect your organization: After this rollout, actions formerly found in the top right of the reading pane (such as Mark unread, Pin, Delete, and Archive) will move to a toolbar at the bottom of the reading pane: Users can customize the order of these actions and choose which actions will be visible in the toolbar and which should stay in the three-dot menu, with the toolbar displaying as many actions as space allows. Left: Reorder conversation actions in the Customize actions pane, which users can access from the three-dot menu in the toolbar at the bottom of the reading pane. Right: Conversation actions in the three-dot menu: This consistent layout will help users build muscle memory, as actions will remain in the same positions across accounts and message views. To maintain consistency across different accounts and views, inaccessible actions will be visibly disabled, lowering the chances of triggering unintentional actions. This change will be on 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. Before rollout, we will update this post with new documentation. MC1068276 — (Updated) Create, Delete, Rename, and Move Folders in Outlook for iOS and Android Microsoft 365 Roadmap ID 489831 Updated May 20, 2025: We have updated the timeline below. Thank you for your patience. In Outlook on iOS and Android you will now be able to more easily create, delete, rename, and move folders on the mobile app. From your inbox, tap the Edit icon in the sidebar. Tap on any folder to create a subfolder, or rename, move, and delete that folder. You can also rearrange and nest your folders by dragging and dropping them. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out on early June 2025 (previously mid-May) and expect to complete by late July 2025 (previously late June). How this will affect your organization: Once available, users will have the ability to create, rename, move, and delete folders more easily on mobile. To do so, users need to open the left-navigation and tap the Edit icon to open the edit favorites/folder menu. Create folders and subfolders: Users can create a folder by tapping "+Create Folder" or by tapping on a folder to create a subfolder. Rename existing folders: User should open the Edit menu, tap on a folder, and tap rename. Move folders: Users can move folders into other folders by tapping on a folder, selecting Move, and then choosing the destination folder. Drag and drop a folder into another folder by pressing and holding the folder row, then dragging it to where you want it. Reorder folders by simply dragging and dropping them in your preferred order. Note: Drag handles (three horizontal lines) will be added next to each folder to make reordering more accessible. These handles are the same ones currently used for reordering items in your Favorites list, although they are not shown for the Folders section in these mocks. Delete folders: User should open the Edit menu, tap on a folder, and tap delete. 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. MC1066439 — (Updated) New Microsoft Outlook for Windows and Outlook for the web: Jump to a message in the message list Microsoft 365 Roadmap ID 490058 Updated May 14, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web: Users will be able to type text and jump to the next message in the message list. For example, when the message list is sorted by sender with From, users will be able to type "Philip" to jump to the first message where the sender is "Philip." When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late May 2025 (previously early May) and expect to complete by late June 2025 (previously mid-June). How this will affect your organization: After this rollout, users will be able to enter text to jump to a message. This includes jumping to a date when sorted by Date, jumping to a sender when sorted by From, jumping to a category when sorted by Category, and so on. This change will be on by default. As an example, when a user has their message list sorted by sender with From, the user can select the arrow icon to reveal the new Type to jump to a sender option to jump to a specific sender: 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. #newoutlookforwindows MC1060466 — (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Mac (GCC) Microsoft 365 Roadmap ID 489216 Updated May 29, 2025: We have updated the 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 Mac. MC980798 (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) (published January 2025, updated February 2025). When this will happen: General Availability (GCC): We will begin rolling out to Excel for Mac early June 2025 (previously mid-May) and expect to complete by late June 2025 (previously late May). 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 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. MC1041965 — (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for the web (GCC) Microsoft 365 Roadmap ID 485764 Updated May 29, 2025: We have updated the 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 the web. MC980798 (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) (published January 2025, updated February 2025). When this will happen: General Availability (GCC): We will begin rolling out to Excel for the web mid-June 2025 (previously early May) and expect to complete by mid-July 2025 (previously mid-May). 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 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. MC1041465 — (Updated) New Microsoft Outlook for Windows and Outlook on the web: Optimized hover actions in the message list Microsoft 365 Roadmap ID 429868 Updated May 20, 2025: We have updated the timeline below. Thank you for your patience. In new Outlook for Windows and Outlook on the web, the hover actions in the message list will be moved to the Sender/From column to be more space-efficient and minimize unnecessary mouse travel for users with their Reading Pane set to Hide or Bottom. The large width occupied by the DateTime Received column will thus be reduced. For all users, a one-time shortcut to change/set your hover actions will be provided. After the changes to the hover actions, the first action will be replaced by a quick button (gear button) to change/set your hover actions. After that button has been triggered once, it will disappear, and your hover action settings will kick in fully. When this will happen: Targeted Release: We will begin rolling out early June 2025 (previously mid-May) and expect to complete by early July 2025 (previously late May). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early July 2025 (previously late May) and expect to complete by late July 2025 (previously late June). How this will affect your organization: For new Outlook for Windows and Outlook on the web, hover actions in the message list will be moved to the Sender/From column to reduce the large width occupied by the DateTime Received column. 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. #newoutlookforwindows MC1041456 — (Updated) New Microsoft Outlook and Outlook for the web: New setting to enable two-click view for encrypted emails Microsoft 365 Roadmap ID 483883 Updated June 3, 2025: We have updated the timeline below. Thank you for your patience. New Outlook for Windows desktop and Outlook for the web will soon support a two-click view for encrypted emails, which requires user confirmation before allowing access to encrypted emails. As an admin, you can enable the two-click feature for your users. When this will happen: General Availability (Worldwide): We will begin rolling out early 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 late May 2025. General Availability (Worldwide, GCC): For Android and iOS, we will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: With this two-click feature enabled, users will be required to select View message for every encrypted email, and then the email will render. This feature ensures that users deliberately access encrypted email content, reducing the risk of accidental exposure, especially in unsecured environments like public spaces or during screen sharing. Admins can find the TwoClickMailPreviewEnabled setting in the Microsoft Azure directory. This setting is a Boolean type with default = 0, which means the experience is disabled by default. To enable the feature for all users in your tenant, set value = 1. Alternatively, you can access and set the value for this setting using the Microsoft PowerShell cmdlet -Set-OrganizationConfiguration in the Microsoft Exchange Online PowerShell. Learn more: Exchange Online PowerShell | Microsoft Learn By default, the two-click setting is off. What you need to do to prepare: No action is required from admins unless you want to enable this feature. This rollout will happen automatically by the specified dates 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 plan to enable this feature. #newoutlookforwindows MC1022526 — (Updated) Microsoft Outlook on the web: Optional connected experiences privacy setting Microsoft 365 Roadmap ID 467248 Updated May 7, 2025: We have updated the timeline below. Thank you for your patience. 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 May 2025 (previously late April). 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) MC947045 — (Updated) Microsoft Outlook for iOS and Android: Attach emails while composing an email Microsoft 365 Roadmap ID 464206 Updated June 3, 2025: We have updated the 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 mid-June 2025 (previously late May). 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. MC946791 — (Updated) Microsoft Outlook for iOS and Android: Minimize the compose window to multitask in the Outlook app Microsoft 365 Roadmap ID 470304 Updated May 7, 2025: We have updated the 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 May 2025 (previously late April). 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. MC917748 — (Updated) Microsoft Teams and Microsoft Outlook: Name pronunciation on the profile card Microsoft 365 Roadmap ID 420329 Updated May 29, 2025: We have updated the timeline below. Thank you for your patience. We will be starting roll out of the feature to Production on Tuesday 13th May 2025. The roll out should take a week and a half to complete to 100%. Admins who have toggled the feature ON should expect the feature to be available on the Profile card for users to record. " Updated April 29, 2025: We have now shipped the admin control, the name pronunciation feature is OFF by default so admins will need to toggle it ON. The instructions in this support document explain how to turn the feature on. Important! Starting from April 29, 2025, if you haven't turned the name pronunciation feature ON, any existing recordings on profile cards will be deleted. Your users will need to re-record their name pronunciation. The admin toggle for Name Pronunciation is rolling out to Production starting this week. Admins will be required to configure in the admin center to avoid loss of data. Instructions to configure are in this support article. Please expect the admin toggle in the admin center starting the week of April 14th through April 18th, 2025. We will be shipping to preview without the admin toggle however an admin toggle will be available before general availability. If there are concerns or your organisation wants to opt out, please raise an incident to address this. Coming soon to Microsoft Outlook and Microsoft Teams: A name pronunciation feature on the profile card in Microsoft Teams and Microsoft Outlook. This new feature helps promote diversity by giving working colleagues relevant information about each other. Names are a crucial part of a person’s identity. The incorrect pronunciation of a person’s name can lead to anxiety and offense in some cases. Correctly pronouncing a person’s name helps to create an inclusive environment. Pronunciation data is stored in each user's mailbox until the user deletes the recording. Learn more: Data Residency for Exchange Online - Microsoft 365 Enterprise | Microsoft Learn This message applies to Teams for Windows desktop, Teams for Mac desktop, new Outlook for Windows desktop, and new Outlook for web. When this will happen: Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by late November 2024. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 (previously mid-January) and expect to complete by early June 2025 (previously mid-May). How this will affect your organization: After this rollout, users can record and share the correct pronunciation of their name on their profile card. With a click, users can play and listen to name pronunciations recorded by their colleagues. To open a profile card in Outlook, double-click a name in the To or From field in any sent or received email. To open your profile card in Teams, select your profile photo in the upper right corner of the screen, and then select your name. To listen to a colleague's recorded pronunciation, select the speaker icon on their profile card. To record the pronunciation of a name, open your profile card in Outlook or Teams, and select the microphone icon: What you need to do to prepare: This feature is off by default. As an admin, you can enable the feature in Microsoft Graph using these instructions: namePronunciationSettings resource type - Microsoft Graph beta | Microsoft Learn Before rollout, we will update this post with revised documentation. You may want to notify your users about this change and update any relevant documentation. #newoutlookforwindows MC882252 — (Updated) New Microsoft Outlook for Windows: Sharing Word, Excel, and PowerPoint local files through email Microsoft 365 Roadmap ID 397094 Updated May 7, 2025: After further review, we are not able to continue rolling this out at this time until July 2025. We apologize for any inconvenience. 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 July 2025 (previously early October) and expect to complete by late October 2025 (previously late August). 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 May 1, 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 May 2025 (previously late April). 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. Exchange Online MC1085578 — Action required: Update Exchange Server and configure the dedicated Exchange hybrid application Starting with the April 2025 Hotfix Update (HU), Exchange Server supports the use of a dedicated Exchange hybrid application in your tenant’s Entra ID. If you have Exchange Server hybrid deployments and use features such as calendar Free/Busy, MailTips, and user profile picture sharing between your on-premises hosted mailboxes and Exchange Online users, you will need to move to using the dedicated Exchange hybrid application. When this will happen: Starting October 2025, Exchange Online will no longer support the shared service principal for these rich coexistence features. How this affects your organization: Note: Administrative action is required to maintain support for rich coexistence features between Exchange Server and Exchange Online functionality beyond this date. Admins must do the following before October 2025: Update all Exchange servers to one of the supported versions listed below, or newer. Configure the new dedicated Exchange Hybrid application in Entra ID and enable the feature in Exchange Server. Exchange Server 2019 CU15 - April 2025 HU - 15.2.1748.24 Exchange Server 2019 CU14 - April 2025 HU - 15.2.1544.25 Exchange Server 2016 CU23 - April 2025 HU - 15.1.2507.55 Setup guidance More information about the requirements and how to configure the dedicated Exchange Hybrid application can be found in the documentation: Deploy dedicated Exchange hybrid app What happens if no action is taken by October 2025? Rich coexistence functionality between on-premises and Exchange Online users will stop working. This includes the following key scenarios: Calendar Free/Busy lookups will fail MailTips will stop working Profile pictures lookups will fail Who is affected? This change applies only to customers running Exchange Hybrid environments (Exchange Server connected to Exchange Online) and who require rich coexistence between users with on-premises mailboxes and users who have Exchange Online mailboxes (specific features: Free/Busy lookups, MailTips and profile picture sharing). The full announcement and additional background information can be found in our blog post: Exchange Server Security Changes for Hybrid Deployments. Need support? If you need help or have questions, please contact your Microsoft account team or raise a support ticket. MC1084635 — Event Updates visible in email Microsoft 365 Roadmap ID 491018 If an organizer updates an event that you have been invited to, you will now see Event Updated in the email and the updated location if applicable. When this will happen: General Availability (Worldwide): We will begin rolling out on early June 2025 and expect to complete by late July 2025. General Availability (GCC): We will begin rolling out on early June 2025 and expect to complete by late July 2025. General Availability (GCC High): We will begin rolling out on early June 2025 and expect to complete by late July 2025. General Availability (DoD): We will begin rolling out on early June 2025 and expect to complete by late July 2025. How this will affect your organization: Users will now understand that their event is being updated when receiving event related emails, when applicable. 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. MC1081538 — Important Update to the Get-FederationInformation Cmdlet in Exchange Online To enhance security and reduce potential data exposure, we are updating the behavior of the Get-FederationInformation cmdlet in Exchange Online. This change limits the scope of domain data returned by the cmdlet. When this will happen: General Availability (Worldwide, GCC, GCC-High, DoD): Rollout will begin in mid-June 2025 and is expected to complete by late June 2025. How this affects your organization: Previously, the Get-FederationInformation cmdlet returned all federated domain information in the DomainNames field. After this update, the cmdlet will only return domain information that is explicitly passed as a parameter. This change may impact scripts or tools that rely on retrieving all federated domains by default. There is no change to the cmdlet’s availability or core functionality—only the scope of data returned is affected. What you can do to prepare: Review any automation, scripts, or tools that use the Get-FederationInformation cmdlet to ensure they explicitly pass the required domain(s) as parameters. Communicate this change to your Exchange Online administrators and support teams to avoid confusion or unexpected results. For more details, refer to the official blog post: Important Update to the Get-FederationInformation Cmdlet in Exchange Online MC1070184 — Microsoft Exchange Online: Check for usage of legacy Exchange tokens before they retire As part of Microsoft’s Secure Future Initiative, we began disabling legacy Microsoft Exchange Online tokens in February 2025. Our telemetry shows you may have temporarily re-enabled these tokens using the Set-AuthenticationPolicy Microsoft PowerShell command. Key dates June 2025: Legacy Exchange Online tokens will be permanently disabled for all tenants. Add-ins relying on these tokens—especially for user identification, Microsoft Exchange Web Services (EWS), or Microsoft Outlook REST API calls—will probably stop working. Re-enabling will only be possible through a Microsoft-approved exemption. October 2025: Full retirement of legacy Exchange Online user identity and callback tokens across all Microsoft 365 tenants with no exemptions. If your Outlook add-ins use legacy tokens, you must migrate to NAA (nested app authentication) and Entra ID tokens as soon as possible to ensure continued functionality. Recommended actions Run a scream test now. As soon as possible, temporarily disable legacy Exchange Online tokens to identify any Outlook add-ins that may break soon. This will help you discover issues before the June 2025 cutoff. For step-by-step guidance, see the Outlook legacy tokens deprecation FAQ. 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 any affected add-ins are discovered in your environment, contact their publishers to understand their migration plans. Note: If your organization has developed and published custom Outlook add-ins, you may need to coordinate updates internally. This retirement impacts all Outlook add-ins that request a legacy Exchange Online token to identify the user, or make Exchange Web Services (EWS) calls, or Outlook REST API calls. This message applies to new and classic Outlook for Windows desktop, Outlook for Mac desktop, Outlook for the web, and Outlook for iOS/Android. This message only applies to Exchange Online and doesn’t apply to Exchange on-premises. Where do I get more information? We regularly update the Outlook legacy tokens deprecation FAQ, which contains information about tools and how to upgrade add-ins. Check the Q&A section for Microsoft 365 administrators and share the FAQ with any developers who need to update custom Outlook add-ins using legacy Exchange Online tokens. Learn more Nested app authentication and Outlook legacy tokens deprecation FAQ - Office Add-ins | Microsoft Learn Turn legacy Exchange Online tokens on or off - Office Add-ins | Microsoft Learn Enable single sign-on in an Office Add-in with nested app authentication - Office Add-ins | Microsoft Learn Office-Add-in-samples/Samples/auth/Outlook-Add-in-SSO-NAA at main · OfficeDev/Office-Add-in-samples · GitHub If you have feedback for our team about tools for legacy Exchange Online tokens, please let us know in our Tenant Information Survey. MC1066337 — (Updated) Microsoft Exchange Online: Introducing ActorInfoString in Exchange Online audit logs Updated May 12, 2025: We have updated the content. Thank you for your patience. Coming soon: ActorInfoString, a new audit log field in Microsoft Exchange Online (EXO) designed to improve the accuracy, clarity, and depth of your audit logs. ActorInfoString records the true user agent responsible for each audited event, giving security and compliance teams increased visibility into actions performed in your Exchange Online environment. This update builds on the existing audit schema by capturing more granular information about clients, devices, and applications involved in audited operations. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late May 2025 and expect to complete by late May 2025. How this will affect your organization: Once enabled, ActorInfoString will appear as a new field in your Exchange Online audit logs, alongside existing fields such as ClientInfoString. This addition provides an unambiguous record of which client, device, or application performed a given operation, supporting better investigation of incidents, improved detection of suspicious activity, and strengthened compliance reporting. Existing audit schema fields, records, and integrations will remain unchanged, ensuring a seamless transition without service impact or data loss. After this rollout, change administrators will see these key improvements: Clarity: Easily reveal the true user agent behind every action in your logs. Better security: Accelerate investigation and threat detection by tracing the actual source of actions. Compliance: Enhance your audit trails to more effectively meet regulatory standards. Future-readiness: Prepare your monitoring and log analysis for evolving audit needs. Use the following to find the new field: Access the Audit Logs: Go to the Microsoft Purview compliance portal: https://compliance.microsoft.com Navigate to Audit > Audit Search Search for Exchange Online Activities: Use filters to narrow down to Exchange Online activities. You can specify date ranges, users, or specific operations. Example of how ActorInfoString should appear for admins: ee33-4930-9efd-2b7f2c8183b7","RecordType" : 50, “Resultstatus" : "Succeeded","UserKey":"1c6b6 ActorInfoString" : “Client-REST ;Client-RESTSystem;UserAgent-[NoUserAgent] [Appld-1c6b689d-1] What you need to do to prepare: No action is required before rollout. However, we recommend reviewing your log collection and analysis tools to ensure they are ready to consume the new ActorInfoString field. This update is non-disruptive and will not alter your existing audit data or integrations. We will update this message with official documentation and release notes that will provide additional details and best practices for leveraging the new field. Microsoft 365 MC1087098 — Microsoft 365: Retiring and modernizing the Semi-Annual Enterprise Channel for Windows desktop apps To help organizations stay current and benefit from the latest Microsoft 365 innovation, we are modernizing the Semi-Annual Enterprise Channel to streamline update options and align with evolving customer needs. These changes simplify channel management and encourage broader adoption of update cadences that deliver features and security updates more efficiently. This message applies to Windows desktop apps. What’s changing Semi-Annual Enterprise Channel Preview and Semi-Annual Enterprise Channel Extended will be retired Devices currently on Semi-Annual Enterprise Channel Preview will not receive updates after July 8, 2025. Support for Semi-Annual Enterprise Channel Extended will end March 10, 2026. Feature previews are now available through Current Channel and Monthly Enterprise Channel. Semi-Annual Enterprise Channel support will be simplified Starting July 8, 2025, the Semi-Annual Enterprise Channel will move to a 6+2-month lifecycle (6 months of feature updates followed by 2 months of rollback support). This channel will be reserved for specialized non-attended scenarios where more frequent updates are not practical. Monthly Enterprise Channel improvements Starting June 1, 2025, the Monthly Enterprise Channel will support N, N-1, and N-2 builds, giving admins greater flexibility during deployment validation. All update channels will continue to receive security updates on Patch Tuesday. What you need to do Now is the time to evaluate your update strategy: Migrate devices off the Semi-Annual Enterprise Channel Preview to ensure they continue receiving security updates. Move interactive or user-facing devices to the Monthly Enterprise Channel for a more modern, validated experience. For any remaining devices on the Semi-Annual Enterprise Channel, plan to follow the twice-yearly update cycle in January and July. Learn more: Overview of update channels for Microsoft 365 Apps MC1081598 — Microsoft 365 web app: Name update to “Microsoft 365 Copilot” and updated UI Microsoft 365 Roadmap ID 494998 Beginning late June 2025, the Microsoft 365 app will update to the Microsoft 365 Copilot app, including a refreshed navigation pane and simplified UI. These updates apply to the web endpoint only, accessible from: https://www.ohome.apps.mil Please refer to MC1051092 for previously communicated updates for the Microsoft 365 app that these updates will build on. When this will happen: General Availability (DoD, web only): We will begin rolling out late June 2025 and expect to complete by early July 2025. How this will affect your organization: All users will see the new app name, Microsoft 365 Copilot, and a refreshed UI. The individual user experience in the Microsoft 365 Copilot app will vary based on if a user has a Microsoft 365 Copilot license. The Microsoft 365 Copilot license will be available for DoD in late June 2025. Users without a Microsoft 365 Copilot license: Refreshed Navigation Pane – The left navigation pane will include essential modules like Search, Create, and Apps. Users can pin and unpin apps to customize their workspace. Search – With this update, Search replaces the Home module. Search will have a refreshed UI, displaying key files in dedicated sections for easier access and a search bar to help them quickly find what they need. User with a Microsoft 365 Copilot license: Includes the updates listed above along with additional specific modules for users with a Microsoft 365 Copilot license: Chat – Chat has been streamlined for a simplified experience with an updated collapsable left navigation page for quick access to chat history and Copilot pages. The input box will be located in the center of the UI with prompt suggestions below it. Users will have access to Work chat to reason over their files and web search (grounding) in Work chat will be off by default. A dedicated Web chat will become available later and will be communicated separately. Notebooks – Copilot can ground on the contents of a user’s notebook, to give them more relevant, contextualized responses based on prompts. Users can gather information from chats, meetings, pages, and files, as well as organize and store important documents, notes, and tasks. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. Admins can manage the Microsoft 365 Copilot app for users with a Microsoft 365 Copilot license with the following controls. MC1081582 — Updates to the Microsoft 365 Copilot app UI (Web only) Microsoft 365 Roadmap ID 495116 Beginning late June 2025, the Microsoft 365 Copilot app will update to include a refreshed navigation pane and simplified UI. These updates apply to the web endpoint only. When this will happen: General Availability (GCC, Web only): We will begin rolling out late June 2025 and expect to complete in July 2025. How this will affect your organization: The individual user experience in the Microsoft 365 Copilot app will vary based on if a user does not have access to Copilot, can access Microsoft 365 Copilot Chat, or has a Microsoft 365 Copilot license. Users without access to Copilot: Refreshed Navigation Pane – The left navigation pane will include essential modules like Search, Create, and Apps. Users can pin and unpin apps to customize their workspace. Search – With this update, Search replaces the Home module. Search will have a refreshed UI, displaying key files in dedicated sections for easier access and a search bar to help them quickly find what they need. Users with access to Microsoft 365 Copilot Chat (please refer to MC1036580 for more details on Copilot Chat for GCC): Includes the updates listed above along with additional modules for Copilot Chat users: Chat – Chat has been streamlined for a simplified experience with an updated collapsable left navigation page for quick access to chat history and Copilot pages. The input box will be located in the center of the UI with prompt suggestions below it. Users will have access to Web chat and web search (grounding) will be off by default. User with a Microsoft 365 Copilot license: Includes the updates listed above along with additional modules for users with a Microsoft 365 Copilot license: Chat – In addition to what’s listed above, Chat for users with a Microsoft 365 Copilot license will have both Work and Web chat. Web search (grounding) is off by default in both Web and Work chat unless you have taken action using the Web Search policy. Please refer to MC1036562 for Web chat availability for Microsoft 365 Copilot licensed users in GCC. Notebooks – Copilot can ground on the contents of a user’s notebook, to give them more relevant, contextualized responses based on prompts. Users can gather information from chats, meetings, pages, and files, as well as organize and store important documents, notes, and tasks. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. Admins can manage the Microsoft 365 Copilot app using the following controls: MC1056996 — (Updated) Microsoft Excel: Extending support for Insights Services (GCC High, DoD) Microsoft 365 Roadmap ID 488142 Updated May 7, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Excel: Support for the Analyze Data feature, which will be found on the Data tab This message applies to Excel for Windows desktop, Excel for Mac desktop, and Excel for the web. When this will happen: General Availability (GCC High, DoD): We will begin rolling out late June 2025 (previously late April) and expect to complete by late August 2025 (previously late June). How this will affect your organization: Analyze Data can generate charts and graphs that may provide insights and answer questions you may have about your data: 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 or after the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Analyze Data in Excel - Microsoft Support MC1051092 — (Updated) Microsoft 365 web app: Updated experience (DoD) Updated May 6, 2025: We have updated the content. Thank you for your patience. Coming soon: An updated experience for the Microsoft 365 web app at https://www.ohome.apps.mil When this will happen: General Availability (DoD): We will begin rolling out late May 2025. How this will affect your organization: This rollout includes these key changes: Microsoft 365 apps that were pinned to the left navigation will be available in the Apps tab. Profile and Settings buttons will move from the top right to the bottom left corner. New content types and templates will be added to the Create tab. Search bar will move from the top header to the Home tab. Organization branding will be removed along with the top header. This change will be on by default. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. MC1051087 — (Updated) Microsoft 365 web app: Updated experience (GCC High) Updated May 6, 2025: We have updated the content. Thank you for your patience. Coming soon: An updated experience for the Microsoft 365 web app at https://www.office365.us When this will happen: General Availability (GCC High): We will begin rolling out late May 2025. How this will affect your organization: This rollout includes these key changes: Microsoft 365 apps that were pinned to the left navigation will be available in the Apps tab. Profile and Settings buttons will move from the top right to the bottom left corner. New content types and templates will be added to the Create tab. Search bar will move from the top header to the Home tab. Organization branding will be removed along with the top header. This change will be on by default. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. Documentation - Office 365 IP Address and URL web service May 30, 2025 - GCC April 30, 2025 - GCC High April 30, 2025 - DODMay and April 2025 - Microsoft 365 US Public Sector Roadmap Newsletter
Purview Labeling improvement for non-Office/PDF files using endpoint DLP Exchange Online Exchange Server Security Changes for Hybrid Deployments Direct Send Control in Exchange Online – Preview GCC, GCCH, DOD Teams Personal Meeting Templates – GCC & GCCH June, DOD August Microsoft 365 Copilot Copilot Wave 2 Spring Release - GCC Discover the Future of AI in Government Are you ready to explore the transformative power of artificial intelligence in the public sector? Join us as we delve into the key themes discussed in the recent seminar, "Microsoft AI for Government," led by Jason Payne, Chief Technology Officer for Microsoft Federal. What’s New in Microsoft 365 Copilot for Government | Microsoft Community Hub The AI-powered capabilities of Microsoft 365 Copilot are expanding across government environments. Whether you’re in GCC, GCC High, or DoD, here’s what you need to know about upcoming availability, what’s changing, and how to prepare. What’s New in Microsoft Teams | April 2025 Brand impersonation phishing protection first launched for commercial users in January, and now is available for the GCC, GCC-H, and DoD audiences. VDI users can join optimized meetings with people in other Microsoft 365 cloud environments (e.g., a user in GCC-H joining a meeting in commercial, GCC, or DOD) through three options: authenticated access via cross-cloud meeting connection, authenticated access using a guest account, or anonymous access. These scenarios require Slimcore-based optimization. Licensing and Pricing Updates for Teams Phone and Power BI Coming July 1, 2025 On April 1, 2025, we updated pricing for commercial customers of Teams Phone and Power BI. Beginning July 1, 2025, Microsoft will implement licensing and pricing updates for new and renewing US government customers across all government cloud deployments: GCC, GCC High, and DoD. 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) 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 MC1062451 — Microsoft SharePoint: Customize your sites with multi-color themes Microsoft 365 Roadmap ID 489833 and Roadmap ID 490062 Coming soon for Microsoft SharePoint: Site owners can apply a multi-color theme to the site. We will offer these multi-color themes out of the box. Site owners will create the themes using the Site branding feature, or the brand manager will use branding from your organization if you have set up a brand center in the Microsoft 365 admin center. NOTE: The brand center app requires the use of a public content delivery network (CDN) available in the Worldwide environment. CDN is not available in the GCC, GCC High, or DoD environments. When this will happen: These releases will roll out to Worldwide (with brand center capability) and to GCC, GCC High and DoD (without brand center capability): Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability: We will begin rolling out early June 2025 and expect to complete by mid-June 2025. How this will affect your organization: This feature introduces multi-color themes that support multiple color combinations in a theme. In addition to custom themes, eight new out-of-the-box site themes will be available after this rollout. The theme colors will show up in the site header and site footer, applied by site managers. The theme colors will also show up in section backgrounds, the rich text editor (text web part), and Design ideas, all edited by page authors. This feature will be available by default. Edit a multi-color theme in Site branding: Apply an out-of-box multi-color theme in Change the look: Apply theme colors to a header in Change the look: 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. Learn more Site theme - SharePoint in Microsoft 365 | Microsoft Learn Site branding - Microsoft Support MC1061109 — Microsoft SharePoint and Microsoft OneDrive: New PDF compression feature Microsoft 365 Roadmap ID 487440 Coming soon: Users will be able to use the new Compress feature to reduce the file sizes of PDFs stored on Microsoft OneDrive for the web or Microsoft SharePoint. Users can choose from three different compression levels. When this will happen: Targeted Release: We will begin rolling out late April 2025 and expect to complete by early May 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early May 2025 and expect to complete by mid-May 2025. How this will affect your organization: To compress PDF files for a smaller size: Open a PDF in OneDrive for the web (in SharePoint, go to the document library and choose Preview): Select the Compressbutton at the top of the screen: Select a compression level and then select Save a copyto save the compressed file: A progress notification will appear at the bottom of the screen. After the compression is complete, select Open from the notification to view the compressed file: FAQ What is the quality and subsampling for each compression level? We offer three levels of image compression. All use lossy compression and chroma subsampling to reduce file sizes while maintaining visual quality. The options are: Light compression: Apply 4:2:0 color subsampling and reduce 25% of image pixels. Medium compression: Apply 4:2:0 color subsampling and reduce 50% of image pixels. Heavy compression: Apply 4:2:0 color subsampling and reduce 75% of image pixels. Users can compress one PDF at a time. The original file must be smaller than 300 MB. This feature is on by default. What you need to do to prepare: Note: Some users may see this feature before other users in your organization. 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. Before rollout, we will update this post with new documentation. MC1055557 — SharePoint Online: Content Security Policy Control in Tenant Administration SharePoint Online Tenant Administrators can now allow script sources for modern pages in SharePoint sites. This feature is particularly useful in scenarios where modern pages have custom code that loads scripts (e.g., TypeScript code) from external sources like a content delivery network (CDN). SharePoint will now report to administrators where sources that have not been allowed are loaded from, providing a way for administrators to identify those sources and take action. Tenant Administrators can also enforce browsers to only load scripts from allowed sources. This behavior can be enabled using SharePoint Online Management Shell. When this will happen: Targeted Release: We will begin rolling out on late March 2025 and expect to complete by early April 2025. General Availability (Worldwide): We will begin rolling out on late April 2025 and expect to complete by late April 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out on late April 2025 and expect to complete by mid-May 2025. How this will affect your organization: Tenant Administrators will have the option to control and govern where custom code loads scripts and, if needed, enforce browsers to only load scripts from trusted sources. A new "Trusted script sources" page will give administrators control over which source can be trusted to load scripts. What you need to do to prepare: This rollout will happen automatically with no admin action required. MC1055555 — Microsoft SharePoint Online: We will remove retired DISCO and WSDL web pages ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We recommend using Microsoft Graph for remote operations where possible. We will remove these pages from Microsoft SharePoint Online starting mid-August 2025 and ending in mid-September 2025. Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online - Microsoft 365 Developer Blog MC1040544 — (Updated) Microsoft SharePoint: Enhancements to Restricted access control (RAC) Microsoft 365 Roadmap ID 483028 Updated March 26, 2025: We have updated the content. Thank you for your patience. Coming soon for Microsoft SharePoint: New enhancements for the restricted access control (RAC) policy for SharePoint admins to restrict access to SharePoint sites, including managing Microsoft 365 group-connected sites with Microsoft 365 groups or Microsoft Entra security groups. Customers with SharePoint Advanced Management (SAM) capabilities in their tenants can use the RAC policy. When this will happen: Public Preview: We will begin rolling out late March 2025 and expect to complete by late April 2025. General Availability (Worldwide): We will begin rolling out early May 2025 and expect to complete by late May 2025. How this will affect your organization: Admins can go to SAM or use Microsoft PowerShell cmdlets to configure the updated RAC policy. The enhanced policy will be available by default for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. Only awareness on how they could utilize this policy in their tenant. Learn more: Restrict SharePoint site access with Microsoft 365 groups and Microsoft Entra security groups - SharePoint in Microsoft 365 | Microsoft Learn (will be updated before rollout) MC1040543 — Retiring "Shared with Us" Feature in SharePoint Teams sites We are retiring the "Shared with us" feature on SharePoint Teams sites, which provided a centralized view of files and folders shared with site members. When this will happen: We will begin retirement mid-April 2025 and expect to complete by mid-May 2025. Are there any recommended alternatives to the "Shared with Us" feature: While there is no direct replacement for this feature, users can leverage existing tools in OneDrive and SharePoint to manage shared content effectively: OneDrive "Shared with me":Users can view files and folders that have been shared with them in OneDrive > Shared for a personalized view of shared content. Microsoft Teams and email notifications:When files are shared via Teams or Outlook, users receive notifications and can access shared content directly from their Teams chat and email. What you need to do to prepare: No action is required, but we recommend informing your users about this change and guiding them on how to find shared content using the recommended alternatives above. We understand that changes to features can impact workflows, and we appreciate your understanding as we focus on improving SharePoint’s overall experience. MC1034592 — SharePoint Online: Table toolbar Microsoft 365 Roadmap ID 394278 In SharePoint Online, Table toolbar is a new toolbar that allows authors to use table functionality. Table Styles was previously available on the text webpart. All the Table Styles styles are now available via the Table toolbar, including some new table features like merge, split, add space before and after, and others. With the introduction of Table toolbar, users see a menu that is always in focus when working on a table. The Table toolbar will automatically adjust by expanding or compressing based on the section layout used. When compressed, the table options move into the overflow (...) button. The new table toolbar will be available in SharePoint and Viva Amplify. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We began rolling out late February 2025 and expect to complete by late March 2025. How this will affect your organization: Within the text web part, users will be able to insert a table and, once the table is inserted, users will see the Table toolbar that is always in focus. Within Table toolbar, users can do all the table editing and formatting that is already available, including change layout, add/delete row/columns, and so on along with any new table features that may be added in the future. Current experience Future experience d 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. MC1031266 — Microsoft SharePoint: Microsoft 365 Copilot customers now have SharePoint Advanced Management capabilities We announced at Ignite (November 2024) that SharePoint Advanced Management will be included with Microsoft 365 Copilot licenses in early 2025. We are pleased to announce that your tenant now includes all SharePoint Advanced Management (SAM) capabilities. Learn more: Get ready for Microsoft 365 Copilot with SharePoint Advanced Management - SharePoint in Microsoft 365 | Microsoft Learn A Microsoft 365 Copilot license is required to use this feature. When this will happen: General Availability (Worldwide): Available now. How this will affect your organization: In the SharePoint admin center, the SharePoint Advanced Management page will display this message: “Your SharePoint Advanced Management subscription is now enabled:" Important recommendations from the product team: The oversharing baseline report using permissions is the first significant step in understanding the current oversharing status in your entire tenant and setting up an appropriate baseline. This report is available in Microsoft PowerShell onlyand is easy to miss because it is not present in SAM. We recommend using PowerShell and initiating the report as soon as possible. After you have the report, you can start to focus on clean-up and remedial actions. Remedial actions such as Restricted access control, Restricted content discovery(to exclude content from appearing in Copilot search), and Site access review are documented in Microsoft SharePoint Premium - SharePoint Advanced Management overview - SharePoint in Microsoft 365 | Microsoft Learn SAM is available by default for admins to configure. What you need to do to prepare: 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. MC1028318 — Microsoft SharePoint Online Management Shell will replace IDCRL authentication protocol with OAuth Starting with the March 28, 2025 release of the Microsoft SharePoint Online Management Shell (SPO Admin PowerShell), we will replace the IDCRL (Identity Client Run Time Library) Authentication protocol with OAuth (modern authentication protocol). This update is part of our ongoing efforts to enhance security and adopt modern authentication practices. To enhance your security, please install the March 28, 2025 or later version of SharePoint Online Management Shell from Download SharePoint Online Management Shell from Official Microsoft Download Center. When this will happen: Starting with the March 28, 2025 version of SharePoint Online Management Shell, requests using the Connect-SPOService cmdlet will be automatically authenticated with the new OAuth protocol. This update does not change existing admin flows and no other admin action is required. We will also display a warning message about this change in the March 28, 2025 or later releases of SharePoint Online Management Shell. How this will affect your organization: How to check your current version of SharePoint Online Management Shell (SPO Admin PowerShell) Method 1: Using PowerShell Open PowerShell. Run this command: Get-Module -Name Microsoft.Online.SharePoint.PowerShell -ListAvailable | Select-Object Name, Version This will display the installed version of the SharePoint Online Management Shell module. Method 2: Using Installed Programs List Open the Control panelin Windows. Go to Programs and Features. Look for Microsoft SharePoint Online Management Shell in the installed programs list. The version number will be displayed there. This warning message in SharePoint Online Management Shell informs admins that we have replaced IDCRL with OAuth: What you need to do to prepare: This rollout will happen automatically by the specified dates 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. Please install the March 28, 2025 or later version of SharePoint Online Management Shell from Download SharePoint Online Management Shell from Official Microsoft Download Center. Learn more: Can't connect to SharePoint Online - SharePoint | Microsoft Learn (will be updated before rollout) MC1026218 — (Updated) Microsoft OneDrive and Microsoft SharePoint: New annotation layout and tools for editing PDFs Microsoft 365 Roadmap ID 483156 Updated April 8, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft OneDrive and Microsoft SharePoint: A new PDF annotation layout that features a more intuitive design. After this rollout, all annotation tools will be in a single row at the top of the screen, including a new type of eraser that can remove pen and highlighter annotations pixel by pixel. This message applies to One Drive for the web and SharePoint Online. When this will happen: Targeted Release: We will begin rolling out early April 2025 (previously late March) and expect to complete by mid-April 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-April 2025 (previously late March) and expect to complete by early May 2025 (previously mid-April). How this will affect your organization: To use the new annotation layout: Find the PDF saved in OneDrive or Microsoft SharePoint and select the PDF to open it. Select Edit at the top right of the screen to access the annotation tools. Note: When editing in OneDrive or SharePoint, ignore the Edit in appoption in the dropdown menu next to Edit, which will open the PDF in another PDF tool such as Adobe Acrobat. All annotation tools are found at the top of the screen. To erase existing pen or highlighter annotations: Find the PDF saved in OneDrive or SharePoint and select the PDF open it. Select Edit at the top right of the screen to access the annotation tools. Select Eraser from the annotation toolbar and left click with the mouse to delete with precision (pixel by pixel). Select Save changesat the top left of the screen. To delete an entire pen or highlighter annotation, choose one of these options: Select an existing annotation and then select the Deletekey on the keyboard. Select the trash icon at the top left of the selected annotation. The Eraser tool does not work for Text annotations. 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 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. MC1025216 — (Updated) Microsoft OneDrive: New naming convention for folder shortcuts Updated March 27, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon: New naming logic for Microsoft OneDrive folder shortcuts. We will add the site name or the user's OneDrive to all new folder shortcuts. Before this rollout, OneDrive shortcuts have the same name as the folder. After this rollout, the shortcut will also include the name of site where there the original folder exists. If a colleague shares a folder with user, and the users creates a shortcut for that folder, the shortcut will include the name of the person who owns the folder. This change will help you easily identify the source of the folder shortcut and differentiate it from other content in your OneDrive > My Files. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late June 2025 (previously mid-March) and expect to complete by mid-July 2025 (previously mid-April). How this will affect your organization: After this rollout, any new folder shortcuts you add to your OneDrive > My Files will follow the new naming convention. For example: If you go to a SharePoint site named Marketing Teamand create a shortcut to a folder named Project File, the shortcut will appear as Marketing Team – Project Files in your OneDrive > My Files. If you add a shortcut to a folder named Blog postfrom Mona Kane’s OneDrive, the shortcut will appear as Mona Kane’s files – Blog post in your OneDrive > My Files. Key points The new naming logic will apply only to new shortcuts added after this rollout. Existing shortcuts will retain their current names. This change will be reflected in OneDrive for the web, OneDrive for iOS/Android, Microsoft File Explorer, Mac Finder, and Microsoft Teams. This change will be available by default. Examples of the new naming logic for folder shortcuts in OneDrive: What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Learn more: Add shortcuts to shared folders in OneDrive for work or school - Microsoft Support (will be updated before rollout) MC1024394 — (Updated) Microsoft SharePoint: New card animation feature for Pages, News, and Microsoft Viva Amplify Microsoft 365 Roadmap ID 481510 Updated April 9, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for Microsoft SharePoint: Cards can be animated for some web parts (Editorial cards, Images, and People) in SharePoint Pages, News, and Microsoft Viva Amplify. When this will happen: Targeted Release: We will begin rolling early April 2025 (previously out late-April) and expect to complete by early May 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-April 2025 (previously early May) and expect to complete by early May 2025 (previously late May). How this will affect your organization: This feature will be enabled by default for new cards created after the feature is released. Users can disable card animation in the web part property pane. To add animation to existing web parts, users can enable the setting in the web part property pane. To preview the card animation, view the published page or use Preview mode. Pages and web parts created before this rollout are not impacted by this change. 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. MC1017119 — (Updated) SharePoint: OneDrive and SharePoint – Protect PDF with password Microsoft 365 Roadmap ID 482193 Updated April 16, 2025: We have updated the title and content. Thank you for your patience. SharePoint and OneDrive users can now secure their PDF files by adding protection that restricts unauthorized access through OneDrive Web. This feature allows you to set an open password, which is required to access the PDF, or an owner password, which sets permissions for actions such as printing or editing the document. This ensures your files remain secure and only accessible to authorized individuals When this will happen: Targeted Release: We will begin rolling out late April 2025 and expect to complete by early May. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early May 2025 and expect to complete by late May 2025 (previously late March). 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. To set up an open password: Open a PDF you have saved in OneDrive or SharePoint document library, Click the lock icon located at the top left of the screen 3.Under Security, enter matching passwords. Click Save as to password protect this document, Choose the location where you want to save the file and click Save here. A notification will appear at the bottom of the screen, indicating that a new file has been successfully saved. To set up an owner password: Open a PDF you have saved in OneDrive or SharePoint document library, Click the lock icon located at the top left of the screen, Under Protection, check the Grant permissions box. Under Grant permission, check the box for the permissions you want to allow on this document. Type matching owner passwords and then click Save as to set permissions for this document, Choose the location where you want to save the file and click Save here, A notification will appear at the bottom of the screen, indicating that a new file has been successfully saved. 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. FAQ Will password protection overwrite my current PDF? No, we currently only allow the "Save as" option, so the original PDF will remain intact. Can I see the same permission set on the same PDF document using other apps? Yes, users are able to view the same permission settings, and the same restrictions are applied when they view the PDF within OneDrive and SharePoint. What you need to do to prepare: Note: Some users may see this feature before other users within your organization. MC1013464 — (Updated) We will remove the EEEU sharing permission from root web and default document library in OneDrive’s Updated April 17, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 17, 2025 (previously April 10) 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 — (Updated) SharePoint Online: Updates to Microsoft Lists forms Microsoft 365 Roadmap ID 124865 Updated April 4, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 April 2025 (previously late March). 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. MC1002417 — (Updated) Microsoft SharePoint: The "spaces" feature will retire Updated April 21, 2025: We will be rolling out the change to prevent users from activating the SharePoint spaces feature in site settings (or using PowerShell) starting May 15th. It will still be possible to disable the feature using this dialog. Users attempting to enable the feature will receive an error message indicating that the Spaces feature is being deprecated and cannot be enabled at this time. Sites with the feature already enabled will continue to function with the feature enabled. 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 March 10, 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 late March 2025 (previously mid-February) and expect to complete by mid-April 2025 (previously late March). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-April 2025 (previously late March) and expect to complete by early May 2025 (previously late April). 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. MC974358 — (Updated) Microsoft SharePoint admin center: New "App insights" feature will be in Public Preview Microsoft 365 Roadmap ID 417481 Updated March 26, 2025: We have updated the rollout timeline below. Thank you for your patience. 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-May 2025 (previously early May) and expect to complete by late May 2025 (previously late March). 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 licenses. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. 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 MC922630 — (Updated) Microsoft OneDrive: We will remove the "EnableHoldTheFile" group policy Microsoft 365 Roadmap ID 429875 Updated April 3, 2025: We have updated the rollout timeline below. We are now one month away from this change taking effect. 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 May 2025 (previously early April) and expect to complete by late May 2025 (previously late April). 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 April 3, 2025: We have updated the rollout timeline below. We are now one month away from this change taking effect. 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 early May 2025 (previously April). 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. MC912181 — (Updated) Microsoft SharePoint: Add approvals to any document library Microsoft 365 Roadmap ID 420336 Updated April 8, 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 April 2025 (previously late March). 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: Enable configured approvals: Approvals column: Disable configured approvals: This feature is on by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. Inform your users of the 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. Microsoft Viva MC1056267 — Microsoft Viva Connections: New Folder card in Dashboard Microsoft 365 Roadmap ID 408536 Coming soon for Microsoft Viva Connections: A new Folder card in the Connections card gallery will provide users with a quick view of the document library files on the dashboard. When this will happen: General Availability (Worldwide, GCC, DoD): We will begin rolling out mid-April 2025 and expect to complete by late April 2025. How this will affect your organization: After this rollout, users will find a new Folder card that provides a quick view of the document library files on the dashboard: 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. Learn more: Available dashboard cards in Viva Connections | Microsoft Learn (will updated before rollout) Microsoft Teams MC1062452 — Microsoft Teams: Join as attendees in Microsoft events from Teams Rooms on Windows Microsoft 365 Roadmap ID 484125 Microsoft Teams Rooms on Windows can now join Microsoft events (webinars, town halls, structured meetings) as attendees. You can attend directly from the invited Teams Room with the same features that attendees have for all events. This is available only in Teams Rooms Pro. When this will happen: General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (GCC): We will begin rolling out late May 2025 and expect to complete by mid-June 2025. General Availability (GCC High): We will begin rolling out late June 2025 and expect to complete by mid-July 2025. General Availability (DoD): We plan begin rolling out late August 2025 and expect to complete by mid-September 2025. How this will affect your organization: Recently we announced official support with Teams Rooms on Windows devices as a presenter in Teams Townhall & Webinars ensuring an optimal experience for every event. Starting from app version 5.2.115.0, Teams Town halls and Webinars are exclusively available in rooms with a Teams Rooms Pro license. Today, Teams Rooms on Windows with a Pro license can now join events as attendees, making it easier to schedule watch parties for your organization and enjoy an official supported experience. Please note that joining events from Teams Rooms with a non-Pro license will not be supported. This feature will be enabled 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. MC1061725 — Microsoft Teams: New DVR (digital video recording) capabilities for town halls on iOS and Android Microsoft 365 Roadmap ID 486694 Coming soon for Microsoft Teams for iOS/Android: New DVR (digital video recording) functionality for users who attend town halls. This feature is available for town hall instances from all organizers, regardless of the license assigned to the organizer. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late May 2025 and expect to complete by late May 2025. General Availability (GCC High, DoD): We will begin rolling out early June 2025 and expect to complete by early June 2025. How this will affect your organization: This new feature will allow town hall attendees to interact with a live streaming town hall in the same way as they would interact with recorded content when viewing on desktop or web. DVR functionality in the town hall enables event attendees to pause and move forward or back in a town hall, navigate to any previously streamed timestamp, and other abilities that make it more convenient and easier for users to interact with a town hall and digest the content being presented. To get started, attendees will touch the screen over the content being presented in the town hall and the DVR controls will appear. In this image, the live town hall is on the left, and the DVR view is on the right: The user can pause, play, skip 10 seconds forward or backward. The user can also control the volume of the content using volume control. The user can also jump to any point of time in the past from the start of an event. The user can catch up with the content and join the live event by selecting the Watch live button. The town hall window will remain open for 24 hours after the end of the event. 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 dates with no admin action required before the rollout. Review your current configuration to assess the impact on 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) MC1059676 — Microsoft Teams: Easily call in a presenter from the roster for town halls and webinars Microsoft 365 Roadmap ID 485812 This feature provides the ability for organizers and presenters to quickly add a missing presenter to an ongoing Teams town hall, webinar, or structured meeting even if the missing presenter was not originally included in the event scheduling form. If the organizer or presenter realizes they've forgotten to add someone as a presenter, they can easily call them in directly from the participant roster. From the roster, organizers can choose whether to call them in as a presenter or attendee even if they are not already attending the session as an attendee. Organizers and presenters can only promote someone as a presenter if they are already in the session. With just a few clicks, the missing presenter is instantly promoted to presenter status, allowing them to join the green room, share content, control the presentation, or interact with the meeting participants. When this will happen: Targeted Release: We will begin rolling out late May 2025 and expect to complete by early June 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (GCC High, DoD): We will begin rolling out late June 2025 and expect to complete by early July 2025. How this will affect your organization: This feature will automatically be available to use once it releases. To use this new feature, organizers and presenters must go to the roster and call in someone into the event. 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. MC1059675 — Microsoft Teams: Pop out live captions and Real-Time Text (RTT) in Teams meetings Microsoft 365 Roadmap ID 484113 We’re introducing the ability to pop out live captions (including live translated captions) and Real-Time Text (RTT) in Microsoft Teams meetings and calls. This new functionality gives users more flexibility and control over how they view text-based communication during meetings, supporting both accessibility and multitasking needs. When this will happen: Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide, GCC): We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (GCCH): We will begin rolling out early June 2025 and expect to complete by mid-June 2025. General Availability (DoD): We will begin rolling out early July 2025 and expect to complete by mid-July 2025. How this will affect your organization: After the rollout, users will see a pop-out icon on the live captions and RTT interface during meetings and calls. This feature will be on by default. When popped out, captions and RTT will open in separate windows that users can drag, resize, and position anywhere on their screen. This allows users to customize their meeting layout and view captions or RTT in a way that works best for their workflow or accessibility needs. Live caption pop-out RTT pop-out What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required. Please notify your users about this change and update any relevant training materials or documentation to reflect the new pop-out experience for captions and RTT. MC1059674 — Microsoft Teams: Real-Time Text (RTT) in Teams meetings and calls Microsoft 365 Roadmap ID 484119 We’re introducing Real-Time Text (RTT) support in Microsoft Teams meetings and calls, available on both desktop and mobile platforms. RTT is an accessible communication method that transmits text character by character as it is typed, enabling more immediate and responsive text-based conversations. This enhancement supports inclusivity by providing an alternative communication channel for users who are deaf or hard of hearing, neurodiverse, or have speech-related disabilities. When this will happen: Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide, 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 early June 2025 and expect to complete by mid-June 2025. General Availability (DoD): We will begin rolling out early July 2025 and expect to complete by mid-July 2025. How this will affect your organization: Once this feature is enabled by your organization, users will be able to turn on Real-Time Text (RTT) during Teams meetings and calls. To access it, go to the meeting toolbar, select More > Speech and language > Enable RTT. When RTT is turned on, it will be enabled for everyone in the meeting. As you type, your message will instantly appear on the screen - letter by letter - so others can read it in real time. This creates a faster and more natural way to communicate through text, especially compared to standard chat. RTT is designed to improve accessibility and also supports users who prefer typing instead of speaking. It can be used together with other features like captions or chat to create a more inclusive and flexible meeting experience. Note: Once RTT is turned on in a meeting, it stays on for the rest of the meeting and cannot be turned off unless everyone leaves and rejoins. What you need to do to prepare: This rollout will happen automatically, and no admin action is required. The RTT policy is enabled by default at the tenant level. We recommend informing your users about this new feature, especially those who may benefit from enhanced accessibility options. You may also want to update any internal documentation or training materials to include guidance on how to use RTT in Teams meetings and calls. MC1059673 — Microsoft Teams: Expanded and enhanced peripheral auto-association support for Bring Your Own Device (BYOD) spaces Microsoft 365 Roadmap ID 486693 Updated April 23, 2025: We have updated the timeline below. Thank you for your patience. Additional room and desk peripherals, including docking stations and webcams, are supported in BYOD spaces (including bookable desks), enabling users to seamlessly connect and utilize audio and video peripherals for a better experience. If the space is licensed, admins get an expanded view and insightful reports for peripherals associated with Bring Your Own Device (BYOD) spaces in the Pro Management portal. When this will happen: Targeted Release: We will begin rolling out early June 2025 and expect to complete in mid-June 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: Docking stations and webcams will now begin to appear in the Pro Management portal inventory device page, crowdsourced from the Teams desktop app. These peripherals can then be manually or automatically associated to BYOD rooms or bookable desks to automate and improve BYOD/Desk UX and provide admin insights into room UX quality. BYOD auto association will begin to receive signals and auto-associate these new peripherals to BYOD rooms. This process automatically builds a full view of your inventory for you, including what peripherals are currently located in which BYOD rooms. As a result, BYOD and Bookable Desks end user experiences will automatically activate for any user who plugs in a peripheral associated to a BYOD room or desk. These user experiences are designed to adapt the Teams desktop client to solve common user issues in rooms and desks, and includes but is not limited to the following features: (Rooms) Auto-select Room AV peripherals so that users don't accidentally use their laptop speaker and mic in a meeting room. (Rooms) Shared display modeto protect confidential information and present clean output without meeting controls or presenter's notes to the room display. (Rooms) Speaker Attribution so transcript (and Microsoft 365 Copilot) know who is speaking in your meeting. (Rooms) Disable voice isolation so others in the room can be heard. (Rooms) Room Node in participant roster. (Desks) Auto-booka desk upon peripheral plug in. What you need to do to prepare: Inform your users about the experiences that will be automatically activated for them when they plug in to a peripheral that has been associated to a room or a desk. These changes are to make their meeting room and desk experiences better. If you do not want end user experiences to automatically activate for a user, please refer to the admin documentation for BYOD rooms or desks. If you do not want peripherals to auto associate to rooms, automatically building your inventory for you, please disable this in settings for the Pro management portal. MC1059667 — Action required: Classic Microsoft Teams end of availability starts July 1, 2025 Starting July 1, 2025, classic Microsoft Teams on Mac and Windows desktops will be unavailable to use as mentioned in End of availability for classic Teams client - Microsoft Teams | Microsoft Learn. To avoid any business continuity issues, you must upgrade to new Teams or use Teams on the web at https://teams.microsoft.com. How this will affect your organization: Starting July 1, 2025, classic Teams users will be blocked from using classic Teams. Users will not be able to dismiss the blocking message or use the classic Teams desktop app. What you need to do to prepare: Use this scriptto find Windows devices that need to be upgraded to new Teams. While the main purpose of the script is to identify issues before installation of new Teams, it can also be used to detect devices running unsupported OS for new Teams Installation. Upgrade users as soon as possible to the new Teams app. Learn more about switching to new Teams. Prerequisites for new Teams installation: Windowsand Mac. Published MC posts for reference MC783985 / Classic Teams Timelines for end of support and end of availability,published April 2024 MC791446 / Classic Microsoft Teams timelines for end of support and end of availability (GCC and GCC High),published May 2024 MC791445 / Classic Microsoft Teams timelines for end of support and end of availability (DoD),published May 2024 Thank you for being a valued Teams customer. Learn more Pre-installation script for new Teams client - Microsoft Teams | Microsoft Learn The Prerequisites for target computerssection of Bulk deploy the new Microsoft Teams desktop client - Microsoft Teams | Microsoft Learn MC1057717 — Microsoft Teams Phones: Users can assign shared lines, call queues, and call transfer key to line keys Microsoft 365 Roadmap ID 486829 Coming soon for Microsoft Teams Phone devices: We are excited to announce the upcoming availability of shared line, collaborative delegation, call queues and call transfers on line keys on Teams certified phone devices. Line keys on phone devices address the pain point of navigating through multiple menus to manager calls, offering enhanced call management where users can manage multiple calls effectively, increased productivity and improved user experience. For shared line and collaborative delegation, this feature will enable you to assign shared lines/collaborative delegation lines to a line key and view the boss/delegates and members of the group (in case of collaborative delegation) along with their presence on Teams Phone devices. This feature allows delegates to pick up calls on behalf of the boss or members of the group (in case of collaborative delegation) by pressing the line key and join active calls. Also, users will be able to assign the transfer action to the line key, enabling them to transfer active calls to specific contacts by pressing that line key. Lastly, after assigning call queues to the line key users can view the status of call queue whether busy or available and receive calls by pressing line key. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (GCC High, DoD): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: This change will be on by default. Left: Shared line assignment on line keys. Right: Transfer assignment on line keys: What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. To access the new features, ensure that your Teams phone devices are updated with the latest application. These features will only be available with the latest application update. Learn more: Set up line keys on your Microsoft Teams phone - Microsoft Support Before rollout, we will update this post with new documentation. MC1057714 — Microsoft Teams: We will retire SMS invitations from Teams to external partners Effective May 17, 2025, we will retire the option for users to invite external partners to Microsoft Teams by sending an SMS to their phone number to join Teams and continue the conversation. We are retiring this feature to provide a more consistent experience. Organizations can continue to use emails to invite partners outside of their organizations for external teamwork. Alternatively, customers can sign up for a two-way SMS calling plan to continue inviting external partners to Teams by sending an SMS to their phone number. This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change, update relevant documentation as appropriate, and share alternatives for users to invite external partners to Teams. Learn more Add or invite people outside your org to a chat in Microsoft Teams - Microsoft Support(will be updated before feature retires) About two-way SMS: Planning for SMS in Microsoft Teams - Microsoft Teams | Microsoft Learn MC1056977 — Microsoft Teams: Streamlined unified Role-Based Access Controls (RBAC) for Teams device management Microsoft 365 Roadmap ID 485760 We are releasing Role-Based Access Control (RBAC) enhancements in the Teams Rooms Pro management portal (PMP). As part of our ongoing efforts to improve device management across portals, we will be extending PMP's RBAC to support additional Entra built-in roles currently available in the Teams admin center (TAC). This transition aims to provide a seamless experience for admins managing Teams Rooms devices. When this will happen: General Availability (Worldwide): We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (GCC, GCCHigh): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. How this will affect your organization: With these enhancements, PMP will now support these four Entra built-in roles: Global Administrator: Read and write access to everything in PMP. Note that the Global Administrator role will no longer be automatically assigned to the Teams Rooms Pro Manager role in PMP. Global Reader: Read-only access with some restrictions in the settings section, such as General, ServiceNow, Signals, and Plan Management. Teams Administrator: Read and write access in PMP, honoring Entra permissions. However, the write access to certain entities like mailbox settings may be restricted. Teams admins assigned to an Administrative Unit (AU) will need to be assigned to a PMP custom role to access PMP. Teams Device Administrator: Read and write access in PMP except for Roles and Partner Management functionalities. Similar to Teams Administrators, any Teams Device Administrator assigned to an AU will need to be assigned to a PMP custom role to access PMP. What you need to do to prepare: This rollout will happen automatically with no admin action required. MC1056268 — (Updated) Microsoft Teams Premium: Ultra-low latency (ULL) attendee experience for town halls Microsoft 365 Roadmap ID 486535 Updated April 22, 2025: We have updated the timeline below. Thank you for your patience. Before this rollout, Microsoft Teams town hall attendees typically watch the presentation with a 20-30 second delay. After this rollout, with ultra-low latency (ULL), attendees will be able to view and participate in a town hall at a much lower latency than before, ensuring they are in sync with content being shared by presenters and organizers. This feature is available for town hall organizers with a Teams Premium license. This feature will only be available for tenants who use the Microsoft eCDN (Enterprise Content Delivery Network) or who do not have an eCDN provider. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS and Android. When this will happen: Targeted Release: We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (Worldwide): We will begin rolling out late June 2025 and expect to complete by early July 2025. General Availability (GCC): We will begin rolling out late June 2025 and expect to complete by early July 2025. How this will affect your organization: This change will be on by default for attendees in town halls scheduled by Teams Premium organizers. What you need to do to prepare: This rollout will happen automatically by the specified dates 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 new documentation. MC1052166 — (Updated) Microsoft Teams: Slide Control for PowerPoint presenters Microsoft 365 Roadmap ID 484844 Updated April 24, 2025: We have updated the timeline below. Thank you for your patience. A new Slide Control feature allows presenters in both meetings and events to share control of their Microsoft PowerPoint presentations. Users with control will be able to move the slides forward and backward for all users in the meeting, making it easy for each speaker to directly control their content. When this will happen: Targeted Release: We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (Worldwide): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (GCC): We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (GCC High): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (DoD): We will begin rolling out early August 2025 and expect to complete by mid-August 2025. How this will affect your organization: On release, Slide Control will be enabled for all internal users in the tenant and disabled for all external users. What you need to do to prepare: Before release, decide what feature scope you'd like to apply within your tenant, meaning which type of users are allowed to use the new Slide Control feature. Note: Slide Control only allows for presenters to share control of their slides with the users they choose; users cannot request control themselves. MC1052163 — Microsoft Teams: Teams button support on multiple connected peripheral devices Microsoft 365 Roadmap ID 485714 You can now use the Teams button across personal peripheral devices without having to manually select a specific device in the Teams devices settings. This provides a more seamless experience navigating across multiple certified for Microsoft Teams personal peripheral USB devices (with a wire or a dongle) connected to the same host device (such as your laptop). For example, you can use the Teams button on headset A to bring up the meeting pre-join screen, then use the Teams button on headset B to join the meeting, and then use the Teams button on your connected speakerphone to raise hand in the meeting, and so on. When this will happen: General Availability (Worldwide): We will begin rolling out early May 2025 and expect to complete by late May 2025. General Availability (GCC): We will begin rolling out late May 2025 and expect to complete by mid-June 2025. General Availability (GCC High): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: The Teams button will work on all peripheral devices that are wired or with a dongle and connected to the same laptop without needing to manually switch between selected devices in the Teams devices settings. What you need to do to prepare: This rollout will happen automatically with no admin action required. The Teams button will work on all peripheral devices that are wired or with a dongle and connected to the same laptop without needing to manually switch between selected devices in the Teams devices settings. You may want to notify your users about this change and update any relevant documentation as appropriate. MC1052162 — Microsoft Teams: Now available - new policy setting for Speaker Attribution in BYOD scenarios - Enabled ON by default Microsoft 365 Roadmap ID 488301 Updated April 29, 2025: We have updated the title, timeline, and content. Thank you for your patience. Available now: The new SpeakerAttributionBYOD setting is now available in csTeamsAIPolicy for Microsoft Teams Premium users. This gives IT admins more control over speaker attribution when users join meetings from personal (BYOD) devices. Admins can now configure this setting using PowerShell. If no action is taken, it will be enabled by default starting in early June 2025. NOTE: If you are a Microsoft Teams customer (not a Microsoft Teams Premium customer), we are sending this message to you because this new setting will take effect automatically for any user assigned a Microsoft Teams Premium or Microsoft 365 Copilot license—even if your organization previously didn’t have these licenses. Therefore, we recommend all organizations review this message, regardless of your organization’s current license status. This setting allows organizations to manage how speaker attribution is used in meetings where users join via personal devices, helping enhance the in-meeting and post-meeting experience with features like speaker labels (Speaker 1, Speaker 2, etc.) and Microsoft 365 Copilot in shared spaces. To access Copilot features, a Microsoft 365 Copilot license is required. This message applies to Teams for Windows desktop and Teams for Mac desktop. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early June 2025 and expect to complete by late June 2025 (previously mid-June). How this will affect your organization: Previously, speaker attribution was managed using the RoomAttributeUserOverrideparameter in CsTeamsMeetingPolicy. Going forward, SpeakerAttributionBYOD in csTeamsAIPolicy will determine whether attribution is used when users join from BYOD scenarios. What you need to do to prepare: The new setting is available now, and admins can begin configuring it using PowerShell based on their organization's preferences. If no action is taken, the setting will be enabled by default during the rollout in June 2025. If you prefer to modify the setting before the rollout begins, you can do so at any time starting now. Learn more Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn MC1047923 — Update: Ensuring Security and Compliance - Keep you Microsoft Teams desktop clients up to date Versions of the new Teams client that were released more than 90 days ago will be blocked. An in-app warning banner will show up 60 days before the app is blocked (30 days for VDI). When will this happen: Users will see blocking page o Starting April 11th, 2025, for users using the Windows desktop app o Starting May 6th, 2025, for users using the Teams app in VDI environment o Starting May 15th, 2025, for users using the Mac desktop app Users will see warning banner starting 60 days before they are blocked (for VDI environments only, users will see it 30 days before they are blocked) How this will affect your organization: Versions of the new Teams client that were released more than 90 days ago will be blocked. Users that are using these versions will be blocked from using the app. Users should either update to the latest version of the Teams app by downloading the latest version from the download page or use the Teams app on the web. What you can do to prepare: Update to the latest version of Teams. Admins should make sure Teams is automatically updating to stay current and within the compatibility window. Common configurations to validate include: o Teams app on macOS has Microsoft AutoUpdate (MAU) configured properly. Learn More o Customer network settings, and any device management software e.g. antivirus, are configured properly to allow automatic updates. o Windows Policies must not block new Teams or the Webview2 updater. o Please visit Why it's important to keep Teams updated to learn more. References: MC931401, MC1034566 and MC1038442 for more details, including screenshots of the respective warning banner and blocking page in persistent and non-persistent environments. MC1047244 — (Updated) Microsoft Teams: New town hall event access policy Microsoft 365 Roadmap ID 483250 Updated April 30, 2025: We have updated the timeline below. Thank you for your patience. Before this rollout, Microsoft Teams has one admin policy to control event access for webinars and town halls. After this rollout, admins can control who can attend town halls in their organization with the new policy setting TownhallEventAccessType. 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 mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: After this rollout, admins can control the event access for town hall created by their users with the new policy setting TownhallEventAccessType in the Teams admin center and Microsoft PowerShell. The policy has two new attributes: Everyone and Everyone in Organization including Guests: If Everyoneis selected, town halls will not be restricted to a certain identity type; however, your organizers can still choose to restrict their town hall as they wish. This is the default setting. If Everyone in Organization including Guests is selected, town halls in your organization will only allow users in your organization and guest users to your tenant to attend. Town hall organizers may choose to further restrict their town halls but cannot invite users who are not part of their organization or who are not guests to attend. If you have feedback on these attributes or have suggestions for new attributes, please send an email to EventAccessFeedback@microsoft.com What you need to do to prepare: This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. By default, TownhallEventAccessType will be set to Everyone. If you would like to change the default setting before the rollout begins, you can use this Microsoft PowerShell code: Set-CsTeamsEventsPolicy -Identity Global -TownhallEventAccessType EveryoneInOrganizationAndGuests Learn more: Manage who can schedule and attend town halls in Microsoft Teams - Microsoft Teams | Microsoft Learn (will be updated before rollout) MC1045226 — (Updated) Microsoft Teams: Speaker recognition and attribution in Teams Rooms on Android Microsoft 365 Roadmap ID 480715 Updated April 8, 2025: We have updated the timeline below. Thank you for your patience. You can now use speaker recognition, transcript attribution, and AI capabilities in Teams Rooms on Android. Intelligent speaker functionalities are brought to existing speakers via the cloud. This feature identifies and attributes people in live transcripts, utilizing a unique voice profile for each participant enabling intelligent recaps and maximum value from Microsoft 365 Copilot and Teams Premium in meetings. Users can easily and securely enroll voices via Teams Settings. This feature requires a Teams Rooms Pro license. Users can enroll voices in the Teams Desktop. Learn more: Set up your digital voice profile When this will happen: General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. How this will affect your organization: With speaker recognition, Teams Rooms on Android can identify speakers during live transcription in shared meeting rooms, ensuring clear and precise voice capture for every participant. This allows you to track who said what during the meeting through intelligent meeting recap and Copilot. What you need to do to prepare: While this functionality is still off by default, if you have already turned it on, be aware that it will enable this feature even for hardware that did not previously support it. To use this new capability, you need to first setup the right policies through PowerShell. For additional information about how to set the right policies, see Manage voice recognition technology controls for an Intelligent Speaker.Participants can set up a voice profile in minutes using the Teams Desktop application. Each person gets a unique voice signature, stored securely in your organization's tenant in the Microsoft Cloud to ensure that every contribution is accurately captured in every meeting, helping you to have a more productive meeting experience. For information about how to enable face and voice enrollment for your organization, see Overview of voice and face enrollment. MC1045221 — Microsoft Teams: New user setting to view incoming calls in a small window Microsoft 365 Roadmap ID 482747 Coming soon for Microsoft Teams: A new setting that allows users to view incoming calls in a small window in Teams to prevent disruptions. Users will be able to take a call in the small window and continue to see what they were working on before the call. This message applies to Teams on Windows desktop, Teams on Mac desktop, Teams for the web, and Teams for iOS/Android. When this will happen: Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (GCC): We will begin rolling out early June 2025 and expect to complete by mid-June 2025. General Availability: (GCC High, DoD): We will begin rolling out early June 2025 and expect to complete by late June 2025. How this will affect your organization: Before this rollout: Teams users are disrupted by the larger Teams screen when viewing an incoming call. After this rollout: Teams users can turn on this setting to view calls in a small window. Note that both large and small windows are resizable: This feature will be on 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. MC1045219 — (Updated) Microsoft Teams: Room Recommender Microsoft 365 Roadmap ID 482191 Updated April 28, 2025: We have updated the timeline below. Thank you for your patience. With this rollout, if no room is booked for the meeting, an AI-generated room suggestion will be sent in the meeting chat an hour before the meeting start time when two or more attendees are co-located in the same building, making in-person collaboration easier. The room suggestion will consider location of participants, room availability, and capacity to find the best space. You can reserve the suggested room with just one click and update the invite for everyone. The organizer must have a Teams premium license for this experience to occur, which is on Teams mobile on iOS. When this will happen: General Availability (Worldwide): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: This will be a default on feature. For a room suggestion to be generated, a meeting must have: Between two to seven attendees with at least two attendees that are co-located Teams meeting link Organizer has Teams premium No room is already booked for the meeting No external attendees Not an all-day event Room suggestions will be generated in buildings where at least two attendees, who haven’t declined the meeting, share the same work location. For instance, if a meeting has four attendees, with two in Building X and two in Building Y, suggestions for both buildings will be sent. Distribution lists are not considered. If a meeting is moved, canceled, or the suggested room becomes unavailable, the card will update dynamically upon clicking ‘Reserve’. 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 team about this change and update any relevant documentation. We recommend making sure that your rooms are properly added to Places directory with a building associated. MC1045217 — Microsoft Teams Phone: Copilot-generated summaries for call transfers on Android devices Microsoft 365 Roadmap ID 475855 Coming soon for Microsoft Teams Phone on Android devices: Copilot-generated summaries for call transfer. This feature is designed to streamline call transfers by providing agents receiving transferred calls with a Copilot summary of the call. This summary includes key details such as caller information, call reason, prior actions, and next steps. It supports Consult and Blind transfers to help ensure effective communication and improve efficiency. A Microsoft 365 Copilot license is required to use this feature. Learn more: License options for Microsoft 365 Copilot | Microsoft Learn When is this rolling out: General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. How this will affect your organization: Copilot-generated summaries for call transfer are visible to the person to whom the call is being transferred: These new features will be available by default. What do I need to prepare: Please ensure that your Teams phone devices are updated with the latest application to get access to the new features described in this message. These features will be available only with the latest application update. Prerequisite to use these new features: Admins must enable Transcription in Calling policies for both transferor and transferee. This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. MC1045214 — (Updated) Microsoft Teams: New Chat and Channels experience (GCC) Microsoft 365 Roadmap ID 485705 Updated April 30, 2025: We have updated the timeline below. Thank you for your patience. The new, streamlined chat and channels experience makes it easier to stay on top of what matters most and organize your digital workspace. Catch up on chat, channels and teams in one place, create custom sections to organize conversations by topics, use filters to triage messages and more. 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, Teams on Mac desktops, Teams on the web, and Teams on 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: General Availability (GCC): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. 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. Favorites, Chats, and Teams and channels in one list in Teams for Windows: Favorites, Chats, and Teams and channels in one list in Teams for iOS (also available for Android): 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. A quick navigation bar for teams and channels is 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. Use /goto: 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. When the new experience is available in your tenant, this screen will display to users: The Get started button will take users to the new combined chat, teams, and channels experience in Chat, and highlight the location of settings. Users will have the option to defer the new experience up to three times over the course of approximately three days, providing flexibility while also moving an organization to the new experience overall. About a week after the new experience is available for a user, they will be presented with a final Get started screen and transition to the new experience. 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 are available on the adoption web page. MC1045213 — Microsoft Teams: New Chat and channels experience (GCC High, DoD) Microsoft 365 Roadmap ID 485706 The new, streamlined chat and channels experience makes it easier to stay on top of what matters most and organize your digital workspace. Catch up on chat, channels and teams in one place, create custom sections to organize conversations by topics, use filters to triage messages and more. 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, Teams on Mac desktops, Teams on the web, and Teams on 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: General Availability (GCC High): We will begin rolling out mid-June 2025 and expect to complete by early July 2025. General Availability (DoD): We will begin rolling out late June 2025 and expect to complete by mid-July 2025. 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. Favorites, Chats, and Teams and channels in one list in Teams for Windows: Favorites, Chats, and Teams and channels in one list in Teams for iOS (also available for Android): 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. A quick navigation bar for teams and channels is 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. Use /goto: 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. When the new experience is available in your tenant, this screen will display to users: The Get started button will take users to the new combined chat, teams, and channels experience in Chat, and highlight the location of settings. Users will have the option to defer the new experience up to three times over the course of approximately three days, providing flexibility while also moving an organization to the new experience overall. About a week after the new experience is available for a user, they will be presented with a final Get started screen and transition to the new experience. 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 are available on the adoption web page. MC1043473 — Microsoft Teams Rooms on Android: New local pan-tilt-zoom (PTZ) controls Microsoft 365 Roadmap ID 482189 Microsoft Teams Rooms on Android will soon support local pan-tilt-zoom (PTZ) controls. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late April 2025 and expect to complete by early May 2025. General Availability (GCC High): We will begin rolling out late May 2025 and expect to complete by early June 2025. How this will affect your organization: After this rollout, the local PTZ controls in the camera settings will pop up for users when the Enhanced framing toggle is set to off. Admins will have the ability to turn this feature on or off in the admin settings for each Teams Rooms on Android device. This setting will be on 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. 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. MC1043466 — Microsoft Teams: Admins can deploy Custom Together Mode scenes (GCC, GCC High, DoD) Coming soon for Microsoft Teams: We're delighted to introduce the ability for admins to deploy Custom Together Mode scenes. You may create a scene from developer portal and deploy it in your organization. Learn more: Custom Together Mode Scenes - Teams | Microsoft Learn A Microsoft Teams Premium license is required to use this feature. Only Teams Premium licensed users will be able to see and apply the scenes that you've deployed. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. When this will happen: General Availability (GCC, GCC High): We will begin rolling out early April 2025 and expect to complete by mid-April 2025. General Availability (DoD): We will begin rolling out mid-April 2025 and expect to complete by late April 2025. This feature will be on 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. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. MC1043271 — Microsoft Teams in VDI: User uploaded custom background images for the new VDI solution Microsoft 365 Roadmap ID 410366 With this new feature, users on the new VDI solution for Teams (SlimCore based) can now replace their background entirely with any image they want by uploading it through the "Video effects and Settings" option. This is currently supported for Azure Virtual Desktops, Windows 365 and Citrix, when connecting from a Windows endpoint. 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): We will begin rolling out mid-April 2025 and expect to complete by late April 2025. General Availability (GCCH, DOD): We will begin rolling out early May 2025 and expect to complete by late May 2025. How this will affect your organization: Users need to upload the background via Teams button 'Add New' (although the file can reside on the user's device, and Teams would then rely on Client Drive Mapping / Drive Redirection in that case). The file is subsequently uploaded to the user's OneDrive folder, fetched by SlimCore on the endpoint, and stored in the user's profile on the endpoint (e.g. for Azure Virtual Desktops or Windows 365: AppData\Local\Microsoft\TeamsVDI\avd-tfw-<guid>\downloads) What you need to do to prepare: Make sure you are using the new VDI solution based on SlimCore, see here for more details. MC1041960 — Microsoft Teams: Standard and Basic licensed Teams rooms on Windows in the Teams admin center portal Microsoft 365 Roadmap ID 482539 We will be transitioning all Teams Rooms on Windows devices, irrespective of their licenses, to the Teams Rooms Pro management portal to meet users' needs for a one-stop destination to configure, monitor, and manage Teams rooms devices. This change delivers a unified device management and admin portal experience. Users currently using the Teams admin center (TAC) will have device management functionalities within the Teams Rooms Pro Management portal. Teams Rooms on Windows devices will not be available in Teams admin center after June 1, 2025. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out May 1, 2025, and expect to complete in early May 2025. How this will affect your organization: All Teams Rooms on Windows devices with Standard or Basic licenses will be visible in the Teams Rooms Pro management portal at https://portal.rooms.microsoft.com. Organizations that have never used the Teams Rooms Pro management portal will need to add additional URLs found in Enroll a Teams Room in the Pro management portal. Those with Teams or Teams Device administrator roles will be able to access the Teams Rooms Pro management portal and see their devices after May 1, 2025. Users with Basic and Standard Teams Rooms licenses will have device management functionalities within the Teams Rooms Pro Management portal. They will not, however, have access to the full suite of device management and space analytics features available with a Teams Rooms Pro license. What you need to do to prepare: For those that have used only Teams admin center and are unfamiliar with the capabilities of Teams Rooms Pro Management, we encourage you to view the short videos on Teams Rooms Pro Management - YouTube and product documentation Microsoft Teams Rooms Pro management. MC1041461 — Microsoft Teams Premium or Microsoft 365 Copilot: New translated recap after multilingual meetings Microsoft 365 Roadmap ID 481144 Microsoft Teams will soon add features that make it easier for Teams Premium and Copilot users to communicate in meetings where attendees speak different languages. After this rollout, each participant can choose their spoken language and a translation language, for more inclusive and productive conversations. Users will also receive an automatically translated intelligent meeting recap in the translation language they selected for live transcription and captions. For admins, these features help to ensure a more inclusive collaboration experience for multilingual teams, without requiring extra setup. A Microsoft 365 Copilot license or a Teams Premium license are required to use this feature. 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: 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-May 2025 and expect to complete by late May 2025. General Availability (GCC): We will begin rolling out early June 2025 and expect to complete by mid-June 2025. How this will affect your organization: After this rollout, users will be able to: Speak in their language: Choose from nine supported languages: Chinese (Mandarin), English, French, German, Italian, Japanese, Korean, Portuguese (Brazil), and Spanish. Read in their preferred language: The meeting transcript will reflect conversations in each user's chosen translation language. Get an automatic recap: After the meeting, Teams will generate an intelligent meeting recap in each user's selected translation language so they can review key discussions with ease. Switch languages anytime: Even after the recap is generated, users can still change the translation language from the drop-down menu on the recap page. This feature will be on 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. 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. MC1041460 — Microsoft Teams Premium or Microsoft 365 Copilot: Meeting transcription supports multiple spoken languages Microsoft 365 Roadmap ID 473434 Coming soon for Microsoft Teams Premium and Microsoft 365 Copilot users: We’re introducing new controls for organizers and users set their own spoken language during multilingual meetings, allowing each participant to communicate in their preferred language. Before this rollout, Teams meetings require a common spoken language to generate a transcript. After this rollout, Teams can generate a meeting transcript in each participant’s language of choice. For admins, these features help to ensure a more inclusive collaboration experience for multilingual teams, without requiring extra setup. A Microsoft 365 Copilot license or a Teams Premium license are required to use this feature. The user feature in this message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. The meeting organizer feature in this message applies to Teams for Windows desktop, Teams for Mac desktop, and 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): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (GCC): We will begin rolling out early June 2025 and expect to complete by mid-June 2025. How this will affect your organization: We will support nine languages for both spoken and translation options. How it works A meeting organizer with a Teams Premium or Copilot license can enable multilingual mode by turning on Enable speech recognitionin Meeting options before the meeting. When the organizer turns on Enable speech recognition,meeting attendees can select their spoken language from the three-dot More menu in the meeting toolbar > Language settings During the meeting, if the meeting organizer has not preconfigured multilingual mode, a Copilot user can enable the Interpreter agent, allowing all participants to dynamically select their spoken language. In Meeting options, meeting organizers can turn on Enable speech recognition: When Enable speech recognition is turned on, users can select Language settings from the three-dot More menu to set their spoken language and translation options: This feature is 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. 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. MC1041451 — (Updated) Microsoft Teams for iOS/Android: New location sharing settings for emergency calls and more Updated April 9, 2025: We have updated the rollout timeline below. Thank you for your patience. This message applies to Microsoft Teams for iOS/Android. Microsoft is updating its policies regarding the sharing of user location data to enhance privacy, improve data security, and ensure compliance with evolving regulatory standards. To enhance transparency and user control, Teams will introduce a new location consent experience that gives users the choice of when and how Teams can use their location data [specifically, the SSID (service set identifier) and the BSSID (basic service set identifier)]. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late April (previously early April) and expect to complete by early May (previously mid-April). General Availability (GCC High, DoD): We will begin rolling out early Mary 2025 (previously late April) and expect to complete by mid-May 2025 (previously early May). How this will affect your organization: All new and existing Teams for Work users in your organization will be prompted to specify if they want to keep location detection on for emergency calls only or if they consent to allowing location access used for IT Admin Insights, for troubleshooting (with a tool such as the Call Quality Dashboard) or for Network and Location matching through BSSID for emergency calling location. NOTE: The new Teams location consent flow does not apply to fully managed devices where users are restricted from user-granted location access. You can expect current policies for managed devices to continue working as expected, and users will not receive the new location consent prompts. The new Teams location consent changes will impact these Teams features: Emergency calling Location-based routing Network and Location matching through BSSID Call Quality Dashboard This change will be available by default. All new Teams for Work users on iOS and Android will first be prompted to allow location permission at the operating system level: Existing Teams for Work users who previously accepted or denied location permission at the operating system level will not see this prompt a second time. If a user allows location access, dynamic emergency calling policies will work as configured, and users enabled for Location Based Routing will be able to make and receive PSTN calls. If a user disallows location access, several Teams Call Quality Dashboard metrics will be impacted, and Network and Location matching through BSSID from dynamic emergency calling policies will not work. Users can still manually add their physical address for emergency calls in the Teams Calls app if an admin has enabled ExternalLocationLookupMode for their users. Immediately after users consent to allow location access at the operating system level (and for users who previously consented to location access), both new and existing Teams for Work users will be prompted to allow location access at the Teams app level. At the Teams level, users must choose between Allow all, which grants Teams full location access (that can be used for emergency calls, IT Admin Insights, or troubleshooting), or Allow emergency only, which restricts location usage to emergency calling. NOTE: Only users who are configured for a dynamic emergency calling policy through ExternalLocationLookUpMode will see this version of the dialog. Users without ExternalLocationLookUpMode enabled will see a slightly different version of this consent prompt that excludes emergency calling. Users can modify their location detection preferences at the operating system level or app level at any time in Teams Settings > Privacy > Location. On fully managed devices, these settings will be on by default and can only be disabled at the operating system level. What you need to do to prepare: We recommend that you educate your users on these selections and what works best for your tenant. If you regularly use the Call Quality Dashboard or leverage Network and Location matching through BSSID, you may want to recommend that users allow location access for those options, or user location data will no longer flow to these services. For emergency calling, you can communicate these changes by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that 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 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) Changes to API behavior for Wi-Fi access and location - Win32 apps | Microsoft Learn User location consent experience in Microsoft Teams - Microsoft Teams | Microsoft Learn For more detailed information and how this will affect each user in your organization, please refer to the public documentation that will be updated here shortly. Before rollout, we will update this post with links to new documentation. This rollout will happen automatically by the specified dates 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. MC1040545 — Microsoft Teams: Enhanced spell checking will support multiple languages Microsoft 365 Roadmap ID 470600 Coming soon for Microsoft Teams: Enhanced spell checking with multi-language support. This feature will help users communicate more effectively with fewer spelling errors. This message applies to Teams on Windows desktop and Teams on 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, 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-June 2025 and expect to complete by late June 2025. General Availability (DoD): We will begin rolling out late June 2025 and expect to complete by early July 2025. How this will affect your organization: Users will choose their languages for spell checking in Teams settings. Before rollout, we will update this post with revised documentation. Key features Advanced spell checking: Improved accuracy to ensure messages are clear and professional. Multi-language support: Seamlessly switch between up to three languages. Custom dictionary: Users can add their own words for personalized spell checking. 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. You may want to notify your users about this change and update any relevant documentation. MC1038684 — (Updated) Prevent/Fix (Detected)Policy changes for Microsoft Teams devices using Device Code Flow Authentication Updated April 3, 2025: We have updated the rollout timeline below. Thank you for your patience. Microsoft is rolling out a new Microsoft Managed Policy to help further secure your tenants against potential threats to accounts using Device Code Flow (DCF) authentication. This messaging is particularly for tenants who have deployed Android based Teams devices in shared spaces as these accounts are not associated with real users, such as: Microsoft Teams Rooms (Android) FoR and Console IP Phones (Licensed as Teams Shared Devices) Panels Displays This policy should be visible in the Entra ID Portal (https://entra.microsoft.com/), as shared in the screenshot below, and we recommend that the Global admins should create exclusion lists for excluding those accounts which sign in on these devices, so that Admins can continue to use the remote sign in and management capabilities. Admins can customize the Microsoft-managed policy according to the tenants' specific needs. Example here: Exclude users When this will happen: The new policy is currently rolling out. How this will affect your organization: In the case where admins do not exclude these devices and enable the policy, then those devices which get signed out for any reason, will not be able to re-authenticate using DCF capability. What you need to do to prepare: If the new policy is visible to your tenant in the Entra ID Portal (https://entra.microsoft.com/), Global admins should create exclusion lists for excluding those accounts which sign in on these devices. The exclusion lists can be created based on the guidelines in this document: Exclude users Click here to learn more: Details of potential security threats to accounts using DCF Authentication: New Microsoft-managed policies to raise your identity security posture Link to the policies list view in the Entra portal. MC1036576 — Microsoft Teams: Share contact information for people in Microsoft Teams channels Microsoft 365 Roadmap ID 375627 Users can now share the contact information in the Teams channel to make it easy for others to reach out to collaborators. When this will happen: General Availability (Worldwide, GCC High, GCC, DoD): This feature update is now available. How this will affect your organization: Users can now easily obtain contact information for users in Teams channels by simply hovering over the contact to view their details in the Profile Card. For more information, see Share a contact in a chat or channel. 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. MC1035710 — Microsoft Teams: Simplified Notes pane in meetings Microsoft 365 Roadmap ID 482398 Coming soon to Microsoft Teams: We will update the Notes pane in meetings to streamline the design and clarify key features. Collaborative meeting notes can be added to scheduled meetings and are not supported for instant meetings or Teams calls. This message applies to Teams for Windows desktop and Teams 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 early May 2025. General Availability (GCC): We will begin rolling out in early May 2025 and expect to complete rollout by late May 2025. How this will affect your organization: Here are the changes in this rollout: We will change the name of the meeting pane from Meeting notesto Notes to match the Notes icon in the meeting toolbar: Users will be able to access controls like Open in new windowand Copy componentfrom the three-dot menu at the top of the Notes pane. We will include the Open in Loopoption there, too. Before this rollout, users select the Pages icon to find the Open in Loop option. This change will be enabled 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. 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: Take meeting notes in Microsoft Teams - Microsoft Support MC1034566 — Microsoft Teams in VDI: Keep your Microsoft Teams desktop clients up to date Microsoft Teams is governed by the Modern Lifecycle Policy which requires that the new Teams desktop client be kept up to date. As communicated in MC931401 in December 2024, new Teams clients in VDI that are out of date will start experiencing warning banners in March 2025 and blocking pages starting from May 6th, 2025. When a client falls out of date, the user will see: Recurring in-app alerts, if the app is between 60d-90d out of date (see screenshot below). A blocking page in Teams, if the app is greater than 90 days out of date. At this point, the app will show options to update, to contact their IT administrator, or continue to Teams on the web (depending on Persistent vs Non-Persistent VDI, see screenshot below). Important: the clock for a specific version (e.g. version N) starts ticking only after the next version (N+1) is completely released, according to this calendar: https://learn.microsoft.com/en-us/officeupdates/teams-app-versioning#windows-version-history As an example: Teams app 24295.x.x.x (a.k.a version N) was released on November 18th, 2024. The next version (a.k.a version N+1), 24335.x.x.x, was released on January 9th, 2025. Therefore, an in-app alert/warning banners would have been shown on March 9th (60 days after the January 9th update) and onwards. An in-app blocking dialogue will be shown on April 9th (90 days after the January 9th update) and onwards. Continuing with this example: The next version after 24335 was 25007, released on February 4th, 2025. Therefore, alerts/warning banners for 24335 will show on April 4th, 2025, and blocking dialogues on May 4th, 2025. The Microsoft Teams desktop client usage report in Teams Admin Center, or similar queries in Call Quality Dashboard, gives you an overview of the Teams desktop clients in use within your organization. What you need to do to prepare: To avoid disruption to end-users, the admins with users on Teams versions older than the currently released versions, should update their users to the most recent version. Admins should make sure Teams is automatically updating (or update the golden image on a frequent cadence) to stay current and within the compatibility window. MC1028320 — (Updated) Microsoft Teams: Teams Rooms Pro Management portal will be generally available (GCC High) Microsoft 365 Roadmap ID 482187 Updated March 27, 2025: We have updated the URL below to show as intended. Thank you for your feedback. NOTE: This message applies to customers with Microsoft Teams Rooms Pro licenses. If you don't have this license, you can ignore this message. After this rollout, admins will have access to the Teams Rooms Pro Management service and portal at https://devices.gov.teams.microsoft.us,where you can use remote device management and analytics features while maintaining high security and privacy standards. When this will happen: General Availability (GCC High): We will begin rolling out early May 2025 and expect to complete by mid-May 2025. How this will affect your organization: This portal will be available by default for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. Learn more: Microsoft Teams Rooms Pro management - Microsoft Teams | Microsoft Learn (will be updated before rollout begins) MC1026225 — Microsoft Teams admin center: We will retire Graph connector management Due to low usage, we will retire the Graph connector management feature from the Microsoft Teams admin center starting April 14, 2025 and ending in late April 2025. Instead, we recommend admins transition their Microsoft Graph connector management activities to the Search & Intelligence feature in the Microsoft 365 admin center. How this will affect your organization: Before this retirement, for Teams apps with the graphConnector property in the manifest, the Teams admin center provides the Graph connector management control to enable or disable the connection to Microsoft Graph. When this control is turned on, the app content is integrated with Microsoft Graph and available for search in Microsoft 365. When this control is turned off, the app content is not integrated with Microsoft Graph. The rest of the app functionality is not impacted by this control. For apps with the graphConnector property, the management control is in the Teams admin center > Manage apps > App details page > Graph connector tab and is available on per-app basis: After this retirement, admins will not be able to turn on or off the connection to Microsoft Graph for Teams apps from the Teams admin center. We will maintain the existing state (on or off) for all apps that may have this property. What you need to do to prepare: This change will happen automatically by the specified date. After this retirement is implemented, there is no impact on users. Any apps used in your environment with the graphConnector property will continue to function and will not be impacted. After this retirement, to manage the graph connector for any Teams app, you can: Delete the connection at Microsoft 365 admin center > Settings > Search and intelligence.Learn more: Monitor Microsoft Graph connectors for Microsoft Search | Microsoft Learn Contact the owner or developer of the app to turn the graph connection on or delete it. In the Microsoft Entra admin center, revoke the ExternalItem.ReadWrite.OwnedBy, ExternalConnection.ReadWrite.OwnedBy, and ExternalConnection.Read.Allpermissions for the app, to limit the app from reading or writing external items and external connections. Learn more: Review permissions granted to enterprise applications. Learn more Deploy Microsoft Graph connectors in Teams admin center | Microsoft Learn Enable the Simplified Admin Experience for your Microsoft Graph connector - Microsoft Graph | Microsoft Learn MC1024383 — (Updated) Microsoft Teams: Update on changes to "csTeamsAIPolicy" (take action) Updated April 8, 2025: We have updated the rollout timeline below. Thank you for your patience. MC912707 (Updated) Microsoft Teams: New policy for voice and face enrollment will default to "On" (configure now), published October 2024. We want to bring to your attention an issue that may have impacted your organization’s configuration of the new csTeamsAIPolicy in Microsoft Teams. As a reminder, this policy provides IT admins with greater control over voice and face enrollment settings, allowing you to manage these features based on your organization’s needs. If you made changes to this policy and settings before October 18, 2024, we recommend you verify those changes. We understand this may have caused confusion, and we sincerely apologize for any inconvenience this may have caused. We have now resolved the issue, and you can proceed with updating your csTeamsAIPolicy settings as needed. The policy is available through Microsoft PowerShell, and any modifications you make will apply successfully. When this will happen: As communicated in MC912707, the PowerShell cmdlets are available now for preparation and to ensure a smooth transition. The policy takes effect starting in mid-March 2025 and is expected to be fully in effect by mid-April 2025 (previously late March). 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 dates. 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. Please review your current csTeamsAIPolicysettings to confirm they align with your intended configuration. If you made changes before October 18, 2024, but they did not take effect, we recommend reapplying those settings now. Ensure that updates to the policy are consistently applied across all assigned locations (global, user-level, or group-level) to avoid unintended configurations. For guidance on configuring the policy, please refer to: o Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) o Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell) o Overview of voice and face enrollment - Microsoft Teams We appreciate your patience and your partnership as we work to ensure a smooth transition. If you have any questions or need further assistance, please contact us. MC1022539 — (Updated) We are making changes to the Resource Account license requirement Updated March 5, 2025: We would like to clarify that the term "Resource Account" in this post specifically refers to the "Teams Phone Resource Account" used for Call Queue, Auto Attendant, and Shared Calling. This does not affect any Common Area Phone or Teams Rooms using the Microsoft Teams Shared Devices or Teams Rooms licenses, respectively. For more details, please refer to the following link: Microsoft Teams Phone Resource Account licenses - Microsoft Teams | Microsoft Learn We are making improvements to how telephone numbers are managed for Teams Phone Resource Account and Teams Phone User Account 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 Teams Phone Resource Accounts. Any existing Teams Phone Resource Account without appropriate “Microsoft Teams Phone Resource Account license” may be converted to Teams Phone User Accounts. Similarly, any Teams Phone User Account with “Microsoft Teams Phone Resource Account license” may be converted to Teams Phone 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 Teams Phone Resource Account without proper “Microsoft Teams Phone Resource Account license”, those accounts may be converted to Teams Phone User Accounts. Similarly, any Teams Phone User Accounts with “Microsoft Teams Phone Resource Account license” may be converted to Teams Phone Resource Account. Starting second week of April 2025, any new phone number assignments to Teams Phone Resource Account will require an appropriate “Microsoft Teams Phone Resource Account license”. More information on Teams Phone 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 Teams Phone Resource Account. If a Teams Phone User Account is desired, please remove any existing “Microsoft Teams Phone Resource Account license”. MC1019312 — (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions Microsoft 365 Roadmap ID 89975 Updated April 23, 2025: We have updated the timeline below. Thank you for your patience. 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 June 2025 and expect to complete by mid-June 2025. General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-June 2025 and expect to complete by late June 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) MC1011152 — (Updated) Microsoft Teams: Updates to the Teams system tray icon and menu Updated April 9, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 April 2025 (previously mid-April). 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 March 27, 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 May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (GCC): We will begin rolling out early June 2025 and expect to complete by late June 2025. General Availability (GCC High): We will begin rolling out early June and expect to complete by late June 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 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 — (Updated) Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails Microsoft 365 Roadmap ID 476488 Updated March 27, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 June 2025 and expect to complete by mid-June 2025. General Availability (Worldwide): We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (GCC, GCC High): We will begin rolling out mid-July 2025 and expect to complete by early August 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 — (Updated) Microsoft Teams: Join town halls using dial-in options and join codes Microsoft 365 Roadmap ID 476489 Updated April 11, 2025: There was an error previously published that we have corrected. Previously we mentioned that the Microsoft Teams town halls dial-in options would be available to attendees and presenters, and that it would appear as separate email invited. This is not correct. Presenters and Organizers can now, with this update, join a Teams town hall using the dial-in options and code displayed on the Event Scheduling page after publishing. This code should only be used for Organizers and Presenters, not attendees. Presenters and attendees can now join Microsoft Teams town halls using dial-in options and join codes. When this will happen: Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. General Availability (GCC, GCC High): We will begin rolling out early June 2025 and expect to complete by late June 2025. How this will affect your organization: With the release of this feature, Teams town hall presenters and organizers may join a Town hall using the dial-in option. Teams town hall does not support dial-in Attendees at this time. 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 March 31, 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-May 2025 and expect to complete by late May 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early June 2025 and expect to complete by early July 2025. 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. 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. MC1005513 — (Updated) Microsoft Teams: Direct routing call troubleshooting with the new "SIP call flow" diagram tool Microsoft 365 Roadmap ID 479413 Updated March 18, 2025: We have updated the rollout timeline below. 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. Additional resources: SIP call flow for Direct Routing in Microsoft Teams - Microsoft Teams | Microsoft Learn MC1000269 — (Updated) Microsoft Teams: New keyboard shortcut for adding emojis Microsoft 365 Roadmap ID 369345 Updated April 16, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 June 2025 and expect to complete by mid-June 2025. General Availability (Worldwide): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (GCC): We will begin rolling out late June 2025 and expect to complete by early July 2025. General Availability (GCC High): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (DoD): We will begin rolling out late June 2025 and expect to complete by early July 2025. General Availability (Gallatin): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (USSec, USNat): We will begin rolling out mid-July 2025 and expect to complete by late 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) 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. MC994287 — (Updated) Microsoft Teams: Webinars will be generally available (DoD) Microsoft 365 Roadmap ID 475279 Updated March 26, 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-May 2025 and expect to complete by late May 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 — (Updated) Microsoft Teams: Native Bluetooth call controls using hands-free protocol for multiple peripheral devices Microsoft 365 Roadmap ID 475853 Updated April 25, 2025: We have updated the timeline below. Thank you for your patience. 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-May 2025 (previously mid-April). 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 Personal peripherals for Microsoft Teams - Microsoft Teams | Microsoft Learn MC993226 — (Updated) Microsoft Teams: New location sharing settings for emergency calls and other features Updated April 16, 2025: We have updated the rollout timeline below. Thank you for your patience. Microsoft is updating its policies regarding the sharing of user location data to enhance privacy, improve data security, and ensure compliance with evolving regulatory standards. To enhance transparency and user control, Teams is introducing a new location consent experience that gives users the choice of when and how Teams can use their location data (specifically SSID & BSSID). Please refer to the public documentation that will be published shortly. 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 mid-April 2025 (previously late March) and expect to complete by mid-April 2025 (previously late March). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late April 2025 (previously mid-April) and expect to complete by late May 2025 (previously early May). How this will affect your organization: All new and existing Teams for Work users within your organization will be prompted to specify if they want to keep location detection on for emergency calls only, or if they consent to allowing location access used for IT Admin Insights or troubleshooting ex via tooling such as Call Quality Dashboard or Network and Locations matching via BSSID for emergency calling location. Important Note - The new Teams location consent flow does not apply to fully managed devices where users are restricted from user granted location access. You can expect current policies to continue working as expected, and users will not be prompted with any of the new location consent dialogs. The new Teams location consent changes will impact the following Teams features: Emergency Calling Location Based Routing Network and Locations matching via BSSID Call Quality Dashboard For all new Teams for Work users, they will first be prompted with an operating system level consent dialog, requesting location permission granting. Existing Teams for Work users who had previously accepted or denied operating system level consent for location will not see this dialog a second time. If location access isallowed, dynamic emergency calling policies will work as configured, and users enabled for Location Based Routing will be able to make and receive PSTN calls. If location access isdisallowed, several Teams Call Quality Dashboard metrics will be impacted, and Network and Location matching via BSSID from dynamic emergency calling policies will not work. Users can still manually add their physical address for emergency calls via the Teams Calls app if an admin has enabled ExternalLookupMode for their users. Immediately after consenting to allow location access at the operating system level (or for those who had previously consented to location access), both new and existing Teams for Work users will be presented with a new Teams app level location permission dialog. Users must choose between "Allow all," which grants Teams full location access used for emergency calls and for IT Admin insights and troubleshooting, or "Keep emergency only," which restricts location usage to emergency calling purposes. It is important to note only end users who are configured for a dynamic emergency calling policy will see this version of the dialog. Users without ExternalLookUpMode enabled will see a slightly different version of this in-app consent dialog that excludes emergency calling. Users can modify their operating system or app level location detection preferences at any time via Teams settings under Privacy > Location. On fully managed devices, these settings will be ON by default and can only be disabled via the OS level location setting. What you need to do to prepare: Please educate your users on these selections and what works best for your tenant. If you regularly use the Call Quality Dashboard or leverage Network and Location matching via BSSID, you may want to recommend that users allow location access for those options, otherwise a user’s location data will no longer flow through to these services. For emergency calling, you can communicate these changes 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 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) WiFi Access Location changes – 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. Please notify your users and admins about this change and update any relevant documentation. MC989975 — (Updated) Microsoft Teams: Occupancy status on Teams panels Microsoft 365 Roadmap ID 474441 Updated April 11, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 April 2025 (previously early April) and expect to complete by late May 2025 (previously late April). 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 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. MC973513 — (Updated) Simplify UX flow to enable Together Mode Microsoft 365 Roadmap ID 470427 Updated April 3, 2025: After further review, this feature continues rolling out. We apologize for any inconvenience. 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-June 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 — (Updated) Microsoft Teams: New "Tag mentions" filter for the Activity feed Microsoft 365 Roadmap ID 470598 Updated March 21, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 April 2025 (previously late February). 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) MC971032 — (Updated) Microsoft Teams: New recording policies for town halls and webinars Microsoft 365 Roadmap ID 473887 Updated April 18, 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: Targeted Release: We will begin rolling out late April 2025 (previously early April) and expect to complete by mid-May 2025 (previously mid-April). 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). 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 April 28, 2025: We have updated the 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: Targeted Release: We will begin rolling out late April 2025 (previously early April) and expect to complete by mid-May 2025 (previously mid-April). General Availability (Worldwide, GCC): 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: 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 MC966633 — (Updated) Microsoft Teams: Meeting recap can be shared as a link Microsoft 365 Roadmap ID 471430 Updated April 11, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams: Meeting participants will be able to share a link to the Meeting recap from the meeting thumbnail in chat and the Recap tab, making it easier to reference and share Meeting recap insights with others. Meeting participants can share the meeting recap link with anyone in their organization. Users who don't have access to the recording or transcript must request access before they can access the Meeting recap. This message applies to Teams for Windows desktop and Teams for Mac desktop. 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): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (GCC High): We will begin rolling out late March 2025 and expect to complete late April 2025 (previously late March). 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. You may want to notify your users about this change and update any relevant documentation. Learn more: Meeting recap in Microsoft Teams - Microsoft Support (will be updated before rollout) MC960811 — (Updated) Microsoft Teams: Enhanced captions for Teams Rooms on Windows Microsoft 365 Roadmap ID 423089 Updated April 25, 2025: We have updated the 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 late April 2025 (previously mid-March) and expect to complete by mid-May 2025 (previously late April). 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. 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 April 25, 2025: We have updated the 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 late April 2025 (previously mid-April) and expect to complete by late May 2025 (previously late April). 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. 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 April 4, 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 late April 2025 (previously late March). 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. MC952889 — (Updated) Microsoft Teams admin center: Non-disruptive device operations for Microsoft Teams devices Microsoft 365 Roadmap ID 418120 Updated March 21, 2025: We have updated the rollout timeline below. Thank you for your patience. We are excited to announce a new capability in the Microsoft Teams admin center designed to ensure that device operations are non-disruptive for Android-based Teams devices. This new feature allows software updates, restarts, and configuration updates to occur only when the device is idle (not busy), preventing any disruptions during meetings or calls. Device admins will now have the ability to manage these operations without affecting end-user experience, ensuring smoother and uninterrupted device usage. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out late February 2025 and expect to complete by early April 2025 (previously early March). How this will affect your organization: This change will significantly enhance the user experience by ensuring that device operations such as software updates, restarts, and configuration updates are carried out only when the device is idle. This means meetings or calls will no longer be interrupted by these operations. This change will be applicable for Teams Rooms on Android, Panels, Phones, and Displays. This change will require an update for Teams app and the Teams admin agent app to take effect. We will update this message closer to the release date with details about the required versions. With this change, the following device operations will automatically function in a non-disruptive way: Software update Device restart Configuration update This change will be applicable for operations created by administrators manually from Teams admin center or the Teams Rooms Pro Management Portal, as well as those being carried out automatically. How this will work: At the time of execution, the device status is checked. The execution goes forward only if the device is free (no ongoing meeting or call) and has no upcoming scheduled event on the calendar. A few minutes before the execution starts, the device shows a notification for the end-users, informing them that the operation is about to start. The device users get an option to Postpone the execution if they want to use the device. The execution of the operation does not start if the device is busy, or has upcoming scheduled events on the calendar, or the end-user has opted to postpone the execution. The device status is checked at regular intervals for a safe window for execution. The status of the operation is available in Teams admin center. Admins can view the details on the device page under the History tab. This ensures that the end-users do not face any disturbance while they are using Teams devices. Additional aspects There could be scenarios where the devices are extremely busy thus delaying the execution of the operation. Administrators will have an option to decide the execution approach if the execution is unable to start even after 24 hrs. There are two options: The operation is cancelled after having tried for 24 hrs.There will be no impact on the device. If the administrator created this operation, they can come back can create it again. This is the default behavior. The operation is force-executed after having tried for 24 hrs. This option will execute the operation, but the status of the device will not be checked at this point. This may cause some disruption if the device is in use. The option to cancel or force the execution of the operations after the 24-hr search of a safe-execution window can be configured from Teams admin center through the Configuration profiles. What you need to do to prepare: The changes will take effect automatically after updating the devices to the required Teams app and Teams admin agent versions. The updates will happen automatically, but admins can choose to update manually also. The details about the required versions will be announced closer to the release date. Refer to Update Microsoft Teams devices remotely - Microsoft Teams | Microsoft Learn for more details about updating devices. Admins should familiarize themselves with the new controls available in the Teams admin center. They should ensure that they configure the settings appropriately to suit their organization's needs. Additionally, it's recommended to communicate these changes to end-users, so they are aware of the improved experience and new notifications they might receive regarding device operations. We believe this feature will greatly improve the reliability and user experience of Teams devices in your organization. For any clarification, feel free to reach out to Microsoft Support. Before rollout, we will update this post with revised documentation. MC948994 — (Updated) Microsoft Teams: Collaborative Notes support for GCC High and DoD environments Microsoft 365 Roadmap ID 418119 Updated April 17, 2025: We have updated the rollout timeline below. Thank you for your patience. Teams Collaborative Notes (powered by Loop), and Loop components in chat and channels, is now available for Microsoft 365 GCC High and DoD environments across desktop and web experiences. Users can create components in meetings to collaborate on their meeting agenda, notes, and action items, create components in compose, share with others and edit inline in Chats and Channels to collaborate synchronously on ideas without leaving the context of Teams. No matter where people are editing, the component will always show the latest updates. You can also share Loop components between chats, channels, and meetings as well as the rest of M365 where Loop is supported. When this will happen: General Availability (GCC High): We will begin rolling out in early June 2025 and expect to complete by late June 2025. General Availability (DoD): We will begin rolling out in early July 2025 and expect to complete by late July 2025. 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 Loop Components will generate a Company Shareable Link (CSL), unless you have set People Specific Link (PSL) as the default. If PSL is the default, only specific users who were sent the original component invite will be able to access the component. Users who were forwarded the meeting or nudged into a meeting will need to request access to the components. Known issues: Users external to an organization will not be able to view or edit the Loop component. Loop meeting notes will generate a Company Shareable Link (CSL) regardless of your organization’s default sharing link type if you use the Teams New Calendar. You can manage this in Teams Calendar and Loop components in chats and channels by following the instructions here. You can manage this in Teams New Calendar by following the instructions here. 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 April 25, 2025: We have updated the 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 late April 2025 (previously mid-April) and expect to complete by late May 2025 (previously late April). 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) MC942831 — (Updated) Microsoft Teams Phones: Remotely manage contacts in Teams admin center Microsoft 365 Roadmap ID 81379 Updated April 25, 2025: We have updated the timeline below. Thank you for your patience. Coming soon to the Microsoft Teams admin center: Admins will be able to remotely manage contacts to ensure crucial contacts are available for users on their Teams Phone devices. This feature is only available for common area phones. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out this feature in mid-June 2025 and expect to complete by late June 2025. General Availability (GCC High): We will begin rolling out this feature in late June 2025 and expect to complete by mid-July 2025. General Availability (DoD): We will begin rolling out this feature in late July 2025 and expect to complete by mid-August 2025. How this will affect your organization: IT admins can access the Manage contacts feature from Teams admin center > Teams Devices > Phones > Common area phones. Select the applicable devices and then select Manage contacts. In the right panel, use the Search box to search for and select contacts to add to selected devices. You can upload a CSV file for contacts not found through Search. Newly added contacts will be synchronized to the Calls app and People app on the Teams phones devices under the group name Company contacts within 24 hours. For any device, admins can review or delete the added contacts from the Manage contacts right panel. Track the progress and status of contact operations with the Activity log in the Teams phone inventory. 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. If you have questions or need further assistance regarding this feature, please reach out to our support team. Before rollout, we will update this post with revised documentation. MC942829 — (Updated) Microsoft Teams admin center: Activity log for Teams Phone device management Microsoft 365 Roadmap ID 420326 Updated April 25, 2025: We have updated the timeline below. Thank you for your patience. We’re excited to announce the rollout of a new feature in the Teams admin center: Activity log for Teams Phone device management. This feature empowers Teams administrators to actively monitor and track device operations, providing greater control over remote operations on Teams devices. Updated December 3, 2024: We have updated the rollout timeline below. Thank you for your patience. Currently, the Activity log supports only the remote management of contacts on Teams Phones; however, we’re working to expand this feature to other device types and additional operation categories. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out this feature in mid-June 2025 and expect to complete by late August 2025. How this will affect your organization: Admins can access the new Activity log by navigating to the Teams admin center > Teams Devices > Phones > Activity log Because only remote management of contacts for Teams Phones is currently supported, admins will be able to track operations such as Add contacts or Delete contacts and details like created time, impacted users, operation status, and more. By selecting an operation name, admins can view status updates at a granular level for each device involved in that operation. The Activity log 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. If you have questions or need further assistance regarding this feature, please reach out to our support team. Before rollout, we will update this post with revised documentation. MC939924 — (Uploaded) Microsoft Teams: Start Whiteboard from Teams Rooms on Android in GCC and GCC-H Updated March 26, 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 June 2025 (previously late March). 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. MC934727 — (Updated) Microsoft Teams: File Interactive Previews Microsoft 365 Roadmap ID 421188 Updated March 20, 2025: We would like to inform you that the general availability and other releases of this feature will be delayed. New timelines for release will be communicated in due course. In the meantime, this feature will be rolled back for about a month from the current target releases. Now users can quickly review files in Microsoft Teams chat and channel conversations using the file preview option. Using preview, users will be able to consume the file within the flow of work, minimizing the context switch and potentially enhancing the efficiency for the users. When this will happen: Targeted Release: We will communicate via Message center when we are ready to proceed. General Availability (Worldwide): We will communicate via Message center when we are ready to proceed. General Availability (GCC): We will communicate via Message center when we are ready to proceed. General Availability (GCC High): We will communicate via Message center when we are ready to proceed. General Availability (DoD): We will communicate via Message center when we are ready to proceed. How this will affect your organization: The stage 1 release of this feature will enable previews for single file attachments in Teams messages, starting with PDF files and gradually extending the support for other popular formats such as Microsoft PowerPoint, Microsoft Word, and later Microsoft Excel. The preview option for files in messages with multiple files will be supported in subsequent releases. This new feature is available by default. What you need to do to prepare: This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate. MC920084 — (Updated) Microsoft Teams: Usage reports for bookable desks Microsoft 365 Roadmap ID 421604 Updated March 21, 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 April 2025 (previously late February). 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) MC912707 — (Updated) Microsoft Teams: New policy for voice and face enrollment will default to "On" (configure now) Microsoft 365 Roadmap ID 413708 Updated April 4, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 April 2025 (previously late March). 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. MC889534 — (Updated) Microsoft Teams: Embed support for Teams town hall Microsoft 365 Roadmap ID 401120 Updated March 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-April 2025 (previously mid-March). 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. MC898391 — (Updated) Microsoft Teams: Performance improvements for meetings in Edge web browser for guests Microsoft 365 Roadmap ID 401117 Updated April 4, 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 April 2025 (previously late March). 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 April 4, 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 April 2025 (previously late March). 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. MC892646 — (Updated) Microsoft Teams: New policy for voice and face enrollment defaulting to 'On' Microsoft 365 Roadmap ID 413708 Updated April 4, 2025: We have updated the rollout timeline below. Thank you for your patience. We're introducing a new policy that gives IT admins enhanced flexibility with distinct settings for voice and face enrollment. This adjustment provides greater control over managing these features, allowing organizations to tailor to their needs. Voice and face biometric enrollment will be enabled by default, enabling voice isolation and speaker recognition in meeting rooms and enhancing intelligent meeting recaps and Microsoft Copilot for meetings. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out the new policy in early October 2024 and expect complete by mid-October 2024. The policy will be enabled beginning in mid-March 2025 (previously early February) and expect to be complete by late April 2025 (previously late March). How this will affect your organization: These changes will provide your organization with increased flexibility in managing voice and face enrollments. By using separate settings, you can customize for your organization's specific needs. The enrollment policy will be enabled by default. Once enabled, these enrollments will activate features like Voice Isolation and enhanced speaker recognition, leading to more efficient and productive meetings. What you need to do to prepare: To ensure you have enough time to prepare for this change, you have until mid-January 2025 to configure everything to best suit your needs. If your organization requires keeping face and voice enrollments off, be sure to review the new policy and adjust the settings during this time. This period provides an opportunity to optimize how you manage voice and face data, enhancing your team's control over the process. The new csTeamsAIPolicy will replace the current csTeamsMeetingPolicy, introducing two separate settings for face and voice enrollment: EnrollFace and EnrollVoice. Each can be set to Enabled or Disabled. To help you get ready, review: Set-CsTeamsMeetingPolicy Get-CsTeamsAIPolicy For more information about voice and face enrollment, visit Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar Microsoft 365 Roadmap ID 409226 Updated April 11, 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 April 2025 (previously late March). 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. MC856756 — (Updated) Microsoft Teams Rooms on Windows: Native PTZ controls Microsoft 365 Roadmap ID 409534 Updated April 2, 2025: We have updated the rollout timeline below. Thank you for your patience. Microsoft Teams Rooms on Windows will soon support native PTZ (pan-tilt-zoom) controls for cameras capable of supporting PTZ controls. The PTZ controls will appear in the Camera settings pop-up menu when the Enhanced Framing toggle is set to off. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early August 2025 and expect to complete by late August 2025. General Availability (GCC High, DoD): We will begin rolling out late August 2025 and expect to complete by early September 2025. How this will affect your organization: Before this rollout: Native PTZ controls are not displayed in Camera settings pop-up menus for PTZ-capable cameras. After this rollout: Admins will be able to toggle this feature for each Teams Rooms on Windows in the device's Admin Settings for Peripherals. This setting will be on by default. Users in a Teams Rooms on Windows with a PTZ-capable camera connected will see PTZ controls in the Camera settings pop-up menu. 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 new capability and update any supporting documentation for your users. Before rollout, we will update this post with revised documentation. MC854652 — (Updated) Microsoft Teams: Meeting participants can choose a breakout room from a list Microsoft 365 Roadmap ID 121269 Updated March 21, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Microsoft Teams meeting organizers can make the list of breakout rooms visible to all meeting participants and allow them to choose which room to join. Enabling this setting in breakout rooms allows participants to move freely from one room to another, simplifying breakout room coordination for meeting organizers and participants. This message applies to Teams for Windows, Mac, and the web. When this will happen: Targeted Release: We will begin rolling out early January 2025 (previously early December) and expect to complete by mid-December 2024 (previously mid-December). General Availability (Worldwide, GCC): We will begin rolling out mid-January 2024 (previously mid-December) and expect to complete by late January 2025 (previously early January). General Availability (GCC High, DoD): We will begin rolling out early February 2025 (previously early January) and expect to complete by late April 2025 (previously late February). How this will affect your organization: Before this rollout: Only the meeting organizer can assign meeting participants to breakout rooms. Participants cannot move between rooms. After this rollout: Meeting participants can select their breakout rooms of choice if the meeting organizer selects this option during setup. Organizers can look for the new feature under the breakout rooms panel when setting up breakout rooms: This feature is on by default and accessible to all meeting participants on the affected platforms if enabled by meeting organizers. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. MC804771 — (Updated) Microsoft Teams: Hiding inactive channels Microsoft 365 Roadmap ID 325780 Updated March 20, 2025: We have updated the content. Thank you for your patience Note: Users with EDU licenses assigned will not receive this change. 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 for Targeted Release, and we will roll out to General Availability later this year in 2025. 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 in 2025. When this will happen: Targeted Release: We will begin rolling out mid-July 2024 and expect to complete later in 2025. General Availability (Worldwide) and all clouds: We will begin rolling out later in 2025. 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 in 2025: Manage preferences for automated suggestions via Teams Settings If users prefer to manage channels manually, they can opt out of the auto-suggestions process. Simply go to Teams settings, select General, and toggle off "Suggestions for hiding 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 "Get Suggestions" button. Note that this action can be performed once every 24 hours. Automated suggestions of inactive channels With this, Teams will suggest channels that have been inactive for the user. Once the inactive channels are identified, the user is notified with the coach mark message, "Looks like you haven’t visited some channels lately. Hide them to help you focus." The user can select Review and Hide to see the details and decide which channels they would like to hide. The user can choose not hide any channels by selecting Not Now. If a user has less than or equal to 25 shown channels, no channels will be suggested for that user. This feature is on by default and all Teams users on the affected platforms will have access to it. What you need to do to prepare: Admins need to be aware of this feature, but no additional action is needed. MC795750 — (Updated) Microsoft Teams: Custom emojis and reactions Microsoft 365 Roadmap ID 80659 Updated March 20, 2025: We have updated the rollout timeline below. Thank you for your patience. In Microsoft Teams, users will be able to add their own custom emojis and reactions by uploading an image or GIF file, and their emojis and reactions will be accessible to all users in the tenant alongside the standard Teams emojis and reactions. Up to 5,000 custom emojis can be added per tenant. When this will happen: Targeted Release: We will begin rolling out early July 2024 (previously late June) and expect to complete by mid-July 2024 (previously early July). Worldwide: We will begin rolling out early August 2024 (previously mid-July) and expect to complete by early September 2024 (previously late July). GCC: We will begin rolling out early 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 2025 and expect to complete by early April 2025. How this will affect your organization: This new custom emojis and reactions feature will be turned on by default. Users in the tenant will be able to upload emojis that are visible to the whole tenant. You can pre-emptively turn this feature off or restrict users who can create new emojis via the Teams Admin Center controls described below. How do I use this feature? Custom emojis and reactions will be found in the emoji and reaction menus in the Custom category. Users with upload abilities can add new content through the plus (+) button. Users with delete abilities can right-click any custom emoji to delete. Please note that deleted emojis may take up to 24 hours to reflect for all users in the tenant. Deleted emojis may take up to 24 hours to reflect for other users. How do I manage this feature? This feature can be managed through the Teams Admin Center. Admins will have access to the following controls: Turn the feature on/off for the whole tenant via the Messaging Settings page (on by default). Set which users can create new emojis via the Messaging Policy groups (on for all users by default). Set which users can delete emojis via the Messaging Policy groups (off for all users except admins by default). The Teams Admin Center controls will be made available in early June. We recommend adjusting your settings as needed prior to the Targeted and Worldwide Releases in late June 2024 to ensure that they are in place when the feature rolls out. What you need to do to prepare: This feature is on by default. If you would like to turn the feature off, please use the provided setting in the Messaging Settings page: Messaging Settings This feature allows all users to create new emojis by default and only allows admins to delete emojis by default. If you would like to adjust emoji creation and deletion permissions, please make the appropriate changes through the Messaging Policy groups: MC781595 — (Updated) Microsoft Teams: Tenant-wide policy for permission to download meeting transcription Microsoft 365 Roadmap ID 332800 Updated April 4, 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 April 2025 (previously late March). 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.) MC726122 — (Updated) Microsoft Teams: View, download, and delete Microsoft OneDrive transcript files Microsoft 365 Roadmap ID 365720 Updated April 11, 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 early April 2025 (previously late April). 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 April 11, 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 April 2025 (previously late March). 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 April 4, 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 April 2025 (previously late March). 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 March 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-April 2025 (previously mid-March). 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. Microsoft Purview MC1061103 — Microsoft Purview | Data Loss Prevention: Ability to rename policy and rules Microsoft 365 Roadmap ID 370535 Coming soon for This feature gives the ability for the DLP admin to rename the existing policy/rule without having to create the entire the rule or policy again When this will happen: Public Preview: We will begin rolling out mid-July 2025 and expect to complete by late July 2025. General Availability (Worldwide): We will begin rolling out late August 2025 and expect to complete by mid-September 2025. General Availability (GCC, GCC High, DOD): We will begin rolling out mid-October 2025 and expect to complete by late October 2025. How this will affect your organization: This feature is currently supported for major workloads: Microsoft Exchange Online, Microsoft Teams, Microsoft SharePoint, Microsoft OneDrive, and Microsoft Endpoint. With this rollout, we will also introduce a new field called DisplayName that you can edit in DLP and in Microsoft PowerShell. For all practical purposes the display name can be used as the name for all the operations. Renaming an existing policy: Editing a rule to rename it: All DLP experiences (such as Incident Reports, User Notifications, Email Alerts, DLP Alerts, MTP Alerts, and Activity Explorer) will start showing the policy/rule names at the point of record generation. For example: If a policy is named P1 at T0 and updated to P2 at T1, all records generated between T0 and T1 will have the name as P1 and all the records from T1 will have the name as P2. This feature will be available by default for admins to configure. What you need to do to prepare: This is a non-invasive feature. The tenant admin will not see any changes unless the admin uses the feature. This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Learn more: Create and deploy a data loss prevention policy | Microsoft Learn MC1059679 — Microsoft Purview | Insider Risk Management: Policy tuning analysis for priority content only policies Microsoft 365 Roadmap ID 378409 In Microsoft Purview | Insider Risk Management (IRM), policy tuning analysis provides admins with a real-time prediction of the number of users in a tenant that could potentially match a given set of policy conditions. After this rollout, policy tuning analysis will support insider risk policies that are scoped for priority content. MC786326 (about the preview for this feature that started in May 2024). When this will happen: General Availability (WW, GCC, GCC High, DoD): We will begin rolling out mid-June 2025 and expect to complete by mid-July 2025. How this will affect your organization: After this rollout, admins can use real-time analytics for policies scoped for priority content to help predict the number of users that could potentially match a given set of policy conditions. This feature enables admins to quickly adjust the selection of indicators and thresholds of activity occurrence so they can efficiently translate their insider risk strategies into pragmatic controls and keep from having too few or too many alerts. In IRM, Navigate to Settings > Insider Risk Management > Analytics,turn on Analytics, and then select Save. Create/edit a policy scoped to all users in the organization. When you get to Content to prioritizein the policy wizard, select the priority content types you want to prioritize: Select the items for each priority content type as applicable. On the scoring page, select Get alerts only for activity that includes priority content: Configure the rest of the policy as applicable and save it. 1-2 days after the policy is saved, edit the policy again and navigate to the indicator thresholds page where insights on user activity containing the scoped priority content for each indicator will be visible under Choose your own thresholds: 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. This change will be available by default for admins to configure. To use this feature, admins will need to enable Analytics in Insider risk management > Settings. After Analytics is enabled and insights are populated, admins will be able to see real-time predictions in policies scoped to all users/groups and scored only for priority content. 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 MC1058262 — Microsoft Purview | Insider Risk Management: Enhancements to global exclusions in IRM settings Microsoft 365 Roadmap ID 486826 and Roadmap ID 483485 Coming soon for Microsoft Purview | Insider Risk Management (IRM): Enhancements to IRM exclusions to reduce alert noise. When this will happen: Public Preview: We began rolling out mid-April 2025 and expect to complete by late April 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late April 2025 and expect to complete by early May 2025. How this will affect your organization: Customer can use this feature to tune down the noise Keyword logic update for email: An email will be excluded from scoring only when all the attachments match the keyword exclusions or email subject matches the keyword exclusions. This will be helpful to reduce the email signature noise that commonly contains keyword "image." Keyword exclusions on both target and source file paths: For signals like File copied to removable media, keyword exclusions apply on both target and source file paths. File path exclusions for removable media: We will start supporting file path exclusions for removable media. Exclusion support for browser: Domain exclusions will be supported for browsing indicators. These enhancements will be available by default for admins to configure. What you need to do to prepare: To get the most out of this feature, admins need to update the exclusion settings at IRM Settings > Global exclusions. This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. 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. MC1046161 — Microsoft Purview | Data Loss Prevention: New inline protection controls for AI apps in Microsoft Edge for Business Microsoft 365 Roadmap ID 486368 Coming soon for Microsoft Purview | Data Loss Prevention (DLP): We will introduce new inline protection capabilities for Microsoft Edge for Business that prevent data leakage for the various ways that users interact with sensitive data in the browser, including typing text directly into a web application or sending a prompt to a generative AI app. Inline protection is built natively into Edge for Business, meaning it can be enabled even without deploying Endpoint DLP, and the inline protection complements existing Endpoint DLP protections for uploading or pasting sensitive content to the browser. This capability will be available starting with several top consumer generative AI apps (ChatGPT, Google Gemini, and DeepSeek), and will expand to support a growing list of unmanaged apps over time. Learn more in our blog: Building layered protection: New Microsoft Purview data security controls for the browser & network | Microsoft Community Hub When this will happen: Public Preview: We will begin rolling out early April 2025 and expect to complete by late April 2025. We will update this message when the plan for General Availability is finalized. How this will affect your organization: After this rollout, admins can block prompts typed by users containing sensitive data, starting with ChatGPT, Google Gemini, and DeepSeek. Inline protection can also leverage Adaptive Protection policy conditions for activities in generative AI apps. This rollout enables data security admins to tailor the level of enforcement to the risk level of the user interacting with the data, minimizing disruption to day-to-day AI usage. This change will be available by default for Admins to configure in Purview. Features aren't activated 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. Review your current configuration to assess the impact on your organization. We recommended informing Security admins and Edge admins at your organization about this change to DLP features. You may want to update any relevant documentation. MC1045278 — Microsoft Purview | Data Loss Prevention: New data protection in Microsoft Edge for Business on unmanaged devices Microsoft 365 Roadmap ID 486366 Coming soon: Microsoft Purview | Data Loss Prevention (DLP) will be integrated in the Microsoft Edge browser to offer DLP protections that apply directly in the Edge browser and target scenarios where users on unmanaged (or bring-your-own/BYO) Windows desktop devices and Mac desktop devices are sharing data to or exfiltrating data from organization-managed cloud apps (apps that use Microsoft Entra authentication for user sign-in). When this will happen: Public Preview: We will begin rolling out late May 2025 and expect to complete by mid-June 2025. General Availability (Worldwide): We will begin rolling out early June 2025 and expect to complete by late June 2025. How this will affect your organization: After this rollout, admins can apply protections from Purview DLP that apply directly in the Edge browser to target user activities sharing data to or from Entra-managed apps, when the user is using Edge for Business on an unmanaged device. Admins can configure Purview DLP to block or audit users when they perform activities including uploading or downloading files with sensitive information. Admins can configure policies in Purview DLP to apply protections in the Edge browser and view outcomes for investigation in the Microsoft Defender portal. This change will be available by default for Admins to configure in Purview. Features aren't activated 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. Review your current configuration to assess the impact on your organization. We recommended informing Security admins and Edge admins at your organization about this change to DLP features. You may want to update any relevant documentation. Before rollout, we will update this post with new documentation. MC1045212 — Microsoft Purview compliance portal: Insider Risk Management user analytics Microsoft 365 Roadmap ID 475058 Microsoft Purview Insider Risk Management will be rolling out a new user analytics feature to help Microsoft Defender, Microsoft Purview Data Loss Prevention, and Communication Compliance analysts access an insider risk summary of user activities. When this will happen: Public Preview: We began rolling out in late March 2025 and expect to complete by mid-April 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late September 2025 and expect to complete by late October 2025. How this will affect your organization: With this new feature, Microsoft Defender, Microsoft Purview Data Loss Prevention, and Communication Compliance analysts with the right permissions can access an insider risk summary of user activities that may lead to potential data security incidents as a part of the alert investigation experience in Microsoft Purview and Microsoft Defender. This feature can help analysts gain insider risk context for a specific user and make more informed decisions about responses to potential incidents related to the user. Insights are generated by Insider Risk Management for potentially risky behaviors of every user and are surfaced across the following experiences: User activity summary in Microsoft Purview Data Loss Prevention alerts User activity summary in Microsoft Defender alerts and user entity pages User activity summary in Communication Compliance policies What you need to do to prepare: Insider Risk admins can enable user-level insights from Insider Risk Management Settings > Analytics. During the initial rollout, user analytics will be enabled for all customers who have enabled Insider Risk Management Analytics and will include an option to opt-out. Insider Risk admins should ensure data sharing is also enabled from Insider Risk Management Settings > Data Sharing. Additional information is available here: Enable Analytics in Insider Risk Management. MC1036579 — (Update) Microsoft Purview | Data Loss Prevention: A new Diagnostics experience in the new portal Microsoft 365 Roadmap ID 469504 Updated April 23, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Purview | Data Loss Prevention: Admins will be able to view and manage Diagnostics in the new Purview portal. Before this rollout, diagnostics are only available through Microsoft PowerShell cmdlets. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out earl May 2025 (previously mid-April) and expect to complete by late May 2025 (previously early May). How this will affect your organization: Admins can find the new experience at: Purview portal> Information Protection > Diagnostics Purview portal> Data Loss Prevention > Diagnostics The PowerShell cmdlets will continue to be available after this rollout. This new experience will be on 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. 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. MC1035707 — Microsoft Purview | Endpoint Data Loss Protection (DLP): Blanket protections for unscannable file types (GCC, GCCH, DoD) Microsoft 365 Roadmap ID 473460 Coming soon for Microsoft Purview | Endpoint Data Loss Protection (DLP): A new feature to apply blanket protection to unscannable file types. After you turn on this policy, you will apply this policy to files that cannot be scanned. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-April 2025 and expect to complete by late April 2025. How this will affect your organization: With this new capability, Microsoft Purview DLP is now providing blanket protection for unscannable files. Learn more: Apply controls to all unsupported files In Microsoft Purview, you can access this feature in Policy settings > Create policy > Create rule > Apply restrictions to only unsupported file extensions: This feature is available by default for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified dates 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 Get started with Endpoint Data Loss Preventionin the Microsoft Purview compliance portal Monitored files in DLPin Learn about Endpoint data loss prevention | Microsoft Learn MC1035703 — Microsoft Purview | Endpoint Data Loss Prevention: New Allow and Off modes for each activity (GCC, GCCH, DoD) Microsoft 365 Roadmap ID 481356 Before this rollout, Microsoft Endpoint data loss prevention (Endpoint DLP) supports Audit only, Block, and Block with override on the Create policy page in Microsoft Purview | Endpoint DLP. This rollout will add two new modes: Off and Allow. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late May 2025 and expect to complete by early June 2025. How this will affect your organization: The two new modes are: Off: Endpoint DLP will not trigger events or Alerts and will not trigger notifications. You can use this enforcement mode to configure restrictions for a specific group. Allow: Endpoint DLP will not trigger Alerts and will not trigger notifications but will trigger events in Activity explorer. In Microsoft Purview, the new Allow and Off enforcement modes on the Create policy page for Endpoint DLP: The new modes will be available by default for admins to configure. What you need to do to prepare: You will need these prerequisites to use the new modes: All prerequisites in Onboard Windows devices into Microsoft 365 overview | Microsoft Learn A Defender Antimalware client version higher than 4.18.25010. To find the version of Microsoft Defender (Windows Defender) Antimalware, follow these steps: Open Windows Security. Click on the Settings gear icon. Look for the About link. The About page contains the version information for the Windows Defender components. 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. MC1034582 — Microsoft Purview compliance portal: Endpoint Data Loss Prevention: "Paste to browser" prevention on macOS devices Microsoft 365 Roadmap ID 483491 Microsoft Purview | Endpoint Data Loss Prevention (DLP) will soon add support for restricting users from pasting sensitive content into web browsers on macOS devices using Microsoft Edge, Safari, Chrome, and Firefox. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out mid-May 2025 and expect to complete by early June 2025. How this will affect your organization: After this rollout, if you have already configured DLP policies to prevent users in your organization from pasting sensitive content into a supported web browser on a Windows device, the policies will automatically apply to a supported web browser on macOS devices also. 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. 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: Learn about Endpoint data loss prevention | Microsoft Learn MC1034577 — (Updated) Microsoft Purview compliance portal: Endpoint Data Loss Prevention: Full file evidence parity for macOS Microsoft 365 Roadmap ID 483492 Updated April 22, 2025: We have updated the timeline below. Thank you for your patience. Microsoft Purview | Endpoint Data Loss Prevention (DLP) will soon add support for copying an item that matches a DLP policy from onboarded macOS devices to a Microsoft Azure storage account. This rollout creates full file evidence parity for macOS. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out late April 2025 (previously mid-April) and expect to complete by late May 2025 (previously early May). How this will affect your organization: After this rollout, if you have already configured DLP policies for users in your organization to collect file evidence in Azure storage to protect Windows devices, the policies will automatically apply to macOS devices also. 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. 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: Learn about collecting files that match DLP policies from devices | Microsoft Learn MC1031293 — Microsoft Purview | Endpoint Data Loss Prevention: New Allow and Off modes for each activity (GCC, GCC High, DoD) Microsoft 365 Roadmap ID 481356 Before this rollout, Microsoft Endpoint data loss prevention (Endpoint DLP) supports Audit only, Block, and Block with override on the Create policy page in Microsoft Purview | Endpoint DLP. This rollout will add two new modes: Off and Allow. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out early May 2025 and expect to complete by late May 2025. How this will affect your organization: The two new modes will be: Off:Endpoint DLP will not trigger events or Alerts and will not trigger notifications. You can use this enforcement mode to configure restrictions for a specific group. Allow:Endpoint DLP will not trigger Alerts and will not trigger notifications but will trigger events in Activity explorer. In Microsoft Purview, the new Allow and Off enforcement modes on the Create policy page for Endpoint DLP: The new modes will be available by default for admins to configure. What you need to do to prepare: You will need these prerequisites to use the new modes: All prerequisites in Onboard Windows devices into Microsoft 365 overview | Microsoft Learn A Defender Antimalware client version higher than 4.18.25010. To find the version of Microsoft Defender (Windows Defender) Antimalware, follow these steps: From your PC, open Windows Security Click on the Settings gear icon. Look for the About link. The About page contains the version information for the Windows Defender components. 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. MC1028323 — Microsoft Purview | Insider Risk Management: New reporting capabilities (GCC, GCC High, DoD) Microsoft 365 Roadmap ID 470027 Coming soon: Microsoft Purview | Insider Risk Management will introduce a central location for all reports, including analytics and user activity reports. New Alerts and Cases operational reports will summarize trends in alerts generated and cases created. Sample reports include alerts and cases generated over time, alerts actioned over time, alerts and cases generated by region and department, top triggering events of alerts generated, and average time to triage alerts and cases. Users with the admin, analyst, or investigator role will be able to access the new Alerts and Cases operational reports. When this will happen: General Availability (GCC, GCC High, DoD): We will begin rolling out early May 2025 and expect to complete by early June 2025. How this will affect your organization: To access the Alerts and Cases reports In Insider Risk Management, go the new Reports page at https://purview.microsoft.com/insiderriskmgmt/reportingpage Select Alerts or Cases To drill deeper into each report, select View details Access the new unified Reports page at https://purview.microsoft.com/insiderriskmgmt/reportingpage To view new reports, Select Alerts or Cases on the Reports page: Example of an Alerts report: This feature is available by default to be configured by admins, analysts, or investigators. 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 and investigators about this change and update any relevant documentation. Learn more: Use reports in insider risk management | Microsoft Learn Before rollout, we will update this post with revised 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.Post Coming soon: Microsoft Purview | Insider Risk Management will introduce a central location for all reports including analytics and user activity reports. New Alerts and Cases operational reports will summarize trends in alerts generated and cases created. Sample reports include alerts and cases generated over time, alerts actioned over time, alerts and cases generated by region and department, top triggering events of alerts generated, and average time to triage alerts and cases. Users with the admin, analyst, or investigator role will be able to access the new Alerts and Cases operational reports. MC1026220 — Microsoft Purview | Endpoint Data Loss Prevention: Support for Just-in-time protection on MacOS devices Microsoft 365 Roadmap ID 483354 Coming soon for Microsoft Purview | Endpoint Data Loss Prevention (DLP): You will be able to use just-in-time (JIT) protection to block all egress activities on monitored files while waiting for policy evaluation to successfully complete. This message applies to macOS devices. For any organizations that have already configured DLP settings with JIT to protect Windows device, the policies will automatically apply to macOS devices also. When JIT protection is enabled, and while policy evaluation is processing, Endpoint DLP blocks all egress activities for each user whose account is in the selected scope. Endpoint DLP audits the egress activities for all user accounts that have been excluded (via the Exclude setting) or are otherwise not in scope. When this will happen: 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: This feature will be available by default for admins to configure. If your organization has already enabled JIT on your Windows device, your macOS devices will start getting the same protection. What you need to do to prepare: No change is required to your existing DLP settings. This rollout will happen automatically by the specified dates 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 on macOS devices about this change and update any relevant documentation. Learn more: Using Endpoint DLP Just-in-time protection | Microsoft Learn MC1025209 — Microsoft Purview compliance portal: New capabilities for Microsoft 365 Copilot Microsoft 365 Roadmap ID 479082 Introducing a set of capabilities in Microsoft Purview designed to enhance data security and support compliance management for Microsoft 365 Copilot. These capabilities will be available once Microsoft 365 Copilot is deployed. Copilot phased rollout: Phase 1: Features already available with Purview capabilities as of December 2024, including Copilot Chat, Microsoft 365 App Copilot (Word, Excel, PowerPoint), Outlook Mail and Calendar, and Teams Chat/Channel Copilot. Phase 2: Purview capabilities will be available once Teams Meeting Copilot, OneNote, Stream, Loop, SharePoint agents, and OneDrive for Business are deployed. Purview capabilities - strengthening data security: Copilot will honor sensitivity labels and content encrypted by Microsoft Purview Information Protection, including sensitivity label inheritance, citation, and honoring Extract usage rights. Purview capabilities - supporting compliance management: Capture events for Copilot prompts and responses using Microsoft Purview Audit. Select and retrieve Copilot interactions when a user mailbox is selected as the source for a search query using Microsoft Purview eDiscovery. You can also perform existing reviewing actions and choose to export the review set or put them on hold. Manage retention and deletion policies for Copilot prompts and responses using Microsoft Purview Data Lifecycle Management. Analyze potentially risky communications in Copilot prompts and responses using Microsoft Purview Communication Compliance. This tool helps organizations detect business conduct and regulatory compliance violations (e.g., SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to help ensure user-level privacy. When this will happen: General Availability (GCC): We will begin rolling out in late March 2025 and expect to complete by late April 2025. How this will affect your organization: These capabilities are meant to help you strengthen data security and compliance for Copilot. 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. Licensing information: Microsoft 365 licensing guidance for security and compliance Service description for Microsoft 365 Copilot Learn more: Protect and manage Microsoft 365 Copilot interactions with Microsoft Purview MC1024388 — (Updated) Microsoft Purview compliance portal: Modern eDiscovery enhancements Microsoft 365 Roadmap ID 482558 Updated April 16, 2025: We have updated the content. Thank you for your patience. We are excited to announce several enhancements to the recently launched modernized eDiscovery experience. These updates include: Case Level Data Source View: Users can now access the case level data source view, which allows them to add data sources to the current case. These sources can be utilized in any searches or holds within the case. Enhanced Search and Hold Capabilities: Users will have the ability to duplicate a search, create a search from an existing hold, or create a hold from an existing search within the current case. Retry Failed Locations: The search statistics view now includes the option to retry failed locations, providing a more comprehensive search estimate. Detailed Process Reports: We are adding information related to compliance boundaries, case/export/search names, and decryption settings into the relevant process report CSVs. When this will happen: General Availability (Worldwide, 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: eDiscovery users will start to see the relevant enhancements in the product, so internal documentation updates may be needed. What you need to do to prepare: Evaluate how this feature will impact your organization’s eDiscovery process and, if needed, modify your internal documents accordingly. For more information, see Learn about eDiscovery solutions | Microsoft Learn. MC1024387 — Microsoft Purview | Data Loss Prevention: New predicates for email DLP to detect number of domains or recipients Microsoft 365 Roadmap ID 483158 Customers have expressed a significant pain point in managing and controlling the distribution of sensitive information in email. The lack of predicates to monitor the number of recipients or domains in outgoing emails poses a risk of data leaks and non-compliance with regulatory requirements. We are addressing this issue in Microsoft Purview | Data Loss Prevention by rolling out new predicates that will enable organizations to set precise policies that trigger alerts or actions when emails exceed a specified number of recipients or domains. This feature is essential for enhancing data security, ensuring compliance, and providing peace of mind to organizations concerned about unauthorized data dissemination. When this will happen: Public Preview: We will begin rolling out late April 2025 and expect to complete by mid-May 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late May 2025 and expect to complete by mid-June 2025. How this will affect your organization: After this rollout, admins can use the new predicates in Data Loss Prevention > Policy settings > Create rule > Unique recipients greater than and Unique domains greater than to take action on emails based on the number of recipients or domains in the email: This change will be available by default for admins to configure. What you need to do to prepare: This rollout will happen automatically by the specified dates 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: New-DlpComplianceRule (ExchangePowerShell) | Microsoft Learn (will be updated before rollout) MC1006621 — (Updated) Microsoft Purview | Insider Risk Management: New compromised user context in Microsoft Entra Microsoft 365 Roadmap ID 420938 Updated April 24, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Purview | Insider Risk Management: IRM analysts will be able to identify if a user being investigated has any compromised user alerts in Microsoft Entra. The new visibility will help the analyst formulate the right response action, such as escalating the Incident to SOC teams for quick remediation. When this will happen: General Availability (Worldwide): We will begin rolling out mid-May 2025 (previously mid-April) and expect to complete by late May 2025 (previously late April). General Availability (GCC, GCC High, DoD): We will begin rolling out early-August 2025 and expect to complete by late August 2025. How this will affect your organization: Microsoft Entra offers two types of compromised user detections: Sign-in risk detections: Compromise risk associated with a specific sign-in User risk detections: Compromise risk associated with a specific user After this rollout: Risk detections will be available in the indicator timeline in the alert investigation experience. Risk detections will not impact the risk score or severity of Insider Risk Management alerts. To access the new risk detections, go to Microsoft Purview portal > Settings > Insider Risk Management > Policy indicators > Built-in Indicators. Scroll down to Microsoft Entra ID Protection indicators, open the dropdown menu and select the applicable indicators. When you create a policy, you will find Microsoft Entra ID Protection indicators on the Indicators page. 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 users about this change and update any relevant documentation. Insider risk management admins can opt into risk detections from Insider Risk Management global settings. Insider risk management admins need to opt into risk detection in Insider Risk Management policies. 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 What are risks in Microsoft Entra ID Protection - Microsoft Entra ID Protection | Microsoft Learn Configure policy indicators in insider risk management | Microsoft Learn MC1004410 — Microsoft Purview | Endpoint Data Loss Prevention - Classification improvements on file read access in macOS devices Microsoft 365 Roadmap ID 478930 Updated April 14, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 (previously April 2025) and expect to complete by early April 2025 (previously late May). 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 Updated April 2, 2025: We have updated the rollout timeline below. Thank you for your patience. 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-September 2025 and expect to complete by late September 2025 General Availability (Worldwide): We will begin rolling out mid-October 2025 and expect to complete by late October 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. 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. MC986518 — (Updated) Microsoft Purview | Insider Risk Management: Updates to email scoring (GCC, GCC High, DoD) Microsoft 365 Roadmap ID 471010 Updated March 5, 2025: We have updated the rollout timeline below. Thank you for your patience. 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 March 2025 (previously late February). 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 MC971035 — Microsoft Purview | Data Lifecycle Management: New secure workflow to bypass legal holds and retention policies Microsoft 365 Roadmap ID 392838 Updated March 17, 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 September 2025 (previously late March) and expect to complete by mid-October 2025 (previously mid-April). 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 March 7, 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 mid-March 2025 (previously late February) and expect to complete by mid-March 2025 (previously late March ). 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. 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 April 10, 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 late April 2025 (previously late February) and expect to complete by early May 2025 (previously late mid-May). 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. MC937158 — (Updated) Microsoft Purview | Insider Risk Management: New scenario-based policy templates Microsoft 365 Roadmap ID 409966 Updated April 3, 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 early April 2025 (previously late March). 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 MC911618 — (Updated) Microsoft Purview | Insider Risk Management: Multi-policy settings in Adaptive Protection Microsoft 365 Roadmap ID 171735 Updated March 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 High, DoD): We will begin rolling out late March 2025 (previously late May) and expect to complete by late April 2025 (previously mid-June). GCC is complete. 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 MC833890 — (Updated) Microsoft Word, Excel, PowerPoint: Protect sensitive files with dynamic watermarking Microsoft 365 Roadmap ID 400717 Updated April 22, 2025: We have recently implemented the necessary fixes to expand the GA scope, enabling support for dynamic watermarking on labels with both user-defined and admin-defined permissions (the original scope). 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. This setting is supported for labels with admin-defined protection. 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 MC805721 — (Updated) Purview | Insider Risk Management: Adaptive Protection is generally available in GCC, GCCH, and DoD Microsoft 365 Roadmap ID 335856 Updated March 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 High, DoD): We will begin rolling out late March 2025 (previously late February) and expect to complete by late April 2025 (previously late March). GCC is complete. 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. MC791110 — (Updated) Microsoft Purview | Data Lifecycle Management: New integration with Adaptive protection Microsoft 365 Roadmap ID 392839 Updated April 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 late September 2025 (previously late May) and expect to complete by mid-October 2025 (previously mid-June). 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. MC788980 — (Updated) Microsoft Purview | Insider Risk Management: Granular trigger throttling Updated March 28, 2025: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience. Coming soon, Microsoft Purview Insider Risk Management will be rolling out public preview of granular trigger throttling limits. When this will happen: Public Preview: We will begin rolling out late October 2024 (previously late August) and expect to complete by late January 2025 (previously late October). General Availability: We will communicate via Message center when we are ready to proceed. How this will affect your organization: With this update, we are introducing more granular trigger throttling limits to isolate the impact of a surge in noisy trigger volumes and prevent other policies from being affected. This ensures that organizations can receive critical alerts without being throttled by these limits. By default, these throttling limits will be applied: All sensitive triggers, including HR signals, Azure AD leavers, and custom triggers, will be limited to 15,000 per day per trigger. All other triggers will be limited to 5,000 per day per trigger. Additionally, the policy health warning messages will be enhanced to assist admins with appropriate permissions in effectively identifying and addressing noisy triggers. What you need to do to prepare: No action is needed from you to prepare for this rollout. You may want to notify your admins about this change and update any relevant documentation as appropriate. 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: Insider risk management | Microsoft Learn MC690178 — (Updated) Information Protection - Keyword highlight support for document trainable classifiers Microsoft 365 Roadmap ID 170738 Updated April 28, 2025: To ensure the best customer experience, we have decided to rollout until October 2025. Thank you for your patience. The keyword highlighting feature for Trainable Classifiers emphasizes the top 10 distinct keywords/phrases that influence the classification, showcasing up to 10 occurrences of each keyword. The feature is being enabled through: Content Explorer: Viewing the classified document through Content explorer will highlight the keywords that match the Trainable classifiers detected. Test Trainable classifier: Uploading a document and testing it for a specific classifier OR selecting the document in the classifier’s matched item will highlight the keywords that match the Trainable classifier detected. Note: This feature will only work on the new/edited documents after the date “keyword highlight” has been enabled. When this will happen: Rollout will begin in early October 2025 (previously early June 2024) and will complete by late October 2025 (previously late June 2025). How this will affect your organization: The keyword highlight feature enables you to: Quickly locate text that caused the positive outcome in the classifier. Establish trust in the effectiveness of trainable classifiers. Reduce the time to decide and take further actions. What you need to do to prepare: This feature will only work on new/edited documents after the date “keyword highlight” has been enabled. Release of Keyword Highlighting for Train & new Business Context Classifier (microsoft.com) Trainable classifiers definitions Increase Classifier Accuracy | Microsoft Learn Defender XDR MC1048617 — Introducing new Advanced Hunting Tables to hunt on Teams messages and URLs Microsoft 365 Roadmap ID: 487411 We are happy to introduce three new Advaned Hunting tables designed to facilitate hunting of Teams messages containing URLs within your organization. The MessageEvents table enabled hunting across Teams messages containing URLs within your tenant. This includes both, known malicious messages blocked immediately after delivery and messages with no malicious content. Each message is uniquely identified by the TeamsMessageId, which can be utilized to establish joins across tables. As there is only a single copy of each message, even in instances of delivery to multiple recipients, only one instance of the message will be accessible for viewing in Advanced Hunting. The MessagePostDeliveryEvents table provides the capability to analyze Teams messages containing URLs within your tenant, that have been identified as malicious after message delivery. If you have Zero-hour Auto Purge (ZAP) enabled for Teams, messages blocked post-delivery will be observable within this table. Each message is uniquely identified by the TeamsMessageId. The MessageURLInfo table support the ability to hunt across URLs embedded within Teams messages in your organization. The tables can be found under the Email & Collaboration in Advanced Hunting. When this will happen: Public Preview (Worldwide): We will begin rolling out late April 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out in late May 2025 and expect to complete by mid-June 2025. How this will affect your organization: You will now have the ability to hunt on Teams messages from Advanced Hunting. What you need to do to prepare: No additional action will be needed to prepare for this rollout. The new hunting tables will be available in your tenant and can be viewed with the right security permissions. More information on these new tables can be found here: MessageEvents: MessageEvents table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn MessagePostDeliveryEvents: MessagePostDeliveryEvents table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn MessageURLInfo: MessageUrlInfo table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn Microsoft 365 Copilot MC1056992 — Pages created in Microsoft 365 Copilot Chat will open in Microsoft 365 Copilot app Coming soon: Microsoft 365 Copilot Pages created in Microsoft 365 Copilot Chat will open in the Microsoft 365 Copilot app for the web. This change is designed to reinforce the Microsoft 365 Copilot app as the center for all content created with Copilot. When this will happen: General Availability (Worldwide, GCC): We will begin rolling out early May 2025 and expect to complete by late May 2025. How this will affect your organization: After this rollout, users who search for Copilot Pages or select links to Copilot Pages will be taken to m365.cloud.microsoft where the link will open. For example, if a user shares a Copilot Pages link with another user in Microsoft Teams, that link will open in the Microsoft 365 Copilot app for the web. Screen recording: We will also update the Copilot Pages icon in this rollout. Left: The old icon. Right: The new icon: This rollout applies to files created in Copilot Chat and files created by the user in My Workspace in Loop. This rollout will not change or affect Loop files created in Team chat, email, or in Loop workspaces. Sensitivity labels for Copilot Pages are available now for Worldwide customers and will be available to GCC customers for Copilot Pages by late April 2025. Learn more about new Copilot capabilities coming soon: Copilot Pages service description What’s New in Microsoft 365 Copilot for Government These changes will be on by default. What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change. Before rollout, we will update this post with revised documentation. MC1056264 — (Updated) Microsoft PowerPoint: Reference a TXT file when creating a presentation with Microsoft 365 Copilot Microsoft 365 Roadmap ID 488795, Roadmap ID 488796, and Roadmap ID 488794 Updated April 18, 2025: After further review we have decided not to proceed with GCC at this time. We also have updated the rollout timeline below. We apologize for any inconvenience When creating a presentation in Copilot for Microsoft PowerPoint, users will be able to reference TXT files in addition to Microsoft Word files. A Microsoft 365 Copilot license is required to use this feature. This message applies to PowerPoint for Windows desktop, PowerPoint for Mac desktop, and PowerPoint on the web. When this will happen: General Availability (Worldwide): We will begin rolling out early May 2025 and expect to complete by mid-May 2025. How this will affect your organization: After this rollout, users can see TXT files when searching for files that Copilot can use to create a presentation. Select the Copilot icon from the PowerPoint ribbon, choose Create a presentation from [file], and search for TXT files by file name or paste the URL of your TXT file from Microsoft OneDrive or Microsoft SharePoint: This feature 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. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Learn more: Create a new presentation with Copilot in PowerPoint - Microsoft Support (will be updated before rollout) MC1052912 — (Updated) Microsoft Teams - Copilot Summary for Transferred Calls Microsoft 365 Roadmap ID 484123 Updated April 28, 2025: We have updated the timeline below. Thank you for your patience. Copilot enabled users will now be able to share the summary of the call from within the transfer panel and the context will be shown in the toast notification and within the call. This feature requires a Copilot license to be enabled. When this will happen: Targeted Release: We will begin rolling out early June 2025 and expect to complete by mid-June 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. How this will affect your organization: Once available and if transcribe is enabled, users will be able to share a summary or a call from the transfer panel. What you need to do to prepare: You may consider updating your training and documenation. No admin configuration required other than allowing users to transcribe their calls. MC1040542 — (Updated) Microsoft 365 Copilot and Microsoft 365 Copilot Chat: Increased transparency for web queries (GCC) Microsoft 365 Roadmap ID 483965 Updated April 17, 2025: We have updated the rollout timeline below. Thank you for your patience. Users with licenses for Microsoft 365 Copilot and Microsoft 365 Copilot Chat will soon be able to see the exact web search queries used by Copilot to generate its response with relevant web data. Users will see this feature if you enable web search. Before this rollout, Copilot provided a list of websites that it used to generate its response. After this rollout, a user will also be able to review the exact queries sent by Copilot, which will enhance the user's awareness of how Copilot sourced the websites used to generate its response. Learn more: Introducing greater transparency and control for web search queries in Microsoft 365 Copilot and Microsoft 365 Copilot Chat | Microsoft Community Hub This feature will be available for both Web and Work chats in Microsoft 365 Copilot and in Microsoft 365 Copilot Chat. For more information on Microsoft 365 Copilot Chat availability, please refer to MC1036580 Microsoft 365 Copilot Chat for GCC customers (published March 2025). A Microsoft 365 Copilot license or an eligible Microsoft 365 license for Microsoft 365 Copilot Chat is required. When this will happen: General Availability (GCC): We will begin rolling out mid-May 2025 (previously early April) and expect to complete by late May 2025 (previously mid-April). How this will affect your organization: This feature will be available by default if you have enabled web search. Learn more about managing web search in Copilot for your organization 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. MC1036580 — (Updated) Microsoft 365 Copilot Chat for GCC customers Microsoft 365 Roadmap ID 464984 Update April 25, 2025: We are currently preparing for availability. However, in a change to our original communication, we do not expect to complete the rollout of Copilot Chat in the GCC cloud until mid-May 2025. We will share more details as we can. Beginning mid-May 2025, Microsoft 365 Copilot Chat (“Copilot Chat”) will be available by default at no additional cost for Entra account users with an eligible Microsoft 365 subscription: Microsoft 365 F1, F3, G3, or G5 Office 365 F1, F3, G3, or G5 Copilot Chat will be available by default from the web. It will also be available and pinned by default in the Microsoft 365 Copilot app (web, desktop), Teams (web, desktop), and Outlook (web, desktop). If Copilot Chat availability for any of these entry points changes, we will inform you. Web grounding in Copilot Chat will be off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy. Note: This only applies to GCC cloud. Copilot Chat availability for GCC High and DoD will be communicated later. When this will happen: General Availability (GCC): We will begin rolling out mid-May 2025 (previously mid-April). How this will affect your organization: Users will be able to access Copilot Chat from the web, and in the Microsoft 365 Copilot app, Outlook, and Teams. Copilot Chat offers: Secure, enterprise-ready AI chat powered by models like GPT-4o. o Note: Web grounding will be off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy. When web grounding is off, users will be alerted via a notification in the UI and Copilot will only use the LLM to provide a response. IT controls for data governance, including enterprise data protection. Note: Agents will not be available initially. Agent availability will be communicated later. What you need to do to prepare: Once Copilot Chat rolls out and is available in your tenant, you will be able to manage user access across entry points. To block access to Copilot Chat, refer to the documentation: Removing access to Copilot Chat. To block access from the web, and in the Microsoft 365 Copilot app and Outlook, refer to Step 2. To block access in Teams, refer to Step 3. Note: As Copilot Chat will be pinned by default in the Microsoft 365 Copilot app, Outlook, and Teams once available, you do not need to implement Step 1. Additionally, Copilot Chat will not be available initially through the Microsoft Edge sidebar, so you do not need to implement Step 4. Web grounding in Copilot Chat is off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy. To manage web grounding in Copilot Chat, please refer to our documentation here. To help your organization get the most out of the Microsoft 365 Copilot Chat, we have updated the Copilot Success Kit and added the new Copilot Chat and Agent Starter Kit. This includes: Copilot Chat user training guideto help your users get started with Copilot Chat and understand how to access it. Copilot Chat and agent IT set up and controls guideto plan, deploy, manage, and measure Microsoft 365 Copilot Chat in your organization. User engagement templatesin a variety of formats—including email, Viva Engage, and Teams—that you can leverage to communicate updates and new features to your users. Note: You can customize these assets to remove content about agents since agents are not available initially. Please also refer to documentation for Copilot Chat here: Overview of Microsoft 365 Copilot Chat MC1036562 — (Updated) Microsoft 365 Copilot: Web chat access for GCC Tenants Update April 16, 2025: We are currently preparing for availability. However, in a change to our original communication, we do not expect to complete the rollout of Web chat for Microsoft 365 Copilot-licensed users in GCC tenants until mid-May 2025. We will share more details as we can. Starting mid-April 2025, Microsoft 365 Copilot-licensed users in GCC tenants will gain access to Web chat, alongside the existing Work chat, as part of their chat experience. Web grounding in Web chat will be off by default unless you have explicitly allowed for web grounding in Microsoft 365 Copilot using the “Allow web search in Copilot” policy. When this will happen: General Availability (GCC): We will begin rolling out mid-April 2025. How this will affect your organization: Microsoft 365 Copilot-licensed users will have access to Web chat starting mid-April. When web grounding is off, users will be alerted via a notification in the UI and Copilot will only use the LLM to provide a response in Web chat. What you need to do to prepare: Web grounding in Web chat will be off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy. Learn more about the “Allow web search in Copilot” policy here. MC1031286 — (Updated) Microsoft PowerPoint: Suggestions for slide templates Microsoft 365 Roadmap ID 475053, 475054 Updated April 24, 2025: We have updated the timeline below. Thank you for your patience. Updated April 8, 2025: We have updated this message to show as intended. The Roadmap items associated with this message have been updated. Additionally, we have determined that we will not be rolling out this change to GCC at this time. We apologize for any confusion this may have caused. A new set of suggestions will soon be shown in Designer for Copilot users when creating a new PowerPoint presentation and adding a new slide. Non-Copilot users will retain access to the standard Designer layouts provided to all Microsoft 365 users. Users with a Microsoft 365 Copilot license will see those standard Designer layouts and additionally, these new Copilot suggestions. This message applies to Microsoft 365 Copilot in PowerPoint on Windows desktop and Mac desktop and to Microsoft PowerPoint on Windows desktop and Mac desktop. When this will happen: General Availability (Worldwide): This change will happen automatically with these three builds: Microsoft 365 Copilot for Windows desktop build 16.0.18526.20000 (planned for release April 7, 2025) Microsoft 365 Copilot for Mac desktop build 16.95.25030315 (planned for release April 21, 2025) This feature will also be coming to Microsoft 365 Copilot for the web in early May 2025 (previously April). How this will affect your organization: Copilot users will gain access to new narrative-driven layout suggestions within the Designer pane when adding new slides. Furthermore, a selection of new templates designed specifically for Copilot functionality will be available in Designer when starting a new blank presentation. Non-Copilot users will retain access to the standard Designer layouts provided to all Microsoft 365 users. This change will be available by default for those with a Copilot license. Designer will continue to be available for non-Copilot users in PowerPoint as described in this message. What you need to do to prepare: This rollout will happen automatically by the specified dates 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 Before rollout, we will update this post with new documentation. MC1031280 — (Updated) Microsoft 365 Copilot: Pages feature (GCC) Microsoft 365 Roadmap ID 485177 Updated March 20, 2025: We have updated the content. Thank you for your patience. The Pages feature enables users to add their Microsoft 365 Copilot responses to a page where they can edit and share with others for collaboration. This happens within the Microsoft 365 Copilot app. For more information, see Introducing Microsoft 365 Copilot Pages - Microsoft Support. When this will happen: General Availability (GCC): We will begin rolling out late March 2025 and expect to complete by early April 2025. How this will affect your organization: Users need to have Copilot Pages enabled for this feature update to work. Enabling this feature allows users to create Loop Page files via Copilot. What you need to do to prepare: For more information, see Copilot pages for IT Admins. 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. MC1020327 — (Updated) M365 Copilot for GCC Environments: Wave 2 Microsoft 365 Roadmap ID 483357 Updated March 26, 2025: We have updated the content. Thank you for your patience. 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 Copilot Pages, 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. MC1003344 — (Updated) Microsoft Copilot: File summary in Microsoft Teams chat Microsoft 365 Roadmap ID 418564 Updated April 23, 2025: We have updated the 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 June 2025 and expect to complete by mid-June 2025. General Availability (Worldwide): We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (GCC): We will begin rolling out mid-June 2025 and expect to complete by late 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. Outlook MC1058261 — New Microsoft Outlook: Changes to how shared mailboxes are displayed in the folder pane Microsoft 365 Roadmap ID 486837 Coming soon for new Microsoft Outlook for Windows desktop: To align with the behavior of classic Outlook for Windows, we will display shared mailboxes in the same way accounts are displayed and add a Shared icon to give users a visual distinction between standard mailboxes and shared mailboxes. When this will happen: Targeted Release: We will begin rolling out early May 2025 and expect to complete by late May 2025. General Availability (Worldwide): We will begin rolling out early June 2025 and expect to complete by late June 2025. General Availability (GCC): We will begin rolling out early July 2025 and expect to complete by late July 2025. How this will affect your organization: After this rollout, shared mailbox users and delegates will no longer have a Shared with me section in the folder pane on the left of the screen. Shared mailboxes and shared folders will display at the same level as accounts in the folder pane. Users will also see a teaching message pointing to the new shared mailboxes and shared folders, so users are not surprised by the change. Users will not lose any shared mailboxes or shared folders. Left: The Shared with me section before the rollout. Right: After the rollout: This change will be on 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. Learn more: Open and use a shared mailbox in Outlook - Microsoft Support (will be updated before rollout) #newoutlookforwindows MC1057715 — Outlook mobile: Edit a recurring event from a chosen date going forward by selecting 'This and all following events' Microsoft 365 Roadmap ID 486835 Users can now edit a recurring event from a chosen date going forward by selecting This and all following events on Android or Edit this and all following events on iOS. When this will happen: General Availability (Worldwide, GCC, GCCHigh, DoD): We will begin rolling out on early May 2025 and expect to complete by late May 2025. How this will affect your organization: Users can now bulk edit all future instances of a recurring event from a chosen date going forward. Anytime a user chooses to edit or cancel an event, they will see the This and all following events option on Android or Edit this and all following events on iOS. Previously, users would only see the option to Edit this event only or Edit all events in the series. Android: iOS: 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. MC1056989 — Microsoft Outlook: New "Shared with me" page in Settings for shared email accounts and folders Microsoft 365 Roadmap ID 486836 The new Microsoft Outlook for Windows and Microsoft Outlook for web will soon have a new Settings page called Shared with me where users can view and manage all shared email accounts and folders that they have been granted permission to access. Before April 30, 2025, we will update this post with new documentation. When this will happen: Targeted Release: We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025. General Availability (Worldwide): We will begin rolling out early June 2025 and expect to complete by early July 2025. General Availability (GCC): We will begin rolling out early July 2025 and expect to complete by early August 2025. How this will affect your organization: After this rollout, users will be able to access the new page in Outlook Settings > Accounts > Shared with me: If users have permission to access shared mailboxes or folders before this rollout, they will appear on this page. After this rollout, users can add new shared mailboxes and folders if their colleague has given them permission to access the mailbox and/or folders. User can remove shared mailboxes and folders from this page, but this action does not revoke permission granted by a colleague. If a colleague revokes a permission, the email account will remain on this page in a disabled state and will say that the user no longer has permission. If your organization uses shared mailboxes, the Shared with me page will give users more insight into the permissions they have for shared mailboxes without needing to ask an admin or mailbox owner. If your organization does not use shared mailboxes, this rollout will not impact you. The Shared with me page will be available for users, but it will stay empty if they do not add shared mailboxes or folders. This change will be available to users 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. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. #newoutlookforwindows MC1047925 — Outlook: open attachments while offline in the new Outlook for Windows Microsoft 365 Roadmap ID 472026 We are adding more functionality to offline mode in the new Outlook for Windows. You will now be able to open and save attachments from your emails without an internet connection. Please note that this is only scoped to classic file attachments. OneDrive and SharePoint links in the body of the emails will still need a connection to be opened. For this functionality to work you need to make sure Offline is enabled and offline attachments are enabled. At the user level you can verify this by checking two settings in new Outlook Settings - General - Offline: Enable offline email, calendar and people Include file attachments This functionality will also be enabled or disabled based on the True/False behavior of the already existing Mailbox Policy: OWAMailboxPolicy- OfflineEnabledWin. Attachments from emails within the timeframe and folder scope selected in the "Settings - General - Offline" will be synced and available locally for users to open without an internet connection. When this will happen: Targeted Release (Worldwide): We will begin rolling out on mid-May 2025 and expect to complete by late May 2025. General Availability (Worldwide): We will begin rolling out on late June 2025 and expect to complete by mid-July 2025. General Availability (GCC): We will begin rolling out on mid-July 2025 and expect to complete by late July 2025. How this will affect your organization: Classic attachments from emails within the timeframe and folder scope selected in the "Settings - General - Offline" will be synced and available locally for users to open without an internet connection: What you need to do to prepare: The default on or off of this feature will depend on your existing Offline configuration in the new Outlook via the following policy: OWAMailboxPolicy- OfflineEnabledWin. This feature will not change the default of this Policy. You can find more information about this Policy here: Set-OwaMailboxPolicy If you have not made any changes to this Policy, then the default of this feature will be on. MC1041465 — (Updated) New Microsoft Outlook for Windows and Outlook on the web: Optimized hover actions in the message list Microsoft 365 Roadmap ID 429868 Updated April 28, 2025: We have updated the timeline below. Thank you for your patience. In new Outlook for Windows and Outlook on the web, the hover actions in the message list will be moved to the Sender/From column to be more space-efficient and minimize unnecessary mouse travel for users with their Reading Pane set to Hide or Bottom. The large width occupied by the DateTime Received column will thus be reduced. For all users, a one-time shortcut to change/set your hover actions will be provided. After the changes to the hover actions, the first action will be replaced by a quick button (gear button) to change/set your hover actions. After that button has been triggered once, it will disappear, and your hover action settings will kick in fully. When this will happen: Targeted Release: We will begin rolling out mid-May 2025 (previously early April) and expect to complete by late May 2025 (previously late April). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late May 2025 (previously late April) and expect to complete by late June 2025 (previously late May). How this will affect your organization: For new Outlook for Windows and Outlook on the web, hover actions in the message list will be moved to the Sender/From column to reduce the large width occupied by the DateTime Received column. 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. #newoutlookforwindows MC1041456 — New Microsoft Outlook and Outlook for the web: New setting to enable two-click view for encrypted emails Microsoft 365 Roadmap ID 483883 New Outlook for Windows desktop and Outlook for the web will soon support a two-click view for encrypted emails, which requires user confirmation before allowing access to encrypted emails. As an admin, you can enable the two-click feature for your users. When this will happen: General Availability (Worldwide): We will begin rolling out early 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 late May 2025. How this will affect your organization: With this two-click feature enabled, users will be required to select View message for every encrypted email, and then the email will render. This feature ensures that users deliberately access encrypted email content, reducing the risk of accidental exposure, especially in unsecured environments like public spaces or during screen sharing: Admins can find the TwoClickMailPreviewEnabled setting in the Microsoft Azure directory. This setting is a Boolean type with default = 0, which means the experience is disabled by default. To enable the feature for all users in your tenant, set value = 1. Alternatively, you can access and set the value for this setting using the Microsoft PowerShell cmdlet -Set-OrganizationConfiguration in the Microsoft Exchange Online PowerShell. Learn more: Exchange Online PowerShell | Microsoft Learn By default, the two-click setting is off. What you need to do to prepare: No action is required from admins unless you want to enable this feature. This rollout will happen automatically by the specified dates 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 plan to enable this feature. #newoutlookforwindows MC1025213 — (Updated) Microsoft Outlook: Message recall in the Outlook app for iOS and Android Microsoft 365 Roadmap ID 471444 Updated April 10, 2025: We have updated the rollout timeline below. Thank you for your patience. From the Microsoft Outlook for iOS and Android apps, you can request that Outlook to attempt to recall a message sent to a colleague within your organization. When this will happen: General Availability (Worldwide, GCC, GCC High): We will begin rolling out in early March 2025 and expect to complete by late April 2025 (previously late March). How this will affect your organization: Users will have the option to request a recall attempt for a sent email. This feature provides an additional layer of control for users who need to retract emails sent in error. Learn more: Recall emails in Outlook for Android and iOS. 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. 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 March 26, 2025: We have updated the rollout timeline below. 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 late March 2025 (previously mid-March) and expect to complete by early April 2025 (previously late March). What you need to do to prepare: 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 MC962527 — Updated: New Microsoft Outlook for Windows and web: Delegates can create new categories for the account owner's Calendar Microsoft 365 Roadmap ID 473997 Updated March 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon for new Microsoft Outlook for Windows and Outlook on the web: Delegates can create new categories on behalf of the account owner who granted them delegate permissions. Delegates can also apply categories to the Calendar of the account owner. When this will happen: Targeted Release: We will begin rolling out mid-January 2025 and expect to complete by mid-February 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-February 2025 and expect to complete by mid-April 2025 (previously mid-March). How this will affect your organization: To access the new capability, the account holder assigning the permissions should open: Open their Calendar > Hover over a calendar name and select the three-dot More optionsmenu. Then, select Sharing and permissions. Enter the email address of the desired delegate. Select Delegate from the dropdown menu and check the box forLet delegate manage categories.Select Share. After the account holder applies the necessary permissions, delegates can view the list of the delegator's categories in their Settings > Accounts > Categories and select the delegator's account from the dropdown menu. This change will be available by default. The new checkbox for Let delegate manage categories will not be selected 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: About delegates: Allow someone to manage your mail and calendar in Outlook - Microsoft Support (will be updated before rollout) #newoutlookforwindows MC947045 — (Updated) Microsoft Outlook for iOS and Android: Attach emails while composing an email Microsoft 365 Roadmap ID 464206 Updated April 9, 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 April 2025 (previously late March). 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. MC946791 — (Updated) Microsoft Outlook for iOS and Android: Minimize the compose window to multitask in the Outlook app Microsoft 365 Roadmap ID 470304 Updated April 1, 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 April 2025 (previously late March). 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. MC926892 — (Updated) Microsoft Outlook: Sync folder order Microsoft 365 Roadmap ID 422816 Updated April 18, 2025: We have updated the rollout timeline below. Thank you for your patience. The order of folders in Microsoft Outlook mobile will now sync to match the folder order on Outlook web, Mac, and Windows platforms. When this will happen: General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early May 2025 (previously mid-April) and expect to complete by late June (previously mid-May). Users will now see an updated folder order on their mobile devices that reflects the folder order on Outlook web and desktop platforms. If users want to re-order the folders, they must do so on Outlook for the web, Mac, and Windows devices, as folder re-ordering is currently not supported on mobile devices. This feature is on by default and cannot be turned off. 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. MC917748 — (Updated) Microsoft Teams and Microsoft Outlook: Name pronunciation on the profile card Microsoft 365 Roadmap ID 420329 Updated April 29, 2025: We have now shipped the admin control, the name pronunciation feature is OFF by default so admins will need to toggle it ON. The instructions in this support document explain how to turn the feature on. Important! Starting from April 29, 2025, if you haven't turned the name pronunciation feature ON, any existing recordings on profile cards will be deleted. Your users will need to re-record their name pronunciation. The admin toggle for Name Pronunciation is rolling out to Production starting this week. Admins will be required to configure in the admin center to avoid loss of data. Instructions to configure are in this support article. Please expect the admin toggle in the admin center starting the week of April 14th through April 18th, 2025. We will be shipping to preview without the admin toggle however an admin toggle will be available before general availability. If there are concerns or your organisation wants to opt out, please raise an incident to address this. Coming soon to Microsoft Outlook and Microsoft Teams: A name pronunciation feature on the profile card in Microsoft Teams and Microsoft Outlook. This new feature helps promote diversity by giving working colleagues relevant information about each other. Names are a crucial part of a person’s identity. The incorrect pronunciation of a person’s name can lead to anxiety and offense in some cases. Correctly pronouncing a person’s name helps to create an inclusive environment. Pronunciation data is stored in each user's mailbox until the user deletes the recording. Learn more: Data Residency for Exchange Online - Microsoft 365 Enterprise | Microsoft Learn This message applies to Teams for Windows desktop, Teams for Mac desktop, new Outlook for Windows desktop, and new Outlook for web. When this will happen: Targeted Release: We will begin rolling out mid-November 2024 and expect to complete by late November 2024. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late March 2025 (previously mid-January) and expect to complete by late April. How this will affect your organization: After this rollout, users can record and share the correct pronunciation of their name on their profile card. With a click, users can play and listen to name pronunciations recorded by their colleagues. To open a profile card in Outlook, double-click a name in the To or From field in any sent or received email. To open your profile card in Teams, select your profile photo in the upper right corner of the screen, and then select your name. To listen to a colleague's recorded pronunciation, select the speaker icon on their profile card. To record the pronunciation of a name, open your profile card in Outlook or Teams, and select the microphone icon. What you need to do to prepare: This feature is off by default. As an admin, you can enable the feature in Microsoft Graph using these instructions: namePronunciationSettings resource type - Microsoft Graph beta | Microsoft Learn Before rollout, we will update this post with revised documentation. You may want to notify your users about this change and update any relevant documentation. #newoutlookforwindows MC901831 — (Updated) New Microsoft Outlook for web and Windows: Organize and reorder folders Microsoft 365 Roadmap ID 378775 Updated March 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon: We will automatically import the folder order from classic Microsoft Outlook for Windows to new Microsoft Outlook for Windows and Outlook for the web. If users have not customized their folder order, the default view will continue to display folders alphabetically in the new Outlook. When this will happen: Targeted Release: We will begin rolling out late November 2024 (previously early October) and expect to complete by late December 2024 (previously early November). General Availability (Worldwide): We will begin rolling out January 2025 (previously early November) and expect to complete by early February 2025 (previously early December). General Availability (GCC, GCC High, DoD): We will begin rolling out early February 2025 (previously early December) and expect to complete by early May 2025 (previously early March). How this will affect your organization: Before this rollout: If a user enabled custom folder order in classic Outlook, the custom order is preserved in the new Outlook for Windows and Outlook on the web. This may result in changes to the folder structure for affected users, as the new Outlook supports only alphabetical ordering. After this rollout: users will see the custom folder order they previously enabled in classic Outlook. Special folders such as Inbox, Drafts, Sent Items, and others will still remain at the top of the folder list, even when the rest of the folders are arranged alphabetically. This change is on by default. To change folder order, go to the new Outlook ribbon, and select View > Layout > Folder pane. Choose one of these options: Order folders A to Z order: This will organize folders alphabetically Custom order Users can hover next to each folder name to see the three-dot menu where they can move folders with drag-and-drop or the move up/move down options: What you need to do to prepare: This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Change the order of folders in the Folder Pane - Microsoft Support (will be updated before rollout) MC847877 — (Updated) Microsoft Outlook for iOS and Android: Choose fonts while composing Microsoft 365 Roadmap ID 409969 Updated April 1, 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 April 2025 (previously late March). 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 April 17, 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 late April 2025 (previously early April). 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 MC714520 — (Updated) Apps for the web: Grid view for tasks in Microsoft To Do web version and To Do inside Microsoft Outlook Microsoft 365 Roadmap ID 381749 Updated April 23, 2025: We have updated the timeline below. Thank you for your patience. In Microsoft 365 apps for the web, users can see their tasks in a grid view and can update details inline in To Do on web and To Do app inside Microsoft Outlook. When this will happen: General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out late April 2024 (previously early April) and expect to complete by mid-May 2025 (previously mid-April). How this will affect your organization: When users open To Do on web within Microsoft Outlook, they will see their tasks in a tabular format or grid. They can continue to have the list view if preferred. What you need to do to prepare: There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate. Exchange Online / Defender for Office 365 MC1061102 — Microsoft Defender for Office 365: Auto-remediation of malicious URL and file clusters identified through AIR (preview) Microsoft 365 Roadmap ID 186576 Coming soon: The automated investigation and response (AIR) capability in Microsoft Defender for Office 365 (MDO) will allow admins to configure auto-remediation of malicious entity clusters (for URL clusters and file clusters) identified by AIR. Auto-remediation expands on the existing capability provided through AIR by equipping customers to further expedite remediations through automation, to increase protection and reduce SOC workload. Auto-remediation will not be on by default and admins desiring to use the new automation will need to turn on auto-remediation for each cluster type in the new MDO automation settings page in Defender. When this will happen: Public Preview: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by early June 2025. How this will affect your organization: After this rollout, admins will have a new MDO automation settings page in the Defender portal in Settings > Email & collaboration > MDO automation settings where you can turn on auto-remediation for malicious URL clusters and file clusters identified through MDO AIR: After you have enabled the new feature, AIR will automatically execute the soft deletion of messages identified in malicious URL clusters and file clusters that remain in mailboxes. Auto-remediated clusters will appear directly in Action center history for review. Also, messages remediated through AIR auto-remediation will be designated as attributed to automation in Explorer, in Advanced hunting and on the email entity page. What you need to do to prepare: Auto-remediation will be off by default. If desired, turn on as described in this message. This rollout will happen automatically by the specified dates with no admin action required before the rollout. Learn more: Automated remediation in AIR - Microsoft Defender for Office 365 | Microsoft Learn. MC1024399 — (Updated) Microsoft Exchange Online: New limit for dynamic distribution groups (DDGs) Updated April 15, 2025: We have updated the rollout timeline below. Thank you for your patience. We will soon introduce a new limit on dynamic distribution groups (DDGs) in Microsoft Exchange Online. Each organization will be limited to a maximum of 3,000 DDGs. After this limit is reached, admins will need to remove existing DDGs before creating new ones. Learn more: Exchange Online limits - Service Descriptions | Microsoft Learn When this will happen: General Availability (Worldwide, GCC): We will begin enforcing this limit in mid-April 2025 (previously early April). How this will affect your organization: If your organization has fewer than 3,000 DDGs, this change will not impact you. However, after your organization reaches this limit, you will not be able to create new DDGs until some existing DDGs are removed. This change will be on by default and cannot be turned off by admins. What you need to do to prepare: The enforcement of the DDG limit 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. We recommend reviewing the usage of Dynamic Distribution Groups (DDGs) in your organization and removing any DDGs that are no longer needed. You can use the Dynamic distribution groups report in the Exchange admin center (EAC) to see the number of DDGs in your organization and insights into their usage. To access this report, go to the EAC > Reports > Mail flow > Dynamic distribution group report. Learn more: Dynamic Distribution Groups report in the new EAC in Exchange Online | Microsoft Learn MC1023294 — (Updated) New Exchange Online Tenant Outbound Email Limits Updated April 21, 2025: We have updated the timelines below. Thank you for your patience. To reduce the risk of misuse and abuse of Exchange Online resources and ensure service availability for all users, we’ll soon introduce new tenant-level outbound email limits, known as the Tenant External Recipient Rate Limit or TERRL. The TERRL restricts the number of external recipients a tenant can send email to per day. If the limit is exceeded further messages sent to external recipients from the tenant will be blocked until the volume for the last 24 hours drops below the quota. A tenant’s TERRL quota is calculated based on the number of email licenses a tenant has purchased. Here is the formula used to calculate a tenant’s quota: 500 * (Purchased Email Licenses^0.7) + 9500 To help admins plan and track their outbound email volume, you’ll find a new report in the Exchange admin center: EAC > Reports > Mail flow > Tenant Outbound External Recipients Rate. This report shows the current volume of external recipients, your tenant’s daily quota, how much of the quota is used, and the number of recipients that were blocked if the limit was exceeded. The report will also show if enforcement for the limit is enabled or disabled. For example, for tenants who have more than 500 email licenses it will show “Disabled” until May 1st, the day we’ll start to enable enforcement for tenants who have more than 500 licenses. When this will happen: This change will roll out in progressive stages over the month of March as per the following rollout schedule: How this will affect your organization: If your tenant exceeds its daily outbound sending limit further messages sent to external recipients will be blocked and senders will receive one of the following bounce messages (also known as Non-Delivery Receipts or NDRs): Trial tenants: 550 5.7.232 - Your message can't be sent because your trial tenant has exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit) Non-trial tenants: 550 5.7.233 - Your message can't be sent because your tenant exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit) What you need to do to prepare: Check the report in the EAC to see your tenant’s quota and current daily outbound email volume and whether or not any messages will be blocked once the TERRL is enabled for your tenant. If your current outbound email volume is well below the quota, you don’t have to do anything. If your outbound email volume is near or exceeding your quota, consider using Azure Communication Services email for high-volume email to external recipients instead. ACS email which offers significant advantages and features for high-volume email, especially for external recipients. Messages sent using ACS email are not counted against your Tenant External Recipient Rate Limit quota. For more information about the Tenant External Recipient Rate feature and report please see this blog post: Introducing Exchange Online Tenant Outbound Email Limits MC676299 — (Updated) Retirement of Exchange Web Services in Exchange Online Updated April 18, 2025: We have updated the content. Thank you for your patience. In 2018, we announced that we were no longer making feature updates to Exchange Web Services (EWS) in Exchange Online, and we advised developers to move to Microsoft Graph. In September 2023, we announced that on October 1, 2026, we will start blocking EWS requests to Exchange Online. We are now less than 18 months from October 1, 2026. We have made progress on closing several parity gaps with more changes in development to be released in the coming quarters. Please refer to Deprecation of Exchange Web Services in Exchange Online for up-to-date guidance and roadmap information. If you haven't already, start the process of working with your application development organization and your application vendors to migrate active EWS applications on your tenant to the Graph API. When this will happen: October 1, 2026 How this affects your organization: While the EWS components of the service will continue to receive security updates and certain non-security updates, product design and features will remain unchanged. This change also applies to the EWS SDKs for Java and .NET, as well. Despite this announcement, EWS is still available and supported for use in production environments. But we strongly suggest migrating to Microsoft Graph to access Exchange Online data and gain access to the latest features and functionality. Today’s update and the retirement of EWS apply only to Microsoft 365 and Exchange Online (all environments); there are no changes to EWS in Exchange Server. Further, the changes in Exchange Online do not affect Outlook for Windows or Mac, Teams, or any other Microsoft product. In our original blog post, we said this change would affect only third-party (non-Microsoft) applications. We have expanded our effort and are now also removing EWS dependencies from Microsoft apps and services, and we’re going to complete that work well before October 2026. We intend to do this as quickly as possible without affecting the quality of service or product. There may be applications running on your tenant created by your organization or 3rd parties that use EWS. We recommend reviewing your application portfolio now to get an understanding of which apps need to be updated by your organization and which applications require updates from vendors. It is important to get started with this effort as soon as possible as the Graph API patterns are quite different from EWS. Equivalent Graph API operations may exhibit subtle differences that affect your use cases and application designs in unanticipated ways. Migrating Applications to Microsoft Graph We know there are several feature gaps between EWS and Microsoft Graph, and though the list below is not exhaustive, these are the gaps most frequently reported to us by developers: Access to Archive Mailboxes – We are working on delivering access to archive mailboxes via Microsoft Graph and will provide an updated timeline in the coming months. Folder Associated Information / User Configuration – We are working on these features and will provide an updated timeline in the coming months. Exchange Online Management – We are investigating solutions for this and will provide an updated timeline in the coming months. Access to Public Folders – After evaluating the usage of public folders, we have decided to restrict programmatic access to public folders to supported Outlook clients only, and for bulk import/export purposes. We will not provide APIs for programmatically creating, reading, updating and deleting public folders after October 2026 (also see Security Related Updates in Exchange Online). We know there are other gaps not listed above, and we continue to work on closing them, but it’s possible some functionality will not make it to Microsoft Graph. We encourage you to refer to Deprecation of Exchange Web Services in Exchange Online for up-to-date guidance and roadmap information. Next Steps The retirement of these APIs follows our Modern Lifecycle Policy. We understand changes like this may cause some inconvenience, but we are confident it will ensure more secure, reliable, and performant experiences. We will publish regular communications as we progress towards this deadline to aid affected tenants in identifying EWS usage. We encourage all customers to monitor Message Center and the Exchange Blog and Deprecation of Exchange Web Services in Exchange Online for related content. Thank you in advance for updating and opening your apps to a wider range of useful and intelligent features on Microsoft Graph. We are extremely excited about the growing opportunities that Microsoft Graph offers to developers, and we remain fully committed to our journey to empower developers to access Microsoft 365 data with the most modern features and tools. Microsoft 365 MC1060472 — (Updated) The new Microsoft Planner for the web (GCC High) Microsoft 365 Roadmap ID 490567 Updated April 23, 2025: We have added the roadmap information. Thank you for your patience. The new Microsoft Planner for the web brings together the simplicity of Microsoft To Do, the collaboration of Planner, and the power of Project for the web into a simple, scalable solution that spans individual task management to professional project management. With this rollout, we will update the existing web version of Planner to the new Planner. A Microsoft 365 license is required to use the new Planner. A Project Plan 3 license, Project Plan 5 license, or a premium Planner trial license is required to create premium plans. When this will happen: General Availability (GCC High): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025. How this will affect your organization: As part of our efforts to simplify Planner, these existing features are not available in the new Planner due to low usage: Charts for pinned plans in Planner Hub While you were awaynotifications Activity log of a task’s creation, assignments, and completion date in the task comments Links to group members, Microsoft Outlook conversations, and Microsoft OneNote notebook (you can still access these links in Outlook) Menu option to Leave plan Suggested attachments Charts view and Schedule view on the Assigned to me page Lastly, after the new Planner for the web is rolled out, users can still access Project for the web. For this rollout, we will merge notification settings in the new Planner and Project for the web. Users will see identical notification options in the two apps, and the settings they choose will be reflected across both apps. Until a user reviews their notification settings, we will maintain what the user had set before the notifications are merged. The new Planner for the web: What you need to do to prepare: The new Planner is on by default for users with the required licenses. 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. Please review our Planner blog announcementto update any internal documentation. We will update Planner help documentation in the coming weeks. Supporting adoption resources: The new Microsoft Planner. MC1060466 — Microsoft Excel: Python in Excel will be generally available in Excel for Mac (GCC) Microsoft 365 Roadmap ID 489216 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 Mac. MC980798 (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) (published January 2025, updated February 2025). When this will happen: General Availability (GCC): We will begin rolling out to Excel for Mac mid-May 2025 and expect to complete by late May 2025. 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 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. MC1058303 — Reminder: Support for the Word Mobile, Excel Mobile, and PowerPoint Mobile UWP applications will end on October 14, 2025 Reminder: Support for the mobile Universal Windows Platform (UWP) apps (Microsoft Word, Microsoft Excel and Microsoft PowerPoint) will end on October 14, 2025. After that date, no further updates, security fixes, or technical support will be available for these applications. We communicated this retirement in MC921113 Support for the Word Mobile, Excel Mobile, and PowerPoint Mobile UWP applications will end on October 14, 2025 (published October 2024) When this will happen: This retirement will occur on October 14, 2025. How this will affect your organization: If Microsoft Windows-based devices within your organization are running Word Mobile, Excel Mobile, or PowerPoint Mobile, we recommend that the applications be removed before the October 14, 2025, end of support date. While they may continue to function, using unsupported software could lead to potential security risks and other issues. If you’re using Microsoft Intune, you can run a report to identify devices running these applications. In the Microsoft Intune admin center, go to All services > Apps | Monitor > Discovered apps and search for "office.word", “office.excel”, or “office.powerpoint”. The application version will start with "16001.14326.xxxxx.x". What you need to do to prepare: To mitigate these risks and ensure your organization remains secure and compliant, we recommend removing these three UWP applications and switching to alternatives: Microsoft 365 Copilot mobile appfor iOS or Android phones and tablet devices Word, Excel, and PowerPoint on the web. Learn more. Windows desktop versions of Word, Excel, and PowerPoint in a Microsoft 365 plan. Compare Microsoft 365 Enterprise Plans. Learn more about the end of support for the OneNote UWP application (OneNote for Windows 10): Moving to OneNote on Windows - Microsoft Support. Planning ahead will help you avoid potential disruptions and keep your organization’s software environment secure and up to date. MC1056996 — (Updated) Microsoft Excel: Extending support for Insights Services (GCC High, DoD) Microsoft 365 Roadmap ID 488142 Updated April 28, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Excel: Support for the Analyze Data feature, which will be found on the Data tab This message applies to Excel for Windows desktop, Excel for Mac desktop, and Excel for the web. When this will happen: General Availability (GCC High, DoD): We will begin rolling out late April 2025 (previously early May) and expect to complete by late June 2025 (previously early June). How this will affect your organization: Analyze Data can generate charts and graphs that may provide insights and answer questions you may have about your data: 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 or after the rollout. You may want to notify your users about this change and update any relevant documentation. Learn more: Analyze Data in Excel - Microsoft Support MC1056260 — Support for Office 2016, Office 2019, and additional apps will end on October 14, 2025 As previously communicated, support for Office 2016 and Office 2019 will end on October 14, 2025. After that date, no further updates, security fixes, or technical support will be available for these versions of Office. While the applications may continue to function, using unsupported software could lead to potential security risks, compliance risks, system incompatibilities, and other issues. Support for Visio 2016 and 2019, Microsoft Project 2016 and 2019, and several other products will also end on October 14, 2025. Organizations using these products should upgrade as soon as possible to maintain security, compliance, and performance. When this will happen: Support for Office 2016, Office 2019, and additional apps will end on October 14, 2025. How this will affect your organization: After end of support, Office 2016 and Office 2019 suites, standalones, and servers will no longer receive security updates or other fixes, and no technical assistance will be available for devices still running them. Continuing to run unsupported software may expose your organization to security vulnerabilities and compliance risks, and may affect the reliability and performance of services. What you need to do to prepare: To mitigate these risks while maintaining access to desktop Office apps, we recommend upgrading devices to a Microsoft 365 or Office 365 suite that includes Microsoft 365 Apps (for enterprise or for business). Microsoft 365 Apps provides always-up-to-date versions of familiar apps like Word, Excel, and PowerPoint for desktop, mobile, and web with continuous support under the Modern Lifecycle Policy, and is eligible for use with the Microsoft 365 Copilot add-on. For scenarios that require a fully disconnected solution, we recommend upgrading to Office LTSC 2024. Office LTSC 2024 includes a subset of the value in Microsoft 365 Apps and will be supported until October 2029 under the Fixed Lifecycle Policy. Take steps to prepare for this transition with the following resources: Read the upgrade guidancefor an overview of how to move from Office 2016 or Office 2019 to Microsoft 365 Apps. Consider engaging Microsoft FastTrack, a Microsoft support service, for moving to Microsoft 365. Plan ahead to avoid potential disruptions and keep your organization’s software environment secure and up to date. MC1051092 — Microsoft 365 web app: Updated experience (DoD) Coming soon: An updated experience for the Microsoft 365 web app at https://www.ohome.apps.mil When this will happen: General Availability (DoD): We will begin rolling out late May 2025. How this will affect your organization: This rollout includes these key changes: Microsoft 365 apps that were pinned to the left navigation will be available in the Apps tab. Profile and Settings buttons will move from the top right to the bottom left corner. New content types and templates will be added to the Create tab. Search bar will move from the top header to the Home tab. Organization branding will be removed along with the top header. The upgraded Microsoft 365 web app home page: This change will be on by default. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. MC1051087 — Microsoft 365 web app: Updated experience (GCC High) Coming soon: An updated experience for the Microsoft 365 web app at https://www.office365.us When this will happen: General Availability (GCC High): We will begin rolling out late May 2025. How this will affect your organization: This rollout includes these key changes: Microsoft 365 apps that were pinned to the left navigation will be available in the Apps tab. Profile and Settings buttons will move from the top right to the bottom left corner. New content types and templates will be added to the Create tab. Search bar will move from the top header to the Home tab. Organization branding will be removed along with the top header. The upgraded Microsoft 365 web app home page: This change will be on by default. What you need to do to prepare: This rollout will happen automatically by the specified dates 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. MC1047236 — Cloud Policy Service available to GCC-H and DoD customers The Cloud policy service will begin rolling out for Microsoft 365 GCC-H and DoD customers early June 2025. The Cloud Policy service allows Microsoft 365 administrators to configure policies for Microsoft 365 apps and assign these policies using Microsoft 365 or Entra ID groups. When this will happen: General Availability (GCC High): We will begin rolling out on early June 2025 and expect to complete by early June 2025. General Availability (DoD): We will begin rolling out on early June 2025 and expect to complete by early June 2025. How this will affect your organization: Once configured, these policies are automatically enforced as users sign in and use Microsoft 365 apps and services. The initial release will support policies for Microsoft 365 Apps for enterprise on Windows and future updates will bring support for additional applications and platforms. What you need to do to prepare: Review online documentation and implement as appropriate for your organization. For additional information about the Cloud Policy service, refer to Overview of the Cloud Policy service for Microsoft 365 Apps for enterprise. MC1041965 — Microsoft Excel: Python in Excel will be generally available in Excel for the web (GCC) Microsoft 365 Roadmap ID 485764 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 the web. MC980798 (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) (published January 2025, updated February 2025). When this will happen: General Availability (GCC): We will begin rolling out to Excel for the web early May 2025 and expect to complete by mid-May 2025. 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 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. MC973511 — (Updated) Microsoft Purview | Data Lifecycle Management: Separate retention policies for Copilot and AI apps Microsoft 365 Roadmap ID 470025 Updated March 18, 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 March 2025 (previously late February) and expect to complete by early April 2025 (previously early March). 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. MC961557 — (Updated) Microsoft Search in Bing Deprecation Updated March 10, 2025: There are additional details available regarding the Microsoft Search in Bing retirement. Some Microsoft Search answers will no longer be available after March 31, 2025, including Q&As and location answers. Recommended bookmarks will also be retired; you can keep them by manually publishing or exporting them by April 30, 2025. Please see the FAQ for more information. Work or school search history on Bing.com will be available through March 31, 2025. Individuals who wish to keep their recent search history must download it by March 31 by signing in with their Entra ID, going to Options on Bing.com, and selecting “Search history.” There is no control available for IT admins to download search terms on behalf of users. To help users on Bing.com, a banner to redirect to M365.cloud.microsoft will be shown in Edge if search terms are high likelihood of being work-related. For more details, please see the FAQ available at Guidance for retiring Microsoft Search in Bing for your organization. Note: Microsoft Edge version 134.0.3124.51+ is required for the work search functionality described below. 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 Chat for more details. Documentation - Office 365 IP Address and URL web service April 30, 2025 - GCC April 30, 2025 - GCC High April 30, 2025 - DOD
Office 365 Public CDN really anonymous accessible?
Hi everyone, I'm a bit confused with the Public CDN option. For my understanding if you setup a public cdn all the files that are allowed (IncludeFileExtensions CSS,EOT,GIF,ICO,JPEG,JPG,JS,MAP,PNG,SVG,TTF,WOFF) are accessible anonymous. This is also what is documented under https://docs.microsoft.com/en-us/office365/enterprise/use-office-365-cdn-with-spo I have setup the public cdn for a custom library and uploaded a jpg file. I can see from developer tools the file is loaded via https://publiccdn.sharepointonline.com/<mytenant>/sites/SiteCollection/cdntest/myfile.jpg?width=1600 if I browse the url while I'm authenticated it opens the file. If I browse the file while I'm not authenticated it shows an access denied. My question is, are these files really accessible via Internet if I have the url? or what is definition of anonymous? kind regards
