Copilot Studio agent accounts: your AI gets its own login

Your next Microsoft 365 user might not be a person. On October 15, Microsoft announced that Copilot Studio agent accounts are rolling out through its Frontier early-access program. Agents get their own credentials, start work on a trigger instead of a prompt, and keep memory of a business process from one week to the next. That turns a chatbot into a staff member with a login. Staff members need a job description.

What actually happened

From the post by Jason Moore, VP of Product for Copilot Studio:

• Agent accounts. Each agent gets its own Microsoft 365 credentials. You can delegate to it in Teams or email, or @mention it in comments in Word, Excel and PowerPoint. It works with scoped permissions, not the credentials of the user or the maker who built it.
• Attribution. Work is attributed to the agent, so a process owner can see which actions the agent took and which a person took.
• Triggers. Through the GitHub Copilot harness, an agent can stay "always on" and start a cycle from an email or a schedule. No prompt needed.
• Business process memory. The agent carries preferences and process context into the next cycle. Makers steer what it keeps by instructions and by naming the authoritative records and policies.
• Admin controls. Admins can scope access and manage agent accounts in the Power Platform admin center. Microsoft says more access policies and cost and lifecycle controls are planned "in the coming months."
• Still coming. Agents that suggest their own improvements, and agents with their own browser-enabled cloud computer.

The post gives no pricing or general availability date. Today this is Frontier only.

Why it matters for your business

We have told clients for a year: give agents their own keys, never a borrowed human login. Microsoft just made that the default inside the suite most offices already pay for. Good.

The hard part moves to you. A triggered agent with memory runs every Tuesday whether anyone remembered it exists. Microsoft's own example is a finance agent that gathers forecasts, chases budget owners and briefs the review. People keep the decision. The agent does the prep and the follow-up. That split is correct, and it only holds if you write it down.

Before you enroll an agent account:

• Write its job description. Which process, which records count as the source of truth, what it may send, and who it reports to.
• Scope it like a new hire. One mailbox, the folders it needs, no tenant-wide read access.
• Audit the memory. Shared memory drifts. Read what the agent kept every month and delete the wrong lessons.
• Name an owner. Every agent account gets a human who answers for it, the same as a service account.

Sources: Microsoft Copilot Blog.