Last updated: November 19, 2026
By ZapAI Team
The Dynamics 365 Field Service mobile app is where technicians actually live, so a rollout succeeds or fails on the phone. Our Dynamics 365 Field Service consultants set it up for mid-market US service teams, and this guide covers licensing, the offline profile, the technician’s day, Copilot on mobile, Teams and Outlook, Remote Assist, Intune and a rollout plan, checked against Microsoft Learn on November 19, 2026.
The Dynamics 365 Field Service mobile app is a model-driven Power Apps app for iOS, Android and Windows. It’s included in the Field Service license, and an admin-built offline profile decides which bookings and work orders sync to each device.
Picture a hypothetical technician in a basement mechanical room. No signal. The work order won’t open, the inspection form spins, and the customer is standing right there waiting for a signature. He takes a photo with his personal camera. He promises to “close it out tonight.” Sound familiar?
That evening never goes well. Our Dynamics 365 Field Service guide covers the product, plans and fit at a high level. This post stays on the device in the technician’s hand, because that’s where adoption is won or quietly lost.
What Is the Dynamics 365 Field Service Mobile App in 2026?
It’s a model-driven app built on Power Platform, not a separate native product. Microsoft’s mobile app overview, updated October 29, 2026, lists Apple iOS, Google Android and Windows 10 or later, and says the app comes with your Field Service license at no extra charge.
Since it’s model-driven, you customize it like any other Dataverse app. Forms, views, business rules and the sitemap all apply. If that distinction is new, our canvas vs model-driven apps guide explains why Microsoft chose this route for technicians.
Two experiences ship inside the same app today.
- The classic Unified Interface experience, which supports offline-first mode.
- A refreshed mobile experience with an agenda view, swipe actions and Copilot.
Here’s the catch nobody puts on a slide. Per Microsoft’s mobile setup guide, the refreshed experience doesn’t support offline mode, so users enabled for offline don’t see it and fall back to Unified Interface, and it isn’t available in the Windows app either. You pick per user. Offline or the new agenda. Not both, for now.
Older Resco-based apps are long gone. The Xamarin Field Service Mobile app was deprecated on June 30, 2022, according to the Field Service deprecations page.
Which Licenses Do Technicians Need?
Every technician needs a Field Service license or a Field Service Contractor license. Microsoft’s users, licenses and security roles page, updated November 11, 2026, lists exactly those two types, and it recommends Microsoft Entra B2B collaboration accounts for contractors and vendors.
| License | US list price | Mobile app | Copilot assistance | Good fit |
|---|---|---|---|---|
| Dynamics 365 Field Service | $105 per user per month, paid yearly | Included | Listed as included | Employed technicians, dispatchers, service managers |
| Dynamics 365 Field Service Contractor | $50 per user per month, paid yearly | Included | Not listed | External or subcontracted technicians |
| Resource Scheduling Optimization add-in | $30 per resource per month, paid yearly | Not a user license | Not applicable | Larger crews with heavy routing |
Those figures come from Microsoft’s Field Service pricing page on November 19, 2026. The page marks Remote Assist, scheduling and dispatching, vendor management and Guides as limited on Contractor, and it leaves out planned maintenance, returns processing and technician performance analysis.
What about frontline licensing? In Field Service, “frontline worker” is a setup concept, not a cheaper SKU. Microsoft’s quick setup form for frontline workers states that each one must hold a Field Service license. We found no Team Members path for technicians in the Field Service docs, and the attach price for users who already own another Dynamics 365 app isn’t on the pricing page, so get it in writing from your reseller. Then check it twice. The bigger licensing picture sits on our Dynamics 365 overview.
How Do You Set Up the Mobile Offline Profile?
Start from Microsoft’s default profile and add only what technicians need. That’s Microsoft’s advice and ours.
According to the offline profile setup guide, updated October 19, 2026, the default Field Service Mobile Offline Profile downloads active bookings assigned to the current user that start or end today or within the next seven days, then pulls related work orders, incidents, products, services, service tasks and not-to-exceed records. Core tables sync every five minutes by default.
- Open Power Apps, select the Field Service Mobile app and go to Settings, then General.
- Turn on Can be used offline.
- Choose Default for everyone with app access, or Restricted to selected users.
- Edit the default profile and review each table’s filter, relationships, files, images and sync frequency.
- Add your custom tables with tight filters, and include every table that a lookup filter references.
- Save, publish the app, then export the profile with your other customizations into test and production.
Two details catch teams later. When Microsoft ships an update to the default profile, filters you edited stay as you left them, while untouched filters receive the update unpublished for you to review. And publishing a profile change creates an active customization layer on top of managed components, which matters if you deploy through pipelines. Our Power Platform governance guide covers environment and release discipline.
Need different data for managers? Build a second profile. A supervisor who reviews a whole territory shouldn’t share a technician’s seven-day filter.
What Limits and Offline Caveats Should Admins Plan For?
More than most project plans assume. Microsoft’s offline profile best practices and limitations page, updated September 14, 2026, is the one to print.
- Never use All records as a filter, and avoid wide date ranges.
- Keep the default record types. Add, don’t remove.
- The default profile allows at most 15 linked tables, downstream tables included.
- Purchase orders, agreements, return to vendor and RMA tables can’t be used offline.
- Inventory validation needs a connection.
- SharePoint documents aren’t available, and knowledge articles may download but can’t be viewed offline.
- No Export to PDF offline.
- Custom code should keep calls to the offline database at two to four concurrent requests.
Power Apps adds its own ceilings. Its mobile offline limitations page caps sync at 3,000,000 records, allows up to 14 image columns across a profile, supports only system and quick views offline, and says calculated and rollup fields only recalculate on the server after sync. It also says field-level security isn’t supported in mobile offline mode. Test that one carefully if technicians rely on column security, and pair it with our Dataverse security roles guide.
Now JavaScript. Flows wait for signal. Power Automate flows run only when the device is online or at the next sync, so Microsoft points you to offline JavaScript using Xrm.WebApi.offline for on-device logic. Web resources are only partly supported, and on iOS, HTML web resources and the scripts inside them can fail offline unless they were cached earlier. Microsoft’s preferred answer is a PCF control, which works in both the browser and the app.
Photos deserve a budget line too. Every image that syncs lands in Dataverse file storage, and a crew of 40 snapping before and after shots on every job adds up faster than anyone expects, especially when nobody turned on optimized image upload during setup. Watch it monthly. Our Dataverse storage capacity guide shows how to watch it.

