Scheduler

Azure Scheduler allows you to invoke actions that call HTTP/S endpoints or post messages to a storage queue on any schedule. In Scheduler, you can create jobs that reliably call services either inside or outside of Windows Azure and run those jobs right away, on a regular or irregular schedule, or set them to run at a future date.

If you have any feedback on Azure Scheduler, we’d love to hear it.

  1. Scheduler support for TLS 1.2

    Hi,

    Our technical team has raised an issue and confirmed with MS that Scheduler currently only supports TLS 1.0.

    Please add support for TLS 1.2. We are trying to use scheduler to initiate Azure Functions running in an ASE in a private VNET. We had planned to have an API receive these triggers from scheduler. We are unwilling to enable TLS 1.0 support on our Azure Application Gateway (AAG) so Scheduler is unable to communicate with the API we planned to create.

    Thanks, Matt

    235 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow scheduling jobs based on timezone

    Currently, you can only schedule jobs based on a fixed time offset from GMT. This means the actual local time when the job runs will change one hour forward or backward, in spring and fall when daylight savings change.

    234 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  10 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Customizable timeout to a scheduled job through Azure Portal

    Add the ability to customize the timeout interval through the Azure portal.
    This feature is right now only available through API.

    121 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    Mr. Andersson,
    To be clear, do you mean the retry policy for an HTTP request (which includes the timespan between retries and the number of retry attempts to make)?

    Thanks,
    Kevin

  4. Email alert if HTTP/S response status is 4xx or 5xx

    Maybe this feature exists already, but I can't see it...

    It would be great to be alerted via email if any of my HTTP/S jobs fail.

    This could be DNS resolution failure, or a response with a code of 4xx or 5xx.

    61 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    Mr. Boot,
    Thank you for your feedback. In the meantime you can create an error action on the job that is configured to send an email via a service like SendGrid or a text message via a service like Twilio.

    -Kevin Lam

  5. Allow call internal endpoint or virtual network address

    I think that it could be useful to make http call to internal endpoind of "private" cloud services or vm inside a private azure vnet (not externally visible)

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    Thanks for making the suggestion.
    This can be done by either opening a port on your VNET, using a Service Bus Relay endpoint, or installing Hybrid Connector.

    -Kevin

  6. Insert a queue message into ARM Storage

    Storage queue action supports only Classic Storage.
    Today, customers tend to use a new deployment model: ARM. So it would be much better to start support for ARM Storage.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Advanced Scheduler Job Dependencies

    For example; Job 2 is dependent on job 1 finishing successfully before it can start.

    A job should not start unless all conditions are met besides a scheduled start time. 3 conditions in particular that would be very useful for this; Queued/waiting, failed and successful. Even more useful if a job could be configured to run an action if it has been sitting in a waiting state for x amount of time...

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add more configurations for Storage Queue Action Type

    We use the scheduler service to start a long running job once a day. We want to set the expiration time to one day so that the service is not running in parallel or twice.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    I’m not exactly clear what you are looking for. Do you mean that you would like the message in the queue to expire (be deleted) if it has not been processed (read) by a certain time?

    Thanks for your suggestion,
    Kevin

  9. create a dashboard with the ability to see upcoming schedules

    We would like to see a dashboard that includes a comprehensive view of what is scheduled for a 24h period. This would show schedules from 12:00am to 11:59pm. I can see that "Nextrun" is data that is already available from the cmdlet "Get-AzureRmSchedulerJobCollection".
    Fields we would like to see are: Job name, job collection, status, start time, end time, and elapsed time.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Append to job history

    If my backend work takes longer than the http request time (asynchronous) or for queue based requests, I would like to have an API to append status to the history of the job to indicate that the actual backend work is completed.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Collection of generic task to be scheduled

    There are a lot of generic tasks that we may have to schedule. For instance shutting down/ up some VMs or other resources...

    Why not having the choice of selecting in a built-in collection of tasks as an alternative to select an url?

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    This is a great idea. Please include a list of the top most generic tasks you would like to see.

  12. Version control in Scheduling Services

    Currently Version control is not enabled in Scheduler.
    Code checkin and check out and team coding will help

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    Today you can save the Scheduler definition as JSON via PowerShell and the API and check that into source control. If there is something that you are looking for in particular in regards to source control would you mind elaborating?

    Thanks,
    Kevin

  13. This needs job completion to trigger other jobs and allow job dependencies

    We use CA 7 for job scheduling, which offers triggering of other jobs based on successful completion. Also jobs that have dependencies on other jobs. I guess this is more of an automated workload processing system, and not a simple scheduler. Are there plans to make Scheduler this powerful?

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add TCP connection

    It would be good to support TCP connection for IoT devices and TCP-based network routing/proxy devices. At first, only reachability checkup is helpful.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  15. Increase max Message Body Size

    I would like to be able to send a greater message body for my Jobs.

    I think at least 64Kb message body size should be supported so it can be used with the maximum payload size of a storage queue message.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    The challenge with upping the limit of the max message size (which is 8K today) is that it increases storage on our backend as we would have to keep those large messages around to be able to send it on each occurrence a job. Referencing a blob is a nice idea for being able to mitigate that. I will add that to our backlog.
    Thanks for your feedback.

    -Kevin

  16. scheduler: job collection auth

    Hi,

    The Azure Scheduler allow us to use Basic Auth.
    However, we have to defined credentials for each Job.

    Because I'm planing, for my company, to use it for a large number of jobs / job collections. I would like to configure the Basic Auth for each Job Collection instead of Jobs directly.

    Ex : If we need for any security reason to change our credentials, we won't need to update hundreds of jobs, but only few job collection.

    Is it possible to override the feature to get the Job Basic Auth if defined or Job collection instead or nothing…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    Thank you for submitting this idea! This has been something that we have been considering but were waiting for customer feedback. In regards to your last question about overriding the feature could you provide more clarity as to what you are looking for?

    Thanks,
    Kevin

  17. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add support for specifying resourceId when setting up Azure AD OAuth for Scheduler

    https://docs.microsoft.com/en-us/azure/scheduler/scheduler-outbound-authentication#request-body-for-activedirectoryoauth-authentication

    Missing resourceId will cause the token to miss any app specific roles that might be configured.

    Now, in our our endpoints that are called with scheduler, we are forced to remove any role-checking attributes. This leaves us more vulnerable to attacks since we check authentication only and not authentication + authorization.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  19. auth0 authentication options

    Hi

    We want to use the scheduler to call (POST) an API endpoint that we currently have secured with JWT tokens.

    As security provider we are using Auth0.

    We noticed that there are some configurations regarding authentication, but seems that there is no way of configuring Auth0 here. The settings needed are (almost) the same as for ActiveDirectoryOAuth.

    Are there any plans currently to support this ? Are there any workarounds that we can apply?

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Scheduled Jobs targeting AppService WebJob fail under Free Tier

    I recently encountered much difficulty creating scheduled job under free tier with the new portal. It is my understanding that I can have 5 scheduled jobs, each of which can run every hour.

    However this does not work when you are targeting an App Service WebJob. It continually complains about missing credentials, however it is impossible to enter authorization credentials (only for plans Basic and higher )

    Please see my question for more details on stackoverflow
    http://stackoverflow.com/questions/42825256/azure-scheduled-job-fails-to-execute

    I recently had a phone call with a support engineer who finally helped my to get the scheduled job running. By adding my…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Features  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base