Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Hybrid Use Benefit calculations seem off #730

Open
flanakin opened this issue Jun 5, 2024 Discussed in #709 · 0 comments
Open

Azure Hybrid Use Benefit calculations seem off #730

flanakin opened this issue Jun 5, 2024 Discussed in #709 · 0 comments
Labels
Area: Power BI Power BI reports Type: Bug 🐛 Something isn't working
Milestone

Comments

@flanakin
Copy link
Contributor

flanakin commented Jun 5, 2024

Discussed in #709

Originally posted by lundejd May 20, 2024
I finally got around to reviewing the Hybrid Benefit tab and am immediately confused by the numbers. For example, we have a Standard_D2ds_v5 server that has 2 vCPUs. On the bottom that same server is listed but the column vCPUs says 16. I have another of the same Standard_D2ds_v5 that has vCPUs of 2, which is correct, and AHB vCPUs of 8 which is correct.

This is only the beginning. Let's say I wanted to license a 16 vCPU server in Azure with AHUB, I would only need to use 16 core licenses to do it. The chart shows 64 and a usage quantity of 24.

I would think AHUB should look like this:

vCPUs. AHB vCPUs
1 8
2 8
8 8
10 16
16 16
20 24

and so on. minimum 8, multiples of 8. vCPU systems that don't divide into 8 end up with some "wasted" AHUB cores.

AHB vCPUs that are enabled should equal UsageQuantity. If I have an 8 vCPU machine enabled for AHUB it should use 8 vCPUs. UsageQuantity seems to be 24 for most.

Here is a screen shot with the same size server, the first has accurate info but the following do not.

Screenshot 2024-05-20 at 8 42 30 AM

@flanakin flanakin added the Type: Bug 🐛 Something isn't working label Jun 5, 2024
@flanakin flanakin added this to the June 2024 milestone Jun 5, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Triage 🔍 Untriaged issue needs to be reviewed label Jun 5, 2024
@flanakin flanakin removed their assignment Jun 6, 2024
@flanakin flanakin added Area: Power BI Power BI reports and removed Needs: Triage 🔍 Untriaged issue needs to be reviewed labels Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Power BI Power BI reports Type: Bug 🐛 Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant