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. For the scheduled tasks product, just place a dropdown with time zone so we know what time we are entering

    Scheduled Jobs, add a time zone dropdown to know what time we are entering. It is so confusing!

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. CRON expression in Azure scheduer

    Could you please provide the option to use CRON expression in Azure scheduler to schedule the job.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 →
  4. 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 →
  5. 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 →
  6. Allow scheduler to be "connected" to vnet, to allow access to hybrid services, running on premises

    To use Scheduler as centralized place to schedule our jobs on both Azure and on-premises Backend Services, we need the scheduler to be access them over Express Route and / or VPN.

    This can be achieved, if Scheduler can be assosiated with VNET.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 →
  8. Notification should be displayed when you save job with past "Start on" time

    If you change recurrence from "Recurring" to "Once" and set a job to "Start on" past time, this job runs immediately after saving. This behavior is a little bit confusing to users who expect the job should not start. It’s very helpful if a caution appears on the portal when users are going to save jobs with past time.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  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. 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 →
  11. 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 →
  12. hybrid worker runbook drainstop for patching/reboot

    It would be nice if there were a way to "drain stop" a hybrid worker so that the node could complete any running runbook and not start any new ones.
    If an Azure runbook is running on a hybrid worker and the server is rebooted, it will likely re-start the runbook on another node which is good, however if the killed job had already completed a step in the runbook which made a change/uploaded data, etc, and the job is restarted, duplication can occur.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Clone button could be helpful

    It would be good to place Clone button on Scheduler Job blade like logic app for making similar jobs faster.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  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. Add Refresh in Scheduler Job Collection blade

    Reproduce step.


    1. Scheduler Job Collection blade > Add

    2. Add a job and click OK.

    3. Return to Scheduler Job Collection blade, but Monitoring section is not refreshed job list.

    So, it would be good to add Refresh button on the Scheduler Job Collection blade.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 →
  17. Run error config now

    Along with "Run now", it would be good to place "Run error config now" for test purpose.

    Currently, I make an error (server down) and click "Run now", then wait for several retry counts in order to confirm my error config settings correctly.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Scheduler Error Policy following Recurrence policy logic

    On this page (https://azure.microsoft.com/en-us/documentation/articles/scheduler-concepts-terms/) under retryPolicy it says that the default retry policy is 5 times with an interval of 1 minute. This isn't the case; it is 4 times with an interval of 30 seconds. Secondly, when I change it to a custom retry policy with retries every minute, it tells me that this is more often than the 1 hour retry policy allowed by this collection plan (because i'm on the free scheduler)

    Every other piece of documentation says that that 1 hour is how often the scheduler can fire a job, and says nothing about…

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

    Thank you for calling this out. I have put in a request to update the documentation to correctly indicate the default values.
    The FREE plan uses the min recurrence configuration setting (1 hour) as its lower bound for configuring the retry policy. The documentation will be updated to make this clearer as well.

  19. For Scheduler REST API, Update Job, should allow setting "schedule=null"

    The current update job REST API (with PATCH) in Scheduler does not allow recurrence frequency changing from week to hour, when the "advanced schedule" is set. That is because "advanced schedule" is only meaningful for weekly schedule. I tried to set "schedule=null", but it did not work. This means I have to use a GET to get the Job, and then a PUT to update the Job in this case. I think a better idea would be letting the user to update schedule to be null, and letting them change recurrence frequency from week to hour

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Scheduler Jobs Storage Queue works with Resource Manager

    It appears that the "storage queue" action only works with "classic" storage accounts, and not the new "Resource Manager" Storage Accounts. It would be nice if the Scheduler worked with the new Storage Account type.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →

    Scheduler does work with resource manager storage accounts today but the portal currently only lists the classic storage accounts. Until we enable the ability to pick a resource manager storage account in the portal you can do it through the REST API today.

← Previous 1 3
  • Don't see your idea?

Scheduler

Categories

Feedback and Knowledge Base