none
Service bus costing

    Question

  • I've been running some cost experiments with the Azure Service Bus.  However, the balance on my MSDN subscription doesn't seem to update.  I've been posting messages to the service bus for hours, and the balance hasn't changed.

    Is there a delay in updating the balance on this, or is it, as it appears to be, effectively cost free?

    • Moved by Md Shihab Monday, June 5, 2017 6:54 AM Better suited in Pricing and Billing
    Sunday, June 4, 2017 1:09 PM

Answers

  • The balance typically gets updated every 24 hours.
    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.
    -----------------------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

    • Marked as answer by pcmichaels Friday, June 9, 2017 5:35 PM
    Wednesday, June 7, 2017 9:17 AM

All replies

  • Service Bus is offered in Basic, Standard and Premium tier. What tier are you in?

    For example, if you’re in the Basic tier, then you get to make up to a million operations a month at the cost of $0.05/month. An operation is any API call to the Service Bus service. The limits are higher as you upgrade the tiers. Are you hitting, at least, a million operations mark in your experiments?

    You can also refer Service Bus pricing details for more information.

    -----------------------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

    • Proposed as answer by Md Shihab Monday, June 5, 2017 7:07 AM
    Monday, June 5, 2017 6:53 AM
  • I'm using the free credit on an MSDN Pro account.

    I have run the tests for 100,000 messages, even if reading and writing are two distinct operations, this only amounts to 200,000 operations.  However, what I don't understand it that the following day, the balance did update, and reduced by around £0.12 (~$0.15).

    I'm just trying to get a clear picture of exactly what the pricing model is, and when the balance is scheduled to update:

    - Does the balance update at the end of each day, or is it real-time?

    - If the price is $0.05 / Million transactions then am I misunderstanding what is meant by a "operation"; how many operations would you expect in adding a single message to a queue, and then reading it from that queue?

    Monday, June 5, 2017 7:11 AM
  • The balance typically gets updated every 24 hours.
    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.
    -----------------------------------------------------------------------------------------------------

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

    • Marked as answer by pcmichaels Friday, June 9, 2017 5:35 PM
    Wednesday, June 7, 2017 9:17 AM