ASK: support nested security groups in M365 Centralized Deployment
Most organizations have already set up security groups before deploying Add-ins. Using those existing groups would be an efficient way to determine what add-ins should get deployed to what users.
But because of Centralized Deployment not supporting nested security groups, organizations are forced to create new dedicated flat security groups for Add-in deployment. They also need to adjust their talent onboarding and leave processes, removing and adding users from and too those new groups. This is an extra effort that many organizations need to organize and fund only because nested groups are not supported in Centralized Deployment.