11-18-2016 06:25 AM
11-18-2016 08:41 AM
11-18-2016 10:00 AM
We added a prefix for all O365 groups so they could be easily identified in the GAL. If I recall in EAC there's an option to create a group policy. The user can create the group name however they'd like and once the group finishes creation it adds the prefix to the front of it.
11-23-2016 01:41 AM
11-23-2016 06:22 AM - edited 11-23-2016 06:24 AM
We are in the same boat. We have disabled (as best we can) everything with O365 Groups. We can't have someone creating a new one as "President@comanyx.com" or just something vulgar in our GAL. User's also don't know a group they create in OWA it is listed in the GAL (such as "my sister's wedding" that someone created in ours). All other similar institutions we talk to are doing the same.
Please give us admin controls on the naming conventions and the ability to remove them from the GAL.
11-23-2016 06:44 AM
11-23-2016 08:41 AM
As mentioned on our public roadmap and at Ignite in this session we are working on these three features around naming policies: https://www.youtube.com/watch?v=mfox9-L5Xt0
- naming policy
- banned words
- profanity checking
04-06-2017 07:08 AM
I see on the Office blog that the Azure AD Naming Conventions will be available within the next 3 months. That is really great.
Unfortunately it requires Azure AD Premium...
It is really disappointing that every time Microsoft adds something to the cloud service portfolio, we have to pay more. They're continously adding extra layers of higher tier subscriptions and suites. I wonder when we will see the E7 plan...
04-12-2017 08:04 PM - edited 04-12-2017 08:05 PM
Interesting this is the first I am seeing this being Premium required. I also see guidelines and classifications are marked as premium. These currently don't require premium so why the change? What about the tenants that are using classifications and guidelines that aren't using premium currently?
04-12-2017 08:12 PM
04-21-2017 05:59 AM
04-21-2017 07:46 AM
05-01-2017 06:56 PM
11-17-2017 08:13 AM
That's good new but we have limited funding. Looks like the requirement for this is "Group naming policy requires Azure active directory Premium P1 license for unique users that are members of Office 365 groups"