Background
Following Red Hat's transition to a scalable vCPU-based pricing model in early 2024, Microsoft Azure implemented corresponding pricing updates for RHEL services. As part of ensuring our billing infrastructure fully supports this new pricing structure, we are updating the billing meter IDs for Red Hat Enterprise Linux services to provide better alignment with the current pricing model.
What's Changing
As part of optimizing our billing infrastructure to fully support Red Hat's updated pricing model, Microsoft Azure is updating the billing meter IDs for Red Hat Enterprise Linux (RHEL) services. These changes ensure our billing system properly accommodates the vCPU-based pricing structure and Reserved Instance functionality.
Effective Date: The meter ID migration will begin rolling out on October 2-8, 2025.
Impact on Customers
Pay-As-You-Go (PAYG) Customers
- Billing Continuity: Your RHEL instances will continue to operate without any service interruption
- Meter ID Changes: New meter IDs will appear in your usage reports and cost management statements starting Oct 2-8, 2025
- Usage Tracking: Historical usage data remains accessible through existing billing reports
Important: No Pricing Impact
This meter ID migration has no impact on pricing. Azure already implemented the RHEL pricing changes in early 2024. This meter ID update is purely a technical billing system change and does not affect your costs in any way. For pricing information, see the Pricing - Red Hat Virtual Machines | Microsoft Azure page.
Action Required: Update Your Billing Tools
To ensure uninterrupted monitoring and reporting, we recommend reviewing and updating the following:
- Billing Reports and Dashboards
-
- Cost Management Reports: Update any custom reports that filter by specific RHEL meter IDs
- Power BI Dashboards: Refresh data connections and update meter ID filters
- Third-party Tools: Verify that cost management tools recognize the new meter IDs
- Budget Alerts and Monitoring
-
- Budget Configurations: Review budgets that target specific RHEL services and update meter ID filters
- Cost Alerts: Ensure automated cost alerts include both old and new meter IDs during the transition period
- Spending Thresholds: Update any spending controls that rely on meter ID identification
- Automated Tools and Scripts
-
- Cost Analysis APIs: Update API calls that reference specific RHEL meter IDs
- Automation Scripts: Modify any scripts that process billing data using meter ID filters
- Integration Tools: Update third-party integrations that rely on meter ID mapping
Transition Period Support
During the migration period, you may see both old and new meter IDs in your statements. This is expected behavior as the transition occurs gradually across different regions and services.
Timeline:
- October 2-8, 2025: New meter IDs begin appearing for RHEL Pay as you go meters
- Transition Period: Both old and new meter IDs may appear in billing during migration
- Completion: Migration will be completed across all regions and services
Affected RHEL Meters
The following RHEL meter names will be updated with new meter IDs as part of this migration:
- 1 vCPU VM License
- 1 vCPU VM License - Free
- 2 vCPU VM License
- 4 vCPU VM License
- 6 vCPU VM License
- 8 vCPU VM License
- 12 vCPU VM License
- 16 vCPU VM License
- 20 vCPU VM License
- 24 vCPU VM License
- 32 vCPU VM License
- 40 vCPU VM License
- 44 vCPU VM License
- 48 vCPU VM License
- 52-vCPU VM License
- 60 vCPU VM License
- 64 vCPU VM License
- 72 vCPU VM License
- 80 vCPU VM License
- 96 vCPU VM License
- 120 vCPU VM License
- 128 vCPU VM License
- 144-vCPU VM License
- 192 vCPU VM License
- 192-vCPU VM License
- 208 vCPU VM License
- 416 vCPU VM License
- 420-vCPU VM License
These meter changes are tied to the vCPU count, not the VM family - meaning any VM with the same vCPU count (whether D family, E family, etc.) uses the same RHEL license meter. For example, all 2 vCPU VMs use the "2 vCPU VM License" meter regardless of the VM family.
If your billing reports, budgets, or automated tools currently filter or reference any of these specific meter names, you'll need to update them to include the new meter IDs once the migration begins.
Support and Resources
Need Help?
- Azure Support: Contact Azure Support for technical assistance with billing or meter ID questions
- Account Team: Reach out to your Microsoft account team for guidance on updating enterprise billing processes
Additional Resources:
- RHEL pricing update details: Red Hat Enterprise Linux Pricing update
- Azure cost optimization resources can be found here
Frequently Asked Questions
Q: Will this affect my RHEL instances or their performance?
A: No, this is purely a billing system update. Your RHEL instances will continue to operate normally with no performance impact.
Q: How can I identify the new meter IDs in my billing?
A: New meter IDs will appear in your Cost Management portal and usage reports and cost management statements starting October 2-8, 2025. Watch for updated RHEL service descriptions in your billing details.
Q: What if my automated tools stop working?
A: Contact Azure Support for assistance. We recommend updating your tools proactively using the meter ID mapping reference provided.
We're committed to making this transition as smooth as possible. If you have questions or need assistance, please reach out to Azure Support or your Microsoft account team.
Microsoft