<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>DevOps - Category - GoToGuy Blog</title><link>https://gotoguy.blog/categories/devops/</link><description>DevOps - Category - GoToGuy Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 15 Sep 2023 12:31:36 +0000</lastBuildDate><atom:link href="https://gotoguy.blog/categories/devops/" rel="self" type="application/rss+xml"/><item><title>Connect to Microsoft Graph in Azure DevOps Pipelines using Workload Identity Federation</title><link>https://gotoguy.blog/2023/09/15/connect-to-microsoft-graph-in-azure-devops-pipelines-using-workload-identity-federation/</link><pubDate>Fri, 15 Sep 2023 12:31:36 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2023/09/15/connect-to-microsoft-graph-in-azure-devops-pipelines-using-workload-identity-federation/</guid><description>Microsoft recently announced that Workload Identity Federation for Azure Pipelines now is in Public Preview: https://devblogs.microsoft.com/devops/public-preview-of-workload-identity-federation-for-azure-pipelines/ .
This opens for a lot of scenarios for Azure service connections, without the need to manage secrets for service principals and more security as there are no secrets that can be exposed or exfiltrated.
As I work a lot with Microsoft Graph and automation, I wanted to see if and how I could use Workload Identity Federation to connect to and send queries to Microsoft Graph using Azure Pipelines.</description></item></channel></rss>