Try to verify if the billing period matches your subscription period and check for any pro-rated charges. Another factor could be inaccuracies in billing metrics reporting due to delays or errors.
As you mentioned that you did some investigations, try also to ompare the usage metrics in the Azure portal with the billing report to identify any discrepancies.
My concerns are the following :
- Reserved instances might also be a cause, as they are billed differently, and any usage beyond the reserved amount incurs on-demand charges.
- Resource misallocation or incorrect reporting can also occur. In this case, the resources billed align with those provisioned, and you will have to check the configurations in the Azure portal to confirm that the D8ds_v5 configuration is still in use.
Try to contact the support team :
- Go to the Azure portal.
- Navigate to Help + Support > New support request.
- Select the relevant subscription and fill in the details, explaining the problem.