Skip to content
All projects
Zero Trust · IdentityHome Lab

Zero Trust Identity Perimeter

Establishing identity as the primary control plane with layered Conditional Access and least privilege.

Zero TrustEntra IDConditional AccessRBACSSPR

Difficulty

Advanced

Environment

Entra ID / Zero Trust

Deployment

Home Lab

Est. Implementation

4–6 weeks

Related certifications:SC-300SC-100
GitHub
Overview

Executive Summary

This home-lab project designs identity as the primary security perimeter, layering Conditional Access, least-privilege RBAC and continuous verification to enable secure remote and hybrid access without relying on the network edge.

It demonstrates a modern Zero Trust identity architecture that can be adapted to enterprise environments.

Context

Business Problem

Traditional network-centric security assumes trust based on location, which breaks down for remote and hybrid work and cloud-first access.

As work moves beyond the corporate network, identity must become the control plane. A network-based perimeter alone no longer protects modern access.

Business Risks

  • Over-trusting network location for access decisions
  • Excessive standing privilege
  • Weak verification for remote access

Compliance Concerns

  • Least-privilege and access governance principles
  • Continuous verification requirements
Approach

Solution Overview

The design layers Conditional Access policies, least-privilege role assignments, self-service password reset and strong authentication to build an identity-centric perimeter.

Access decisions are based on identity, device and risk signals rather than network location, enabling secure access from anywhere.

Design

Architecture

Architecture Diagram
100%

Architecture diagram placeholder

Zero Trust identity architecture — identity as control plane with layered Conditional Access, RBAC and continuous verification. Detailed diagram to be added.
Stack

Technology Stack

Microsoft Entra ID

Identity provider and control plane

Conditional Access

Layered, signal-based access policies

RBAC

Least-privilege role assignments

SSPR

Self-service password reset

Hyper-V

Home-lab virtualisation for test identities

Environment

Lab Environment

Tenant
Microsoft 365 developer / lab tenant
Licensing
Entra ID P2 (lab)
Identity
Microsoft Entra ID
Virtual Machines
Hyper-V lab VMs
Operating Systems
Windows Server + Windows 11
Network
Segmented lab network
Build

Implementation

A phased, expandable walkthrough. Screenshots and evidence can be attached to each phase.

  1. Stand up the lab tenant and identities.

    • Provision lab tenant and users
    • Configure Hyper-V test VMs
    • Establish baseline identity configuration
    Screenshots for this phase can be added here.
Automation

PowerShell

Illustrative example snippets — copy or download each script. Production values are placeholders.

Review role assignments (Graph)

get-role-assignments.ps1
# Example — review directory role assignments via Microsoft Graph
Connect-MgGraph -Scopes "RoleManagement.Read.Directory"

Get-MgRoleManagementDirectoryRoleAssignment |
  Select-Object PrincipalId, RoleDefinitionId
Evidence

Configuration Screenshots

Click any tile to open the lightbox. Real screenshots will replace these placeholders.

Proof

Validation

  • Identity-Based Access

    Access decisions use identity and risk, not location.

  • Least Privilege

    Roles follow least-privilege principles.

  • Strong Authentication

    MFA and SSPR are enforced.

  • Continuous Verification

    Signals are re-evaluated per access.

Reality

Challenges

Policy layering complexity

Designing non-conflicting, layered policies required careful planning and testing.

Balancing security and usability

Strong controls were tuned to avoid unnecessary friction for legitimate access.

Insight

Lessons Learned

  • Identity-first design is the foundation of modern Zero Trust.
  • Least privilege must be governed continuously, not set once.
  • A home lab is an excellent way to prove architecture before production.
Outcome

Business Impact

Identity control plane

Zero Trust Alignment

Least privilege

Reduced Risk

Location-independent

Secure Remote Access

Role model

Improved Governance

Capability

Skills Demonstrated

Zero Trust ArchitectureMicrosoft Entra IDConditional AccessRBAC & Least PrivilegeMFA & SSPRIdentity Governance
Mapping

Related Certifications

Certifications this project maps to are highlighted.

MS-102SC-200SC-300SC-400AZ-900AZ-500SC-100
Reading

Related Blog Articles

Placeholder cards — future TechCertGuide integration.

Source

GitHub Repository

lokeshm-it/m365-zero-trust-identity

Public

Home-lab Zero Trust identity architecture and notes.

Resources

Download Center

Project Case Study

PDF · Available soon

Architecture Diagram

PDF · Available soon

PowerShell Scripts

ZIP · Available soon

Technical Documentation

PDF · Available soon