Dynamics 365 - Business Units and Multiple Security Roles

[@khalidakohistany9806]

The video are great. You are very good in explaining. I have never worked with D365. Your videos are great help for me. Thank you so much. I appreciate your hard work.

[@Novideosposted]

Excellent explanation & demonstration!!!!

[@CanonCrested]

This is a great video. Very explanatory and detailed.

[@Novideosposted]

You are a Guru!! Got into brain very easily

[@d365proz]

Good to hear that the content helped! Let me know if you would like to see more such content or any topic that you would like to see.

[@ShahramZadeh]

excellent video, very informative. thanks

[@paul4637]

I have a question regarding applying security roles to Business Units. When you create or copy a new security role on a business unit, does that mean that the role is available to the business unit, but the role still needs to be applied to a user or team under the business unit to become active/effective ?

[@d365proz]

The role needs to be applied to the User/Team. I personally prefer to apply role to Team(s), and assign/unassign Users to respective teams. The user will automatically inherit the roles privileges assigned to the team. This makes user permission management much easier, rather than applying roles to individual users.

[@JCarterB]

What do you mean by security roles can be created in a Business Unit. Isn't is actually that a Security role can be assigned to a Business Unit? You generally create security roles in an Environment and asign it to either a User, Team (M365 or AAD Group), Assign team or BU

[@d365proz]

You are correct from assignment part. The main point to understand is that Security Roles cannot reside on its own. Within D365 security structure Business Unit come first and things have to be associated to it. If that logic is clear, however you want to say it, its the same thing!

[@shubhamchopra934]

you said that for sales BU, let the parent BU be as it is (crm345668, which was there). Was there any other option? There can be only one Org level BU, which means crm345668 had to be there, right? Sorry, if its confusing

[@d365proz]

You are correct there can be one parent (root) business unit. In this case, as it was a demo environment, the parent (root) BU was crm345668 (I didn't change the name). The "Sales" Business Unit was inherited from the root BU, i.e. "crm345668".

[@telugufunnyreels.3500]

Really superb explanation . I want full crm course.please tell there is any option to Leaen.

[@d365proz]

Hi Sreekanth, Thank you for the appreciation. I completely understand what you are asking and I have received similar feedback as well. So, in some of my latest videos (like for Case Management) I started including Episodes. Anyways, you referred to one of my earlier videos.I do not have a formal full course as such, but I have tried to maintain similar topics in form of playlist. I hope the following information helps. For Configuration Topics in D365 refer to the following playlist: kzbin.info/aero/PLfhjZ6p90fkziWUhOX_31YvspM0JMxXGs For Entity Management Topics in D365 refer to the following playlist: kzbin.info/www/bejne/q6DPfYtmidh0nJo For Customer Service (start from EP11) in D365 refer to the following playlist: kzbin.info/www/bejne/omWvl5ece69-opY Currently I am working on Project Service Automation (PSA) topics, and you will start seeing them from Feb. 2020. For upcoming videos I will definitely try to implement your suggestions. Till then stay tuned :) !

[@solomonnorman5126]

Good video.

[@d365proz]

Thanks for the appreciation. Please let me know if there is any feedback. Currently I am working on Project Service Automation (PSA) topics, and you will start seeing them from Feb. 2020. Till then stay tuned :) !