IBM Cloudability

 View Only

 Does Cloudability support getting data only from specific business units or countries?

Jump to  Best Answer
Emil Magni's profile image
Emil Magni posted Tue February 04, 2025 07:02 AM

Can Cloudability fetch and display data only for specific business units or countries within a shared tenant environment, where cloud subscriptions are used by thousands of business units worldwide?

Im not experienced in the data ingest/setup but understand that maybe we cannot do this? Seems we get all data from the MCA in Azure or the entire billing CUR in AWS. Would liked to see it being possible to filter, if for example the Norwegian BU of a large global company want to procure Cloudability, without fetching billing data from the entire global company. 

Can Cloudability be configured to fetch and display data specifically for one or more given business units or countries within a shared tenant environment where cloud subscriptions are used by thousands of business units worldwide? Currently, we're working with a company in Norway that has emphasized professionalizing their FinOps practices. They're looking for a solution to optimize and report on cloud spend but are restricted because their cloud subscriptions are under a single tenant shared globally across numerous business units. The challenge is that before any filtering, a solution like Cloudability would have access to data from all business units, which is not permissible. Is there a feature in Cloudability that can ensure data is only ingested or displayed for the specific business unit in Norway, or can we apply filters to manage this data post-ingestion?

Lisa Harnett's profile image
Lisa Harnett posted Wed February 05, 2025 09:52 AM  Best Answer

If it is all under a single payer, it is not supported to bring in only a selected few linked account / subscriptions.  Cloudability is designed to take in multiple payer accounts/subscriptions because it uses both the API and the cost data exports available.  

There is a Cloudability version that is specific to the provider in your situation, called Cloudability MSP.  This would allow the vendor/service provider (MSP) to add their payer and then create Cloudability instances for each of their customers. It is similar in concept to the AWS Billing Conductor mentioned by @Graham Lea. The MSP would be able to configure what accounts or tags indicated it is specific to a single customer's data and your customer Cloudability instance would only contain that information. 

Graham Lea's profile image
Graham Lea posted Tue February 04, 2025 11:08 AM

Not an answer per se, but how about using something like billing conductor (AWS Billing Conductor – Amazon Web Services) from AWS to produce a CUR file for just the business unit your interested in pushing to Cloudabilty?