Posted on
sharepoint architecture

If you’ve ever thought about how you can structure your SharePoint sites, you aren’t alone. For individuals which have been doing SharePoint for some time, you know that we’ve lengthy had the controversy – where do your department sites use SharePoint?

Could they be considered publishing sites or collaboration sites? Or both?  Could they be sub-sites or site collections? Exactly how should we structure sites therefore we secure some content but still publish content for other people without which makes it too complicated?

This problem frequently results in a effective intranet build, but prevents true collaboration from occurring in SharePoint. We watch as our HR teams, Finance, yet others still resist adding their most dependable content into SharePoint (and particularly in to the cloud!) whenever we be aware of file share is not a good option for your content.

This problem will get much more complex whenever we bring Microsoft Teams– that are based on SharePoint sites – in to the picture. I wish to take a moment to speak through what is not considered a good idea, after which give a substitute, modern method of site architecture guidelines in Office 365.

Legacy site architecture approaches

I had been always of the perception you ought to have sub-sites from the root site for the publishing intranet sites (see Figure 1). Then, create site collections for the safer content.  This provided two benefits:

  1. There is a obvious division between your site that’s discussing content for other people versus. what’s guaranteed information for that department (Example: HR provides 401k benefits information to everybody (root sub-sites), but worker reviews have to be locked lower to some select few of people (site collection) This limited confusion and security mistakes.
  2. Should you did more complicated branding in your intranet site collection, it had been also simpler to configure the extra sites and corresponding navigation. Giving your collaboration sites a far more fundamental feel and look also built them into simpler to handle and led to the consumer understanding whether or not they were inside a secure site or publishing site.

Another approach I’d generally see would look something similar to figure 2, where secure subsites were tucked underneath the publishing site for simplicity towards the finish-user. Although this never was my preferred approach because of security concerns, I understand lots of organizations who implemented by doing this.

This complicates the thought of “where does my content belong?” I consider you one of the lucky ones – all the best to individuals sorting their way from the folder and item level security structures!

Figure 1: Publishing sub-site and secure site collection approach
















At its core, the concept I assumed was still relevant at work 365. *We still want the obvious separation of the items includes a publishing site versus a cooperation space*  An area, in which you might have many readers and couple of content proprietors/creators along with other areas enabling you to have numerous collaborators, without compromising security. Now exactly what do we all do?

Modern sites bring modern approaches

It’s time for you to flatten your website architecture from individuals deep legacy structures into an architecture that’s simple to manage, secure, organize, and re-organize for your heart’s content. We’re also keeping our philosophy on separating printed (intranet) content from collaboration content.

Yet another good bonus – you need to see better performance in site collections than you’d hidden within the sub-site structure. So, exactly what does all of this mean?  Our new structure will appear something similar to this:


Planning: How do you know when you should use Classic sites versus Modern Communications Sites versus Teams?

At Work 365 and SharePoint Online, we’ve two modern site templates we are able to use while still utilizing classic sites when needed:

  1. Classic Team or Publishing Site – For now, this it’s still your root site collection since modern isn’t available there.
  • Use Modern Pages on Classic sites to assist bridge the space.
  • Personalize the masterpage at the own risk (changes will always be entirely possible that could break your website)
  • Suggestion: Share news rollups with search web parts, provide links to internal and exterior applications or perhaps embed a relevant video from Stream here! CEOs like to share their message in the latest town hall conferences around the webpage.
  • An alternative choice: use a redirect came from here to transmit users to Modern Site.

2. Communication Sites — They are best throughout your publishing sites (intranet sites)

  • These websites can’t be “groupified,” meaning it’s a solo SharePoint site not connected to some Group or Microsoft Team.
  • Ideal for discussing communications and publishing content and fantastic for that mobile experience.
  • Here’s your legacy intranet substitute! One Communication Site (site collection) per department.

3. Microsoft Teams for Collaboration

  • Every Microsoft Team produced is supported by a contemporary team site in SharePoint.
  • Ideal for collaborating, team conversation, and the opportunity to utilize SharePoint alongside with Planer, Stream, PowerBI, and much more from one interface. All guaranteed having a simple AD Group they owner can manage themselves.
  • Teams can replace shared folders on the file share.
  • Teams might not be department focus — think functionally! How can you interact? You might find that producing Microsoft Teams according to “Projects” are simpler to handle!

How about navigation?

Moving out now – you’re going so that you can create automatic navigation by joining the website collection to some Hub site. If it’s not necessary this yet, you ought to have it soon. Hub sites will give you a method to gather related sites – you are able to roll-up news/activity feeds, produce a shared navigation, as well as share the appear and feel from the site.

You’ll be able to include and take away sites from hubs when needed.  Your website architecture it’s still flat, the websites don’t be a sub-site towards the hub site, but they’ll be connected to one another. Forget about re-organization headaches.

I wish to know what you think!

Finally – I would like to hear coming from all both you and your encounters with collaborating at work 365 – the very best factor about our community is to discover what’s employed by others and put it on within our own way. Best of luck!

**This information is a listing of your blog “Modern Methods to Site Architecture for SharePoint and Office 365” and features a couple of updates because the original blog was printed.

Like that which you read? Make sure to sign up for our blog to remain in the fold for those things Office 365, SharePoint and much more!