Search for a command to run...
#AzureAD #AzureADConnect #AzureADcloudsync
No comments yet. Be the first to comment.
AWS Agent Plugins let AI coding agents deploy, architect, and operate on AWS. Here's what that means for the future of DevOps.
AWS Storage Gateway bridges your on-premises infrastructure with Amazon's cloud storage — letting you use familiar protocols like NFS, SMB, and iSCSI while your data lives safely in S3, EBS, or Glacie
This AZ-104 domain emphasizes secure identity management and efficient resource governance, which are essential for Azure administrators to ensure compliance and cost control. Overview of Azure Identi
Scaling your EC2 instances to match dynamic workloads can be challenging. Amazon EC2 Auto Scaling simplifies this with target tracking scaling policies, a powerful feature that automatically adjusts capacity to maintain optimal performance and cost e...
IntroductionAmazon Elastic Block Store (EBS) is a cornerstone of AWS storage solutions, offering persistent block-level storage for EC2 instances. While EBS volumes are typically attached to a single instance.# EBS Multi-Attach breaks this mold, allo...
CloudCubes by Jinesh
45 posts
Cloud Infrastructure Consultant
Find me here : jineshkumar.bio.link
https://jineshkumar.com
In this Tutorial Blog, We will integrate a Single Forest On-Premise Active Directory (AD) with our Azure Active Directory(AAD) using
Azure AD Connect > "Azure AD cloud sync"
Azure AD Connect Cloud Sync is a cloud service alternative to Azure AD Connect software. The organization deploys one or more lightweight agents in their on-premises environment to bridge AD and Azure AD. The configuration is done in the cloud.
My Set up
Create Azure AD and Create a Tanent
Tanent Type : Azure Active Directory
Configure the Organization Name and Domain Name. Review+Create
Download Azure AD cloud sync Agent and Move it to your Local On Premise Active Directory Server
Installing AADConnectProvisioningAgentSetup.exe on On Prem AD Server.
Connect/Authenticate Login to Azure AD using Global Admin Account created for Azure AD Directory.
Configure Service Account
Connect On Prem Active Directory Domain (Mine is JP.local)
Agent Install Configuration Confirm Page.
Active Directory Configuration to Local Domain (JP.LOCAL)
Azure Active Directory Global Administrator Login configuration.
Your agent Installation and Configuration is complete. Provision on Azure AD Portal.
Azure portal agent verification by > Azure AD> Azure AD Connect Cloud Sync > Review All Agents >It shows Active for my AD Machine.
Also, verify on On-Premise AD Server Services where "Azure AD Connect Agent" Services are running,
So far so good. Verified. Status: Active.
Configure Azure AD Connect cloud sync
Portal > Azure AD > Azure AD Connect > Manage Azure AD cloud sync > New Configuration.
It will automatically filled recently installed AD Connect Cloud Sync Agent Domain (Mine is JP.local)
Next will allow to edit this provisioning configuration which asks Configuration Scope for Domain or if you want to use any Filter for scope for sync. Also Validate , Notification settings and deploy.
Great ! Saved and My AD Provisioning for JP.local domain is showing "HEALTHY" STATUS
And Wooooalllaaaa!! It all synced in few Seconds to my Azure AD under all Users. Note : Directory Synced: YES for local AD Synced Users.
Managing Users from Microsoft 365 Admin Center
I could have also assigned an Administrator Role and have New User signed in into MS 365 Admin Center to manage AD Administration.
Hope you followed up with this hands-on tutorial. Thank you for the read. I appreciate your time. Let me know if you have any questions or queries during following along with the steps.
Follow for more Azure and AWS Content.
Regards,
Jineshkumar Patel
