Microsoft Statement Update

To simplify our Microsoft statement generation for our Azure partner customers and migrate completely off the APIs that Microsoft is deprecating, we are updating our statement generation to combine two of the statements. This applies to all customers on Azure Plan with reserved instances. 

For the artifacts uploaded through automation to S3,  we will be combining the statements starting with “azure_partner_customer_mc_bill” with their corresponding statement starting with “azure_partner_customer_csp_bill”. All costs will be captured in “azure_partner_customer_mc_bill” starting on Feb 28th when Microsoft deprecates the APIs. For Statements downloaded through the Statements page, we will be performing the same combination. All costs will be captured in the billing files starting with “Azure Billing Account”

AWS Bill Collection Optimization

To create predictability in your reports, CloudHealth has added a feature that will detect if a bill older than the prior month changes and instead of automatically generating reports with the new bill, you will be presented with the cost difference and make the decision if you want to recollect the bill. By default, we will be able to alert if a cost change is detected. To access this, you’ll need to bring in the column “Billing Updates Available”. If updates are available, this column will contain the number and you can drill into those changes.

If you want visibility into the cost difference, you’ll need to give the following permission to the IAM role for each of your Consolidated accounts.

{

      "Effect": "Allow",

      "Action": [

        "ce:GetCostAndUsage"

      ],

      "Resource": "*"

    }

You can find a link to the documentation here