There is a lot of news out there about the acquisition and what it means. One question that is interesting to the data center community is what happens to LinkedIn's data center infrastructure when they are part of Microsoft.
Let's start with the press release which is here. http://news.microsoft.com/2016/06/13/microsoft-to-acquire-linkedin/#sm.0001oz1nmex7gedxpaa28q5zji3ou
So part of making the LinkedIn customers feel good is to let them know the brand and culture will be maintained and LinkedIn will be independent. Satya then states with Microsoft LinkedIn will grow faster while supporting growth of Office 365 and Dynamics. And, there will be a combination of Microsoft's Cloud and LinkedIn's network.
So the independence is for the brand and some teams in LinkedIn, but not the team that runs the DC infrastructure which includes the data centers, network, and some software services. An example of a software service is the ability to sign-in to LinkedIn with a Microsoft sign-in. Simple. what about the data center infrastructure that will be connected to the Microsoft Cloud? Not so easy.
Where is LinkedIn's DC infrastructure? They celebrated their last move from retail to wholesale space in this blog post. https://engineering.linkedin.com/blog/2015/11/introducing-linkedins-west-coast-data-center. This post announces their green data center efforts in Informart's data center in Hillsboro.
When LinkedIn made decisions on its datacenter locations it focused on how best to service their users. Now their biggest user and their owner Microsoft needs to be served. And part of that service is lower latency and higher bandwidth connections to Microsoft's Cloud. It's a long ways from Hillsboro to Quincy, WA. Seems things would work so much better if LinkedIn was at the same site as Microsoft's cloud.
DatacenterKnowledge reports on the other LinkedIn locations. http://www.datacenterknowledge.com/archives/2014/02/12/linkedin-will-add-third-data-center-next-year/