Late confirmation MIcrosoft Authenticator

Question

I have a local Active Directory and Azure Entra ID. Between them there is a VPN connection and user synchronization.

I installed an NPS server on the local Active Directory, configured Connection Request i Network Policy,

The access point that I have in my office is configured as a client radius.

I have this problem when connecting to a wifi network ( I enter my username and password ) a notification from Microsoft Authenticator comes to my phone.

but when I click confirm, the request is rejected on my computer. as if I don't have enough time to confirm

*

I tested this on another Active Directory which does not have there is no connection between the cloud, everything works for me there. My settings on the network side are fine

Answer 1

Hi Arsen Aghamuradov,

Thank you for posting in the Microsoft Community Forums.

Check time synchronization:

Ensure that the time is fully synchronized between the local Active Directory and Azure AD.

Optimize the VPN connection:

Check the stability and speed of the VPN connection to ensure that it meets the needs of the authentication process.

Consider using a more stable VPN protocol or increasing the VPN bandwidth.

Check NPS server configuration:

Double-check the connection request policies and network policies of the NPS servers to ensure that they can properly handle authentication responses from Azure AD.

Ensure that the NPS server is properly configured as a RADIUS server and that RADIUS clients (such as wireless access points) are properly set up.

Check the client device configuration:

Ensure that the network settings on the client device allow communication with the NPS server and Azure AD.

Check if any security software or firewalls are blocking the authentication process.

Adjust Azure AD and Microsoft Authenticator settings:

Log in to the Azure AD management portal and check the conditional access policy and MFA settings.

Make sure that these settings do not prevent you from authenticating with Microsoft Authenticator.

If possible, try temporarily disabling some of the conditional access policies or MFA requirements to see if that resolves the issue.

Review logs and error messages:

Check log files and error messages on the NPS server, Azure AD, and client devices for more information about authentication failures.

These logs may contain specifics about why the connection request was denied.

Best regards

Neuvi