The Australia Regions are available to customers with a business presence in Australia or New Zealand.
The India regions are currently available to volume licensing customers and partners with a local enrollment in India. For more information, contact your Microsoft India partner manager or account manager. The India regions will open to direct online Azure subscriptions in 2016.
Important: The price in R$ is merely a reference; this is an int'l transaction and the final price is subject to exchange rates and the inclusion of IOF taxes and an eNF will not be issued.
Service Bus comes in Basic, Standard and Premium tiers. Here’s how they compare:
|ForwardTo / SendVia||–|
|Message Size||256 KB||256 KB||1 MB|
|Brokered connections included||100||1,0001||1,000 per MU|
|Brokered connections (overage allowed)||–||(billable)||Up to 1,000 per MU|
An operation is any API call to the Service Bus service.
|Operations||$0.05 per million operations|
|Base charge 1||$10/mo|
|First 12.5M Ops / Month||Included|
|Next 88M Ops (13M - 100M Ops) / Month||$0.8 per million operations|
|Next 2,400M Ops (100M - 2,500M Ops) / Month||$0.5 per million operations|
|Over 2,501M Ops / Month||$0.2 per million operations|
|Daily (special pricing through August 31, 2016)||$11.13 fixed rate per Message Unit|
|Daily (starting September 1, 2016)||$22.26 fixed rate per Message Unit|
Number of AMQP connections or HTTP calls to Service Bus.
|First 1K / Month||Included|
|Next 99K (1K – 100K) / Month||$0.03 per connection / month|
|Next 400K (100K – 500K) / Month||$0.025 per connection / month|
|Over 500K / Month||$0.015 per connection / month|
|Brokered connections are not charged in the Premium tier.|
Relays are available only in Standard tier and are charged by message volume and relay hours.
|Relay hours||$0.1 for every 100 relay hours|
|Messages||$0.01 for every 10,000 messages|
The Relay counts each message sent to the Relay and each message sent by the Relay as billable. A billable message is a data frame of at most 64Kbyte. If a message exceeds 64Kbyte, such as an HTTP reply that returns an image, each further 64Kbyte counts as an additional billable message. For a normal relayed service that implements a request/response scheme, the request first travels to the Relay, then to the service, and the reply traverses the same path. That amounts to at least four billable messages. For a multicast service that has 4 listeners, the message sent to the Relay counts as one message, and the 4 messages sent to the listeners also each count as a message, resulting in a total of 5 messages.
For brokered entities (queues and topics/subscriptions), an operation is any API interaction with Service Bus service on any protocol.
A send, receive delete for a message that is less than or equal to 64KB in size is considered as one billable operation. If the message is greater than 64KB in size, the number of billable operations is calculated according to the message size in multiples of 64KB. For example, an 8 KB message sent to the Service Bus will be billed as one operation, but a 96 KB message sent to the Service Bus will be billed as two operations. Reading the 8KB message with a lock and then completing or explicitly abandoning the message will be billed as two operations. Renewing the lock on a message also incurs an operation.
Multiple deliveries of the same message (for example, message fan out to multiple subscribers or message retrieval after abandon, deferral, or dead lettering) will be counted as independent operations. For example, in the case of a topic with three subscriptions, a single 64KB message sent and subsequently received will generate four billable operations, one “in” plus three “out”, assuming all messages are delivered to all subscriptions and deleted during the read.
Additionally creating, reading (listing), updating and deleting a queue, topic or subscription will each incur an operation charge.
Operations are API calls made against queue or topic/subscription service endpoints. This includes Management, Send/Receive and Session State Operations.
|Management||Create, read, update, delete against queues or topics/subscriptions|
|Messaging||Sending and receiving messages with queues or topics/subscriptions|
|Session state||Getting or setting session state on a queue or topic/subscription|
|Premium tier does not charge for Operations up to the purchased capacity limit|
Relay hours are billed for the cumulative amount of time during which each Service Bus Relay is “open”. A Relay is implicitly instantiated and opened at a given Service Bus address (service namespace URL) when a Relay-enabled WCF service, or “Relay listener,” first connects to that address. It is closed only when the last listener disconnects from its address. Therefore, for billing purposes a Relay is considered “open” from the time the first Relay listener connects, to the time the last Relay listener disconnects from the Service Bus address of that Relay.
Microsoft charges for the peak number of concurrent brokered connections that exceed the included quantity (1,000 in the Standard and Premium tier). Peaks are measured on an hourly basis, prorated by dividing by 744 hours in a month, and added up over the monthly billing period. The included quantity (1,000 brokered connections per month) is applied at the end of the billing period against the sum of the prorated hourly peaks.Examples:
Yes they do. There are no connection charges for sending events using HTTP, regardless of the number of sending systems/devices. Receiving events with HTTP using a timeout greater than zero, sometimes called “long polling”, generate brokered connection charges. AMQP connections generate brokered connection charges regardless of whether the connections are being used to send or receive. Note that 100 brokered connections are allowed at no charge in a Basic namespace (this is also the maximum number of brokered connections allowed for the Azure Subscription). The first 1,000 brokered connections across any/all Standard namespaces in an Azure Subscription are included at no extra charge (beyond the base charge). Since these allowances are enough to cover many service-to-service messaging scenarios, brokered connection charges usually only become relevant if you plan to use AMQP or HTTP long-polling with a large number of clients, i.e. to achieve more efficient event streaming or enable bi-directional communication with thousands/millions of devices or app instances.
No. The Standard base charge is billed only once per month per Azure subscription. This means that after you create a single Standard Tier Service Bus namespace, you will be able to create as many additional Standard Tier namespaces as you like under that same Azure subscription without incurring additional base charges.
The Premium tier of Service Bus Messaging provides all the messaging features of Azure Service Bus queues and topics with predictable, repeatable performance, higher throughput, and improved availability. The Premium tier uses a dedicated resource allocation model to provide workload isolation and consistent performance. Because the compute and memory resources in the Premium Tier are dedicated, there are no per-message transaction charges as in other tiers. All transactions are included in the message unit allocation.
A Messaging Unit is a set of dedicated resources exclusively reserved for Premium namespaces. This resource set can deliver a consistent and repeatable performance of messaging workloads. Each Premium namespace can have 1, 2, or 4 Messaging Units and the resource allocation grows linearly: 2 Messaging Units is twice as many resources as 1 Messaging Unit.
The Premium tier of Service Bus Messaging is a flat daily rate per Messaging Unit purchased. Namespaces created as Premium can have 1, 2, or 4 Messaging Units which will each accrue the given number of Messaging Unit daily rate charges. Premium namespaces can have the number of purchased Messaging Units changed at any time, but the daily rate is based on the maximum number of Message Units assigned to the namespace at any time.
Yes, it is technically possible to upgrade and downgrade between Premium and other tiers.
Please see this article for additional Service Bus billing FAQs