Skip to main content

6 Reasons Microsoft's LinkedIn Acquisition is Different



For anyone left who thinks that Microsoft is the same company it was in the heyday of Windows, today's acquisition of LinkedIn shows just how far Microsoft is willing to go in pursuit of its long term vision.

How is this acquisition different from earlier acquisitions?

  1. Microsoft is acquiring the leader.  Similar to the Skype acquisition, Microsoft is gaining market share from a top player and not an also-ran. 
  2. Microsoft's timing for cloud and social is right. Microsoft comes into this acquisition with strong momentum of Office 365 and Dynamics CRM Online cloud growth.
  3. LinkedIn targets business rather than consumer users. The business market is more conservative and less likely to flit from one social network to another.  
  4. Paid and free services go well together. Microsoft offers a strong sales channel and field sales presence that create new opportunities to monetize LinkedIn.  Free users create a steady stream of prospects for the combined product and service offering. 
  5. The target customers of Microsoft and LinkedIn overlap. Office 365 is a potential jumping off point for LinkedIn (and vice versa) and a large number of current customers use both services. 
  6. Microsoft CEO Satya Nadella is on a roll. In his memo explaining the acquisition, Mr. Nadella points to new customer experiences that will be made possible in Office 365, Dynamics CRM and LinkedIn.  He has energized Microsoft's leadership and shown the boldness needed to make further progress. 

The possibilities of using LinkedIn data to improve sales and marketing are tantalizing.  What if you could integrate Office 365 messaging with LinkedIn paid subscriptions for messaging?  Could you post directly from Office 365 to LinkedIn groups?  How about building a marketing list in Dynamics CRM of your LinkedIn connections and invite them to an online event?

The LinkedIn acquisition answers the question of how Microsoft will use its cash to increase its competitiveness for the long haul.  It may produce results in the short run and change the behavior of Microsoft's competitors.




Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises