Modern Commerce Multi-currency Support - Coming Soon

Beginning the week of February 1st, we will be adding the ability to apply currency conversion to costs incurred by Modern Commerce subscriptions. Using the currency setting in the tenant, you can now control which currency your costs should be viewed as.

Example: If some of your customers are being billed in EUR and others in GBP, but you select USD in the settings menu, we will convert the costs for all Modern Commerce subscriptions to USD.

To apply the conversion, we’ll first use a value in the Microsoft API that comes with each line item called exchangeRateDate which equals the day that the currency was calculated at. Then, we’ll do a lookup at the beginning of that day for the exchange rate using OANDA, and we’ll calculate using that rate.

If you currently have multiple currencies configured in your partner or customer tenants, or have updated the setting in CloudHealth to be something other than the Microsoft bill, please keep in mind that we will now convert those costs to reflect the currency in the settings menu.

Support for Azure EA in FlexReports

We’re excited to announce that CloudHealth FlexReports now support Microsoft Azure Enterprise Agreements (EAs). Previously, you were only able to create reports with data from AWS Cost and Usage Reports (CUR). Now, you will have an option to select AWS CUR or Azure EA and evaluate costs using various dimensions and filter criteria. 

The FlexOrgs organization hierarchy will be applicable to Azure EA data, and FlexOrgs is available as a 'dimension' in FlexReports for the Azure EA data set. Using this dimension, you can slice and dice data, segregated based on immediate child/sub orgs (one level down) of the organization in context. 

Learn more about CloudHealth FlexReports in this Help Center article and API documentation.

Updates to Azure CIS Security Policy

We have released the following policy conditions aligned with the Azure CIS 1.2 Foundations Benchmark. These are now available to be created as policy conditions:

• 3.6 Ensure default network access rule for Storage Accounts is set to deny 

• 3.8 Ensure soft delete is enabled for Azure Storage Blob Containers

• 3.9 Ensure storage for critical data are encrypted with Customer Managed Key

• 7.1 Ensure Virtual Machines are utilizing Managed Disks

• 7.2 Ensure that 'OS and Data' disks are encrypted with CMK Ensure that each disk is encrypted with CMK

• 7.3 Ensure that 'Unattached disks' are encrypted with CMK

• 8.4 Ensure the key vault is recoverable

Azure CIS 1.2 Security Policy - Coming Soon

With the release of the policy conditions above, we will be updating the default CIS policy to begin reflecting CIS 1.2 standards in the coming weeks. You can expect more updates to the default policy as we release additional policy conditions.