Joel Verhagen @joelverhagen.com · 24/09/2025OIDC integration in build/deploy pipelines and in Entra ID is such a game-changer in my mind. It simplifies so much secret management and gives you the "feeling" (analogous capabilities) of managed identities outside of Azure. 010
Joel Verhagen @joelverhagen.com · 24/09/2025Azure DevOps WIF is the analogous idea in Azure DevOps land: devblogs.microsoft.com/devops/intro.... For a while, you traded an ADO minted token for Entra ID. Now you trade on Entra ID token (managed by ADO) for your service principal. But still, same idea as GHA. 100
Joel Verhagen @joelverhagen.com · 24/09/2025This can be done with the federated credentials. docs.github.com/en/actions/h... and learn.microsoft.com/en-us/entra/.... It's very cool! The mental model is that you trade a GHA OIDC token for an Entra ID token. This is allowed by configuring your MI to accept a specific pattern of GitHub token.docs.github.comConfiguring OpenID Connect in Azure - GitHub DocsUse OpenID Connect within your workflows to authenticate with Azure. 101
Joel Verhagen @joelverhagen.com · 13/09/2025Thanks Mattias, that's encouraging! My team did the hard work. I just happened to be on comms at the time and answering questions :) I'm excited to see it GA soon. Great combination of UX improvement (no more manual rotation of secrets) and a security win (not needing long-lived API keys). 010
Joel Verhagen @joelverhagen.com · 28/08/2025> Environment.TickCount is different from the DateTime.Ticks property, which is the number of 100-nanosecond intervals that have elapsed since 1/1/0001, 12:00am. 😑learn.microsoft.comEnvironment.TickCount Property (System)Gets the number of milliseconds elapsed since the system started. 000