
Agent 365 / AI Teammate install fails with "You don't have the required licence"
I Built a custom AI Teammate agent using the a365 CLI1.1.184, blueprint created in Entra, all 5 admin consents granted (Microsoft Graph, Messaging Bot API, Agent 365 Tools, Observability API, Power Platform API), Observability S2S app role assigned, messaging endpoint registered, manifest published. Teams Developer Portal config done (API Based + notification URL on our App Service). I've verified the blueprint app properties through Graph too managerApplications set, signInAudience AzureADMultipleOrgs, access_agent_as_user scope enabled. As far as I can tell every documented requirement is met.
On the licensing side, the affected users all have Microsoft 365 E3 + Microsoft 365 Copilot + Agent 365 (the per-user GA SKU, purchased post-launch on May 1). Per Microsoft's own Agent 365 Licensing FAQs at https://www.microsoft.com/licensing/faqs/122 the docs are unambiguous:
"Agent 365 is licensed per user, whether purchased as part of Microsoft 365 E7 or as a standalone offering. **Agents do not require their own licenses.** Blueprints, agents, and agent instances are not licensed separately. They do not count as individual licensing units."
So in theory we're fully licensed. In practice, two things go wrong.
First, when I upload the manifest in the M365 admin centre the Apply Template step shows "Microsoft Agent 365 - 0 of 0 licenses available"
In o365 admin portal, licenses section, I can see Agent 365 with 19 available out of 25
the wizard calls it "Microsoft Agent 365" but the licensing page just calls it "Agent 365" It might be a naming inconsistency, might be a hint that they're pointed at different things. Either way the wizard counter doesn't actually block publishing so I clicked through, the agent shows as Available in the Agents Registry, all looks good.
Then licensed a fully licensed user tries to install / Create instance from the Copilot Agent Store (m365.cloud.microsoft/chat/agentstore) and gets "You don't have the required licence to create this agent." every time.
I opened DevTools in Edge and captured the HAR while reproducing it. The client fires this sequence on every failed attempt:
AgentDetailsDialogAddButtonClicked
AgentDetailsDialogCreateBlueprintMissingLicense
AgentCenterDetailsDialogInfo
errorMessage: "BlueprintMissingLicense"
licenseType: "AAD_AISKU"
acquisitionTitleState: "Unacquired"
Same telemetry block also reports `m365CopilotAcquisitionState: "acquired"` and `officeHomeEcsRing: "FrontierPublic"` so the client itself agrees we're M365 Copilot licensed and on the Frontier ring, yet it still rejects with BlueprintMissingLicense.
I've ruled out a load of stuff already. Tried manifestVersion devPreview and 1.27, no change. Verified everything via Graph against the Learn docs and it all checks out. Admin consents are tenant-wide. Blueprint SP sign-in logs are completely empty during failed installs which tells me the rejection is happening upstream of any token request against our agent. Built a brand new parallel test agent from scratch today on the latest CLI just to rule out stale state on the original same exact error. Tried PATCHing assignLicense against the blueprint SP via Graph and Graph says Method Not Allowed (which lines up with the FAQ saying agents don't get their own licences). I also googled BlueprintMissingLicense and got zero hits anywhere, including Microsoft's own Agent365 GitHub repos.
Best guess at this point is the wizard counter and the install code path are both checking for a per-agent-instance licence pool that the GA licensing FAQ explicitly says doesn't exist. Our per-user pool is healthy with 19 free seats. There's a direct contradiction between Microsoft's documented model (https://www.microsoft.com/licensing/faqs/122) and the deployed code path.