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 Use of Anthropic AI Models Creates Concerns for Tenants
On September 24, Microsoft announced that Anthrophic LLMs could be used with the Copilot Researcher agent and to build agents with Copilot Studio. Although it’s great to enable choice so that customers can choose the AI model they prefer, questions about data security, lack of support for compliance solutions, and adherence to standards like the EU data boundary will concern Microsoft 365 tenants. https://office365itpros.com/2025/09/26/anthrophic-copilot/
How to add links to external docs in CoPilot Studio
Hi as a rank amateur, I am trying to develop a copilot agent that will display links to external reference documents that will contain more information than the co pilot knowledge answer. All the docs are held in various SharePoint sites. However I try to insert links in the knowledge documents, they will not display in the copilot agent. I have tried hyperlinks, raw urls, and trying to create a seperate heading for the references but nothing seems to make them appear in the agent answer. Can anyone help before I loose anymore hair from my fast receding hairline 😁😁
Windows-based Copilot Pro ONLY crashing on loading larger Conversation, other platforms work.
Hi everyone, I'm writing this post with a bit of frustration. I spent quite a few hours waiting and speaking with the Copilot Microsoft Support live, however; they were unable to help after doing the routine fixes like rebooting, re-installing, Repair, and some cache cleaning (they called it a Backend issue) - then they said that here I would find the solution... which I found a little strange, but here goes. I am working on a software project and have been for the past few months, so there has been a lot of activity in the particular Conversation on Copilot, and as of a couple days ago after uploading a screenshot, it froze and had to be restarted - and any time I would try to load that particular Conversation, it would freeze. Its just that one Conversation on a Windows 11 Copilot Pro setup, every other Conversation works on the Windows setup, and on my other devices like my phone, Copilot has no issues at all, even with the Conversation that won't load on the Windows setup. The difficulty for me is that I am somewhat limited to using the Windows Copilot for functionality, so my phone is out, and the Web-based version doesn't load Conversations. This is a pure Copilot Pro setup, not much to do with 365. Please help, thanks in advance.
Feature Suggestion: Personalized Product Alerts via Wishlist and Regional Availability Tracking
It’d be amazing if Copilot could notify users when specific products they care about become available—especially if it could tie in wishlist items and region-based tracking. Imagine being able to tag a graphics card or monitor you’ve had your eye on, and then Copilot lets you know the moment it’s up for order in your area. No more manually checking five different websites every morning. Just one smart alert when the product is available, with all the relevant specs and vendor links. This would save time, cut through the noise, and make Copilot way more proactive. It’s the kind of feature that fits perfectly with how people already use Copilot—so why not take it a step further? If Copilot’s goal is to be truly helpful and intuitive, adding personalized product alerts would be a strong move in the right direction.
Improving Copilot's Causal Reasoning and Command Throughput via Centralized Protocol Layer (EDCA)
Problem Statement Copilot's agentic behavior is confined to pre-defined workflows or embedded tools. Prompt variability leads to semantic drift across sessions. Causal reasoning is weak under user goal ambiguity (e.g., “X + Y + Z triggers unintended output B”). Developer-side cost for scaling model I/O is too high under the current chain-of-thought format. Proposed Architecture: EDCA Central Control Layer (Mediator Core) Acts as routing hub between expression → intention → execution path. Supports fallback chains, multi-path detection, and output anchoring. Protocol-based Expression Parsing User utterances are parsed through a control protocol rather than raw prompts. Enables modular injection of reasoning modules. Agent Proxy Submodules For scalable delegation in C-end scenarios (non-technical users). Acts under a value-aligned behavior sandbox. Results from Experimental Deployment Metric Before (Raw Prompt) After (EDCA Protocol) Throughput (req/min/core) ~120 ~170 Semantic Coherence (avg depth) Moderate Significantly Higher Resource Waste (multi-chain) ~23% conflict ~5% conflict Why This Matters for Copilot Scales beyond pre-defined tools Enhances user trust via stable expression paths Reduces cost via intention compression & fewer back-and-forth calls Enables structured delegation for both B-end and C-end deployment scenarios Call for Feedback This is not a product — this is a thinking protocol. We’d love to hear from Copilot devs, LLM architects, and interaction designers: Where is Copilot heading? How can control layers like EDCA join the ecosystem? Contact: email address removed for privacy reasons
