IAM includes several specialties, so “learn identity” is still too broad to tell you what to study next.
Choose the problem you want to become good at solving. Directory integration, employee SSO, governance, privileged access, and customer sign-in involve different systems and responsibilities.
The five categories below help you compare those directions with your current background. You don't need to master all five before applying. Pick one plausible starting point and an adjacent area to understand, then use actual job requirements to refine the choice.
Directory and hybrid identity: trace an account across systems
This specialty concerns identities and relationships used across on-premises and cloud environments. Start with three questions:
- Management: Where is the account or relevant attribute managed?
- Movement: How does its information reach the other directory?
- Disagreement: What should you investigate when the systems show different information?
Windows administration and directory-support experience can provide useful context. The next challenge is understanding the relationship between environments, rather than assuming cloud identity is another domain controller.
Microsoft's hybrid identity overview is a useful reference.
For a learning project, trace one fictional identity through a documented synchronization scenario. Record the source, the change, and the observed result. Keep the claim limited to what you actually configured and tested rather than treating one successful sync as mastery of hybrid identity.
Workforce access and SSO: connect employees to applications
This lane focuses on how employees sign in and receive appropriate application access.
You may work with application owners, vendors, and support teams to investigate sign-in failures or implement integrations.
A small test application gives you a way to follow the normal login path and diagnose one intentional configuration error. You should distinguish successful authentication from permission to use a particular application function.
This can appeal to someone who likes tracing interactions between systems and explaining where a request stopped.
Identity governance: make access decisions accountable
Governance work asks who should receive access, who approves it, and whether the access still belongs later.
The technical tools matter, but so do ownership, employment changes, exceptions, and usable evidence.
A first exercise could be a fictional access review: identify users, assigned permissions, resource owners, and the decision each owner should make. Record what changes after the review.
You may enjoy this lane if you like turning an ambiguous process into something people can follow and verify.
Privileged access: control powerful permissions
Privileged access work concerns accounts and capabilities that can make high-impact changes.
The questions include who can elevate, for what purpose, for how long, and how that use is reviewed. Microsoft's PIM overview illustrates one implementation; privileged access management is broader than that single feature.
A starting exercise can compare an ordinary account with a separate administrative role and explain the approval and time boundary for the privileged task.
Do not grant broad access merely to make the demonstration easier.
Customer identity: make sign-in work for external users
Customer identity deals with people using an organization's customer-facing applications, not only its workforce.
Registration, account recovery, application integration, and the user experience can become central concerns. Microsoft's CIAM overview describes one product's approach.
A small application sign-in scenario can help you decide whether you enjoy working close to developers and product requirements.
A familiar authentication term does not mean customer and workforce identity have identical operating assumptions.
These lanes overlap. A customer application still needs governance decisions, and a directory engineer may investigate SSO. The categories help you choose an initial emphasis; they are not walls between teams or permanent limits on your career.
Pick one lane and one adjacent skill
Compare the five areas with your existing experience and several realistic job descriptions. Choose one primary direction for your next project, plus one adjacent area to understand later.
Choosing a first lane without treating it as a lifetime commitment makes this decision less intimidating.
The Six-Figure IAM Career Playbook brings the lane comparison together with skills, labs, and a 90-day plan. The $9 guide is meant to help you focus, not convince you to learn every identity product.
A narrower starting point gives you a clearer reason for what you study next.