2 points of disagreement: - "Don't use the MSIT image you get from PXE boot on corpnet": The customized Microsoft-internal image works fine, and saves you time

2 points of disagreement: - "Don't use the MSIT image you get from PXE boot on corpnet": The customized Microsoft-internal image works fine, and saves you time installing Office. You can't avoid "MSIT shovelware" by installing clean Windows; if you join corp.microsoft.com AD or @microsoft.com AAD, the same software will still be pushed to your PC eventually via System Center Config. Mgr. and Microsoft Intune. In any case, soon you won't be able to do network boot to install anyway, either plain Windows or the customized Microsoft-internal image. CSE&O (Microsoft's IT department) intends to shut down the Windows Deployment Services network boot servers as part of its overall thrust to make the corporate network unnecessary and move Microsoft entirely to the cloud. - "domain join to Microsoft's Azure Active Directory instance": If the machine is a desktop, I recommend you join to on-premise AD instead ([location].corp.microsoft.com). If you join your PC to AAD, you can connect to it via Remote Desktop only from another box that is also AAD-joined or on-premise-AD-joined. Which means if you want to work from home without a laptop by TSing/RDPing into your desktop, you won't be able to avoid joining your home computer to AAD - negating the current advantage of the CSE&O RD Gateway. In addition, the management policies are slightly different between @microsoft.com AAD joined machines and on-premise-AD-joined boxes. Usually this is to the detriment of dev work on the AAD-joined boxes.