Module Summary

Module Summary

Module MSA0 established the foundations of security architecture thinking — the discipline, the methodology, the environment, and the tools you'll use across fifteen modules.

Security architecture vs configuration (Section 0.1). Configuration answers "what is turned on." Architecture answers "why this design, what was rejected, what risk remains." The course teaches the second — the documented reasoning that makes every security decision defensible.

The M365 security stack as an architecture (Section 0.2). Twelve security domains connected by data flows and signal dependencies. Identity feeds authentication. Authentication feeds Conditional Access. CA consumes device trust from Intune. Detection monitors what protection prevents. The connections are the architecture.

Architecture Decision Records (Section 0.3). The documentation methodology for every design decision. Context, decision, alternatives rejected, consequences, and the 30-second version for the CISO. By course end, you have thirty or more ADRs.

Threat-informed architecture (Section 0.4). Design from the attacker's perspective, not from a best-practice checklist. Map controls to specific techniques. Name the gaps as residual risk. An architecture designed without a threat model protects against theoretical attacks.

Northgate Engineering (Section 0.5). The 810-person organization you'll architect security for throughout the course — with every constraint real environments have. Legacy applications, mixed licensing, executive exceptions, vendor demands.

Lab environment (Section 0.6). M365 E5 developer tenant and Azure subscription configured. Cost managed under $25/month. The architecture you design is the architecture you implement.

Architecture package (Section 0.7). The deliverable structure: ADRs, decision matrices, risk register, compliance mapping, and executive summary. Populated across fifteen modules.

What you built in the free modules

Across MSA0 and MSA1, you've built the foundation the rest of the course depends on.

The methodology. You know how to think about security architecture — not as a list of settings but as a set of connected decisions with documented reasoning. You know how to write ADRs. You know how to design from the attacker's perspective.

The identity layer. MSA1 designed the identity architecture — tenant decisions, identity type governance, hybrid identity, administrative boundaries, lifecycle automation, naming conventions, and group architecture. Every security control from MSA2 onward operates on this identity layer.

The environment. Your developer tenant is configured. Your architecture package structure is established. Your baseline assessment is complete. The lab is ready for MSA2.

What happens next