[D 4.3] Operating Mail Security: Submissions, Quarantine, and the Queue
Prevention is bought once. Operations is the part that never stops, and it is where Defender for Office 365 either earns its place or gathers dust.
Aaron
[D 4.2] The Protection Stack: What Safe Links, Safe Attachments, and Anti-Phishing Actually Do
Three engines do the real catching, and each hides one decision that matters more than the rest. Teams is now inside the same blast radius.
[D 4.1] Policy Architecture: Presets, Precedence, and the Work That Remains
The mail policy layer is a precedence order, not a pile of settings, and the first policy to match a user wins outright. Knowing which policy speaks for whom is the whole discipline.
[D 4] Defender for Office 365: What Email Security Became
Email is still the way in, but the part you configure has collapsed into a layered platform Microsoft tunes for you. This is where authority over mail and collaboration actually sits, and what is left to own.
[AF 8] The Decision: Replace, Cache, or Keep
The capstone: which workloads move to Azure Files directly, which sit behind a cache, and which honestly belong somewhere else, with the criteria stated plainly enough to argue with.
[AF 7.1] Build Sheet: Data Protection and Alerts
Vaulted backup, a snapshot schedule, soft delete verified, three alert rules, and the restore drill that turns the backup policy from hypothesis into fact.
[AF 7] Operating Azure Files: Backup, Monitoring, and the DR You Actually Have
Snapshots are not backup, vaulted backup finally is, three alerts cover ninety percent of incidents, and the geo-failover story deserves to be told without euphemism.
[AF 6.2] Build Sheet: The Small-Shop Cutover and the Old-Fashioned Drive Map
One server, one weekend, no DFS: the small-business migration to Azure Files, and mapping the same drive letters users have had for twenty years, by GPO, by Intune, or by plain net use.
