Partner Billing Support for Azure Enterprise Agreements - General Availability

We’re excited to announce the general availability of partner billing support for Microsoft Azure Enterprise Agreements (EAs)! Through this new feature, you’ll be able to configure an EA within the partner tenant and then assign a subset of the subscriptions to customer tenants. Most importantly, CloudHealth will only report on the costs associated with the subscriptions assigned to the customer tenant. In addition to being able to assign the subscriptions, you’ll also be able to create billing rules at a per subscription basis. This way, you’ll be able to specify at a more granular level which subscriptions the rules should be applied to.

All of the functionality above is possible through both the CloudHealth Platform and API. For more information, view this Help Center article.

Update to Azure Amortized Cost Report - Coming Soon

In the next few weeks, we will be updating the Azure Amortized Cost Report to begin including monthly payment reservations for Azure Virtual Machines. With this change, monthly reservations will be its own service category group and you will be able to view these costs separately from your other reservations.

Support for Additional AWS Services

We’re pleased to announce that we have updated costs for the services mentioned below.

AWS Elemental MediaConvert
Amazon Managed Blockchain

Previously, these costs were lumped into the indirect cost item - ‘Other’. Going forward, costs associated with the services listed above will be distributed into the following direct charges:

Elemental MediaConvert - Professional Tier
Elemental MediaConvert - Add On
Managed Blockchain - Membership
Managed Blockchain - Node Usage

And the following indirect charges:

Elemental MediaConvert - Basic Tier
Elemental MediaConvert - Other
Managed Blockchain - Other

For these services, we will be using AWS Tags, CloudHealth Tags, and Resource IDs for cost and asset allocation. This allocation will be applicable to the past 13 months. We recommend that you add or update your reallocation rules to adapt to this change.

Learn more about supported AWS services in this Help Center article.

Deprecating IAM User Authentication

AWS best practices include the use of Assumed Roles instead of Account or IAM Users Credentials. Accounts setup with IAM Users in the CloudHealth platform can be considered a security risk. We (along with AWS) strongly recommend setting up accounts with IAM Roles. As a result, we have deprecated the ability to use the IAM User authentication mechanism for any new account configuration. Changes related to this deprecation are not going to affect any existing accounts configured.