We are retiring the login.microsoftonline.com endpoint for Azure AD B2C tenants

Question

Our Azure AD B2C page contains the warning: We are retiring the login.microsoftonline.com endpoint for Azure AD B2C tenants. To avoid service disruptions, please move to the b2clogin.com endpoint. We previously migrated our URLs. Are we receiving this as a general warning, or is there a problem with our configuration?

Answer 1

No, if you have migrated yours, you have no issue. It's a general reminder.

This message is a general advisory from Microsoft reminding Azure AD B2C tenants to migrate from the login.microsoftonline.com endpoint to the b2clogin.com endpoint.

See the general advisory here: https://learn.microsoft.com/en-us/azure/active-directory-b2c/b2clogin?source=recommendations

You can mark it 'Accept Answer' and 'Upvote' if this helped you

Regards,

Abiola

Answer 2

Hi Andrew Barber,

Thank you for posting in the Q&A Forums.

Why do I need to migrate?

Better Security: b2clogin.com provides a more direct path to authentication, reducing potential security risks.

Better performance and reliability: The new endpoint is designed to better handle authentication traffic, improving performance and reliability.

Functionality improvements: Some future functionality updates may only be available to tenants using b2clogin.com.

How do I handle this warning?

Ensure all custom domains and policies are updated: Review all of your user flows (also known as policies) and custom domain settings to ensure they are updated to use b2clogin.com. This includes updating the redirect URIs and authorization/token endpoints in your application configuration.

TEST: Thoroughly test all of your authentication processes to ensure they are working properly on the new endpoints before fully migrating. This includes registration, login, password reset and any multi-factor authentication processes.

Update documentation and communications: If your application or service relies on external users or partners, make sure they are also aware of the change and are ready to update accordingly.

Progressive Migration: If possible, consider migrating users to a new endpoint gradually to monitor and resolve any potential issues.

Monitoring and feedback: Continuously monitor your authentication process after migration and provide Microsoft with any feedback or issues encountered.

Post-migration benefits

Enhanced security: Protect your users and data by reducing the potential attack surface.

Better user experience: Reduce authentication delays and improve the overall user experience.

Long-term compatibility: Ensures that your services will be able to take advantage of future features and improvements in Azure AD B2C.

Best regards

NeuviJ

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 3

Hi Andrew Barber,

Thank you for posting in the Q&A Forums.

Why do I need to migrate?

Better Security: b2clogin.com provides a more direct path to authentication, reducing potential security risks.

Better performance and reliability: The new endpoint is designed to better handle authentication traffic, improving performance and reliability.

Functionality improvements: Some future functionality updates may only be available to tenants using b2clogin.com.

How do I handle this warning?

Ensure all custom domains and policies are updated: Review all of your user flows (also known as policies) and custom domain settings to ensure they are updated to use b2clogin.com. This includes updating the redirect URIs and authorization/token endpoints in your application configuration.

TEST: Thoroughly test all of your authentication processes to ensure they are working properly on the new endpoints before fully migrating. This includes registration, login, password reset and any multi-factor authentication processes.

Update documentation and communications: If your application or service relies on external users or partners, make sure they are also aware of the change and are ready to update accordingly.

Progressive Migration: If possible, consider migrating users to a new endpoint gradually to monitor and resolve any potential issues.

Monitoring and feedback: Continuously monitor your authentication process after migration and provide Microsoft with any feedback or issues encountered.

Post-migration benefits

Enhanced security: Protect your users and data by reducing the potential attack surface.

Better user experience: Reduce authentication delays and improve the overall user experience.

Long-term compatibility: Ensures that your services will be able to take advantage of future features and improvements in Azure AD B2C.

Best regards

NeuviJ

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.