An error occurred while saving the commentPohl, BJ commented
This is a good idea. Similar idea with same result (don't want to dilute the ideas with a separate posting): Alert based on projected spend exceeding budget.
Point is, the fixed % of budget is only so useful depending on when it is exceeded.
2 votes0 comments · Azure Active Directory » Entitlement Management · Flag idea as inappropriate… · Admin →Pohl, BJ shared this idea ·
Thanks for this suggestion!
We are working on this . The fix will support PUT scenario though Re-PUT/GET will not return the uri as before for security reasons. ETA would be Feb-End CY21.
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.