How to extract Service Connection name (and possibly other information) from an Azure DevOps Service Connection GUID
Recently, I had an opportunity to work with a customer who asked to automate Azure DevOps pipelines to GitHub Actions. I can hopefully write more about that specific topic later on. What I wanted to talk in this blog was a way I researched and created a script for a task to extract Service Connection name from a special ID called GUID, which usually belongs to Azure service component, which in this case is Azure DevOps Service Connection.
GUID can come from a different source, such as Virtual Computing machine, Azure DevOps Service connection, and many more. In this case, the customer wants to know where the Service Connection comes based on a GUID, which looks like this: 4b3s9ae-b9d4–4059–816e-d25ca53d23e2
If you at a Service Connection under a Project, it looks like this:
Now, GUIDs can show up in number of different places, but those GUIDs for our cases showed up whenever I was trying to transform Azure DevOps to GitHub Actions using a special migration tool. The customer wanted to get the associated Service Connection from each…
