Scheduling Operations Agent

What it does

An AI agent that proposes optimised technician schedules, either interactively for a handful of resources from the schedule board or Copilot pane, or in asynchronous batch runs against a defined scope. A dispatcher reviews the suggestion and applies or discards it. It's in preview.

Key facts

Preview. Not supported for production use, and the feature set is still moving.
Needs Field Service 8.8.133.214 or newer and Universal Resource Scheduling 3.12.149.15 or newer, with location and map settings turned on.
Enabled in the Field Service app under Resources > Scheduling Parameters > Resource Scheduling > Agents, via the Scheduling Operations Agent (Preview) toggle.
Two additive security roles: Scheduling Operations Agent Administrator (create and edit scopes, goals and plans) and Scheduling Operations Agent User (run optimisations, view results). Users also need a normal dispatcher role such as Field Service - Dispatcher for the underlying scheduling tables.
It consumes Copilot Credits, billed either from prepaid Copilot message packs assigned in the Power Platform admin centre or pay-as-you-go against a linked Azure subscription. Prepaid capacity is drawn down first. Message consumption scales with the number of resources in the run.
Interactive limits: up to 5 resources, up to 120 jobs (existing bookings plus open requirements), and any 72-hour window in the future.
Batch limits: up to 50 resources, up to 4,000 jobs, up to 2,000 bookings per resource, and a range of up to 14 days.
Batch runs are configured as Scope (which resources and requirements), Goal (objectives and constraints) and Plan (the combination of the two). Interactive runs pick a goal from the settings panel — Maximise Utilisation or Front-load High-Priority Work.
Behaviour is driven by two data settings people forget: Optimization Method on each booking status (Optimize, Do Not Move, Ignore — defaulting to Do Not Move) and Priority Value 1–100 on priorities. The agent ignores the old Level of Importance field entirely.
Bookable resources must have Display on schedule board set to Yes to be considered.
It does not support Crew, Equipment, Pool or Facility resource types, requirement groups, multiday requirements, requirement fulfilment preferences, or RSO-specific fields. Maximum three breaks per working day — four or more throws an error.
Available in the same Azure regions as Field Service, excluding Azure Government and China. Online only. Prompt detection has been tested in English.
Results expire: older than 72 hours, or past the start of their time range, and you have to re-run.

When to use / skip

This is for the dispatcher's bad afternoon — a cancellation to backfill, a job that has overrun and pushed everything right, an urgent call that needs squeezing in. Interactive optimisation over five resources and 72 hours fits that shape well, and the review-then-apply flow means the dispatcher stays in charge.

It is not a replacement for Resource Scheduling Optimization. RSO is GA, it's licensed as an add-in, it runs at proper scale overnight, and it handles resource types and scenarios the agent flatly doesn't. If a client's requirement is "optimise 400 engineers every night", the answer is still RSO. The agent's batch mode tops out at 50 resources, and that ceiling decides most conversations before any other consideration.

Skip it for now on any project that can't absorb preview risk, that uses crews or facilities meaningfully, that has multiday requirements, or that has no appetite for a consumption-based cost line. And skip it if the client's booking statuses and priority values have never been curated — the agent will produce nonsense from bad configuration data and the client will blame the AI.

Configuration decisions

Interactive only, batch only, or both — and if batch, who owns the scopes, goals and plans as living configuration rather than a one-off setup task.
The optimisation method assigned to every booking status. Getting Scheduled and Committed onto Optimize while keeping in-progress and customer-committed work on Do Not Move is the single most consequential decision here.
The priority value scheme, 1–100, and whether the existing priority records need rebuilding because Level of Importance is now ignored.
Which objectives carry weight in each goal, and whether the client genuinely wants travel minimised over priority coverage or the other way round.
Whether to buy prepaid Copilot message packs or run pay-as-you-go, and who watches consumption.
Which security roles go to which dispatchers, and whether the Scheduling Operations Agent Team needs additional roles to reach custom tables or columns protected by field security profiles.

Gotchas

The agent runs as a team identity. If the client uses custom tables or column-level security, the Scheduling Operations Agent Team needs matching roles or optimisations quietly return worse results with no obvious error.
Booking statuses default to Do Not Move when Optimization Method is unset. A first run that "does nothing" is almost always this.
Level of Importance is ignored. Clients who spent a previous project tuning it will need to redo that work in Priority Value.
Truncation is silent-ish. Exceed the limits and the agent drops lower-priority records — open requirements first — and tells you records were truncated rather than refusing to run.
Cost scales with resources per run, so an enthusiastic dispatcher running batch plans repeatedly is a budget event. Set capacity alerts early.
Suggested results expire after 72 hours or once their time range starts, so a suggestion left over lunch may need re-running.
Preview status means no production support. Do not put it on the critical path of a go-live.

Consultant notes

Frame it to the client as a dispatcher assistant, not automation. The human approval step is the feature, and it is also the answer to the governance question they're about to ask.
Demo interactive optimisation with a real overrun scenario. Batch mode demos badly and its limits invite the wrong comparison with RSO.
Do the booking status and priority data work before the first demo. Nothing kills confidence faster than an optimisation that returns the same schedule.
Get the Copilot Credits conversation done with whoever owns the tenant budget, in the same meeting where you agree the pilot scope.
Before any pilot, confirm the client's resource types. Crews and facilities are common in maintenance-heavy estates and are simply out of scope today.

Worth revisiting when the agent reaches general availability, or when the 50-resource batch ceiling moves.