COMPARISON
Microsoft Dynamics 365 Field Service is the FSM inside the Microsoft cloud: work orders, customer assets, agreements, inventory, the Schedule Board for the dispatcher and Resource Scheduling Optimization as the optional AI add-on, with Copilot, Power Automate, Teams and Outlook wired in. eLogii is the routing and optimization layer that runs alongside Dynamics 365 Field Service when the planning problem grows past what the Schedule Board and Resource Scheduling Optimization are designed to lead on. Two engines, six configurable modes, multi-day, multi-depot, recurring patterns, rule-based re-optimization, all callable over REST.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
Dynamics 365 Field Service and eLogii do different jobs in the same field-service stack. Dynamics 365 Field Service is the FSM: the system of record for the work order, the customer asset, the agreement, the inventory transaction and the booking. eLogii is the routing engine for operations where the optimizer needs to do the heavy lifting across multi-day, multi-depot and constraint-heavy plans, and where the dispatcher needs the engine to decide assignments rather than steer them on the Schedule Board.
The combined deployment pattern: Dynamics 365 Field Service stays the system of record for the work order, customer asset, agreement, inventory and the booking itself. eLogii reads work orders, requirement groups, bookable resources, vehicles, territories, customer assets and agreement-driven recurring templates from Dynamics 365 via the Web API, runs the optimization across the routing horizons the Schedule Board and Resource Scheduling Optimization are not designed to lead on, and writes optimized bookings and ETAs back. The technician opens Field Service Mobile on site; the route they take is the one eLogii planned. Dynamics 365 Field Service keeps the work-order lifecycle, asset record and inventory flow it owns end to end; eLogii owns the optimization decision layer.
Dynamics 365 Field Service is the Microsoft FSM. eLogii is the routing engine for the optimization-driven side of the problem. The table below isolates where each side leads.
| eLogii adds | Dynamics 365 Field Service today | |
|---|---|---|
| Optimizer-driven assignment under heavy constraint | Engine decides which resource takes which work order under skills, capacity, time-window, SLA and depot constraints, as the primary surface | Schedule Board is the dispatcher cockpit; Resource Scheduling Optimization adds AI-driven scheduling within configured scopes; tuned for the Dynamics 365 work-order model rather than constraint-heavy multi-depot dispatch |
| Multi-depot routing in one pass | Route across multiple depots, branches and home start locations as a single optimization input | Territory-based scheduling in Dynamics 365; cross-territory and cross-depot rebalancing as operator work in the Schedule Board |
| Multi-day, long-haul, full-month horizons | Plan a single day or an entire month in one run; multi-day routes with overnight stops | Multi-day bookings and Resource Scheduling Optimization scopes supported in the work-order record; not solved as a single multi-day optimization across crews and depots |
| Recurring service programs at scale | Task and route template groups: weekly, monthly, quarterly, bespoke cadences modeled as inputs to the optimizer | Agreements generate work orders against customer assets on a cadence; the cross-program optimization across reactive break-fix work is left to the scheduler |
| Two engines, six configurable modes | Default + Advanced engines, three assignment modes + three load-balancing modes, all REST-callable | Resource Scheduling Optimization runs as an AI add-on with configurable goals and scopes; not publicly documented as REST-callable optimization endpoints with operator-visible modes |
| Rule-based re-optimization the dispatcher can see | Operator-visible rules; live re-optimize while protecting locked SLAs and customer-confirmed slots | Reshuffle on exception is handled on the Schedule Board; optimization rules live inside Resource Scheduling Optimization goals and constraints |
| Slot booking co-pilot | Route-aware availability calculation: only slots that fit the current optimized plan, returned to your booking layer over REST | Customer Service Hub and Power Pages support self-service booking; route-aware availability is not the lead workflow |
Sources: Microsoft Learn: Dynamics 365 Field Service overview, Resource Scheduling Optimization overview, Schedule Board reference; eLogii optimization engines. Verified June 2026.
| eLogii | Dynamics 365 Field Service | |
|---|---|---|
| API style | REST, JSON over SSL, ApiKey authentication, predictable resource URLs | Dataverse Web API (OData v4) for every table, including work orders, bookable resources, requirements, customer assets and agreements; Power Automate connectors and Azure Service Bus / Event Grid integration patterns on top |
| API access | Included as part of the platform; documented at elogiiapidocs.apidog.io | Dataverse Web API available to every D365 tenant; API limits apply per Microsoft service-protection policy |
| Sandbox environment | Full API parity at api-sandbox.elogii.com | Sandbox environments in Power Platform admin center, with full Dynamics 365 parity for development and UAT |
| Bulk operations | POST /tasks/createOrUpdateMany handles hundreds of tasks per call | Dataverse Web API supports batch requests via $batch for multi-operation calls; per-table endpoints for individual reads/writes |
| Webhooks / streaming | Seven event types including Driver/Task Tracking Update with live GPS stream and Route ETAs Update | Microsoft webhooks, Power Automate triggers, Azure Service Bus and Event Grid for downstream subscribers; no productized live driver GPS stream from Field Service Mobile |
| Optimization callable via API | All six modes callable via REST; lock specific routes, manually reorder stops, re-run with new constraints | Resource Scheduling Optimization can be triggered programmatically against configured scopes; no public set of named modes (assignment vs. load-balancing) exposed as documented REST endpoints |
Sources: eLogii API documentation; Dataverse Web API overview; Dynamics 365 Field Service developer guide. Verified June 2026.
| eLogii | Dynamics 365 Field Service | |
|---|---|---|
| Role in the stack | The routing and optimization decision layer. Runs alongside an FSM, never replaces it. | The Microsoft FSM: work order, customer asset, agreement, inventory, booking, Schedule Board and Resource Scheduling Optimization. One product inside the Dynamics 365 family, alongside Customer Service, Sales and Business Central. |
| Where it shines | Operations where the optimizer needs to decide assignments under heavy constraints across days, depots and crews | Microsoft-anchored field-service operations that already run in Dynamics 365, Power Platform, Teams and Outlook, with the work-order, agreement and inventory model as the spine |
| Reference customers | J-Club, NHS, Belfast City Council, Vergo, Bristow & Sutor, Greenix, Porcelanosa, Brymec, Heatleys | Microsoft publishes customer stories across utilities, manufacturing, medical, telecom and facilities; representative names include G&J Pepsi-Cola Bottlers and Daikin Applied (US) |
| Ownership | Independent platform focused on routing and optimization | Microsoft |
| Security certifications | ISO 27001 + SOC 2 Type 2, publicly listed | Microsoft cloud compliance baseline: ISO 27001, SOC 1/2/3, FedRAMP, HIPAA, GDPR and the wider Microsoft Trust Center catalog |
| Typical implementation | 3 to 5 weeks including building the connector against the Dataverse Web API | Partner-led implementations typically run weeks to months; Schedule Board, Resource Scheduling Optimization and Connected Field Service rollouts often staged separately |
| Pricing model | Platform fee, banded by field staff/drivers/jobs per day/modules, from $3,000/mo. Composes with what Microsoft charges per user. | Microsoft publishes list pricing: USD 105 per user per month for the qualifying user, USD 30 per user per month for additional users, plus the Resource Scheduling Optimization add-on for tenants that license it. Field Service Contractor is a lower-cost SKU. |
| Customer review stance | 3 to 4× ROI within 6 months typical; fast time-to-value cited | G2 and TrustRadius reviewers praise the Microsoft platform depth, Power Platform extensibility and the Microsoft 365 surface; common review notes flag Schedule Board ramp time, Resource Scheduling Optimization configuration depth and the lift required to tune it for multi-depot constraint-heavy operations |
Sources: Microsoft Dynamics 365 Field Service product page, Dynamics 365 pricing, Resource Scheduling Optimization overview, Microsoft Customer Stories, G2 reviews, TrustRadius reviews. Verified June 2026.
Dynamics 365 Field Service’s scheduling is built around the work order and the bookable resource, surfaced on the Schedule Board, with Resource Scheduling Optimization as the licensed AI layer on top. What neither the Schedule Board nor Resource Scheduling Optimization positions as the lead capability is constraint-heavy optimization across multi-day, multi-technician and multi-depot operations in one solver run, recurring service programs at thousands of stops as a single optimization input, or a public REST surface for the optimizer itself with named assignment and load-balancing modes. eLogii’s optimizer covers exactly that side, callable over REST.
eLogii’s optimizer is built around two engines and six configurable modes, all callable via REST and exposed to the dispatcher as controls they can see and adjust.
Beyond the modes, eLogii ships the operational surface the Schedule Board isn’t designed to lead on: multi-day and long-haul routing (“plan a single day or an entire month in one run”), multi-depot (“route across multiple depots, branches, or home start locations in a single run”), recurring service patterns via task and route template groups (weekly, monthly, quarterly, bespoke cadences modeled as inputs to the optimizer, not as agreement-generated work orders to be hand-rebalanced), multi-technician crew jobs with skills, capacity and SLA constraints, and rule-based re-optimization the operator can see and steer.
If the dispatcher’s morning routine is “open the Schedule Board, confirm the booking, drag the work order to the resource in the right territory, let Resource Scheduling Optimization clean up the rest”, Dynamics 365 Field Service is the right tool and adding eLogii would be over-engineering. If the dispatcher’s morning routine is “run the optimizer against today’s open work orders across three depots, balance against next week’s agreement-generated maintenance book, protect the SLA-locked priority bookings, route around the resource who’s off Tuesday”, the Schedule Board is being asked to do a job it wasn’t built for and Resource Scheduling Optimization is being stretched past its sweet spot. eLogii covers that side via REST API; Dynamics 365 Field Service stays in place for the work order, the customer asset, the agreement and the inventory.
eLogii has fundamentally transformed the way we operate. The productivity gains, enhanced visibility, and ability to scale confidently have been game-changing. The rollout was smooth, the support exceptional, and the results speak for themselves.
Paul Clark, Co-Chief Operating Officer, Richburns · nationwide UK field services team
Dynamics 365 Field Service covers the Microsoft-anchored field-service workflow well across utilities, manufacturing, medical, telecom and facilities. The signal that the routing problem has grown past what the Schedule Board and Resource Scheduling Optimization were designed for tends to be operational rather than headcount-based. Three patterns show up:
Where any of these is the dominant shape of the work, eLogii is the routing layer. Where none of them is, the Schedule Board with or without Resource Scheduling Optimization is the right tool and adding eLogii is over-engineering. The honest answer for many Dynamics 365 Field Service customers is “you don’t need eLogii.” The honest answer for the operations where the optimizer is the bottleneck is that eLogii is built for exactly that.
Dynamics 365 Field Service continues to do the Microsoft FSM work it’s built for. The difference shows up where the routing problem used to dominate. Brymec lifted productivity 30% and routing efficiency 20% on eLogii. ATS Building Products improved deliveries per route by ~98%. Porcelanosa runs eLogii with 95%+ ETA accuracy on daily distribution. Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. These are operational outcomes that come from moving the assignment problem from the dispatcher’s morning into the optimizer:
The typical Microsoft-anchored field service stack: a Microsoft FSM for the work order, customer asset, agreement and inventory (Dynamics 365 Field Service), an ERP for finance and customer master data (Dynamics 365 Business Central, Dynamics 365 Finance & Operations, SAP, NetSuite), telematics for the vehicles (Samsara, Geotab, TomTom), an IoT layer for condition-based service (Connected Field Service, Azure IoT Hub), Teams and Outlook on top, and a routing decision layer alongside the Schedule Board for operations where the optimizer is the bottleneck.
eLogii is built for that shape. It plugs into Dynamics 365 Field Service, leaving the work-order lifecycle, customer asset record, agreements, inventory and Field Service Mobile where they already are. The technician opens Field Service Mobile on site; eLogii plans the route they take to get there, surfaces the live ETAs, picks up GPS, and pushes completion back into Dynamics 365. The common patterns:
What makes the stack pattern straightforward:
api-sandbox.elogii.com so integration work can run in parallel with the existing Dynamics 365 / ERP rollout.POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.Microsoft exposes the Dataverse Web API to every Dynamics 365 tenant, with Power Automate, Azure Service Bus and Event Grid available for downstream subscribers. The two APIs combine cleanly: eLogii calls the Dataverse Web API to read work orders, bookable resources, vehicles, territories, customer assets and agreement-driven recurring templates, runs the optimization across the routing horizons the Schedule Board and Resource Scheduling Optimization are not designed to lead on, and writes optimized bookings and ETAs back. Field Service Mobile picks up the planned route; completion data flows back into Dynamics 365 for the work-order record, customer asset history, inventory and reporting.
Both sides expose REST APIs. Microsoft’s is the integration surface for the Dynamics 365 data model, reachable on every Dynamics 365 tenant through the Web API, Power Automate connectors and Azure messaging. eLogii’s is the integration surface for a routing and optimization engine, with the optimizer itself callable as REST endpoints.
api-sandbox.elogii.com, full parity with production at api-35.elogii.com.POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.For an integration team, the typical pattern when Dynamics 365 Field Service and eLogii are both in the stack: Dynamics 365 Field Service owns the system of record for work orders, customer assets, agreements, inventory and bookable resources; eLogii reads work orders/requirements/resources/vehicles/territories from Dynamics 365 over the Web API, runs the optimization across the horizons the Schedule Board and Resource Scheduling Optimization are not designed for, writes optimized bookings and ETAs back; Field Service Mobile shows the route to the technician; completion writes back to Dynamics 365 for the work-order record, customer asset history and inventory.
eLogii runs alongside Dynamics 365 Field Service; it does not replace what you’re paying Microsoft today. The question is what eLogii adds on top, and what it costs to add it.
eLogii pricing starts from $3,000 per month as a platform fee, banded by field staff, drivers, jobs per day and the modules required. Each band includes a quota; cost steps up when the operation crosses a band, not when you add an individual seat. Customers typically report 3 to 4× return on investment within 6 months, and combined Dynamics 365 Field Service + eLogii rollouts complete in 3 to 5 weeks including the connector build.
Microsoft publishes list pricing for Dynamics 365 Field Service: USD 105 per user per month for the qualifying user, USD 30 per user per month for additional users on a qualifying tenant, plus the Resource Scheduling Optimization add-on for tenants that license it. Field Service Contractor is a lower-cost SKU for occasional crew members. The pricing models compose: Microsoft charges per user for the FSM and Resource Scheduling Optimization, eLogii charges a platform fee for the routing layer. There is no per-seat cost from eLogii.
30-minute custom simulation with your real Dynamics 365 work orders, customer assets and field-service plans. Projected savings in drive time, fuel and dispatcher hours from adding eLogii on top.
We’d never go back to the way we were planning before. eLogii is the backbone as well as the brain of our planning operations, translating actively to our bottom line.
Jord Van Dijk, IT Director, J-Club · 9,000+ stores routed on eLogii
Three steps for Dynamics 365 Field Service customers whose dispatch problem has grown past what the Schedule Board and Resource Scheduling Optimization are designed to solve. Dynamics 365 Field Service stays in place for the Microsoft FSM; eLogii layers on as the routing engine.
Bookable resources, vehicles, territories, customers, customer assets, work orders, requirement groups, agreements and recurring service templates sync from Dynamics 365 via the Web API. Resource home locations, characteristics and skill sets, customer accounts and asset hierarchies map to eLogii drivers, depots and constraints. Dynamics 365 agreements become eLogii task and route template groups. Read-write integration designed so Dynamics 365 Field Service stays the system of record for the work order.
Weeks 1–2Custom data simulation against your historical Dynamics 365 work orders so you can validate the modeling and project savings before go-live. Side-by-side comparison: what the Schedule Board (with or without Resource Scheduling Optimization) produces today vs. what eLogii’s optimizer produces with multi-day, multi-depot or recurring-program optimization on the same data.
Weeks 2–3Start with the business unit where the Schedule Board is leaking the most: usually a multi-depot regional service book, a large agreement-driven maintenance program, or the part of the operation where the dispatcher is hand-rebalancing every morning. Run it on eLogii, prove the lift on real work orders, then expand. Dynamics 365 Field Service keeps owning the work order, customer asset, agreement and inventory in parallel. Most teams complete the transition in 3 to 5 weeks total including the connector build.
Weeks 3–5Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. Multi-country rollouts deploy in weeks, not quarters.
Dynamics 365 Field Service’s dispatch surface is excellent at Dynamics 365 Field Service. Four patterns where the optimization decision layer alongside it is the bottleneck, each with its own deep dive:
Resource Scheduling Optimization is the licensed AI scheduler on top of the Schedule Board. The constraint-based assignment engine that decides under skills, capacity, SLAs and depots as a single problem is its own decision layer.
Dynamics 365 Field Service models territory cleanly. Regional service networks need cross-territory rebalancing as a single optimization input. eLogii covers it.
Dynamics 365 Field Service generates work orders from agreements against customer assets. Optimizing the generated stops at scale, against reactive break-fix, needs an engine.
Dynamics 365 Field Service has a customer self-service portal and Power Pages. Route-aware availability that respects the current optimized plan is its own layer.
A single overview of the four patterns where the Schedule Board reaches its design ceiling, plus diagnostic signals for spotting them.
Complement, in most cases. Microsoft Dynamics 365 Field Service is the FSM in the Microsoft cloud: work orders, customer assets, agreements, inventory, the Schedule Board for the dispatcher and Resource Scheduling Optimization as the optional AI add-on, with Copilot, Power Automate, Teams and Outlook wired in. eLogii is the routing and optimization layer that runs alongside Dynamics 365 Field Service when the planning problem starts to dominate: multi-depot field-service operations, dense same-day plans with hundreds of competing time-window constraints, optimizer-driven assignment across crews, recurring service programs at thousands of stops. Dynamics 365 Field Service stays the system of record for the work order, customer asset, agreement and inventory. Integration runs over the Dataverse Web API on one side and eLogii’s REST API on the other.
When the Schedule Board stops being the right place to solve the optimization problem and Resource Scheduling Optimization is not closing the gap. The Schedule Board is a powerful dispatcher cockpit for assignment, drag-and-drop and exception handling on top of Microsoft Dynamics 365, and Resource Scheduling Optimization adds AI-driven booking and optimization as a licensed add-on. Both are valid for the core work-order lifecycle. eLogii layers on when the operation needs constraint-aware assignment across multi-day, multi-depot and recurring patterns in one optimization run, programmatic re-optimization with operator-visible rules, and slot booking that respects the current optimized plan.
Yes at the FSM-workflow level. Dynamics 365 Field Service supports requirement groups for multi-resource bookings, multi-day work orders, agreements and territory-based scheduling in Dynamics 365. Resource Scheduling Optimization handles AI-driven scheduling within configured scopes. What neither the Schedule Board nor Resource Scheduling Optimization positions as the lead capability is constraint-heavy optimization across multi-day plans and multi-depot rebalancing as a single optimization input, recurring service programs at thousands of stops in one solver run, or operator-visible rule-based re-optimization callable as a public REST surface. That’s where eLogii’s two engines and six configurable modes add depth, with Dynamics 365 Field Service staying the system of record for the work order, customer asset, agreement and inventory.
Integration runs over the Dataverse Web API (OData v4) and the Power Platform connectors for Dynamics 365. eLogii’s REST API has 70+ endpoints, ApiKey auth, a full-parity sandbox at api-sandbox.elogii.com and seven webhook events including live driver GPS and Route ETAs Update. Dynamics 365 Field Service exposes its data model through the Dataverse Web API, Power Automate, custom connectors and Azure Service Bus / Event Grid integration patterns. The typical pattern, Typically: eLogii reads work orders, requirement groups, bookable resources, vehicles, territories, customer assets and agreement-driven recurring templates from Dynamics 365; runs the optimization across the routing horizons the Schedule Board and Resource Scheduling Optimization are not designed to lead on; writes optimized bookings and ETAs back. Completion writes back to Dynamics 365 Field Service for the work-order record, customer asset history, inventory and reporting.
Microsoft publishes list pricing. Dynamics 365 Field Service is USD 105 per user per month for the qualifying user and USD 30 per user per month for additional users on a qualifying tenant. Resource Scheduling Optimization is a separately licensed add-on; tenants without it run on the Schedule Board only. Field Service Contractor is a lower-cost SKU for occasional crew members. eLogii is a platform fee, banded by field staff, drivers, jobs per day and modules, from USD 3,000 per month. The pricing models compose: Microsoft charges per user for the FSM and Resource Scheduling Optimization, eLogii charges a platform fee for the routing layer. Customers typically report 3 to 4× return on investment within 6 months on eLogii.
Typically 3 to 5 weeks from kickoff to a phased go-live, including building the custom connector against the Dataverse Web API. eLogii reads work orders, requirement groups, bookable resources, vehicles, territories, customer assets and agreement-driven recurring templates from Dynamics 365 Field Service; routes, ETAs and completion data flow back. Most teams start with the business unit where the Schedule Board is leaking the most: usually a multi-depot regional field-service book, a recurring service program at scale, or the part of the operation where the dispatcher is hand-rebalancing every morning. Dynamics 365 Field Service stays in place for everything else.
Three reasons. First, the Schedule Board and Resource Scheduling Optimization were built to assign work to bookable resources against the Dynamics 365 work-order model. Once the operation needs constraint-heavy multi-day, multi-depot optimization as the daily input, that surface is not the tool. Second, eLogii customers at scale report operational outcomes that go past what FSM scheduling alone delivers: Brymec 30% productivity and 20% routing efficiency; ATS Building Products 98% improvement in deliveries per route; Porcelanosa 60%+ planning time cut; Unimasters 50% less planning time and 49% fewer service calls. Third, eLogii exposes the optimizer itself as REST endpoints with seven webhook events, so the routing layer integrates cleanly into the Microsoft stack via Power Automate and Azure messaging.
Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo Pest Management (400 technicians, Tyro Group), Bristow & Sutor (200+ enforcement agents, 200,000+ case visits routed annually), Porcelanosa, Caldic and Berkmann Wine Cellars. ISO 27001 and SOC 2 Type 2 certified.
Last updated: June 2026. Information about Microsoft Dynamics 365 Field Service is drawn from Microsoft Dynamics 365 Field Service product page, Microsoft Learn: Dynamics 365 Field Service overview, Resource Scheduling Optimization overview, Schedule Board reference, Dataverse Web API overview, Microsoft Dynamics 365 pricing, Microsoft Customer Stories, and G2 and TrustRadius reviews. Information about eLogii is drawn from elogii.com and the eLogii API documentation.
Custom simulation
A 30-minute working session with our solutions team. We take a sample of your real jobs, depots, vehicles and SLAs, run them through the eLogii engine, and show you the projected delta against how you plan today. No slides, no generic benchmarks.