title: Azure deployment: Error while creating webjob schedule (400 Bad Request)
body: <p>I receive the following error while publishing and Azure Website from Visual Studio 2013:</p>
  
  <blockquote>
    <p>12>Publish Succeeded. 12>Creating the scheduler job
    12>C:\projectPath\packages\Microsoft.Web.WebJobs.Publish.1.0.7\tools\webjobs.console.targets(110,5):
    Error : An error occurred while creating the WebJob schedule: Response
    status code does not indicate success: 400 (Bad Request).</p>
  </blockquote>
  
  <p>I have read another posts with similar issues: 404 error, BadRequest: The condition specified by the ETag is not satisfied... but none of these seem to be the problem here. I have reinstalled the Microsoft Azure Tools for VS 2013, the webjobs.publish package in my solution and it didn't work either. I also checked this post <a href="https://social.msdn.microsoft.com/forums/azure/en-US/d5b44e53-c4d7-48ff-a024-4bdd6eb48b79/sheduled-web-jobs-in-azure-web-site-not-configurable-in-same-region-as-web-siteand-workaround?forum=azurescheduler#d5b44e53-c4d7-48ff-a024-4bdd6eb48b79" rel="nofollow">https://social.msdn.microsoft.com/forums/azure/en-US/d5b44e53-c4d7-48ff-a024-4bdd6eb48b79/sheduled-web-jobs-in-azure-web-site-not-configurable-in-same-region-as-web-siteand-workaround?forum=azurescheduler#d5b44e53-c4d7-48ff-a024-4bdd6eb48b79</a> and did what he tried but it haven't solved the issue. 
  It looks like all my files are uploaded correctly to the Azure website, and the issue begins when the scheduler jobs are being created.</p>
  
  <p>The strange thing is that the webjobs are uploaded (updated) and that they are also working correctly, but the scheduled webjobs are not in my jobcollection list in the Azure management portal. I also tried to remove my current job collection and all the jobs from my website, but when I publish the site, all the webjobs are created but the job collection is empty. 
  I had a similar issue with VS and the problemas was that the credentials of the website were expired, but the problem was solved by reentering the credentials in VS. Any idea of how to solve this issue?</p>