You are designing the security and access control architecture for an Azure Storage account named clinicaldata that contains proprietary research datasets. The solution must satisfy the following requirements:
- Internal researchers must only be granted access to the data during active project phases, which typically last up to 90 days. They must not have permanent standing permissions.
- Permissions for the internal researchers must be managed collectively to minimize administrative overhead.
- An external third-party analysis tool requires write access to a specific container for the same 90-day period. The tool does not support Microsoft Entra ID authentication.
- Access for the third-party tool must be easily revoked if a security compromise is suspected, without rotating the storage account keys and without affecting other workloads.
Which access control configuration should you recommend to meet these requirements?
- AAssign researchers to a Microsoft Entra ID security group configured with an active role assignment in Privileged Identity Management (PIM) for the Storage Blob Data Reader role. For the third-party tool, generate an ad-hoc Service Shared Access Signature (SAS) token with a 90-day validity period.
- Assign researchers to a Microsoft Entra ID security group configured with an eligible role assignment in Privileged Identity Management (PIM) for the Storage Blob Data Reader role. For the third-party tool, generate a Service Shared Access Signature (SAS) token associated with a Stored Access Policy.Answer
- CAssign the Storage Blob Data Reader role directly to each researcher's Entra ID account as an active assignment. For the third-party tool, generate an ad-hoc User Delegation SAS token with a 90-day validity period.
- DAssign researchers to a Microsoft Entra ID security group. For the third-party tool, generate an ad-hoc Service Shared Access Signature (SAS) token with a 90-day expiration period, signed directly with the storage account key without a stored access policy.