Skip to content

Commit 9935f7f

Browse files
Edits
1 parent 9ef6778 commit 9935f7f

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

articles/storage/blobs/TOC.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -609,6 +609,8 @@ items:
609609
href: storage-blob-container-delete.md
610610
- name: List containers
611611
href: storage-blob-containers-list.md
612+
- name: Manage container leases
613+
href: storage-blob-container-lease.md
612614
- name: Manage properties and metadata
613615
href: storage-blob-container-properties-metadata.md
614616
- name: Blob actions
@@ -627,8 +629,8 @@ items:
627629
href: storage-blob-tags.md
628630
- name: Manage blob properties and metadata
629631
href: storage-blob-properties-metadata.md
630-
- name: Create and manage leases
631-
href: storage-blob-container-lease.md
632+
- name: Manage blob leases
633+
href: storage-blob-lease.md
632634
- name: Create and manage snapshots
633635
href: snapshots-manage-dotnet.md
634636
- name: Create and list blob versions

includes/storage-dev-guides/storage-dev-guide-about-container-lease.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,6 @@ ms.author: pauljewell
1010
ms.custom: include file
1111
---
1212

13-
A lease establishes and manages a lock on a container for delete operations. The lock duration can be 15 to 60 seconds, or can be infinite. A lease on a container provides exclusive delete access to the container. A container lease only controls the ability to delete the container using the [Delete Container](/rest/api/storageservices/delete-container) REST API operation. To delete a container with an active lease, a client must include the active lease ID with the delete request. All other container operations will succeed on a leased container without the lease ID. If you've enabled [container soft delete](soft-delete-container-overview.md), you can restore deleted containers.
13+
A lease establishes and manages a lock on a container for delete operations. The lock duration can be 15 to 60 seconds, or can be infinite. A lease on a container provides exclusive delete access to the container. A container lease only controls the ability to delete the container using the [Delete Container](/rest/api/storageservices/delete-container) REST API operation. To delete a container with an active lease, a client must include the active lease ID with the delete request. All other container operations succeed on a leased container without the lease ID. If you've enabled [container soft delete](../../articles/storage/blobs/soft-delete-container-overview.md), you can restore deleted containers.
1414

1515
Lease operations are handled by the [BlobLeaseClient](/dotnet/api/azure.storage.blobs.specialized.blobleaseclient) class, which provides a client containing all lease operations for blobs and blob containers. To learn more about lease states and when you might perform an action on a lease, see [Lease states and actions](#lease-states-and-actions).

0 commit comments

Comments
 (0)