Feb 17 2022 08:43 PM - edited Mar 10 2022 03:31 PM
Resolution process for those who have this as well:
Microsoft unable to advise issue and had no idea on why it wasn't working.
After getting back to looking into this, errors looked like routing issue, this turned out to be correct.
If you have already setup a ONPC using Hybrid join type then you need only create a new subnet in the same vNet and routing will work correctly.
Using same subnet as Hybrid join type will also result in routing failure.
~~~~~~~~~~~~~~~
Hi All,
Looking for some ideas around my current issue.
Previously configured successfully Windows 365 Enterprise via setting up new domain for client + AADC. The cloud pcs worked as expected joining intune / domain etc and they could be used as intended.
Since the client doesn't want to manage the DC's, I'm configuring some new VM's using the new provisioning policy of Join Type 'Azure AD Join'.
When using a new provisioning policy configured to use Azure AD Join I am receiving the following error
Mar 23 2022 09:37 AM
@Grebfinismydndname : Thanks for taking the time to update this thread. This is odd, as we've seen multiple customers be successful creating both an Azure AD Join and a Hybrid Azure AD Join On-Premises Network Connection using the same subnet.
We'll continue monitoring this to see if your case is the "rule" as opposed to the "exception."