Azure reservation assets are missing or not populating as expected in the CloudHealth (CH) Platform.
The CloudHealth platform requires the Reader role to be applied directly at the Reservation Order resource level.
If the Reader role is inherited from a parent scope (such as the Root Management Group) or applied only at the individual reservation level, the Microsoft API will not return the required data to CloudHealth.
The key indicator of this issue is that the Microsoft List API call: providers/Microsoft.Capacity/reservations
does not return the expected reservation data. Customers can verify this by executing the call using their configured Service Principal. If the data is absent from the API response, it will not appear in the CloudHealth Platform.
Log in to the Azure Portal and navigate to Reservations.
Locate each Reservation Order resource (indicated by 'Reservation Order' under the resource name).
Select Access Control (IAM) > Role assignments.
Confirm that a Reader role is directly assigned to the configured Service Principal for this specific resource scope (This resource).
If the Reader role is missing at the Reservation Order level, follow the step-by-step configuration guide in the official CloudHealth documentation: