Share
ReportLooking for community input on a licensing classification question. Anonymized scenario:
Setup
A retail customer uses a 3rd-party POS in their stores. Receipts are exported as XML and imported into D365 F&O via a partner-built interface. The data lands in Commerce store transaction tables (visible under Retail and Commerce → Inquiries and reports → Store transactions) and runs through the standard Commerce statement calculation and posting process, including retail-specific cash management and end-of-day flows.
Functionally: the front-end POS is 3rd-party, but the entire D365 back-office workload is Commerce.
Disagreement
An ISV partner claims the customer is covered by Operations – Order Lines capacity licenses only.
My concerns:
1. Order Lines scope. Per Microsoft's Licensing Guidance, Order Lines requires (a) indirect access only, and (b) transactions limited to designated qualifying order line tables. Commerce statement processing operates on a different table complex (RetailTransactionTable → statements → retail postings) and triggers retail-specific processes that, to my reading, are not covered by the qualifying Order Lines entities.
2. Multiplexing. The Licensing Guidance and the Multiplexing brief state:
Setup
A retail customer uses a 3rd-party POS in their stores. Receipts are exported as XML and imported into D365 F&O via a partner-built interface. The data lands in Commerce store transaction tables (visible under Retail and Commerce → Inquiries and reports → Store transactions) and runs through the standard Commerce statement calculation and posting process, including retail-specific cash management and end-of-day flows.
Functionally: the front-end POS is 3rd-party, but the entire D365 back-office workload is Commerce.
Disagreement
An ISV partner claims the customer is covered by Operations – Order Lines capacity licenses only.
My concerns:
1. Order Lines scope. Per Microsoft's Licensing Guidance, Order Lines requires (a) indirect access only, and (b) transactions limited to designated qualifying order line tables. Commerce statement processing operates on a different table complex (RetailTransactionTable → statements → retail postings) and triggers retail-specific processes that, to my reading, are not covered by the qualifying Order Lines entities.
2. Multiplexing. The Licensing Guidance and the Multiplexing brief state:
- "Multiplexing does not reduce the number of SLs of any type required"
- "Any user or device that accesses the service — directly or indirectly — must be properly licensed"
- "The number of tiers of hardware or software… does not affect the number of SLs required"
A 3rd-party POS terminal that creates transactional records in D365 via an automated pipeline appears to be a textbook multiplexing case — suggesting the POS terminals themselves require Operations – Device licenses, in addition to the HQ/back-office user licensing.
Questions:
Questions:
How would you classify this — Order Lines capacity, or Commerce workload + device licensing on the 3rd-party terminals?
Has anyone been through an MS license review on a comparable setup? Was multiplexing cited?
Any Microsoft written guidance that specifically addresses 3rd-party POS feeding Commerce statement processing?
Has anyone been through an MS license review on a comparable setup? Was multiplexing cited?
Any Microsoft written guidance that specifically addresses 3rd-party POS feeding Commerce statement processing?
Audit risk sits with the customer, so I'd like to sanity-check before escalating through formal channels.
Thanks for your support.
Thanks for your support.
Categories:
I have the same question (0)
All responses (
Answers (
159
