What will my bill look like if I use the S1 tier?

All APIs in the S1 tier are charged at a flat rate of USD 5 per 1,000 transactions. Learn more about Azure Maps pricing

Related questions and answers

  • You can change the configuration of your Azure Maps account at any time. For instructions on how to make changes in the Azure portal, please see the documentation on managing the pricing tier of your Azure Maps account.

  • When you use Site Recovery, you incur charges for the Site Recovery licence, Azure storage, storage transactions and outbound data transfer. The Site Recovery licence is per protected instance, where an instance is a virtual machine or a physical server.

    • If a virtual machine disk replicates to a standard storage account, the Azure Storage charge is for the storage consumption. For example, if the source disk size is 1 TB, and 400 GB of storage is used, Site Recovery creates a 1 TB VHD in Azure, but the storage charged is 400 GB (plus the amount of storage space used for replication logs).
    • If a virtual machine disk replicates to a premium storage account, the Azure storage charge is for the provisioned storage size, rounded out for the nearest premium storage disk option. For example, if the source disk size is 50 GB, Site Recovery creates a 50 GB disk in Azure, and Azure maps this to the nearest premium storage disk (P10). Costs are calculated on P10, and not on the 50 GB disk size. Learn more. If you're using premium storage, a standard storage account for replication logging is also required, and the amount of standard storage space used for these logs is also billed.
    • No disks are created until a test failover or a failover. In the replication state, storage charges under the category of "Page blob and disk" as per the storage pricing calculator are incurred. These charges are based on the type of storage – premium or standard – and the data redundancy type, including LRS, GRS, RA-GRS and more.

    If the option to use managed disks on a failover is selected, charges for managed disks apply after a failover or test failover. Managed disks charges do not apply during replication. During replication, storage charges under the category of “Unmanaged disks and page blobs” are incurred. These charges are based on the storage type of premium/standard and the data redundancy type – LRS, GRS, RA-GRS, etc. Example: For a VM replicating to premium storage with 128 GB OS disk and 500 GB data disk: 1. During replication: Storage charges under the category of “Unmanaged disks and page blobs” for premium storage disk sizes P10 and P20 are incurred. The size of the disks being replicated (128 GB and 500 GB) are rounded off to the nearest unmanaged premium disk size of P10 (128 GB) and P20 (512 GB) for billing. A standard storage account for logging delta changes during replication is also used. Storage charges under the category of “Unmanaged disks and page blobs” based on the amount of standard storage used for these logs is also billed. 2. During a Test failover or after failover to managed disks: Managed disk charges for premium managed disks of sizes P10 and P20 apply. Example: For a VM replicating to standard storage with 32 GB OS disk and 250 GB data disk: 1. During replication: Storage charges under the category of “Unmanaged disks and page blobs” for standard storage are incurred. 2. During a Test failover or after failover to managed disks: Managed disk charges for standard managed disks of sizes S4(32 GB) and S15(256 GB) apply. As you can see, the size of the disks (32 GB and 250 GB) have been rounded off to the nearest standard managed disk size of S4 (32 GB) and S15 (256 GB).

    • If the option to use managed disks on a failover is not selected, storage charges under the category of "Unmanaged Disks and Page blobs" as per the Storage pricing calculator are incurred after failover. These charges are based on the type of storage – premium or standard – and the data redundancy type, including LRS, GRS, RA-GRS and more.
    • Storage transactions are charged during steady-state replication and for regular virtual machine operations after a failover or test failover. But these charges are negligible. Costs are also incurred during test failover, where the virtual machine, storage, egress and storage transactions costs will be applied.
  • Please refer to the ExpressRoute Documenation for ExpressRoute peering location to zone mapping.

  • Learn how to map a custom domain.

  • The Cloud Service Dependency Map (CSDM) documents critical system dependencies, both upstream and downstream, that could impact your cloud services. This will help your IT staff recognise potential issues before they happen, and help them resolve issues faster when a problem occurs.

  • It depends on the current state of a channel. Possible values include:

    • Stopped. This is the initial state of the channel after its creation. In this state, the channel properties can be updated but streaming is not allowed.
    • Starting. The channel is being started. No updates or streaming are allowed during this state. If an error occurs, the channel returns to the “Stopped” state.
    • Running. The channel is capable of processing live streams.
    • Stopping. The channel is being stopped. No updates or streaming are allowed during this state.
    • Deleting. The channel is being deleted. No updates or streaming are allowed during this state. The following table shows how channel states map to the billing mode. |Channel state|Portal UI indicators|Billed?| |---|---|---| |Starting|Starting|No (transient state)| |Running|Ready (no programs running) or Streaming (at least one program running)|Yes| |Stopping|Stopping|No (transient state)| |Stopped|Stopped|No|