Forum Discussion
Why SharePoint Site get created with /sites prefix when Microsoft Team created
Hi,
Can someone please explain to me why Microsoft Teams creates a companion SharePoint site collection in the /sites/ "managed path".
I think we can change this by changing the SharePoint tenancy settings, but when we change this to teams, if someone creates a modern communication site the site url will have /teams instead /sites.
What is the best approach to this issue.
Also, I had a look the following post and Steve has mentioned that " When Microsoft Teams creates a the companion SharePoint site collection in the /sites/ "managed path" it does this intentionally for security and content isolation." Can someone please explain to me why MS intentionally did this and what is the security and data isolation mechanism.
Sharepoint team site created from Microsoft Teams to prefix "teams"
Thanks.
- Well, this is not a prefix is how SPO URLs are built and what the article says is that by design everytime you create a site in SPO you are creating a site collection that by nature is an isolated container in terms of security, personalizations applied, etc. Basically the /sites and /teams managed path are there by design and required to create Site Collections in SPO, so there is no way to avoid them
- Hi Juan,
Thanks for your reply, but I m well aware what you have mentioned.
What I asking is if we default to url /teams then someone creates a Sharepoint communication the url will have /teams/xxx, wich is not looking good. Specially with modern site we don't have a option to select /teams or /sites while creating SP site.
Any idea.
