Clarify SMS support after legacy policy deprecation

[carolinemutua]

Added clarification that SMS and other methods will remain functional under the Authentication methods policy despite the deprecation of legacy policies. The reason for this is customers are coming up with questions on this and we have an external blog written that is confusing customers even further. https://www.vissensa.com/blog/microsoft-mfa-microsoft-to-remove-sms-multi-factor-authentication/

[prmerger-automator]

@carolinemutua : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit f040bbd:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/identity/authentication/concept-authentication-methods-manage.md	✅Succeeded

For more details, please refer to the build report.

[v-dirichards]

@Justinha

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[Copilot]

Pull Request Overview

This PR adds clarification to documentation about the deprecation of legacy authentication policies, specifically addressing customer confusion about whether SMS and other authentication methods will remain functional after the September 30, 2025 deprecation date.

• Clarifies that SMS and other authentication methods will continue to work under the Authentication methods policy
• Addresses customer confusion stemming from external blog posts about the deprecation

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] This sentence is very long and contains multiple important pieces of information. Consider breaking it into separate sentences or using a bulleted list to improve readability and ensure key points aren't missed.

Suggested change

	>In March 2023, we announced the deprecation of managing authentication methods in the legacy multifactor authentication and self-service password reset (SSPR) policies. Beginning September 30, 2025, authentication methods can't be managed in these legacy MFA and SSPR policies. We recommend customers use the manual migration control to migrate to the Authentication methods policy by the deprecation date. Note: This change does not mean that any authentication methods, such as SMS, are being deprecated. SMS and other supported methods will continue to work when managed through the Authentication methods policy.
	>- In March 2023, we announced the deprecation of managing authentication methods in the legacy multifactor authentication and self-service password reset (SSPR) policies.
	>- Beginning September 30, 2025, authentication methods can't be managed in these legacy MFA and SSPR policies.
	>- We recommend customers use the manual migration control to migrate to the Authentication methods policy by the deprecation date.
	>- **Note:** This change does not mean that any authentication methods, such as SMS, are being deprecated. SMS and other supported methods will continue to work when managed through the Authentication methods policy.