Forum Discussion
DerrickFl
Aug 01, 2017Copper Contributor
Azure Active Directory Domain Services On -premises workstation Join
Hello, Just a quick one, I know this might not be something new but was wondering if anyone can help. Scenario: Company A is a start up company who wants a cloud only infrastructure with Offi...
- Aug 02, 2017
Hello Gian,
Microsoft is trying to help customers simplify their cloud networks by building more services in the cloud. Before AAD DS, many customers used to build AD DS VMs on Azure in order to provide LDAP/Kerberos, etc., authentication for specific requirements. So, MS has simplified this by implementing AAD DS, meaning you get two IP DNS sources that are, in effect, AD DS VMs unmanaged by you. This is desgined devices that are on your Azure virtual network. This being said, for on-premises devices to authenticate to AAD DS, you must have a point-to-point VPN tunnel and point the local devices to your AAD DS DNS ips. But you should have a reliable network connection. As for AAD Connect (formerly DirSync), thats required for local AD DS synchronization to your AAD. Given that you prefer not having any local server resources, this would not apply in your case. Hope this helps.
Sid Merrett
Aug 03, 2017Copper Contributor
Oh and @Gian - I apologise if I have rather hijacked this thread - I think you and I have similar if not identical ambitions for Azure AD and I hope my observations are relevant to your original post.
Sid
Sid
DerrickFl
Aug 15, 2017Copper Contributor
Hi Sid,
No problem. Glad you have good observations too and yes I think we have identical ambitions for Azure Active Directory. Thank you for adding this up.
Cheers!