I have an Azure Functions backend whose job, among other things, is serving a web app’s static files out of Blob Storage: JS bundles, fonts, icons, an index.html. Same files, same users, many times a day. And for a while, every single request did the same dumb thing: download the blob from …

I needed to host an internal handbook. Nothing fancy: a static site full of onboarding guides and how-tos, built with a static site generator into a folder of HTML, CSS, JS, and images. The one hard requirement: only signed-in employees get to see it. And that requirement quietly kills all the easy …

Every time I sit down to build a SharePoint provisioning engine, I hit the same dilemma: do I put everything into one big PnP template, or do I split it into many smaller ones — one per feature? Both approaches work. Both have real trade-offs. And for a long time I did not have a strong opinion …