---
schema_version: "1"
id: 9d57d760b0dd8a8533d72ba4b5e1cdcc1629d14691fb41665db8e1dc8e456990
title: MDP Supported Verification Methods
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mcidp_dato_getstarted_security_mfa_methods.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mcidp_dato_getstarted_security_mfa_methods.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 21ada12a0569dc2c1057e2743ba26030058d432a1afb99347675a3275e210f79
description: When a user logs in to Marketing Cloud Intelligence Data Pipelines for the first time using MFA, the user must select at least one verification method.
products:
  - Marketing
  - Marketing Cloud Intelligence
release: "264"
---
# MDP Supported Verification Methods

When a user logs in to Marketing Cloud Intelligence Data Pipelines for the first time using MFA, the user must select at least one verification method.

Email and SMS text messages aren’t allowed as a second factor for MFA, because email credentials can be compromised and text messages can be intercepted.

Supported verification methods:

- **Salesforce Authenticator**—A Salesforce mobile app that provides secure and fast MFA via push notifications. It’s highly recommended that users set up a PIN or biometric requirement on their mobile device to ensure that unauthorized parties can’t access Salesforce Authenticator. For more information, see the Salesforce Authenticator web page.
- **One-time password generator**—A third-party authenticator app, such as Google Authenticator or Authy, that generates specific time-based, one-time passcodes that users enter when they log in.
- **Security key**—A small physical device, such as a Yubikey or Google Titan Key, that users connect to their computers when logging in.
- **Built-in authenticator**—A service, such as Windows Hello or Touch ID, that verifies a user’s identity with a fingerprint, iris, or facial recognition scan. This method is bound to a specific device, and users must register a built-in authenticator on each device that they log in from.
- **Recovery code**—Generates a list of 10 codes that you can copy or download. Each code can be used only once. This method doesn’t require additional devices. Recovery codes are only recommended as a back up option and not your primary verification method. If you run out of recovery codes, contact your Datorama Admin.