Multi-Factor Authentication (MFA)
Multi-Factor Authentication adds another layer of security to the Equinix portals. MFA increases security with an additional verification step that requires a one-time passcode (OTP) sent to or generated by a registered trusted device.
Note: Equinix strongly recommends that you enable MFA for your organization.
Important: Disabling MFA for your entire organization does not disable MFA for email-based user accounts. IAM users can enable MFA individually or deactivate MFA individually for their user account.
Note: Enabling MFA on the Customer Portal also enables MFA on other Equinix portals.
Important: When you enable MFA, all users within your organization must register a secondary authentication method using an alternate mechanism (such as a cell phone or email address). This is used to receive the OTP for all subsequent sign-ins to the portal.
-
Sign into the Customer Portal.
-
Click Administration, and select Account & Security Management.
-
Select Multi-Factor Authentication.
A message is displayed:
-
Read the information carefully, then click Enable.
An email notification is sent to the master administrator.
Once MFA is enabled, users are asked to register for MFA during their next login.
Note: Applicable to organizations with MFA enabled at the organization level. For self-enabled MFA, see Enable Multi-Factor Authentication.
Important: You are required to register at least two authentication methods. The method you select first is used as the primary method.
While signed into the portal:
-
On the Multi Factor Authentication Registration, click Continue.
-
Choose a method and click Next.
Follow the instructions to authenticate.
-
Repeat these steps to configure additional methods.
Note: You must completely register one authentication method before you start to register another method. You can click Cancel at any point in the process to clear all registration methods that were previously configured.
Authentication Methods
Important: If you have migrated to the IAM platform, or if you are using Federated SSO, the only authentication methods available are SMS/Text and Mobile App.
Note: Applicable to organizations with MFA enabled on organization level. For self-enabled MFA, see Enable Multi-Factor Authentication.
To configure this authentication method:
-
Select SMS/Texting and click Next.
-
Select your home country, enter your mobile number, and click Next.
A registration code is sent to your device.
-
Enter the one-time passcode received on your mobile device, then click Next.
-
Click Register Another to configure another method, or click Finish Registration.
Note: Applicable to organizations with MFA enabled on organization level.
To configure this authentication method:
Note: Applicable to organizations with MFA enabled on organization level.
To configure this authentication method:
Note: Applicable to organizations with MFA enabled at the organization level. For self-enabled MFA, see Enable Multi-Factor Authentication.
To configure this authentication method:
Note: Applicable to organizations with MFA enabled on organization level.
When you sign into the portal, you are asked for your one-time passcode:
-
Enter the code you receive from your primary authentication method (text, email, etc.).
or
To use an alternate registered device:
-
Click Change Device.
All the registered devices are displayed.
-
Select the alternate authentication method.
-
Enter the code received.
-
-
Click Sign On.
Note: Applicable to organizations with MFA enabled on organization level. For information on managing devices for self-enabled MFA, see Manage Multi-Factor Authentication.
To make changes to the devices you use to authenticate your sign in:
-
Sign into the Customer Portal.
You are asked for your one-time passcode:
-
Click Settings.
All the registered devices are displayed.
-
Actions:
-
You can edit the details for the registered devices.
-
You can add another authentication method by clicking Add and following the instructions.
-
You can specify your primary method of authentication.
Note: Some of these actions require you to authenticate with your existing primary method first.
-