How can we avoid this authentication issue in production?

Summary:

We are currently deploying changes from the test environment to production. However, when attempting to access the production environment, we are encountering an issue where the system requires sign-in using a Microsoft-related user account.

When trying to establish the connection to the production environment, this authentication behavior is unexpected. In other client environments where there is no integration with Microsoft accounts or directory services, authentication is completed automatically using the provided production username and password.

We would appreciate your guidance on this behavior. Specifically, we would like to understand why this additional authentication step is required and what steps we should follow to avoid such issues in the future. Any recommendations or best practices for handling this type of configuration would be very helpful.