Hello @Michael Smith
For standard Microsoft Entra workforce SSPR, there isn’t a customer-configurable monthly SMS quota or a “cloud provider messaging quota” that the tenant administrator can increase. Microsoft operates the telephony service and applies risk-based throttling to SMS and voice authentication requests to prevent fraud.
Here are the recommended actions:
- Stop repeated SMS requests and retry later. For user-level SSPR throttling, wait 24 hours after the last blocked attempt in certain scenarios.
- Have affected users select another previously registered method, such as Microsoft Authenticator, software OATH, hardware OATH, or email OTP. I recommend registering multiple methods so users aren’t dependent on SMS.
- For users who remain blocked, a Password Administrator can reset the password through Microsoft Entra admin center > Entra ID > Users > Reset password. Hybrid users require password writeback, or you must perform the reset in on-premises Active Directory.
- If every user in the tenant or a particular country is affected, open a Microsoft support request. Some region codes require Microsoft to enable telephony verification, and only Microsoft Support can investigate service-side throttling or fraud protection.
If this SSPR implementation uses a custom application or third-party SMS gateway rather than native Microsoft Entra SSPR, its quota must be handled with that provider. To distinguish those cases, we need the exact portal error and tenant type - workforce, External ID, or Azure AD B2C.
References:
Microsoft Entra telephony protections and throttling
How SSPR works and supported methods
Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.