Copilot Studio agents gain accounts, memory and triggers
Diesen Beitrag auf Deutsch lesen
Copilot Studio Frontier agents can use their own Microsoft 365 identity, shared business-process memory and event or schedule triggers.
TL;DR
Copilot Studio agents in the Frontier rollout can receive their own Microsoft 365 identity and mailbox, share business-process memory across users, and start work from events or schedules. Publishing and activation are required, usage is metered, and agent accounts currently support document generation but not targeted editing or coauthoring of existing documents.
Original by Josh Cook, on Flow Alt Delete. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Pilot one small shared process with synthetic information and two users to inspect memory, tool identity and trigger behavior.
- Admins/IT: Confirm the early-release environment, administrator activation and licensing prerequisites before promising an agent-account pilot.
- Leadership/Business: Define an owner, task and reviewable output because shared memory can expose summaries beyond the people who accessed the original content.
Frequently asked questions
How do Copilot Studio agent accounts share memory between users?
Agent-account memory is shared across users, including one-to-one conversations. Summaries of contributed files or chats can appear to people who cannot access the originals.
What can Copilot Studio agent triggers start?
Triggers can start agent work from events or schedules, but the agent’s tools and instructions determine what it does. Publishing and activation are required.
What licenses are required for Copilot Studio agent accounts?
The stated prerequisites include Microsoft 365 E5 plus Agent 365, or E7, and an available Microsoft 365 Frontier for AI Teammates license for each agent.