You are developing a background daemon service named DataArchiver that runs on a schedule to back up documents from all user OneDrive libraries to an Azure Blob Storage container. The service must authenticate silently without any user interaction.
You register DataArchiver in Microsoft Entra ID. You need to configure the permissions for Microsoft Graph to allow the service to read the files.
Which configuration should you apply to the application registration to meet the requirements while adhering to the principle of least privilege?
- Configure Microsoft Graph Application permissions for Files.Read.All, and obtain tenant-wide admin consent.Cevap
- BConfigure Microsoft Graph Delegated permissions for Files.Read.All, and have each user log in once to consent to the permissions.
- CConfigure Microsoft Graph Delegated permissions for Files.Read.All, and configure a Shared Access Signature (SAS) token on the target storage account to delegate user authority.
- DConfigure Microsoft Graph Application permissions for Files.Read.All, and configure a Shared Access Signature (SAS) token in the application registration settings to authorize the client credentials.
Cevap
Configure Microsoft Graph Application permissions for Files.Read.All, and obtain tenant-wide admin consent.
The correct configuration is to use Microsoft Graph Application permissions for Files.Read.All and obtain tenant-wide admin consent. Because the daemon runs as a background service without a signed-in user, it must authenticate as its own identity using Application permissions rather than Delegated permissions. Additionally, reading data across all users' OneDrive libraries is a high-privilege operation that requires tenant-wide admin consent.
Adım Adım Çözüm
Anahtar Kavram
Configuring Application Permissions and Consent for Daemon Apps
Tahmini Süre:1m 30s