You can clear the SCP in AD:
https://github.com/MicrosoftDocs/azure-docs/issues/55187
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We enabled Hybrid AAD Join using AAD Connect, we've since discovered it is writing computer objects to AAD without an associated user, or the wrong user. The issue is all of our computers join the domain with SCCM OSD task sequences, but no user has logged in. AAD Connect picks up the computer account and does the Hybrid AAD join, without the user, and at times using a service account used for the AD domain join operation.
We have decided to address this problem we will turn off Hybrid AAD Join in AAD Connector, and use SCCM to establish the Hybrid AAD Join since we can delay the operation until the user has had a chance to log in.
The problem comes is that we go into the AAD Connect > Device Options and select Configure Hybrid Azure AD Join, then under Device Systems turn OFF the "Windows 10 or later domain-joined devices" checkbox. Note the downlevel checkbox is also turned off. The problem is the "Next" button is not enabled so there is no way to continue.
At this point the only other option would be to tear down the AAD Connect and rebuild it, but we really don't want to do that because of issues that likely would occur.
Unfortunately, fixing the user record association with the computer would be a lot of work. Without the user association makes using Intune problematic in many ways.
Well, I'm sure you have seen this:
https://albandrodsmemory.wordpress.com/2021/04/15/how-to-disable-hybrid-azure-ad-join/
But I cant vouch for it or if its supported
It appears that the need may be moot. We ran some tests today and discovered that a computer created using SCCM OSD would register without a user as expected. When a user logged in the record in AAD updated quickly. Intune created a second record, but at least the user to computer association was there.