Policies excluding subscriptions, and accounts from anomaly object policies

Products

• CloudHealth

Issue/Introduction

Under the "AWS Anomaly" and "Azure Anomaly" resources types you can filter cost impact blocks by account or subscription. The filter offers both the option to include or exclude accounts/subscriptions currently but if you make use of the exclude option you will find that the policy won't fire currently. 

This is due to a platform limitation for the two resource types mentioned above, you can workaround this by providing the inverse filter via the include option however.

Resolution

To workaround the issue please take these steps:

1. Note down any accounts or subscriptions you have selected under the exclude filter. 


2. Switch the filter from exclude to include, and then use the select all function.


3. Untick the checkboxes associated with the accounts / subscriptions you wish to exclude the policy from reporting on.