We have an Azure Website setup with a \"staging\" deployment slot, and we use a continuous Azure WebJob to process long-running background jobs. It appears that when you pub
To deploy a continuous WebJob in a stopped state simply add a file called disable.job at the root of your WebJob (binaries), this will tell the framework that the WebJob is currently stopped.
To view this behavior you can simply stop a continuous WebJob and see that this file is generated and placed at the WebJob's directory.