title: Best way to check app health endpoint after deployment in a YAML deployment job?
body: <p>Before you shout &quot;gates!&quot; please read.</p>
  <p>I have on-prem IIS servers farms, I have created a VM Environment for each (dev, test, prod). In all of my apps, I have a CD YAML like so:</p>
  <pre class="lang-yaml prettyprint-override"><code>- stage: Deploy_Test
    jobs:
    - deployment: APIDeployTestIISFarm
      displayName: Deploy API to Test IIS
      environment:
        name: Test
        resourceType: VirtualMachine
      strategy:
        runOnce:
          deploy:
            steps:
  </code></pre>
  <p>Because I have 20 different apps all targeting the same environments, I can not use the gates feature. Not ALL apps have the exact same <code>/health</code> endpoint.</p>
  <p>I am currently crafting a powershell command to simply call /health and maybe throw on the result if &quot;unhealthy&quot;. Although that sounds horribly ugly to me compare to HTTP gate that would simply check 200, and I bet its also fault tolerant/resilient. After all, IIS sites take a second to spin up on first hit after a deployment.</p>
  <p>Open to other ideas or tasks that I have not seen yet.</p>