Change groups sites/URL URL.
Today when you create a group, it is created under the "/sites" managed path. Please change this so we always can have complete governance over the /sites-path. So when we want to create new site-collections you won't get URL-conflicts.
Jennifer McTaggart commented
Beck is 100% dead on for this. I recently had a case where my SP Admin was trying to create a site collection that conflicted with an O365 group. Instead of the failure message stating that, it displayed 'Access Denied'. In hindsight, I understand it, but at the time, it was very unclear and caused us a few hours of chasing our tails. Please give us more control over O365 Groups!
What would be great would be if the SPO URL for sites created by Office 365 groups had /groups in the path instead of /sites. That would be another way to avoid this conflict. I was asked to create a /sites/marketing SPO site however I was getting an access denied message as a global admin. Turns out there was an Office 365 group created 2 months ago called Marketing and since sites created automatically for groups use the /sites URL they in essence squatted on the URL 1st. My global admin account did not have access to the group, hence the access denied message when trying to create the new site collection with the sites/marketing URL. *facepalm*
J Baker commented
be great if we can change SharePointSiteUrl address when our business want to change the group's name details.
Can seem to change the primary smtp address via powershell - but for the site's url - no go.. can this be looked into? This would be a practical solution to a business problem that can happen, outside of IT's control.
A. Auras commented
"Unavoidable Business Reality" yep - you nailed it down.
Please allow this update! It's frustrating to have groups change names and be unable to update the url to follow. Name changes are an unavoidable business reality.
Being able to control URLs for my own preference of naming convention would be ideal. I have a group that has been appended 7 times with random numbers and I cannot do anything about it.
J Yates commented
When creating an azure AD dynamic Office 365 group, the URL is the unique ID of the group (which is a GUID), which doesn't make sense. It should be the name of the group. This would be a use case to change the URL
Thinking about it more than 2 years ago. Any update?
Please enable users to change URLs of Group and Team Sites on SP.
This governance problem is really getting worser with Teams launched. Teamgroups are also using /sites/...
Managing consistent SharePoint sitecollection names is a total disaster ATM, thinking about disabling Teams before governance is getting out of control
Aaron Hawryluk commented
This is a SharePoint governance nightmare. Please fix, or at least allow us to see the Groups site collections in the list of site collections.
Denis Lacroix commented
Frederick Lin commented
We've reconfigured or tenant to have Groups be created in the /teams managed path but it doesn't help with Groups that already reside in the /sites managed path.
Martijn O. commented
Please create the /groups/ url for O365 Groups!
Dear SPO / Office 365 team, this is really a mess. Please get this fixed soon and make the admins life easier...
Pablo M. commented
@minjanou bishoff how do you what you mention?
mijanou bishoff commented
You can already set al net groups sites te be created at the /teams managed path. This leaves /sites for the non-group SPO sites created from the admin centre. It's doesn't give you a lot of options but at least it's something.
Has anyone considered this as an alternative?
I agree with everything everyone has said here, too. Please change it.
Mitchell Cooper commented
I agree with everything everyone has said here. Honestly, having admins just guess as to if a group has already taken a path you want to make a site collection of... then, not allowing us to change the group's SharePoint site URL... PLUS not having a way to make a group go to a managed path like /groups or /teams by default.... Really disappointing and it's really muddying the waters for us administrators.