Hi,
Great question , and yes, you're on the right track. BC now supports Azure AD security groups for managing user permissions, and they’re designed to replace traditional user groups in future releases.
Let’s break it down:
1. Do you need multiple security groups?
Yes , if you want to assign different permission sets to users based on their roles (e.g., AP, AR, GL), it’s best to create separate Azure AD security groups for each functional area.
Example:
BC_AP_Users → Assigned AP-related permission sets
BC_AR_Users → Assigned AR-related permission sets
BC_GL_Users → Assigned GL-related permission sets
This gives you granular control and makes permission management scalable.
2. How security groups differ from user groups
Security groups are created in Azure AD or Microsoft 365 Admin Center, not inside BC. Once synced:
- You link them to BC via the Security Groups page
- Assign permission sets to the group
- All members inherit those permissions automatically
Unlike user groups, security groups are cross-platform and reusable across other Microsoft services.
3. How to manage permissions effectively
Here’s a recommended approach:
- Create Azure AD security groups for each business role
- Sync them into BC
- Assign relevant permission sets to each group
- Avoid assigning permissions directly to individual users , this becomes hard to maintain
- Use the Security Group Members FactBox to review who has access to what
You can also export/import security group setups or migrate existing user groups using the User Group Migration assisted setup.
Helpful references:
Manage user permissions using security groups – Microsoft Learn
Create & manage Security Groups in D365 BC – Shubhfordynamics
Mastering Permissions in BC – D365 Training
If you find this helpful, feel free to mark this as the suggested or verified answer.
Cheers
Jeffrey