Lab 03: Solution - Portal Walkthrough
Only refer to this after attempting the tasks yourself!
Pre-Lab Setup
Create Break-Glass Account
- Go to Entra ID → Users → + New user → Create new user
- Configure:
- User principal name:
breakglass1 - Display name:
Break Glass Admin 1 - Auto-generate password: Yes (copy and store securely!)
- User principal name:
- Click Next: Properties
- Leave minimal info (this is emergency only)
- Click Next: Assignments
- Add role: Global Administrator
- Create
Store the password in a physical safe or secure offline location.
Create Exclusion Group
- Go to Entra ID → Groups → + New group
- Configure:
- Group type: Security
- Group name:
CA-Exclude-BreakGlass - Description:
Emergency accounts excluded from all Conditional Access - Membership type: Assigned
- Members: Add
Break Glass Admin 1
- Create
Create Pilot Group
- Same process:
- Group name:
CA-Pilot-Users - Members: Add 2-3 test users
- Group name:
Task 2: Create Named Locations
Corporate Office IPs
- Go to Entra ID → Security → Conditional Access
- Click Named locations in left menu
- Click + IP ranges location
- Configure:
- Name:
Corporate-Office-IPs - Mark as trusted location: Yes ✓
- Click + to add IP range
- Enter:
YOUR.PUBLIC.IP/32(e.g.,203.0.113.50/32) - For multiple IPs/ranges, add each one
- Name:
- Create
Blocked Countries
- Still in Named locations
- Click + Countries location
- Configure:
- Name:
Blocked-High-Risk-Countries - Determine location by: IP address (recommended)
- Select countries (example: North Korea, Russia, China - adjust per your policy)
- Include unknown countries/regions: Yes ✓
- Name:
- Create
Task 3: Block High-Risk Countries Policy
- Go to Conditional Access → Policies
- Click + New policy
Name
- Enter:
BLOCK - High Risk Countries
Assignments - Users
- Under Users, click 0 users and groups selected
- Include tab → Select All users
- Exclude tab → Check Users and groups
- Click Select excluded users and groups
- Search and select:
CA-Exclude-BreakGlass - Click Select
Target Resources
- Under Target resources, click No target resources selected
- Select what this policy applies to: Cloud apps
- Include tab → Select All cloud apps
Conditions
- Under Conditions, click 0 conditions selected
- Click Locations
- Configure: Yes
- Include tab → Select Selected locations
- Check:
Blocked-High-Risk-Countries
- Check:
- Done
Access Controls
- Under Grant, click 0 controls selected
- Select Block access
- Select
Enable Policy
- At bottom, Enable policy: Select Report-only
- Click Create
Task 4: Require MFA for All Users Policy
- + New policy
Configuration
Name:
GRANT - Require MFA for All UsersUsers:
- Include: All users
- Exclude:
CA-Exclude-BreakGlass
Target resources:
- Include: All cloud apps
Conditions:
- Leave all as Not configured
Grant:
- Select Grant access
- Check: Require multifactor authentication
- Click Select
Enable policy: Report-only
- Create
Task 5: MFA When Not in Office Policy
- + New policy
Configuration
Name:
GRANT - MFA When Not in OfficeUsers:
- Include: All users
- Exclude:
CA-Exclude-BreakGlass
Target resources:
- Include: All cloud apps
Conditions:
- Click Locations → Configure: Yes
- Include: Any location
- Exclude: Selected locations → Check
Corporate-Office-IPs - Done
Grant:
- Grant access
- Check: Require multifactor authentication
- Select
Enable policy: Report-only
- Create
Task 6: Strong Auth for Azure Management
- + New policy
Configuration
Name:
GRANT - Strong Auth for Azure ManagementUsers:
- Include: Click Select users and groups
- Check Directory roles
- Select roles:
- Global Administrator
- User Administrator
- Application Administrator
- (Add others as needed)
- Exclude:
CA-Exclude-BreakGlass
Target resources:
- Select what this policy applies to: Cloud apps
- Include: Select apps
- Click None → Search for
Microsoft Azure Management - Select it → Select
Conditions:
- Leave all as Not configured
Grant:
- Grant access
- Select Require authentication strength
- Choose: Phishing-resistant MFA
- Select
Enable policy: Report-only
- Create
Task 7: Block Legacy Authentication
- + New policy
Configuration
Name:
BLOCK - Legacy AuthenticationUsers:
- Include: All users
- Exclude:
CA-Exclude-BreakGlass
Target resources:
- Include: All cloud apps
Conditions:
- Click Client apps → Configure: Yes
- UNCHECK: Browser, Mobile apps and desktop clients
- CHECK: Exchange ActiveSync clients, Other clients
- Done
Grant:
- Select Block access
- Select
Enable policy: Report-only
- Create
Task 8: Test Using Sign-in Logs
Accessing Sign-in Logs
- Go to Entra ID → Sign-in logs (under Monitoring)
Finding Relevant Entries
- Click Add filters
- Add filter: User → Enter test user's name
- Add filter: Date → Last 24 hours
- Click Apply
Analyzing a Sign-in
- Click on a sign-in entry
- In the details pane, click Conditional Access tab
- You'll see a list of policies and their result:
| Status | Meaning |
|---|---|
| Success | Policy applied, user met requirements |
| Failure | Policy applied, user blocked/failed |
| Not applied | Policy conditions didn't match this sign-in |
| Report-only: Success | Would have succeeded if policy was on |
| Report-only: Failure | Would have failed if policy was on |
What to Look For
- Are any legitimate sign-ins showing "Report-only: Failure"?
- Are expected policies being evaluated?
- Is the location detected correctly?
Task 9: Enabling Policies
Safe Enablement Process
For each policy:
- Go to Conditional Access → Policies
- Click the policy name
- Scroll to Enable policy
- Change from Report-only to On
- Click Save
- Monitor for 24 hours before enabling next policy
Emergency Rollback
If users report being locked out:
- Sign in with break-glass account
- Go to the problematic policy
- Change to Report-only or Off
- Save
- Investigate sign-in logs to understand what happened
Common Mistakes to Avoid
- Forgetting to exclude break-glass - Always exclude emergency accounts
- Testing on yourself first - Don't lock out your only admin account
- Enabling all policies at once - Enable one at a time
- Not testing Report-only first - Always test before enforcing
- Blocking "All locations" instead of specific ones - Be precise
- Not considering mobile apps - Client apps affect what's blocked
- Conflicting policies - Two policies requiring different things = most restrictive wins