Azure AD B2C documentation missing SMS Limit information

[landonpierce]

Azure AD B2C includes a feature to enable sign in and/or MFA with SMS. There are certain limits that exist for this feature such as the number of text messages sent per period of time, and you will get an error message upon hitting one of these limits. For example, if a user tries to send too many SMS codes in a short period, they will get a (configurable) error message that says: You hit the limit on the number of text messages. Try again shortly..

These limits do not seem to be documented anywhere. I would expect that all applicable limits for this feature would be documented on this page (or a similar location): https://learn.microsoft.com/en-us/azure/active-directory-b2c/service-limits?pivots=b2c-custom-policy

title: Azure Active Directory B2C service limits and restrictions
description: Reference for service limits and restrictions for Azure Active Directory B2C service.
services: active-directory-b2c
author: kengaderdus
ms.author: kengaderdus
manager: CelesteDG
ms.service: active-directory
ms.workload: identity
ms.topic: reference
ms.date: 12/01/2022
ms.subservice: B2C
zone_pivot_groups: b2c-policy-type

[YashikaTyagii]

@landonpierce
Thanks for your feedback! We will investigate and update as appropriate.

[YashikaTyagii]

@landonpierce
Thank you for your feedback!

Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an Azure support request. Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.

Teams Q&A forum for technical questions about the configuration and administration of Microsoft Teams on Windows.
Microsoft Teams Community forum
Thank you for your time and patience throughout this issue.

[YashikaTyagii]

@kengaderdus
Kindly take a look at this issue?

[kengaderdus]

@landonpierce

Thank you for you feedback and patience. We confirm that this issue is due to a throttling done on our side to protect the system against fraudulent activity. #please-close.