Microsoft's AI agents get mailboxes and managers: NZ checks

By DataForge team21 November 20265 min read

At Ignite 2026, Microsoft gave its AI agents their own logins, mailboxes and named human managers. NZ Microsoft 365 tenants need rules in place first.

What Microsoft announced at Ignite 2026

Microsoft used Ignite (17 to 20 November) to make some of its AI agents look much more like staff accounts. In an 18 November post on what's new in Foundry Agent Service, Microsoft's Foundry team says supported hosted agents now get their own Entra Agent ID, an email address, Teams presence and a place in the org chart. Foundry is also being connected to Microsoft 365 Resources for Agents, which gives each supported agent its own mailbox, calendar and OneDrive storage. Microsoft says these features will reach supported agents across its product range, with admins controlling access through Entra and Agent 365. The post gives no release dates and doesn't mention licensing.

The Copilot side moved the same way. Microsoft's Ignite Book of News calls Autopilot its "first enterprise-grade long-running personal productivity agent." Autopilot is rolling out through Microsoft's Frontier early-access programme. Each Autopilot sits in the customer's tenant with its own identity, memory and tool access, and colleagues can @mention a person's Autopilot in Teams chats. The Book of News also says every action an Autopilot takes, including actions taken for a user, is recorded against the agent's own ID.

The Agent 365 Ignite update from 17 November fills in the identity plumbing. Entra Agent ID now covers Autopilot in preview. Agents connected from Salesforce Agentforce, ServiceNow, SAP, UiPath, Snowflake and several other platforms get an Entra Agent ID automatically, and that rollout finishes in December. Conditional Access can now apply separate policies to an agent acting on a user's behalf, distinct from the user's own policies. A new Action center, due in preview in December, will show agents that have no owner or have gone inactive.

A WindowsForum guide to Foundry autopilots published on 19 November summarises Microsoft's setup documentation, and it covers the commercial detail the announcements leave out. To join the preview, a tenant has to be enrolled in Frontier and hold at least one Microsoft 365 Copilot or Agent 365 licence. Eligible tenants get a 25-seat preview subscription, and every autopilot instance uses one seat because it creates an agent user account. Whoever hires an instance in Teams becomes its manager and decides which sites and projects it can reach. Offboarding deletes the account and ends its access straight away. The guide also notes that giving an agent a mailbox doesn't, on its own, let the agent send mail.

Why a separate account changes the controls

Until now, most agents in Microsoft 365 borrowed the identity of the person using them. When an agent edited a file or drafted an email, the audit log showed the employee's name. An agent with its own account shows up as itself in sign-in logs, mail traces and file access records. Investigations get easier, because you can tell what the person did from what the agent did on their behalf.

The cost of that clarity is a new type of account that needs looking after. An agent user account has a mailbox other people can write to, a OneDrive that fills up with working files, and permissions that grow whenever its manager adds another project. Your joiner, mover and leaver process probably assumes every account belongs to a person with an HR record. Agent accounts have a manager instead, and managers change roles and leave. Microsoft building an Action center to find ownerless agents tells you orphaned agents are an expected problem.

Licensing works per instance. On the preview terms, every hired autopilot uses a seat, so ten staff each hiring a workstream agent means ten seats. Microsoft hasn't published what those agent accounts will cost outside the preview, so nobody can budget firmly yet.

What it means for NZ Microsoft 365 shops

Plenty of NZ organisations run Microsoft 365 with an IT team of one to five people, often backed by an MSP. In those tenants, identity tidy-up usually happens after something breaks. Agent accounts will turn up over the next few months through several routes: Frontier previews, Copilot Studio builds, and third-party platforms such as ServiceNow or Salesforce that now register their agents in Entra automatically. If your organisation uses any of those platforms, agent identities could appear in your directory without anyone in-house creating them.

Customer-facing work raises a separate question. An agent with its own mailbox can email suppliers and customers directly. Before you allow that, decide how the agent signs its emails, whether recipients are told they're dealing with an agent, and who reads the replies when the agent can't deal with them.

Data location hasn't been settled either. The WindowsForum guide lists data residency as one of the areas still needing attention, and Microsoft hasn't said where an autopilot's memory is stored for tenants outside the EU and US. If your privacy commitments to customers name where their data is held, get that answer from Microsoft or your licensing partner in writing before anything sensitive reaches an agent.

None of this means you should wait for general availability. Running a small preview with clear limits will teach your team more than reading the launch posts. Our AI agents page sets out how we approach agent design, and the ownership questions belong in your wider AI governance work.

Practical next steps

  • Run an Entra report of existing agent identities now, before the December rollout for connected platforms finishes, so you have a baseline to compare against.
  • Add agent accounts to your joiner, mover and leaver process, with a rule that a manager must name a replacement owner before leaving or changing roles.
  • Decide who may hire an autopilot during the preview, and cap seat use below the 25 seats in the preview subscription so you can see what usage looks like.
  • Write a Conditional Access policy for agents acting for users, and set it to block access from unmanaged devices and to high-risk apps until you've tested it.
  • Keep send-as rights and external email off by default, and grant them per agent with a named reviewer for outbound mail.
  • Get Microsoft or your licensing partner to put in writing where agent memory and OneDrive data are stored for NZ tenants, and what agent accounts will cost after the preview.
  • Track the Action center preview in December and schedule a monthly review of ownerless and inactive agents.

Microsoft has shipped the identity features before the commercial terms and data location details. Firms that put ownership and access rules in place during the preview will be ready when pricing and data residency are published.

Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.

Get my free assessment How we help
Get new articles by RSS