Forum Discussion
Azure Cost Management Connector - Optional Parameters and RI Recommendations
Hi. I am working with the Azure Cost management Connector and have two questions that I have not been able to answers to from online documentation or forum posts. The only documentation I have come across is this url:
https://docs.microsoft.com/en-us/power-bi/connect-data/desktop-connect-azure-cost-management
Question 1)
By default, RI recommendations (single and shared) seem to only includes normalized SKU and quantity in the recommendations. Is there a way to change it to reflect the different skus within a family, just like in the API itself and in the old connector?
Question 2)
In different forum post I am reading about different optional parameters to include in power query for adjusting what the connectors return. Is there a place where I can find a list of optional parameters? I tried looking at AzureCostManagement.Contents in PQ as suggested in this post:
However, that only provides examples.
2 Replies
- v-xulin-mstf
Community Support
Hi pbiquest
I'm not sure what your expected outcome is for 'change it to reflect the different skus within a family', could you provide more details?
Best Regards,
Link
Is that the answer you're looking for? If this post helps, then please consider Accept it as the solution. Really appreciate!
Hi and thank you for your response.
Two options usually are usually available for RI recommendations:
- Non-normalized recommendations, where recommendations are broken down by actual usage for each machine size. This is what I want. Example: 1 x Standard_D16s_v3 and 2 x Standard_D4s_v3 in north eu region.
- Normalized: Recommendations are given in terms of an equivalent number of recommendations at the smallest machine type in a so-called size flexibility group:
https://docs.microsoft.com/en-us/azure/virtual-machines/reserved-vm-instance-size-flexibility
Normalize usage can simplify many scenarios, as RI discounts can be shared across different sizes in a group. With the above usage example, the normalized recommendation would be (8 + 2 x 2) = 12 x Standard_D2s_v3 (ratio is used to convert sizes).
I need to create an intuitive link between recommendations and actual usage, and for this purpose I cannot work with normalized usage.
