Over the next week, we’ll be releasing three reports related to Azure Policy, and we’re excited to say the first of those three has been released!
The Policy Assignment Asset Report lets you view the current state of each Policy Assignment and the number of compliant and non-compliant resources. You can also select a specific Policy Assignment to see which individual resources are compliant and non compliant.

This will be an asset report that will allow you to track the compliance status of individual resources. As teams act upon alerts for non-compliant resources, this report will allow you to track when those resources become compliant again.
This will be the overall summary report where you’ll be able to get a high level view of the state of the Azure Policy Assignment by subscription, with links to drill into specific resources and metrics. These links will bring you to filtered views of the aforementioned asset reports to give different lenses into the data.
As part of our effort to more directly help you quantify your (high level or low level) KPIs, and operationalize how they are measured and how actions are driven against them, we are releasing the first of a number of new discount (e.g. RIs, Savings Plans) related KPIs. This first release is specific to AWS EC2 discounts “Coverage”; identifying how much of your EC2 spend is covered by a discount mechanism (normalized to On-Demand rates). This will help you answer for example, (at an account level, or organization level, or perspective level, etc) how much of your EC2 spend, that would have otherwise been On-Demand, was covered by Savings Plans, RIs, Spot, or was left On-Demand.
This Coverage measure currently lives in the CloudHealth AWS Savings Report. Soon you will see a summarized view in a custom dashboard rack that will appear by default in the Savings Plan Dashboard. Clicking on this rack will bring you into the Savings Report to introspect further. The dashboard summary rack will show you how the entire organization is doing, and users can complement this by bringing in specific configurations of the Coverage measures in the Savings Report into dashboards as a widget, to see how different business groupings are tracking on this KPI. These KPIs also tie back into how incremental commitments in the Savings Plans Recommendations Report will affect your target coverage rates. We’re looking forward to learning more about how you’re operationalizing “Coverage” based KPIs and how CloudHealth can help. Note: similar to the “Coverage Type” dimension for EC2 reports that was introduced after AWS introduced Savings Plans back in November, data for this KPI is available starting in July 2019.


AWS Single Sign-On makes it easy for end users to sign into the AWS Console and access applications with a single set of credentials. Until now, you had to sign in to the AWS Console to work with AWS resources, and then had to sign in separately to CloudHealth to analyze and manage your computing environment or the resources in your environment.
Learn how to connect CloudHealth with AWS SSO using SAML 2.0, so you have a single experience to access both the AWS Console and CloudHealth.
We have added tag support for Elastic IP Addresses – you can see this reflected in the CloudHealth platform under Assets > By Service > AWS > EC2 > Elastic IPs. You can use the tags to allocate related assets and charges into Perspective groups, and run configuration policies based on tagging. Remember, CloudHealth tags take precedence over AWS tags. For better sync and reporting of Elastic IP Address tags created in your AWS environment, please remove any CloudHealth account tags that overlap with them or are exact copies of them.