> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/help-and-support/faqs/im-unable-to-view-the-reserved-instance-data.md).

# I'm unable to view the Reserved Instance data

In some cases, the consumption data for your Azure Reserved Instances might be unavailable in the Client Portal. 

If you are not able to view the data, you must update your permissions and assign the Reservations reader role to each tenant through the Azure Portal. 

To learn about the Reservation reader role and how to assign it, see [Permissions to view and manage Azure reservations](https://docs.microsoft.com/en-us/azure/cost-management-billing/reservations/view-reservations). You can also assign the role by following the steps in this topic.

## Before you begin <a href="#assign-the-owner-role-for-all-reservations" id="assign-the-owner-role-for-all-reservations"></a>

You can assign the Reservations reader role only if you have the User Access Administrator or Owner role in Azure. If you need to elevate your access, see [Elevate access to manage all Azure subscriptions and management groups](https://learn.microsoft.com/en-us/azure/role-based-access-control/elevate-access-global-admin?tabs=azure-portal).

## Assigning the Reservations Reader role using Azure <a href="#assign-the-owner-role-for-all-reservations" id="assign-the-owner-role-for-all-reservations"></a>

To assign the role:

1. Sign in to the [Azure Portal](https://portal.azure.com/) and search for **Reservations**.&#x20;
2. Select **Role Assignment**.&#x20;
3. On the **Access Control** page, select **Add** > **Add role assignment**. The **Add role assignment** page opens.

<figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/lrrwDIRuktjCe2kIMPo2/Add%20role%20assignment.png" alt=""><figcaption><p>Add role assignment</p></figcaption></figure>

4. On the **Role** tab, select **Reservations Reader** as the role. Then, select **Next**. &#x20;

<figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/Hcod85uD8cDpbx8zx4fz/ReservationsReader.png" alt=""><figcaption><p>Reservations Reader role</p></figcaption></figure>

5. On the **Members** tab, do the following:
   1. Select **User, group, or service principal** if it's not selected by default, and then select **Select members**. &#x20;
   2. In the **Select members** panel, type **PyraCloud** and then select **PyraCloud (Azure)** from the search results.&#x20;
   3. Choose **Select**.&#x20;

<figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/mIPMacXJ7uoBPOPKbIhN/Select%20Members.png" alt=""><figcaption><p>Select members</p></figcaption></figure>

6. Select **Review + assign**.
7. On the **Review + assign tab**, review the details and click **Review + assign** to confirm the role assignment.&#x20;

After you've completed these steps, the **Reservations Reader** role is assigned and displayed on the **Role assignments** tab.&#x20;

Once the role is assigned, it might take up to 24 hours for your consumption data to become available in the Client Portal. If you are not able to view the data after 24 hours, [contact support.](/help-and-support/contact-support.md)&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform.softwareone.com/help-and-support/faqs/im-unable-to-view-the-reserved-instance-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.