How to Become a Desktop Engineer — Part 5: Identity: AD, GPO, Entra ID, Conditional Access
How to Become a Desktop Engineer — Part 5 of 13
Identity: AD, GPO, Entra ID, Conditional Access
Post 4 gave you the machine — Windows 11 from the power button to the desktop. This is the fifth post in a thirteen-part series on how to become a desktop engineer, and it’s about the other half of the story: who gets in, and what they’re allowed to do once they’re there.
In the old world, the perimeter was the office wall. If you were on the network, you were in. That world is gone. The device is in a kitchen, the user is on a home network, and the only thing standing between the company’s data and anyone with a stolen password is identity. The firewall didn’t disappear — it moved into the sign-in. That’s why identity is the new perimeter.
The research backs that up: Active Directory was named in 20% of 2,745 US IT-support job ads in October 2026 — one in five postings asks for it by name. One employer lists Entra ID operational administration and Conditional Access troubleshooting as day-to-day work. This isn’t a side topic.
The old world: Active Directory and Group Policy
Most estates still run Active Directory, and the engineer’s job starts with understanding what it actually is: a directory of everything — users, computers, groups — and a set of rules about who can do what to which of them.
Organisational units are how you organise that directory — containers for a department, a site, a fleet of laptops. Policies apply to OUs, and so does delegation, so design the tree the way the company actually works, not the way the org chart looked five years ago.
Group Policy is how AD pushes configuration: settings, scripts, drive mappings, security baselines, delivered at sign-in and on a refresh cycle. GPO design is a skill in itself — one policy per purpose, named so the next person can tell what it does, linked at the right level, tested on a small group before it reaches the fleet.
Troubleshooting GPOs is a method, not a guess. When a setting doesn’t land: is the machine in the OU the policy is linked to? Is the policy actually enabled, or left “not configured”? Is something else winning — a policy linked closer to the object, or an enforced policy higher up? gpresult on the machine shows exactly which policies applied and which were denied, with the reason. Read the result before you change anything.
And here’s the part that matters for your career: migration thinking. Microsoft’s direction is Intune, and the bridge is Group Policy analytics — a tool that reads your existing GPOs and tells you which settings Intune can replace and which ones can’t. You don’t need to run a migration to be valuable; you need to be the person who can look at a GPO estate and say, honestly, what moves cleanly and what doesn’t.
The new world: Entra ID
Entra ID — the service that used to be called Azure AD — is where cloud identity lives. It’s the directory for Microsoft 365, for cloud apps, for every sign-in that doesn’t touch a domain controller. And the first thing to get straight is the difference between the two ways a device relates to it.
Registration is the light touch: a personal or BYOD device, where the user signs in with a work account and gets single sign-on to cloud apps plus Conditional Access evaluation — but the device stays user-owned and lightly managed. Join is the full commitment: an organisation-owned device where Entra ID is the authority, managed in full through Intune, with single sign-on to cloud resources. Confuse the two and you’ll spend an afternoon wondering why a registered device isn’t getting your policies.
The day-to-day work is quieter than the concepts: the user lifecycle — accounts created, changed, disabled when someone leaves; the device lifecycle — devices enrolled, retired, wiped; and the steady drip of sign-in issues. Operating Entra ID means reading sign-in logs the way Post 4 taught you to read Event Viewer — the evidence is already written down, with a time stamp, if you know where to look.
Conditional Access: the enforcement chain
Conditional Access is where identity stops being a directory and becomes a decision. Every sign-in runs through a chain, and each link has to hold:
- The device proves its health — a compliance policy in Intune says it’s encrypted, patched, not jailbroken.
- The user proves who they are — a password plus a second factor, or Windows Hello.
- The context is checked — where is the sign-in coming from, and is this a normal pattern for this user?
- The policy decides — allow, block, or allow with a condition, like requiring MFA or a compliant device.
Compliance policy says the device is healthy, Conditional Access lets it in. That’s the chain in one sentence — and when it breaks, run the same five-step loop from Post 3 on the chain instead of the machine. Is it this user, this device, or everyone? If everyone is blocked, you changed a policy, not a device — check what landed recently. The sign-in log names the exact policy that blocked the attempt and the exact condition that failed; the fix matches the cause — a device that needs to re-check compliance, a policy with the wrong group in scope, a location that should have been trusted.
The hard case is Conditional Access blocking the wrong person. A VIP locked out of email the morning of a board meeting is the ticket that teaches you the difference between a policy and a punishment. Resist the temptation to exempt the person and move on. The exemption hides the fault; the sign-in log explains it. Fix the scope, fix the condition, and the next VIP never calls.

MFA, Windows Hello, and the local admin password
Two more pieces complete the picture. Multi-factor authentication is the second factor in the chain — something the user has, like a phone, on top of something they know. It’s the cheapest security improvement in the whole estate, and the one users resist most. Windows Hello for Business replaces the password with a PIN or biometrics tied to the device — phishing-resistant, because the credential never leaves the machine.
Then there’s the password nobody thinks about until it matters: the local administrator password. Windows LAPS gives each machine its own unique, rotating local admin password, stored centrally. Before LAPS, estates ran one shared local admin password on every device, and one leak compromised the fleet.
The hybrid reality: debugging across the seam
Here’s the truth about real estates: most run both worlds at once. Domain-joined machines on-prem, Entra-joined laptops in the cloud, hybrid-joined devices in both directories at the same time. Two directories, two policy engines, one user who just wants to sign in.
The engineer who only knows the old world can’t debug the new one; the engineer who only knows the cloud can’t explain why the domain-joined machine in the corner office isn’t getting its policy. The valuable engineer is the one who can stand on the seam and trace a fault across it.
Hybrid join is the clearest example: one device in both directories, one sign-on that has to work in both directions. When it breaks, the symptom is always the same — “I can’t sign in” — and the cause could live in either world. The sign-in log tells you which one.
None of this is glamorous — identity is infrastructure, and infrastructure is the job. The perimeter moved to the sign-in. Learn to read the chain, and you can debug anything that crosses it.

Practise it this week
- Run
gpresulton your own machine. Read which policies applied and which were denied, and find one you can explain. - Read one sign-in log. In Entra ID, find a sign-in — yours, or a test account’s — and trace which policies evaluated it and what each one decided.
- Map your estate’s seam. On paper: which devices are domain-joined, which are Entra-joined, which are hybrid? If you can’t answer, that’s the first thing to find out.
Next up: Networking Essentials. Identity decides who gets in — but the packets still have to get there. The next post is just enough networking to never be blocked by it: TCP/IP, DNS, DHCP and VPN, taught from the endpoint’s point of view.
Missed the earlier posts? Start with Part 1: What a Desktop Engineer Actually Does, Part 2: The Path, Stage by Stage, Part 3: The Mindset — Curiosity Is a Technical Skill, and Part 4: Windows 11 Inside Out.



















