My interpretation of the SLA, from the SLA documentation and this link:
https://social.msdn.microsoft.com/Forums/azure/en-US/9a95dcd6-ba25-4b2d-9f13-d3896261d8ac/service-bus-sla-what-does-it-really-mean?forum=servbus
Is that Azure Service bus considers outages or lack of communication of <1minute to be within SLA. Does this same SLA apply to lock refreshes? We currently refresh locks with 30 seconds remaining on the lock, but occasionally get large batch
failures. My interpretation would be that this is in line with Azure Service Bus losing communication for >30s, leading to locks expiring.
Is this a valid interpretation? If this is a valid interpretation, I am assuming then that if I have a long running process, that I will be required to refresh earlier than with 30 seconds remaining on the lock?
Thanks!
Nathan