Azure Automazion Runbook not saveable

Question

Azure Automazion Runbook not saveable

Jegg Niklas 30

Hello,

does anyone know why i am not able to save changes i made to an Azure runbook? this is driving me crazy since yesterday.

I have the right permissions and i can edit the runbook. However when i hit save and the publish, refresh the page and view the runbook it is still blank or on existing ones my changes did not save.

Or is this again a MS Problem?

Thanks and BR Niklas

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-02-15T06:16:43.8133333+00:00

@Jegg Niklas I wanted to check if you are still facing this issue and/or the response above has helped.

Answer accepted by question author

AnuragSingh-MSFT 21,566 Moderator

@Jegg Niklas I am sorry for the inconvenience. Can you please check the following and help us understand the issue better:

Are you still facing this issue? I checked and could not find any other complaints for the similar issue from past few days. I was able to edit/publish runbooks in my Automation Accounts without any issue.
If you are still facing this issue, the following would help isolate the issue further for troubleshooting/resolving. a. Is it happening with only one Automation Account? b. It could be related to the browser cache or browser extensions being used. Please try to change browser and disable/remove the extension to see if you are still facing this issue. c. Also, see if other users are also facing this issue. d. Is it only a single runbook for which issue is being reported or multiple runbooks?
If you are not facing this issue currently, the issue could have been transient/short-lived due to the environmental factor.

Please let me know if you have any questions.

Jared-2530 40 Reputation points

2026-11-08T22:20:36.3033333+00:00
Hi, I experienced a similar issue to this, not exactly, but I figure this information could be useful.

Problem:

I could:

Create runbooks

Edit/Save runbooks

I couldn't:

Publish (with the portal)

The portal UI allowed me to press the Publish button via Edit > Edit in portal, but I was not receiving the notification that the runbook publish is either in progress or completed, and the runbook stayed unpublished.

I've asked multiple colleagues in our tenant with the same IAM permission to press Publish on the same runbooks, and they were successful.

"Solution":

I can't confirm this is the actual solution; however, it fixed itself immediately after I used the Azure CLI to publish the runbook. The CLI publish succeeded, and after that the Publish button in the portal started working as expected.

I used the following command: az automation runbook publish --resource-group "<resource-group>" --automation-account-name "<automation-account-name>" --name "<runbook-name>"
Your questions:

a. Is it happening with only one Automation Account?

I didn't check this

b. It could be related to the browser cache or browser extensions being used. Please try to change browser and disable/remove the extension to see if you are still facing this issue.

I tried:

Edge

InPrivate Edge

Chrome with clear cache

None of these worked until after publishing with the CLI.

c. Also, see if other users are also facing this issue.

No, other users weren't affected.

d. Is it only a single runbook for which issue is being reported or multiple runbooks

Multiple runbooks.

1 additional answer

AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-02-15T06:16:43.8133333+00:00

@Jegg Niklas I wanted to check if you are still facing this issue and/or the response above has helped.
Jared-2530 40 Reputation points

2026-11-08T22:20:36.3033333+00:00

Hi, I experienced a similar issue to this, not exactly, but I figure this information could be useful.

Problem:

I could:

Create runbooks

Edit/Save runbooks

I couldn't:

Publish (with the portal)

The portal UI allowed me to press the Publish button via Edit > Edit in portal, but I was not receiving the notification that the runbook publish is either in progress or completed, and the runbook stayed unpublished.

I've asked multiple colleagues in our tenant with the same IAM permission to press Publish on the same runbooks, and they were successful.

"Solution":

I can't confirm this is the actual solution; however, it fixed itself immediately after I used the Azure CLI to publish the runbook. The CLI publish succeeded, and after that the Publish button in the portal started working as expected.

I used the following command: az automation runbook publish --resource-group "<resource-group>" --automation-account-name "<automation-account-name>" --name "<runbook-name>"
Your questions:

a. Is it happening with only one Automation Account?

I didn't check this

b. It could be related to the browser cache or browser extensions being used. Please try to change browser and disable/remove the extension to see if you are still facing this issue.

I tried:

Edge

InPrivate Edge

Chrome with clear cache

None of these worked until after publishing with the CLI.

c. Also, see if other users are also facing this issue.

No, other users weren't affected.

d. Is it only a single runbook for which issue is being reported or multiple runbooks

Multiple runbooks.

Answer 1

Jegg Niklas 30

@AnuragSingh-MSFT it is solved now somehow. But the whole tenant was facing the issue last week. 9. and 10th February.

on 9th the whole day and on 10th until like 9 in the morning

AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-02-15T06:48:47.48+00:00

@Jegg Niklas thank you for the confirmation that the issue is resolved now.