Forum Discussion
Error/Failed/Difficulty Joining One Group to Another via Azure AD
Hello dears, I hope all is well with everyone. Please don't pay too much attention to the text. I'm trying to make do with a translator. Well, in a single Tenet environment, with multiple dom...
- It should work if you use Azure AD security groups (even synchronized from on-premises). Create a "parent" security group, then add as many "child" security groups to it.
Hi
Sorry for the delay in getting back.
And thank you very much for your attention
Well, let's see...
When it says that there is no universal support, I understand that it is not just any group that I can add to another.
In my case, I generated a Security group which has permissions to perform a certain task. Instead of adding users directly, I would like to add groups, which I believe is best practice. This last group also has to be Security. This is it?
These groups must be created via Azure AD, right?
And when it says "no to M365 groups, distribution or mail-enabled security groups" does it mean that these would not be possible to fulfill my wish?
I reinforce the apology with these doubts of mine, but I believe that my doubts are being fully clarified.
Thank you,
I remain at your disposal for further clarification.
Sincerely,
TB
Sorry for the delay in getting back.
And thank you very much for your attention
Well, let's see...
When it says that there is no universal support, I understand that it is not just any group that I can add to another.
In my case, I generated a Security group which has permissions to perform a certain task. Instead of adding users directly, I would like to add groups, which I believe is best practice. This last group also has to be Security. This is it?
These groups must be created via Azure AD, right?
And when it says "no to M365 groups, distribution or mail-enabled security groups" does it mean that these would not be possible to fulfill my wish?
I reinforce the apology with these doubts of mine, but I believe that my doubts are being fully clarified.
Thank you,
I remain at your disposal for further clarification.
Sincerely,
TB
It should work if you use Azure AD security groups (even synchronized from on-premises). Create a "parent" security group, then add as many "child" security groups to it.
