
Previously in Dynamics NAV2016, user was linked with office365 account and there was multi-factor authentication enabled. So user can login to NAV using office365 credential and 2FA which is secured login. Now Microsoft has upgrade TLS for office365 but did not upgrade the security feature on Dynamics NAV2016. For which we cannot use office365 account and 2FA anymore for NAV login. It's blocking the application. So it is required to disable office365 integration with NAV. Now we need to use simple NAV user ID and password to login to NAV and there is no multi-factor authentication. Is it secured way to login to Dynamics NAV? Is Dynamics NAV not Microsoft product? Microsoft upgrade security for one platform but did not upgrade security for another platform which are linked with each other. How Microsoft can do like this? And one more thing is there is no limitation for entering wrong password. Anybody can try unlimited times to break any password which is not logical also. Are we paying to Microsoft for unsecured service? We are looking for a proper secured solution immediately. We cannot leave our Dynamics NAV unsecured.
Hello,
The reason is that Dynamics NAV 2016 went out of support as announced here:
docs.microsoft.com/.../dynamics-nav-2016
Note that Dynamics NAV 2017 will soon also reach end of support:
docs.microsoft.com/.../dynamics-nav-2017
Dynamics NAV 2018 will reach end of support in Jan 2023.
The keys your are looking for are:
LockoutPolicyFailedAuthenticationCount
koutPolicyFailedAuthenticationWindow
I personally requested this adjustment to be backported to CU62 for Dynamics NAV 2016:
The last CU that we released for Dynamics NAV 2016 is CU67:
If your installed release of Dynamics NAV 2016 does not support these two keys, it is very likely that you are running an unsupported release of Dynamics NAV and also an older cumulative update.
The only good suggestion at this point is to ask your partner to upgrade you to Dynamics 365 Business Central.
Thanks.