Your company runs a hybrid environment across Azure and Azure Stack and uses Azure DevOps for CI/CD. Some applications are built with Erlang and Hack. You need a build execution approach that ensures support for these languages across the hybrid cloud while minimizing management overhead. Which option should you use to run the build pipeline?

The correct option is Azure DevOps self-hosted agents on virtual machines that run on Azure Stack. This approach allows you to install the necessary Erlang and Hack runtimes and build tools directly on the agent machines, ensuring support for these specialized languages. Placing these agents on Azure Stack virtual machines extends your CI/CD capabilities to your on-premises environment, which is crucial for a hybrid setup, while still being managed by Azure DevOps. This minimizes management overhead compared to maintaining separate build systems. Microsoft-hosted agents are unsuitable because they do not pre-install Erlang or Hack, and you cannot customize their environments for these specific languages. Using Azure DevTest Labs or Hyper-V virtual machines for self-hosted agents would work for language support but would not integrate directly with the Azure Stack environment for hybrid deployments, potentially increasing complexity and management overhead for a hybrid scenario.