An incomplete wrapper for AZ CLI

All this Action does is wrap the az CLI—what’s the point? It only supports a subset of the functionality that `az` already provides, so why would anyone use this instead of just running az directly? I don’t see any real benefit.

The sensible approach would be for the Action to interact directly with Azure’s API, rather than just piggybacking on a tool that users can already invoke without adding this extra noise.

The issue does not name any files, tests, or entry points. Start by locating the Action's existing az CLI wrapper and reviewing how Azure API interaction would replace it; done would require an agreed scope and a direct Azure API implementation, but the issue does not define either.

Written by the indexing model from the issue text.