If youāve been following my recent posts on agentic DevOps, you know Iām a big believer in letting AI handle the repetitive parts of infrastructure reviews. But hereās the thing - most teams are still doing manual PR reviews for Bicep (and Terraform) files, catching the same anti-patterns over and over: āHey, you forgot to enable HTTPS-only on that storage account.ā āThis VM SKU is way oversized for a dev environment.ā āDid you check if this violates our naming conventions?ā
When I was still on the Microsoft Technical Trainer, delivering classes or presenting to Executives or speaking at conferences on AI (M365 Copilot, Foundry and Github Copilot primarily), apart from the technical conversations, one other question that always popped up, was āgreat scenario Peter, but what does this actually cost?ā And while GitHub Enterprise with GitHub Copilot provides great insights, not all developers use GitHub Copilot organization-wide.
Thatās where about 4 months back, I compiled a basic GitHub Copilot Consumption Viewer terminal app together, sharing simple metrics on tokens, LLMs used, etc.
If youāve been following me for a while, you know I write a fair bit about Microsoft DevOps, Azure, and lately GitHub Copilot. What you probably donāt know is that Iāve been leaning on VS Codeās agent mode to help me stay on top of whatās trending. It scans GitHub changelog feeds, filters for the DevOps-relevant bits, overall looks at top DevOps online resources - which now feels like a good topic for another blog post - and hands me a shortlist of topics worth exploring. That partās been working well for months. (And yes, I do miss the good old RSS-feeds, although I know some sites still have themā¦)
You know Iām always interested when something new ships that makes automation (DevOps, right!) easier, especially when it involves AI agents. So when two GitHub changelog entries landed on the same day last week, I knew they were made for each other. GitHub Agentic Workflows is now in public preview, and at the exact same time, agentic workflows no longer need a personal access token.
Let me explain why this matters, what an agentic workflow actually looks like, and why ditching the PAT is a genuinely good security win.
Over the last few weeks, Iāve been deep into building (even more)custom agents for my day-to-day job and the broader content team Iām in. One thing that kept bugging me was the manual wiring, where you have to point each agent to the right MCP servers, skills, and tools. Itās a lot of YAML editing and context window planning. Apart from the time, effort and testing that is still required when authoring your own custom VSCode Agents and skills.
If youāve followed this blog for a while, you know it runs on Hugo, a fantastic static site generator that turns a folder of Markdown files into a fast, fully static website. For the past couple of years that site has been hosted on Azure Static Web Apps, with an Azure DevOps pipeline doing the heavy lifting of compiling Hugo and publishing the output.
That setup served me well. After migration my old site templates and structure to a new one last February (see:https://www.pdtit.be/post/how-i-used-github-copilot-to-modernize-my-8-year-old-hugo-website/), I now wanted to consolidate everything into a single ecosystem and move the site to GitHub Pages, built and deployed by GitHub Actions. And because I wanted to see how far the tooling has come, I did the entire migration side-by-side with GitHub Copilot in agent mode inside VS Code.
If you have been following me for a while, you know Iām a big fan of Azure reliability. It was the main topic I presented on several years ago (in the early days of Azure - if that sounds right?) and also mapped with a big part of my job as Azure Architect, consultant and trainer.
I got amazed at the end of 2021 by Azure Chaos Studio, a service that allows you to inject faults against your Azure workloads (preferably production!), to make them more stable, more reliable.
I recently decided to give my 8 year old Hugo website a serious refresh. The trigger was simple: I still used the first Hugo theme I picked up 8 years ago, some content menu options didnāt actually do anything or were no longer relevant. Then I also had screenshots and other image files all over the place (5 different folder locations, duplicate image file names and alike).
Instead of doing this modernization and cleanup manually over a few weekends, I used GitHub Copilot as an active engineering partner to accelerate the full modernization journey.
Syncing MCP config from VS Code to Copilot CLI in a few simple steps.
Hey awesome people,
Over the last weeks, IĆ¢ā¬ā¢ve been jumping between VS Code and Copilot CLI a lot more than usual. One thing kept annoying me: my MCP setup was perfect in VS Code, but I had to keep tweaking pieces again in CLI.
If that sounds familiar, good news: if you already have MCP servers working in VS Code, you can reuse most of that setup in GitHub Copilot CLI.
In this post, I want to share my review of Azure for Developers (Third Edition) by Kamil MrzygĆ āĆĀ³d, published by Packt Publishing and available on Amazon as well as other e-book subscription platforms.
This definitive guide focuses on creating secure, scalable Azure apps with GenAI, serverless, and DevOps pipelines, making it an essential resource for developers looking to build modern cloud-native applications on Azure with the latest technologies.All Posts
Cookie Consent
We use cookies to enhance your browsing experience and analyze site traffic.
Cookie Preferences
These cookies are required for the website to function and cannot be disabled.
These cookies help us understand how visitors interact with our website.
These cookies enable features like comments and embedded content.