Question 870
During a cloud security review, the operations team observes: Two Azure Functions need a consistent workload principal across independent deployments, but each uses a transient system-assigned identity that breaks shared policy references. What should the engineer implement first to address the weakness?
Explanation
Correct Answer
The cause is: Separate system-assigned identities do not provide the stable reusable principal desired across resources. The appropriate change is: Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly. Verify it with this outcome: Both functions obtain tokens for the approved user-assigned identity without duplicating secrets.
Incorrect Answers
This action concerns application client secret expiration, where The app registration client credential has expired and the workload has no safe rotation mechanism. The reported incident instead involves Separate system-assigned identities do not provide the stable reusable principal desired across resources.
This action concerns enterprise application service principal, where The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. The corrective response here is “Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly”; this alternative does not provide that response.
This action concerns key vault data role for workload identity, where Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. The stem reports two Azure Functions need a consistent workload principal across independent deployments, but each uses a transient system-assigned identity that breaks shared policy references; this control addresses a different failure condition.