Forum Discussion
Business Central Device Licensing - Service Management
Microsoft limits the Business Central Device licence to specific device scenarios and capabilities, such as Point of Sale, Store Manager, Shop Floor and Warehouse devices.
Service Management, on the other hand, is part of Business Central Premium. Therefore, if each field technician needs to perform Service Management activities that require Premium functionality, a Business Central Device licence would not automatically provide those rights just because they are accessing Business Central through a mobile device.
If we distinguish between the device being used and the licensing model. Using a phone/tablet in the field does not by itself make the user eligible for a Device licence.
What the technicians need to do in Business Central — for example, whether they only need limited updates/read access or whether they are creating/updating/posting Service Orders and performing other Premium Service Management functions. That functional scope is important when determining whether Premium, Team Member, or another licensing approach is appropriate.
For a large field-service deployment, I would recommend validating the exact activities against the current Dynamics 365 Licensing Guide/Product Terms rather than assuming that every mobile user either qualifies for a Device licence or necessarily requires the same licence.
Oh, I know how the licensing works. The problem is that there are third party mobile service solutions that allow technicians to consume inventory and post transactions, without requiring any BC license at all...or they require just a Team Member license. The Anveo mobile client (as an example) is fully BC-centric, and it can't do the same...it only works if the users have a full premium license. Even though third party apps do the exact same things, they get away with either no license or just a Team Member license. Those solutions are not properly licensed...but Microsoft never does anything about it. I wish the playing field was level for more BC-centric platforms.
Thanks for clarifying. Looking back at the earlier discussion, I understand your point better now.
Your concern isn't really about what a Device licence allows, but about the commercial difference between a BC-centric field service solution and third-party solutions that may achieve similar operational outcomes through a different architecture and licensing model.
I agree that this can be frustrating, particularly where the end-user experience and business process appear very similar from the customer's perspective.
As you mentioned, the architecture of the third-party solution becomes important here — especially whether users are directly exercising Business Central functionality or whether the external application handles the field process and integrates the resulting transactions back into BC.
It would definitely be useful to have clearer Microsoft guidance specifically comparing these scenarios, as that would help partners evaluate BC-native versus external field-service solutions from both a technical and licensing perspective.