InvestorPlace InvestorPlace - Stock Market News, Stock Advice & Trading Tips
Salesforce.com, Inc. (NYSE: CRM ) is attempting to block Microsoft Corporation's (NASDAQ: MSFT ) offer to acquire LinkedIn Corp (NYSE: LNKD ).
The acquisition of LinkedIn by Microsoft would allow the tech company access to LNKD's data for more than 450 million professionals. Salesforce argues that MSFT could deny this information to competitors. The cloud computing company said this could threaten "the future of innovation and competition."
Microsoft is offering $26.2 billion for LinkedIn. This beat out Salesforce's own offer for the social media network for professionals. However, CRM may still be interested in obtaining a social media company. Rumors claim that it is interested in buying Twitter Inc (NYSE: TWTR ), reports CNNMoney .
Microsoft has countered Salesforce's arguments by pointing out that it is "committed to continuing to work to bring price competition to a CRM market." It went on to note that the cloud company charges higher prices in that market than it does.
Microsoft doesn't appear to be worried about Salesforce's complaints. It pointed out that the deal has already been approved by regulators in the United States, Canada and Brazil. It expects to close the deal by the end of 2016, if regulators approve.
Salesforce may have better luck convincing antitrust regulators in the European Commission to block the deal. Margrethe Vestager, an antitrust chief from Denmark, said the organization should look more closely at mergers concerning valuable data.
More From InvestorPlace
- 7 Stock Charts to Watch in October
- 7 Make-or-Break Earnings Reports Coming in October
- 5 Stocks to Sell for October
The post CRM, MSFT, LNKD: Salesforce.com, Inc. Aims to Block Microsoft Corporation-LinkedIn Corp Deal appeared first on InvestorPlace .
The views and opinions expressed herein are the views and opinions of the author and do not necessarily reflect those of Nasdaq, Inc.
The views and opinions expressed herein are the views and opinions of the author and do not necessarily reflect those of Nasdaq, Inc.