Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We've got a healthcare customer who are using D365 CE as their core customer management system. However, they also have another health management system to manage all their clients health and medicine related info and activities.
As part of the future roadmap, they're planning on integrating with D365 CE to get the latest client record into the healthcare system. Once they get the latest client record from CE, they'll then go ahead and plan all the medical and health needs for their clients in the healthcare system.
The healthcare system is used by 6000 staff whereas D365 CE is being used by the sales, marketing and customer service teams ~100 staff.
Question : Is this a multiplexing scenario and does MS expect our customer to buy 6000 CE licenses to make this integration work?
Can someone please confirm this?
Are those 6000 users going to D365, then yes license is required.
If it is system to system integration (D365 - health care system) and 6000 users are using health care system only, then no additional license is required for the users.
The users of health care system will not access the user interface of D365, they will access only data via system to system integration (API / Web service / batch job) then only license for Integration (API calls) is to be procured. Additional user licenses are not required.
I'm sorry but the confusion for me is the way Microsoft has worded their licensing model around licensing. Below is the snippet from the D365 licensing guide:
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 accessing Dynamics 365 restricted data indirectly through a Power Apps 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.
If I'm reading the above correctly, it appears that MS expects us to buy a licence for all the users who are accessing D365 data via a pooled connection?
You might read the continuation to that in licensing guide and download the Multiplexing CAL requirement document and read that as well.
If the user of healthcare system is not accessing "user specific" data for e.g. "My Accounts" via "health care system" that is read from D365 directly
If the user is not accessing D365 user interface
If the user is not performing transactions on top of D365 data and writing back to D365
No license is required.
You can just push D365 data to your health care system and deal the transaction there.
First off, thank you for trying to help me out in this situation. I really appreciate it.
Now, I did read the CAL requirement document and please correct me if I'm wrong but isn't Figure 1, under the SQL server scenario exactly similar to my situation?
User 1 creates a record in CRM and User 2 is accessing this data via a pooled connection. As per that document, User 2 needs a CAL.
Have I missed something?
Also, the other thing that I did not mention as I didn't think it mattered was that in case of an emergency, users may create clients directly into the healthcare system and this will be synchronised back into CRM. The reason I thought this did not matter was because as per the licensing guide and the CAL requirement document, even viewing data from CRM through a pooled connection requires a license.
Business Applications communities