Book Image

SharePoint Architect's Planning Guide

By : Patrick Tucker
Book Image

SharePoint Architect's Planning Guide

By: Patrick Tucker

Overview of this book

After opening a toolbox full of tools, it can initially be hard to know which is the right one for the job – which tool works best and when. Showing you how to create an informed and purposeful plan for SharePoint Online in the context of the Microsoft 365 suite of tools is what this book is all about. SharePoint Architect's Planning Guide will help you understand all you can do with SharePoint. Whether the tools are new to you or you’ve used the older versions in the past, your journey will start by learning about the building blocks. This book is not a step-by-step guide; there are tons of online resources to give you that and to help you better keep up with the pace of change. This book is a planning guide, helping you with the context, capabilities, and considerations for implementing SharePoint Online in the most successful way possible. Whether you need to plan a new intranet, migrate files to a modern platform, or take advantage of tools such as Power Platform, Teams, and Planner, this guide will help you get to grips with the technology, ask the right questions to build your plan, and successfully implement it from the technical and user adoption perspectives. By the end of this Microsoft book, you’ll be able to perceive the toolbox as a whole and efficiently prepare a planning and governance document for use in your organization.
Table of Contents (17 chapters)
1
Part 1:From Farm to Cloud
5
Part 2:From Lone Wolf to Pack Leader – SPO Integrations with M365
9
Part 3:From Tall to Flat – SPO Information Architecture
13
Part 4:From Current to Change

Provisioning and life cycle

Since groups are the foundation for all our collaboration tools and practices in M365, a question that quickly arises is who should be able to create them? Who should be responsible for making sure they are being created purposefully, managed well, and going away when their need has been fulfilled?

By default, all licensed M365 users can create a new group. This means that every person in your organization can create a group from Outlook, by creating a SharePoint site, spinning up a new plan in Planner, and all the other ways we’ve mentioned in this chapter. The default assumption from Microsoft is that adoption is strongest when people can get the collaboration spaces they need when they need them. It is the democratization of collaboration.

Everyone can create groups, but should they? Let’s look at options for balancing adoption and strict governance. We’ll see that good naming and expiration policies can make that job simpler...