Digital Deep Dive: Copilot Control System (CCS)
Join us for two days of insights, demos, and deep dives on Copilot Control System (CCS)! Learn how to secure, manage, and analyze Microsoft 365 Copilot, Copilot Chat, Microsoft Copilot Studio, and agents across your organization using the Copilot Control System (CCS). This two-day digital skilling event kicks off with a guided overview of CCS—your framework for managing Copilot securely, at scale, and with clarity. Day 1 dives into security, governance, and preparing your environment for Copilot and agents. Day 2 shifts to management controls, agent lifecycle, reporting, and user enablement. We’ll close with key takeaways and resources to support your next steps. What to Expect A breakdown of the Copilot Control System and how it applies across workloads Technical guidance for managing oversharing, insider risks, and web search settings Practical ways to build and secure enterprise-scale agents Lifecycle management approaches for Copilot agents and Copilot Studio makers Insights on measurement, analytics, and usage trends Guidance on enabling users and aligning AI adoption with organizational goals Live AMAs with Microsoft product team members throughout the event Day 1: Foundations & Security – Tuesday, June 17, 2025 (PT) Time Session Title Speaker(s) Description 8:00–8:30 AM PT Introduction to Copilot Control System Ben Summers Overview of the event structure, CCS components, and session navigation tips. 8:30–9:30 AM PT Secure Microsoft 365 Copilot and agents Sophie Ke, Dave Minasyan Addressing oversharing risks using SAM and Purview. 9:30–10:30 AM PT Prevent data loss and insider risks for Microsoft 365 Copilot Erica Toelle Using Microsoft Purview to mitigate insider threats and enforce protections. 10:30–11:00 AM PT Understanding web search controls in Microsoft 365 Copilot Alex Pozin, Suhel Parekh Configuring and governing Copilot's web search behavior. 11:00 AM–12:00 PM PT Build enterprise-scale agents securely Mik Ferland Best practices for secure agent lifecycle management and governance. Day 2: Management & Adoption – Wednesday, June 18, 2025 (PT) Time Session Title Speaker(s) Description 8:00–9:00 AM PT Copilot agent management and controls James Bell, Ganesh Krishnamurthy How to manage Copilot agents in the Microsoft 365 admin center. 9:00–10:00 AM PT Empower Copilot Studio makers with enterprise-grade management controls Asaf Tzuk Governance, visibility, and cost management in Copilot Studio. 10:00–11:00 AM PT Measure usage and impact of Copilot and agents Mike Walsh, Samer Baroudi Using Copilot Analytics to assess adoption, usage, and impact. 11:00 AM–12:00 PM PT Practical guidance for AI and collaboration adoption Karuana Gatimu Real-world strategies for enabling collaboration and AI adoption. 12:00–12:15 PM PT That’s a wrap! What’s next for your Copilot Control System journey Efe Abugo Key takeaways, resources, and how to continue learning after the event. How to Participate Register for the Microsoft Tech Community using your email if you haven’t already. This allows you to post comments and ask questions. Visit each individual session page during its scheduled time to join the conversation. You can post your questions in the comments, and product team members will respond live during the AMA. Watch the session live or catch the recording on demand after the event. Keep the conversation going in the Microsoft 365 Copilot Tech Community discussion space after the sessions conclude. It’s a great place to follow up, share what’s working, and connect with others exploring similar topics. Hope to see you there! Come ready to learn and ask our experts all of your burning questions!
Painful behavior of "slash" ("/") in chat prompts
I know about the /commands (/reset, /help, ...) in Copilot powered applications where hitting "/" triggers auto-completion suggestions. Here we are talking about Copilot chat (Teams or Web app for instance) Each time you hit the "/" key, it pops up a menu inviting you to upload files, preventing you from going on typing until you hit the <esc> key. That's too disruptive. That would be ok if the upload menu what acting like a suggestion -- You may select with arrow keys if you wish, or just go on typing if you just need a "/" in your prompts. Please consider disabling this "feature" or I at least enhancing it so the upload menu is not modal and gets dismissed when you go on typing. Comments positive or negative are welcome, thumbs up too 😉
Web Search in Copilot Notebooks Still Disabled Despite Policy Configuration
I've followed Microsoft's documentation to enable Web Search in Microsoft 365 Copilot Notebooks by creating a policy in the Cloud Policy Service. The policy includes: Allow web search in Copilot Pin Microsoft 365 Copilot Chat Allow creation and viewing of Copilot Pages and Notebooks The policy is assigned to an All Staff group, and users have the appropriate Microsoft 365 Copilot licenses. It's been over 24 hours since the policy was applied, but the Web Search toggle in Copilot Notebooks is still greyed out. I've verified: Users are on the Current Channel for Microsoft 365 Apps No conflicting Intune or GPO settings Network access to Bing and Microsoft services is unrestricted Relevant Microsoft documentation: Manage public web access in Microsoft 365 Copilot: https://learn.microsoft.com/en-us/copilot/microsoft-365/manage-public-web-access Configure policies using the Cloud Policy service: https://learn.microsoft.com/en-us/deployoffice/admincenter/overview-cloud-policy Microsoft 365 Copilot service description: https://learn.microsoft.com/en-us/microsoft-365-copilot/microsoft-365-copilot-service-description Has anyone else run into this issue? Any ideas or workarounds?
Repeated Connection Prompts and "Send Failed. Retry" Errors When Using SharePoint Lists in Copilot
Hi everyone, I'm working on integrating SharePoint lists as a knowledge source in a Copilot agent. The setup works initially, but I'm encountering persistent issues when testing the agent or accessing it via Microsoft Teams/SharePoint site after publishing. Issue Details: Initial Connection Prompt: When I first test the agent or access it from Teams/Site, it prompts me to connect to the SharePoint data source. This is expected and works fine. Repeated Prompts: After the initial connection, the agent repeatedly asks me to reconnect to the SharePoint list, even within the same session. This happens multiple times during a single conversation. Error Message: Frequently, I receive the error message: "Send failed. Retry" This disrupts the conversation and makes the agent unreliable for end users. After 2-3 retry it worked Expected Behavior: I expect the connection to persist once authenticated, and for the agent to access the SharePoint list seamlessly throughout the session. What I’ve Tried: Verified that the SharePoint list is correctly configured and accessible. Ensured that the data source connection is added and published in the Copilot Studio. Tested in both the Copilot Studio test environment and Microsoft Teams and its working fine on Copilot Studio test environment. Questions: Is this a known issue with SharePoint list integration in Copilot agents? Are there any best practices to ensure persistent authentication or session handling? Could this be related to Teams-specific permissions or token expiration? Any workarounds or configuration changes that could help resolve this? Any help or guidance would be greatly appreciated! Thanks in advance.
Help Needed: Sharing Microsoft 365 Copilot Chat AI Agent with Colleagues
Hello everyone, I have a Microsoft 365 Copilot license and have created my own Chat AI Agent using Copilot Chat. This agent is designed primarily for chat responses, with knowledge sourced from a specific website and an internal SharePoint site. I shared the agent with my colleagues, and they are able to install it. However, when they ask questions, they always receive the response: "Sorry, I’m unable to respond to that. Is there anything else I can assist you with?" All these colleagues have access to the SharePoint site, and regardless of whether they have a Microsoft 365 Copilot license or not, they get the same unhelpful answer. Could someone please advise how I can enable everyone to use this agent properly? Thank you in advance for your help!
Is application/vnd.api+json a supported API response format for a Copilot Declarative Agent?
I have been testing some 3rd party API's we use to see how they work with a declarative copilot agent built with the MS365 Agents Toolkit (formerly the Teams Toolkit). I have one API that the agent fails to return responses from (it successfully calls the API, but the debug console says it failed to return data). As far as I can tell application/vnd.api+json is a standard .JSON format (and everything works fine in Postman) so I am trying to get some clarity on if this is supported or not (or if someone has been able to get this working).
