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への挑戦はまだ終わらない。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.Using the Enterprise Website Microsoft 365 Copilot Connector
Microsoft 365 Copilot Search can be extended by ingesting information from external sources through a Microsoft 365 Copilot Connector. In this article, we show how to configure the Enterprise websites prebuilt connector to ingest articles from the Office365ITPros.com and Practical365.com sites, and how Copilot Search presents that information in its results and summaries. It’s quick, easy, and seamless – so really pretty good! https://office365itpros.com/2025/09/29/microsoft-365-copilot-connector/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/Agent not visible in M365 Copilot
I created an agent in M365, including its name, description, instructions, and required actions. The agent is properly tested in Copilot Studio and published, but it is not visible in the M365 Copilot agent list. Interestingly, one agent is visible while the other is not, and I am unable to determine the issue.
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
Copilot connection to Powerbi
Hi Everyone. Currently trying to make a connection to our PowerBi platform through Copilot Studios. So far i keep getting a connection failure. I have tried to adjust our security settings in Active Directory. I have tried adjusting the permission on the workspace and access to the datasheet. When i use the Json query to extract on the columns in the giving table i just get a connection error. even though the connection seems valid. Any suggestions on how to proceed?
Feature Request: API Access for Copilot to Support Knowledge Management Tools
I'd love to see Microsoft offer a public API endpoint for Copilot, especially one that's compatible with OpenAI-style integrations. This would unlock massive potential for developers and users working in tools like: Obsidian (local-first, markdown-based personal knowledge management) Logseq, Zettlr, and other note-based or PKM systems Custom research environments, digital gardens, and AI-enhanced workflows Currently, many plugins in this ecosystem support third-party models (OpenAI, Anthropic, Gemini), but Copilot is not accessible—despite the fact that Microsoft has positioned it as a cross-platform assistant with memory, reasoning, and contextual awareness. An API endpoint would allow: Seamless AI interactions within a user's vault or notes Context-sensitive summaries, tagging, and creative workflows Natural-language search across local files using Copilot’s memory and intelligence Voice or chat-based journaling that connects to structured PKM formats Microsoft already supports Copilot integrations in Office apps like Word and OneNote, but many users prefer markdown-based, privacy-respecting environments. Providing API-level access would allow broader use cases while respecting platform independence. Obsidian alone has millions of users and a thriving plugin ecosystem. A Copilot integration—even just one with simple API compatibility—could become a game-changer for anyone building personalized, long-term knowledge workflows. If this isn't the best place to post this please let me know :)
