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.
Part 8 of the EU data sovereignty series. An honest cost and complexity analysis of the Keycloak–Entra ID federation architecture: infrastructure costs, operational overhead, comparison to native Entra ID licensing, and a practical decision framework for which organisations genuinely need this.
What Apple Pay and Google Pay teach security architects about tokenization, trust anchors, device-bound assurance, and Zero Trust identity design.
Deep dive into PIM Custom Extensions: automated logic gates for privileged access workflows. How to approve/deny elevation requests based on custom business logic, audit trails, and real-world patterns.
Part 7 of the EU data sovereignty series. How to rotate your Keycloak SAML signing certificate without breaking M365 authentication, monitor federation health, tune Conditional Access under federation, and build a break-glass procedure for Keycloak downtime.
Azure Functions now has a serverless agents runtime in public preview: agents defined as .agent.md files, triggered by the same events as Functions, wired to 1,400+ connectors and MCP servers.
Why Microsoft moved Agent ID and agent-user lifecycle permissions away from Global Administrator, which AI and Agent ID roles now own the work, and how to review it in a tenant.
Part 6 of the EU data sovereignty series. How to provision users from Keycloak to Entra ID via SCIM — the ImmutableID anchor problem, attribute mapping for Governance lifecycle workflows, deprovisioning, and handling edge cases.
