Skip to main content

Azure Insights: Installing AD Connect; Policy for Kubernetes; Automation with CLI; User node pools

by MSDW Reporter
Editorial Team,

Azure pros share their latest insights on installing AD Connect, leveraging Azure Policy for Kubernetes, automation with CLI and System versus User node pools.

Doing a manual install of AD Connect

Writing on 2 Azure, Cor den Boer explained how to do a manual install of Active Directory Connect, linking AD on-prem to Azure AD. Before getting started, users need an Office 365 admin account, AD Server with AD Enterprise admin permissions as well as the AD Connect tool. Launching the setup wizard, Boer installed AD Connect and then powered up the configuration wizard, agreed with the license terms and continued. The Customize option allows users to leverage their own SQL Server or a pre-created service account, while express settings support a local database with a service account.

For the purposes of setup, Boer granted global admin permissions to his user account. An Enterprise Administrator account comes into play for connecting with the local AD domain. He touched on topics like adding a DNS suffix and wrote:

Some valuable information is that in the background a scheduled task is created to sync all AD objects every 30 minutes. Passwords will be synced every few minutes, depending on the number of objects in your Active Directory. If you need to force a sync, you can do that by running some commands.

Azure Policy for Kubernetes

FREE Membership Required to View Full Content:

Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

About MSDW Reporter
More about MSDW Reporter