I have worked with Azure Automation since the early days, and one thing kept bothering me: the development experience never really felt right.
Too much of the process ended up split between the Azure portal, local scripts, manual testing, and deployment steps living somewhere else. It worked, but it rarely felt like a proper development workflow.
read more ...
I have been preparing something special.
It has been quietly taking shape for a while now, and it comes from a frustration I have had for years.
Anyone who has spent serious time with Azure Automation knows the story: too much back and forth, too much portal dependency, too much friction between authoring, testing, debugging, and deployment.
We end up stitching together folders, scripts, manual checks, and half-working approaches when what we really want is a proper development experience.
That gap has bothered me for a long time.
I wanted something that treats runbooks like real source code.
Something workspace-first. Something Azure-connected. Something that feels closer to modern software engineering and much less like trial and error in a browser tab.
That gap has bothered me for a long time.
I wanted something that treats runbooks like real source code.
Something workspace-first. Something Azure-connected. Something that feels closer to modern software engineering and much less like trial and error in a browser tab.
read more ...
Managed identities provide an identity for applications to use when connecting to resources that support Azure AD authentication.
read more ...