Azure Resource Locks - Impact of ReadOnly Lock on RG1 in Azure Portal

C

ReadOnly allows authorized users to read a resource, but they can't delete or update the resource. Applying this lock is similar to restricting all authorized users to the permissions granted by the Reader role.

When you apply a ReadOnly lock to a resource group in Azure, it restricts all types of modifications or updates to the resources contained in that resource group. However, it still allows read operations, such as viewing the resources and their properties, but not any modifications.

So, with the ReadOnly lock applied to the RG1 resource group, you can perform the following actions from the Azure portal:

A. Start VM1 - You cannot start VM1, as starting a VM is a modification operation that requires write access to the resources. Therefore, you cannot perform this action while the ReadOnly lock is applied.

B. Upload a blob to storageaccount1 - You cannot upload a blob to storageaccount1 as it requires write access, which is not possible when a ReadOnly lock is applied to the resource group.

C. View the keys of storageaccount1 - You can view the access keys of the storage account as it's only a read operation and doesn't require write access.

D. Generate an automation script for RG1 - You can generate an automation script for RG1, as it's a read-only operation that doesn't require write access to the resources.

In conclusion, only option C (View the keys of storageaccount1) and option D (Generate an automation script for RG1) are possible actions that you can perform from the Azure portal with a ReadOnly lock applied to RG1.