Compared to ARM templates, Terraform is often preferred because it is more versatile and user-friendly. With Terraform, you can create a single, generic script that works across multiple cloud environments, including AWS, Azure, GCP, and even Oracle Cloud. This eliminates the need to write separate scripts for each platform. ARM templates are specifically designed for use with Microsoft Azure and cannot be used with other platforms. In contrast, Terraform supports multiple cloud platforms, allowing you to easily provision VMs and other resources across different environments like AWS, Azure, GCP, and Oracle Cloud. It gives you more feasibility. It gives you more features. It is very useful for multi-cloud management. ARM templates should be enhanced to offer more flexibility and support new features. Ideally, they could be adapted for multi-cloud use. For example, if I write a template for Azure, I should be able to switch to AWS or GCP easily and have the same template create resources on those platforms. This would eliminate the need to write separate scripts for different clouds. If ARM templates were upgraded to support multi-cloud environments, our workflow would be greatly simplified.
I have not reached a level where I can provide input on improving the tool. I need to study other cloud services, and then only I can comment on how Azure differs from others. At a group level, if I apply a policy, it gets cascaded to all the resources underneath it, but it is not possible when it comes to tags. When I apply tags at a group level, it should go to the resource under it.
Data & Analytics Service, Associate Director at ACL Digital
Real User
2021-04-07T17:57:37Z
Apr 7, 2021
There is room for improvement. They have so many roles and contributors, but we primarily use three categories or the main contributor and reader roles. They have created a lot of other roles, but they are still not efficient enough to use. If you just use one service like Azure Data Factory, they also offer separate services, but they aren't as efficient as their main three roles. I would like Microsoft to at least work on that. For the last two years, I'm have been working on the services to try to come up with a different way or different control approach. But I have to use the three general roles like contribute, filter, and the reader. We aren't able to use the service days in roles because it's not working properly. It's not integrated, and it gives some people or one person one service day role. It won't be easy for him or her to work. I see they have defined many roles, including individual roles, but they aren't as good as the three main roles they have defined in Resource Management. I think they can work on that. They have created multiple roles, but I would rather they simplify the roles they already have. The main goal is to work with efficient data. Their support could also be better.
Digital Transformation Architecture, Manager at a tech services company with 1,001-5,000 employees
Real User
2020-12-03T07:55:29Z
Dec 3, 2020
It would be helpful if they would create a common line within the user interface so that if you want to automate or scale a reserve deployment, it can be done simply. It would mean running directly from the resource manager or finding a way to automate without using a common line.
The Azure Resource Manager (ARM) is the service used to provision resources in your Azure subscription. It was first announced at Build 2014 when the new Azure portal ( portal.azure.com ) was announced and provides a new set of API's that are used to provision resources.
Compared to ARM templates, Terraform is often preferred because it is more versatile and user-friendly. With Terraform, you can create a single, generic script that works across multiple cloud environments, including AWS, Azure, GCP, and even Oracle Cloud. This eliminates the need to write separate scripts for each platform. ARM templates are specifically designed for use with Microsoft Azure and cannot be used with other platforms. In contrast, Terraform supports multiple cloud platforms, allowing you to easily provision VMs and other resources across different environments like AWS, Azure, GCP, and Oracle Cloud. It gives you more feasibility. It gives you more features. It is very useful for multi-cloud management. ARM templates should be enhanced to offer more flexibility and support new features. Ideally, they could be adapted for multi-cloud use. For example, if I write a template for Azure, I should be able to switch to AWS or GCP easily and have the same template create resources on those platforms. This would eliminate the need to write separate scripts for different clouds. If ARM templates were upgraded to support multi-cloud environments, our workflow would be greatly simplified.
I have not reached a level where I can provide input on improving the tool. I need to study other cloud services, and then only I can comment on how Azure differs from others. At a group level, if I apply a policy, it gets cascaded to all the resources underneath it, but it is not possible when it comes to tags. When I apply tags at a group level, it should go to the resource under it.
The latency has room for improvement. The cost has room for improvement.
Unlike Terraform, Azure Resource Manager is hard to maintain and modularize and has room for improvement.
There is room for improvement. They have so many roles and contributors, but we primarily use three categories or the main contributor and reader roles. They have created a lot of other roles, but they are still not efficient enough to use. If you just use one service like Azure Data Factory, they also offer separate services, but they aren't as efficient as their main three roles. I would like Microsoft to at least work on that. For the last two years, I'm have been working on the services to try to come up with a different way or different control approach. But I have to use the three general roles like contribute, filter, and the reader. We aren't able to use the service days in roles because it's not working properly. It's not integrated, and it gives some people or one person one service day role. It won't be easy for him or her to work. I see they have defined many roles, including individual roles, but they aren't as good as the three main roles they have defined in Resource Management. I think they can work on that. They have created multiple roles, but I would rather they simplify the roles they already have. The main goal is to work with efficient data. Their support could also be better.
It would be helpful if they would create a common line within the user interface so that if you want to automate or scale a reserve deployment, it can be done simply. It would mean running directly from the resource manager or finding a way to automate without using a common line.
They can maybe improve the interface.