You’re offline. This is a read only version of the page.
We are considering to use the team member licence / essential licence for an ON-PREM Microsoft Dynamics 365 solution (v.9)
I would like to to know to what extend this license restricts the user to perform basic tasks in the system . Our solution is meant to be a very light version of Microsoft Dynanamics where the use only needs to send and receive email messages. Online documentation such as the on prem-licence guide is not completely clear on the exact restriction of the team member licence and how to configure these restrictions within the system: https://mbs.microsoft.com/Files/public/365/Dynamics365EnterpriseEditionOnPremisesLicensingGuide.pdf
There is currently no security role available in Microsoft Dynamics 365 for the team member license on our on-prem v9 environment that can actually limited the accessibility according to the license terms. We like to be absolutely sure to what extend the team member licence restricts the usage within the system and how to test this within the system.
Existing posts regarding this topic is that the team member licence is based on trust that the user will set the appropriate security roles to comply to the team member / essential licence. If this is true, i would like to know how to set up the security role that complies with the restriction of the team member licence.
Hope someone can provide more clarity on this.
Hi mike,
I find it a rather strange way to comply to a licence but thank you for confirming this! This helps us forward.
Kind regards,
Max van Dun
Hi Max,
The Team Member licence can be a bit difficult to nail down, especially as it seems to change quite frequently, but Appendix A in the document you referenced is really the most detailed list of what you can access, and what you can't.
As far as specific security roles are concerned you are right in that there are none pre-configured based on licence type but that's because the roles are defined to try and match job roles rather than the licence you have.
The best way to build a Team Member licence would be to start from a blank role (but with a default role visible in another window so you can cross-reference) and then build it up according to the job requirements and the list in the appendix. It's a long old job, and somewhat tedious, but it is the best way to really ensure compliance and relevance.
Having just had to create a number of security roles myself I know how much "fun" it can be - but it really is the best way to go with this.
Hope this helps
Mike Hartley
Hart of the Midlands
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (