> For the complete documentation index, see [llms.txt](https://docs.cloudassert.com/azure-stack-billing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudassert.com/azure-stack-billing/features/multi-stamp-azure-stack-hub.md).

# Cost Management Across Multiple Azure Stack Hub Stamps

The Cloud Assert Billing solution is capable of querying usage of subscriptions from multiple stamps and computing the costs. It can also give reports on quota consumption of Microsoft.Compute, Microsoft.Storage and Microsoft.Network services. To enable this capability, connections to the stamps needs to be created.

To add connection to an Azure AD integrated Stamp (Connected Stamp):

{% content-ref url="/pages/-MdvLfD86I5snDacUGCf" %}
[Connecting to an Azure AD Stamp](/azure-stack-billing/features/multi-stamp-azure-stack-hub/connecting-to-an-azure-ad-stamp.md)
{% endcontent-ref %}

To add connection to an ADFS integrated or disconnected stamp:

{% content-ref url="/pages/-MdvSVFEbgcBUm5-XcVH" %}
[Connecting to an ADFS Stamp](/azure-stack-billing/features/multi-stamp-azure-stack-hub/connecting-to-an-adfs-stamp.md)
{% endcontent-ref %}

Once the connections are connected, the Billing service will sync the subscriptions across stamps and map them against the subscriptions of the same users in the master stamp. The costs and invoices will be generated for the mapped master stamp subscriptions. If, the costs and invoices needs to be generated for each subscription across stamps, the mapping can be changed manually from the Billing admin extension. The following page has the steps to configure the same.

{% content-ref url="/pages/-MBr6ttNsD7XHZT2l-zJ" %}
[Mapping Subscriptions](/azure-stack-billing/installation/configuration/mapping-subscriptions.md)
{% endcontent-ref %}

For the Cloud Assert Billing solution to generate reports regarding quota consumption, the service administrator needs to do a one-time step and the tenant users needs to give consent to Billing application. 

{% hint style="info" %}
This is a licensed feature and it is currently supported only for connected Azure Stack Hub integrated with single Azure Active directory tenant.
{% endhint %}

Service administrator one-time setup:

{% content-ref url="/pages/-MWSnqFk1a-TVFg1582n" %}
[Enabling End Users To View Usage Costs And Quota Consumption For Subscriptions Across Stamps](/azure-stack-billing/features/admin-features/enabling-end-users-to-view-usage-costs-and-quota-consumption-for-subscriptions-across-stamps.md)
{% endcontent-ref %}

Tenant user consent:

{% content-ref url="/pages/-MWSU8dynJiQEz8cDgRo" %}
[Manage Subscriptions](/azure-stack-billing/features/tenant-features/manage-subscriptions.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cloudassert.com/azure-stack-billing/features/multi-stamp-azure-stack-hub.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.