On-premises network connection

%3CLINGO-SUB%20id%3D%22lingo-sub-2609394%22%20slang%3D%22en-US%22%3EOn-premises%20network%20connection%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2609394%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20DC%20setup%20ina%20Azure%2C%20with%20AD%20connect%20installed%20and%20working%20(as%20far%20as%20i%20can%20tell)%20however%20the%20On-premises%20Network%20Connection%20is%20giving%20me%20warnings%2C%20as%20attached.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22jamesratcliffe_0-1628071185926.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F300409i7CE88640ED646B60%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22jamesratcliffe_0-1628071185926.png%22%20alt%3D%22jamesratcliffe_0-1628071185926.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20cannot%20see%20what%20I%20need%20to%20change.%20I%20have%20changed%20the%20DNS%20in%20the%20VNET%20to%20point%20to%20the%20DC.%3C%2FP%3E%3CP%3EThe%20users%20are%20assigned%20M365%20Business%20Premium%20licenses%2C%20could%20that%20be%20the%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2609612%22%20slang%3D%22en-US%22%3ERe%3A%20On-premises%20network%20connection%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2609612%22%20slang%3D%22en-US%22%3EYeah%20you've%20confused%20the%20two.%3CBR%20%2F%3EWindows%20365%20Business%20isn't%20managed%20through%20MEM%20provisioning%2C%20so%20you%20don't%20need%20the%20OPNC%20at%20all.%3CBR%20%2F%3EThe%20warning%20won't%20stop%20you%20creating%20a%20provisioning%20policy%20inside%20MEM%20now%2C%20but%20you%20will%20need%20to%20add%20Windows%20365%20Enterprise%20licenses%20to%20users%20as%20well%20as%20assigning%20them%20to%20a%20provisioning%20policy.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2609633%22%20slang%3D%22en-US%22%3ERe%3A%20On-premises%20network%20connection%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2609633%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F196561%22%20target%3D%22_blank%22%3E%40Steven%20DeQuincey%3C%2FA%3E%26nbsp%3BI%20havent%20assigned%20Windows%20365%20business%20PC's%20I%20have%20assigned%20Windows%20365%20Enterprise%20PC's.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20I%20need%20the%20OPNC%20for%20managing%20and%20provisioning%20PC's%20that%20are%20enterprise%20Pc's%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I have a DC setup ina Azure, with AD connect installed and working (as far as i can tell) however the On-premises Network Connection is giving me warnings, as attached.

jamesratcliffe_0-1628071185926.png

 

I cannot see what I need to change. I have changed the DNS in the VNET to point to the DC.

The users are assigned M365 Business Premium licenses, could that be the issue?

5 Replies
Yeah you've confused the two.
Windows 365 Business isn't managed through MEM provisioning, so you don't need the OPNC at all.
The warning won't stop you creating a provisioning policy inside MEM now, but you will need to add Windows 365 Enterprise licenses to users as well as assigning them to a provisioning policy.

@Steven DeQuincey I havent assigned Windows 365 business PC's I have assigned Windows 365 Enterprise PC's. 

 

I know I need the OPNC for managing and provisioning PC's that are enterprise Pc's

Sorry I mis read your original post, M365 BP, that's ok.
Is your provisioning failing? The warning on the OPNC happens because AD Sync hasn't ran while we tested the OPNC and created a computer object. Marked as a warning because it's normally just an AD Connect timing issue rather than a hard failure.

@Steven DeQuincey I I have mananged to get one PC provisioned, however there are 2 more that are just sitting at provisioning for nearly 2 hours now:

jamesratcliffe_0-1628076270049.png

I can see the object being created in the DC, but it just doesn't seem to be reliable.

Even after leaving it all last night, when doing checks this morning the OPNC test came back with the same warning.

 

Long running is normally a sign of a delayed AD Connect sync. It will either complete, or eventually time out. Then the error should help you troubleshoot, but you can also raise a ticked directly in MEM and we'll take a look at the logs for you.