Overview
This guide walks you through the multiple cost management units in Azure, how they relate to each other, and how they are registered in Ripple.
Azure and Ripple Data Structure
Azure | Ripple |
Partner / MSP level — MPN ID | Ripple account level |
Customer level — Azure Plan ID, Tenant ID, Customer ID | Billing Group |
Department / Service / Environment level — Subscription ID (Resource groups can be configured under a subscription to group resources) | Linked to a Billing Group |
Notes Multiple Azure Plan IDs may be linked to a single Customer ID / Tenant ID. Multiple subscriptions can be linked to a single Billing Group.
How Billing Groups Are Structured in Ripple
Ripple aggregates and manages costs at the Billing Group level. For Azure, multiple subscriptions can be linked to a single Billing Group.
In most cases, Billing Groups are created based on one of the following grouping units:
Customer ID
Tenant ID
Azure Plan ID
Subscriptions are then linked to the appropriate Billing Group according to your management structure.
Example: Cost Management by Tenant ID
If your organisation manages costs based on Tenant ID, the structure may look like this:
Tenant A
├── Azure Plan ID A
│ ├── Subscription A
│ └── Subscription B
└── Azure Plan ID B
├── Subscription D
└── Subscription E
In this case, link Subscriptions A, B, D, and E to a single Billing Group. This allows you to process billing and create Wave accounts in line with your management structure.
Need More Help?
If any errors occur during the process or if you have any questions, please reach out to us:
📧 Email: ripple_cs@alphaus.cloud
💬 Live Chat: Available in the bottom-right corner of your dashboard
📖 Help Center: https://help.alphaus.cloud/