Building a Production-Ready Azure Lighthouse Deployment Pipeline with EPAC
Recently I worked on an interesting project for an end-to-end Azure Lighthouse implementation. What really stood out to me was the combination of Azure Lighthouse, EPAC, DevOps, and workload identity federation. The deployment model was so compelling that I decided to build and validate the full solution hands-on in my own personal Azure tenants. The result is a detailed article that documents the entire journey, including pipeline design, implementation steps, and the scripts I prepared along the way. You can read the full article hereHow to deploy from Azure DevOps pipeline to App Service in customer Subscription, through Lighthouse
Hi all. We have a project, a normal web app, in our Azure DevOps. Build & deploy work just fine using the pipelines, to our own dev subscriptions. But the actual customer has their own Azure tenant and subscription(s). We have access to there through Azure Lighthouse - it works, we can work on the resources in their subscription and so on. Access is through a security group in our AAD. But we are having trouble deploying from Azure DevOps pipeline (YAML, if that makes a difference) to the customer subscription. We created a service connection in DevOps, I added the service principal to the security group in our AAD that has the Lighthouse access - no go, deployments fail. Error seems to indicate that the deploy pipeline can't find the App Service in the customer subscription, which I think means it doesn't have access. Has anyone been able to do this is? Is it supposed to work, or am I missing something?
