So here is the scenario where will migrate Dirsync to Azure AD Connect in new Active Directory Forest. We have one of our customers using DirSync on old Active Directory domain. Users & Computers have been migrated to new Active Directory Forest. Now, it was the time to move from DirSync to Azure AD Connet onto the new forest. During the transition, we kept legacy domain dirsync turned on.

AWS started in year 2006 and has been growing consistently providing over 70 different services with their most popular AWS EC2 (elastic compute) and AWS S3 (simple storage service). AWS has been proven a huge success for companies of all size where they want to either move their dev and qa to AWS, or want to try out building new services without having to spend a vast amount of capital procuring IT hardware or they want to move their production environment to AWS or even legacy applications to AWS without having to go through hardware refresh for legacy apps.

I have recently architecture & deployed highly available Active Directory Federation Service and Web Application Proxy setup for one of my customers. The setup is meant for providing Single Sign on for Office 365 applications, Proxy authentication and few external web applications.

Office 365 has been a choice of platform for small business enterprises who are Microsoft shop & doesn’t have large user base and specialized skills within their in-house IT. There are quite a number of offerings within Office 365