 Nicholas asks, I have a question regarding adding a group to a team. From what I know, you need to be owner of the team that you are adding the group to. Also, users in that group is added one by one, so it is not dynamic. We have several security groups, mail-enabled distributions list, etc., sync to Office 365. What is the best way to do this? The same group is also needed to add as a group permission to a SharePoint site. I would like to use on-prem created type of group sync to Office 365, but what is the best way here? This is a fun one, identity management. I've got to wipe the dust off with this knowledge. You're using on-prem groups. You want to maintain them on-prem? I respect that. It makes things a little bit more complicated. Now, yes, you're right. You can add a group to a team. You have the add members, the wizard dialog box, and it says you can add a distribution list or security group, but that's a point in time. Unpack the membership, puts it in the team, and it's done. If you want that to be a permanent syncing thing, I've only got two options that I can think of. A, set up some automation, power automate, PowerShell script, something like that to regularly sync membership or add the people to the team and cross-reference and remove them when they get removed from the group and so on and so forth, or create a new team and make it a dynamic membership group where it's looking at some sort of attributes on your users and on-prem, instead of adding your users to a group or in addition to adding them to a group, set an attribute for them. So, does this go back to where, in SharePoint, you couldn't add a group as a member of another group? Kind of. Yeah, because you could use security groups, but you couldn't use a permission group or SharePoint permission group as a group within that, correct? So, that's kind of the way I was reading into this is like they're trying to add a group to a group which doesn't work, but I like what your solutions are, Max. Yeah, even worse with the Microsoft 365 groups platform because its members can't be groups, just never can be. Yeah, especially as I'm trying to. The SharePoints that are associated with it, sure, you can screw around with the permissions and they're all you want and add security groups and all sorts of fun stuff, but now, if we're talking about an m65 group, which is a team, you're going to have to do some wonky, custom stuff if you want an on-prem group to in any way sync with the membership there. If you can let go of the on-prem component, your life will be a lot easier, but I understand that there may be other implications there. I love that. It depends. Answer again. All is. Do we answer the full question? I think so. That was. I think it's good to address these things. I wonder how long, what's the life cycle of this? How much longer, when are these people going to move away from holding onto these components where it's not going to make any sense to maintain these on-prem components and this current architecture and update? Well, because they can have their active directory in the cloud and sync to something on-prem, they can make the cloud the primary, right? And then sync it to an on-prem if they need to versus on-prem being the primary and sync to the cloud. This is beyond my scope, I'm asking. You're actually right. An Office 365 group can be reverse-synced on-prem for use on-prem. It'll be overwritten every time it syncs. So if you make changes to the on-prem group, those'll go away, every sync which happens every 30 minutes unless you customize it. But yeah, that's a great point is if you want to reverse the way you do things, if you need that group on-prem for some sort of on-prem app, that's an absolutely good idea of a way to go. I just ventured into my danger zone. Yeah, but it was a good point.