Labs
Student lab steps and instructor-only runbooks.
Do not commit real tenant secrets, tokens, private keys, or reusable credentials.
Structure
student/- learner-facing lab steps and learning observations.instructor/- setup, reset, troubleshooting, and demo-only notes.
Labs should avoid requiring student Global Administrator privileges. If a privileged setup step is required, keep it in instructor/.
Teaching Style
Labs are learning checkpoints, not CTF challenges.
- Do not design flags.
- Do not require students to submit tool output, logs, screenshots, or artifacts.
- Use observations to check understanding: students should be able to explain what they saw and why it matters.
- Instructor-held screenshots or sanitized outputs are teaching aids, not grading requirements.
Original Markdown source
# Labs
Student lab steps and instructor-only runbooks.
Do not commit real tenant secrets, tokens, private keys, or reusable credentials.
## Structure
- `student/` - learner-facing lab steps and learning observations.
- `instructor/` - setup, reset, troubleshooting, and demo-only notes.
Labs should avoid requiring student Global Administrator privileges. If a privileged setup step is required, keep it in `instructor/`.
## Teaching Style
Labs are learning checkpoints, not CTF challenges.
- Do not design flags.
- Do not require students to submit tool output, logs, screenshots, or artifacts.
- Use observations to check understanding: students should be able to explain what they saw and why it matters.
- Instructor-held screenshots or sanitized outputs are teaching aids, not grading requirements.