License Multiplexing

Multiplexing is a complex topic and one that changes over time. Modern cloud services commonly offer many types of integration and the licensing requirements of each scenario can vary by the specific implementation and between customer agreements for the same product. Multiplexing may impact the licensing needs of Altus customers when individuals use hardware or software to pool connections, reroute or indirectly access information, and/or reduce the number of devices or users who directly access or use a product.

From an Altus perspective, there are several areas where multiplexing may be considered.

Inbound Dataverse Multiplexing

From the perspective of the Dataverse, inbound multiplexing occurs when users are able to enter data into the Dataverse without having a Power Platform license.

From Power Platform Licensing Guide - April 2024.pdf:

"Any user or device that inputs data into, queries, views data from or otherwise accesses Power Apps, Power Automate, Power Virtual Agents and Power Pages apps, directly or indirectly must be properly licensed"

Outbound Dataverse Multiplexing

Outbound multiplexing occurs when data is automatically extracted from the Dataverse and then consumed by users that do not have a Dataverse license:

From Licensing_Brief_PLT_Multiplexing.pdf:

"Any user or device that accesses the service, files, data, or content provided by the service that is made available through an automated process requires a Dynamics 365 service license"

Third-party multiplexing

There is also the potential for multiplexing with third-party applications. The exact requirements of each third-party application may differ, so please refer to your own individual license agreement with the third-party to assess the compliance requirements.