How can we improve Azure Automation service?

← Automation

Redeploying jobSchedule resource from ARM template

Currently Microsoft.Automation/automationAccounts/jobSchedules resources cannot be redeployed from ARM template if there are existing jobSchedules pointing to the same runbook and schedule. The deployment would return:

"A job schedule for the specified runbook and schedule already exists"

Same issue even deploying with a different name (GUID) for the jobSchedule.

Currently the workaround is deleting the existing resource and redeploy, which is a very cumbersome approach for automation.

275 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Yulun Zeng shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
planned  ·  AdminAutomation Team (Product Manager, Microsoft Azure) responded  · 

Redeploying job schedule through ARM template needs a different jobschedule GUID. Even if you delete the job schedule , the GUID is retained in the database , hence a 2nd deployment will succeed only if the GUID is different.

The scenarios where jobschedule GUID cannot be reused is as follows:

1) The automation account is deleted before deleting the job schedule. The job schedule entry is soft deleted but is still present in the database.

2) The automation account is created with the same name again and the same GUID is used for job schedule.

We have identified as a bug & an improvement task is planned. We will pick this up as resourcing allows since this would need some changes in the architecture. As a workaround to this, pls update the GUID for jobSchedule.

Show previous admin responses (2)

13 comments

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment

Automation: Bug

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice