question

CasperRubaek avatar image
0 Votes"
CasperRubaek asked SadiqhAhmed-MSFT commented

Azure Retail Pricing API is not consistent with azure.microsoft.com pricing page

I am comparing Service Bus prices from Azure Retail Pricing API to the Service Bus pricing page on https://azure.microsoft.com/en-us/pricing/details/service-bus/ and I have found that they are not consistent.

Can someone explain why this is?

Specifically I am comparing the Service Bus Standard base charge for North Europe region with CurrencyCode DKK.

Here is the output from the Azure Retail Pricing API:

98873-image.png

And here is the output from https://azure.microsoft.com/en-us/pricing/details/service-bus/ :

Standard Base charge: kr0.0846/hour


azure-cost-management
image.png (6.4 KiB)
image.png (22.9 KiB)
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@CasperRubaek Thanks for reaching out. I have tested the Retail API and observe the same behavior. I have reached out to my team for their input. I will update you once I heard back from them.

1 Vote 1 ·

Thanks, looking forward to it.

0 Votes 0 ·

@CasperRubaek This issue is more related to the cost management side. I have added the right tag (azure-cost-management) and updated the team to assist you further.

0 Votes 0 ·
Show more comments

1 Answer

SadiqhAhmed-MSFT avatar image
0 Votes"
SadiqhAhmed-MSFT answered SadiqhAhmed-MSFT commented

@CasperRubaek The discrepancy between the Retail API and Azure Pricing pages occurs due to the FX rate used. The price for this particular meter is USD 0.013441 and it converts to DKK 0.0827 on Retail API and DKK 0.0846 on Azure pricing pages.

• Retail API uses Modern FX rate (for DKK, it is 6.1507)
• Azure Pricing pages uses Legacy FX rate (for DKK, it is 6.2934)


Additional details

• Retail API decided to launch the support for local currencies and went with modern FX rates to optimize for users with Modern Agreement.
• Changes on Azure.com pricing pages and pricing calculator will default the experience to show modern rates by end of the year.

Hope this clarifies!


If the response helped, do "Accept Answer" and up-vote it

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@SadiqhAhmed-MSFT

This explains the issue, however which amount do I pay when deploying the resources, the price on the pricing page or the price from the API?
Also which API do you use for FX conversions?


0 Votes 0 ·

@CasperRubaek If it is a legacy agreement, then you would pay what you see on the pricing page. If it is a modern agreement, then you would pay what you see on the API. But I don’t think transition to modern has happened in the countries that use DKK, so I suspect it is a legacy agreement. May be portal exposes the actual price in DKK when you try to deploy so that would be a sure shot way to know. I am not too sure as I don’t have any test account in a non-USD currency.


For legacy FX rates, there is no API.
For modern FX rates, the pricing team has an endpoint that they support. The endpoint is not exposed to pubic.

There is WIP that should complete by next quarter post that the documentation about legacy and modern FX rates will be published and made available to the users.


If the response helped, do "Accept Answer" and up-vote it

0 Votes 0 ·