Microsoft Identity | Secure GitHub Actions with Azure Workload Identity Federation

In the final episode of our #MicrosoftIdentity series, Christos and April highlight how to protect Azure DevOps and GitHub pipelines and actions with the Microsoft Identity platform. They'll run through the Azure DevOps pipeline with a service principal account, GitHub action with Managed Identity and Workload Federated Identity and talk through which one is better! MSIdentity Series playlist: https:aka.ms/DevOpsLab/MSIdentitySeries
Jump to:
00:00 Welcome to the DevOps Lab
01:01 What is Workload Federated Identity and why we need it
02:04 Demo
06:18 Microsoft Identity Series in review
Learn more:
Managed Identities aka.ms/DevOpsLab/ManagedID
Implement Managed ID aka.ms/DevOpsLab/ImplementMan...
Learn more with the Microsoft 425Show 425show.com/
Azure DevOps Docs aka.ms/AzureDevOpsDocumentation
DevOps Blogs aka.ms/devopsblog
Connect:
April / theapriledwards
Christos / christosmatskas
Check out new episodes every week at aka.ms/DevOpsIsForEveryone

[@muhammadshameem5674]

Perfect timing since i have implemented this few days back 😀👌

[@techyrk99]

Can you help me understand... i see lot video on GitHub Action even from MS than Azure Devops pipeline... i understand that both now MS, but does that mean even MS is pushing more on GitHub Actions rather than Azure DevOps

[@AzureDevOps]

Actions and Pipelines are very separate products. Actions are owned by GitHub, not Microsoft.
Azure Pipelines are very much used for CI/CD, whereas GitHub Actions are awesome at automation. For example, you can trigger Action Workflows using timer triggers and use them to automate previously manual tasks.