Dynamics 365 Field Service Adds Usage-Based and Sequenced Maintenance Plans
Microsoft's AI at Work roadmap entry 571665, titled "Plan asset maintenance using time, actual usage, and service sequences," names Dynamics 365 Field Service as the product. It lists Android, Desktop, iOS and Web as platforms and the Worldwide (Standard Multi-Tenant) cloud as the only instance. Both a Preview ring and a General Availability ring are listed. No government or sovereign cloud instances appear on the entry, so organizations in those environments should not assume they are covered.
The roadmap describes three scheduling approaches that sit together in a single maintenance plan:
- Usage-based intervals are tied to a meter on one specific asset. Microsoft's examples are an oil change every 150 operating hours, or an inspection after a set number of miles, cycles or units produced.
- Calendar recurrence can be used alone or combined with a usage rule. In a combined rule, maintenance starts when either the time threshold or the usage threshold is reached, whichever happens first.
- Sequential programs move through different activities at different points in the cycle, such as inspections, then minor services, then major services, then overhauls, instead of repeating the same job every time.
According to Microsoft, the plan keeps checking its intervals against the asset's dates, its recorded meter usage and which step of the sequence was completed last. That tells it which activity is due next. When a threshold is reached, the plan creates a maintenance requirement, and that requirement drives work-order generation further down the line. Microsoft presents this as one place to manage calendar-based, usage-based, whichever-comes-first and multi-step strategies.
Why Meter Readings Matter More Than the Calendar
Field Service already supports preventive maintenance. Microsoft's product overview calls it an "agreement-based" model: recurring maintenance runs through agreements, and the system generates work orders at predefined intervals. The same overview separates this from predictive, IoT-driven service, where connected devices raise alerts or create work orders through Connected Field Service. The new capability fits between the two. It is still planned maintenance, but the interval can follow how hard the equipment actually works.
The roadmap spells out the problem it is meant to fix. A fixed calendar can over-service lightly used equipment. It can also let heavily used equipment run past its required interval. Tying the trigger to meter readings means work is driven by operating hours, mileage, cycles, production counts or another tracked measure, not an estimated calendar gap.
The whichever-comes-first rule covers a common real-world need. Many service obligations set both a usage limit and a maximum time between visits. Machines that sit idle still need attention at least once in a while. The roadmap frames combined scheduling as a way to follow manufacturer guidance, internal reliability standards and contractual maintenance commitments more consistently. Microsoft states these benefits but has published no figures on cost or downtime for this feature.
Sequencing solves a different problem. In a flat recurring schedule, every interval produces the same job. A sequenced program can make the 500-hour visit an inspection and the 2,000-hour visit an overhaul. The plan remembers where the asset sits in the cycle, so a planner no longer has to keep that in their head.
A Related Release-Plan Entry Adds Detail on Triggers and IoT Feeds
Microsoft has described very similar functionality before. A Field Service entry in the 2026 release wave 1 plan on Microsoft Learn, titled "Predict asset service dates by usage or calendar," covers the same idea. It is not confirmed to be the same feature as roadmap item 571665. The Learn entry says customers can service assets based on actual usage rather than a fixed calendar, which means assets that are used less get serviced less. That entry goes into much more detail than the roadmap text.
It describes four ways of deciding when an activity is due. Relative triggers are based on how much has changed since the last service (for example, every 500 hours of use or every 90 days since the last visit). Absolute triggers are based on fixed milestones from when the asset first went into service (for example, at 1,000 hours and again at 2,000 hours). Whatever Comes First uses both a usage-based rule and a calendar rule and picks whichever date arrives sooner.
The Learn entry also adds active windows. Each maintenance activity can also have an active window—for example, "only apply this between 500 and 5,000 hours" or "only during the first two years." Once an activity moves outside its active window, it stops generating work orders automatically. Windows like these are one way a sequenced program could hand off from early-life inspections to later overhauls. The roadmap entry does not say whether 571665 uses the same mechanism.
On recalculation, the Learn page says due dates recalculate whenever conditions change: you edit the plan, time passes, or new service meter unit (SMU) readings are logged. It adds that connected or IoT devices that write usage data directly to the asset's service meter log automatically feed into maintenance plans and keep projected due dates current without manual intervention. Planners can also override the calculated value at any time. And the feature isn't enabled automatically. Someone has to create and configure maintenance plans before anything happens.
Treat all of this as Microsoft's description of a related planned capability, not as confirmed behavior for roadmap item 571665. The roadmap text mentions meter readings "recorded for the individual asset" but does not say how readings arrive, whether IoT feeds are supported, or how missing or corrected readings are handled.
Two Microsoft Timelines for One Maintenance Idea
The timing is confusing. Roadmap entry 571665 gives October 2026 for preview and February 2027 for general availability. The Learn entry sits in the 2026 release wave 1 plan, which Microsoft says covers features planned to release from April through September 2026. Microsoft's public material does not explain whether the roadmap item replaces the release-plan entry, extends it, or is a separate feature with overlapping capabilities.
One likely reason for the overlap is a change in how Microsoft publishes plans. The Field Service release-plan pages now carry a notice that Release Plans stop being published in September 2026. New Dynamics 365, Power Platform and Dataverse capabilities go to the AI at Work roadmap from that month, and existing release plans stay online for historical reference. Roadmap entry 571665 appeared on September 23, 2026, right in that transition. For anyone planning around this feature, the most recent dated record is the roadmap entry, and its dates are the ones to plan against.
Those dates are estimates. Microsoft's roadmap says it gives estimated release dates, that all information may change, and that entries are removed once a feature becomes generally available, is cancelled, or is postponed. A Preview ring in October 2026 means early access for evaluation, not a production-ready release.
Where Field Service Planners Should Expect the Real Work
Configuring intervals will probably be the easy part. The harder work is data discipline. Every usage-based trigger depends on readings recorded against the correct asset and meter, at a pace that keeps up with actual use. A meter updated once a quarter produces due points that are always stale. A reading logged against the wrong asset can trigger service on one machine and silently delay it on another.
Not much has been published yet. The roadmap entry lists sample meter types but no full list. It gives no setup steps, no detail on how sequences are configured, no limits, and nothing on licensing. It also doesn't say exactly how the maintenance requirement turns into a work order, or how that fits with the agreement-based recurring work orders many Field Service customers already run. Microsoft Learn documents a separate Dynamics 365 Supply Chain Management Asset Management feature with time and counter plan lines and a "maintenance sequence" concept. That is a different product, and its setup steps should not be assumed to carry over to Field Service.
The handoff also stops at the requirement. The roadmap says the plan produces the requirement that drives work-order generation. It does not promise that a technician will be assigned, parts will be available, or the visit will be booked. Those still depend on the existing Field Service scheduling tools, such as the schedule board and Resource Scheduling Optimization.
What this means for you
Field Service administrators and service planners on the worldwide commercial cloud should use the time before the October 2026 preview to get their asset and meter data ready. They should not change any production maintenance processes yet. Teams whose maintenance is already correctly driven by the calendar, or by IoT alerts through Connected Field Service, can wait for general availability and for detailed documentation.
- Roadmap item 571665 is in development. Microsoft estimates preview in October 2026 and general availability in February 2027, and those dates can move.
- Only the Worldwide (Standard Multi-Tenant) cloud is listed, so government-cloud customers should not assume they are covered.
- Check that each serviceable asset has the right meters defined and that readings are logged often enough to reflect real use. Usage-based triggers are only as good as that data.
- Collect the manufacturer and contract intervals that set both a usage limit and a time limit. Those are the natural first candidates for whichever-comes-first rules.
- Write down multi-stage service programs, such as inspection, minor service, major service and overhaul, so they are ready to model as sequences once preview opens.
- Don't assume IoT readings will feed these plans automatically, or that existing agreements will convert to the new plans. Microsoft has described IoT feeds only for the related release-plan feature, not for this roadmap item.
In Field Service today, preventive maintenance mostly runs on fixed recurring intervals. Microsoft's roadmap points toward plans that track each asset's hours, miles or cycles and move through a proper service program, and it names a concrete path: preview in October 2026, general availability targeted for February 2027. Organizations that clean up their meter data before then will be able to test the new triggers with real asset history once preview opens, instead of starting from empty or unreliable readings.