Online vs Offline Mode in the Field Service Mobile App
Offline-first isn’t only for crews with bad coverage. Microsoft recommends setting up offline even when technicians usually have signal, for a faster and steadier experience. The trade-offs are real, though. Test both.
| Factor | Online only | Offline-first profile |
|---|---|---|
| Speed on weak signal | Spinners and timeouts | Reads from the local database |
| Refreshed agenda experience | Available on iOS and Android | Not shown, users get Unified Interface |
| Copilot quick actions on bookings | Available through the refreshed experience | Not available, since they live in the refreshed experience |
| Power Automate flows | Run when triggered | Run only at the next sync |
| Search | Dataverse search across tables | Categorized search on offline tables, one table at a time |
| Data in scope | Anything the security role allows | Only rows matching profile filters |
| Custom web resources | Work as on the web | Partly supported, weakest on iOS |
| Admin effort | Low | Filters, testing, sync monitoring |
So which do you pick? If your technicians enter basements, rural sites or plants with dead zones, offline wins, and the new agenda waits. If they work in dense metro areas with steady coverage and you want Copilot updates today, the refreshed experience earns a pilot.
What Does a Technician’s Day Look Like on the Phone?
Bookings first. In the refreshed experience, the agenda view shows the day’s jobs, and a swipe opens quick actions to change status, get directions or call Copilot. Status changes also rewrite booking times, so moving a booking to Traveling sets the start time to now, and moving it to Completed sets the end time to now.
Directions use the address coordinates. Technicians can choose Automatically update so the booking flips to Traveling every time they request directions. Small thing. Dispatchers love it. Technicians mostly forget it exists.
Then the work order itself. From the booking, the technician opens the work order form to log services, products, notes, time and follow-up work. Our sister post on Dynamics 365 Field Service work orders covers the record structure and lifecycle, and the Field Service scheduling guide covers how bookings reach the phone in the first place.
Service tasks and inspections carry the checklist. A technician opens the service task, completes the inspection form, and can attach files or photos from the camera. Inspections work offline, but inactive inspections and service tasks aren’t available offline, so publish templates before the pilot starts.
Barcode scanning needs setup. Microsoft’s barcode scanning guide has you add the BarcodeScannerControl to a field such as Asset Tag, and it notes global search with barcode scanning isn’t available on tablets or the Windows app. Test real labels. Faded ones too.
At the end, the service report. The app can generate a customer-facing report with a signature and share it as a PDF, though that export won’t run while offline. Plan the handoff for when the device reconnects.
What Can Copilot Do for Technicians on Mobile?
Copilot does two things today, with a third on the roadmap. Each sits in the refreshed experience, which means none of them reach offline-enabled users yet.
| Capability | What it does | Status we found on November 19, 2026 |
|---|---|---|
| Work order summary | Summarizes status, priority, assets and history, tuned to the lifecycle stage | Documented with no preview label. Admin must enable it |
| AI-powered work order update | Technician types or speaks what was done, Copilot proposes field changes, the technician confirms | Preview. Paid environments only, not trials |
| Copilot chat in the mobile app | Natural language questions about Field Service data | Roadmap item RM571663, in development, GA targeted for February 2027 |
Summaries first. Microsoft’s work order summary page, updated November 3, 2026, says a summary for a scheduled job focuses on planning, arrival and the asset’s history, while a completed one recaps costs, prices and invoice details. Summaries aren’t saved. Only the person who generated one sees it.
Voice updates are the more interesting one for technicians with gloves on. The work order update page, updated November 17, 2026, lists what Copilot can change, which is booking status and times, service task completion, product quantity and line status, and service duration and line status. Microsoft labels it a preview not meant for production use. Pilot it with a few volunteers. Don’t build a process on it.
What does it cost? The pricing page lists Copilot AI assistance inside the $105 Field Service plan, not on Contractor, and says Copilot Credits are needed for prebuilt and custom agents, such as the Scheduling Operations Agent, which is still in preview. We found no Microsoft statement that technician summaries or updates draw credits. Ask your reseller. Confirm before scaling, and budget agents separately with our Copilot in Dynamics 365 use cases post.
On Ignite 2026, which runs November 17 to 20, we found no indexed Field Service mobile announcement while writing this. We’ll update the table once Microsoft’s session notes and roadmap entries land.
Where Do Teams and Outlook Fit for Frontline Managers?
Smaller than they used to. The Field Service deprecations page says the Outlook add-in, the Teams app, Viva Connections and Planner integrations aren’t supported after October 30, 2025. If a partner pitch still shows managers creating work orders inside Outlook, ask which year the demo was recorded, because that add-in has been unsupported for more than a year now.
Calendar sync is what remains. Per Microsoft’s Outlook bookings integration guide, bookings tied to a work order appear in the technician’s Outlook calendar within 15 minutes through server-side sync, and since Teams reads the same Exchange calendar, they show there too.
- Sync runs one way, from Field Service to Exchange.
- It covers one week back and two weeks forward, and that window can’t be edited.
- Only bookings tied to a work order sync.
- Changing only the work order won’t update Outlook. The booking itself has to change.
- Each user syncs with one environment at a time.
For managers who want Copilot help in Microsoft 365, our Microsoft 365 Copilot adoption guide covers measuring whether those seats earn their keep.
What Happens to Remote Assist and Guides?
They end. The Microsoft lifecycle notice on Guides and Remote Assist end of support sets December 31, 2026 as the date both apps stop working, with subscriptions sold or renewed only until November 1, 2025. Data stays in your Dataverse environment.
That includes Guides embedded in the Field Service mobile app. If technicians open a Library tab for step-by-step procedures, that tab goes away with it. Microsoft suggests Marketplace mixed reality products and spatial annotation in Teams mobile for some Remote Assist scenarios. Plan for it now. Export your guides, and move the high-value procedures into inspection templates or knowledge articles your crews can reach on the phone, keeping in mind that knowledge articles can’t be viewed offline.

How Should You Manage Devices With Intune and BYOD?
With Intune, if you already own it. Microsoft’s Intune management page says Intune can assign the app to groups, report usage, block cut, copy, paste and save as, and encrypt data at rest. It also says Intune is a separate service, not part of Field Service, and that each platform needs its own configuration.
One limitation trips up rollout teams. Intune can’t prefill the environment URL or username for the Field Service app, so technicians still pick the right app module themselves on first sign-in. It’s minor. Put that step in the training card.
Our practice opinion on BYOD. For company-owned phones, full device enrollment plus app protection is fine. For personal phones, app protection policies without full enrollment usually go down easier with technicians who don’t want IT wiping their family photos, and they still keep customer data inside managed apps where it belongs. Either way, decide before the pilot, not after the first lost phone.
Mobile Customization Do’s and Don’ts
Every field you add costs sync time and screen space. We’ve seen more rollouts stall on form bloat than on any licensing question. Less is faster.
- Do build a mobile-specific form with the eight to twelve fields technicians actually touch.
- Do use PCF controls for custom UI instead of HTML web resources.
- Do keep file names for scripts in lower case, which Microsoft calls out for offline web resources.
- Do turn on optimized image upload so photos default to smaller files.
- Don’t add tables to the offline profile that Microsoft lists as unsupported offline.
- Don’t depend on field mapping when technicians create related records offline. It won’t prefill.
- Don’t fire Power Automate flows for logic the technician needs on site.
- Don’t let each region invent its own app module without a reason.
Custom pages and dashboards in the sitemap render in classic Unified Interface even inside the refreshed experience. Plan for that look. When the job needs canvas screens or deeper Power Apps work, our Power Apps services team builds them to the same offline rules.
A Rollout Plan Technicians Will Actually Use
Our rollout sequence below is practice opinion, not Microsoft guidance. Adjust the durations to your crew size.
- Decide the mode per crew. Offline-first or refreshed experience, based on real coverage maps.
- Build the form and offline profile in a test environment with production-like data volumes.
- Configure Intune, licenses, security roles and the Field Service Resource field security profile.
- Run a two-week pilot with five to ten technicians, including your most skeptical senior tech.
- Collect feedback daily in the first week. Sync errors, missing data, slow forms.
- Fix, republish, and send a one-page training card with screenshots.
- Roll out by region or crew, never all at once, with a named super user per crew.
- Review sync health and adoption at 30 days. Then trim fields again.
Keep training short or it fails. Really short. Thirty minutes in the yard with the real phone beats a two-hour webinar every single time, and the trainer should log at least one job offline in front of the group so everyone sees what sync looks like when signal comes back.

