Cloud Cost Management (CCM / CI) - Error - Execution for Azure Balance Summary failed

huntera
Tera Contributor

Hello,

 

After successfully connecting a Azure subscription to the module I am getting this error, despite following all steps listed here - https://docs.servicenow.com/bundle/xanadu-it-asset-management/page/product/cloud-insights/concept/az...

 

I've assigned the "cost management reader" to the app registration.

 

I've also tried assigning "cost management contributor" to the app registration as well, which doesn't fix it either. The mid-server can reach the URL needed "management.azure.com". What are we missing here to get this to work? A lot of ServiceNow documentation for this connection refers to leveraging Azure Enterprise Reporting APIs, which has been retired by Microsoft in favor of "Microsoft Cost Management APIs".

huntera_0-1730323474391.png

 

"Execution is not created because of the below reason(s) :
success: Connection to MetricBase successful
success: Connection to MID Server successful
warning: Connection to Azure Balance Summary failed"

 

Any thoughts or additional insights that can be provided would be greatly appreciated!

3 REPLIES 3

ParkHyunSun
Tera Expert

Hi, is there anyone who resolved this problem?

I'm encountering the same issue, too.

konijetisumanth
Giga Guru

 

 

1)In Azure portal Go to Portal.azure.com -- Cost Management + Billing -- Select Billing Scope -- Go to Properties and note down the billing account ID

2)In ServiceNow Add the billing account ID in the Account ID field of Cloud Service Account.

3) You are supposed to use two different Service Accounts for Billing Jobs & Discovery. Check if you are using same account for Billing jobs and discovery. Create two different accounts. One for Discovery and one for Download billing jobs. And for Download billing job, Service account should be billing ID.

Thanks @konijetisumanth  I have the same issue, made sure billing account ID was in account ID field of Cloud Service account and have separate service accounts for billing jobs and discovery. Still not solving the issue. Any other thoughts?