Operations | Monitoring | ITSM | DevOps | Cloud

A practical guide to reducing SharePoint Online storage - trim version history, empty the recycle bins, clear the Preservation Hold Library, find your largest sites, and archive inactive content to cut the $0.20/GB overage bill.

Version history is often the biggest consumer of SharePoint storage. How automatic version limits work, why setting a limit does not trim existing versions, and the exact PowerShell to reclaim the space.

Four ways to identify which SharePoint sites and libraries are consuming your storage - the Active sites view, per-site Storage Metrics, PowerShell (Get-SPOSite), and the admin usage reports - plus what to do once you have found them.

Most cloud-native cost tools are built to find and address waste reactively. Underutilized nodes, oversized requests, and idle workloads are revealed in the utilization data, the fixes are well documented, and the initial savings these tools drive are very real. But what we’ve seen consistently across clusters is a different category of blocker, one that quietly prevents consolidation and strands capacity your autoscaler can never reach. They don’t surface in dashboards as obvious waste.

For the past couple of years, most conversations about AI in business have centered on adoption. Which tools should organizations deploy? Where can AI improve productivity? How quickly can it deliver value? Those questions still matter, but they are no longer the most difficult ones to answer. AI is now appearing across business applications, employee workflows, development environments, and customer-facing services.

Using JFrog CLI used to come with a catch. To run a build through it, you had to put it in front of the command. For example, jf npm install instead of npm install or jf mvn package instead of mvn package per the example below: npm install → jf npm install mvn package → jf mvn package Doing that once is easy enough.

A Terraform string is just a sequence of characters, but almost everything you write in HCL touches one: resource names, tags, file paths, generated policies, connection strings. Knowing how Terraform builds, combines, and templates strings will save you from some of the more confusing errors you'll hit in a growing configuration.