How much it cost Azure?

Cloud technologies generally enable you to minimize or eliminate capital expenditures completely. They also might help customers lower their operational costs. These principles are applicable to Azure and are reflected in its pricing model.

Azure charges are, for the most part, calculated on a per-minute basis, and they reflect actual usage. For example, when you deploy Azure virtual machines, the corresponding cost relates mainly to their compute time. These charges apply whenever a virtual machine is running, but terminate as soon as you stop the virtual machine by using the Azure portal or Azure PowerShell. Another less significant part of virtual-machine cost relates to the content of virtual-disk files that you host in an Azure Standard storage account. In this case, you are charged for only the disk space that you use and for the number of Input/Output storage operations that your workload performs. For example, if you provision a 1 terabyte (TB) disk, but you store only 20 gigabyte (GB) of data on it, then your cost will represent 2% of the entire disk’s pricing.

Note: There are some exceptions to this rule, typically applicable to higher end services where you pay for guaranteed, provisioned capacity. For example, with the Premium Storage (hosted on solid state drives), you would pay for entire 1TB disk, regardless of the amount of data you store on it. Conversely, in this case, there would be no charges for the number of Input/Output storage operations performed by your workload.

Microsoft offers a majority of Azure services in several pricing tiers, to accommodate different customer needs and facilitate vertical scaling. However, by implementing vertical scaling, customers can increase or decrease processing power and service capacity rapidly. You also can implement horizontal scaling to provide a different, and typically more effective, approach to meet fluctuating demand. This option also is available in Azure. In either case, customers can minimize usage charges by adjusting service levels dynamically.

Pricing also might vary depending on the region in which your services will be hosted and, with respect to licensed products, on the licensing model that is applicable when you implement them in a public cloud.

To estimate the cost of Azure services that you plan to provision, you can use the Azure pricing calculator. This web-based tool allows you to pick different types of Azure services, specify their total projected usage (in hours, weeks, or months), pricing tier, target Azure region, and support options. Then based on this information, you can determine the overall cost of a solution that meets your need.

You also can use the full calculator node for more complex Azure subscriptions. This node enables you to select individual services and their configuration options from all available Azure services.

After you select and configure your Azure subscription services, you can proceed to purchase and provision the subscription.

Here is the link to access the Azure pricing tool:

Azure PowerShell to manage Azure Subscriptions

After you install the Azure PowerShell modules, you can connect the Azure PowerShell session to the Azure subscriptions that you want to manage. To establish this connection, you first need to authenticate by using an account that exists in the Azure AD tenant and that is associated with the target subscription.

This can be a Microsoft account that you either used to create the subscription or added subsequently to the subscription’s Azure AD tenant. Alternatively, you can also create new accounts in Azure AD. These accounts were formerly referred to as organizational accounts and are now known as work or school accounts.

When managing Azure Resource Manager resources, you authenticate by running the Add-AzureRmAccount cmdlet. By default, running this cmdlet opens a browser window prompting you for the user name and the password of a user account with access to the Azure subscription that you intend to manage.

Azure AD authentication is token-based, and after signing in, the user remains authenticated until the authentication token expires. The expiration time for an Azure AD token is 12 hours.

After you authenticate, you can use the Get-AzureRmSubscription cmdlet to view a list of subscriptions associated with your account. If you have multiple subscriptions, you can specify the one you want to manage by using the Set-AzureRmSubscription cmdlet and providing either the subscription name or ID. You can identify the subscription name and ID by reviewing the output of the Get-AzureRmSubscription cmdlet.

After you authenticate from within a Windows PowerShell session, Azure PowerShell automatically generates a collection of session-related objects, which is known as the session context. That context contains objects such as the account, Azure subscription, and corresponding Azure AD tenant. You can manage the content of the context by using the Set-AzureRmContext and Select-AzureRmSubscription cmdlets and view the context by using the Get-AzureRmContext cmdlet.

When managing Azure Service Management services, you authenticate by running the Add-AzureAccount cmdlet. For access to subscription management functionality that is equivalent to that from Get-AzureRmSubscription and Select-AzureRmSubscription, you can run the corresponding Azure PowerShell cmdlets, including Get-AzureSubscription and Select-AzureSubscription. However, in this case, no corresponding session context exists, so you need to manage its components separately.