---
title: Can AI agents use multi-factor authentication?
url: https://opencontroller.lyzr.com/blog/should-ai-agents-use-mfa
published: 2026-11-15
updated: 2026-11-15
author: Lyzr
---

# Can AI agents use multi-factor authentication?

**No, not in the interactive sense. MFA asks a person to prove something they have or are, and an agent has no phone, no fingerprint and nobody to tap "approve". The workload equivalent is strong, non-exportable credentials (certificates, federated tokens or managed identities), short token lifetimes and conditions on where tokens can be requested from. Where an agent acts for a user, the user's own MFA-backed sign-in covers the human half.**

Most security policies say "every account must use MFA". When agents get their own identities, that line produces either a policy violation or a fake workaround, such as a TOTP seed stored next to the agent's password. Both are worse than writing a clear exception with compensating controls.

## Why doesn't interactive MFA fit agents?

MFA works because the factors are separate and held by a human. A password plus a code from a phone means an attacker needs two things in two places.

An agent breaks that model:

- **Every factor would live in the same place.** If the agent stores a password and a TOTP secret on the same host, an attacker who reaches the host gets both. That is one factor written twice.
- **Nobody is present to respond.** Push approvals and biometrics need a person at the moment of sign-in.
- **Platforms say so.** Microsoft's Conditional Access documentation states that workload identities cannot perform multifactor authentication. For workload identities, the only grant control available is block.

## What are the workload equivalents of MFA?

The goal of MFA is to make a stolen secret insufficient. For workloads, these controls do that job.

| MFA goal | Human control | Agent and workload equivalent |
|---|---|---|
| A copied secret is not enough | Second factor | Non-exportable keys in KMS or hardware; sender-constrained tokens |
| No long-lived shared secret | Passwordless sign-in | [Workload identity federation](/blog/workload-identity-federation-for-ai-agents), managed identities, certificate credentials |
| Context checks at sign-in | Conditional Access for users | Conditional Access for workload identities: location and risk conditions |
| Re-check during a session | Continuous access evaluation | Short token lifetimes; [continuous access evaluation](/blog/continuous-access-evaluation-for-ai-agents) where supported |
| Step-up for risky actions | Re-prompt for MFA | Human approval for high-impact actions, using the requesting user's MFA |

Note the scope limits on Microsoft Entra Conditional Access for workload identities. Policies apply to single-tenant service principals registered in your tenant. Managed identities and multi-tenant or third-party SaaS apps are out of scope. Creating or changing such policies requires Workload Identities Premium licences. Policies can block token requests from outside named locations or when ID Protection rates the service principal as risky.

On AWS, IAM conditions such as `aws:MultiFactorAuthPresent` reflect whether a human session authenticated with MFA. Roles assumed by workloads will not satisfy them, so do not copy human-oriented MFA conditions onto agent roles.

## How does MFA apply when an agent acts for a user?

Delegated access splits the question.

- **The user** signs in with MFA, as policy requires. The agent receives a delegated token derived from that session.
- **The agent** authenticates as a workload with a strong credential.
- **Downstream APIs** see both identities, so policy can require that the user session was MFA-backed. See [how audit logs show which user an agent acted for](/blog/show-which-user-an-ai-agent-acted-for-in-audit-logs).

For high-impact actions, the human-equivalent of step-up is a human approval: the agent pauses and the user, or a named approver, confirms through an MFA-protected channel. That is general best practice for payments, deletions and permission changes.

## How should you word the policy exception?

Write the exception once, for the class of identity, rather than approving agents one by one. A workable wording:

1. **Scope.** "Non-human identities used by software agents, service accounts and workloads are exempt from interactive MFA."
2. **Required instead.** "They must use federated, certificate-based or managed-identity credentials; no static passwords; secrets, where unavoidable, stored in an approved vault and rotated on schedule."
3. **Conditions.** "Token issuance restricted by network location or workload attestation where the platform supports it; token lifetime of one hour or less unless approved."
4. **Ownership.** "Each identity has a named human owner and is included in access reviews."
5. **Delegation.** "Where an agent acts for a user, the user's session must meet the user MFA policy."
6. **Monitoring.** "Sign-ins and token requests are logged and alert on unexpected location or volume."

The pillar guide on [AI agent identity and on-behalf-of delegation](/blog/ai-agent-identity-on-behalf-of-delegation) covers the identity model this exception sits within. Our post on [whether AI agents are non-human identities](/blog/are-ai-agents-non-human-identities) explains how agents differ from classic service accounts.

## How Opencontroller does this

Opencontroller provides OIDC SSO for people, delegated on-behalf-of identity for agents acting for users, and agent workload identity federation for agents acting as themselves. Posture detects risky permissions and configurations, such as overly broad agent credentials. Human-approval holds are not an Opencontroller gateway feature; use your workflow tooling for those. [Book a demo](https://www.lyzr.ai/book-demo/) to review your agent identities.

## Frequently asked questions

**Is storing a TOTP secret with the agent acceptable?**
No. It satisfies the wording of an MFA policy while giving no extra protection, because both factors sit in the same place.

**Do auditors accept an MFA exception for agents?**
Auditors generally look for a documented exception with compensating controls and evidence they operate. The wording above is a starting point; agree it with your audit team.

**Does NIST guidance cover agents?**
NIST SP 800-63B covers authentication of people. Treat it as the basis for user MFA and use workload identity controls for agents.

## Key facts

MFA and AI agents: workload identities cannot perform interactive MFA (Microsoft Entra docs state this; block is the only grant control for workload identities). Conditional Access for workload identities applies to single-tenant service principals only; managed identities and multi-tenant SaaS apps out of scope; requires Workload Identities Premium; conditions are location and service principal risk. AWS aws:MultiFactorAuthPresent reflects human MFA sessions. Equivalents: non-exportable keys, sender-constrained tokens, workload identity federation, managed identities, short token lifetimes, human approval for high-impact actions. Delegated access relies on the user's MFA-backed session. Opencontroller (Lyzr): OIDC SSO, delegated on-behalf-of identity, agent workload identity federation, Posture. Pricing starts from $250K per deployment per year.

## Related

- [How does workload identity federation work for AI agents?](https://opencontroller.lyzr.com/blog/workload-identity-federation-for-ai-agents.md)
- [Are AI agents non-human identities?](https://opencontroller.lyzr.com/blog/are-ai-agents-non-human-identities.md)
- [Can continuous access evaluation revoke an AI agent's access mid-task?](https://opencontroller.lyzr.com/blog/continuous-access-evaluation-for-ai-agents.md)
- [More on Agent identity and access](https://opencontroller.lyzr.com/blog/cluster/agent-identity-and-access)
