COnnect to on premise domain

%3CLINGO-SUB%20id%3D%22lingo-sub-2611780%22%20slang%3D%22en-US%22%3ECOnnect%20to%20on%20premise%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2611780%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20just%20setup%20a%20trial%20Windows%20365%20Computer.%20What%20is%20best%20practice%20to%20have%20this%20system%20access%20the%20resources%20on%20our%20local%20on%20premise%20domain%20(ERP%20system%20etc)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20see%20this%20as%20a%20great%20option%20for%20remote%20contractors%20doing%20It%20work%2C%20but%20again%2C%20they%20would%20need%20access%20to%20our%20domain%20resources.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2613016%22%20slang%3D%22en-US%22%3ERe%3A%20COnnect%20to%20on%20premise%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2613016%22%20slang%3D%22en-US%22%3ESeems%20the%20Business%20option%20of%20Win365%20was%20used%2C%20in%20that%20scenario%20the%20Cloud%20PC's%20are%20Azure%20AD%20joined%20and%20deployed%20to%20a%20private%20virtual%20network%20and%20don't%20have%20networking%20line%20of%20sight%20to%20other%20resources.%20If%20you%20deploy%20the%20Enterprise%20version%20of%20Win365%20then%20all%20your%20Cloud%20PC's%20are%20deployed%20to%20an%20Azure%20VNET%20that%20you%20create%2C%20manage%2C%20own%20and%20requires%20networking%20line%20of%20sight%20to%20your%20AD%20domain%20controller.%20This%20VNET%20can%20be%20configured%20to%20other%20Azure%20VNET's%20via%20a%20VNET%20to%20VNET%20also%2C%20you%20have%20full%20control%20and%20most%20control%20using%20Enterprise%20method.%3C%2FLINGO-BODY%3E
Occasional Visitor

I have just setup a trial Windows 365 Computer. What is best practice to have this system access the resources on our local on premise domain (ERP system etc)

 

I can see this as a great option for remote contractors doing It work, but again, they would need access to our domain resources.

1 Reply
Seems the Business option of Win365 was used, in that scenario the Cloud PC's are Azure AD joined and deployed to a private virtual network and don't have networking line of sight to other resources. If you deploy the Enterprise version of Win365 then all your Cloud PC's are deployed to an Azure VNET that you create, manage, own and requires networking line of sight to your AD domain controller. This VNET can be configured to other Azure VNET's via a VNET to VNET also, you have full control and most control using Enterprise method.