Diagram Header Lease For Free

The Break(Nullable<TimeSpan>, RequestConditions, Cancellation) operation breaks the blob or container's previously-acquired lease (if it exists). Once a lease is broken, it cannot be renewed. Any authorized request can break the lease; the request is not required to specify a matching lease ID.

A lease on a blob provides exclusive write and delete access to the blob. To write to a blob with an active lease, a client must include the active lease ID with the write request. The lease is granted for the duration specified when the lease is acquired.

A lease can only be cleanly released by using the lease id that was returned during the original lease operation. You can change the lease state to available manually by leasing and releasing the blob using Azure CLI, or any other SDK.

The lease may be released if the client lease id specified matches that associated with the container or blob. Releasing the lease allows another client to immediately acquire the lease for the container or blob as soon as the release is complete. :keyword ~datetime. datetime if_modified_since: A DateTime value.

Releasing the lease allows another client to immediately acquire the lease for the blob, as soon as the release is complete. break : Breaks the lease, if the blob has an active lease. After a lease is broken, it can't be renewed.

About blob leases A lease creates and manages a lock on a blob for write and delete operations. The lock duration can be 15 to 60 seconds, or can be infinite. A lease on a blob provides exclusive write and delete access to the blob.

Any authorized request can break the lease; the request is not required to specify a matching lease ID. When a lease is broken, the lease break period is allowed to elapse, during which time no lease operation except break and release can be performed on the container or blob.