Azure queue triggered function - avoiding loss of messages

If your Azure function is triggered by a message from a queue and that Azure function is reliant upon a resource and that resource becomes unavailable, is there a recommended design pattern to implement to avoid loss of messages and ensuring that messages don't end up on the dead letter queue?

What is required is a way for the project that created the Brokered message and puts the message onto the queue, for that project to detect that the resource is currently unavailable and to put the queue into a suspended state so any messages currently in the queue don't get processed and wait until the queue is un-suspended.