Skip to content

Commit f260c04

Browse files
committed
Updates.
1 parent f0feae5 commit f260c04

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-machines/includes/disks-sas-change.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@
99
ms.custom: include file
1010
---
1111
> [!IMPORTANT]
12-
> On February 15th, 2025, the Shared Access Signature (SAS) access time for disks and snapshots will be limited to a maximum of 60 days. Trying to generate a SAS with an expiration longer than 60 days results in an error. Any existing disk or snapshot SAS with expirations longer than 60 days won't be supported after 60 days and may result in a 403 error during authorization.
12+
> On February 15th, 2025, the Shared Access Signature (SAS) access time for disks and snapshots will be limited to a maximum of 60 days. Trying to generate a SAS with an expiration longer than 60 days results in an error. Any existing disk or snapshot SAS created with an expiration longer than 60 days may stop working 60 days after the date of creation and will result in a 403 error during authorization.
1313
14-
Review all your calls that generate a managed disk or snapshot SAS to ensure that they're requesting access for 60 days (5,184,000 seconds) or less. If a SAS's access is longer than 60 days, you should revoke its access and generate a new SAS that requests access for 60 days (5,184,000 seconds) or less.
14+
Review all your calls that generate a managed disk or snapshot SAS to ensure that they're requesting access for 60 days (5,184,000 seconds) or less. If a SAS's access is longer than 60 days, revoke its access and generate a new SAS that requests access for 60 days (5,184,000 seconds) or less. use shared access signatures (SAS) with smaller expiration dates to guard against risks such as a SAS leaking, which can let anyone who obtains it access to your disks. You should make these changes prior to February 15, 2025 to prevent service interruption. The following links can be used to find, revoke, and request a new SAS.
1515

1616
- To check if a disk has an active SAS, you can either use the [REST API](/rest/api/compute/disks/get?view=rest-compute-2024-03-01&tabs=HTTP#diskstate), the [Azure CLI](/cli/azure/disk?view=azure-cli-latest#az-disk-show), or the [Azure PowerShell module](/powershell/module/az.compute/get-azdisk?view=azps-12.0.0), and examine the **DiskState** property.
1717
- To revoke a SAS, you can use either the [REST API](/rest/api/compute/disks/revoke-access?view=rest-compute-2024-03-01&tabs=HTTP), the [Azure CLI](/cli/azure/disk?view=azure-cli-latest#az-disk-revoke-access), or the [Azure PowerShell module](/powershell/module/az.compute/revoke-azdiskaccess?view=azps-12.0.0).

0 commit comments

Comments
 (0)