Encrypt Online
Theme

Azure Storage SAS Debugger

Find expiry, permission, and resource mismatches behind a failed SAS request

Checks run in your browser. The link is not opened. A SAS URL grants access; use a test link when possible.

SAS URL and requestNo Azure login or account key needed
Request details and reference time

Use the specific error code in the response body or x-ms-error-code header.

Leave empty to use the current time. Set the failure time when investigating an older request.

SAS dates and permissions

Choose the operation that failed to check its permissions and resource scope. For create-only block uploads, add the request version and whether the target blob is new.

For a 403 response, select the error code returned by Azure to see the relevant checks.

Debug Azure SAS 403 errors

AuthenticationFailed can point to timing, encoding, or a changed signature. AuthorizationPermissionMismatch points to the request's permission requirements. The exact Blob operation matters: listing a container and downloading a blob require different permissions and resource scopes.

Start with the original SAS value and the operation that failed. Follow the Azure SAS 403 troubleshooting guide for CLI and request examples.

SAS types and access policies

Account, service, and user delegation SAS use different signed fields. The operation checks here cover Blob Storage REST requests. If the dates and permissions look correct, check the stored access policy, credential revocation, firewall rules, RBAC, and container encryption-scope policy that apply to the request.

Use an Azure SDK or Storage Explorer to create a replacement SAS. Changing a signed permission or expiry invalidates its signature. For deployment identity failures, use the Entra Federated Credential Debugger.

Microsoft's Azure Storage 403 reference

Single uploads and block uploads

Download examples (JSON)

Compare create-only and write permissions for single uploads and block uploads using request version 2023-11-03.

Create-only permission for a single upload

A create-only SAS has the permission needed for a single Put Blob that creates a new block blob.

The c permission covers creating a new block blob in one Put Blob. A live upload still needs a valid SAS signature and Azure authorization.

Inputs and expected values
  1. Paste the SAS URL into the debugger.
  2. Choose Create a blob (single upload).
  3. Under Request details and reference time, set the reference time to 2026-10-20 12:00:00 UTC.
  4. Select Inspect SAS and open Selected operation to see the permission check.
SAS URL
https://storage.example.invalid/uploads/example.txt?sv=2023-11-03&sr=b&sp=c&st=2026-10-20T11%3A00%3A00Z&se=2026-10-20T13%3A00%3A00Z&spr=https&sig=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA%3D
Request version
2023-11-03
Permission letters
c
Operation permission check
success

Create-only permission fails for older block requests

The same create-only SAS lacks w for Put Block and Put Block List with request version 2023-11-03.

Request version 2023-11-03 needs w to stage and commit blocks. Generate a new SAS with write permission for that upload.

Inputs and expected values
  1. Paste the SAS URL and choose Upload blocks (SDK or large file).
  2. Under Request details and reference time, enter block request version 2023-11-03 and choose Create a new blob.
  3. Set the reference time to 2026-10-20 12:00:00 UTC.
  4. Select Inspect SAS. The result identifies the missing w permission.
SAS URL
https://storage.example.invalid/uploads/example.txt?sv=2023-11-03&sr=b&sp=c&st=2026-10-20T11%3A00%3A00Z&se=2026-10-20T13%3A00%3A00Z&spr=https&sig=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA%3D
Request version
2023-11-03
Permission letters
c
Operation permission check
error

Write permission covers the block upload

A SAS containing c and w covers the block-upload permission requirement for request version 2023-11-03.

The w permission covers staging and committing blocks. Generate a replacement SAS for real use; editing sp in an existing signed URL invalidates its signature.

Inputs and expected values
  1. Paste this separate example SAS URL and choose Upload blocks (SDK or large file).
  2. Under Request details and reference time, enter block request version 2023-11-03 and choose Create a new blob.
  3. Set the reference time to 2026-10-20 12:00:00 UTC.
  4. Select Inspect SAS and open Selected operation to see the permission check.
SAS URL
https://storage.example.invalid/uploads/example.txt?sv=2023-11-03&sr=b&sp=cw&st=2026-10-20T11%3A00%3A00Z&se=2026-10-20T13%3A00%3A00Z&spr=https&sig=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA%3D
Request version
2023-11-03
Permission letters
cw
Operation permission check
success

These examples check permissions for a new blob with request version 2023-11-03. The placeholder signatures grant no access. From request version 2026-04-06, Put Block and Put Block List can also create a new block blob with c permission; overwrites still require w.

Checked 2026-10-20. From the site's webapp3 directory, run npm run check:citation-evidence to compare the tool results with the saved expectations. The JSON includes every input, expected output, and source hash.

Inputs are not saved. The site may load analytics and advertising. Privacy details.