A legal services firm is designing a secure Azure Blob storage solution for hosting sensitive litigation files. External forensic investigators require temporary read-only access to specific folders inside a container for a period of up to 48 hours. The access must be restricted to a specific external public IP range. The firm's security policy requires that administrative control must be maintained to immediately revoke access if a breach is suspected, without rotating the storage account access keys or impacting other active access tokens. Which two configuration steps should you include in the design to meet these security requirements? (Select TWO.)
- Create a stored access policy on the target container and generate a Shared Access Signature (SAS) token associated with that policy.Answer
- BGenerate an ad-hoc Shared Access Signature (SAS) token with a 48-hour expiration directly on the container parameters.
- CAssign the Storage Blob Data Reader role directly to the individual external investigator Microsoft Entra ID user accounts.
- Configure the allowed public IP address range directly on the parameters of the generated Shared Access Signature (SAS) token.Answer
- EConfigure a Microsoft Entra Privileged Identity Management (PIM) active assignment for the Storage Blob Data Reader role on the storage account.
Answer
Create a stored access policy on the target container, generate a Shared Access Signature (SAS) token associated with that policy, and configure the allowed public IP address range directly on the parameters of the generated SAS token.
To implement immediately revocable, time-bound access for external users without rotating storage account keys, you must create a stored access policy and generate a SAS token associated with that policy. Deleting or modifying the policy immediately invalidates the SAS token. To restrict the network origin, you must configure the allowed public IP address range directly in the SAS token parameters.
Step-by-Step Solution
Key Concept
Stored Access Policies vs. Ad-hoc SAS and parameter-based network constraints for access control.
Estimated Time:2m 0s