MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.29k stars 21.47k forks source link

Need clarification with RI and AHUB Pricing for AVS #61553

Closed Mahesh-MSFT closed 4 years ago

Mahesh-MSFT commented 4 years ago

Are following statements in the documentation still valid?

  1. What's in an Azure VMware Solution (AVS) assessment? mentions that “…RIs are currently not supported for AVS nodes…”. However, Azure Pricing calculator provides option to select RI pricing for AVS.

  2. What's in an Azure VMware Solution (AVS) assessment? mentions that ““…Although it[Hybrid Benefits] has no impact on Azure VMware solutions pricing due to the node-based price…"

Also, does costs arrived after Azure Migrate assessment automatically include AHUB benefits for Windows and SQL Servers?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

SadiqhAhmed-MSFT commented 4 years ago

@Mahesh-MSFT Thanks for the question. We are looking into this issue and will get back to you shortly.

SadiqhAhmed-MSFT commented 4 years ago

@Mahesh-MSFT For your first statement, I believe that’s in reference to what the Azure Migrate assessment produces (or takes into account). There may, in fact, be Reserved Instances (RIs) available for the AVS platform, but currently, the Azure Migrate assessment does not include that in it’s calculation/options.

For the second question, Azure Migrate does not automatically include Azure Hybrid Use Benefits (HUB) benefits in it’s assessment. In a “normal” assessment (ie. Non-AVS targeted), there is an option within the Assessment Properties available to toggle Azure Hybrid Use Benefits (HUB).

Hope that clarifies!

SadiqhAhmed-MSFT commented 4 years ago

@Mahesh-MSFT Do you have any other questions?

Mahesh-MSFT commented 4 years ago

Thanks @SadiqhAhmed-MSFT . No further questions.

SadiqhAhmed-MSFT commented 4 years ago

@Mahesh-MSFT Thanks for confirming. Closing this issue for now.