Custom tags on azure backup

I’m wondering if the policy is stopping the VSA from adding tags?  What kind of error message do you see?

Might be worth a support case, though I’d like to see what we can figure out here as well.

Hi Mike, 

The policy does not stop the VSA from adding tags, it stops a resource without the custom tags to be created.

The error messages indicate that a snapshot is not being able to be created due to the customer required tags are needed. In fact there are multiple different tags they require, including department and company. Some of these are inherited if empty, but another (facilitator) is required on the resource to be allowed to be created.

These tags are not the ones set by commvault, and we do successfully backup the vm if we set the policy to audit (for the facilitator tag which are missing) and still require the inherited ones.

The question still applies, are we able to define a set of custom tags to push when creating the snapshot, in addition to the tags commvault currently adds, to be able to adhere to the local policy.

Or do I have to tell the customer to exclude snapshots from this policy. Same rules will also apply on restores, haven’t yet tested if tags are protected/restored from customer VM. Customer has these rules to ensure that all resources are being billed to the correct department and could also be using this for other usecases as well.

As a supportcase goes, its not really needed as the error is customer configuration of azure teanant. I do know why it errors and how to resolve it by setting policy in audit mode for the time beeing. 

If we currently do not have the ability to set custom tags, I will work with customer to see if we can work around the policy requirements.

@wgrande Thanks. I will check these.

This solved my issue. The snapshots are now assigned the correct tags, as long as the VM has it as well.