Between the 23 September and 6 October 2026 editions of the Microsoft 365 Copilot release notes, and public roadmap updates through to 14 October, Microsoft moved a cluster of named agents to Launched or Rolling out: the Sales Development Agent on Salesforce (rolling out, updated 12 October), the Employee Self-Service Agent in Microsoft 365 Copilot (Launched), Planner Agent chat and Planner in Copilot Chat (rolling out), the Dynamics 365 Business Central Payables Agent and agent-management updates (Launched for October), and the Teams organisation evaluation score for apps and agents (Launched, updated 14 October).
This note takes each on four lines: what it does, who it is for, what the roadmap says about prerequisites, and the one governance question Frontrow would settle before switching it on. Several entries say nothing about licence terms, and an agent that writes to a CRM or a finance ledger is a different risk class from one that summarises a meeting. The controls that apply across all of them are already at /insights/agent-365-what-it-governs-who-needs-it, /insights/copilot-agents-governance-billing-by-type and /insights/entra-agent-id-governing-ai-agent-identities.
Sales Development Agent on Salesforce (574105)
What it does. The roadmap entry, Rolling out for October 2026, says the Sales Development Agent (SDA) can now be used with an existing Salesforce CRM: it can access leads, manage prospect records, log sales activities, and keep qualification, disqualification and ownership changes connected to the CRM workflow, through Microsoft's Salesforce Model Context Protocol (MCP) server.
Who it is for. Sales teams on Salesforce rather than Dynamics 365, which in Frontrow's experience is the larger share of Australian mid-market businesses. The use cases in /insights/copilot-studio-agent-sales still hold.
Prerequisites. The entry sits under Microsoft Copilot (Microsoft 365) on Current Channel and does not state licence terms. Price it with your partner before a pilot rather than assuming it is inside an existing Copilot seat.
Governance question. This agent writes to the CRM. Decide, before anyone connects it, which identity those writes land under and how a sales manager audits them.
Employee Self-Service Agent in Microsoft 365 Copilot (487836)
What it does. The roadmap describes an agent that expedites answers to the most common workplace policy questions and takes action on key HR and IT tasks, connecting employees to authorised knowledge bases and HR and IT systems of record. The entry carries a November 2025 general availability month, was last updated on 1 September 2026, and shows Launched across web, desktop, iOS and Android, still tagged Preview and Targeted Release.
Who it is for. HR and IT teams fielding the same leave, policy and access questions by email. The build-it-yourself version is at /insights/copilot-studio-agent-hr.
Prerequisites. Not spelled out beyond placement under Microsoft 365 Copilot. The real prerequisite is content: the agent is only as accurate as the knowledge bases it is pointed at.
Governance question. An agent that answers policy questions from internal content inherits every oversharing mistake in that content. The 6 October notes also shipped a SharePoint Advanced Management report listing item-level permissions granted to the Everyone and Everyone except external users groups (roadmap 561038), which is the right pre-check.
Try it
Check what a self-service agent would find
Before pointing a policy-answering agent at SharePoint, run the oversharing check to see which sites and files are open wider than their owners think.
Score each dimension · 4 options
Is your tenant ready for Microsoft 365 Copilot?
Copilot is as smart as your tenant is tidy. Twelve quick questions — each mapped to a Microsoft-native capability that closes the gap. Takes about ten minutes.
- 01
Anonymous "anyone with the link" shares
External access
How does your tenant handle anonymous sharing links?
- 02
Tenant-wide / "Everyone except external" site sharing
Permissions hygiene
Do you have sites shared with "Everyone" or "Everyone except external users"?
- 03
External guest access hygiene
External access
How do you manage external guest users in Entra ID?
- 04
Site collection admin sprawl
Identity & privileged access
How tightly is SharePoint site collection admin access controlled?
- 05
Broken permission inheritance
Permissions hygiene
How much unique (non-inherited) permissioning exists across your sites?
- 06
Orphaned sites with no active owner
Permissions hygiene
How do you handle sites whose owner has left or gone inactive?
- 07
OneDrive personal sharing patterns
External access
Do staff share sensitive documents (HR, finance, contracts) from OneDrive?
- 08
Sensitivity label coverage
Content classification
How much of your content is classified with Microsoft Purview sensitivity labels?
- 09
Restricted SharePoint Search / content discovery controls
Content classification
Have you enabled Restricted SharePoint Search or equivalent discovery controls for sensitive sites?
- 10
Microsoft Teams / Groups public vs private hygiene
Permissions hygiene
How strict is the hygiene on Team / Microsoft 365 Group privacy settings?
- 11
Legacy classic SharePoint sites
Permissions hygiene
Do you still have classic (pre-modern) SharePoint sites in the tenant?
- 12
Access review cadence for sensitive sites + external access
Identity & privileged access
How often do you review access to sensitive sites and external user lists?
Planner Agent chat and Planner in Copilot Chat (567671, 516577)
What it does. The 23 September notes describe Planner Agent chat as built-in natural language Q&A, smart task discovery and in-plan task management, opened from the Copilot icon in Planner; roadmap 567671 tracks it for basic plans (Rolling out, Targeted Release). Roadmap 516577, also Rolling out, adds the other direction: creating Planner tasks and plans and querying Planner information from inside Microsoft 365 Copilot Chat. The 11 August notes had already extended Planner Agent itself, with task execution and status reporting, to all group-based plans including basic plans (roadmap 511820).
Who it is for. Any team that runs work in Planner. It is the lowest-risk item here.
Prerequisites. The 11 August note is explicit: Planner Agent in basic plans is for Microsoft 365 Copilot licensed users, with no plan upgrade required.
Governance question. The agent executes tasks on group plans, so whoever owns the Microsoft 365 group owns what the agent does there. Confirm group ownership is current.
Business Central Payables Agent and agent management (573380, 573370, 573363)
What it does. The Business Central October 2026 wave, Launched on the roadmap on 30 September, tightens the Payables Agent and the controls around every agent in the product. Roadmap 573380 improves purchase order matching by giving the agent an enriched PO Lines list with Line Amount and Expected Receipt Date, so it can match on value and timing rather than description and quantity alone, which Microsoft notes matters for service lines where quantity is often just one. The agent now also respects the Never block draft finalization setting on purchase orders, aligning with existing posting controls.
Around it: 573370 lets administrators assign additional permissions to agents when the agents request them; 573363 adds a task pane, openable from anywhere in Business Central, collecting suggestions, validations, follow-ups and draft documents from all agents; and 573364 shows avatars on list pages indicating whether a user, a system user or an AI agent created or last modified a record.
Who it is for. Finance teams on Business Central, and the accountants and order processors who will now see agent activity beside their own. The accounts payable use case is at /insights/copilot-studio-agent-finance.
Prerequisites. These ship inside Business Central, which is licensed separately from Microsoft 365. The roadmap entries state no additional licence for the agents; confirm with Frontrow or your Dynamics partner before assuming they are included.
Governance question. Item 573370 is the one to think about. Approving permissions on request is convenient, and it is also the exact mechanism by which an agent accumulates rights nobody designed. Write down who may approve an agent permission request, and review agent permission sets on the same cycle as user access reviews.
Teams organisation evaluation score for apps and agents (532720)
What it does. This is a control rather than an agent. Until now, admins reviewed trust data for Teams apps and agents manually in the Teams admin centre. Now they define the organisation's trust requirements once, and the system assesses each app and agent against them, producing an evaluation score and a detailed report showing which meet the standard and which need further review. The entry carries a February 2026 general availability month, is tagged Targeted Release, and was last updated, showing Launched, on 14 October 2026.
Who it is for. Anyone asked to approve a third-party agent in Teams with nothing better than the publisher's own compliance page to go on. No prerequisite is stated beyond Teams admin centre access.
Governance question. The score is only as good as the requirements entered. Set them deliberately, with the security lead in the room.
Not in this roundup
The Viva Engage Community Agent does not appear in the launched or rolling-out roadmap data Frontrow reviewed, so it is not treated as shipped. The Engage change that did ship, in the 25 August notes, is narrower: private community and event content is now a grounding source for Microsoft 365 Copilot, with users seeing only content they already have permission to access (roadmap 515144).
What it means for an Australian business
The pattern is that Microsoft's packaged agents are moving from reading data to writing it. SDA changes lead ownership; the Payables Agent finalises drafts within posting controls; Planner Agent executes tasks. The governance model most Australian businesses built for Copilot in 2025 assumed a read-only assistant inside a user's own permissions, and it needs one extension: a decision about which actions an agent may take, under whose identity, with what approval step. Whether that needs the Agent 365 control plane or Entra and Purview alone is the question /insights/agent-365-what-it-governs-who-needs-it answers.
On cost, none of these entries publishes a price and Frontrow will not guess one. Agents packaged inside a product licence (Planner, Business Central) carry their cost in that licence; anything extended through Copilot Studio or consumption billing can run away from a budget in an afternoon, and the diagnose-and-cap sequence at /insights/copilot-studio-bill-shock-diagnose-cap-spend applies there. For how the pieces combine into an operating model, see /insights/agentic-workforce-microsoft-365 and /insights/power-automate-copilot-agents-workflow.
What to do this month
- 1Check which of these agents is already reachable in the tenant. Targeted Release and Rolling out items arrive unevenly, so look rather than assume.
- 2Run the SharePoint Advanced Management report on Everyone and Everyone except external users permissions before any policy-answering agent is piloted.
- 3Write a one-page agent action policy: which agents may write to which systems, under which identity, and who approves permission requests.
- 4If sales runs Salesforce, scope an SDA pilot with pricing confirmed in writing, and agree how agent-made disqualifications and ownership changes get reviewed.
- 5Set the Teams organisation trust requirements deliberately, then let the evaluation score do the first pass on every new app and agent request.