Documentation and Best Practices

Learn how to use Cloudability and get the most out of our cloud cost management tool

— User assistance content is no longer updated on this site —

— For up-to-date information, check out the Apptio Help Center

Follow

Enabling Amortized Cost Data for Existing Cloudability Azure Customers

Please ensure you have reviewed the Setup Guide Overview before beginning the steps outlined below for updating your Cloudability Azure credentials to enable access to amortized cost data.

 

Updating Your Cloudability Credential Setup for Azure EA Customers

Following these steps should result in the creation of 2 CSV formatted files: one file for actual cost data and one file for amortized cost data  

Note: both CSV formatted files are required by the Cloudability platform and must be present in the storage account being used to collect cost management data. 

 

Before you begin the steps below, please ensure you login to the Azure portal and have access to your organization's EA enrollment by selecting the Billing scope for your EA. For examplesee the pic here:
blobid0.png

 

Creating Billing Data Exports in the Azure Portal

Step.1:
from the Azure Portal, search for "Cost Management + Billing" and select it from the list to open the Billing Scope page. For example:blobid1.png

 

Step.2:
from your Cost Management + Billing console, ensure you have selected the Billing Scope for your EA; if you have multiple, select the scope with the majority of your cloud spend. 

Step.3:
from the Cost Management + Billing console, find the "Export" menu item from the left-side panel under the "Settings" category and click it to open the Azure export utility
blobid5.png

 

Step.4:
click the "Add" button to open the export page for creating a new CSV export
blobid6.png

 

Step.5:
on the new export page, fill in the export details form to: 
a. provide a filename for your export 
b. select a cash basis for your export; this will be either "actual cost" or  
   "amortized cost" 
c. select the export type to be "Daily export of month-to-date costs" 
d. confirm the start_date is the current day 
e. select an existing or create a new (recommended) storage destination for  
    the export and provide a single root directory for both CSV files.

for example:
blobid7.png

 

Step.6:
repeat the steps 5a.->5d (above) to export cost data for the other cash basis and this time use the storage selected/created for 5e. 

 

friendly reminder: following these steps should result in the creation of 2 CSV formatted files: one file for actual cost data and one file for amortized cost data. 

 

 

 

Gathering Billing Data Info for Your Cloudability Credential Setup 

Now that you've completed the steps for creating a billing data export, we’ll need some information from your Azure Portal for the Cloudability Credential setup. 

What information does Cloudability need? 

All the properties can be found using the Azure Portal Cost Management console.  Please lookup and save the following information for use later: 

Property Name 

How-to find it 

ø tenant id 
 

  1. search for "Azure Active Directory" and select it to load the AD Overview page 
  2. copy and save the tenant id  
    see example pic here: https://share.getcloudapp.com/qGuvYGjK 

 
 

ø api access key

  1. search for "Cost Management + Billing" and select it from the list to open the cost management console on the “Overview” page 
  2. click on the “EA Portal” shortcut link 
    see pic here: https://share.getcloudapp.com/OAuWOjNA  
  3. open the “API Access” page under the “Download Usage” tab from the “Reports” menu; copy and save your “API Access Key” 
    see pic here:  https://share.getcloudapp.com/ApuGnDpB 

 

ø subscription id 
ø resource group name 
ø storage account name 
 

  1. search for "Cost Management + Billing" and select it from the list to open the Billing Scope page 
  2. selected the Billing Account scope for your EA, then click "Exports" from the side menu to show a table with your billing data storage account 
  3. click on the storage account for your billing data to open the "Overview" page to reveal the subscription id, resource group name and storage account name. 
    see pic here: https://share.getcloudapp.com/nOunQOrm 

 
 

ø container name 
ø directory name 
ø cost export name 
ø amortized export name 
 

  1. from the storage account "Overview" page, click through "Containers" 
  2. navigate to the directory that houses the exports  
  3. copy and save the container namedirectory name and both the actual cost export and amortized cost export file names 
    see pic here: https://share.getcloudapp.com/p9uwY9WQ 

 
 

 

 

 

Updating Your Cloudability Credential using the Billing Data Info

Once you’ve gathered the information from the table above, you will be entering it into the Cloudability Credentials Azure UI for your EA credential. 

Cloudability will use that information to generate a PowerShell script that you can download and run from your Cloud Shell to grant the Cloudability Storage Blob Data Reader role access to the storage account that was designated for billing data.

 

Step.1:
navigate to the Cloudability Credentials Azure UI (direct link here) 

 

Step.2:
click to edit your EA credential, for example:
blobid0.png

 

Step.3:
when the side panel opens, enter your EA API Access Key and the other information gathered from your Azure Portal into the corresponding UI fields;  see the example here: https://share.getcloudapp.com/2NujOj4P

 

Step.4:
click “Generate Setup Script” to download the new script file

 

Step.5:
click the “Close” button for now; you will return to verify the changes.

 

 

 

Granting Cloudability Access from the Azure Portal

The next step is to grant Cloudability access to read the cost & usage data from your Azure storage. 

Once the information outlined in the previous table has been input to the Cloudability Azure Credentials UI and a setup script created, you will run the setup script in your Azure Portal Cloud Shell.   

These commands will enable the Storage Blob Data Reader Role for Cloudability to access the storage account that has the exported CSV files.

 

to run the script: 

  1. login to the Azure Portal and switch to the required Tenant 
    (aka directory that is the highest level of in Azure for the target enrollment) 
  2. from the Azure Portal launch the Cloud Shell and select PowerShell as the scripting language 
  3. once the Cloud Shell has initialized, select "Upload" from the Cloud Shell terminal menu 
  4. upload the setup script file provided by Cloudability 
  5. once the file has been uploaded, run the script by typing 
    >: ./<YOUR_SCRIPT_NAME_HERE>.ps1 

for example:
blobid9.png

 

 

 

Complete the Setup from the Cloudability UI 

The final step to complete the setup is to verify your updated Cloudability EA credential.

 

Step.1:
return to the Cloudability Credentials Azure UI (direct link here) 

 

Step.2:
click to edit your EA credential. for example:
blobid2.png

 

Step.3:
click on the “Verify Credential” button at the bottom of the side panel; you Azure Credential will have green checkbox under the “Billing Reports” column once it has been validated.

 

Step.4:

Important: ensure that  
    (i) all your EA Cloudability credentials have been updated with these steps and  
   (ii) you remember and socialize your Azure amortized cost cutover date 

 

if you have >1 EA credential, you must follow these steps for all your EA credentials.

 

Once these steps have been completed for all your EA credentials, Cloudability will automatically detect your Azure v2 cutover date.

 
What is the Azure v2 cutover date? 
This represents the earliest date for which you provided enhanced billing data to Cloudability (including amortized cost data) from the new Azure billing data source.  

By establishing the "Azure v2" cutover date, Cloudability can distinguish between (i) the enhanced billing data which includes amortized cost from the new Azure billing data source and, (ii) billing data from the “original Azure data source, which does not include any enhancements (or amortized cost data). 

For example:  if it is December and you have provided CSV export files for each month from January to November, then your Azure v2 cutover date will be automatically set to January 1st. 

It is important to be aware of this cutover date because reports that surface cost data across the cutover date boundary will represent an aggregation of “original” and “new” billing data - this could potentially lead to confusion. for example: “original” billing data does not include any amortized cost data

 

 

 

Please allow 8 hours for your enhanced cost and usage billing data to populate. 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.