update TOTP export to be softer language (FusionAuth#2819)

ritza-co · Jan 12, 2024 · 36f9323 · 36f9323
1 parent 1be1241
commit 36f9323
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/astro/src/content/docs/lifecycle/migrate-users/bulk/auth0.mdx b/astro/src/content/docs/lifecycle/migrate-users/bulk/auth0.mdx
@@ -322,7 +322,7 @@ The former will [trigger an MAU increment](/docs/get-started/core-concepts/users
 
 While you can't generate a fixed set of recovery codes, once MFA has been enabled for a user, you can [retrieve the recovery codes](/docs/apis/two-factor#retrieve-recovery-codes).
 
-If your user uses TOTP for MFA, where they provide a one time code provided by an application like Google Authenticator, you'll need to re-enroll them. As of Oct 2022, [Auth0 doesn't support export of TOTP secrets](https://community.auth0.com/t/can-mfa-secrets-be-exported/91656).
+If your user uses TOTP for MFA, where they provide a one time code provided by an application like Google Authenticator, you'll probably need to re-enroll them. As of Oct 2022, [Auth0 "probably" doesn't support export of TOTP secrets](https://community.auth0.com/t/can-mfa-secrets-be-exported/91656). However, we suggest confirming this by opening a support ticket with Auth0.
 
 If your users use a different method unsupported by FusionAuth, then you should map the Auth0 method to a FusionAuth method.