CLARITY S68: Azure Hybrid Benefit TrackingAZURE

Automatically detect Windows Server VMs and SQL Server databases not using Azure Hybrid Benefit licensing. Find the Windows VMs and SQL databases paying Microsoft twice, and see what each one is worth on your own bill.

The Problem: Hidden AHUB Opportunities

Most Azure customers with existing Microsoft licenses don't realize they're overpaying for Windows Server and SQL Server workloads in the cloud. Azure Hybrid Benefit (AHUB) allows you to bring your on-premises licenses to Azure and save 40% on Windows VMs and 55% on SQL databases — but finding which resources are eligible requires manual auditing across potentially hundreds of VMs and databases.

The reason it goes unnoticed is not carelessness. licenseType is set at deployment time, it is invisible on the Azure cost screens, and nothing about a VM's behaviour changes when it is wrong — the machine runs identically whether you are paying for the licence twice or not. It is a field that only shows up on the invoice, aggregated with everything else.

The Solution: Automatic AHUB Detection

CloudBitz now queries Azure APIs to detect the licenseType property on every Windows VM and SQL database. If a resource is configured as "License Included" (paying for the license) but could use "BasePrice" or "Windows_Server" (bring your own license), we flag it as an optimization opportunity and calculate the exact monthly savings.

What You Get

1. Dashboard Hero Card

When Azure is connected and AHUB savings exceed $500/month, a prominent blue banner appears at the top of your dashboard showing:

• Total monthly & annual savings potential
• Count of eligible VMs and SQL databases
• One-click navigation to detailed recommendations

2. Azure-Specific Insights Section

The Insights page now features a dedicated "Licensing" category with Azure branding:

• Blue background & "AZURE" badge — visually distinct from multi-cloud insights
• Grouped opportunities — all AHUB findings in one collapsible section
• Human-readable names — "Production Web Server 01" not "web-prod-01"

3. Detailed Insight Modal

Click any AHUB opportunity to see:

• Before/After Cost Comparison — visual grid showing current vs. AHUB pricing
• Azure CLI Commands — copy-paste ready commands to enable AHUB
• License Requirements — clear disclaimer about Software Assurance needs
• Savings Breakdown — exact monthly/annual impact per resource

az vm update \
  --resource-group production-rg \
  --name web-server-01 \
  --license-type Windows_Server

4. Cost Optimization Reports

AHUB opportunities now appear in executive reports with:

• Summary statistics (total savings, resource counts)
• Top 10 Windows VM opportunities
• Top 10 SQL Database opportunities
• License compliance disclaimer

What it finds on a real estate

Measured on our own production Azure subscription on 7 September 2026 — 20 virtual machines, which is a small estate and the numbers are correspondingly small:

• 1 VM with licenseType: None — flagged, $94.17/month of assumed saving
• 1 VM already on Windows_Server — the benefit is applied; nothing to do
• 18 VMs on Windows_Client — not flagged, and that is the correct answer

That last line is the part worth dwelling on. Windows_Client is the multi-session Windows 10/11 licence used by Azure Virtual Desktop, and it is already a bring-your-own-licence configuration. A rule that simply looked for "not Windows_Server" would have raised eighteen findings on this subscription, every one of them wrong, and buried the single real one underneath them. The rule tests for None specifically.

We are publishing a $94.17 finding rather than a five-figure one because it is the finding that exists. A larger Windows estate scales this linearly — the same rule on 200 unlicensed VMs is a four-figure monthly number — but that is arithmetic you can do, not a customer we have.

What This Is (and Isn't)

Why the limitation? Azure APIs don't expose total license counts — that data lives in Microsoft's Volume Licensing Service Center (VLSC) and has no API. Every FinOps competitor faces this same limitation, though some marketing materials suggest otherwise.

The 40% and the 55% are assumptions, and the product says so

Microsoft publishes Azure Hybrid Benefit as saving "up to" those figures. What you actually save depends on your region, your VM series, whether you hold Software Assurance, and what share of the machine's bill is licence rather than compute and storage. We apply a flat 40% to a Windows VM's total cost and 55% to a SQL database's, and that is a band, not a quote.

So the figure carries its own provenance. Every savings number in CLARITY is classified as measured, quoted, assumed or none, and both AHUB rules are declared assumed in shared/savings-provenance.ts, with the reason written next to them: "40% of the VM bill assumed recoverable by applying an owned Windows Server licence." A finding built on a percentage band is not presented the same way as one built on a price we can cite.

There is a third AHUB rule, ahub_misconfigured, and it claims no dollars at all. It fires when the benefit is enabled where it cannot apply — Linux, most commonly — which is a licensing mistake worth telling you about and not a saving worth quoting. Its provenance entry reads none. A finding that invents a dollar figure to look actionable is worse than one that admits it has none.

Our approach: We're honest about what we can and can't do. We show you cost optimization opportunities based on real Azure API data. You remain responsible for license compliance — CloudBitz simply helps you avoid overpaying for licenses you already own.

Getting Started

1. Connect Azure — Add your Azure credentials if you haven't already
2. Wait for sync — AHUB insights generate automatically within 5-10 minutes
3. Check Dashboard — Look for the blue "Azure Cost Optimization" banner
4. Review Insights — Navigate to Insights → Licensing category
5. Enable AHUB — Use the provided CLI commands or Azure Portal

Have questions about license compliance? Consult with Microsoft licensing specialists or your procurement team to confirm you own the required licenses with active Software Assurance before enabling AHUB.

Technical Details

How It Works

• Data Source: Azure Compute API (vm.licenseType) and Azure SQL API (database.licenseType)
• Detection Logic:
  • VMs: licenseType === 'None' + osType === 'Windows' + state === 'Running'
  • SQL: licenseType === 'LicenseIncluded' + state === 'Online'
• Minimum Thresholds: VMs ≥ $50/month, SQL DBs ≥ $100/month (filters noise)
• Savings Calculation:
  • Windows VMs: currentCost × 0.40 (40% AHUB discount)
  • SQL Databases: currentCost × 0.55 (55% AHUB discount)

Validated Pricing

Demo and production environments use realistic Azure pricing:

• GP_Gen5_8 SQL Database: ~$1,250/month (without AHUB) → ~$563/month (with AHUB)
• Standard_D4s_v3 Windows VM: ~$300/month (without AHUB) → ~$180/month (with AHUB)

Based on Azure US East pricing as of July 2026. Actual costs vary by region and reserved instance usage.

What's Next

This release focuses on Windows Server and SQL Server AHUB detection. Future enhancements may include:

• Azure VMware Solution (AVS) AHUB tracking
• Windows Client (VDI) AHUB tracking
• Historical AHUB adoption trending
• AHUB status alerting (Slack/Teams/email)