Number matching is a security upgrade to traditional second factor notifications in Microsoft Authenticator. I'm unable to bring one customer on Azure Because of this.New Number matching Azure MFA feature impact Microsoft RDGW & NPS extensionĪre you using Microsoft Native Remote Desktop Gateway (RDGW) in combination with the NPS extension to secure your RDGW with MFA? Prepare for this change which will be enforced tenant-wide for all users starting February 27, 2023!
NPS team was unable to understand our environment hence they are struggling and I have not received any response from them till date. I explained everything to them and they said NPS is the component which RDG uses hence they MFA team said as NPS is not forwarding the attribute hence it is not them who can answer, they involved RDG team. I've created a support ticket on 11th of September. That is why I'm handling the authentication on NPS itself to authenticate.īut I'm not sure which condition would work in my scenario (Client Access IPV4 or something else)
This is what i wanted to achieve through connection request policy, I know if we forward the authentication to MFA it won't get the Attribute 66 which you mentioned.
I'm creating another connection request policy under the 2nd Priority which eventually checks the Client Access IPV4 Address and authenticates on the server, this can be done using Create Connection Request Policy -> Going to Condition tabs select the So in the 1st link, Microsoft RDS team is suggesting us to create a duplicate policy so that the connection which is coming from the MFA should be authenticated on the NPS server (Should not get through the loop of authentication)Īfter creating the duplicating the policy we have 2nd priority policy which forwards the connection to MFA server and 1st priority policy takes the connection from the MFA and authenticates on the NPS server Thanks for sharing the information in detail, So i have made the environment using the below suggested article.Īlso the same can be find in the Third party article
0 kommentar(er)
