Copilot OneDrive and Teams Integration useless for PDFs of scanned documents
Hi, I have this ubiquitous Copilot button everywhere in OneDrive, Teams, SharePoint, you name it. But Everytime I use the suggested „Summarise this file“ button of a PDF document that contains scanned pages Copilot complains that the images are very low resolution and nothing meaningful can be extracted. But when I let Copilot analyse the exact same file in the pure Copilot view everything works fine. After some lengthy conversations with Copilot it admits, that it only access the complete file when the Copilot view is used. In all other views using Copilot only works on the preview images that are created of the file when uploaded. That explains why the images to analyse are of a too low resolution to do OCR and why on some files only the first page gets processed. Why is Copilot integrated in that way? I expect Copilot to always work on the original file for any request I do. Especially when Copilot is promoted everywhere and I’m constantly nagged to get a summary or FAQ of a selected file. The way it currently works would be better removed or -better- just redirect with the selected file into Copilot view. CheersCopilot and DLP policy behaviours
Hi Copilot Brain Trust, Looking for some real-world experiences with Microsoft 365 Copilot DLP enforcement. We've implemented a DLP policy targeting the Microsoft 365 Copilot location with the action to prevent Copilot from processing content that contains our sensitivity label (restricted). The implementation is based on the following Microsoft documentation: DLP for Microsoft 365 Copilot: https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot-location-learn-about Create DLP policies for Microsoft 365 Copilot: https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot Microsoft documentation states that when a DLP policy blocks Copilot processing, protected content should not be processed or used in Copilot-generated responses (although citations may still appear). However, during testing we're observing scenarios where Copilot appears to access/process provide restricted snippet with file names from content that should be protected by the DLP policy. A few questions for anyone who has implemented this in production: Have you successfully validated DLP policies preventing Copilot from summarising sensitivity-labelled content? Are there any known delays between policy deployment and enforcement? Have you observed differences between Copilot Chat and Copilot experiences within Word, Excel, or PowerPoint? Are there any prerequisites, limitations, or known issues not currently reflected in the public documentation? I'm interested to hear whether others have seen similar behaviour or have successfully validated this scenario end-to-end. Thanks in advance.
Feature Proposal: OS-level Intelligent Task Organizer (Windows + Copilot)
A Idea about Intelligent Tasks organizer, I have to remember a lot of things during the team meetings like what is been said (we'll schedule a call or follow up etc.,) and what has been communicated in the emails (I'll get back to you after 2 weeks, or call us after two weeks) , And notes that I took in the notepad, or notepad ++,or sticky notes, or word, or one note. I want to chronologically display tasks on the right hand side of the laptop screen just like sticky note and it shall display all tasks one by one, it shall remove tasks are already complete (email sent with confirmation). and arrange, adjust every few mins according to priority/time or user added priority. App shall display small icon (just like chat) upon clicking it shall display ordered list of tasks. and desktop apps like teams/note/word/notepad++,sticky notes can participate by default or other apps like notepad++ can be onboarded manually in to the app. You can use a local model which infers the meaning of “I’ll call you in two weeks” - who is “I”? you or them? “Let’s follow up later” - task or casual statement? “I sent it” - which task did this complete? You can use a local model such that Corporate Teams/Outlook access may allow by corporate policy. Need to put much emphasis on false positives if the app keeps inventing tasks. Do not need to bring big LLMs in to the picture for inference, because of corporate policies may not allow. Microsoft provides operating system,office 365, tools with copilot, the inference can be possible because of all apps/content can be accessible at os level. Problem: Users capture tasks across multiple tools: Teams meetings and chats Outlook emails Notes (OneNote, Notepad, Sticky Notes, Word) Tasks become fragmented, untracked, and often lost. Proposed Solution: A lightweight system-level task layer integrated with Windows + Copilot that: Core Features Automatic task extraction From Teams, Outlook, notes, and user text Example interpretations: “I’ll call you in 2 weeks” “Let’s follow up later” Context-aware inference (local model) Identify: Task owner (“I” vs “you”) Priority signals Deadlines Minimize false positives Chronological task timeline Tasks auto-organized by: Time Priority Recency Floating task panel (desktop UI) Docked widget (like Sticky Notes or chat bubble) Expand/collapse view Always visible option Automatic task lifecycle tracking Detect completion: “Email sent” “File shared” Remove or mark complete automatically Continuous re-prioritization Adjust every few minutes based on: New inputs Deadlines User behavior Privacy-first architecture Use local models (SLM) instead of large cloud LLMs Enterprise admin control for data access Why this matters: Millions of users manually track tasks across fragmented tools, losing productivity daily. This feature would unify task understanding across the OS and M365 ecosystem.
Copilot in Edge needs direct export integration
While using Copilot in Microsoft Edge, I noticed a key limitation: there is no option to directly save or export text snippets or summaries to OneDrive, Word, or OneNote. Users must copy manually, which breaks the reading flow and reduces productivity. Competitor comparison: Claude → PDF export, integration with Notion and Drive ChatGPT → PDF/DOCX export, integration with Google Drive Gemini → Automatic export, integration with Google Drive Copilot (Edge) → Only copy/paste or browser PDF, no native integrationCopilot automation assumes OneDrive—hidden productivity cost in Google‑first environments
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } We’re a Google‑first organization with a limited Microsoft 365 tenant. After recent Copilot updates, automation suggestions appear everywhere and feel “easy,” but nearly all meaningful automation requires files to live in OneDrive or SharePoint. In a hybrid environment, this creates hidden costs: duplicate file management, copying between systems, increased version/corruption risk, and hours of admin work just to discover limitations mid‑workflow. Copilot looks capable, but the storage and identity prerequisites aren’t explicit up front, so users lose time and trust. Are there plans to better support hybrid scenarios (for example, Google Drive as a system of record), or to provide clearer in‑product guidance before suggesting OneDrive‑only automations?
Proposal for a Unified Copilot Architecture and Tiered AI Assistant Model
Submitted by: Craig D. Evans Detroit, Michigan Executive Summary This proposal outlines a strategic redesign of Microsoft Copilot that transforms it from a collection of isolated chat instances into a unified, persistent, account based artificial intelligence assistant. The proposed architecture positions Copilot as the central intelligence that operates all Microsoft Office applications, maintains long term memory, and follows the user across all devices. This model introduces a tiered pricing structure that creates a scalable revenue engine while strengthening Microsoft’s long term dominance in productivity software. The proposal also introduces the concept of a dual AI verification system, in which Copilot performs tasks and a secondary model provides independent review. This structure increases reliability, reduces errors, and enhances user trust. Problem Statement The current Copilot experience is fragmented. Each application instance behaves as a separate assistant with limited continuity, limited memory, and limited cross application intelligence. Users must repeatedly re explain context, re establish preferences, and manually coordinate tasks across Word, Excel, PowerPoint, Outlook, and other Microsoft 365 applications. This fragmentation reduces efficiency, increases cognitive load, and prevents Copilot from functioning as a true personal assistant. It also limits Microsoft’s ability to monetize Copilot at scale, because the product does not yet offer a unified, persistent experience that users would be willing to subscribe to at higher tiers. Vision The vision is a single, persistent Copilot identity that the user logs into, similar to any modern online service. This identity follows the user across all devices and applications, retaining memory, preferences, formatting rules, workflows, and ongoing projects. In this model, Copilot becomes the central intelligence that operates the Microsoft Office ecosystem. Office applications become the tools, and Copilot becomes the operator. This transformation elevates Copilot from a chatbot to a long term digital assistant that remains with the user for decades. Functional Overview 1. Persistent Copilot Identity A single Copilot account that retains: Long term memory User preferences Formatting rules Writing style Project context Cross application workflows Templates and document structures This identity behaves like any other modern login system, such as Amazon, Walmart, or email services. 2. Copilot as the Central Intelligence of Office Copilot should be capable of: Opening and managing Word documents Applying templates and formatting Building PowerPoint presentations Managing Excel formulas and data structures Organizing files and directories Coordinating tasks across applications Executing workflows on behalf of the user Office becomes the body. Copilot becomes the brain. 3. Cross Device Continuity The user logs into Copilot once, and the assistant follows the user across: Desktop Laptop Mobile Web Cloud environments This creates a seamless, continuous experience. Tiered Pricing Model A tiered structure creates a scalable revenue engine and aligns with Microsoft’s existing subscription model. Tier 1: Free Copilot Basic chat No memory No continuity Limited functionality This tier serves as the entry point that encourages users to upgrade. Tier 2: Copilot with Memory and Formatting Persistent memory Document formatting intelligence Writing style retention Basic cross application awareness This tier provides immediate value and will attract a large user base. Tier 3: Cross Device Copilot Identity Full continuity across devices Unified assistant experience Project level intelligence Long term context retention This tier becomes the premium personal assistant model. Tier 4: Copilot as Full Office Manager Complete control of Word, Excel, PowerPoint, Outlook Workflow automation File management Multi application coordination Enterprise grade productivity This tier becomes the flagship offering for professionals and businesses. Optional Tier: Dual AI Verification (Copilot + Reviewer Model) Copilot performs tasks. A secondary model independently reviews output for: Accuracy Formatting Logic Consistency This reduces errors and increases trust. It becomes a high value premium tier. Competitive Advantage This architecture provides Microsoft with several strategic advantages: A unified assistant that no competitor currently offers A multi tier revenue structure that scales with user needs A long term relationship between user and assistant Increased adoption of Microsoft 365 subscriptions Strong differentiation from competing AI products Reduced user churn due to persistent memory and continuity This model positions Microsoft as the leader in personal and professional AI assistance. Long Term Strategic Value A persistent Copilot identity ensures that users remain within the Microsoft ecosystem for decades. As the assistant accumulates memory, preferences, and workflows, the cost of switching to another platform becomes extremely high. This creates: Long term subscription stability Increased enterprise adoption Stronger user loyalty A durable competitive moat Copilot becomes not only a feature, but a lifelong digital partner. Closing Statement I respectfully submit this proposal as a long time user who believes that Microsoft has the opportunity to define the future of personal and professional artificial intelligence. A unified Copilot identity, combined with a tiered pricing model and a dual AI verification system, will create a powerful, scalable, and enduring platform that strengthens Microsoft’s leadership in productivity software. Submitted by: Craig D. Evans Detroit, MichiganCopilot missing in Word, Excel and PowerPoint desktop apps of some users
Hi Everyone, At my company we're setting up copilot. After allowing access through the Admin Centers we've encountered various oddities. Some users can use the sharepoint/onedrive search functionality. But most can't. Some users have the Copilot button in some of their apps. There is no consistency in which app they get it. Some have it in word, others in excel, some in multiple, some in none. A handful of users have Copilot in all apps. Things like transcribe work fine everywhere. We switched intune to push Office apps with Current Channel instead of Semi-Annual, to no avail. We use M365 Business premium with the Teams phone standard addon.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 の世界を、学び人の視点から描いた教育物語です。 技術的な面も考慮しつつ、筆者はユーザーの「理解」を最も重視して執筆しています。あらかじめご了承ください。
