Thanks!
We really appreciate the efforts for enhancing group-governance!
One question:
Features for adding pre/suffix to OWA-groups requires AAD premium. We do have several services, apps and even domain controllers in Azure, but the AAD linked to our tenant is licensed with "basic" license. We use ADFS and AAD-sync to our directories so I believe we did like most, and simply created a tenant with AAD included 🙂
Our problem is that our users (employees and students) label OWA-groups with department names etc. These names have a high probability of being used by exchange in the future, since all addresses created on our federated domain, also gets an onmicrosoft-address (naturally). Example: If a student creates a group called “Sales”, we have a problem… 😊
Two ways to solve this: we could add a new non-federated domain (won't work with federated domains) and add groups to that domain, but we rather avoid this. Or we can add a pre/suffix to the group, but that requires AAD premium.
Are there any other options? We could create a list of banned names, but there are some creative people at our university 😉
This is the one small issue we face now with groups (and therefore Teams, Planner, Modern Sites etc). Not a huge problem today, but it might be in the future. For us it looks like an AAD Premium subscription is the way to go, but that is one hefty price when including all our students. If anyone could point us in the right direction on this, it would be much appreciated!
Sincerely
Torbjørn
