Plan with confidence using the newly refreshed Microsoft 365 roadmap
We know many of you rely on the Microsoft 365 public roadmap as a trusted planning tool. Based on feedback from customers across roles, we’ve refreshed the top of the experience to make it easier to stay informed at a glance. Everything beneath the surface remains fully intact. Your filters, detailed views, and the roadmap API are unchanged, and nothing has been removed. New at the top are curated highlights summarizing: Announcements – a quick visual of the latest product announcements Available Now – top features that are now generally available and ready for your teams to use Coming Soon – top features in development that you can track and stay ahead of Frontier program – experimental features you can try and share feedback on Explore the refreshed roadmap at aka.ms/m365roadmap and stay up to date on the latest Microsoft 365 updates–from core apps to Copilot and agents.Accelerating Microsoft 365 Copilot Adoption with Automated Readiness Assessment
From Weeks of Manual Evaluation to Minutes of API-Driven Analysis Note: This playbook is designed for Microsoft partners operating within the AI Business Solutions commercial solution area to support their customers with the adoption journey of Microsoft365 Copilot.Employees can bring Copilot from their personal Microsoft 365 plans to work - what it means for IT
Today, we made some exciting announcements for Microsoft 365 Personal, Family and the new Premium plans. Among them is how employees can use Copilot from these plans on their work documents with Enterprise Data Protection, even if they don’t have a M365 Copilot license from your organization.Copilot Chat + Outlook: Email Summary Behavior
Sharing my discoveries. Copilot Chat is available to Microsoft 365 work or school accounts. Using Summarize this email in Outlook saves each summary as a Copilot Chat conversation, which can clutter Chat History. There’s no bulk delete; chats must be removed one at a time. This is expected behavior. Using Temporary Chat for one-time summaries helps keep Chat History clean. Impacted users: Outlook + Copilot Chat (no add-on license required) 📹 Video walkthrough and 📝 blog post . If you find this information helpful, please mark it as the best solution to assist others. #traccreations4e-p25 1/28/2026Upcoming January 2026 Microsoft 365 Champion Community Call
Join our next community call on January 27, 2026, to dive into Copilot Pages! Reminder: Our community calls are in the Teams webinar format, which means you must register to ensure you will be able to join the call when it starts. The registration links for both sessions are below. Once you register, you will receive an email confirmation and calendar invite with the webinar join link. https://aka.ms/M365ChampionCallAM https://aka.ms/M365ChampionCallPM The calls will still start at 5 minutes past the hour for both sessions (at 8:05 AM and 5:05 PM PT), and it will still end at the top of the hour (9:00 AM and 6:00 PM PT, respectively). While our calls are open to everyone, you must be a member of the Microsoft 365 Champion Program in order to access the presentation materials - the access link is in the initial welcome email and the monthly newsletter emails sent the week before the community calls. An on-demand recording will still be available on our Driving Adoption > Events pages, as well as on our Microsoft Community Learning YouTube channel. If you have not yet joined our Champion community, sign up here to get access to the monthly newsletters, calendar invites, and program assets (e.g., the presentations).Upcoming M365 Copilot Government Roadshow Dates
Get ready to dive into a new wave of hands‑on M365 Copilot and agentic AI experiences designed to help your organization build real skills and accelerate adoption. We're rolling out immersive workshops across multiple cities, each packed with practical exercises, expert guidance, and actionable takeaways. Explore the upcoming events and find the perfect session to jump‑start your next stage of AI transformation.Error Exporting Solution - Copilot Studio Agent with Confluence MCP “search” Tool
Hi all, I'm running into an issue when trying to export a solution that contains an agent built in Copilot Studio using the Confluence MCP “search” tool (Rovo search). I’m hoping someone can help clarify whether additional steps are required, or if this is a product limitation/bug. Scenario I’m building an agent that uses the Confluence MCP connector, specifically the Rovo “search” tool, combined with agent instructions to filter a specific Confluence space. Everything works fine in my developer environment, and now I’m preparing to move the solution to QA. However, I'm blocked at the export step. Steps I Followed Created the agent Added and configured Confluence MCP Selected only the “search” tool Set up agent instructions Created a new solution Added the agent to the solution Exported the solution Received the following error: Solution "xxxxxx" failed to export: Exporting connection reference <masked_connection_reference_id> for a custom connector requires the custom connector to be added to a Dataverse solution. Please add connector <masked_connector_id> to a solution and retry. What I Already Checked When I added the agent to the solution, only the Connection References were added automatically — no Custom Connectors were included. So, I manually added the Confluence MCP Custom Connector to the solution. Despite doing so, the export still fails with the same error. Additional Observations If I create a similar agent that uses only the searchConfluenceUsingCql tool (not the Rovo “search” tool), the solution exports without issues and I can successfully import it into QA. This makes me suspect that the problem is specific to the Rovo “search” capability in the MCP. Question Has anyone encountered this before? Do different steps need to be followed when an agent uses the Rovo “search” tool in the Confluence MCP? Or could it be a known issue? Any guidance or workarounds would be greatly appreciated. Thank youuu!
Copilot Agent ALM and Knowledge Source Management Across Environments
Hello everyone, I currently have an agent in a Dev environment and want to deploy it to a second environment (e.g., Test or Prod). During deployment, we need to change the references to the knowledge sources. I’ve seen some articles where environment variables are used within Conversational Boosting topics to handle this, but I wanted to check if there is a supported or recommended way to manage or update knowledge source references from the Knowledge section itself to make them dynamic by using Environment variable? Any guidance or best practices would help. Thankyou.General availability of source specific filters in Copilot Search
We’re excited to share that source specific filters are now generally available worldwide in Copilot Search 🎉. This release addresses a long‑standing challenge in enterprise search: helping users move seamlessly from broad discovery to precise, actionable results… without friction.
