> ## Documentation Index
> Fetch the complete documentation index at: https://auth0.generaltranslation.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Auth0's Unified Phone Experience for Multi-Factor Authentication

> Migrate your phone provider configuration to the Unified Phone Experience.

<Card title="Before you start">
  To migrate to the Unified Phone Experience, you must:

  * Have Multi-Factor Authentication (MFA) SMS, Voice, or SMS+Voice notifications enabled and configured in your tenant, or
  * Have Passwordless SMS enabled and configured in your tenant

  If you have not configured either MFA or Passwordless, read [Configure Auth0's Unified Phone Experience](/docs/ja-JP/ja-jp/customize/phone-messages/unified-phone/configure-unified-phone) to start from the beginning.

  If you have both MFA and Passwordless integrations with different providers, you must use a [Custom Phone Provider](/docs/ja-JP/ja-jp/customize/phone-messages/configure-phone-messaging-providers/configure-a-custom-phone-provider).

  If you utilize Phone as ID, you are automatically using Auth0's Unified Phone Experience and no additional action is needed.
</Card>

The Unified Phone Experience centralizes all your phone provider configurations in one location in your tenant. You won’t need to configure a phone provider multiple times for various phone authentication factors. To learn more about phone factors for <Tooltip data-tooltip-id="react-containers-DefinitionTooltip-0" href="/docs/ja-JP/ja-jp/glossary?term=multifactor-authentication" tip="多要素認証（MFA）: ユーザー名とパスワードに加えて、SMS経由のコードなどの要素を使用するユーザー認証プロセス。" cta="用語集の表示">MFA</Tooltip>, read [SMS and voice notifications for MFA](/docs/ja-JP/ja-jp/secure/multi-factor-authentication/multi-factor-authentication-factors/configure-sms-voice-notifications-mfa).

If you already have a phone provider configured for Multi-Factor Authentication (MFA), you can migrate your configuration to the Unified Phone Experience and apply your configuration at the tenant-level.

<Callout icon="file-lines" color="#0EA5E9" iconType="regular">
  Auth0 does not provide feedback to the end user on whether a phone message has been sent successfully with the tenant-level provider. To troubleshoot issues, review the [tenant logs](/docs/ja-JP/ja-jp/deploy-monitor/logs).
</Callout>

<div id="update-your-phone-provider">
  ## Update your phone provider
</div>

To use the Unified Phone Experience, you need to:

* Verify current settings
* Configure your provider:

  * Configure Twilio
  * Configure a custom phone provider
* Update your phone factors and delivery methods
* Update <Tooltip data-tooltip-id="react-containers-DefinitionTooltip-0" href="/docs/ja-JP/ja-jp/glossary?term=management-api" tip="Management API: 顧客が管理タスクを実行できるようにするための製品。" cta="用語集の表示">Management API</Tooltip> endpoints
* Update Auth0 Actions triggers

<div id="verify-current-settings">
  ### Verify current settings
</div>

1. To verify your current MFA settings, navigate to [**Auth0 Dashboard > Security > Multi-factor Auth** ](https://manage.auth0.com/#/security/mfa).
2. Select **Phone Message** .
3. If you are able to use the Unified Phone Experience, a banner advises you to configure a tenant-level provider:

   <Frame>
     <img src="https://mintcdn.com/generaltranslationinc/P5C2FvJW5xWCh6NI/docs/images/ja-jp/cdy7uua7fh8z/1mZryDWIpdkpGmhxn4Gr8K/4bdad7fbcd81dd0bf4855d94b7205e8b/2025-02-11_23-20-07.png?fit=max&auto=format&n=P5C2FvJW5xWCh6NI&q=85&s=dae3adb8ef844c55321cc5e11d68d723" alt="" width="902" height="782" data-path="docs/images/ja-jp/cdy7uua7fh8z/1mZryDWIpdkpGmhxn4Gr8K/4bdad7fbcd81dd0bf4855d94b7205e8b/2025-02-11_23-20-07.png" />
   </Frame>

<Callout icon="file-lines" color="#0EA5E9" iconType="regular">
  If you must use the legacy experience to configure your phone provider, and the toggle to use a tenant-level provider is missing, contact [Auth0 Support](https://auth0.com/docs/troubleshoot/customer-support).
</Callout>

<div id="configure-twilio-as-a-tenant-level-provider">
  ### Configure Twilio as a tenant-level provider
</div>

If you are using Twilio as your phone provider for Multi-Factor Authentication, you must add the Twilio SID and AuthToken to the Unified Phone Experience. You can copy the Twilio SID from your existing configuration, but you will need to get the value of the AuthToken from Twilio.

1. Navigate to [**Branding > Phone Provider** ](https://manage.auth0.com/#/phone/templates/phone/provider).

2. Select and configure your provider:

   <Frame>
     <img src="https://mintcdn.com/generaltranslationinc/UCtxRPLKKGiAgiWv/docs/images/ja-jp/cdy7uua7fh8z/6TESTIdmhUL0LEitACadIK/fcdc34e18a6b66b47370f6d754c085b5/2025-02-21_12-49-53.png?fit=max&auto=format&n=UCtxRPLKKGiAgiWv&q=85&s=18b88431ddfd3947cff80c7a861c5ae6" alt="Branding > Phone Provider > Twilio" data-og-width="500" width="500" data-og-height="612" height="612" data-path="docs/images/ja-jp/cdy7uua7fh8z/6TESTIdmhUL0LEitACadIK/fcdc34e18a6b66b47370f6d754c085b5/2025-02-21_12-49-53.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/generaltranslationinc/UCtxRPLKKGiAgiWv/docs/images/ja-jp/cdy7uua7fh8z/6TESTIdmhUL0LEitACadIK/fcdc34e18a6b66b47370f6d754c085b5/2025-02-21_12-49-53.png?w=280&fit=max&auto=format&n=UCtxRPLKKGiAgiWv&q=85&s=c5bbe4a9438a41c6c723a64321836c02 280w, https://mintcdn.com/generaltranslationinc/UCtxRPLKKGiAgiWv/docs/images/ja-jp/cdy7uua7fh8z/6TESTIdmhUL0LEitACadIK/fcdc34e18a6b66b47370f6d754c085b5/2025-02-21_12-49-53.png?w=560&fit=max&auto=format&n=UCtxRPLKKGiAgiWv&q=85&s=34298d2a74b82feb5c823bf362a9ee3d 560w, https://mintcdn.com/generaltranslationinc/UCtxRPLKKGiAgiWv/docs/images/ja-jp/cdy7uua7fh8z/6TESTIdmhUL0LEitACadIK/fcdc34e18a6b66b47370f6d754c085b5/2025-02-21_12-49-53.png?w=840&fit=max&auto=format&n=UCtxRPLKKGiAgiWv&q=85&s=66c8540c3eae0c36142cc0c5bfbc7107 840w, https://mintcdn.com/generaltranslationinc/UCtxRPLKKGiAgiWv/docs/images/ja-jp/cdy7uua7fh8z/6TESTIdmhUL0LEitACadIK/fcdc34e18a6b66b47370f6d754c085b5/2025-02-21_12-49-53.png?w=1100&fit=max&auto=format&n=UCtxRPLKKGiAgiWv&q=85&s=c87a5a09809ed47c86aea6a8e3095f6b 1100w, https://mintcdn.com/generaltranslationinc/UCtxRPLKKGiAgiWv/docs/images/ja-jp/cdy7uua7fh8z/6TESTIdmhUL0LEitACadIK/fcdc34e18a6b66b47370f6d754c085b5/2025-02-21_12-49-53.png?w=1650&fit=max&auto=format&n=UCtxRPLKKGiAgiWv&q=85&s=727a0f9ea02ba933ad9f20bcb8204a81 1650w, https://mintcdn.com/generaltranslationinc/UCtxRPLKKGiAgiWv/docs/images/ja-jp/cdy7uua7fh8z/6TESTIdmhUL0LEitACadIK/fcdc34e18a6b66b47370f6d754c085b5/2025-02-21_12-49-53.png?w=2500&fit=max&auto=format&n=UCtxRPLKKGiAgiWv&q=85&s=e07899151720013123a6601502d3d24a 2500w" />
   </Frame>

   1. Choose Twilio as your phone provider.
   2. Choose your delivery methods.
   3. Enter Twilio settings.

      <Callout icon="file-lines" color="#0EA5E9" iconType="regular">
        Desired MFA factors must be a subset of the delivery methods you configure at the tenant-level.
      </Callout>

3. **Save** your changes.

4. Select **Send Test Message** to test the tenant-level provider before using it in a production environment.

5. Enable a tenant-level provider.

   1. For MFA, navigate to [**Security > Multi-factor Auth > Phone Message** .](https://manage.auth0.com/#/security/mfa)
   2. Select **Use Tenant-level Messaging Provider** .

      <Warning>
        If no toggle exists in your tenant, you are already using the Unified Phone experience.
      </Warning>

6. **Save** your changes.

<div id="configure-a-custom-provider-with-auth0-actions">
  ### Configure a custom provider with Auth0 Actions
</div>

The Unified Phone Experience uses the `custom-phone-provider` Actions Trigger for phone notifications rather than the `send-phone-message` Actions Trigger for custom phone notifications.

You cannot directly migrate your `send-phone-message` Actions trigger to the `custom-phone-provider` Actions trigger because:

* There is no 1:1 mapping between message and notification types.
* Migrating secrets and dependencies associated with the send-phone-message Actions trigger could cause security concerns or break the tenant experience.
* Actions can support more than one trigger and could be difficult to migrate. For example, Actions can support both the `send-phone-message` and `post-login` triggers.
* The `send-phone-message` and `custom-phone-provider` Actions triggers support different event types:

  * `send-phone-message` supports the SMS and Voice message types. To learn more, read [Action triggers: send-phone-message Event Object](/docs/ja-JP/ja-jp/customize/actions/explore-triggers/mfa-notifications-trigger/send-phone-message-event-object).
  * `custom-phone-provider` supports the `otp_verify`, `otp_enroll`, `blocked_account`, `change_password`, and `password_breach` notification types. To learn more, read [Actions triggers: custom-phone-provider Event Object](/docs/ja-JP/ja-jp/customize/phone-messages/configure-phone-messaging-providers/configure-a-custom-phone-provider/actions-triggers-custom-phone-provider-event-object).
* You can only set one Action per custom phone provider. If you have already set an Action for a custom phone provider, you **must** disable it before associating it with a new Action.

As a result, you need to translate your existing `send-phone-message` into a new `custom-phone-provider` using the new contextual variables:

<Accordion title="Core payload">
  <table class="table">
    <thead>
      <tr>
        <th><b>`send-phone-message` context object</b></th>
        <th><b>`custom-phone-provider` context object</b></th>
        <th><b>Status</b></th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>`text`</td>
        <td>`notification.as_text` and `notification.as_voice`</td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>`message_type`</td>
        <td>`notification.message_type` <ul><li>Note the difference in values: `second-factor-authentication` vs `otp_enroll`, `verify` vs `otp_verify`)</li></ul></td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>`action`</td>
        <td>`notification.delivery_method`</td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>`language`</td>
        <td>`notification.locale`</td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>`code`</td>
        <td>`notification.code`</td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>`recipient`</td>
        <td>`notification.recipient`</td>
        <td>Updated</td>
      </tr>
    </tbody>
  </table>
</Accordion>

<Accordion title="Request data">
  <table class="table">
    <thead>
      <tr>
        <th><b> `send-phone-message` context object </b></th>
        <th><b>Tenant-level provider context object</b></th>
        <th><b> Status </b></th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>`ip`</td>
        <td>`ip`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user_agent`</td>
        <td>`user_agent`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`language`</td>
        <td>`language`</td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>`method`</td>
        <td>`method` optional</td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>`hostname`</td>
        <td>`hostname` optional</td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>`geoip`</td>
        <td>`geoip`</td>
        <td>Updated</td>
      </tr>
    </tbody>
  </table>
</Accordion>

<Accordion title="Tenant data">
  <table class="table">
    <thead>
      <tr>
        <th><b> `send-phone-message` context object </b></th>
        <th><b>Tenant-level provider context object</b></th>
        <th><b> Status </b></th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>`tenant.id`</td>
        <td>`tenant`</td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>N/A</td>
        <td>`tenant.home_url`</td>
        <td>New</td>
      </tr>

      <tr>
        <td>N/A</td>
        <td>`tenant.logo_url`</td>
        <td>New</td>
      </tr>

      <tr>
        <td>N/A</td>
        <td>`tenant.support_email`</td>
        <td>New</td>
      </tr>

      <tr>
        <td>N/A</td>
        <td>`tenant.support_url`</td>
        <td>New</td>
      </tr>
    </tbody>
  </table>
</Accordion>

<Accordion title="Application data">
  <table class="table">
    <thead>
      <tr>
        <th><b> `send-phone-message` context object </b></th>
        <th><b>Tenant-level provider context object</b></th>
        <th><b> Status </b></th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>`client.client_metadata`</td>
        <td>`client.metadata`</td>
        <td>Updated</td>
      </tr>

      <tr>
        <td>`client.client_id`</td>
        <td>`client.client_id`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`client.name`</td>
        <td>`client.name`</td>
        <td>Unchanged</td>
      </tr>
    </tbody>
  </table>
</Accordion>

<Accordion title="User data">
  <table class="table">
    <thead>
      <tr>
        <th><b> `send-phone-message` context object </b></th>
        <th><b>Tenant-level provider context object</b></th>
        <th><b> Status </b></th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>`user.user_id`</td>
        <td>`user.user_id`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.name`</td>
        <td>`user.name`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.email`</td>
        <td>`user.email`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.app_metadata`</td>
        <td>`user.app_metadata`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.user_metadata`</td>
        <td>`user.user_metadata`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.email_verified`</td>
        <td>`user.email_verified`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.phone_number`</td>
        <td>`user.phone_number`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.phone_verified`</td>
        <td>`user.phone_verified`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.picture`</td>
        <td>`user.picture`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.created_at`</td>
        <td>`user.created_at`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.updated_at`</td>
        <td>`user.updated_at`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.multifactor`</td>
        <td>`user.multifactor`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.identities`</td>
        <td>N/A</td>
        <td>Removed</td>
      </tr>

      <tr>
        <td>`user.family_name`</td>
        <td>`user.family_name`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.given_name`</td>
        <td>`user.given_name`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.nickname`</td>
        <td>`user.nickname`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>`user.username`</td>
        <td>`user.username`</td>
        <td>Unchanged</td>
      </tr>

      <tr>
        <td>N/A</td>
        <td>`user.login_count`</td>
        <td>New</td>
      </tr>
    </tbody>
  </table>
</Accordion>

For a complete list of the contextual variables, read [Customize Phone Templates](/docs/ja-JP/ja-jp/customize/phone-messages/customize-phone-templates).

Review the custom phone provider example:

```javascript lines theme={null}
const { fetch } = require('undici');
/**
* Handler to be executed while sending a phone notification
* @param {Event} event - Details about the user and the context in which they are logging in.
* @param {CustomPhoneProviderAPI} api - Methods and utilities to help change the behavior of sending a phone notification.
*/
exports.onExecuteCustomPhoneProvider = async (event, api) => {

  if (event.notification.message_type.startsWith('otp')) {
    const body = {
      from: event.notification.from,
      action: event.notification.message_type === 'otp_verify' ? 'second-factor-authenticator' : 'enrollment',
      language: event.notification.locale,
      recipient: event.notification.recipient,
      message_type: event.notification.delivery_method,
      text: event.notification.as_text,
      code: event.notification.code,
    };

    const response = await fetch(event.secrets['MY_ENDPOINT'], {
      method: 'POST',
      headers: {
        authorization: `Bearer ${event.secrets['MY_SECRET']}`,
      },
      body: JSON.stringify(body),
    });

    console.log(response.status); // 200
    console.log(await response.text()); // request's response body!
  }

  return;
};
```

<div id="configure-mfa-custom-phone-provider">
  #### Configure MFA custom-phone-provider
</div>

To continue and configure your MFA `custom-phone-provider` trigger:

1. Navigate to [**Branding > Phone Provider** ](https://manage.auth0.com/#/phone/templates/phone/provider).
2. Select your provider:

   1. Choose **Custom** .
   2. Under **Provider Configuration** , add your translated `send-phone-message` Action code in the embedded code editor.
3. **Save** your changes.
4. Select **Send Test Message** to test the tenant-level provider before using it in a production environment.
5. Navigate back to [**Security > Multi-factor Auth > Phone Message** ](https://manage.auth0.com/#/security/mfa) to enable the **Use Tenant-level Messaging Provider** .
6. **Save** your changes.

<div id="update-mfa-phone-factors-and-delivery-methods">
  ### Update MFA phone factors and delivery methods
</div>

<Warning>
  If you have not enabled a tenant-level provider in the Auth0 Dashboard, you won’t be able to configure phone SMS and voice phone factors for MFA.

  <Frame>
    <img src="https://mintcdn.com/generaltranslationinc/UCtxRPLKKGiAgiWv/docs/images/ja-jp/cdy7uua7fh8z/6HE10zh6tL6ByihAh4Cj6K/c0faf43eb8e4d606ef1ac20ec538bcac/2025-02-12_09-14-41.png?fit=max&auto=format&n=UCtxRPLKKGiAgiWv&q=85&s=59938a9873615da9a7036b961957e10c" alt="Unified phone MFA no tenant provider configured warning" width="760" height="40" data-path="docs/images/ja-jp/cdy7uua7fh8z/6HE10zh6tL6ByihAh4Cj6K/c0faf43eb8e4d606ef1ac20ec538bcac/2025-02-12_09-14-41.png" />
  </Frame>
</Warning>

If you want to update the current notification MFA factor(s) to a different type during the migration to the Unified Phone Experience, some configuration changes may be necessary.

<table class="table">
  <thead>
    <tr>
      <th><b>Current MFA Phone factors</b></th>
      <th><b>Desired MFA factors</b></th>
      <th><b>Tenant-level delivery method</b></th>
      <th><b>User action</b></th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>SMS</td>
      <td>Voice</td>
      <td>SMS</td>
      <td>User must update tenant-level provider to allow for desired MFA phone factor</td>
    </tr>

    <tr>
      <td>SMS</td>
      <td>Voice</td>
      <td>SMS + Voice</td>
      <td>None</td>
    </tr>

    <tr>
      <td>SMS</td>
      <td>SMS + Voice</td>
      <td>SMS</td>
      <td>User must update tenant-level provider to allow for desired MFA phone factor</td>
    </tr>

    <tr>
      <td>SMS</td>
      <td>SMS + Voice</td>
      <td>SMS + Voice</td>
      <td>None</td>
    </tr>

    <tr>
      <td>Voice</td>
      <td>SMS</td>
      <td>SMS + Voice</td>
      <td>User must update tenant-level provider to allow for desired MFA phone factor</td>
    </tr>

    <tr>
      <td>Voice</td>
      <td>SMS</td>
      <td>SMS + Voice</td>
      <td>None</td>
    </tr>

    <tr>
      <td>Voice</td>
      <td>SMS + Voice</td>
      <td>Voice</td>
      <td>User must update tenant-level provider to allow for desired MFA phone factor</td>
    </tr>

    <tr>
      <td>Voice</td>
      <td>SMS + Voice</td>
      <td>SMS + Voice</td>
      <td>None</td>
    </tr>

    <tr>
      <td>SMS + Voice</td>
      <td>SMS</td>
      <td>SMS + Voice</td>
      <td>None</td>
    </tr>

    <tr>
      <td>SMS + Voice</td>
      <td>Voice</td>
      <td>SMS + Voice</td>
      <td>None</td>
    </tr>
  </tbody>
</table>

If you want to update the current tenant-level phone provider delivery method(s) to a different type during the migration to the Unified Phone Experience, some configuration changes may be necessary.

<table class="table">
  <thead>
    <tr>
      <th><b>MFA Phone factors</b></th>
      <th><b>Current tenant-level delivery method</b></th>
      <th><b>Desired tenant-level delivery method</b></th>
      <th><b>User action</b></th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>SMS</td>
      <td>SMS</td>
      <td>SMS + Voice</td>
      <td>None</td>
    </tr>

    <tr>
      <td>SMS</td>
      <td>SMS</td>
      <td>Voice</td>
      <td>User must update MFA phone factors to be a subset of the delivery methods enabled for the tenant-level provider</td>
    </tr>

    <tr>
      <td>SMS</td>
      <td>SMS + Voice</td>
      <td>Voice</td>
      <td>User must update MFA phone factors to be a subset of the delivery methods enabled for the tenant-level provider</td>
    </tr>

    <tr>
      <td>SMS</td>
      <td>SMS + Voice</td>
      <td>SMS</td>
      <td>None</td>
    </tr>

    <tr>
      <td>Voice</td>
      <td>Voice</td>
      <td>SMS</td>
      <td>User must update MFA phone factors to be a subset of the delivery methods enabled for the tenant-level provider</td>
    </tr>

    <tr>
      <td>Voice</td>
      <td>Voice</td>
      <td>SMS + Voice</td>
      <td>None</td>
    </tr>

    <tr>
      <td>Voice</td>
      <td>SMS + Voice</td>
      <td>SMS</td>
      <td>User must update MFA phone factors to be a subset of the delivery methods enabled for the tenant-level provider</td>
    </tr>

    <tr>
      <td>Voice</td>
      <td>SMS + Voice</td>
      <td>Voice</td>
      <td>None</td>
    </tr>

    <tr>
      <td>SMS + Voice</td>
      <td>SMS + Voice</td>
      <td>SMS</td>
      <td>None</td>
    </tr>

    <tr>
      <td>SMS + Voice</td>
      <td>SMS + Voice</td>
      <td>Voice</td>
      <td>None</td>
    </tr>
  </tbody>
</table>

<div id="update-guardian-endpoints-with-management-api">
  ### Update Guardian endpoints with Management API
</div>

The Unified Phone Experience uses specific endpoints for notifications. If you’ve been using [Auth0 Guardian](/docs/ja-JP/ja-jp/secure/multi-factor-authentication/auth0-guardian) for push notifications and one-time passwords, you must update your configuration to use the new Phone Provider Branding endpoints.

The following Guardian endpoints will no longer work with the Unified Phone Experience:

<table class="table">
  <thead>
    <tr>
      <th><b>Send-phone-message Guardian endpoint</b></th>
      <th><b>Scope</b></th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/get-phone-twilio-factor-provider">Get Twilio configuration</a></li><li><a href="https://auth0.com/docs/api/management/v2/guardian/get-sms-twilio-factor-provider">Get Twilio SMS configuration</a></li></ul></td>
      <td>`read:guardian_factors`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/get-guardian-phone-providers">Get phone provider configuration</a></li><li><a href="https://auth0.com/docs/api/management/v2/guardian/get-sms-providers">Get phone provider SMS configuration</a></li></ul></td>
      <td>`read:guardian_factors`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/put-twilio">Update Twilio configuration</a></li><li><a href="https://auth0.com/docs/api/management/v2/guardian/put-sms-twilio-factor-provider">Update Twilio SMS configuration</a></li></ul></td>
      <td>`update:guardian_factors`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/put-phone-providers">Update phone provider configuration</a></li><li><a href="https://auth0.com/docs/api/management/v2/guardian/put-sms-providers">Update SMS configuration</a></li></ul></td>
      <td>`update:guardian_factors`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/get-factor-phone-templates">Get enrollment and verification phone templates</a></li><li><a href="https://auth0.com/docs/api/management/v2/guardian/get-factor-sms-templates">Get SMS enrollment and verification templates</a></li></ul></td>
      <td>`read:guardian_factors`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/put-factor-phone-templates">Update enrollment and verification phone templates</a></li><li><a href="https://auth0.com/docs/api/management/v2/guardian/put-factor-sms-templates">Update SMS enrollment and verification templates</a></li></ul></td>
      <td>`update:guardian_factors`</td>
    </tr>
  </tbody>
</table>

Replace the Guardian endpoints with the new Phone Provider Branding endpoints and scopes:

<table class="table">
  <thead>
    <tr>
      <th><b>Phone Provider Branding endpoint</b></th>
      <th><b>Scope</b></th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/branding/get-branding-phone-providers">Get the phone providers set for a tenant</a></li><li><a href="https://auth0.com/docs/api/management/v2/branding/get-phone-provider">Get the phone provider</a></li></ul></td>
      <td>`read:phone_providers`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/branding/update-phone-provider">Update the phone provider</a></li></ul></td>
      <td>`update:phone_providers`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/branding/create-phone-provider">Configure the phone provider</a></li></ul></td>
      <td>`create:phone_providers`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/branding/get-phone-templates">Get list of phone notification templates</a></li><li><a href="https://auth0.com/docs/api/management/v2/branding/get-phone-template">Get a phone notification template</a></li></ul></td>
      <td>`read:phone_templates`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/branding/update-phone-template">Update a phone notification template</a></li></ul></td>
      <td>`update:phone_templates`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/branding/create-phone-template">Create a phone notification template</a></li></ul></td>
      <td>`create:phone_templates`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/branding/delete-phone-provider">Delete a phone template</a></li></ul></td>
      <td>`delete:phone_templates`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/branding/delete-phone-provider">Delete a phone provider</a></li></ul></td>
      <td>`delete:phone_providers`</td>
    </tr>
  </tbody>
</table>

The following Guardian endpoints work with the Unified Phone Experience and will not need to be updated:

<table class="table">
  <thead>
    <tr>
      <th><b>MFA phone factor endpoint</b></th>
      <th><b>Scope</b></th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/get-message-types">Get enabled phone factors</a></li></ul></td>
      <td>`read:guardian_factors`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/put-message-types">Update enabled phone factors</a></li></ul></td>
      <td>`update:guardian_factors`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/get-guardian-phone-providers">Get phone provider configuration</a></li></ul></td>
      <td>`read:guardian_factors`</td>
    </tr>

    <tr>
      <td><ul><li><a href="https://auth0.com/docs/api/management/v2/guardian/put-phone-providers">Update phone provider configuration</a></li></ul></td>
      <td>`update:guardian_factors`</td>
    </tr>
  </tbody>
</table>

<div id="disable-phone-provider">
  ## Disable phone provider
</div>

If you configure the Unified Phone Experience and then disable it, existing integrations with your phone provider, including MFA, could break.

<Frame>
  <img src="https://mintcdn.com/generaltranslationinc/JoMgZsgQxj2_Gov3/docs/images/ja-jp/cdy7uua7fh8z/3qqa2QWXRNKZV96AQq6O0G/28cdff44a9532f5c005a5e1acb763ab8/2025-02-24_14-58-47.png?fit=max&auto=format&n=JoMgZsgQxj2_Gov3&q=85&s=2dedc37dd28ccf6f436321fa7b0f0067" alt="" width="400" height="227" data-path="docs/images/ja-jp/cdy7uua7fh8z/3qqa2QWXRNKZV96AQq6O0G/28cdff44a9532f5c005a5e1acb763ab8/2025-02-24_14-58-47.png" />
</Frame>