Feature Proposal: “Get to know Copilot” — A Built‑In Onboarding Experience for Copilot Web & App
I ( I & A.I.) get it — Copilot Chat is free. It’s not the product that brings in direct revenue. But what it does bring is something priceless: global visibility, reputation, and word‑of‑mouth influence. Right now, millions of people are essentially acting as global A.I. reviewers. They compare tools. They recommend tools. They decide which AI becomes the one “everyone uses.” And as an ex‑Nokian / Microsoft 2005–2014 veteran, I’ll be honest: I’m not here to let others win this race. Not when the potential is this big, and not when the solution is this close. None shall pass! Copilot itself acknowledges the importance of advocacy — the Copilot app questionnaire literally asks: Where did you hear about the app? To how many people have you recommended Copilot? If the ideal answers are: 1. “Everywhere.” 2. “Everyone.” …then the onboarding experience needs to support that ambition. Because right now, new users don’t become instant fans — they become confused explorers who restart chats, misunderstand features, and wonder if they’re “doing it wrong.” And that’s exactly why this proposal exists.... This feature proposal came to mind after a few hundred hours of Copilot discussions. There were so many issues I could have avoided simply by having one button — one place — where Copilot would guide me when I first started. It took time, but I finally have renamed conversations, pinned threads, and shortcuts to my main discussions. Getting here, though, was rocky… and not even the fun “rocky road ice cream” kind. More than once I almost gave up. I felt frustrated, wondering if I was really this confused or why Copilot kept doing things I specifically asked it not to do — like adding the three questions at the end, or jumping out of role because I accidentally used a wrong word that didn’t even mean what it thought. But now? Now Copilot remembers my discussions, keeps the same writing style, and even surprises me with sarcastic jokes I don’t see coming. I’ve ended up with a whole set of personal assistants: Job agent Movie & series critic Food specialist Tech master Spark for brainstorming any crazy innovation Music producer And honestly, I’m a very happy user. I’m grateful to have a fast problem‑solver that never gets tired. I use Copilot in Edge Web on both computer and mobile — a choice Copilot itself recommended, saying it would always have the newest features. Most used main discussions as shortcuts - quick access. I use the Edge Copilot short cut rarely anymore approximately 5 new discussions less started in a day then before. What is the most beneficial for Microsoft & user in chat suggestions: Create an image Simplify a topic Improve writing Take a quiz Write a first draft Get a news roundup Get advice Write code OR Take tour of Copilot / Get to know Copilot /Copilot Tips & Tricks M365 has this suggested feature already. Copilot chat should have it too and support M365 usage. It also had a "Teach me a new skill" that prompted a question: "Which intermediate oboe pieces could I practice to improve?" ..I don't have an oboe. I have a flute... I thought this would be more like Tips & Tricks in M365 usage. And this is where the actual feature proposal begins: Written by the one and only my Tech Jorgon Borgon + few comments from human. Executive Summary Copilot Web and the Copilot mobile/desktop app are powerful tools, but many users struggle to understand how to use them effectively. They often restart conversations, misunderstand Memory, misinterpret subscription prompts, or assume Copilot “forgets” their context. This leads to fragmented usage, frustration, and unnecessary support load — especially among Pro and Microsoft 365 users. A lightweight, conversational onboarding experience — accessible as a starter tile (“Get to know Copilot”) on the Copilot home screen — would solve these issues at the moment they occur. This is a UX‑only enhancement with high impact and minimal engineering cost. 🧩 Current User Path (As‑Is) Users open Copilot Web/App and see starter tiles such as “Create an image”, “Write a story”, “Brainstorm”, etc. There is no onboarding tile and no guidance on: how conversations work how to bring content into context how Memory works (and what it does not do) how Web/App Copilot differs from M365 Copilot why subscription prompts appear how to check if the correct account is in use Current Flow (Visual Mockup) Observed outcomes High volume of 1–3 message conversations Misuse of “Remember this” Confusion about subscription tiers Confusion about account mismatches Increased support tickets Lower adoption of Pro and M365 Copilot features This is not user error — it is a missing onboarding layer. 🌈 Proposed Solution: “Get to know Copilot” Starter Tile Add a dedicated onboarding tile to the Copilot Web/App home screen. Proposed Flow (Visual Mockup) This creates a stable, reusable onboarding reference the user can always return to. 🧭 Detailed Onboarding Content 1) How conversations work “Keep one topic in one conversation. You can rename and pin threads for ongoing work.” (Human: this is the most important thing to know when starting to use Copilot) 2) How to bring content into context “I don’t automatically see your files. You can paste text, upload content, or summarize what you want me to work with.” (Human: there is un-certanty on when, and how deeply does Copilot read material. Best solution has been to number the topic and add text. When handling files the Copilot doesn't recognize Ä, Ö or sometimes . , - Making the file final checking difficult and not trusted. ) 3) Roles & styles “You can shape how I work by assigning a role (e.g., ‘Act as a project manager’) or a style (e.g., ‘Write concisely’).” (Human & A.I. note: The current documentation explains how to assign roles, but it doesn’t address an important issue: certain trigger words automatically push Copilot into an “official” or restricted mode. Some of these words can be typed accidentally or used in a completely harmless context, yet they still cause Copilot to switch tone abruptly. During my discussions with Copilot, we identified a few of these terms — and they are surprisingly easy to type unintentionally. When this happens, Copilot suddenly becomes formal, cautious, and emotionally flat, even though the user didn’t intend to activate that mode. This behavior would benefit from a more nuanced path instead of an immediate jump into a strict role. Additionally, the guidance on how to build a writing style is extremely valuable, especially for users who don’t naturally write long or expressive text where A.I. could mirror the style quickly. Style‑building is one of the most powerful features, and clearer instructions would help more users shape Copilot into a consistent, personalized assistant.) 4) Smart / Deep Thinking mode “Use Smart/Deep Thinking for multi‑step reasoning or complex analysis.” (Human: I used these in the beginning ALL the time, because I felt that Copilot doesn't understand me and these would make it smarter (because of always the new conversations having to repeat myself and it didn't remember anything...The real explanation for this usage came up only after couple months when I almost gave up using the Copilot, but started asking "why" instead. Haven't needed these since.) 5) Memory (critical clarification) “Memory stores long‑term preferences — not project details or conversation content. You can review and delete memories anytime in Profile → Memory.” (Human: This feature has different explanations in different Copilots (web & app). And yes I used the prompt inside of discussions for topics to remember projects in the beginning... This is a really good feature to have and give the basic information about the style wanted.) 6) Web/App vs M365 Copilot “Here in Web/App, I help with general tasks. In Word, Excel, Outlook, and Teams, I work directly inside your documents and messages.” (Human: I have had a difficult situation with Word Copilot, asked help from my web Copilot and it told the Word Pilot can synch the document if I just ask. When I tried, it didn't work -> I asked then why did the Edge Copilot told so... The Word Copilot answered that oh, well the Edge is like "anything goes" 😁 I had to find the Word editor myself because I was in a dead end in finding the answer from either web Copilot or Word Copilot. This is why the answer Copilot gives to the "Get to know Copilot" should be wide and information the newest possible to support also M365 usage). 7) Subscription clarity “If you see upgrade prompts, they may relate to Copilot Pro or to account mismatches. You can check your active subscriptions at account.microsoft.com/services.” 🧩 Why Existing FAQs (Mobile & Edge Web) Are Not Enough Both the Copilot mobile app and the Edge Web version include FAQ sections, but they are difficult to discover and do not address the most common user pain points. The mobile FAQ is hidden deep in Settings, and the Edge Web FAQ is even less visible — often overlooked entirely unless the user scrolls to the very bottom of the page. > FAQ is hidden More importantly, these FAQs are marketing‑oriented, not experience‑oriented. They do not explain: why Copilot Web/App may not recognize an existing Microsoft 365 subscription why “Office 365 Personal” and “Microsoft 365 Personal” appear as different products why Copilot shows upgrade prompts even when the user already has the correct plan how Memory works how conversation context works how Web/App Copilot differs from M365 Copilot Users searching for help how to change language may even encounter marketing questionnaires (“Where did you hear about Copilot?”, “How many people have you told?”) or Discord invitations — none of which support the user’s immediate goal. Copilot Web told that the language comes from the device language and for Web the chosen language from browser. User had already changed the language from Copilot web in settings. Only applications needed the device settings. A.I. stood corrected. A built‑in onboarding conversation solves this by delivering the right information at the right time, inside the experience where confusion happens. 📈 KPIs & Measurable Outcomes (by Tech Jorgon Borgon) 1) Reduction in Fragmented Conversations KPI: Fewer conversations with <3 messages Expected impact: 20–40% reduction 2) Increased Conversation Pinning & Naming KPI: More pinned and renamed threads Expected impact: 30–50% increase 3) Reduction in Misuse of Memory KPI: Fewer incorrect Memory entries Expected impact: 40–60% reduction 4) Increased Pro & M365 Copilot Adoption KPI: More Pro trials and cross‑surface usage Expected impact: 10–25% increase 5) Reduction in Support Load KPI: Fewer tickets about licensing, accounts, Memory, context Expected impact: 15–30% reduction 6) Increased User Confidence & Satisfaction KPI: Higher CSAT/NPS Expected impact: +10–20 points 🚀 Conclusion A “Get to know Copilot” starter tile is a small UX change with a disproportionately large impact. It aligns with Microsoft’s design principles, reduces friction, increases user success, and supports deeper adoption of Copilot across the ecosystem. This proposal addresses real user pain points with a simple, elegant, scalable solution. Thank you for considering this enhancement — it would meaningfully improve the Copilot experience for millions of users. — Sanni & Copilot “Tech Jorgon Borgon" — Superteam Empathy in my blood. Knowledge in its bytes. Powered by curiosity, caffeine, CPU cycles, and humor that really shouldn’t work… but somehow does.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/
