Licensing changes started the EUC conversation. Operations is finishing it.

If you run a large virtual desktop environment, you’ve probably been in this conversation lately. A renewal comes in with new terms, and someone asks whether it’s time to see what else is out there. From there, many people assume the decision comes down to price. 

The Great Migration, our new independent research of 175 enterprise EUC decision-makers, tells a different story: price is often what gets the evaluation started, but once a team begins looking, other priorities start to shape what they choose. 

Pricing changes moved the market from waiting to acting

In the research, 63% of respondents said pricing and licensing changes have accelerated their end-user computing (EUC) modernization plans or become a primary driver. That marks a real shift from a few years ago, when most organizations were still evaluating alternatives and are now acting on them. You can see it in how renewals get handled. A contract that used to get signed in the last week of the quarter now arrives with a project plan, a named owner, and a decision date, so what had been a loose intention to modernize someday has become a deadline. 

If the findings stopped there, the common story about price driving the market would hold up. But the survey also asked what is behind modernization decisions, and when respondents answered that question, the list looked quite different. 

Price isn’t what enterprises are solving for

When the survey asked what was driving modernization, operational priorities ranked well ahead of cost. Modernizing legacy environments ranked first at 50%, and automation and operational consistency, security and compliance, and leveraging existing Microsoft investments each landed at 47%. Optimizing licensing and infrastructure costs came in at 30%, which puts it 17 to 20 points below the operational drivers. Pricing pressure often gets an organization to start looking, but once the evaluation is underway, most of the conversation turns to how the environment will run day to day. 

If you’ve been through one of these evaluations, you’ve probably seen how it plays out. The first meeting usually centers on a spreadsheet comparing per-user costs. By the third or fourth, the questions have shifted to how images get built and patched, how long a new hire waits for a working desktop, who gets the call when a session host goes down at 2 am, and how much of the Microsoft licensing the company already pays for is sitting unused. The renewal date sets the schedule for those meetings, and the operational questions end up taking most of the time in them. 

That can put IT leaders in an awkward position, since the executives they report to tend to ask about cost first. A per-user price is easy to put on a slide, while the hours a team spends keeping an environment running rarely appear in any budget line, so the two don’t get weighed on equal footing. A platform that costs less per seat but still requires the same manual effort next year has moved the expense somewhere harder to see, and the total hasn’t gone down. Licensing changes got most enterprises to the point of making a decision, but they say very little about which platform those enterprises will end up choosing, and a decision based on price alone answers a question that most of them have already moved past. 

What to ask if you’re facing a renewal

If a renewal or platform evaluation is coming up, price will be part of the conversation whether or not anyone brings it up. A few other questions are worth putting next to it: 

• How will this environment be operated day to day, and which team owns each part of that work? 
• How many other platforms will we be running alongside it, and how does that affect the workload of the people supporting all of them? 
• Which tasks can be automated, and which will still depend on someone logging in to a console? 
• How well does it fit the Microsoft investments we’ve already made? 

None of these gives you a number you can drop into a cost model, which is probably why they tend to get skipped. They matter anyway, because the answers decide whether your team is still working through the same problems two years after the contract is signed. 

It also helps to ask these questions of more than one group, since each one sees a different part of the environment. The engineers who run it today know where the hours actually go, whether that’s manual image updates, scripts only one person understands, or exceptions that piled up over several renewals. Your security and compliance teams will have their own concerns, and so will whoever manages Microsoft licensing. If you collect those answers before the first vendor conversation, you end up with a baseline, and you can measure each option against the work your organization really does instead of against a vendor’s feature list. 

Those same answers are useful when you talk to executives. Leadership usually asks about cost first because it’s the easiest thing to compare, so it helps to arrive with more than a price. If you can explain what each option would take to operate, how much of that work could be automated, and how much of your existing Microsoft spend it would put to use, you’re giving them a fuller picture to base the decision on. 

What the full report covers

This finding is one part of a larger set of results. The report also covers what enterprises say they will prioritize next and what separates the organizations that are further along from the ones still working out their approach. 

Download The Great Migration report to see the full research.