Forum Discussion
Licensing using Power BI with Dynamics 365 data
Well according to the following on Dynamics 365 licensing regarding multiplexing, anyone using/consuming the data should have a license.
Multiplexing
Multiplexing refers to the use of hardware or software that a customer uses to pool connections, reroute
information, or reduce the number of devices or users that directly access or use the Dynamics 365
service. Multiplexing does NOT reduce the number of SLs of any type required to access the Dynamics
365 service. Any user or device that accesses the Dynamics 365 service —whether directly or indirectly—
must be properly licensed.
Dynamics 365 SLs are required for users or devices that directly input, query, or view data from the
Dynamics 365 service. Similarly, Dynamics 365 SLs are required for users or devices that input data into,
query, or view data from the Dynamics 365 service through a pooling device. Pooled connections use a
non-interactive user account in Dynamics 365 that can access the system but only via the web service
layer. Internal users and devices accessing Dynamics 365 data indirectly through a portal or via an API to a
separate service such Microsoft Outlook must also be properly licensed, regardless of if they are set up as
a Dynamics 365 user in the service, for example:
• Internal users and devices access Dynamics 365 data indirectly through a PowerApps must still be
properly licensed for Dynamics 365
• 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 SL
• The number of tiers of hardware or software between the Dynamics 365 service and the user or
devices that ultimately use its data, services, or functionality does not affect the number of SLs
required.
For qualifying indirect transaction types, the Operations Order Lines SKU may also be used to license
indirect access scenarios such that a user or device license is not required. Please see the Order Lines
section for more details.
For additional information about multiplexing refer to the Microsoft Volume Licensing Brief
Multiplexing—Client Access License (CAL) Requirements. Note, this document is intended to provide
general multiplexing guidance that can be used for online as well as on-premises situations.
Note: Licensed users may manually rekey information (when coming from non-licensed users) into the Dynamics 365
service. This scenario is not considered multiplexing.
Hi wlknsnBI ,
" but do they also require a Dynamics 365 license for consuming the data (multiplexing)?"
They don't need it, but the report creator(the owner of the dataset) may need it.
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Well according to the following on Dynamics 365 licensing regarding multiplexing, anyone using/consuming the data should have a license.
Multiplexing
Multiplexing refers to the use of hardware or software that a customer uses to pool connections, reroute
information, or reduce the number of devices or users that directly access or use the Dynamics 365
service. Multiplexing does NOT reduce the number of SLs of any type required to access the Dynamics
365 service. Any user or device that accesses the Dynamics 365 service —whether directly or indirectly—
must be properly licensed.
Dynamics 365 SLs are required for users or devices that directly input, query, or view data from the
Dynamics 365 service. Similarly, Dynamics 365 SLs are required for users or devices that input data into,
query, or view data from the Dynamics 365 service through a pooling device. Pooled connections use a
non-interactive user account in Dynamics 365 that can access the system but only via the web service
layer. Internal users and devices accessing Dynamics 365 data indirectly through a portal or via an API to a
separate service such Microsoft Outlook must also be properly licensed, regardless of if they are set up as
a Dynamics 365 user in the service, for example:
• Internal users and devices access Dynamics 365 data indirectly through a PowerApps must still be
properly licensed for Dynamics 365
• 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 SL
• The number of tiers of hardware or software between the Dynamics 365 service and the user or
devices that ultimately use its data, services, or functionality does not affect the number of SLs
required.
For qualifying indirect transaction types, the Operations Order Lines SKU may also be used to license
indirect access scenarios such that a user or device license is not required. Please see the Order Lines
section for more details.
For additional information about multiplexing refer to the Microsoft Volume Licensing Brief
Multiplexing—Client Access License (CAL) Requirements. Note, this document is intended to provide
general multiplexing guidance that can be used for online as well as on-premises situations.
Note: Licensed users may manually rekey information (when coming from non-licensed users) into the Dynamics 365
service. This scenario is not considered multiplexing.