Building tools is never really finished. You ship something, people use it, and reality hands you a list of things you did not anticipate. This update is that list, worked through.
Azure Runbook Workbench just got a meaningful round of improvements : less about adding features, more about making what is already there actually dependable.
Modules That Actually Land
Deploying local PowerShell modules to Azure Automation sounds straightforward until you hit the async nature of the import process. You push a module, the blob is already gone, and Azure quietly tells you it found nothing to import. Frustrating, and hard to reproduce consistently.
That race condition is fixed. The pipeline now polls Azure Automation’s provisioning state after each module import and only cleans up the staging blob once the operation has settled. No more phantom failures mid-deployment.
The rest of the local module flow got tidied up too. A temporary staging storage account is created automatically when needed : no manual setup, no extra role assignments : and it disappears cleanly when the work is done. The whole thing is more self-contained now, which means fewer moving parts to configure before you can get anything running.
A Proper Publish Path
Until now, publishing the extension to the Marketplace involved a few too many manual steps. That is sorted. There is now a GitHub Actions workflow for publishing, plus a script you can run locally when you want to do it outside of CI. The publisher metadata in package.json is updated, the banner image is converted from SVG to PNG (the Marketplace is particular about that), and the whole process is repeatable.
It is the kind of infrastructure work that is invisible when it goes well, which is exactly the point.
Documentation That Reflects Reality
The docs had accumulated some rough edges : hardcoded local paths, missing pieces of the workspace structure, commands described in ways that no longer matched what they actually did. All of that has been cleaned up.
The guides now cover the full deployment flow end to end, including how the pipeline orchestrates its sub-scripts and how the local module staging and cleanup cycle works. If you have been piecing things together from partial documentation, this should fill in the gaps.
This is the kind of update that does not always make for a dramatic announcement, but it matters. The extension is more reliable, better documented, and easier to publish going forward. If you have been using it and running into rough edges, now is a good time to pull the latest.
