group naming policy using extension attributes
Please implement additional functionality to allow the use of Extension Attributes as part of a Group Naming Policy. This is required as the Department name is too large and many organisations have a shortened department code which they apply via an Extension Attribute. Using a long department name in a Group Naming POlicy creates names that are too long to be useful, but using a shortened department code plus group name means that the group can be easily identified and attributed to a department without cluttering the name space.
e.g. Information and Communication Technology has a short code of ICT in ExtensionAttribute11
Finance has a short code of FIN in ExtensionAttribute11
Using a Group Naming policy where is is set to use "[ExtensionAttribute11]-[GroupName]" would then create ICT-[GroupName] or FIN-[GroupName] depending on code applied to the user in ExtensionAttribute11.
Thank you for your feedback! We have heard you and are considering future implementation options. There is no timeline yet for implementation. If this feature matters to you, keep voting as it will help us prioritize.
We are aware of this feature request. Though we don't have a timeline yet, this work item is being tracked in our backlog.
Yes, please add this feature. It would make the naming policy usable. The current available attributes are pretty worthless for identifying groups in an enterprise.
Please enable group naming policy using extension attributes to have ability for large organization to achieve governance policy for naming standards.
Don Basham commented
USDA needs this feature across all our departments and staff. Please "make it so" as soon as you can. Thanks for the opportunity for feedback!
This sounds like a great idea!
Please enable group naming policy using extension attributes to have ability for large organization to achieve governance policy for naming standards. Due to lack of ability we need to perform extra step of automation's to achieve naming policy for new GROUP or TEAMS creation.
Please expand the naming policy supported attributes to include extension attributes. James Everett's comment captured this concern very well. Our large organization has this same concern; please add extension attribute support.
"For a large and diverse organization located at a single location (which makes the address related attributes unusable) this is a prerequisite for any sort of sensible self service process.
In the meantime we will have to disable self service and use a separate process for creating new sites, teams, groups with meaningful/manageable names"
James Everett commented
For a large and diverse organisation located at a single location (which makes the address related attributes unusable) this is a prerequisite for any sort of sensible self service process.
In the meantime we will have to disable self service and use a separate process for creating new sites, teams, groups with meaningful/manageable names
Andrew Swiffin commented
This would make O365 groups/teams much more manageable
McWilliams, Barry commented
Would make it much simpler to deploy and manage Teams & Groups in our university. Please implement ASAP.
Kimpton, Michael commented
This would help with managing groups
Mike Macary commented
This would make opening up group creation much easier. Please consider implementing MS!
Yes this would open more options to better manage O365.
Would support office group /teams governance.
AAD needs to support the capabilities of on prem AD and this is a big blocker for Azure/O365 adoption of services
Max Caines commented
Would make it much simpler to deploy Teams
Pip Cartwright commented
Challenges with naming conventions was the root reason that Teams has yet to be made available at UEA.
An essential addition in order to help with the governance which as many will agree is a key factor in the successful implementation of any project.
Definitely a beneficial feature for us.
Same for our university. An important feature. Please implement soon.