I built a small local tool to run everyday Azure operations with the credentials of a service principal, without opening the portal. [One sentence on why you built it, in your words.] It runs on your machine, either as a web app on localhost or as a Windows desktop app (.NET 8, Blazor). It has pages for VMs, App Service, Function Apps, Key Vault, AKS, Storage, SQL, App Insights, Log Analytics, networking, role assignments, the activity log and Resource Graph queries. There is also a PowerShell terminal already signed in with the active service principal, with kubectl and helm helpers for AKS. Some details: The client secret is encrypted with Windows DPAPI. A connection can be exported to a passphrase-protected file. No telemetry. It only calls Microsoft endpoints: Entra ID, Azure Resource Manager, Graph and the data plane of the resource you open. The interface is in English and Italian. It is early, and so far only I have tested it, on development environments and a sandbox. Ten delete and revoke actions (NSG rules, role assignments, registry tags and a few more) are switched off in the code, because I never ran them on real resources. The README lists what I tried and what I did not. What would help: run it on a test subscription, tell me the minimum role each page needs, and tell me what breaks. Pull requests are welcome, including one that switches on a disabled delete after you tried it on a throwaway resource. MIT license. It is not affiliated with Microsoft.   submitted by   /u/Dependent_Ideal9870 [link]   [comments]