Azure Prototype Topology Diagram
============================================
- topology-diagram.md (Pure Markdown — GitHub‑ready) ============================================ markdown
This document provides a clean, resume‑ready 2D ASCII topology diagram representing the minimal Azure prototype environment used for demonstrating identity, endpoint management, and cloud infrastructure capability.
Code
Azure Region
(US West 3)
│
▼
Secure Cloud Access Layer
│
▼
Public IP Address (Static)
- Standard inbound access controls
│
▼
Azure Load Balancer
- Basic inbound mapping for management access
│
▼
Virtual Machine (General Purpose)
- Modern Windows OS
- Cloud identity joined
- Centrally managed
- Security baseline applied
- Endpoint protection enabled
│
▼
Network Interface (NIC)
- Private addressing
- Network security applied
│
▼
Virtual Network (VNet)
- Private address space
- Segmented subnet design
- Network security applied
│
▼
Cloud Identity Platform
- Authentication
- Device identity
- Access control
- Conditional Access
│
▼
Microsoft 365 Platform
- Cloud productivity services
- File storage and collaboration
- Device and application management
- Security and compliance capabilities
│
▼
Unified Endpoint Management
- Windows device enrollment
- Mobile device enrollment
- Configuration and compliance
- Application deployment
- Security integration
│
▼
Endpoint Security Platform
- Threat detection and response
- Device risk scoring
- Security posture insights
│
▼
Mobile Device Platform (Android Enterprise)
- Work Profile separation
- Managed application deployment
- Corporate data protection
- Privacy‑preserving BYOD model
markdown This topology reflects a minimal-cost, production-pattern Azure environment suitable for demonstrating modern cloud identity, endpoint management, and infrastructure skills.
- public-redacted.md (Strong visual formatting) ============================================ markdown
A Production-pattern Azure environment demonstrating:
- Identity (Entra ID)
- Endpoint Management (Intune)
- Security (Defender)
- Infrastructure (VM, VNet, Load Balancer)
- IaC (Bicep, PowerShell, Terraform)
Public IP → Load Balancer → NAT → VM → Intune → Defender → M365
Demonstrates capability to design, deploy, and manage a modern cloud environment aligned with current industry expectations.
- Internal domain names
- Admin accounts
- Subscription details
- Billing configuration
- Internal scripts ============================================
- iac-tooling-overview.md (Pure Markdown — GitHub‑ready) ============================================ markdown
This document describes where Bicep, PowerShell, and Terraform are used in the Azure prototype environment.
Used for:
- VNet and subnet creation
- NIC creation
- Public IP
- Load Balancer + NAT rules
- VM deployment
- NSG rules
Used for:
- Entra ID automation
- Intune device onboarding
- VM configuration scripts
- Local hardening tasks
Used for:
- Cross-cloud portability
- Demonstrating multi-cloud IaC capability
- Mirroring Bicep modules for comparison ============================================