Describe Factors That Can Affect Costs in Azure: Learning Objectives
Describe Factors That Can Affect Costs in Azure: Learning Objectives
Describe Factors That Can Affect Costs in Azure: Learning Objectives
Learning objectives
After completing this module, you’ll be able to:
Resource type
Consumption
Maintenance
Geography
Subscription type
Azure Marketplace
Resource type
A number of factors influence the cost of Azure resources. The type of resources, the settings
for the resource, and the Azure region will all have an impact on how much a resource costs
Examples
1. With a storage account, you specify a type such as blob, a performance tier, an access tier,
redundancy settings, and a region. Creating the same storage account in different regions
may show different costs and changing any of the settings may also impact the price.
2. With a virtual machine (VM), you may have to consider licensing for the operating system or
other software, the processor and number of cores for the VM, the attached storage, and
the network interface. Just like with storage, provisioning the same virtual machine in
different regions may result in different costs.
Maintenance
If you deprovision the VM, those additional resources may not deprovision at the same time, either
intentionally or unintentionally.By keeping an eye on your resources and making sure you’re not
keeping around resources that are no longer needed, you can help control cloud costs.
Network Traffic
Billing zones are a factor in determining the cost of some Azure services.
Bandwidth refers to data moving in and out of Azure datacenters. Some inbound data transfers
(data going into Azure datacenters) are free. For outbound data transfers (data leaving Azure
datacenters), data transfer pricing is based on zones.
A zone is a geographical grouping of Azure regions for billing purposes. The bandwidth pricing
page has additional information on pricing for data ingress, egress, and transfer.
Pricing calculator
Note
The Pricing calculator is for information purposes only. The prices are only an estimate.
Nothing is provisioned when you add resources to the pricing calculator, and you won't be
charged for any services you select.
TCO calculator
The TCO calculator is designed to help you compare the costs for running an on-premises
infrastructure compared to an Azure Cloud infrastructure
With the TCO calculator, you enter your configuration, add in assumptions like power and IT
labor costs, and are presented with an estimation of the cost difference to run the same
environment in your current datacenter or in Azure.
You can add, modify, or delete resource tags through Windows PowerShell, the Azure CLI, Azure
Resource Manager templates, the REST API, or the Azure portal.
You can use Azure Policy to enforce tagging rules and conventions. For example, you can require
that certain tags be added to new resources as they're provisioned. You can also define rules that
reapply tags that have been removed. Tags aren’t inherited, meaning that you can apply tags one
level and not have those tags automatically show up at a different level, allowing you to create
custom tagging schemas that change depending on the level (resource, resource group, subscription,
and so on).
A resource tag consists of a name and a value. You can assign one or more tags to each Azure
resource.
Name Value
Keep in mind that you don't need to enforce that a specific tag is present on all of your resources.
For example, you might decide that only mission-critical resources have the Impact tag. All non-
tagged resources would then not be considered as mission-critical.