Did you know that the average month in Azure is 732 hours long? And that when you ask an Azure pricing tool for a monthly cost, it takes the hourly cost and multiplies it by 732 … and that used to be 744!
Since I started working with Microsoft Azure, I’ve been using 744 hours as the average month in the Azure universe. That was because that’s what Microsoft used.
Only this week my colleague saw that Microsoft had switched to using 732 hours. I was puzzled so we checked, confirmed, and opened Excel to do some maths.
Let’s analyse 744 hours first:
744 (hours per month) * 12 months = 8928 hours per year.
8928 hours per year / 365 days = 24.46 hours.
Hmm. Let’s allow for a leap year:
8928 hours per year / 366 days = 24.39 hours.
OK. Let’s forget 744 hours and go with 732.
732 (hours per month) * 12 months = 8784 hours per year.
8784 hours per year / 365 days = 24.066 hours.
Not quite even. Let’s go with a leap year:
8784 hours per year / 365 days = 24 hours exactly.
732 hours is the average length of a month in a leap year.
Azure’s monthly pricing is based on the average month in a leap year.
Was This Post Useful?
If you found this information useful, then imagine what 2 days of training might mean to you. I’m delivering a 2-day course in London on Feb 22-23, teaching newbies and experienced Azure admins about Azure Infrastructure. There’ll be lots of in-depth information, covering the foundations, best practices, troubleshooting, and advanced configurations. You can learn more here.