| Cloud security on Azure :👈 | 👉:Azure Application vs Delegated Permissions |
Cloud Security with Windows and Active Directory |
AD provides centralized identity management for users, devices, and services.
Federation allows trust between on-prem AD and external identity providers.
You're migrating a legacy app to Azure:
Result: A secure, hybrid identity infrastructure with centralized control, federated trust, and cloud-native protection.
Flow: User signs in → Azure AD checks identity → Syncs with On-Prem AD or Federated AD → Issues token → Accesses cloud app securely.
| Feature | Active Directory (AD) | Azure Active Directory (Azure AD) | Federated AD |
|---|---|---|---|
| Deployment | On-premises | Cloud-based | Hybrid (AD + external identity provider) |
| Authentication Protocols | Kerberos, NTLM | OAuth2, OpenID Connect, SAML | SAML, WS-Fed, OAuth2 |
| SSO Support | Limited to domain-joined devices | SSO across cloud apps | SSO across trusted domains/providers |
| User Management | Manual or via Group Policy | Cloud-based with automation | Delegated to federated provider |
| Integration | Windows Server, Exchange, SCCM | Microsoft 365, Azure, SaaS apps | External apps and identity providers |
| Security Features | Group Policy, ACLs | MFA, Conditional Access, Identity Protection | Token-based access, claims transformation |
| Use Case | Traditional enterprise networks | Cloud-first or hybrid organizations | Cross-org collaboration and SSO |
Tip: Use Azure AD Connect to sync on-prem AD with Azure AD, and AD FS for federation with external identity providers.
| Cloud security on Azure :👈 | 👉:Azure Application vs Delegated Permissions |