Hello @Jason Hand ,
Thanks for posting your query on Microsoft QnA.
I understand that after purchasing flexible RIs, you are not seeing them getting applied to resources form same VM size group.
Below are a few things you should check and go through to make sure the RI gets applied/utilized. If you still see the RI not getting applied even after going through the below steps mentioned in the document, please do let me know, and maybe I can help you open a support case for the same.
Here is the document mentioning all the possible scenarios when your RI might not get applied : Troubleshoot reservation utilization.
Some resources report usage slower than others. Additionally, some product types like SQL Databases are slow to report their usage data.
The latency can cause the utilization calculation to show lower values than the actual usage. The difference is noticeable at the day boundary. In such cases, if Azure doesn’t get usage data from four to eight hours, it calculates a value of 0%. The 0% value is shown because usage data hasn’t arrived, and it appears that the reservation isn’t applying a benefit to any resources.
As usage data arrives, the value changes toward the correct percentage. When all the usage data is collected, the correct value is determined and is shown accurately in the graph.
Common scenarios when your RI might not apply :
You may have stopped running resource A and started running resource B which is not applicable for the reservation you purchased for. To solve this, you may need to exchange the reservation to match it to the right resource.
You may have moved a resource from one subscription or resource group to another, whereas the scope of the reservation is different from where the resource is being moved to. To resolve this case, you may need to change the scope of the reservation.
You may have purchased another reservation that also applied a benefit to the same scope, and as a result, less of an existing reserved instance applied a benefit. To solve this, you may need to exchange/refund one of the reservations.
You may have stopped running a particular resource, and as a result it stopped emitting usage and the benefit stopped applying. To solve this, you may need to exchange the reservation to match it to the right resource.
You may have changed the scope of the reservation and that caused it to stop applying a benefit to the resources. To rectify this, you may need to change the scope of the reservation again to make sure the resources are deployed in same scope.
The subscription that the reservation was scoped to was deleted or moved out, so the benefit is not being applied to the resources. To rectify this, you may need to change the scope of the reservation
Hope this helps. If you still face issues, please do reach back and tag me in your response.
accept as answer and
upvote if the information provided was helpful.