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
11-19-2017 07:34 PM
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"
01-10-2018 11:12 PM
Hi All, thanks for starting this thread Brent and others for the helpful responses. I am looking for a solution that balances the needs of the teams that manage and look after AD as well as the end user. My concern using the same pre-fix is both UX and UI related - and end user looking for a specific group in a list of groups that all start with "G" or "Group" etc. will have a hard time finding it - it's an extra "mental tax" to using the product. From a UI perspective, using pre-fixes also means that it's harder to read the full name of a group in the UI. On the flip side, I can completely understand the needs of the AD and Exchange teams.
Having watched both the MS session and Martina's session it seems to me it should be possible to balance these in one of two ways:
1 - use a only suffix instead of a pre-fix
2 - allow the users to create the groups as they wish and, as it is created, write it into the directory with the pre-fix/suffix of choice. Creation is easy, the display name makes sense and the needs in AD are met
In your experience are these feasible options (I do not come from a technical background)? Thanks for any input
01-11-2018 04:33 AM
We use dl_ for our distribution lists. r_ for our conference rooms and therefore grp_ for our groups when created through Outlook endpoints.
Would like to see Azure AD group name convention and group lifecyle management coming out of preview so we can start using it though.
The difficulty we are facing with this model for naming policies is that it exploits only attributes of the currently logged-in user, hence an automated procedure won't be able to rely on that (e.g. the "create on behalf of" could be a great feature here ).
Add the variety of the business needs, e.g. create groups for projects/initiatives, or ad-hoc groups or departmental teams, etc. leads to making use of administrator's exceptions mostly at all times.
So we ended up every time into providing a form enabling collection of a various parameters, that get concatenated to fit the purpose of the customer, curated to escape spaces and other unwanted characters, and ultimately the prefix / suffix are merely used to add small things to match A-AD requirements set by admins.
A most appropriate solution should allow the definition of a formula, e.g. RegEx language, and injection of parameters via a pre-defined syntax to abide by, instead of exploiting user's attributes.