# Using EntraID users with multifactor authentication (MFA) for unattended robots

> EntraID user accounts with MFA for unattended robots: supported authentication factors and limitations of password-only credentials.

Multifactor authentication (MFA) adds an extra layer of security by requiring users to verify their identity using two or more factors, such as:

* Something you know: a password
* Something you have: a mobile device or smart card
* Something you are: a fingerprint or face scan

MFA helps protect against unauthorized access, even if a password is compromised. However, it introduces additional complexity when setting up unattended automations.

Passwords count as a single authentication factor. Because MFA requires at least two factors, Robots cannot create user sessions using password credentials alone.

To enable MFA users to authenticate, set the **Credential type** of the robot account in Orchestrator to **Smart Card** and enter the PIN in the **Password** field. This applies to both Windows Hello for Business PINs and virtual smart card PINs.

:::important
Smart card authentication requires **Login to Console** to be set to **True**. It does not work with RDP sessions, which means it is **not compatible with High-Density Robot environments**. For more details, see [SmartCard Authentication](https://docs.uipath.com/orchestrator/standalone/latest/user-guide/smartcard-authentication).
:::

## Using Windows Hello for Business with a PIN

The Robot can authenticate users using a Windows Hello for Business (WHfB) PIN.

To enable Windows Hello for Business for your organization, refer to the [official documentation](https://learn.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/configure).

You can [configure the PIN](https://support.microsoft.com/en-us/windows/configure-windows-hello-dae28983-8242-bb2a-d3d1-87c9d265a5f0) in Windows Settings. Before setting up the PIN, you must authenticate using MFA.

:::important
WHfB PIN can only be configured in a console session. Remote sessions (RDP) are not supported for enrollment.
:::

## Using Entra Certificate-Based Authentication

### Step 1: Create virtual smart cards

Virtual smart cards are easier to deploy and manage across multiple machines.

You must create virtual smart cards on all virtual machines (VMs) where robots run. Do this for each Entra ID user that executes automations.

A virtual smart card functions as a physical one, but instead of using a physical container, it relies on the machine [Trusted Platform Module (TPM)](https://learn.microsoft.com/en-us/windows/security/identity-protection/virtual-smart-cards/virtual-smart-card-get-started) chip to securely store cryptographic keys.

### Step 2: Configure Entra certificate-based authentication

After creating the virtual smart cards, configure [Entra certificate-based authentication](https://learn.microsoft.com/en-us/entra/identity/authentication/concept-certificate-based-authentication) to allow Entra ID users to authenticate using certificates.

The certificates used for authentication must be configured as [multi-factor](https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-certificate-based-authentication#step-3-configure-an-authentication-binding-policy) to meet MFA requirements.
