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. 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 →
  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. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. Time fields should show 24-hour time

    Start-time field and End-time field now show 12-hour time; For example, '12:00:00 AM' or in Japanese locale, '12:00:00 午前'. However, we must type Chinese characters '午前' to input a date.
    In order to save trouble, it will be useful to show 24-hour time in those fields.

    28 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 →
  19. Save UTC offset settings

    When we create a job, we can enter a UTC offset field.
    However, when we edit the job, the UTC setting is never saved and start-time and end-time fields are changed as UTC time, as if UTC settings were ignored.

    From the perspective of UX, UTC settings should be saved just as we enter the data. This specification may confuse Azure Scheduler users.

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

Scheduler

Categories

Feedback and Knowledge Base