Driving Azure Profitability: HealthCheck for Azure FAQ

Last week we hosted a webinar that explored Azure assessments powered by HealthCheck for Azure. If you aren’t familiar, HealthCheck for Azure is an amazing infrastructure assessment tool that provides detailed readiness reporting, cost analysis, and planning tools to help your customers make the most informed decisions when considering a move to Azure.

We had a boatload of great questions from webinar attendees, and wanted to share the answers with you in this FAQ. Check it out!


Are there any limitations to the types of infrastructures HealthCheck for Azure can assess?

Nope! You can assess any and all servers and workloads, physical and virtual.

What are the agent install requirements? What about impact to servers?

The only requirement for the server is the OS: Windows or Linux. The agent is incredibly lightweight and doesn’t use much disk space or impact server performance over the 14-day collection period. In the event it reaches a certain utilization, the agent will shut itself off.

Why collect data for 14 days?

We recommend a 14-day collection period to provide more accurate information of usage patterns, rather than looking at a snapshot of usage in time. This helps your customer make the most informed decisions when exploring what-if scenarios and right-sizing instances in Azure. Soon, you’ll be able to customize the length of time for an even longer assessment period, should you choose.

Can I run HealthCheck on Azure VMs?

It’s something we are building right now. Please reach out if you’re interested!

How is the Azure pricing calculated? What if I have an EA or CSP pricing?

The pricing is based on the Azure Pricing API. If you have an EA or CSP pricing, you can add discounts within the tool, and we can also help you define a design based on your situation. We can also factor regional cost differences depending on which datacenter the customer would use. Get in touch with us to us to learn more.

What’s the difference between “Hardware, pay-as-you-go” and “Workload, pay-as-you-go”?

“Hardware, pay-as-you-go” is what we also call a “lift-and-shift” model, meaning you’re recreating the current infrastructure in the cloud as closely as possible to the current operating model.

“Workload, pay-as-you-go” lets you look at the same infrastructure (or by machine) but right-sized. There may be ways to restructure the workload to for better efficiency and lower costs. It is recommended because this is where you’ll often see the most savings for your customer, including the ROI from right-sizing.

After collecting the data, does the tool automatically generate TCO and build an analysis report?

It takes about two days after data collection to generate the report. But the report won’t have all the answers—it’s up to you to act as the consultant, between interpreting the data and aligning what-if scenarios with your customer’s immediate needs and long-term goals.

Can I export the results data to put into a tool of my choice?

You can export raw data as an Excel document to then upload into other programs.

Is HealthCheck for Azure available through any incentive programs?

Yes! If you’d like to learn more and find out if you qualify, check out this blog post!

Can I do a trial to see what HealthCheck for Azure is about?

We can give you 10 licenses for Internal Use Rights to see how it works. Contact us to learn more.

I missed the webinar. Can I watch the recording?

Yes, please! You can view it on-demand here.

About the author

Spencer Czapiewski

Spencer Czapiewski is a senior staff writer for ModernMSP. A Seattle native with a passion for writing and marketing, he loves putting narrative and lightheartedness into his technology content.

Leave a Reply

Be the First to Comment!

Notify of