As you’d expect, we run a massive internal SharePoint system at Microsoft. It contains 250,000 site collections and 36 terabytes of data – growing at the rate of 1 terabyte every three months (yup, that’s the equivalent of 300,000 extra 1MB documents every month). The impact of that growth was not just storage cost – it is also search speed and search relevance (if you’re searching a gazillion out-of-date documents, it makes it harder to find the one you really want).
The Microsoft IT Team, who keep it all running, have implemented a SharePoint governance and lifecycle management system, to help meet the information standards for the business, as well as reduce cost and improve the search experience. And then written a great Technical Case Study to share their experiences. I thought it worth sharing because I know that education users of SharePoint are grappling with similar issues, as they develop SharePoint usage out from an IT department to institution-wide.
Policies for SharePoint site lifecycle management
There were four key policies implemented, which helped bring the system under better control:
Site classification. Sites must assign and maintain site information classification, information security classification, and ownership. Eg Team sites must have one full-time employee site owner and two administrators at all times.
Site lifecycle management of expired/abandoned sites. Sites expire one year after creation and must be renewed annually. Sites that have no activity over a period of six months are considered abandoned and are subject to decommission.
Site storage and quota management. Depending on the hosting environment, storage quota limits range from 2 gigabytes (GB) to 100 GB, depending on the type of sites and hosting options. SharePoint libraries and lists are not to exceed 5,000 items. Sites are backed up daily and recoverable up to 14 days.
Customization and server-side access. For most of the standard SharePoint-hosted services offerings, MSIT neither allows server-side access or server-side configuration changes by users, nor does it allow most third-party plug-ins, site customizations, new features, or additions.
Although our IT environment is very different to an average education user, there is some really useful implementation advice in the IT Showcase case study – for example, in the way that we’ve tagged all SharePoint sites with an Information Classification – something that could be ideal for categorising sets of data in an education SharePoint system (see right).
There’s also interesting insight into the way that sites are categorised for traffic – with ‘heavy hitters’ categorised when they reach more than 100,000 hits a day, or consuming more than 10GB of memory.