Skip to main content
When a plan includes a sensitive step, such as a Microsoft 365 password reset, the agent waits for the requesting employee to approve an MFA push before it runs that step.

How it works

1

Agent detects a sensitive operation

As the agent builds its plan, it identifies that one or more steps require elevated assurance, such as resetting a Microsoft 365 password or creating a new admin account.
2

Agent initiates verification

The agent calls the identity verification service, which sends a push to the employee’s authenticator app. The agent tells the employee on the source ticket, call, or chat that they will receive a verification push and should approve it.
3

Employee approves the push notification

The employee opens their authenticator app and approves the push notification.
4

Agent receives the result

Rallied gets the result from the provider automatically. The agent does not need to ask the employee anything further.
5

Agent proceeds or stops

If the employee approved the push, the agent proceeds with the sensitive operation and confirms completion on the source ticket, call, or chat. If not, it stops. See What happens when verification fails.

Supported providers

When your Microsoft 365 integration is connected, the agent triggers MFA through the user’s registered method. That is usually a Microsoft Authenticator push, or whatever method the user has registered.
  • The employee receives a standard Microsoft Authenticator push, identical to the ones they already use for Microsoft 365 sign-ins.
  • Rallied gets the result automatically through Microsoft Graph.

Configuration

Identity verification needs no configuration beyond connecting your MFA integration. Once Microsoft 365 or Traceless is connected, the agent triggers identity verification whenever it determines an operation is sensitive. Your technicians don’t need to do anything.
Credential resets, admin privilege changes, and permission grants always trigger identity verification. The agent classifies the request automatically. You don’t define which operations qualify.
If you use Traceless, you can turn off requester verification from its integration detail page. When it’s off, Traceless sends no push. A technician must approve the agent’s plan instead, and the plan states that the requester’s identity was not verified. See Turn off requester verification.

What happens when verification fails

The agent immediately stops. It reports the denial on the source ticket, call, or chat and does not execute the action. The employee can resubmit their original request if they want to try again.
If the employee doesn’t respond within the provider’s timeout window, the verification expires:
  • Microsoft 365: up to 3 minutes
  • Traceless: up to 5 minutes
The agent reports the timeout on the source ticket, call, or chat and does not execute the action.
If the employee has no MFA device enrolled with the connected provider, the provider can’t deliver the push. The agent reports that verification could not be completed and escalates the request to your technicians for manual handling.
If verification fails or times out, the agent never executes the sensitive operation, regardless of other approvals already in place. Each new attempt needs a fresh verification.