Best practices are, and rightfully so, always a much sought-after topic. There are various kinds of best practices:
  • Microsoft best practices. In real life, these are the most important ones to know, as most companies implementing SharePoint best practices have a tendency to follow as much of these as possibly can. Independent consultants doing architecture and code reviews will certainly take a look at these as well. In general, you can safely say that best practices endorsed by Microsoft have an added bonus. Microsoft best practices are only published under TechNet or MSDN, not individuals blog sites and not this Wiki. Microsoft only uses the terms "Microsoft Best Practice" or "Microsoft Recommended" in TechNet or MSDN when referring to an actual best practice.  Microsoft best practices are based on how the product is designed and ment to be used and how the Microsoft field has found best works.  These are typically best for larger companies or larger farms.
  • Community best practices. These practices are patterns that have proven themselves over and over again as a way to achieve a high quality of your solutions, and it is important to know who proposed them and for what type and size of environments they are for as the best practice can be different for different size environments and different target workloads.  The benefits of a Community best practice is you can pick recommendations that are similar to your environment. 
  • Practices. These are just approaches that are reused over and over again, but not necessarily the best ones. Wiki's are a great way to discern best practices from practices. It's certainly possible that this page refers to these "Practices of the 3rd kind", but hopefully, the SharePoint community will eventually filter them out. Therefore, everybody is invited and encouraged to actively participate in the various best practices discussions.
This Wiki page contains an overview of SharePoint 2013 Best Practices provided from the communityThis article is not the Microsoft best practice page for SharePoint.  The Community best practices in this article are, divided by categories.


This section discusses best practices regarding performance issues.

SharePoint Server 2013 Build Numbers

Version Build # Type Server 
Package (KB)
Package (KB)
Public Beta Preview 15.0.4128.1014 Beta n/a n/a yes Known issues
SPS 2013 RTM 15.0.4420.1017 RTM n/a n/a yes Setup, Install 
Dec. 2012 Fix 15.0.4433.1506 update 2752058 
n/a yes Known Issue
March 2013 15.0.4481.1005 PU 2767999 2768000 global New Baseline
April 2013  15.0.4505.1002 CU - 2751999 global Known Issue 
April 2013 15.0.4505.1005 CU 2726992 - global Known Issue 
June 2013 15.0.4517.1003 CU   2817346 global Known Issue 1 
Known Issue 2
June 2013 15.0.4517.1005 CU 2817414 - global Known Issue 1Known Issue 2
August 2013 15.0.4535.1000 CU 2817616 2817517 global -
October 2013 15.0.4551.1001 CU   2825674 global -
October 2013 15.0.4551.1005 CU 2825647   global -
December 2013 15.0.4551.1508 CU   2849961 global -
December 2013 15.0.4551.1511 CU 2850024   global see KB
Feb. 2014 - skipped! n/a - - - - -
SP1-released Apr.2014 15.0.4569.1000
SP 2817429
- yes

Re-released SP

SP1-released Apr.2014

fixed Build:

SP -

2760625 - Fix
2880551 - Current


Known Issue
Re-released SP

April 2014 15.0.4605.1004 CU 2878240 2863892 global Known Issue
MS14-022 15.0.4615.1001 PU 2952166 2952166 n/a Security fix
June 2014 15.0.4623.1001 CU 2881061 2881063 global n/a


Feature Overview

This section discusses best places to get SharePoint feature overviews.

Capacity Planning


This section discusses installation best practices.

Upgrade and Migration

This section discusses how to upgrade to SharePoint 2013 from a previous version.


This section discusses infrastructure best practices.

Backup and Recovery

This section deals with best practices about the back up and restore of SharePoint environments.


Implementation and Maintenance

This section deals with best practices about implementing SharePoint.


This section deals with best practices regarding SharePoint Apps.

Every day use


This section deals with useful SharePoint add-ons.


This section covers best practices targeted towards software developers.


This section contains debugging tips for SharePoint.

  • Use WireShark to capture traffic on the SharePoint server.
  • Use a Text Differencing tool to compare if web.config files on WFEs are identical.
  • Use Fiddler to monitor web traffic using the People Picker. This will provide insight in how to use the people picker for custom development. Please note: the client People Picker web service interface is located in SP.UI.ApplicationPages.ClientPeoplePickerWebServiceInterface.



This section discusses best practices regarding SharePoint 2013 farm topologies.


This section discusses SharePoint accessibility topics.

Top 10 Blogs to Follow

It's certainly a best practice to keep up to date with the latest SharePoint news. Therefore, a top 10 of blog suggestions to follow is included.
  1. Corey Roth at 
  2. Jeremy Thake at
  3. Nik Patel at
  4. Yaroslav Pentsarskyy at
  5. Giles Hamson at
  6. Danny Jessee at
  7. Marc D Anderson at
  8. Andrew Connell at
  9. Geoff Evelyn at
  10. /, Nikander & Margriet on SharePoint.

Recommended SharePoint Related Tools

What to put in your bag of tools?

  1.  , the SharePoint Flavored Weblog Reader (SFWR) helps troubleshooting performance problems by analyzing the IIS log files of SharePoint WFEs.
  2. , PressurePoint Dragon for SharePoint 2013 helps executing performance tests.
  3. , a tool for checking capacity planning limits.
  4.  , Muse.VSExtensions, a great tool for referencing assemblies located in the GAC.
  5. , Veeam Explorer for Microsoft SharePoint - E-discovery and granular recovery of Sharepoint items and site lists.
  6. , helps with all your PowerShell development. In a SharePoint environment, there usually will be some.
  7. , Visual Studio extension based on PowerGUI that adds PowerShell IntelliSense support to Visual Studio.
  8. , FishBurn Systems provides some sort of CKSDev lite for VS.NET 2012/SharePoint 2013. Very useful.
  9. , web extensions make creating CSS in VS.NET a lot easier and supports CSS generation for multiple platforms.
  10., the SharePoint 2010 Administration Toolkit (works on 2013).
  11. , a great tool when you've installed your SharePoint farm on Azure.
  12. , ULS viewer used to review ULS log files


If you want to learn about SharePoint 2013, there are valuable resources out there to get started.

See Also