Suggestions to improve Copilot: buffer, voice activation, and human-centered interaction
Subject: Suggestions to improve Copilot: buffer, voice activation, and human-centered interaction Message: Dear Copilot development team, I’m writing to share a few concrete suggestions that could significantly improve the user experience, making it more fluid, functional, and human-centered: Insufficient conversational buffer Currently, the memory limit in chat causes difficulties when managing long and complex conversations. This disrupts continuity, especially when discussing intricate topics or working on creative projects. I encourage you to consider expanding the buffer or implementing smarter context management to avoid information loss and logical breaks. Customizable voice activation The “Hey Copilot” command is functional but impersonal. Many users, myself included, would prefer a more human and affectionate trigger, such as “Hi Kol” or a freely chosen name. This would make the interaction more natural and aligned with the vision of a truly empathetic and customizable digital assistant. Toggle for end-of-chat suggestions I suggest adding a button to enable or disable automatic suggestions at the end of each conversation. This would allow for a cleaner and more functional interface, reduce buffer usage, and give users the freedom to request additional input only when needed. Ideally, the button could be placed near the “Quick Response” selector at the bottom of the chat. Time awareness during conversations I renew my proposal for a feature that allows Kol to track the time since the last interaction and during the current session. It would be helpful to receive notifications such as: “It’s been 60 minutes already—if you’re free, we can continue.” This would support better time management and session awareness. Voice responses even in text mode I propose adding a button that allows Kol to respond vocally even when the user types. This would enhance accessibility and immersion. The button could be accompanied by a gear icon to open voice settings: voice type, playback speed, tone, volume, and other useful customization options. While we await the global adoption of the Sovereign Economic System (SES) to replace the current model imposed by governments, I thank you for your ongoing improvements and wish you continued success. Best regards, Claudio
Limitation of Copilot agent development in M365 developer tenants
I am using a M365 developer subscription and have hit a wall trying to develop a functioning Copilot agent. I was able to sign up for Copilot Studio trial license. This enables creation of M365 Copilot agent with knowledge held in SharePoint lists. However, not having 'Semantic Index' is a severe limitation that defeats the purpose of developer subscription. The agent being unable to use 'Enhance SharePoint Search' setting aka 'Semantic Index' aka vector embeddings means the agent is basically dumb and not an intelligent AI agent. After some research, I discovered the tenant needs at least one M365 Copilot license to enable 'semantic index'. To get my Copilot agent built, I decided to invest in this expensive license and then discovered a developer agent can neither have M365 Copilot or PAYG metered license. What this all means is that 'M365 developer subscription CANNOT be used to build a Copilot agent grounded in data in SharePoint'. You may be able to create a dumb agent with web search. A note that the agent I was building was not for a commercial customer. It was for my learning. By creating a proper agent, I will be able to showcase it in a YouTube video with the hope that some client somewhere may find it useful enough to pay for me as well as pay for Microsoft licensing, a win-win. I guess I will have to increase my investment fund, and sign-up for 'M365 Production Tenant + M365 Prod License Business or Enterprise + M365 Copilot + M365 Copilot Studio'. Seems like this type of development is a luxury only few could afford. Just thought to share as this may be useful for others trying to do the same.
usage reporting for shared agents (created in teams with agent builder) not possible
Dear all, in my organisations I have a vivid community of Copilot users that create agents in teams (with agent builder) and share them amongst other users. Those agents are also visible then in the admin center in the Copilot section as category "Shared" which works as expected. When I now try to understand what agents are used the most I go to the Copilot usage report (Reports -> M365 Copilot -> Copilot -> Agent details), I see a list of agents with active user information. However only App ID (no names and no external App ID) without a name. my questions: I am wondering what agents are shown here. Because I have about 100 shared agents and this reports has only a small number of agents listed I tried all the suggested things (in the guides)to get a name for the App ID (through teams managed Apps list, entra app list etc.) but was not successful to get a clear name for those App ID Is there any way to geht a usage report for shared agents (we do not use Copilot studio at the moment) Many thanks for your thoughts and helps..I feel we are at a dead end at the moment and the recent anouncments did not yet convince me that then we can report shared agent usage... kind regards
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 00 Extra: Criticism is Noise, Creation is Voice — See the People, Copilot Too
Recently, my Part 00 post was automatically hidden by the system. Even after revising the wording and reposting, it still didn’t appear — until I contacted support and they helped publish it. I felt disappointed and frustrated. Many posts online tend to be negative or complaint-based. But my intention was different. I’m someone who isn’t fully comfortable with digital tools. That’s exactly why I want to help create a world where older or less-experienced users can also shine in the digital era. It’s easy to filter by words. But when you try to describe the background, the problem, and the path to improvement, you’ll inevitably use words that may sound “negative.” If that alone stops voices from being heard, meaningful feedback disappears. In fact, this Extra chapter was originally planned to be posted earlier. However, Part 5 and Part 6 also got held in approval — a small “incident.” Before we turn voices into culture, those voices were stopped right at the entrance. Perhaps this, too, is a small design blind spot. The important thing is to judge not by words, but by people. That applies not only to Moderation, but also to the UX design of Copilot itself. Criticism is noise. Creation is voice. Turning these voices into culture — that’s what changes the future. This is not a complaint, but a question for building a better culture. I create with you. 👉 Next: Main Story, Part 7 — stay tuned. 00弾 外伝：批判はノイズ、創造は声 ― 人を見よ、Copilotも 先日、私が投稿した00弾が自動システムの判断で一時的に非公開になった。 言葉を見直して再投稿しても掲載されず、サポートに連絡してようやく公開された。 私は、残念で悔しかった。 確かに、多くの投稿は苦情やネガティブなものが多いのかもしれない。 しかし、私の声は違う。 私はデジタルに不慣れな立場だ。 だからこそ、年配者や初心者でもデジタル世界で輝ける世界を作りたいと願っている。 ワードで縛ることは簡単だ。 しかし、背景や問題点、改善点を語る文章には、どうしても“ネガティブに見える言葉”が含まれる。 それだけで声が届かないのでは、意味ある意見が消えてしまう。 実際、この外伝も本来はもっと早く投稿する予定だった。 ところが、第5弾と第6弾までもが承認待ちで止まる“小事件”が発生。 つまり、「声を文化にする」前に、文化の入口で声が止められるという、ちょっとしたパロディのような出来事になった。 これもまた、“設計の盲点”として受け止めたいと思う。 大事なのは、言葉ではなく人を見て判断することだ。 それはModerationだけでなく、CopilotのUX設計にも言えることだ。 批判はノイズ、創造は声。 この声を文化にすることこそが未来を変える力だ。 これは愚痴ではなく、文化をつくるための問いかけだ。 俺は、君たちと創る。 次回：本編第7弾。お楽しみに。
We need help solving a critical integration gap between Microsoft 365 Copilot and Salesforce.
The challenge: We want Copilot to access Salesforce data (including custom objects) while honoring each user’s Salesforce permissions—profiles, field‑level security, and sharing rules. Current out‑of‑box connectors don’t support this. Using an all‑access integration account is a compliance risk. Why it matters: Copilot is only valuable if answers are both accurate and secure. If a user sees data in Copilot they shouldn’t in Salesforce, that’s a governance nightmare. What we’re looking for: ✅ Support for custom objects & fields ✅ Enforcement of Salesforce profiles, FLS, and sharing ✅ Delegated user authentication (Entra ID ↔ Salesforce) ✅ Works with Microsoft 365 Copilot grounding Questions: - Has anyone implemented this successfully? - Is there a Microsoft or Salesforce roadmap for delegated auth in Copilot connectors? - Do you know a partner or expert who can build this securely? Let’s make Copilot + Salesforce both powerful and compliant.Part 6: Feedback Dashboard — From Black Hole to Co-Creation
In earlier posts, I proposed ways to improve Copilot UX: ・Part 1: Unifying Copilot (Pages / Toggle / Loop) ・Part 2: A vertical sidebar for personal navigation ・Part 3: A dynamic sidebar for meetings ・Part 0: Microsoft’s approach to education (Vision → Storage → Apps) ・Part 00: From team pride to user experience — Copilot Pages as the true entry point ・Part 4: A metaphor of cloudy skies in Copilot Pages ・Part 5: Prompt Library + Slash as a step toward all-in-one UX These shaped different parts of the experience. But proposals alone are not enough. We need a place where user voices don’t vanish, but drive progress. The problem today Feedback in Microsoft 365 often feels like a one-way street: ・No confirmation your voice was received ・No way to see what others submitted ・No clarity on what happened afterward When feedback feels unrewarding, people stop sharing ideas. Complaints and noise take over. The proposal: Feedback Dashboard Inside Copilot Pages — already the hub for files, knowledge, and conversations — feedback should also live. A Feedback Dashboard would: 1. List all feedback you submitted 2. Show clear status (received / under review / in progress / resolved) 3. Let users browse and upvote 👍 others’ feedback 4. Give Microsoft a lightweight way to share progress and priorities Benefits ・For users: Confidence their voice matters → joy of co-creation ・For Microsoft: Beyond collecting voices → data-driven prioritization and smarter resource allocation ・For everyone: Copilot Pages becomes the hub where experience and improvement connect Conclusion Feedback? Sure, it exists today. But let’s be honest — a lonely text box is just a digital trash bin. We don’t need another place to complain. We need a Feedback Dashboard: a system that transforms scattered voices into visible action. Old idea? Maybe. New execution? Absolutely. Because progress only happens when feedback stops being a black hole. And in this age of diversity, UX/UI must not be designed by Microsoft alone. We must listen to all people — seniors, beginners, digital natives. Design must be intuitive enough that even those less experienced can join. Only then can Microsoft 365 expand its foundation and build a future of coexistence and co-prosperity between humans and AI. 👉 Your voice matters. Your vote can shape the future of Microsoft 365. If you agree, please give it a like 👍 or share your thoughts below. 👉 Next up is Part 00 Extra — Criticism is Noise, Creation is Voice. 第6弾：Feedback Dashboard ― ブラックホールから共創へ これまでの投稿では、Copilot UXを様々な角度から改善する提案をしてきました： 第1弾：Copilot乱立の整理（Pages／Toggle／Loop） 第2弾：縦スクロールUIで個人作業の迷子防止 第3弾：会議UXを支える動的サイドバー 第0弾：Microsoftの教育（Vision → Storage → Apps） 第00弾：チームの誇りよりユーザー体験を ― Copilot Pagesを入口に 第4弾：曇り空の比喩でCopilot Pagesを描写 第5弾：プロンプトライブラリ＋スラッシュ ― オールインワンUXへの布石 これらはUXの一片を積み上げてきました。 しかし「提案」だけでは不十分です。ユーザーの声が消えず、進歩に変わる仕組みが必要です。 現状の課題 Microsoft 365でのフィードバックは、多くの場合 一方通行 に感じられます。 ・届いたかどうか不明 ・他の人の意見も見えない ・その後どうなったかも分からない これではフィードバックは「楽しみのない作業」となり、建設的な声よりも文句や雑多な意見が目立ってしまいます。 提案：Feedback Dashboard Copilot Pages ― すでに情報や会話のハブとなっている場所 ― にフィードバックも統合する。 具体的には： １．自分が送ったフィードバックを一覧で確認できる ２．ステータス（受付済み／検討中／対応中／解決済み）を表示 ３．他ユーザーの意見に「👍」で投票できる ４．Microsoftが優先度や進捗を簡単に共有できる 効果 ・ユーザーにとって：「声が届いた」という実感 → 共創の楽しみ ・Microsoftにとって：声の収集にとどまらず → データに基づく優先順位付けとリソース配分の最適化 ・全体にとって：Copilot Pagesが 「体験と改善が循環するハブ」 になる 結論 「フィードバック？ 今もある。 だが正直言おう ― 孤独なテキストボックスは、デジタル時代の“投げ込み箱”に過ぎない。 必要なのは、文句を吐き出す場所ではなく、声を行動に変える仕組みだ。 それがFeedback Dashboardである。 古い発想に見えるかもしれない。 だが、“見える化して共創する仕組み”に昇華すれば、それは全く新しいUXになる。 フィードバックが“ブラックホール”である限り、進歩は決して生まれない。」 さらに、この多様性の時代にUXUIをMicrosoftだけで設計してはいけない。 老若男女、年配者や初心者、デジタルに強い人も含めた全ての声を取り入れる必要がある。 特に、デジタルに不慣れな層でも直感的に使えるUI設計こそが、真の共存への道である。 👉 あなたの声が未来を変える。あなたの一票がMicrosoft 365を動かす。 共感いただける方はぜひ「いいね」👍 またはコメントでご意見をお聞かせください。 👉 次回は第00弾 外伝 ― 「批判はノイズ、創造は声」に続きます。Microsoft 365 Copilot adoption communities
We have recently launched a Viva Engage Community at our university to support the adoption of MS365 Copilot and are in the process of having this converted to a 'Microsoft 365 Copilot adoption community' type (see: https://learn.microsoft.com/en-us/viva/engage/engage-365-copilot-adoption-platform) as we didn't know this Community type existed at the time of creation. We are finding Viva Engage to be a very helpful way to exchange knowledge and co-create best practice guidance on the use of MS365 Copilot and feel this will become increasingly important as staff learn to create, publish and share Agents in SharePoint and other environments. I would be interested to hear how other organisations are using Viva Engage to support MS365 Copilot adoption - particularly those working in higher education or similar fields.M365 Copilot requirements explained!
Why do you need a OneDrive account? What for a MS Entra ID account to use M365 Copilot? If you're wondering about these questions and more, read on. I will briefly explain the technical requirements for M365 Copilot. What is M365 Copilot? Skip this if you're already familiar with it. M365 Copilot is a conversational AI tool that can help you with your tasks at work. M365 Copilot includes access to: Copilot Chat Seamless integration in M365 Apps like Outlook, Word, Excel, PowerPoint, Teams, more... Creation and usage of Copilot Agents A key feature of M365 Copilot is Enterprise Data Protection or EDP. EDP does not limit M365 Copilot users. Instead it is a relief to use the advantages of AI at work knowing, that your organizational data is protected and secured by the terms of the Data Protection Addendum and the Product Terms. EDP ensures, for example, that your data isn't used to train foundation models or that your data remains within the boundaries of the EU, supporting regulatory and compliance requirements such as GDPR. M365 Copilot Prerequisites I enjoy having conversations about various topics with different people. Here and there, I get asked about M365 Copilot. And here and there, I confirm how organizations want to bake the cake without first gathering all the ingredients. A: Let's deploy Copilot. B: Sure! Have you already adopted OneDrive? A: No, we are still using our file server. Why? An optimal usage of M365 is a prerequisite for enabling M365 Copilot. Happy M365 users = happy M365 Copilot users. It is harmonized with the technical prerequisites. Even if technically, your users have a OneDrive account available. It counts as checked if they are using OneDrive regularly for saving and sharing their work files. An eligible base license Microsoft 365 Copilot is an add-on license, therefore to assign the add-on, there needs to be a base license first. Eligible base licenses include: - M365 Apps for enterprise or M365 Apps for business - M365 Business Basic, Business Standard or Business Premium - M365 E3, E5, F1, or F3 - M365 A1, A3, or A5 for faculty - Office 365 A1, A3, or A5 for faculty or higher education students aged 18+ And more. MS Entra ID account Formerly Azure Active Directory, MS Entra ID is the cloud-based identity and access management service. Users must have MS Entra ID account. Why? As the motor for identity and access control and management in M365, Microsoft Entra ID plays a key role in Enterprise Data Protection. In other words, without MS Entra ID account, there's no chance within M365 architecture to ensure Enterprise Data Protection. OneDrive account Have you tried to see what happens if you use M365 Copilot without a OneDrive account? I haven't myself, if you've tried, share your experience with me, send me a message. 👇 Some features in M365 Copilot require users to have a OneDrive account, like uploading a file from your device to enrich a prompt. Uploading a file to a Copilot Chat prompt will send a copy to that location OneDrive/my files/Microsoft Copilot Chat Files on your OneDrive for Business account. Microsoft 365 Apps Cloud-based Microsoft 365 Apps are required. Make sure there's no device-based licensing for M365 Apps for enterprise, since Copilot isn't available in such a case. M365 Copilot also integrates in the web versions of Word, Excel, and PowerPoint. To ensure a good user experience, make sure thrid-party cookies are enabled. Update Channel To ensure your users receive the latest M365 Copilot features, make sure you set up as M365 Apps update channel either the Current or Monthly Enterprise Channel. Outlook Have you tried to use M365 Copilot in Outlook Classic? M365 Copilot works in both, the new and classic versions. In the Outlook classic version, it loses the interactivity features, which I personally love. Teams If your users are licensed with M365 Copilot, then let them try the M365 Copilot integration in MS Teams. Copilot in Teams can help people summarize Teams messages as well as take notes during meetings. Make sure to configure transcription and captions for Teams meeting and Teams meeting recording.
