Copilot Notebooks chat and file creation
I recently have access to the Notebooks in Copilot after the recent update, including chat search!, when using chat within a created notebook, has anyone else seen an issue with Copilot making the document actually available for download? I've tried different ways and only get it telling me the file is ready to download in this location: "sandbox:/mnt/data/[filename is listed here]". My first thought was maybe it wa just putting this newly generated file into the References within the Notebook...but it was not. If I get out of the chat in a Notebook and just start a new web or work chat and ask for the same file to be created, it works as usual with a link to download.
Copilot Chat page displays "Coming Soon" message
Over the past couple of days, I've had several people in my org report that they see a "Coming Soon" page when attempting to use Microsoft 365 Copilot Chat (see included image). The two people reporting the issue to me this week both have Microsoft 365 E3 licenses with standard Copilot Chat included, and they were not seeing this page last week. I tested with an account that has that same licensing as well as an account that has Microsoft 365 Copilot license, but I could not recreate the issue. For the people impacted, here is what I've noticed: It occurs in both Chrome and Edge. It occurs when the URLs in the address bar are m365.cloud.microsoft or copilot.cloud.microsoft The Edge sidebar app for Copilot seems to work, but when the popout button is used, it displays the "Coming Soon" message. If anyone has some insight on this or additional troubleshooting guidance, I'd greatly appreciate it! Thanks!Microsoft 365 Copilot Notebooks Explained: A Complete Guide (2025)
🚀 Discover the New Microsoft 365 Copilot Notebooks! In this video, I dive into the latest feature in the Microsoft 365 ecosystem — Copilot Notebooks. Whether you're a productivity enthusiast, IT admin, or business user, this deep dive will show you how Copilot Notebooks can help you analyze, automate, and work smarter. 🔍 What you'll learn: What are Copilot Notebooks? How to use them effectively in Microsoft 365 Real-world scenarios and productivity tips Integration with the new M365 dashboard My first impressions and use case examples 📌 Stay ahead in your Microsoft 365 journey and see how AI is reshaping productivity with tools like Copilot. 👇 Let me know in the comments how you plan to use Copilot Notebooks! 🔔 Don’t forget to subscribe for more Microsoft 365 insights: youtube.com/giulianodeluca #Microsoft365 #CopilotNotebooks #M365Copilot #MicrosoftCopilot #ProductivityAI #GiulianoDeLuca #TechNews #Microsoft365Tips #AIProductivity #Office365 #CopilotInActionMastering 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.Copilot agent not working on team when added as an app
We have created few agents, and it works as expected in copilot studio. The agent was published on teams and added as an app. It behaves differently on teams and does not refer to the knowledge source provided. Instead, it is showing generic web data (old LLMs probably). Not sure if we are missing any features in GCC tenants
