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
We are experiencing a strange issue with the updated connector (version 6.2501.2000.5 onwards)
It successfully installs, enrols and correctly creates and permissions the MSA account and assigns it to the service. There are no errors in the logs and it's synchronising successfully to our Intune tenant. Everything looks good.
Yet the updated connector will not pick up any ODJ requests and will continually report 'ODJRequestHandlingPipelineDownload_NoWork: No requests pending to be downloaded.' in the logs until the Autopilot provisioning errors out as it didn't receive an ODJ blob response (error 0x80070002)
If the old connector (6.2304.38.4) is re-installed on a server it works perfectly and picks up the ODJ requests when you'd expect and completes the domain join. Nothing about our Autopilot or Domain Join policies has changed - the new connector just seems to break the process.
Currently have an open ticket with Microsoft support but not had any breakthrough so far.
Still experiencing this issue with 6.2504.2001.8 sadly, no change in behaviour.
Removed the old connector and left us running only the new connector active in our environment for 48+ hours but all attempts to provision a device fail at the ODJ/domain join step.
Re-installing 6.2304.38.4 on a server instantly resolves the issue and provisioning completes successfully.
lm101did you ever get this sorted with Microsoft? we experienced the same today.
no ODJ and keeps giving this event "ODJRequestHandlingPipelineDownload_NoWork: No requests pending to be downloaded"
when reverting back to the old connector it works directly again.BrtVnglStill experiencing this at the moment, haven't made much progress on my support ticket (they keep focusing on Autopilot deployment profiles and other settings, even though these haven't changed and all work perfectly with the old connector)
Let me know if you have any breakthroughs. Seems like a behind-the-scenes issue preventing the new connector from picking up any ODJ requests.lm101 we fixed it today, as we had to install the new Intune AD connector on our server in the same domain as where the clients will be domain joined. our old connector was installed in the root domain, but clients are located in a different domain.
I don't know when the info was added but checking back a week ago I noticed this info was added.
after setting up the connector in the same domain as the clients everything started working fineUsing the Intune Connector with multiple domains
Customers who are already using the connector with more than one domain will be able to use the new connector by setting up a separate server per domain and installing a separate connector build for each domain.
Configuring the connector
- The Intune Connector for Active Directory needs to be installed on each domain that you plan to use for domain join. If you need to have a second account redundancy, you will need to install the connector on a different server (in the same domain).
we have now successfully added a system to the domain again using Autopilot.We have disabled the old connector now and will remove it at the end of June.
