microsoft / microsoft/Agent365-Samples
Creating an AI Teammate agent instance in Teams fails with HTTP 500 at the final activation step, on a completely clean blueprint.
@ajmfehr is already working on this.
Since Jun 11, 2026.
- Dominant language
- C#
- Stars
- 108
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
What I'm trying to do
I'm building an AI Teammate agent ("a governance assistant") to demo at an upcoming conference session on agent governance with Agent 365. The goal is a working end-to-end story: an agent registered as a first-class identity, deployed to the cloud, observable, and reachable in Teams — so I can show the full governance lifecycle live.
I've gotten everything working except the very last step: activating the agent instance in Teams consistently fails with HTTP 500.
Environment
- Frontier-enrolled tenant
- Agent 365 standalone license
- AI Teammate agent (
a365 setup all --aiteammate --m365) - CLI version: 1.1.199
- Agent code hosted on Azure Container Apps, confirmed running and healthy
Steps to reproduce
- Clean up all old blueprints (
a365 cleanup) and purge soft-deleted ones via Graph a365 setup all --aiteammate --m365 --agent-name "<name>"— completes successfully- Confirm
managerApplicationsis set on the blueprint - Register messaging endpoint via
a365 setup blueprint --endpoint-only a365 publish, then upload manifest to admin center (succeeds)- All 4 wizard steps complete (Select users, Apply template, Accept permissions, Review & finish)
- Final activation fails: "We couldn't activate your agent. Request failed with status 500"
Expected behavior
Agent instance activates and the AI Teammate is provisioned.
Actual behavior
HTTP 500 at activation. Reproduced on two separate clean blueprints with identical results.
Verified NOT the cause
- Single blueprint, no duplicates (soft-deleted ones purged)
managerApplicationsis set on the blueprint- All API permissions consented (Graph, Agent 365 Tools MCP, Bot API, Observability, Power Platform)
- S2S app roles granted
- Agent running and healthy in hosting (/api/health returns ok)
- Messaging endpoint registered successfully
- Manifest uploaded successfully
- Tenant is Frontier-enrolled
I'd appreciate if you could help me fix this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.