The second part of the series looks at policy as code, drift reconciliation, security scanning, GitHub environments, and how AI can participate in remediation without undermining the trust boundary.
I've been breaking down Microsoft's security stack since before Entra ID was even called Entra ID. No fluff, no paywalls — just technical depth on Entra, Sentinel, Defender, Purview, and Azure Security that the official docs rarely give you.

Discussion on technical topics and MVP path exploration. Pick the intensity that fits your timeline. Only for Individuals.
The second part of the series looks at policy as code, drift reconciliation, security scanning, GitHub environments, and how AI can participate in remediation without undermining the trust boundary.
A practical look at how GitHub, GitHub Actions, Azure identity, policy as code and AI-assisted engineering fit together in a secure Infrastructure as Code delivery model.
Why AI agent security must protect authority, not just prompts, with deterministic policy, isolated sessions, runtime attestation and tenant governance.
Microsoft Entra Agent ID, identity blueprints, MCP authentication and the security controls enterprises need as AI agents become first-class actors.
How Microsoft's Agentic Applications for Unified Data Foundation solution accelerator connects Fabric data, Microsoft Foundry, Agent Framework, and App Service, with practical isolation and AI security controls.
Why I think security architects working with AI should start the Microsoft Frontier Titan, or Frontier Transformation Engineer, track now, and how GH-300, AI-103, AB-100, and the Frontier project assessments fit together.
Microsoft argues that vulnerability remediation is slower than exploitation. My practical view of the network as a fast compensating control, with Azure Front Door, WAF, Firewall, Container Apps, and Zero Trust examples.