If reservations assets are not showing as expected in the platform, follow the steps below to review if the configuration steps were followed correctly.
We require the reader role to be applied directly to the Reservation Order resource.
When the Microsoft API does not return the expected results, it is likely the reader role is inherited from a parent (like the Root Management Group), or applied at the reservation level.
Our configuration documentation explains how to apply the role directly on the Reservation Order resource steps found via the link below.
To review if these steps were followed, locate each Reservation Order resource in the Azure portal, indicated by 'Reservation Order' under the resource name (as seen in the screenshot below), and ensure there is a reader role assigned for the resource.