What Mistakes Break a Field Service Mobile Rollout?
From projects we’ve reviewed, these seven do most of the damage. Watch for them.
- Turning on the refreshed experience for crews that need offline, then wondering why nobody sees it.
- Editing the default profile so heavily that Microsoft’s filter updates never apply.
- Lookup filters that reference tables missing from the profile, which leaves blank screens.
- Testing as a System Administrator instead of a real technician role.
- Heavy scripts written with online APIs that break once the device drops signal.
- Ignoring Remote Assist end of support until December.
- Launching with forms built for dispatchers, not for thumbs.
What Belongs on a Mobile Readiness Checklist?
Ten checks before go-live.
- Every technician has a Field Service or Contractor license and an environment seat.
- Security roles and field security profiles are tested with a real technician account.
- Offline or refreshed experience is chosen per crew and written down.
- The offline profile filters are scoped by date, owner and status.
- Every lookup-referenced table is in the profile.
- Inspection templates are published.
- Barcode fields and search tables are configured if you scan assets.
- Intune policies assigned per platform.
- Outlook calendar sync is enabled for technician mailboxes if wanted.
- A plan exists for anything that lived in Guides or Remote Assist.
ZapAI Decision Rules for the Field Service Mobile App
These are our practice opinions, not Microsoft guidance. Use them as starting defaults. Break them with reason.
| Situation | Our rule |
|---|---|
| Crews regularly lose signal on site | Offline-first for those users. Skip the refreshed experience until it supports offline |
| Metro crews with steady coverage | Pilot the refreshed experience and work order summary with a small group |
| Copilot voice updates | Volunteers only while it’s in preview, never a required step |
| Subcontractors | Contractor license through B2B accounts, with a narrower offline profile |
| Personal phones | App protection policies, not full device enrollment |
| Custom logic needed on site | Offline JavaScript or PCF, not flows |
| Remote Assist users today | Move to Teams mobile calls and inspection templates before December 31, 2026 |
One rule sits above the table. If a technician can’t finish a job in a dead zone, the app isn’t ready. No matter how good the demo looked.
Wrapping Up
Get the mode decision right first. Everything else follows. Offline-first and the refreshed Copilot experience don’t mix yet, so choose per crew, keep the offline profile lean, test as a real technician, and plan now for Remote Assist ending on December 31, 2026.
ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric and AI consulting firm in Irving, Texas, working with businesses across Dallas-Fort Worth and nationwide. Our Field Service implementation team configures offline profiles, mobile forms and device policies for mid-market service companies. Want a second look first? Ask for a mobile rollout review, and we’ll go through your profile, forms and pilot plan with you.
Questions Field Service Leaders Ask About the Mobile App
Does the mobile app cost extra?
No. Microsoft says the app is included with the Field Service license at no extra charge, and the Contractor license includes mobile access too.
Can technicians use Copilot while offline?
Not today. Copilot quick actions live in the refreshed mobile experience, and Microsoft says that experience doesn’t support offline mode, so offline-enabled users fall back to Unified Interface.
How much data syncs to each phone by default?
Bookings assigned to the user that start or end today or within the next seven days, plus their related work orders and line records. Core tables sync every five minutes unless you change the interval.
What replaced Field Service in Teams and Outlook?
Calendar sync. The add-in and Teams app lost support after October 30, 2025, and bookings now sync one way into Outlook calendars through Exchange, which Teams also displays.
Will Remote Assist keep working in 2027?
No. Dynamics 365 Remote Assist and Guides reach end of support on December 31, 2026 and stop working, though their data stays in Dataverse.
Do subcontractors need a full license?
Usually not. The Field Service Contractor license lists at $50 per user per month, paid yearly, with limited scheduling, vendor management and Remote Assist, and no Copilot assistance listed.
Is Intune required?
Optional, but sensible. Microsoft supports Intune app management for the Field Service app, though Intune is licensed separately and each platform needs its own configuration.
