Docs say Azure AD, portal says Entra ID, which is which
Microsoft renamed Azure AD to Entra ID. Functionally the same, only the name changed in 2023.
Try this first
- 1Read 'Azure AD' in old docs as 'Entra ID' unless context says otherwise
- 2AzureAD and MSOnline PowerShell modules are deprecated, use Microsoft.Graph
- 3Entra ID Free comes with every M365 tenant, P1/P2 add features
- 4Conditional Access requires Entra ID P1; Identity Protection requires P2
When to bring us in
For B2B/B2C scenarios, Entra External ID is the new product. Plan a separate review.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.