Azure AD Connect: 5-Day Implementation

###Overview

Microsoft Azure AD Connect is a bridge solution between an on-premises Active Directory and cloud-based Azure Active Directory. By integrating on-premises Active Directory to Azure Active Directory, users can use a single identity to access both on-premises and cloud-based resources

###Why Azure AD Connect?

• Password hash sync: With Azure AD Connect users have a consistent sign-in experience from any location, they can access applications faster and from anywhere
• Sigle Identity: With Azure AD Connect, you can have a single identity for your users both on premises and cloud
• ADDS as Authority: With Azure AD Connect, your on premises ADDS becomes the primary source of authority for user identity
• Azure AD Connect Health: monitor your identity infrastructure and synchronization services, view alerts, and usage analytics

###Steps for Implementation

Day 1-2: Assessment, Design & Planning

• Assessment of current environment
• Assessment of Business requirement
• Define user and stakeholder communication plan
• Plan and design AAD connect Deployment
• Identify prerequisites
• Identifying risk, issues, and dependencies

Day 3-5: Testing & pilot

• Running IDFix
• Azure ADD Connect deployment
• Azure AAD connect configuration
• Synchronization of test and pilot users
• Support and Handover
• Documentation

###Note

• The above estimate is for a Single forest, Single domain ADDS deployment with a maximum of 300 users, for customization, we can discuss
• Any changes on client/user/device are not in the scope
• Azure AD Connect Health requires Azure AD Premium license