Publish Evidence, Keep Administration Private
ABD Labs needs a public portfolio, but the Microsoft Enterprise Lab will contain administration paths and intentionally broken configurations during learning and incident scenarios.
Microsoft enterprise lab and technical portfolio
ABD Labs publishes verified operations work.
A public evidence record for Windows administration, identity, Microsoft 365 automation and infrastructure work. The lab is built from repeatable steps, and only sanitized outputs are published.
Live route https://abdlabs.org
Static portfolio over TLS, with www redirected to the canonical domain.
Boundary Public proof, private admin
No lab management services are exposed through the portfolio route.
Next gate Lab compute decision
Choose compute, private access, storage quota and snapshot policy.
Case studies
Current Work
completed
ABD Labs Portfolio Routing
abdlabs.org serves a static HTTPS portfolio from this VPS, with www redirected, TLS issued and renewal verified.
nginx / Let's Encrypt / certbot / Static HTML ongoingMicrosoft Enterprise Lab Foundation
The lab has documented architecture, network, security, dataset and automation scaffolds without deploying Windows VMs or paid cloud resources.
Markdown architecture docs / Mermaid diagrams / Synthetic CSV data / PowerShell scaffoldsArchitecture log
Recent Decisions
Use Astro Static Output For ABD Labs
ABD Labs needed to move beyond a hand-written marker page while keeping the public site easy to version, build and serve from nginx.
Prefer Bare-Metal Lab Compute For Windows Lab V1
Windows Lab V1 needs a domain controller, a Windows workstation, private administration, snapshots and repeatable rebuilds. The current VPS is already ruled out for Windows VMs.
Roadmap
Next Practical Step
The public portfolio source is now maintainable. The next lab step is to select the Lab V1 compute path and private access method before any Windows VM, hypervisor or paid cloud resource is created.