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.
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.