Scenario
An application team may require a non‑interactive user account, such as a synthetic monitoring account or automated script account, to access an application and perform tasks on a recurring basis. Multi‑factor authentication (MFA) during sign‑in may interrupt these automated processes. The application team may request support to allow the account to bypass MFA during authentication. Based on this request, an administrator reviews the account’s authentication activity and, where appropriate, enables or disables the risk‑based authentication (RBA) whitelist setting for the account. This allows the account to bypass MFA for subsequent sign‑ins when required, while ensuring that the change is applied only to approved use cases and not to active user accounts.