Azure VMs are good value for money
March 27, 2022

Azure VMs are good value for money

Filip Grasheski | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Azure Virtual Machines

We use VMs for many different purposes:
- Isolated development machines for working with Azure cloud services.
- Hosting Jenkins master server used to deploy our Azure-based applications.
- Hosting Jenkins agents for CI/CD pipelines which are built on separate VNETs for dev, test, sim, and prod.
- Azure Data Factory integration runtime to run ADF pipelines.
  • Very easy to spin up.
  • Low amount of maintenance.
  • Low cost when using reserved instances.
  • Flexible in terms of supported OSs.
  • Additional security risk that needs to be managed.
  • Complexity to make replicas of a VM.
  • Potentially build and forget in larger enterprises which will drain money.
  • Allowed developers to use machines without the necessity of purchasing additional hardware.
  • Paying for computing and storage for distributed systems as opposed to self-hosted hardware would be more expensive.
In comparison with AWS EC2, it is easier to deploy using the GUI, when it comes to using CLI is pretty much the same.

Do you think Azure Virtual Machines delivers good value for the price?

Yes

Are you happy with Azure Virtual Machines's feature set?

Yes

Did Azure Virtual Machines live up to sales and marketing promises?

Yes

Did implementation of Azure Virtual Machines go as expected?

Yes

Would you buy Azure Virtual Machines again?

Yes

Using a self-hosted integration runtime with Azure Data Factory, although only supports Windows, will make it more expensive. Hosting DevOps tools, such as Jenkins, code scanners, etc. can be set up very easily and replicated if needed. Any kind of distributed architecture, like Selenium grid for GUI testing of applications, can be set up very easily because of the myriad of possibilities for OSs.

Azure Virtual Machines Feature Ratings

Virtual machine automated provisioning
10
Hypervisor-level security
5