Courtesy of by Jimmy De Santis/ShareGate

For those of us who have been working with SharePoint for a while, we have a bit of a soft spot for the 2010 release. The product represents the first iteration that was truly enterprise ready, and made an attempt to integrate with other Microsoft products, noticeably the Office Suite. Some of the features that the platform introduced were:

  • The Office Ribbon
  • Early social features
  • A rebuilt central administration
  • Service applications for administrators.

It also added client-side object models, BCS and PowerShell support for a range of other integrations and development potential.

There were some areas that weren’t as popular or well liked, but by far and large SharePoint 2010 was a positive stepping stone towards what we see today. In short, it was a huge improvement over SharePoint 2007, and led to some truly powerful internal business systems, Intranets and tools – and many of these systems are still running today.

So it’s important to note that mainstream support from Microsoft is ending soon. A shame, we know… But an inevitable step. So what does this mean for you?

End of mainstream support – October 13th 2015

Microsoft is Ending SharePoint 2010 Support

That’s when it all ends. Well… For the most part. That date represents the 5th anniversary of SharePoint 2010 being released to the world. It also marks the closing out of what Microsoft calls mainstream support. This doesn’t mean that you’ll be unsupported, there’ll still be options there but they’ll just cost you more. Potentially a lot more. To fully understand how this works for SharePoint 2010, let’s have a look at how Microsoft support cycles tend to work.

  • 5 years onward from a product launch, Microsoft provide what’s known as mainstream support. This includes:
    1. The ability to request design changes
    2. Security updates
    3. Non Security updates
    4. Complimentary support
    5. Paid SharePoint 2010 support
  • 5 years onwards from the end of mainstream support, Microsoft will move a product into Extended Support. This is similar to the above but minus the (very, very) important perks of non-security updates or service patches. Support calls are typically charged fully regardless of what the root issue cause is.

For those not used to Microsoft language, this might not seem like a great deal, but it can be and it’s important to understand it fully.

The potential to be charged for a SharePoint 2010 support call, even if the underlying problem isn’t of your own making is one thing. It’s another entirely to see any form of patching removed entirely beyond security patches. These two factors combined mean that any issues that arise will only be resolvable with lots of time and/or money.

Critical Upgrade Path

While the situation above is far from perfect for many, there are alternative options, it isn’t all quite that bad. Upgrading to a newer platform will remove most of this issues above, and there are several pain free routes that can be taken to achieve this.

Read more