For brokered entities (queues, topics/subscriptions, message buffers), an operation is any API call to the Service Bus service.
A send, receive, or 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 deleting the message will be billed as two operations.
Multiple deliveries of the same message (for example, message fan out to multiple listeners 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).
Receiving a message with a ReceiveMode of PeekLock and later deleting that message with a complete call will incur two separate operations. Renewing the lock on a message also incurs an operation.
Additionally creating, reading (listing), updating and deleting a queue, topic or subscription will 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|