<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Conditional-Access on Trust Anchor</title><link>https://trustanchor.pro/tags/conditional-access/</link><description>Recent content in Conditional-Access on Trust Anchor</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 George Vaculik</copyright><lastBuildDate>Sun, 11 Oct 2026 14:30:00 +0200</lastBuildDate><atom:link href="https://trustanchor.pro/tags/conditional-access/index.xml" rel="self" type="application/rss+xml"/><item><title>Just-in-time admin access to Azure DevOps: the group holds the permission, never the human</title><link>https://trustanchor.pro/posts/jit-ado-via-pim-and-ca-auth-contexts/</link><pubDate>Sun, 11 Oct 2026 14:30:00 +0200</pubDate><guid>https://trustanchor.pro/posts/jit-ado-via-pim-and-ca-auth-contexts/</guid><description>Azure DevOps organizations tend to carry permanent administrators, because the usual fix, adding people to Project Collection Administrators behind a Conditional Access policy, time-boxes nothing. This post builds the alternative: the permission sits permanently on an Entra group, the human holds only eligible membership, and an authentication context lets a Conditional Access policy gate the activation itself. The design runs on Microsoft Entra tokens with personal access tokens turned off, ends access through a block policy when the membership ends, and names what it does not prevent: the organization owner and direct assignments.</description></item></channel></rss>