Is it possible to restore previous version of runbook once published?

Refer to https://learn.microsoft.com/en-us/answers/questions/5764039/how-to-restore-previous-version-of-runbook-after-p

Azure Automation does not support restoring or rolling back to a previous published version of a runbook. When a runbook is published, it permanently replaces the earlier published version, and Azure Automation does not maintain version history for published runbooks.

The only supported rollback scenario is reverting a draft to the last published version before publishing. Once published again, rollback is not possible.

Azure supports recovery only for deleted runbooks (within ~29 days) using PowerShell or REST APIs, which does not apply to version rollback.

Microsoft recommends maintaining runbooks in an external source control system (such as Azure DevOps or GitHub) and importing them into Azure Automation to manage versions safely.

What is supported (to avoid confusion):

1. Revert Draft to Last Published (Only before publishing): If changes are made in Draft and not yet published, you can discard the draft and revert back to the last published version.
2. Restore a deleted runbook (NOT previous version): If a runbook itself is deleted, Microsoft allows recovery within ~29 days using PowerShell/REST.

• Supported only for deleted runbooks
• Does not restore earlier published versions

What is NOT supported:

• Restoring a previous published version
• Viewing published version history
• Rolling back after publish
• API / PowerShell / Portal‑based rollback. Azure Automation does not store historical published versions.

Because rollback is not supported, Microsoft recommends external version control, such as:

• Azure DevOps Repos
• GitHub
• Maintaining source‑controlled runbooks and importing them into AutomationAzure Automation does not support restoring or rolling back to a previous published version of a runbook. When a runbook is published, it permanently replaces the earlier published version, and Azure Automation does not maintain version history for published runbooks. The only supported rollback scenario is reverting a draft to the last published version before publishing. Once published again, rollback is not possible. Azure supports recovery only for deleted runbooks (within ~29 days) using PowerShell or REST APIs, which does not apply to version rollback. Microsoft recommends maintaining runbooks in an external source control system (such as Azure DevOps or GitHub) and importing them into Azure Automation to manage versions safely. What is supported (to avoid confusion):
  1. Revert Draft to Last Published (Only before publishing): If changes are made in Draft and not yet published, you can discard the draft and revert back to the last published version.
     1. Restore a deleted runbook (NOT previous version): If a runbook itself is deleted, Microsoft allows recovery within ~29 days using PowerShell/REST.
        • Supported only for deleted runbooks
          • Does not restore earlier published versions
  What is NOT supported:
  • Restoring a previous published version
    • Viewing published version history
      • Rolling back after publish
        • API / PowerShell / Portal‑based rollback. Azure Automation does not store historical published versions.
  Because rollback is not supported, Microsoft recommends external version control, such as:
  • Azure DevOps Repos
  • GitHub
  • Maintaining source‑controlled runbooks and importing them into Automation

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin