2

In Office 365 when you create a new site collection, the Web Site Address gives you the option to choose to create your site collection under "sites" or "teams". What is the difference and why would you choose one over the other?

5

There is no real difference, it is a matter of taste and consistency,

I for example would create my projects and team sites under /teams, and other types of site collections under /sites

This blog seems to describe Managed Paths in an Office 365 context quite well: http://schakrabortytcs.blogspot.se/2011/10/office-365-sharepoint-online-managed.html?m=1

| improve this answer | |
  • +1 it seems odd to have those two options and just have it down as a matter of taste. Is it possible that teams would originally have been for intranet type sites and 'sites' for public websites which is being discontinued if I understand it correctly? – Jacques Aug 24 '16 at 9:11
  • 1
    No, the public site had its own AAM: public-TENANTNAME.sharepoint.com – Robert Lindgren Aug 24 '16 at 10:06
0

Robert is absolutely right. To summarize though there are 2 main types of managed paths, which practically control whether you go Wide vs. Deep in your URL structure (when creating site collections) for on prem installations (this is not applicable for SharePoint Online):

  • Explicit inclusion managed path defines an exact path to which a single site collection can be directly attached.
  • A wildcard inclusion managed path defines a path that will not allow creation of a site collection directly at this point, bur rather create multiple site collections assigned beneath it (sites and teams are examples of Wildcard)

You must also be aware that it is recomanded to keep to < 20 per Web Application, so you need to balance carefully how new Managed Paths are created.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.