Recent Discussions
Deleted Copilot Chats and Temporary Chat: What End Users Should Know
I published a short video for end users who are asking a practical Copilot question: Can employers see deleted Copilot chats? The question usually starts when users see the “Permanently delete chat?” warning in Copilot. That warning can be easy to misunderstand, especially in work or school accounts where workplace policies may still apply. The video explains this in plain language, including: What users should understand before deleting Copilot chats Why Temporary Chat needs a closer look Why deleted from your view may not mean the same thing in a workplace account What users should avoid typing into Copilot at work Watch the video here: https://youtu.be/ND9Cdp5h9rs?si=FyBkInRHpVgc_x1I Supporting article: https://traccreations4e.com/can-employers-see-deleted-copilot-chats/ Related deletion guide: https://traccreations4e.com/copilot-delete-chat-history/ traccreations4e-p26 6/8/2026Copilot Studio Preview : MCP Agent works in Teams but not in Microsoft 365 Copilot Chat
I’m currently testing the new preview version of Copilot Studio and I ran into a behavior I’d like to validate with the community. I created a custom Copilot agent using the new interface, connected to a Microsoft Learn MCP server (for retrieving official documentation), and deployed it across both: - Microsoft Teams - Microsoft 365 Copilot (Copilot Chat) Configuration-wise, everything seems correctly set up: - Agent published - Channel enabled for Teams and Microsoft 365 Copilot - Permissions and access configured - MCP tool working properly Here is the key point: - In Microsoft Teams: The agent works perfectly. It correctly calls the MCP server, retrieves Microsoft Learn documentation, and returns accurate responses. - In Microsoft 365 Copilot Chat: The same agent does not work at all. No MCP call is triggered, and no response is generated from the agent. Instead, Copilot returns the following message: "Sorry, I am not able to find a related topic. Can you rephrase and try again?" Even with: - Explicit invocation using @AgentName - Very simple prompts - Minimal instructions - Added knowledge sources (for testing) The behavior remains the same. At this point, it looks like: - The agent is accessible and deployed - But it is not actually executed by the Microsoft 365 Copilot runtime Has anyone experienced the same behavior with agents in the new Copilot Studio preview, especially when using MCP tools? Is there any known limitation or requirement for agents to be properly executed inside Microsoft 365 Copilot Chat (compared to Teams)? Thanks in advance for your feedback.6Views0likes1CommentLearning Agent by Microsoft: The Future of Personalized AI-Powered Employee Upskilling Has Arrived
In today’s rapidly evolving workplace, one challenge continues to stand out for organizations across industries: keeping employee skills aligned with changing business needs. Traditional training programs often struggle to deliver relevant learning experiences at the right time, leaving employees overwhelmed with generic courses that may not match their career goals or daily responsibilities. https://dellenny.com/learning-agent-by-microsoft-the-future-of-personalized-ai-powered-employee-upskilling-has-arrived/32Views0likes0CommentsCan Microsoft Frontier Program Copilot Cowork Agent Delegate Tasks to Other Copilot Agents?
Hi everyone, I'm currently exploring the capabilities of Copilot Cowork that is available through the Microsoft Frontier Program, and I'm trying to understand whether a multi-agent orchestration pattern is officially supported. My Use Case I want users to interact with only a single, central Copilot Cowork agent. For example: User asks the Cowork agent to create or update a Jira ticket. Instead of Cowork handling the Jira operation directly, it delegates or hands off the task to a dedicated Jira Copilot Agent. The Jira agent performs the required actions and returns the result. The Cowork agent then presents the final response back to the user. Similarly, I would like to have specialized agents for: Jira ServiceNow Knowledge Management HR Operations Internal IT Support Other business systems The goal is to have Cowork act as an intelligent orchestrator/router while specialized agents handle domain-specific operations. Questions Is agent-to-agent delegation or handoff officially supported in Copilot Cowork (Frontier Program)? Can Cowork directly invoke another Copilot Studio agent? Is there any built-in multi-agent orchestration framework available today? If this is supported, what is the recommended architecture and implementation process? If it is not currently supported, what workarounds are people using? Power Automate? Agent as a tool/action? Custom APIs? Azure AI Foundry / Azure AI Agent Service? Other approaches? I'm specifically looking for guidance from anyone who has worked with Copilot Cowork in the Frontier Program, since the documentation and public examples seem to focus mostly on standalone agents. Any insights, architecture diagrams, documentation links, or real-world experiences would be greatly appreciated. Thanks!37Views1like1CommentMicrosoft Introduces Scout: The Always-On Personal AI Agent
Microsoft has officially unveiled Microsoft Scout, a new AI-powered personal agent designed to work continuously in the background and help users manage tasks, schedules, communications, and workflows across the Microsoft 365 ecosystem. Announced on June 2, 2026, Scout represents Microsoft’s latest step toward autonomous AI agents that move beyond traditional chatbot interactions and actively help users get work done. https://dellenny.com/microsoft-introduces-scout-the-always-on-personal-ai-agent-that-could-redefine-workplace-productivity/108Views0likes1CommentDesigning Multi-Agent Systems in Copilot Studio
Modern organizations rarely solve complex business problems with a single AI assistant. Customer support, IT operations, sales, HR, and analytics teams all have different goals, data sources, and workflows. This is where multi-agent systems become valuable. Instead of relying on one large, general-purpose agent, a multi-agent architecture uses several specialized agents that collaborate to complete tasks efficiently. https://dellenny.com/designing-multi-agent-systems-in-copilot-studio/35Views0likes0CommentsCopilot Studio Pricing Explained for Enterprises: Licensing, Costs, and ROI in 2026
As enterprises accelerate their AI adoption strategies, Microsoft Copilot Studio has emerged as one of the most powerful platforms for building custom AI assistants, automating business processes, and creating intelligent customer experiences. Whether you’re developing internal employee copilots, customer support agents, or workflow automation tools, Copilot Studio provides a flexible environment to create AI-powered solutions tailored to your business needs. https://dellenny.com/copilot-studio-pricing-explained-for-enterprises-licensing-costs-and-roi-in-2026/45Views0likes0CommentsCopilot Connectors >Azure DevOps Work Items >Add Property
Hi I have setup the Azure DevOps Work Item connector and all is working OOTB. However when I try to 'Add a new source Property' and add for example 'TargetDate' when I publish the schema change it errors with: Schema failed to publish with error [Removal existing property is not allowed.] I havent removed anything just added. Anyone else experienced this? Many thanks7Views0likes0CommentsPowerShell: Export Microsoft 365 Copilot Agent Inventory and Availability Assignments
Hi everyone, I needed a way to export Microsoft 365 Copilot agent inventory and availability assignments from the Microsoft 365 Admin Center, but couldn't find a built-in export option. After investigating the admin portal's network traffic, I built a PowerShell script that uses the same internal API consumed by the Microsoft 365 Admin Center to export all Copilot agents to CSV. ### Features - Exports all Microsoft 365 Copilot agents - Automatically follows pagination (`nextLink`) - Exports: - Agent Name - App ID - Title ID - Publisher - Created By - Availability Settings - Allowed Users / Groups - Assignment Information - Deployment Information - Version Information - Timestamps - CSV output ### Tested The script has been tested against a tenant containing 482 Copilot agents and successfully exported the complete inventory. ### GitHub https://github.com/gwestergren/M365-Copilot-Agent-Inventory ### Notes - Uses an authenticated browser session cookie from the Microsoft 365 Admin Center. - Uses the same internal API currently consumed by the admin portal. - This is an undocumented API and Microsoft may change it at any time. Feedback, testing results, and improvements are welcome. Here are some screen shots: output to csv Successful run of the scriptHas anyone seen Excel workbooks become corrupt after using M365 Copilot to summarize data?
We’ve run into an issue twice where a user opened an existing Excel sales workbook, used Microsoft 365 Copilot in Excel to summarize/analyze the data, received the response successfully, and then later could no longer open the original workbook because Excel reported it as corrupt. Internally, this has been reported as happening on some files but not all, and it has occurred twice so far. I’m trying to determine whether this is: a known issue with Copilot in Excel a workbook-specific problem related to file location/sync/versioning or something tied to workbook structure I did find public reports of related Excel Copilot issues — including Copilot crashing in Excel, failures that seem specific to certain workbooks, and Copilot-created Excel files being reported as invalid/corrupt — but I have not yet found a clear Microsoft-hosted thread describing this exact scenario with the original existing workbook becoming corrupt after summarization. If anyone has seen this, I’d appreciate any insight on: whether Microsoft has acknowledged a known issue whether this points to specific workbook features/structures whether there are logs or diagnostics that help isolate root cause whether there are best practices to reduce the risk9Views0likes0CommentsSuccession 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.8Views0likes0CommentsFollow Microsoft Build Live for the latest updates and announcements
Microsoft Build is happening now, and the live blog is a great way to stay up to date on the latest announcements, demos, and key moments as they happen: 👉 Follow Microsoft Build Live What are you most interested in learning more about from Build this year? 👀61Views1like0CommentsPlatform Issue: Agent-Level MCP Initialization Blocks All Topics for Users Without Connection Access
I’m writing to report a significant platform behavior issue we’ve encountered with MCP (Model Context Protocol) server initialization in Copilot Studio that is severely impacting end-user experience. ENVIRONMENT • Platform: Microsoft Copilot Studio • Deployment Channel: Microsoft Teams • Agent Type: Custom Agent (EdiSENSE DEV) • MCP Server: Atlassian Confluence-Jira MCP • Affected Users: Users without Confluence/Jira access entitlements PROBLEM SUMMARY When an MCP server is registered at the agent level in Copilot Studio, it appears to be initialized globally before any topic routing occurs. If a user’s MCP connection is in a Not Connected state — even if their query has absolutely nothing to do with that MCP server - the agent gets stuck in an authentication loop, repeatedly prompting: “Let’s get you connected first. Open connection manager to verify your credentials. Once the connection is ready, retry your request.” The user is shown Retry / Cancel buttons, and the agent never proceeds to route the query to the appropriate topic. STEPS TO REPRODUCE 1. Register an MCP server (e.g., Confluence-Jira) at the agent level in Copilot Studio 2. Deploy the agent to Microsoft Teams 3. Log in as a user who does NOT have access to the MCP-connected service (e.g., no Confluence license) 4. Ask the agent any question completely unrelated to the MCP service 5. Observe: Agent does not route to any topic. Instead, it loops on MCP connection prompt indefinitely EXPECTED BEHAVIOR • MCP initialization failure for a specific service should NOT block unrelated topic routing • The agent should gracefully degrade - if an MCP connection is unavailable for a user, it should skip that MCP and continue routing the query to relevant topics • There should be a way to scope MCP connections to specific topics, or at minimum, mark them as optional/non-blocking ACTUAL BEHAVIOR • Agent-level MCP initialization blocks the entire conversation flow • Users without MCP access cannot use ANY functionality of the agent, even features completely unrelated to the MCP service • There is no graceful fallback or bypass mechanism available to agent builders BUSINESS IMPACT This is a critical gap for enterprise deployments where: • Not all users have access to every integrated service • Agents serve a broad user base with varying entitlements • Admins have no control over MCP initialization order or failure handling In our case, a large portion of our Teams users are completely locked out of the agent’s core functionality simply because they don’t have a Confluence license - even though they never intended to use Confluence-related features. FEATURE REQUEST / SUGGESTED RESOLUTION 1. Allow MCP servers to be scoped at the topic level, not just agent level 2. Introduce an optional flag for MCP connections so initialization failure is non-blocking 3. Provide agent builders with a connection status condition node in the topic flow to handle MCP failures gracefully 4. At minimum, allow the Cancel button in the auth prompt to fall through to normal topic routing I’d appreciate any guidance on whether there is a current workaround, or if this is a known limitation on the roadmap for resolution. Thank you for your time and support.19Views0likes1CommentHow to Build Your First AI Agent in Copilot Studio in 15 Minutes
Artificial Intelligence is no longer reserved for data scientists and software developers. With tools like Microsoft Copilot Studio, anyone can create intelligent AI agents that automate tasks, answer questions, and improve productivity without writing complex code. https://dellenny.com/how-to-build-your-first-ai-agent-in-copilot-studio-in-15-minutes/54Views0likes0CommentsPrompt Lab: Three Critical Bugs That Make It Unusable as a Prompt Management Tool
Product: Microsoft 365 Copilot — Prompt Lab (accessed via ... button in Copilot Chat) Date: June 1, 2026 Environment: M365 Copilot, Web (Edge), Work IQ mode Bug #1: Empty State Crash Steps to reproduce: Open Prompt Lab via the ... button in Copilot Chat Ensure "Your saved prompts" contains zero prompts (either as a new user or by deleting all saved prompts) Observe the result Expected behavior: An empty state placeholder (e.g., "You haven't saved any prompts yet.") Actual behavior: The entire Prompt Lab panel throws a red error banner: "Something went wrong. Please close the dialog and try again later." The "Your saved prompts" category does not render at all. The panel only shows Microsoft's preset categories (Prompt topics, Agent prompts). Why this matters: An empty container is a valid state — it is literally every new user's initial state. A UI component should never crash because a list has zero items. This is a null/empty array handling failure that should have been caught by basic QA. Bug #2: Search Does Not Index User's Saved Prompts Steps to reproduce: Save a custom prompt with a distinctive title (e.g., "AI每日新闻") and body containing the keyword "AI" Open Prompt Lab Use the search box at the bottom to search for "AI" Expected behavior: Search results include the user's saved prompt alongside Microsoft's preset prompts. Actual behavior: Only Microsoft preset prompts matching "AI" are returned (e.g., "Stay on top of AI," "Prompt Compliance"). The user's own saved prompt — whose title and body both contain "AI" — does not appear in the results. Why this matters: The search box creates a false expectation that it searches all prompts. In reality, it only indexes Microsoft's template library. This means as a user accumulates more saved prompts, the only way to find one is manual scrolling. A search function that excludes user-created content is fundamentally broken by design. Bug #3: Saved Prompts Lost During Migration Context: The standalone Copilot Lab / Prompt Gallery app was retired on July 15, 2025, and its functionality was merged into the built-in Prompt Lab within Copilot Chat. What happened: All previously saved prompts from the old Copilot Lab app are gone. They do not appear in the new Prompt Lab's "Your saved prompts" section. There was no migration notice, no export tool for end users, and no recovery path. Why this matters: Users invested time curating and refining their prompt libraries. Silently dropping that data during a platform migration — without warning, backup, or migration tooling — is a breach of user trust. Summary These three issues compound into a single conclusion: Prompt Lab is currently non-functional as a prompt management tool. Capability Status Reliable storage ❌ Data lost during migration Empty state handling ❌ Crashes when empty Search / retrieval ❌ Does not index user content Displaying Microsoft templates ✅ Works The only feature that works correctly is showcasing Microsoft's own preset prompts. For a tool whose entire purpose is to help users save, organize, and reuse their own prompts, this is an unacceptable state of quality. I'd strongly recommend the team prioritize: (1) proper null-state handling, (2) including user prompts in the search index, and (3) investigating whether migrated prompt data can be recovered from Substrate.44Views0likes0CommentsCopilot Down - June 1st
I used Copilot this morning and everything was working smoothly. All of a sudden when I open the app on Windows I get this message "Couldn't load the app. Wait a bit, then try again." I tried using the version on Edge but I get a "503 Service Unavailable Error." I tried restarting my laptop and I get the same error. Checked on my phone app and indeed, it confirmed the service is down. Does anyone know when this will be resolved?356Views0likes3CommentsCopilot Studio agent not visible in M365 mobile app without desktop access
Hi, I'm having an issue with a Copilot Studio agent not being discoverable in the Microsoft 365 mobile app for users without desktop access. **Setup:** - Agent created in Copilot Studio, published and shared with specific users - All users have the same Microsoft 365 Copilot license - Target channel is the Microsoft 365 app (not Teams) - The agent has been published to both the Teams and Microsoft 365 channels in Copilot Studio **The problem:** Users who have access to a desktop/browser can open the agent via a direct link, add it, and after that it appears correctly in the M365 mobile app. However, users who only have access to the M365 mobile app cannot find the agent there — even though it has been shared with them. **What I've tried:** - Verified the agent is published and shared directly with the affected users in Copilot Studio - Confirmed all users have the same license - Published the agent to both Teams and Microsoft 365 channels - Sending a direct link to the agent — works on desktop/browser but not actionable in the mobile app in a way that adds the agent - Logging out and back in to the M365 mobile app **What I'm looking for:** Is there a way for users to discover and add a shared Copilot Studio agent directly from the M365 mobile app, without needing desktop or browser access first? Any help or workarounds are appreciated!Solved53Views0likes3CommentsSurface Copilot+ PCs: Microsoft’s Bold Step into the Future of AI Computing
The personal computer has evolved dramatically over the past few decades. From simple productivity machines to powerful devices capable of handling creative workloads, gaming, and business operations, PCs continue to redefine what users can accomplish. Now, Microsoft is ushering in a new era with its Surface Copilot+ PCs, a lineup designed to bring artificial intelligence directly into everyday computing experiences. https://dellenny.com/surface-copilot-pcs-microsofts-bold-step-into-the-future-of-ai-computing/41Views0likes0CommentsHow Microsoft Copilot Studio Fits Into the Power Platform Ecosystem
Artificial intelligence is no longer just a futuristic concept reserved for large enterprises with deep technical teams. Today, businesses of all sizes are searching for practical ways to automate repetitive tasks, improve customer experiences, and empower employees with smarter tools. This shift is exactly where Microsoft Copilot Studio enters the picture. https://dellenny.com/how-microsoft-copilot-studio-fits-into-the-power-platform-ecosystem/37Views0likes0Comments
Events
Recent Blogs
- Meet Learning Agent in Microsoft 365 Copilot Today we’re excited to announce the general availability of Learning Agent in Microsoft 365 Copilot, to help every employee build Copilot and AI sk...Jun 02, 20268.9KViews6likes0Comments
- Welcome to the May 2026 edition of What's New in Microsoft 365 Copilot! Every month, we highlight new features and enhancements to keep Microsoft 365 admins up to date with Copilot features that...May 29, 202611KViews7likes4Comments