Managing Subcontractor Engineers in Field Service Without Buying Every Licence

Can subcontractor engineers use Dynamics 365 Field Service without a licence?

Not directly. Anyone who signs in to Field Service, whether in the mobile app or a model-driven app, and reads or updates work orders and bookings needs a user licence that includes those rights. Microsoft licenses Dynamics 365 per named user, not per company and not per job, and a subcontractor engineer is a user like any other when they use the system.

What is licensed is the person doing the work in the system, which is why the useful question is not how to avoid licences but who actually needs to touch the system and how. Some subcontractors only need to be scheduled and to report completion. Others need the full job on a device. Those are different access shapes with different licensing and different audit evidence.

Microsoft has at times offered lower-cost licence options aimed at frontline or contractor use, and device licences exist for some products. What each permits, and whether one applies to Field Service work orders in your agreement, changes over time, so check the current Dynamics 365 licensing guide and confirm with a licensing specialist before designing around it. Our licensing renewal guide covers rightsizing the seats you already hold.

Does a shared login, proxy account or integration avoid Field Service licensing?

No. Microsoft calls routing many people through fewer licences multiplexing, and its licensing guidance is that pooling, shared accounts, middleware and integrations do not reduce the number of licences required for the people who use the data. A single "subcontractor" account used by twenty engineers is both a licensing breach and an audit failure, because every record it touches is attributed to nobody.

The same applies to an app or portal that reads and writes Dataverse through one service account on behalf of many people: the people are still the users. How this plays out for custom front ends over Dataverse is explained in Power Pages or a custom front end.

Manual work by a licensed person is treated differently from automated pooling in Microsoft's guidance, which is what makes a dispatcher model possible. Where exactly the line sits depends on detail, such as whether engineers see Dynamics 365 data forwarded back to them in bulk, so check the current multiplexing guidance and take licensing advice on your specific design.

What are the realistic ways to give subcontractors access to Field Service work?

Four models cover almost every case. They are not exclusive: many organisations use a dispatcher proxy for occasional subcontractors and a portal or licences for the regular ones.

How does a dispatcher proxy model work in Field Service?

The subcontractor engineer is scheduled but never signs in. Create each subcontractor company as an account and each engineer as a contact, and make the engineer a bookable resource of type Contact so they appear on the schedule board and can be booked with their skills and territories. The dispatcher books the work order, and a flow sends the job details to the engineer by email or SMS.

The engineer reports back by a fixed channel: a reply to that email with photos, a structured form link, or a call. The dispatcher updates the booking status, work order products and service tasks, and attaches what was received. The record must say that it was entered on behalf of someone, so add columns for the reporting engineer, the channel, the time reported and a link to the source message, and keep the original email or form submission attached to the work order.

The cost is dispatcher time and a delay between work and record. The risk is licensing: if the proxy becomes a routine pipeline where engineers effectively use Dynamics 365 data through the dispatcher, it can look like multiplexing. Keep it manual, proportionate and confirmed with licensing advice. Why dispatching through messaging apps gets expensive at scale is covered in dispatching field technicians via WhatsApp.

When do a few licences on shared company devices make sense?

When a stable group of subcontractor engineers does full jobs regularly, needs checklists, parts, asset history and offline working, and will not use personal phones. The company provides the devices; each engineer still has their own identity and licence, and signs in and out of the Field Service mobile app. A shared device is fine. A shared login is not.

The saving comes from licensing only the engineers who actually use the app, not every subcontractor on the approved list, and from reviewing assignments as the subcontractor pool changes. Use Microsoft Entra B2B guest accounts or accounts in your tenant for these people, enforce multi-factor authentication, manage the devices with Intune so a lost tablet can be wiped, and disable accounts the day a subcontract ends.

This model produces the strongest audit evidence, because every booking status change, part used and signature is recorded under the engineer's own identity with a timestamp. Device licences exist only for some Microsoft products and scenarios, so do not assume a shared device can be licensed once for several engineers; check the current licensing guide. Offline profile design for these devices is covered in Power Apps offline field data loss.

How does a Power Pages portal for subcontractors work?

Subcontractor engineers sign in to a portal with an external identity, see the jobs booked to them, and submit start and finish times, parts used, service task answers, photos and a completion note. Behind it, each engineer is a contact linked to their subcontractor company account and to a bookable resource of type Contact, and table permissions limit them to bookings assigned to that resource and to their own company's records. Getting those permissions right, and testing that one subcontractor cannot see another's jobs, is covered in Power Pages table permissions.

