What is our primary use case?
We are using it in our company and the customer's company as well. So, it works on both sides. For certain development environments, we need to build our internal environment, and we need it for that. Similarly, we need to build the production environment for the customer, and we use it for that.
What is most valuable?
The beauty of Azure is that most of the features are easily accessible. It is user-friendly. Almost all resources in Azure are very easily accessible. For example, you can access a virtual machine, and you can scale it up. You can go ahead with different infrastructure-as-a-service in Azure for the platform or for the cloud. Different levels of development could be done using it.
What needs improvement?
It should be improved in terms of integrations. It could be integrated more with external tools.
We have Azure Purview for governance, but that is for data governance. For code governance, we have to use SonarQube or WhiteSource for vulnerabilities and license management. We would like to have a native code compliance tool.
For how long have I used the solution?
I have been working with this solution for three years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
It is scalable. The resources in Azure are scalable for a smooth transaction.
How are customer service and support?
Their technical support is very good. They are always easily available when we need them.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have been working with different automation tools such as Jenkins. Jenkins is a good tool to start with. Being a DevOps person, I had to go with Azure ADO and Azure DevOps, which basically gives you the view of how DevOps actually works.
How was the initial setup?
It is easy to set up. It takes you minutes to set it up.
What's my experience with pricing, setup cost, and licensing?
Azure has a subscription version. It has a pay-as-you-go subscription with a subscription ID. So, you have your particular subscription with an enterprise agreement. There is a dev-type subscription for development and testing.
The pricing seems pretty reasonable. The pricing could be per resource. For example, you have Databricks, Data Factory, Scaled DB, and Cosmos. You have everything in Azure. They have an Azure pricing calculator that you can use to check the price of every resource. It gives you a proper cost estimation. You can compare the cost and then go for the best resource for your project.
What other advice do I have?
I would definitely advise others to implement it as an infrastructure service only because you get to learn more. You get to explore the code more and know different steps. You can automate more and better. You can get automation done on top of what is already there, which could lead to another invention.
I would rate it an eight out of ten.