Updated 04/18/25: Based on customer feedback around challenges with setting up the connector with build 6.2501.2000.5, we have released an updated build with improved functionality and updated our tr...
Updated Apr 18, 2025
Version 5.0
Blog Post
I'm having the same issue as well, this is the only place I've found where it's being reported. Have a ticket open, struggling to get it to someone who can accept there's an issue with the connector though.
Jonny-EE It's good to know our experience isn't isolated (although I wish the issue didn't exist in the first place!)
I asked if my own support ticket could be escalated to the product team but haven't had much success.
Intune_Support_Team are we able to get any input on if this is a logged issue with the new connector?
This is working for us now and ended up not being a connector issue. The user that the device was being provisioned for wasn't in a group that automatically enrolled into Intune (another team had messed up the prerequisites), so the device was being told by the Autopilot profile to do a domain join but could never apply the domain join policy because it wasn't ever getting to a point where it would receive that policy. The symptoms are the client stuck on "Please wait while we setup your device" and nothing happening.
In order to diagnose this I ended up targeting a Entra Join Autopilot profile to the device and when it completed the build and came out the other side with none of the applications installed and no attention being paid to things like Windows Hello policy I realised there was a bigger problem.
This is unlikely to help you if the only change you're making is shifting between the old and new connectors.