Unable to publish Foundry agent to M365 copilot or Teams
I’m encountering an issue while publishing an agent in Microsoft Foundry to M365 Copilot or Teams. After creating the agent and Foundry resource, the process automatically created a Bot Service resource. However, I noticed that this resource has the same ID as the Application ID shown in the configuration. Is this expected behavior? If not, how should I resolve it? I followed the steps in the official documentation: https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/publish-copilot?view=foundry Despite this, I keep getting the following error: There was a problem submitting the agent. Response status code does not indicate success: 401 (Unauthorized). Status Code: 401 Any guidance on what might be causing this and how to fix it would be greatly appreciated.What's New in Microsoft EDU webinar - August 2025
Join us on Wednesday, August 20th, 2025 for our latest "What's New in Microsoft EDU" webinar! These 30-minute webinars are put on by the Microsoft Education Product Management group and happen once per month, this month both 8:00am Pacific Time and 4:00pm Pacific time to cover as many global time zones as possible around the world. And don’t worry – we’ll be recording these and posting on our Microsoft Education YouTube channel in the new “What’s New in Microsoft EDU” playlist, so you’ll always to able to watch later or share with others! Here is our August 2025 webinar agenda: Microsoft Copilot and Copilot Chat for students 13+ M365 Copilot updates for Educators and Students Learning Zone public preview and the Copilot+ PC Microsoft 365 LTI for Learning Management Systems Learning Accelerator updates Microsoft 365 app updates AMA - Ask Microsoft EDU Anything (Q&A) We look forward to having you attend the event! How to sign up OPTION 1: August 20th, Wednesday @ 8:00am Pacific Time Register here OPTION 2: August 20th, Wednesday @ 4:00pm Pacific Time Register here This is what the webinar portal will look like when you register: Look forward to seeing you there! Mike Tholfsen Group Product Manager Microsoft EDUMastering Agent Governance in Microsoft 365
The "Mastering Agent Governance in Microsoft 365" series is based on the Administering and Governing Agents whitepaper published by Microsoft and designed to educate IT leaders, compliance officers, and decision-makers about the importance of governance for AI agents in Microsoft 365, particularly in highly regulated industries like Healthcare and Life Sciences (HLS). The six-episode series cover the growing role of agents, the risks of unmanaged agents, and the strategic importance of governance frameworks. Empowering innovation while protecting patient data and ensuring compliance In the age of AI-powered productivity, agents—automated digital assistants built with tools like Microsoft 365 Copilot, SharePoint, and Copilot Studio—are transforming how work gets done. From streamlining clinical documentation to automating regulatory reporting, agents are becoming indispensable in Healthcare and Life Sciences (HLS). But with great power comes great responsibility. Why Governance Can’t Be an Afterthought In highly regulated industries like HLS, where data sensitivity and compliance are paramount, the rise of autonomous agents introduces new risks: Unauthorized data access could expose protected health information (PHI). Unmonitored agent behavior could lead to regulatory violations. Lack of lifecycle controls could result in outdated or insecure agents operating in production environments. Agent governance isn’t just an IT concern—it’s a business imperative. It ensures that innovation doesn’t outpace compliance, and that every agent deployed aligns with organizational policies, security standards, and regulatory frameworks like HIPAA, GDPR, and FDA 21 CFR Part 11. Understanding the Agent Landscape Microsoft 365 supports a spectrum of agent creators: End Users using SharePoint or Copilot templates to automate simple tasks. Makers building more complex agents in Copilot Studio. Developers crafting sophisticated, enterprise-grade agents with Azure AI and Teams Toolkit. Each persona requires a different level of oversight. For example, a clinical researcher using SharePoint to build a data retrieval agent may need minimal governance, while a developer building a patient-facing chatbot must adhere to strict data protection and validation protocols. Governance in Action Microsoft provides a layered governance model: Tool Controls: Define what agent creators can do within tools like Copilot Studio and SharePoint. Content Controls: Ensure agents only access data they’re authorized to use, leveraging Microsoft Purview for sensitivity labeling and DLP. Agent Management: Monitor usage, enforce lifecycle policies, and block non-compliant agents via the Microsoft 365 Admin Center. This framework allows organizations to empower innovation while maintaining control—critical in environments where patient safety and regulatory compliance are non-negotiable. The Business Case for Governance For HLS organizations, agent governance delivers tangible benefits: Reduced compliance risk through proactive policy enforcement. Improved operational efficiency by enabling safe automation. Greater trust from patients, regulators, and internal stakeholders. In short, governance is the foundation that allows agents to scale safely and sustainably.95% Efficiency creating Contract Renewal J&A with M365 Copilot
Episode 1: “The COR Files – Automating the Annual Grind” In the world of federal procurement, Contracting Officer’s Representatives (CORs) are the unsung heroes. Managing contracts, ensuring they contracts are executed effectively and in compliance with the FAR. Among their many responsibilities, every contract requires full and open competition unless "the agency head determines that it is not in the public interest" (FAR 6.302-7); or maybe it's due to use of brand name (FAR 11.104). No matter the reason, when an exception is required the COR will prepare a Justification and Approval (J&A) document showing salient physical, functional, or performance characteristics of the solution. During a recent Prompt Design engagement at the Microsoft Innovation Hub, Washington DC, a COR walked us through the process they have to do for each of the 800 contracts their office manages. Each year, as many as 800 contracts go through a J&A. Depending on familiarity with the contract this can take 4-5 hours of research, organization, documentation, and even creating a presentation. We have over 100 people who, as a tertiary responsibility, must create these or risk a contract being lost and the organization has to start from zero in bidding the solution again. However, in 30 minutes of brainstorming and testing, their Prompt Design team developed the following M365 Copilot prompt. The COR then used Copilot in PowerPoint to automatically generate a slide deck from the output, applied the agency PowerPoint template, and they were done. The result? What normally took half a day was completed in under 30 minutes. Under 5 minutes to create the salient characteristics and the PowerPoint slides, the remaining time reviewing the content and validating its accuracy. “As a Contracting Officer's Representative, I want to develop salient characteristics about [NAME OF TECH] to write a justification and approval using my OneDrive folders [REFERENCE FOLDER NAME OF TECHNOLOGY DOCUMENTATION]. Reference old procurement documents [REFERENCE FOLDER NAME OF SAMPLE PROCUREMENT DOCUMENTS] to help understand the expected format.” When scaled across an agency managing 800 IT contracts, the COR estimates a potential savings of as much as 3,600 hours annually and more than 95% efficiency gained. What ways has your agency successfully used M365 Copilot to gain efficiencies in the annual grind? Copilot+Alt+Gov COPILOT+ALT+GOV is a series dedicated to sharing government use cases for generative AI from real government employees. In the spirit of reproducing these results in as many agencies as possible, we will work to share as much information about the process, the use cases, and the impact of these use cases. If you have a use case YOU want to share, reach out to and me, we'd love to work with you on it! Learn more at aka.ms/copilotgov
