Skip to main content

Azure Price estimation - what you need to take into account

By
Calculating the cost consumption for a solution that runs in cloud can be sometimes challenging. First of all you need do a forecast of how many resources are required and secondly you need to put on the paper all things that are billable by the cloud provider.

Azure Price Calculator
The pricing calculator offered by Microsoft for Azure is a nice tool, that helps you to take into account all the items. It is able to persist the cost even if you close the tab and when you are done you can export it to an excel file. For basic estimations is good, but I expect that you'll end up pretty fast with a complex excel.


Excel Calculator
In the last few years, I was involved at least 2 time per month in Azure consumption estimations for different projects - from the small one that consume a few hundreds of euros per month to big ones where you end up with a bill that has six or seven figures per year. 
You'll find different templates on the internet that you can use and don't be surprise if you end up creating your own template.

Tips and Tricks
I have a list of items that I take into account when I do price estimations for Azure. It doesn't covers everything, some things I ignore and other I consider them by default added them to the cost estimations. It's only a checklist for me, that I decided to share with others.

Things to consider
General
  1. Special support from Azure (premier support)
  2. In general computation is the main driver cost, but don't be surprised is traffic will also be around 20-30% of your cost, especially in IoT era
  3. Development, integration, testing environment also cost money, deallocate them when you don't use them
  4. Development, integration, testing environment don't need to run at full capacity
  5.  Select the right tire - to big is just waste of money
  6. Change the tier based on your needs (not only VMs, also SQL tier)
Computation
  1. VMs disk are not included in VM price and needs to be included in estimations. You pay only what you use
  2. Outbound traffic from VM
  3. The minimal number of VMs of computation units is 2, never 1
  4. Scale down when you don't need all the power

Storage
  1. Outbound traffic for Azure Storage (blobs, Azure Table)
  2. Outbound traffic when you do a sync between two different Azure Regions (storage, DB, ...)
  3. Storage cost for backups
  4. Cost of transactions, especially on Azure Tables
  5. Size of the logs
  6. Use CDNs as much as possible
  7. Non-critical use cases can implement a back-off mechanism for cost optimization (reduce number of transactions)
DB
  1. Storage cost of SQL Azure backup
Messaging
  1. Outbound traffic for Service Bus, Event Hub and other messaging system
  2. Number of events price for Event Hub
  3. Number of messages for Service Bus
Azure AD
  1. Number of users 
  2. Multi-factor authentication
  3. Number of applications
Service Fabric
  1. Minimum number of VMs in cluster (is not 2)
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more