As I am into banking services, I work for a bank where the tool plays a critical role. People cannot just configure the tool the way they want, as it is a public cloud. There are some risks and compliance needs that need to be followed. Whatever the templates get approved by the governance and risk team, the provisioning team or deployment team should be easily able to select the template without any hassle and then start provisioning the service according to the requirements. The tool's most beneficial feature for managing resources revolves around how we can define the hierarchy and how that will help us manage different things. For example, if you want to apply a policy on a particular resource manager, you can do that. With Azure Resource Manager level, you can just apply it, and it will be cascaded to all the areas below in the hierarchy. If you want a breakup, cost at a hierarchy level. For example, you can define for a group or a particular team that these are the resources, or you can decide which part is only for storage and which part is particularly for VMs, allowing you to organize it all in different ways. You can implement your policies, and you can easily apply them to the intended groups or set of resources and monitor the costs at a resource group level. I don't see anything is required when it comes to the maintenance part as it is for logical grouping and setting up of templates. There is nothing like maintenance needed. There is nothing like billing for it, so there is no maintenance involved. My company uses other cloud services as well, while Azure Resource Manager is used by me. Corporate needs are different. I don't have much insight into it to be able to comment on it. I spoke about my own experience with the tool. I would like to set up my own product in the cloud environment soon, and that is how the journey started. I recommend others to use the tool. The tool is helpful for grouping features. With Azure Blueprint lines, it is good for governance and compliance and Azure Resource Manager is really handy for those who are very security and risk conscious. The tool was not used to support any AI-driven projects. I rate the tool a nine out of ten.
I give the solution a seven out of ten. There is no limit to what can be done with Azure Resource Manager Templates, as they are just APIs and are fully documented. However, they can be difficult to maintain. I started using the solution because it was the only one to provision at the time. We can use the solution in some cases, but it is not suitable for all projects. We must adhere to the requirements; for instance, Terraform is usually the preferred choice as it has the state, but there are times when Azure Resource Manager Template is more suitable as Terraform has limitations that Azure Resource Manager Template does not.
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's important to monitor costs. There are a lot of things that can be done to reduce the cost of the solution and it's easy to reduce the resources lying around. You have to monitor closely what you're using. I would rate this solution a nine out of 10.
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.
Overall, I rate the solution an eight out of ten.
As I am into banking services, I work for a bank where the tool plays a critical role. People cannot just configure the tool the way they want, as it is a public cloud. There are some risks and compliance needs that need to be followed. Whatever the templates get approved by the governance and risk team, the provisioning team or deployment team should be easily able to select the template without any hassle and then start provisioning the service according to the requirements. The tool's most beneficial feature for managing resources revolves around how we can define the hierarchy and how that will help us manage different things. For example, if you want to apply a policy on a particular resource manager, you can do that. With Azure Resource Manager level, you can just apply it, and it will be cascaded to all the areas below in the hierarchy. If you want a breakup, cost at a hierarchy level. For example, you can define for a group or a particular team that these are the resources, or you can decide which part is only for storage and which part is particularly for VMs, allowing you to organize it all in different ways. You can implement your policies, and you can easily apply them to the intended groups or set of resources and monitor the costs at a resource group level. I don't see anything is required when it comes to the maintenance part as it is for logical grouping and setting up of templates. There is nothing like maintenance needed. There is nothing like billing for it, so there is no maintenance involved. My company uses other cloud services as well, while Azure Resource Manager is used by me. Corporate needs are different. I don't have much insight into it to be able to comment on it. I spoke about my own experience with the tool. I would like to set up my own product in the cloud environment soon, and that is how the journey started. I recommend others to use the tool. The tool is helpful for grouping features. With Azure Blueprint lines, it is good for governance and compliance and Azure Resource Manager is really handy for those who are very security and risk conscious. The tool was not used to support any AI-driven projects. I rate the tool a nine out of ten.
I give the solution a nine out of ten. Azure Resource Manager is the best option available and I recommend it to others.
I give the solution a seven out of ten. There is no limit to what can be done with Azure Resource Manager Templates, as they are just APIs and are fully documented. However, they can be difficult to maintain. I started using the solution because it was the only one to provision at the time. We can use the solution in some cases, but it is not suitable for all projects. We must adhere to the requirements; for instance, Terraform is usually the preferred choice as it has the state, but there are times when Azure Resource Manager Template is more suitable as Terraform has limitations that Azure Resource Manager Template does not.
On a scale from one to ten, I would give Azure Resource Manager a six.
It's important to monitor costs. There are a lot of things that can be done to reduce the cost of the solution and it's easy to reduce the resources lying around. You have to monitor closely what you're using. I would rate this solution a nine out of 10.
If customers are looking for this kind of management tool for monitoring, I would recommend it. I would rate Azure Resource Manager a ten out of ten.