Gartner Blog Network


Microsoft MQ Updates – Results are Mixed

by Merv Adrian  |  October 19, 2015  |  2 Comments

Each quarter, I update my quarterly map of the several dozen Gartner Magic Quadrants that feature Microsoft offerings. Previous posts include December 2014’s Microsoft’s Product Positions – Positive Progress, March’s Microsoft in MQs – March On,  and July’s Microsoft in MQs – June is Bustin’ Out.  This post follows the end of a fiscal year with quarterly revenue of $19.90 billion for the quarter ended June 30, 2015 and management shifts that are reshaping the company for its new fiscal year.

As always, the reports shown in bold have been refreshed  in the past 12 months; the ones in italics are appearing for the first time in this version of the chart. Next time, everything will be reset and only updated and changed ones from that quarter will be typographically emphasized. This time, Corporate Telephony moved left to Challenger, and Web Content Management moved down to Niche Player. Mobile Application Development Platforms and Mobile Data Protection moved up to Challenger, and Secure Email Gateways moved right into the Leader quadrant.

Screen Shot 2015-10-18 at 10.54.26 PM

Category: gartner  industry-trends  magic-quadrant  

Merv Adrian
Research VP
5 years with Gartner
38 years in IT industry

Merv Adrian is an analyst following database and adjacent technologies as extreme data transforms assumptions about what to persist as well as when, where and how. He also watches the way the software/hardware boundary… Read Full Bio


Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.