--Tom-- on Wed, 16 Mar 2016 02:32:35
At present, when publishing a WebJob from Visual Studio 2015, it can be published to a free-tier job collection, even though WebJob's use basic authentication and the free tier doesn't support 'outbound authentication' (see the
pricing page). When modifying the schedule in the new portal, an error message is displayed, as you would expect.
There are a few mismatches between the old portal, new portal and Azure SDK tooling. Could the Scheduler team comment on the current state and where things are headed? Also, how do you intend for WebJob's to be tested with websites hosted in the App Service free tier? Will the 'Authorization' header be blocked in future seeing the 'outbound authentication' paid feature?