Content Comparison

Create role for Storage Account keys access

The built-in role "Reader" may not have required permissions

...

, such as default access to the Storage Account keys

...

necessary for collecting data about VHDs

...

Create a Custom Role

...

.

1. In the Azure portal, open select a subscription or a resource group where a custom role is should to be assigned to.

2. Open 'Access control (IAM)'. Click Add → Add custom role. Name the role CloudAware Cloudaware Custom Policy.

...

3. Select one of the following options to proceed:

a) 'Start from scratch'.

Open the tab Permissions → Add permissions. Copy and paste Microsoft.Storage/storageAccounts/listKeys/action in the Search for a permission box to select Microsoft Storage. Check the box near the permission. Click Add.

...

Click Add.

b) 'Start from JSON'.

Use the JSON template below to create a file. Fill your subscription id in the {subscription_id} field.

...

*Commonly used Azure built-in roles:

Read more

Open the tab 'JSON' to check and modify the permissions (see 3 a) if necessary. The JSON body of the existing role should look like in the template below:

...

Replace {your-existing-Role-definition-id} with your role definition id. In the section "AssignableScopes" add the string "/subscriptions/{subscription-id}" with your {subscription-id}.

4. Assign the If you add a native application, assign the created custom role to a user in case you are adding a Native application, or to the application in case you are adding a Web app/API.

...

. If you add a Web app/API, assign the role to the application.

5. Open the tab 'Review + Create'. Check the role details and click Create.

...

Create role for tagging

Anchor
#Custom-role-for-tagging #Custom-role-for-tagging

Another use case for creating Create a custom role is a necessity to provide Cloudaware with minimum permissions for tagging Azure resources.:

"properties": {
        "roleName": "{your-Role-name}",
        "description": "{your-Role-description}",
        "assignableScopes": [
            "/subscriptions/{subscription-id}",
        ],
        "permissions": [
            {
                "actions": [
                    "Microsoft.Resources/subscriptions/tagNames/read",
                    "Microsoft.Resources/subscriptions/tagNames/write",
                    "Microsoft.Resources/subscriptions/tagNames/delete",
                    "Microsoft.Resources/subscriptions/tagNames/tagValues/read",
                    "Microsoft.Resources/subscriptions/tagNames/tagValues/write",
                    "Microsoft.Resources/subscriptions/tagNames/tagValues/delete",
                    "Microsoft.Resources/subscriptions/resourceGroups/read",
                    "Microsoft.Resources/tags/write",
                    "Microsoft.Resources/tags/delete",
                    "Microsoft.Resources/tags/read"
                ],
                "notActions": [],
                "dataActions": [],
                "notDataActions": []
            }
        ]
    }

Replace {your-Role-name}, {your-Role-description} and {subscription-id} with corresponding values from your Azure environment.

Update

...

existing Cloudaware custom policy

Cloudaware may regularly introduce new capabilities which that require addition of new additional actions and permissions. In cases If a Cloudaware custom role is already existsin place, you can update this role without updating it for every subscription. If updating an existing Cloudaware Custom Policy role is required, your it can be updated once across all subscriptions. Cloudaware Technical Account manager will provide you with instructions on how to perform this actionthe instructions.