How can we improve Office 365 Groups?

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.

734 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Arne Nøstvik shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      • PSJ commented  ·   ·  Flag as inappropriate

        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  ·   ·  Flag as inappropriate

        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.

      • Frederick Lin commented  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Dear SPO / Office 365 team, this is really a mess. Please get this fixed soon and make the admins life easier...

      • mijanou bishoff commented  ·   ·  Flag as inappropriate

        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.

      • Jordi commented  ·   ·  Flag as inappropriate

        I agree with everything everyone has said here, too. Please change it.

      • Mitchell Cooper commented  ·   ·  Flag as inappropriate

        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.

      • B Chin commented  ·   ·  Flag as inappropriate

        It is so confusing right now. Sites created by O365 Groups are different than sites created via SPO Admin. They should be treated differently and therefore have a different managed path.

      • A. Auras commented  ·   ·  Flag as inappropriate

        @Benoit: This very likely will never happen. Microsoft discourages to use Managed Pathes as they don't scale and they will not enable it in their own cloud farm. What you can do is using prefixes instead (.../sites/group-myGroup, .../sites/team-myTeam, ...) by configuring a distribution group naming policy.

        Boundaries & Limits: and boundaries
        Distribution Group Naming Policy:

      • Benoit Fournier commented  ·   ·  Flag as inappropriate

        Please allow us to create managed path. We currently use /teams; /clients; /groups; on-premises.

        Then, when we create groups, let us decide the path it will be created under.

        We have >100k clients site collections. We want to be able separate our teams and groups.

      • Matty commented  ·   ·  Flag as inappropriate

        I agree, either place them into a /groups/ managed path or a different URL entirely and make these separate from the rest of SharePoint's Sites

      • Ryan commented  ·   ·  Flag as inappropriate

        Sometimes we want to create groups at /sites, other times /teams. Other times, something else entirely (/dept, /projects/, /shared, the sky's the limit really).

        In my organization, we really need to provide a list of acceptable URLs for users to select from when creating an Office 365 group. If we supply just one URL, then the user must select that one URL. But admins need a separate list of acceptable URLs, managed by the company administrator.

      • Shawn Fagan commented  ·   ·  Flag as inappropriate

        Office 365 Groups should go under it's own Managed Path of Groups. That would solve any and all URL Conflicts.

      • Thomas Radman commented  ·   ·  Flag as inappropriate

        absolutely ridiculous, that the development team or at least the product manager did not think of that problem!
        Sitecollections created through the groups-feature are also not shown on the admin page (
        So it´s always guesswork when you try to create new sitecollections

        Please change the default managed path for groups to /groups/

      Feedback and Knowledge Base