Operations | Monitoring | ITSM | DevOps | Cloud

Eight buyer questions for SharePoint archiving 2026. Compares Microsoft 365 Archive, AvePoint Opus, Archive360 and Squirrel on data, Copilot, labels.

Machine learning models are not like other software artifacts. A single fine-tuned LLM can weigh 70 GB. A model family may share 95% of its weights across dozens of variants. When hundreds of developers, training jobs, and GPU clusters all need the same model at the same time, the infrastructure underneath needs to be built for it.

In November 2025, we introduced new triggers and workflows to Bitbucket Pipelines to help teams manage and scale complex CI/CD workflows. We later extended that foundation with additional event-based triggers for pipeline, deployment, and pull request events. We’re now extending that model with a new package-artifact-created trigger.

When we introduced native Pipelines authentication for Bitbucket Packages, we made it easier to publish artifacts from CI/CD without relying on personal credentials. Now we’re extending that integration further: package artifacts published through the Pipelines integration can display a Source Pipeline, making it easy to trace an artifact back to the pipeline run that created it.

If your team bIf your team builds with Python or.NET, your packages have likely lived separately from your code, stored in a registry with distinct login, permissions, and billing. Starting today, they don’t have to. Bitbucket Packages now supports the Python Package Index (PyPI) and NuGet, integrating Python and.NET package management into the platform where your team writes code, reviews pull requests, and runs pipelines.

Eight new Azure recommendation types now scan your environment for idle, unattached, and over-provisioned resources, then tell you exactly what to cut.

This is the first in a series we’re calling AI ROI Dispatches, where we share stories from CloudZero and our customers on tying AI spend to real business outcomes.

Retention policies apply to locations. Retention labels apply to items. Both live in Microsoft Purview, both retain content, and admins regularly use the wrong one. What each actually does and when to use which.

Feature flag migrations have a reputation problem. Ask anybody who’s been through one before and you’ll hear the stories, usually from someone still a little frustrated about a bad cutover, with a postmortem or two to show for it. The reputation is mostly undeserved. While the risks are real, they’re well understood and easily controlled. Getting a migration right doesn’t require a big coordinated effort.

Your developers install agent plugins every day: pulling from unmanaged GitHub repos, copying Cursor commands out of Slack, pointing Codex at a personal Git fork. Each of those is a new, uncontrolled distribution channel inside your software development lifecycle, and your platform team has zero visibility into any of it. A plugin is not a preference file. It is executable software, and right now it’s arriving on developer machines with no versioning, no provenance, and no audit trail.