apwestgarth Thanks for the detailed explanation, sharing layers across app services hosted on the same plan is a nice feature. Regarding Full Windows Server images: you tested it with an IIS based image and it worked because that image included port configuration whereas in my case it was a plain windows image (with an application layer on top) that kept restarting. The reason I have to use the fat image is because I need to be able to run Chrome headless browser and have it render websites with custom fonts and export them to PDF, which doesn't work on Core or Nano. The other three options are ACI, AKS and VMs: ACI doesn't cache image layers and takes a long time to start, AKS requires a cluster and VMs are harder to manage.