- Active Directory will remain with us for a long time to come:
– Microsoft is not planning to eliminate Active Directory
– The structure of Azure AD differs significantly from the structure of local AD environments
- Functional reasons for using on-premises Active Directory:
– Companies that do not plan to migrate all services to Azure still need a local Active Directory
– Legacy applications often require access to LDAP, NTLM, or Kerberos which Azure AD does not support
- Active Directory support in future Windows Server versions:
– Active Directory is still included in the successor to Windows Server 2022
– Active Directory is expected to be part of Windows servers until at least 2030
- Strengths of Active Directory and Azure Active Directory:
– Azure AD’s mission is to extend on-premises AD environments into the cloud
– Azure AD and Active Directory can work together to provide single sign-on scenarios
- Active Directory and Azure AD are growing together:
– Azure AD provides value and security for cloud services
– Active Directory can be used to secure traditional applications in on-premises data centers
– Synchronization and Azure AD Connect allow both worlds to be connected
- Suitable software solutions for hybrid IT world:
– FirstAttribute offers software solutions for managing identities in on-premises AD environments and in the cloud
– The FirstWare IDM Portal and my-IAM Cloud Identity Management Platform are examples of these solutions
- Future integration of Azure resources into local AD environments:
– Azure resources like data backup and VM synchronization can be integrated into local AD environments
– Windows Admin Center is used for managing the integration
- No significant innovations in Active Directory:
– There have been no significant innovations in Active Directory since Windows Server 2016
– Azure AD can be used for extending authentication to the cloud if needed
