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. Please don't retire Azure Scheduler

    The Azure Scheduler seems exactly what I need to fire a REST request or some other task on a regular basis but I see it is set to retire on 30th Sept 2019 in favour of LogicApps. LogicApps seems overkill for a simple use case like this.

    4 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 →
  2. 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 →
  3. Scheduler deprecated?

    Hi Microsoft, are You sure to deprecate Scheduler ?

    Google recentrly launched its own scheduler https://cloud.google.com/scheduler/

    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 →
  4. 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 →
  5. 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 →
  6. Do not hide an 'Advanced Schedule' on Schedule blade

    The idea to hide an 'Advanced Schedule' on Schedule blade when minute or hour recurrence is selected is definitely an extremely bad idea!
    I was looking for advances scheduling for 6 hours today and even wrote my own ARM template for this. I've discovered the schedule service REST API, ARM schema, all PowerShell cmdlets, etc. But accidentally I've discovered that it is simply hidden! :)))
    Please, do not hide such things in UI.
    Disable them!

    10 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 →
  7. Disable wrapping message with StorageQueueMessage XML

    We would like an option to prevent the scheduler from wrapping the message with StorageQueueMessage XML. There is no indication in the portal that Azure will alter our message text.

    We insert into our queues from the scheduler and our own code. Our messages are JSON strings. It's very inconvenient and inefficient to have to serialize and deserialize multiple times to get/put our message.

    44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  API & SDK  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

  9. 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

  10. 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.

    64 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

  11. 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.

    236 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 →
  12. Azure Scheduler support for variables

    Having the possibility to use date variables in azure scheduler POST requests would allow us for example to make a REST call to azure table storage like 'delete all records before {DateTime.UtcNow.AddMonths(-1)}'.

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  API & SDK  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Kevin Lam responded

    It would be helpful to hear which variables would be most useful to everyone by adding them to the comments of this suggestion.

    Thanks,
    Kevin

  13. 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.

    13 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

  14. 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 →
  15. CRON expression in Azure scheduer

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

    7 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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 →
← Previous 1 3
  • Don't see your idea?

Scheduler

Categories

Feedback and Knowledge Base