Forum Discussion
User name and password not recognized error after Intune/Autopilot Device Provisioning Process
Hi All, I am currently in the middle of rolling out an Intune deployment strategy using Azure AD Joined rather than Hybrid Azure AD Joined. Everything is working as intended with the exception of...
Could PingID be a factor here? If I remember correctly (it's been a while), it requires the installation of an additional credential provider for integration with Windows sign-in.
Hey Niels, that could definitely be a factor and that's been the route that I've been going down to figure out what's going on. What I found during my testing yesterday was that if I set my UPN and Primary Email for the user in AD to match exactly, I'm able to log into my desktop without issue after the provisioning process. Because of this, it makes me wonder if the issue is with the credential validator in Ping Federate and what it's trying to match on.