Question 710
A production Azure security implementation shows this failure: An unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events. What should the engineer implement first to address the weakness?
Explanation
Correct Answer
The cause is: Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. The appropriate change is: Inspect service principal sign-in logs and correlated credential or conditional policy results. Verify it with this outcome: The failing app identity, time and error reason are identified in the service principal log stream.
Incorrect Answers
This action concerns cross tenant service principal consent, where Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. The reported incident instead involves Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.
This action concerns user consent policies for third party apps, where The user consent configuration permits risky OAuth grants without publisher and permission restrictions. The corrective response here is “Inspect service principal sign-in logs and correlated credential or conditional policy results”; this alternative does not provide that response.
This action concerns expose an api permission scope, where The protected application registration has not exposed an OAuth permission scope for the required delegated operation. The stem reports an unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events; this control addresses a different failure condition.