@Huma Selot CU200816...
The multiplexing rule:
Microsoft explicitly prohibits using a single service account or middleware layer to funnel transactions from multiple unlicensed external users into D365 F&O. This is called multiplexing and it violates the D365 F&O licensing terms regardless of whether the external users ever directly touch the D365 interface.
The correct licensing approach:
Every person whose business activity generates a transaction that enters D365 F&O must be licensed — even if they interact through an external system and never log into D365 directly. The license requirement follows the business activity, not the technical access method.
If 500 external sales agents generate orders through your external ecommerce platform and those orders flow into D365 F&O via a single service account API — all 500 agents require D365 F&O licenses under Microsoft's multiplexing rules.
The service account license:
The service account itself requires a full Operations license if it is creating or modifying transactional data — sales orders, purchase orders, invoices, journals. A Team Members license is insufficient for write operations on transactional entities.
The practical exceptions:
Microsoft does provide specific connector licenses and external connector rights for certain integration scenarios — particularly for high volume automated integrations where human activity is not the driver. These must be explicitly agreed in your Enterprise Agreement. Check your EA terms or raise with your Microsoft licensing contact before assuming this applies.
Recommendation:
Document your integration architecture and the number of external users driving transactions. Present this to your Microsoft licensing contact or a Microsoft licensing specialist before go-live. A SAM audit that uncovers multiplexing post go-live can result in significant back-billing for all unlicensed periods.
If it helps, Mark answered.
