Microsoft made two changes in April 2026 that pulled Copilot in opposite directions. Chat disappeared from Word, Excel, PowerPoint, and OneNote for unlicensed users in tenants over 2,000 seats, and prepaid capacity packs started working without an Azure subscription. The licensing fog around agents got sharper, not simpler. This article maps the four layers admins need to walk before sharing a Copilot Studio agent (user license, authentication, sharing surface, consumption), pulls in a real test where an unlicensed user happily ran a tenant-grounded agent without a single capacity pack purchased, and explains why that doesn’t break the rule, just exposes where the bill is hiding. It also covers the Work IQ toggle that quietly splits your agent’s behaviour into two: one experience for licensed users, another for everyone else.
Microsoft patched CVE-2026-26133 on March 11, 2026 — a cross-prompt injection vulnerability in Copilot’s email and Teams summarization that let attackers shape what your AI told you, without a single attachment or macro. The specific exploit is closed. But the attack exposed something a patch alone cannot fix: Copilot trusts the content it reads, and in a misconfigured tenant, that trust is a liability. Here is what happened, why it matters beyond the CVE, and what admins should actually do about it.
Keep those EPIC prompts stored centrally and av. With the introduction of the Power App Prompt Buddy, Microsoft Teams users now have a streamlined solution for managing and sharing AI prompts. This tool is designed to enhance team productivity by facilitating the easy exchange of AI-driven insights and ideas. This post aims to guide you …
