A partner's reporting job needs to read one blob, sales-2026.csv, in the exports container for the next 24 hours. The exports container also holds files for other partners. Your security team requires that storage account keys are not used to sign anything handed to partners. Which SAS should you issue?
Choose one.
Least-privilege SAS design combines two choices: what signs the token (account key versus Entra user delegation key) and what the token covers (signed resource, permissions and expiry).
The user delegation SAS on the single blob satisfies both constraints: no account key is involved, and the token can read only sales-2026.csv for 24 hours. The service SAS has the right scope but the wrong signer. The container-scoped user delegation SAS has the right signer but the wrong scope, because the container holds other partners' data. The account SAS fails on both counts.
- Apply the signing constraint first: rule out the account SAS and the key-signed service SAS.
- Compare the remaining user delegation SAS options by signed resource.
- Container scope with list permission exposes other partners' blobs, so reject it.
- Choose blob scope, read permission and a 24-hour expiry.
Exam tip: Pick the signer from the key policy, then shrink the signed resource and permissions to exactly what the caller needs.
Configure Access to Azure Storage: SAS, Keys & Firewalls (AZ-104) — the lesson that teaches this.