Billing Center Cost Anomaly Detection

Version:The Billing Center Cost Anomaly policy was deprecated in October 2022. It is superseded by the Cloud Cost Anomaly Alerts policy. For information about the Cloud Cost Anomaly Alerts policy, see Cloud Cost Anomaly Alerts.

The Cost Anomaly Detection feature analyzes the spend of all Billing Centers in an Organization over a specified time period. If the percentage change of the most recent period compared to the previous period exceeds the specified threshold, then an email alert is sent out to any addresses indicated during configuration.

This section describes:

Billing Center Cost Anomaly Functionality
Billing Center Cost Anomaly Input Parameters
Billing Center Cost Anomaly Required Permissions
Billing Center Cost Anomaly Supported Clouds

Billing Center Cost Anomaly Functionality

The feature polls all Billing Centers, looking for any that have exceeded the Percent Change threshold.
The last 2 days are not included in the analysis, due to potential delays of the cloud providers updating their billing data.

Billing Center Cost Anomaly Input Parameters

Time Period—Number of days to analyze in each period. For example, if 6 days is set, then the latest time period will be 8 days ago to 3 days ago (to account for cloud provider bill delays) and the previous time period will be 14 days ago to 9 days ago.
Minimum Value: 1
Maximum Value: 31
Anomaly Threshold—Percentage change threshold. If the percentage change of Billing Center spend from the latest time period compared to the previous time period exceeds this value, then a report is sent out via email.
Cost Metric—Specify options for amortized vs nonamortized and blended vs unblended costs
Email addresses of the recipients you wish to notify—A list of email addresses to notify

Billing Center Cost Anomaly Required Permissions

Important:This feature requires permissions to access Cloud Cost Optimization resources. Before applying this feature, add the View cloud costs role for the user hoping to leverage this functionality. The role should be applied to any individual accounts where the feature will run, or to the entire organization to apply to all accounts. For complete descriptions of each role available in Flexera One, see Flexera One Roles. For more information on modifying roles, see the “Editing User Groups to Apply Roles at Organization or Account Level” section of Creating and Managing User Groups.

Billing Center Cost Anomaly Supported Clouds

AWS
Azure
Google