An enterprise is migrating a legacy batch processing system to Azure. The system consists of an on-premises scheduler service that must securely upload transaction logs to an Azure Blob Storage container. Corporate security policies strictly prohibit storing passwords, client secrets, or access keys in the service configuration. You must establish authentication using a Microsoft Entra ID service principal configured with a client certificate.
You need to configure the required Microsoft Entra ID and Azure resources to establish this secure communication flow.
Which five actions should you perform in sequence? To answer, arrange the actions from the list of actions in the correct order.
- 1Generate a self-signed certificate locally and export the public key certificate (.cer) file.
- 2Create an application registration in Microsoft Entra ID.
- 3Upload the public key (.cer) file to the Certificates & secrets section of the application registration.
- 4Assign the Storage Blob Data Contributor role to the application's service principal at the storage account scope.
- 5Configure the scheduler service to authenticate using the client certificate's private key to acquire an Entra ID token.
Cevap
Generate a self-signed certificate locally and export the public key -> Create an application registration in Microsoft Entra ID -> Upload the public key certificate to the application registration -> Assign the Storage Blob Data Contributor role to the application's service principal -> Configure the scheduler service to authenticate using the client certificate's private key.
Establishing a secure connection without secrets requires a certificate-based flow. First, the certificate pair must be generated on the client machine to create the public key. Next, the application is registered in Microsoft Entra ID to establish its identity. After registration, the public key is uploaded to Microsoft Entra ID to associate the credential with the registration. Next, the Storage Blob Data Contributor role is assigned to the service principal in the tenant to allow data plane access. Finally, the daemon scheduler is configured with the private key locally to acquire access tokens using the client credentials flow.
Adım Adım Çözüm
Anahtar Kavram
Configuring certificate-based client credentials flow using Microsoft Entra ID application registrations, local service principals, and role assignments.
Tahmini Süre:3m 0s