I know what the role and responsibility we take regarding the Data Box, but as of now we do not provide the solution to the end customer. We only do the cases where the data size is not high. Wherever the data size would be huge, such as 5 TB or 10 TB, then we might require the Data Box or Data Disk to transfer the data from their on-prem server to the Azure Cloud. I personally take part in deployments. The time I spend on deployment of Azure Resource Manager totally depends on the commercial shared with the customers and how many resources are there. Based on that, we can configure different resource groups. It takes no longer than an hour or two hours. We configure the separate resource group if we have multiple deployment plans for the UAT or production. I have not found any weak points against Azure Resource Manager as of now. The RBAC policies provide the end customer access as per their requirement, whether contributor access, admin access, or read-only access, which can be defined in the policy assignment, enabling user access based on the assigned policies. I employ access control and tagging capabilities. I talk about access control specifically for the storage account, where we provide access control to the particular user with read and write access policies that we apply in the portal based on those policies users can only access what they are assigned. We do not do the compliance management activity with the help of ARM or Terraform; we only use the template for resource deployment manually for policy assignment. On a scale of 1-10, I rate Azure Resource Manager a 10.