Skip to content

Commit 136d352

Browse files
Update billing explanation for soft delete in Azure Files pv2
Clarified the billing explanation for deleted file shares with soft delete enabled, emphasizing the billing and resource usage details.
1 parent e0adcaf commit 136d352

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/storage/files/understanding-billing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -238,7 +238,7 @@ Snapshots are always differential from the live share and from each other. In th
238238
Some value-added services for Azure Files use snapshots as part of their value proposition. For more information, see [value-added services for Azure Files](#value-added-services).
239239

240240
### Provisioned v2 soft delete
241-
Deleted file shares in storage accounts with soft-delete enabled are billed based on the used storage capacity of the deleted share for the defined retention period. To ensure that a deleted file share can always be restored, the provisioned storage, IOPS, and throughput of the share count against the storage account's limits until the file share is purged. However, they aren't billed. For more information on soft delete, see [How to enable soft delete on Azure file shares](storage-files-enable-soft-delete.md).
241+
When soft delete is enabled, deleted file shares are billed based on their used storage capacity during the retention period. The provisioned storage, IOPS, and throughput of a deleted share continue to count toward the storage accounts limits until the share is purged, ensuring it can be restored. However, these resources are not billed. For details on enabling soft delete, see [How to enable soft delete on Azure file shares](storage-files-enable-soft-delete.md).
242242

243243
### Provisioned v2 billing meters
244244
File shares provisioned using the provisioned v2 billing model are billed against the following billing meters:

0 commit comments

Comments
 (0)