Making CoPilot Work for our Organisation
We're currently exploring how Microsoft Copilot can be used to support our bid writing process, and I’d really appreciate some insights or examples from others who’ve tried anything similar or just have a good understanding of CoPilot. What We’re Trying to Do We’d like Copilot to help us write and draft bid responses by referencing information already stored across our SharePoint libraries — including past bids, case studies, and company information — and then generate new content in our tone, structure, and style. In essence, we want Copilot to act like an “internal bid writer” that knows our history and can draw on it intelligently when producing answers. What We’re Trying to Understand I’m trying to get clarity on a few key things: What does GPT-5.0 actually bring to Copilot — is it just better reasoning and writing, or does it enable deeper integration with our Microsoft 365 data? What do we need to do (technically or in terms of setup) to let Copilot “see” our environment — e.g., access our SharePoint libraries and use that content effectively? I've saw some things around Microsoft Graph being enabled. What’s the practical difference between using Copilot and using ChatGPT for this type of work? We’ve also tried getting Copilot to fill in Excel sheets using data from SharePoint, but it doesn’t seem to behave as we expected. Is this something Copilot can’t currently do, or are we just approaching it the wrong way? What We’d Love to Learn What are the best practices for helping Copilot understand and use your SharePoint content effectively? Has anyone successfully used Copilot for bids, PQQs, tenders, or document generation? Any examples or use cases you can share of how you’ve made Copilot genuinely useful in a business context would be hugely appreciated. Thanks in advance — it’d be great to hear how others are making the most of Copilot in real-world scenarios.Copilot Connector with Windows, Google Drive
Copilot in Windows now allow connections with Google Drive, Google Calendar and Google Contacts. It also allows connection with personal accounts of Outlook and OneDrive. You can now get insights and prompt Copilot based on these connections. You can test it out and give feedback to Microsoft to further improve Copilot's connection with third-party applications. You can learn more here - https://blogs.windows.com/windows-insider/2025/10/09/copilot-on-windows-connectors-and-document-creation/
Prologue — Microsoft Planet (Episode 0)
Welcome to a world not of code, but of connection. Here begins the story of the “Microsoft Planet.” A world where four great nations and countless app kingdoms coexist, connected by invisible roads and bridges of information. The Four Great Nations — Foundations of the Planet Upon the vast continent of SharePoint, four great nations stand as the backbone of this world: ・SharePoint Federation ・OneDrive Kingdom ・Z-Cloud Empire ・Outlook Union Each serves as a place of preservation, guarding the memories and history of the planet. The App Kingdoms — The Front Stage Excel, PowerPoint, Teams, Word... Each nation holds its own culture and purpose, sometimes competing, sometimes supporting one another, together shaping the rhythm of the Microsoft Planet. Its citizens grow, learn, and occasionally misunderstand one another — many of these missteps arise simply because they have yet to truly understand how the world works. Roads and Bridges — The Network of Flow The nations are linked by countless roads and bridges. Through these paths, information flows freely, connections emerge, and the planet begins to move as one. The Traveler and the Fairy And within this world walks a traveler — a seeker of understanding, journeying through the Microsoft Planet. Beside them floats a small, imperfect yet reliable companion: the Copilot Fairy. When the traveler asks a question, the fairy lights the path and quietly guides them forward. Thus begins the journey — a story of understanding that moves the heart of the Microsoft world itself. Author’s Note In this story, the primary “storage realms” are represented as SharePoint, OneDrive, Z-Cloud, and Outlook, in alignment with how users actually perceive them. Technically, these all exist atop SharePoint, but the narrative prioritizes the user’s perspective for clarity. Stories of the individual app kingdoms (Excel, Teams, etc.) will later appear as side tales within the same world. ※ This story is an educational narrative written from the perspective of a learner, depicting the world of Microsoft as seen by momotarou. While technical aspects are considered, the author prioritizes user understanding above all else. 0話 ― Microsoft星 序幕 ここは「Microsoft星」。 四つの大国と、数多のアプリ国が息づき、 道や橋で結ばれた、不思議な星である。 四つの大国 ― 星の基盤 この星を支えるのは、広大なSharePoint大陸の上に築かれた四つの大国。 ・SharePoint連合国 ・OneDrive王国 ・Zクラウド大帝国 ・Outlook連邦 それぞれが「保存先」として、星の記憶と歴史を守っている。 アプリ国 ― 表舞台 Excel国、PowerPoint国、Teams共和国、Word国――。 それぞれが独自の文化と役割を持ち、 時に競い、時に支え合いながら、Microsoft星の営みを形づくっている。 国々の住民たちは、成長を重ねながらも、時にすれ違う。 すれ違いの多くは、この星の仕組みを十分に理解できていないことから生まれていた。 道や橋 ― 交通網 国々を結ぶのは道や橋。 情報が流れ、連携が生まれ、星全体がひとつに動き出す。 旅人と妖精 この物語には、一人の旅人がいる。 Microsoft星を巡りながら、まだ見ぬ真実を探す冒険者。 その傍らには、完璧ではないが頼れる伴走者―― 小さな妖精コパイロットがいる。 旅人が問いを投げれば、道を照らし、静かに導いてくれる。 こうして物語は始まる。 星の仕組みをめぐる“理解の旅”が、いま静かに、しかし確かに動き出した。 解説 この物語では、主要な保存先をユーザーの感覚に沿って、 SharePoint、OneDrive、Zクラウド、Outlookとして描いています。 本来、これらはすべてSharePoint上に存在しますが、 物語の中ではユーザー目線を優先にして表現しています。 なお、各アプリ（Excel、Teamsなど）の物語は、後日、外伝として描きたいと考えています。 ※ この物語は、@momotarou が見た Microsoft の世界を、学び人の視点から描いた教育物語です。 技術的な面も考慮しつつ、筆者はユーザーの「理解」を最も重視して執筆しています。あらかじめご了承ください。
Markdown-Dateien (.md) in Copilot for OneDrive / Graph Data Connect
Hi everyone, I’m currently exploring the use of Microsoft 365 Copilot with OneDrive as a personal and team knowledge base. However, I noticed that Markdown (.md) files are not being indexed or recognized by Copilot — even when OneDrive access is granted and the files are fully visible in Microsoft Search. Markdown is widely used for technical and structured documentation (for example, meeting notes, system specs, and transcriptions), and many of us store these files directly in OneDrive or SharePoint. It would be extremely useful if Copilot could read and summarize Markdown files just like it does with Word, PDF, or plain-text files. My questions are: Is there currently any way to make Copilot index Markdown files, perhaps via Microsoft Graph or the Admin Center (for example, MIME-type mapping or content connectors)? If not, is support for Markdown planned for Copilot in OneDrive or Graph Data Connect? Context: I maintain an internal knowledge base of project documentation and transcripts in Markdown stored in OneDrive. I’d like to use Copilot to query, summarize, and cross-reference this content directly, without having to convert the files to .docx or .pdf. Any insights, workarounds, or roadmap hints would be greatly appreciated. Thank you in advance for your help and for all the great work you’re doing to make Copilot more versatile. Best regards, Nick Suggested tags: Copilot, OneDrive, Microsoft 365, Graph Data Connect, Markdown
Copilot on Android
When attempting to open a password protected xlsm file through Copilot on my Android phone the file is disabled. When I open the file through the Onedrive app it opens properly in Copilot. The file is stored in Onedrive, not in the vault. Is it because the file is an xlsm file or because it is password protected?Creating Work Instructions/Process from a video with Copilot
I'm looking to document a process in the most efficient way possible. Has anyone been able to use Copilot to interpret a video from Teams or a screen recording and have it create accurate work instructions? Would like to save time and avoid manually typing work instructions by potentially using Copilot to speed up this process. Any tutorials would be much appreciated.
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.
Copilot Agent - assigning permissions to apps like Outlook and OneDrive
I'm trying to create an agent to do the following: - Automate the process of creating an email addressed to XXX - Attach the most recent file from OneDrive without renaming the file. - Prompt the user for a subject line before sending the email. - Only send the email after the subject line is provided by the user. - Launch the agent when the user enters the prompt 'XXX" - Ensure the attachment is not renamed during the process Copilot will create the agent, but does not send the email. Copilot tells me that the agent may not have access to Outlook to send the email. How do I assign permissions to a Copilot agent? All my searching over the last two hours has left me with no solution. Any assistance is appreciated. Thank you!
4 hrs 30 min on Copilot 365, 5 min on ChatGPT
I spent 4 hours and 30 minutes on Copil 365 to have it organize files and folders, sort documents, and convert them to PDF. It could not write the script. ChatGPT completed the task in under 5 minutes. Goodbye copilot365 & copilot. You were amazing-NOT! P.S. On top of that, it crashed at least twice.Part 00: Beyond Team Pride — Copilot Pages as the True Entry Point
In Part 0, I shared my personal motivation from an education experience. Building on that, here I want to highlight another reason — the fragmentation of Microsoft 365. The Problem The boundaries between apps are too strong, so to users they appear as completely separate worlds. The Challenge If this siloed culture continues, even new features will not solve the root issue — they will only add more complexity. My Proposal (Parts 1–3) That’s why I made my proposals in Part 1–3: Part 1: Simplify Copilot fragmentation Part 2: Vertical navigation to prevent getting lost Part 3: Dynamic sidebar for meetings Feasibility This is not an impossible idea. With Graph API and Fluent UI, plus existing side panels (e.g., Teams), unified lists, switching, and a meeting sidebar can all be implemented. It’s mainly integration and UX alignment, which makes it low-cost and high-impact. My Ask So please, prioritize user experience over team pride. If Copilot Pages becomes the true all-in-one entry point, Microsoft’s technology will shine even brighter — and users will finally say: “This is exactly what we’ve been waiting for.” 👉 Next: Part 4, “Thoughts Under a Cloudy Sky”, to explore the future vision. 00弾：メンツよりユーザー体験を ― Copilot Pagesを入口に 0弾では、自分の教育体験からの“きっかけ”を書きました。 その延長線上で、もう一つの理由――Microsoft 365の分断問題について整理します。 Microsoftの問題点 アプリごとの境界が強すぎて、ユーザーからは“別々の世界”に見えてしまう。 Microsoftの課題 この「縦割り文化」が続けば、新機能を出しても根本的な解決にはならず、かえって複雑さを増すだけです。 私の提案（第1〜3弾） だからこそ私は、第1弾〜第3弾の提案を出しました。 第1弾：Copilot乱立の整理 第2弾：縦スクロールUIで迷子防止 第3弾：会議UXの進化（動的サイドバー） 提案実現の可能性 これは実現不可能な話ではありません。 Graph API と Fluent UI、そして既存のサイドパネル（例：Teams）を組み合わせれば、統一リスト／切替や会議サイドバーは実装できます。 要は 統合とUX整理 であり、低コスト・高効果です。 最後にお願い どうか、メンツよりユーザー体験を最優先にしてください。 Copilot Pagesが本当のオールインワン入口になれば、Microsoftの技術はさらに輝き、ユーザーはこう言うでしょう。 「これこそ、私たちが求めていたものだ」と。 👉 次は第4弾、「曇り空に想うこと」 で、さらに未来像を描きます。
