Request for Consistent Search Experience Regardless of Copilot License
Microsoft has long positioned Unified Search as a consistent experience for all users. With the introduction of Copilot, that vision now feels increasingly fragmented. I fully understand that non-Copilot licensed users should not receive Copilot-specific capabilities such as summaries, overviews, follow-up questioning, or FAQ generation. That differentiation makes sense. However, beyond those value-added features, the core search experience should remain consistent regardless of licensing. Today, that is not the case. Non-licensed users are presented with a completely different and noticeably older UI, while licensed users get the modern Copilot-driven experience. This creates two parallel search experiences within the same organisation, which directly contradicts the idea of unified search. From what we are seeing, the legacy experience appears to be receiving little to no future investment, while Microsoft is focusing almost entirely on Copilot. The result is a growing divide in both usability and capability across the user base. At a minimum, it would make sense for: The same core UI to be available to all users Copilot-licensed users to receive additional enhancements such as summaries and overviews layered on top Semantic search capabilities to be broadly available, not fully gated by licensing Beyond this, there are ongoing challenges with Copilot (Graph) Connectors, and continued uncertainty around the future of SharePoint Search. Despite numerous known issues, there is little visible clarity or direction, even when engaging directly with Microsoft. Copilot is clearly a major strategic investment, but it should not come at the expense of foundational experiences. There are still many core capabilities across Microsoft 365 that require attention, and from a customer perspective, the roadmap for addressing these gaps remains unclear. Microsoft has an opportunity here to reinforce trust by ensuring consistency, clarity, and continued investment in the broader platform, not just Copilot.
Do I need to have a Copilot license to use MCP servers through Frontier?
Do I need to have a Copilot license to use Microsoft-published MCP servers for Word / Teams / Outlook / SharePoint under Microsoft Agent 365 (Frontier)? https://learn.microsoft.com/en-us/microsoft-agent-365/tooling-servers-overviewError 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!Propuesta: Modo Profesional para proyectos largos en Microsoft 365 Copilot
PROPUESTA: MODO PROFESIONAL PARA PROYECTOS LARGOS EN MICROSOFT 365 COPILOT Por Matías Hola, soy Matías. Trabajo integrando la IA en proyectos narrativos, técnicos y organizativos de largo plazo. Copilot no es para mí solo un asistente: es una parte fundamental de mi proceso creativo diario. Lo utilizo para estructurar proyectos complejos, escribir documentación extensa, diseñar sistemas e ideas, organizar tareas y manejar múltiples líneas de trabajo continuas. Por eso necesito que Copilot sea estable, persistente y confiable. PROBLEMA REAL Cuando Copilot se usa más allá de consultas breves, aparecen dificultades que afectan directamente la continuidad: Las conversaciones no quedan asociadas a proyectos. El hilo se fragmenta entre dispositivos. Si la ventana se refresca, se pierde parte del contexto. El progreso puede quedar desfasado entre PC, móvil y navegador. No existe un espacio organizado con materiales, notas o memoria persistente. Para un profesional, esto no es un detalle técnico: es una interrupción real del flujo de trabajo. EJEMPLO CONCRETO Mi día laboral combina PC en casa, móvil en el trabajo y laptop en movimiento. Cuando Copilot no sincroniza exactamente los estados entre dispositivos, termino con conversaciones incompletas, respuestas que no reflejan el trabajo previo, necesidad de reexplicar contexto y pérdida de ritmo creativo. Perder ritmo es perder claridad, productividad e incluso decisiones importantes de un proyecto. POR QUÉ ESTO ES NECESARIO Copilot está evolucionando rapidamente. Cada vez más usuarios integramos la IA no como curiosidad, sino como parte del oleoducto productivo. Como cualquier software profesional (IDE, gestor de tareas, editor, etc), Copilot necesita estabilidad, memoria persistente, continuidad y sincronización perfecta. No es un lujo. Es una necesidad diaria. PROPUESTA: MODO PROFESIONAL Un entorno mejorado pensado para proyectos serios y extensos, basado en tres puntos: Persistencia de proyectos Espacios que integren conversaciones, documentos, notas, memoria por proyecto y contexto permanente. Sincronización total Continuidad idéntica entre PC, portátil, navegador y aplicación móvil. Estabilidad reforzada Evitar refrescos automáticos, proteger mensajes largos, prevenir pérdida de contexto y garantizar que el progreso no se fragmente. CIERRE Copilot tiene el potencial de conversión en una herramienta central para la creatividad, la productividad y la construcción de proyectos modernos. Para lograrlo, necesaria ofrecer un entorno estable y persistente, pensado para quienes crean y trabajadores todos los días con IA. Ningún buscamos reemplazar al humano. Buscamos un espacio donde humano e IA puedan convivir de manea fluida, profesional y continua. Gracias por leer. — MatíasFrom PC to Home Window: AI as Data Surgeon
Hello Copilot Community, I’d like to share a vision for the future of AI in Windows and beyond: evolving from a reactive assistant into a Data Surgeon — diagnosing, repairing, and reconstructing the lifeblood of modern life: data. 🩺 Diagnose Scan for corruption in files, registries, and hardware sectors Detect anomalies with machine learning and predict failures before they happen 🛠 Repair Auto-heal OS inconsistencies, registry errors, and driver mismatches Reconstruct corrupted files using backups, metadata, and contextual inference 🧬 Reconstruct Repopulate missing data from previous versions and cloud syncs Fill gaps in documents, databases, or media with AI-driven interpolation 🧑⚕️ Prescribe & Prevent Recommend preventive actions: backup schedules, hardware upgrades, cooling solutions Provide digital wellness reports — like a health checkup for your PC 🛤 Roadmap Toward the “Home Window” 2025–2027: AI-assisted diagnostics and repair tools 2027–2030: Household integration and predictive maintenance — the “Home Window Baby” stage 2030–2035: Cross-domain AI collaboration (social media, banking, utilities) 2035–2040: Fully fledged “Home Window” — essential for every modern home Discussion Prompt: How do you see Copilot evolving into this role? What technical milestones or safeguards would be essential? Could this align with Microsoft’s roadmap for Copilot in Windows and household AI?Copilot Connector for DevOps - Crawl Account = Search Admin?
Hi all, We’re about to set up Copilot Connectors for Azure DevOps (ADO) Wikis and Work Items across multiple organizations. During this process, we discovered that the account used to create the connector—requiring the Search Administrator role—is automatically designated as the crawl account. This crawl account must have read access across all projects within the ADO organization. Currently, we’re using our individual user accounts (with Search Administrator privileges) to create the connectors. However, we cannot use these accounts as crawl accounts due to access limitations. Ideally, the crawl account should be a service account with the necessary read permissions. The issue is that Microsoft’s configuration appears to require the same account to both create the connector and act as the crawl account. This would mean logging in with a service account that has Search Administrator rights, which is not a viable or secure option for us. Are we misunderstanding the setup? Is there a way to use our own accounts to create the connector and then specify a separate service account as the crawl account during configuration? We’re hoping someone can confirm that this separation is possible—and that we don’t need to grant Search Administrator privileges to a service account just to complete connector setup. Thanks - Grant.
Your interactive guide to setting up the web client via Direct Connect
Project Overview> I developed a way to use copilot studio agent using direct connect. This guide outlines how to configure a Microsoft Copilot Studio agent for secure web integration using Direct Connect, Azure Bot Services, and Power Platform. The web client uses a secure Express.js backend to handle credential exchange, ensuring the **Client Secret** is never exposed on the frontend. If anyone is interested, I can provide the source code. Prerequisites You must have administrative access to the following resources to complete the setup. 💻 Local Development Node.js (v12+) and Git installed. 🤖 Copilot Studio Agent Agent created and imported to the Production Environment. 🛡️ Azure Access Access to Azure Subscription 1 and Microsoft Entra ID for App Registration.Microsoft 365 Copilot Usage Report API General Availability
The Copilot usage report Graph API is now generally available. Like the report APIs for the other workloads, the Copilot usage API helps to understand usage of some very expensive licenses. Even better, the usage data can be combined with data from other Microsoft 365 sources to produce interesting and valuable insights. All it takes is some PowerShell to knit everything together. https://office365itpros.com/2025/10/10/copilot-usage-report-api-ga/Part 7: Copilot Pages × Teams — One Screen, No More Switching
Switching apps kills meetings. Silence. Dead air. Mistakes. The cure? One screen. Copilot Pages × Teams = Zero switching. Prepare, run, wrap — all in Pages. “Open once, close with confidence.” In Part 6, I proposed a “Feedback Dashboard” to connect users and Microsoft in continuous improvement. Now in Part 7, let’s face the toughest meeting problem: constant app switching. On the other side of the screen, nobody sees what’s happening — only waiting and broken focus. The solution is simple: don’t switch at all. Copilot Pages becomes the single cockpit for meetings: 1.Before — prepare everything in one Page. 2.During — dynamic sidebar and Teams control box. 3.After — results sync back automatically. Benefits • No more “Where’s the file?” moments. • No more dead air while someone fumbles with apps. • Teams and Pages finally feel like one seamless cockpit. In short: “Open Pages, run the meeting, close with confidence. No more switching.” Part One ends here — but my challenge to Microsoft is far from over. 第7弾：Copilot Pages × Teams ― アプリ切替ゼロの会議体験 会議を止めるのは、アプリ切替。 沈黙、待ち時間、ミス。 解決はシンプル。画面はひとつ。 Copilot Pages × Teams = 切替ゼロ。 準備も進行も振り返りも、Pagesで完結。 「沈黙ゼロ、切替ゼロ。Pagesを開けば、会議は止まらない。」 第6弾では「Feedback Dashboard」を提案し、ユーザーとMicrosoftが共に改善できる仕組みを描きました。 そして第7弾は、会議で最も深刻な問題に切り込みます。 アプリの切替による混乱とミス です。 参加者には見えない沈黙と待ち時間。 操作ミスが重なり、会議の流れが止まる。 解決策はただひとつ。切替をやめること。 Copilot Pagesを会議の“司令塔”にする： 会議前 ― 議題や資料をPagesに集約して準備。 会議中 ― 動的サイドバー（第3弾）と「Teams操作BOX」で進行を制御。 会議後 ― 成果は自動でTeamsチャネルに戻る。 効果 • 「ファイルどこ？」が消える。 • アプリ切替の沈黙がなくなる。 • TeamsとPagesが完全に融合し、ひとつの司令塔になる。 一言で言えば： 「沈黙ゼロ、切替ゼロ。Pagesを開けば、会議は止まらない。」 第1部はここで一区切り。 でも、Microsoftへの挑戦はまだ終わらない。
