The Problem: Manual Excel Updates Were Slowing Everything Down
Our cloud infrastructure team was growing fast. Every time a new Azure resource got spun up — a virtual machine, a storage account, a network interface — someone had to manually log into the portal, pull the details, and update a shared Excel Projects. It sounds manageable until you're doing it a dozen times a week and the report is already three days behind.
I was the one tasked with fixing this. The goal was straightforward on paper: set up an Azure Automation account that would detect when a new resource was created and automatically push that data into an Excel file. No manual steps, no lag, no missed entries.
What I Tried First
I started by exploring Azure Automation runbooks. I had a working understanding of PowerShell and had used it for basic Azure tasks before, so I figured I could piece this together with some documentation and trial and error.
I got a runbook running. It could pull resource data using the Az module and log output to the console. That part worked. But connecting the automation trigger — specifically using Azure Event Grid to fire the runbook on resource creation — and then having it write structured data into a live Excel file through the Microsoft Graph API was where things started to unravel.
The authentication flow between the Automation account's managed identity, the Graph API permissions, and the Excel Online endpoint required a level of configuration I hadn't worked with before. I spent two days troubleshooting token scopes and permissions errors before I accepted that this was going to take longer than I had.
Bringing in Outside Help
After hitting that wall, I came across Helion360. I explained exactly what I was trying to build — an Azure Automation runbook triggered by resource creation events, writing rows into an Excel file hosted on SharePoint via the Graph API. Their team understood the setup immediately and asked the right clarifying questions: which resource types to monitor, what data fields to capture, how the Excel file was structured, and whether we needed error handling for duplicate entries.
Within a day they had a working plan, and within a few days the solution was in place.
How the Final Setup Actually Worked
The completed solution used an Azure Automation account with a system-assigned managed identity. A PowerShell runbook was written to handle the Excel update logic — it called the Microsoft Graph API to append a new row to the target worksheet each time it was invoked. The runbook captured key resource metadata: resource name, type, resource group, subscription, location, and timestamp.
On the trigger side, an Azure Event Grid subscription was configured to watch for resource creation events across the subscription and route them to a webhook that fired the runbook. Role assignments were set correctly so the managed identity had the right permissions without over-provisioning.
Error handling was built in so that if the Graph API call failed, the runbook logged the error and retried rather than silently failing. The Excel file stayed clean and consistent.
What Changed After This Was Running
The difference was immediate. Resource data started appearing in the Excel report automatically, usually within a minute or two of a resource being created. The team stopped maintaining the report manually, and the data was actually more accurate because human delays and omissions were eliminated.
It also opened up a conversation about what else could be automated in our reporting workflow. If creation events could trigger updates, so could deletion or tag changes. The architecture was already in place to extend it.
The real lesson for me was that Azure Automation and PowerShell scripting are genuinely powerful tools, but the integration layer — managed identities, Graph API permissions, Event Grid routing — requires hands-on experience to get right without spending days in circles.
If you're working on a similar cloud automation setup and the integration pieces are holding you back, Helion360 handled exactly this kind of technical work and delivered a clean, production-ready solution without overcomplicating it. Learn more about Excel to PowerPoint automation and how expert help can accelerate your projects.