Job collection task for which Azure WebJob is assigned

Question

Can I specify which Visual Studio work collection to use when deploying Azure Web Job with a schedule? By default, it tries to create a new Free-tier collection, but since I already have one (and the limit is one per account), it does not expand.

I want to set up a paid job collection and include all of my deployments in this collection.

I am using WebJob from Visual Studio Publish as Azure WebJob... Error message in Visual Studio:

An error occurred while creating the WebJob schedule: in the subscription "XXX" there can be no more than "1" free work collections. (/subscriptions/XXX/resourceGroups/CS-WestEurope-scheduler/providers/Microsoft.Scheduler/jobCollections/YYY)

I want to keep the existing free assignment of assignments (since there are other manually created HTTP assignments in it). It would be much better if I could specify where the WebJob schedule should be.

Thanks!

Answer 1

I managed to get around this now. I have completed the following steps:

• Remove the existing Free Tier job collection on the Azure Portal website.
• Deploy one or more of my new web applications from Visual Studio (including schedule information).
• Return to the Azure Portal website and change the Scale tab in the Free Job Tasks since it was created by Visual Studio for Standard / Premium.
• On the Azure Portal website, create a new (free) collection of tasks and re-add existing manually created HTTP tasks to it.

Once this is done, deployments from Visual Studio will switch to an automatically created collection of tasks (automatically called WebJobs-WestEurope after geolocation of my application), and the other collection will remain alone so that you can use as you want.

Basically, Visual Studio needs to get into FIRST in order to create its collection, and after that you can add collections as you wish. It seems like a limitation that you cannot control which collection it selects, so you should remember that a certain collection is magically associated with Visual Studio deployments. I agree with the configuration, but I don’t agree with the ENVIRONMENT configuration.