Checklist - Design for cost

Use this checklist when designing a cost-effective workload.

Cost model

  • Capture clear requirements. Gather detailed information about the business workflow, regulatory, security, and availability.

  • Estimate the initial cost. Use tools such as Azure pricing calculator to assess cost of the services you plan to use in the workload. Use Azure Migrate and Microsoft Azure Total Cost of Ownership (TCO) Calculator for migration projects. Accurately reflect the cost associated with right storage type. Add hidden costs, such as networking cost for large data download.

  • Define policies for the cost constraints defined by the organization. Understand the constraints and define acceptable boundaries for quality pillars of scale, availability, security.

  • Identify shared assets. Evaluate the business areas where you can use shared resources. Review the billing meters build chargeback reports per consumer to identify metered costs for shared cloud services.

  • Plan a governance strategy. Plan for cost controls through Azure Policy. Use resource tags so that custom cost report can be created. Define budgets and alerts to send notifications when certain thresholds are reached.

Architecture

  • Check the cost of resources in various Azure geographic regions. Check your egress and ingress cost, within regions and across regions. Only deploy to multiple regions if your service levels require it for either availability or geo-distribution.

  • Choose a subscription that is appropriate for the workload. Azure Dev/Test subscription types are suitable for experimental or non-production workloads and have lower prices on some Azure services such as specific VM sizes. If you can commit to one or three years, consider subscriptions and offer types that support Azure Reservations.

  • Choose the right resources to handle the performance. Understand the usage meters and the number of meters for each resource in the workload. Consider tradeoffs over time. For example, cheaper virtual machines may initially indicate a lower cost but can be more expensive over time to maintain a certain performance level. Be clear about the billing model of third-party services.

  • Compare consumption-based pricing with pre-provisioned cost. Establish baseline cost by considering the peaks and the frequency of peaks when analyzing performance.

  • Use proof-of-concept deployments. The Azure Architecture Center has many reference architectures and implementations that can serve as a starting point. The Azure Tech Community has architecture and services forums.

  • Choose managed services when possible. With PaaS and SaaS options, the cost of running and maintaining the infrastructure is included in the service price.