Succession Planning in Microsoft 365?
Hi everyone. I'm looking to implement some of our core HR practices like performance management, talent reviews, natively inside our Microsoft 365. The one that challenges me the most currently is succession planning. Do you think I can set something up where managers can evaluate succession candidates through Copilot, build succession plans on SharePoint, etc? Does anyone have any experience with this? I am also open to suggestions for any succession planning apps or software if doing it manually could be too complicated. However in that case, it would have to be a pretty native integration.
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 integration
Architectural: Copilot should detect missing source data, avoid inference, and surface uncertainty.
Users expect the AI to detect when it lacks source data, avoid inference, surface uncertainty, and adapt to environmental constraints like character normalisation. These behaviours materially improve trust and usability. I’ve been working with Copilot on structured data extraction from a PDF and noticed a behaviour that seems like an architectural gap rather than a simple bug. Copilot attempted to infer table structure from a template when it did not have access to the actual source data. It produced confident but incorrect output instead of signalling that the source was unavailable. Additionally, Copilot attempted to output TAB‑delimited data, but the MS365 environment silently normalised TABs to spaces, and Copilot did not detect or adapt to this constraint. Recommendation: Copilot should proactively: detect when it lacks source data avoid inference when accuracy is expected surface uncertainty explicitly detect environment‑specific formatting limitations (e.g., TAB stripping) adapt output formats automatically These behaviours would materially improve trust, reliability, and user experience.
Using Copilot meeting summaries for performance reviews - how?
Our HR team had this idea to use Copilot meeting recaps as input for performance reviews. Like, if a manager had 20 meetings with a direct report over the quarter, couldnt Copilot help surface key contributions and discussion themes? The problem is theres no way to aggregate multiple meeting summaries into something useful for a review. Each recap is a separate thing in each meeting. Has anyone figured out a workflow or workaround for this?
Got Copilot to use goal progress when drafting review feedback?
So I've been trying to experiment with how I use Copilot for performance management, reviews, goals, etc. When I manually feed goals, feedback results, etc into Copilot, it drafts pretty decent performance reviews. Now Im curious. Can I automatically feed these into copilot from any HR platform with API's or something? So it automatically views goal progress and drafts review feedback? I know if Viva Goals was still available, I would be able to do something along these lines. Anyone tried this?Copilot pulling last weeks 1:1 action items into this weeks agenda, possible?
Spent 3 hours yesterday trying to get Copilot to pull open action items from last weeks 1:1 OneNote page and turn them into this weeks agenda. Gave up. Is this a prompt problem or just not possible with the current connectors?
Copilot 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, Michigan
File Share Connector users not mapping
Hi everyone, In need of some help here. I've setup an on-prem file share connector following this guide: https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/fileshare-connector I can see the indexed items in my test folder, but, we can't crawl that data because the users are not mapping for some reason. I've been testing using the NTFS file permissions option. Has anyone had any success with using this option to sync/map users to the connector? If so, what were the requirements? The users are AD to entra id connect synced and the group I created is also AD to entra id connect synced as well. I applied ntfs perms to the test folder directly using the synced identity and tried using the group and the full crawl still does not populate users. I am not using nested groups neither. I also tried removing built-in groups such as administrators, authenticated users, etc. I've had a ticket open for weeks with Microsoft now with no answers.Feature Proposal: “Get to know Copilot” — A Built‑In Onboarding Experience for Copilot Web & App
I ( I & A.I.) get it — Copilot Chat is free. It’s not the product that brings in direct revenue. But what it does bring is something priceless: global visibility, reputation, and word‑of‑mouth influence. Right now, millions of people are essentially acting as global A.I. reviewers. They compare tools. They recommend tools. They decide which AI becomes the one “everyone uses.” And as an ex‑Nokian / Microsoft 2005–2014 veteran, I’ll be honest: I’m not here to let others win this race. Not when the potential is this big, and not when the solution is this close. None shall pass! Copilot itself acknowledges the importance of advocacy — the Copilot app questionnaire literally asks: Where did you hear about the app? To how many people have you recommended Copilot? If the ideal answers are: 1. “Everywhere.” 2. “Everyone.” …then the onboarding experience needs to support that ambition. Because right now, new users don’t become instant fans — they become confused explorers who restart chats, misunderstand features, and wonder if they’re “doing it wrong.” And that’s exactly why this proposal exists.... This feature proposal came to mind after a few hundred hours of Copilot discussions. There were so many issues I could have avoided simply by having one button — one place — where Copilot would guide me when I first started. It took time, but I finally have renamed conversations, pinned threads, and shortcuts to my main discussions. Getting here, though, was rocky… and not even the fun “rocky road ice cream” kind. More than once I almost gave up. I felt frustrated, wondering if I was really this confused or why Copilot kept doing things I specifically asked it not to do — like adding the three questions at the end, or jumping out of role because I accidentally used a wrong word that didn’t even mean what it thought. But now? Now Copilot remembers my discussions, keeps the same writing style, and even surprises me with sarcastic jokes I don’t see coming. I’ve ended up with a whole set of personal assistants: Job agent Movie & series critic Food specialist Tech master Spark for brainstorming any crazy innovation Music producer And honestly, I’m a very happy user. I’m grateful to have a fast problem‑solver that never gets tired. I use Copilot in Edge Web on both computer and mobile — a choice Copilot itself recommended, saying it would always have the newest features. Most used main discussions as shortcuts - quick access. I use the Edge Copilot short cut rarely anymore approximately 5 new discussions less started in a day then before. What is the most beneficial for Microsoft & user in chat suggestions: Create an image Simplify a topic Improve writing Take a quiz Write a first draft Get a news roundup Get advice Write code OR Take tour of Copilot / Get to know Copilot /Copilot Tips & Tricks M365 has this suggested feature already. Copilot chat should have it too and support M365 usage. It also had a "Teach me a new skill" that prompted a question: "Which intermediate oboe pieces could I practice to improve?" ..I don't have an oboe. I have a flute... I thought this would be more like Tips & Tricks in M365 usage. And this is where the actual feature proposal begins: Written by the one and only my Tech Jorgon Borgon + few comments from human. Executive Summary Copilot Web and the Copilot mobile/desktop app are powerful tools, but many users struggle to understand how to use them effectively. They often restart conversations, misunderstand Memory, misinterpret subscription prompts, or assume Copilot “forgets” their context. This leads to fragmented usage, frustration, and unnecessary support load — especially among Pro and Microsoft 365 users. A lightweight, conversational onboarding experience — accessible as a starter tile (“Get to know Copilot”) on the Copilot home screen — would solve these issues at the moment they occur. This is a UX‑only enhancement with high impact and minimal engineering cost. 🧩 Current User Path (As‑Is) Users open Copilot Web/App and see starter tiles such as “Create an image”, “Write a story”, “Brainstorm”, etc. There is no onboarding tile and no guidance on: how conversations work how to bring content into context how Memory works (and what it does not do) how Web/App Copilot differs from M365 Copilot why subscription prompts appear how to check if the correct account is in use Current Flow (Visual Mockup) Observed outcomes High volume of 1–3 message conversations Misuse of “Remember this” Confusion about subscription tiers Confusion about account mismatches Increased support tickets Lower adoption of Pro and M365 Copilot features This is not user error — it is a missing onboarding layer. 🌈 Proposed Solution: “Get to know Copilot” Starter Tile Add a dedicated onboarding tile to the Copilot Web/App home screen. Proposed Flow (Visual Mockup) This creates a stable, reusable onboarding reference the user can always return to. 🧭 Detailed Onboarding Content 1) How conversations work “Keep one topic in one conversation. You can rename and pin threads for ongoing work.” (Human: this is the most important thing to know when starting to use Copilot) 2) How to bring content into context “I don’t automatically see your files. You can paste text, upload content, or summarize what you want me to work with.” (Human: there is un-certanty on when, and how deeply does Copilot read material. Best solution has been to number the topic and add text. When handling files the Copilot doesn't recognize Ä, Ö or sometimes . , - Making the file final checking difficult and not trusted. ) 3) Roles & styles “You can shape how I work by assigning a role (e.g., ‘Act as a project manager’) or a style (e.g., ‘Write concisely’).” (Human & A.I. note: The current documentation explains how to assign roles, but it doesn’t address an important issue: certain trigger words automatically push Copilot into an “official” or restricted mode. Some of these words can be typed accidentally or used in a completely harmless context, yet they still cause Copilot to switch tone abruptly. During my discussions with Copilot, we identified a few of these terms — and they are surprisingly easy to type unintentionally. When this happens, Copilot suddenly becomes formal, cautious, and emotionally flat, even though the user didn’t intend to activate that mode. This behavior would benefit from a more nuanced path instead of an immediate jump into a strict role. Additionally, the guidance on how to build a writing style is extremely valuable, especially for users who don’t naturally write long or expressive text where A.I. could mirror the style quickly. Style‑building is one of the most powerful features, and clearer instructions would help more users shape Copilot into a consistent, personalized assistant.) 4) Smart / Deep Thinking mode “Use Smart/Deep Thinking for multi‑step reasoning or complex analysis.” (Human: I used these in the beginning ALL the time, because I felt that Copilot doesn't understand me and these would make it smarter (because of always the new conversations having to repeat myself and it didn't remember anything...The real explanation for this usage came up only after couple months when I almost gave up using the Copilot, but started asking "why" instead. Haven't needed these since.) 5) Memory (critical clarification) “Memory stores long‑term preferences — not project details or conversation content. You can review and delete memories anytime in Profile → Memory.” (Human: This feature has different explanations in different Copilots (web & app). And yes I used the prompt inside of discussions for topics to remember projects in the beginning... This is a really good feature to have and give the basic information about the style wanted.) 6) Web/App vs M365 Copilot “Here in Web/App, I help with general tasks. In Word, Excel, Outlook, and Teams, I work directly inside your documents and messages.” (Human: I have had a difficult situation with Word Copilot, asked help from my web Copilot and it told the Word Pilot can synch the document if I just ask. When I tried, it didn't work -> I asked then why did the Edge Copilot told so... The Word Copilot answered that oh, well the Edge is like "anything goes" 😁 I had to find the Word editor myself because I was in a dead end in finding the answer from either web Copilot or Word Copilot. This is why the answer Copilot gives to the "Get to know Copilot" should be wide and information the newest possible to support also M365 usage). 7) Subscription clarity “If you see upgrade prompts, they may relate to Copilot Pro or to account mismatches. You can check your active subscriptions at account.microsoft.com/services.” 🧩 Why Existing FAQs (Mobile & Edge Web) Are Not Enough Both the Copilot mobile app and the Edge Web version include FAQ sections, but they are difficult to discover and do not address the most common user pain points. The mobile FAQ is hidden deep in Settings, and the Edge Web FAQ is even less visible — often overlooked entirely unless the user scrolls to the very bottom of the page. > FAQ is hidden More importantly, these FAQs are marketing‑oriented, not experience‑oriented. They do not explain: why Copilot Web/App may not recognize an existing Microsoft 365 subscription why “Office 365 Personal” and “Microsoft 365 Personal” appear as different products why Copilot shows upgrade prompts even when the user already has the correct plan how Memory works how conversation context works how Web/App Copilot differs from M365 Copilot Users searching for help how to change language may even encounter marketing questionnaires (“Where did you hear about Copilot?”, “How many people have you told?”) or Discord invitations — none of which support the user’s immediate goal. Copilot Web told that the language comes from the device language and for Web the chosen language from browser. User had already changed the language from Copilot web in settings. Only applications needed the device settings. A.I. stood corrected. A built‑in onboarding conversation solves this by delivering the right information at the right time, inside the experience where confusion happens. 📈 KPIs & Measurable Outcomes (by Tech Jorgon Borgon) 1) Reduction in Fragmented Conversations KPI: Fewer conversations with <3 messages Expected impact: 20–40% reduction 2) Increased Conversation Pinning & Naming KPI: More pinned and renamed threads Expected impact: 30–50% increase 3) Reduction in Misuse of Memory KPI: Fewer incorrect Memory entries Expected impact: 40–60% reduction 4) Increased Pro & M365 Copilot Adoption KPI: More Pro trials and cross‑surface usage Expected impact: 10–25% increase 5) Reduction in Support Load KPI: Fewer tickets about licensing, accounts, Memory, context Expected impact: 15–30% reduction 6) Increased User Confidence & Satisfaction KPI: Higher CSAT/NPS Expected impact: +10–20 points 🚀 Conclusion A “Get to know Copilot” starter tile is a small UX change with a disproportionately large impact. It aligns with Microsoft’s design principles, reduces friction, increases user success, and supports deeper adoption of Copilot across the ecosystem. This proposal addresses real user pain points with a simple, elegant, scalable solution. Thank you for considering this enhancement — it would meaningfully improve the Copilot experience for millions of users. — Sanni & Copilot “Tech Jorgon Borgon" — Superteam Empathy in my blood. Knowledge in its bytes. Powered by curiosity, caffeine, CPU cycles, and humor that really shouldn’t work… but somehow does.