Portal submissions should land as they were submitted, then update the work order through a flow or plug-in, so the audit trail keeps both what the engineer said and what the system did with it. What a Power Pages build involves is on our Power Platform consulting page.

Two licensing points need checking. Power Pages is licensed by authenticated user capacity per website per month rather than per named user, as set out in Power Pages or a custom front end. And Microsoft distinguishes internal users, who need user licences, from external users; depending on the current terms and how closely a subcontractor works as part of your organisation, they may count as internal. Confirm the classification before committing to this model.

When does per-login portal capacity cost more than buying named licences?

When most subcontractor engineers sign in every month. Portal capacity is counted by unique authenticated users per site per month, so an engineer who signs in once in a month consumes the same capacity as one who signs in daily. Named licences are paid whether used or not, but give full Field Service functionality. Compare the two with your own numbers and current Microsoft pricing rather than a rule of thumb.

• Count distinct subcontractor engineers who would sign in during each month over the last year, not the size of the approved list.
• Split them into regular engineers who work most weeks and occasional ones who appear a few times a year.
• Price regular engineers both ways: as named licences and as monthly authenticated users, using current Microsoft pricing and your agreement.
• Add what the portal needs that the mobile app already provides: offline working, barcode scanning, signatures and the build and maintenance of portal pages.
• Add the dispatcher time avoided or created by each model, since a portal and the mobile app both remove rekeying.
• Recheck the comparison at renewal, because the subcontractor mix and Microsoft pricing both change.

What if subcontractor engineers refuse to use their personal phones?

Take the refusal seriously, because it is usually reasonable. Subcontractors do not want your app, your device management or location tracking on their own phone, and data protection rules make installing a managed app on a personal device a conversation rather than an instruction.

Each model answers it differently. The dispatcher proxy needs nothing installed: a phone call or an email reply works from any phone. Shared company devices remove the personal phone from the question entirely, at the cost of buying and managing the devices. A Power Pages portal runs in a browser with nothing installed and no device management, which many subcontractors accept even on a personal phone, but it still asks them to sign in with a personal account. A custom portal has the same trade-off as Power Pages.

If the refusal is about device management rather than the phone itself, make clear what the portal does and does not collect. If it is absolute, the choice is between the proxy and company devices.

What audit evidence does each subcontractor model produce?

An audit of subcontracted work asks who did the job, when, whether they were qualified, what they used and how you know. A spreadsheet typed up afterwards fails because it records a claim, not evidence. Each model can pass, but they produce different evidence and need different controls. Which records hold proof of work on a Field Service job is covered in detail in our Field Service proof of work guide, and audit history settings in audit trail and compliance.

When is a custom subcontractor portal or custom CRM the better choice?

A custom portal is cheaper than seats or portal capacity only when it does not simply put a new face on Dataverse data, because reading and writing Dynamics 365 through one integration account for many people is still multiplexing. It makes sense when the subcontractor workflow can genuinely live outside Dynamics 365, with its own database, and only agreed summaries flow back, subject to licensing advice, or when the whole service operation does not need the Microsoft stack.

We recommend the right solution - whether that's Microsoft Dynamics 365, Power Platform, or a custom-built CRM. Some businesses need the Microsoft ecosystem. Others need full control without licensing. We deliver both. For a service business whose engineers are mostly subcontractors, a custom-built CRM on React, Node.js, PostgreSQL or .NET with its own scheduling and subcontractor portal removes per-user licensing altogether. For a business that relies on Field Service scheduling, assets and agreements, the Microsoft models above are usually the right answer, and Power Platform consulting covers building the portal or flows around them.

How does Solzet help manage subcontractor engineers in Field Service?

We start with the subcontractor list and the audit finding: who works for you, how often, on what kind of job, on what devices, and what the auditor could not see. From that we map each group of subcontractors to a model, design the contact and bookable resource setup, the on-behalf-of fields or portal permissions, and the evidence each job must carry, and we flag every point where licensing advice is needed rather than guessing. Then we build it and replace the spreadsheet.

The work is done by senior consultants and full-stack developers delivering remotely from Yerevan, Armenia, with 8+ years of Dynamics 365 Customer Engagement and Power Platform work, directly for your team or white-label for Microsoft partners. We are not a licensing reseller and give no licensing guarantees, so final licensing decisions sit with your licensing partner. The wider Field Service build is on our Field Service implementation partner page.