Microsoft's Software Licensing: Why I've Had Enough
Our company could be so much further ahead if Microsoft would simplify its licensing terms so that non-PhDs could understand them.
We take the approach at our company that our customers' success equals our own success. It's hardly a breakthrough concept. I've never worked for Microsoft, nor am I friends with anyone who does, but I bet that the value of customers' success isn't a foreign concept to Microsoft, either.
So why, then, does Microsoft force both employees and customers to waste what must be hundreds of thousands of hours per year trying to decipher its latest software licensing logic? Customers practically need an Enigma machine.
I understand the premise: Make the licensing so utterly complicated that customers sign your all-encompassing (or so you think) Enterprise Agreements, just to relieve the pain. "Sure, you can try to figure out how to buy from a Select agreement, but can you really afford the time to find all of the land mines we've planted in there?" goes Microsoft's thought process. It's not a clever approach; it's just annoying and inefficient.
Stop it. Now, please. I buy productivity software from a company that impairs my productivity whenever I deal with it. There's something really wrong here. Our Microsoft rep is unable to help us make the correct purchase decision, and he readily admits it. We could send our staffers to Microsoft licensing courses, I'm told. My initial reaction was to suggest that our rep attend the course.
It gets better, as Microsoft now offers "Licensing Training and Accreditation for Customers." In other words, if we invest even more time and money with Microsoft, it will bestow on us formal credentials saying we've mastered its convoluted licensing. At that point, can we then approve our own price proposal? We would be accredited, after all. No, all it would mean is that our arguments with Microsoft would continue longer than they do now.
Much of the wasted time in recycling the same issue is due to a difference in opinion. We read the licensing terms and pricing our way, and then Microsoft finds someone who interprets them another way. And then we argue. I'm also aggravated with Microsoft's insistence on including products in the deal that I don't want. The more strongly we indicate we're not interested in its CRM product, for instance, the more likely the company leads every discussion with a Microsoft CRM overview.
Microsoft organized a half-day demo for us, and we arranged for many of our senior executives to attend. Our main interest was to understand the value of unified video, voice, and data communications. We have a distributed organization, with many field offices and reps. The economics of person-to-person unified communications look solid. But change will be painful, as many of our senior execs have never used Skype or Facetime. The demo event was Microsoft's chance to show true added value. Maybe we should consider full Lync functionality.
So why did Microsoft spend the first two hours highlighting the benefits of its CRM software? More generally, why does Microsoft focus so intently on what it wants rather than what we need? Microsoft finally got around to the UC topics we were interested in hearing about, but not until after it delivered the full CRM pitch.
"Are we switching to Microsoft CRM?" was the first question Vic, our VP of marketing, asked me after the presentation. "It looks very powerful. Will it integrate with our other systems, like our home-grown CRM does? Are we going to retrain the sales organization? Have you budgeted for this, because I have not and that training is going to be expensive."
"No, we're not switching CRM systems!" I repeated numerous times over the next few days. I'm reliving my frustration just thinking about it.
My organization is simply trying to understand our pressing software needs and buy what we need. I dislike bundled channels on my cable TV, and I don't like Enterprise Agreements, either. Call me old school, but I want what I want and I don't want to pay for what I don't want. Neither do our shareholders.
We could be so much further ahead if Microsoft would simplify its licensing terms so that non-PhDs could understand them. And with the productivity savings, we just might have time to evaluate other Microsoft products.
I know what you're thinking: I should be spending my time with our Google Enterprise rep. I assure you, we're taking Google's offerings seriously. But my concerns are similar to those of my peers, as revealed in Art Wittmann's recent InformationWeek research report titled "Google in the Enterprise." Those include shortcomings in the areas of data security, integration with existing infrastructure, and Google's overall enterprise capabilities.
Among the top reasons companies are considering Google: end user demand, cost of purchase, ease of use, application availability, and ease of deployment. "CIO frustration with Microsoft and its licensing schemes" should be on next year's Google in the Enterprise survey.
There's no single migration path to the next generation of enterprise communications and collaboration systems and services, and Enterprise Connect delivers what you need to evaluate all the options. Register today and learn about the full range of platforms, services and applications that comprise modern communications, and collaboration systems. Register with code MPIWK and save $200 on the entire event and Tuesday-Thursday conference passes or for a Free Expo pass. It happens in Orlando, Fla., March 17-19.
Top IT Trends to Watch in Financial ServicesIT pros at banks, investment houses, insurance companies, and other financial services organizations are focused on a range of issues, from peer-to-peer lending to cybersecurity to performance, agility, and compliance. It all matters.
Join us for a roundup of the top stories on InformationWeek.com for the week of October 9, 2016. We'll be talking with the InformationWeek.com editors and correspondents who brought you the top stories of the week to get the "story behind the story."