If you use Team Member licenses in your Dynamics 365 deployment, you need to know about new enforcement that is coming in 2020 Wave 1 for Dynamics 365.
Starting in April for new customers and July for existing customers, users with Team Member licenses will need to use one of two new model-driven apps that will restrict which entities can be used by team member licenses.
Watch this video to learn what you need to know so your users’ access isn’t disrupted.
Give us your feedback, all of it: good, bad, and ugly, I’m sure we can take it. Suggest new topics either in comments or by sending your ideas to email@example.com.
Don’t forget to subscribe to http://youtube.com/crmtipoftheday.
Cover photo courtesy of Library of Congress
Thanks for the tip! Can you confirm that create and edit of Contacts are allowed? Your video mentions it is and the licencing agreement says it is however, the security role doesn’t allow it?
To give Create and Edit rights on Contact you will have to create a new custom security role with those privileges and assign it to a Team Member licence user in addition to the new OOB Team Member security role.
I realise that I can do that, I wanted to confirm it is allowed as the supplied role contradicts that so was looking for some clarification.
Update on this from Microsoft: “The Sales Team Member security role is now updated to allow CRUD for Contact. The role is also now customisable”
that is true. You would need to add a role with contact create permissions.