We’re pleased to announce the general availability of Oracle Cloud Infrastructure (OCI) support, as announced at VMworld 2020. As mentioned in the beta announcement, the following functionality is supported for OCI:
Dashboard: Cost and usage overview with historical cost segregated by service categories. Customers can build their own dashboards using saved reports.
Cost History Report: Ability to slice-and-dice cost across Oracle Cloud services, compartments, and Perspectives with cost drill down showing resource level cost details
Compute Usage Report: Visibility into usage hours for compute shape resources
Multicloud Cost Report: OCI is now included in this report so you have a single point of reference across clouds
Perspectives: Ability to create dynamic business groups based on resource tags, compartments, derived assets, regions, and VMs
Asset inventory and reporting: Visibility into OCI compartments, a comprehensive list of assets, and API-driven reporting on Oracle Virtual Machines
Budget: Create and track your OCI budget and report on budget vs. actual spend
Learn more about the CloudHealth Oracle Cloud solution in this Help Center article.

We’re pleased to announce that we’ve entered public beta for FlexOrgs Local and Shared Perspectives for AWS. This release allows for:
Perspectives to be selected as shared from the top level throughout your FlexOrgs hierarchy
Perspective creation to be available at all levels of your FlexOrgs hierarchy for AWS. Members of subOrganizations can manage their own subset of Perspectives that are contextually relevant to them.
Learn more about Local & Shared Perspectives for AWS in this Help Center article. If you’re interested in participating in this public beta, please email flexorgsbeta@groups.vmware.com to get started.


FlexOrgs is the new method for configuring your organizations in a hierarchy to align with how you do business. During our transition over to FlexOrgs, customers were required to have their top level organization operate as a “classic” organization resulting in complexity for user access management. Customers needed to maintain both the old concept of users and roles for the top level organization while also configuring role documents and user groups for all of your FlexOrgs. We’re happy to announce that is no longer the case. You are now able to have a complete FlexOrgs experience where you only need to manage role documents and user groups.
For existing customers: Contact your Technical Account Manager to plan a switch over for your top level organization. We want to engage with you to ensure a seamless experience.
For new customers: All new customer tenants that are created going forward will have an entirely FlexOrgs experience.
For MSPs: Stay tuned. We’re working on bringing this same experience to you too, but this is available for your customers now.
With the introduction of FlexOrgs, user accounts now exist in many organizations instead of just one. When creating automation or querying CloudHealth APIs it wasn’t always clear what Organization your query was executed within. In order to drive the effectiveness of our APIs this change now allows you to be explicit about the Organization in which you would like to execute your query. We have introduced an optional argument called ‘org_id’ to specify which Organization ID you would like to run against. This is supported in the following APIs:
Asset API
Reporting API
Perspective API
Metrics API
Organizations API
AWS Account Configuration API
We have added support for Glacier Deep Archive in our Cost, Usage, and Metrics Reports for Amazon S3. We now have two new Y-Axis measures for ‘Glacier Deep Archive - Overhead’ and ‘Glacier Deep Archive - Storage’ in the S3 Cost and Usage Reports. In the S3 Metrics Report, we’re introducing eight new columns for Max, Min, Avg, and Sum.


We have released our first phase of support for Azure Spot VMs. For Spot VMs, you can now view the spot-specific metadata on those resources by using ‘Edit Columns’ on the VM Asset Report or by clicking into an instance and switching to the Spot menu.

For years now, CloudHealth customers have been able to distribute the costs of shared cloud compute resources used by their containerized applications, based on how many resources various components have requested to be provisioned, answering the question, what costs should be associated with each namespace, or each app, or each team, etc. Soon you will see an enhancement to this capability, which will allow for multiple distributions of those costs that support containerized applications, for example, being able to measure the costs of a cluster split by namespace, product line, or team. You should note that this new capability will require you to select the cost distribution rule of choice in the Containers Cost History Report via a new drop down selector. As a result, report links will need to be updated. We will begin updating Saved Reports and Subscriptions for you to incorporate this link change, but we ask that you double check these changes and also update your saved bookmark links.
We’re in the final stages of releasing support in GCP for creating more granular Perspectives! With this functionality, you will now be able to allocate your costs to Perspective Groups based on labels that have been added at the resource level. In addition to allocating costs based on the resource label, you’ll also be able to allocate GCP cost SKUs to Perspective Groups for granular cost chargeback.
To use this feature, you will need to configure the BigQuery billing export. If you have not done that yet, please view this Help Center article.
We’re actively building a new user interface for the top and side navigation bars in the CloudHealth platform. This change will introduce more consistency across our software portfolio and will help make navigation more intuitive.
Please note that the navigation of CloudHealth will not fundamentally change with this update. You will not lose access to any functionality nor have we changed the access to any part of the application.