AEM Cloud Manager and Delivery in 2026: What's GA, What's Still Beta, and What to Actually Try
Most AEM Cloud Service discussion is about authoring and AI. The 2026 release notes also changed the DevOps and delivery side: build pipelines, secrets, observability, and the CDN layer. Below, each item is labeled by status (GA vs Beta), because several of the interesting ones are still Beta.
Shipped as GA in 2026
1. Managed secrets in configuration pipelines (Cloud Manager 2026.1.0, Jan 22, 2026). You can add and manage secrets directly in Cloud Manager configuration pipelines. These override config values for environment-specific deployments, so you don't have to keep per-environment secrets in the repo or hand-set them. The same item also appears in the 2026.2.0 notes.
2. AEM Edge Functions (listed as GA in the AEM CS 2026.8.0 notes). These run JavaScript at the Adobe-managed CDN, which Adobe positions as a way to reduce latency for personalization and dynamic content delivery. Check the current status in Adobe's docs before you plan around it. A search summary I saw elsewhere described Edge Functions as a Beta program, so the status may differ by listing or have changed. Any latency benefit also needs measuring on your own traffic.
3. Permission Management Agent (listed as GA in 2026.8.0). It audits effective ACLs and answers "who can do what on this content path." It also recommends least-privilege group assignments. If your permission model grew organically over years, this is a practical cleanup aid. Treat the recommendations as input to review, not as auto-approved changes.
Still Beta, so don't promise these to stakeholders yet
4. Smart Build / module caching (Beta, Cloud Manager 2026.1.0 and 2026.2.0). Smart Build compiles only modules that changed since the last commit, as an alternative to a Full Build. It's available for Code Quality and Dev Deployment pipelines during the beta. Adobe frames it as shortening build time. Whether that matters for you depends on your repo structure, so benchmark it before relying on it.
5. Canary Production Deployments (Beta, 2026.8.0). This tests production builds before live traffic reaches them, which could reduce the blast radius of a bad release. It's Beta, so check its limits before putting it on a production release checklist.
6. OpenTelemetry APM integration (Beta, 2026.8.0). AEM CS is moving from its built-in APM integration toward OpenTelemetry, an open, industry-standard approach to observability. If you rely on the current APM integration, track this migration now rather than when it becomes mandatory. I haven't confirmed a retirement date for the old integration, so check Adobe's docs for one.
7. AI-assisted troubleshooting (Beta or beta program, varies by tool). Replication AI Troubleshooting for queue issues is Beta in 2026.8.0. A Development Agent that helps diagnose pipeline failures, including the Code Scanning step, and a Cloud Manager MCP Server for driving Cloud Manager APIs from your IDE are also described in the release notes as beta programs. Since these are betas, test them on non-critical pipelines.
What's not new but still matters
The Cloud Manager pipeline model, its code quality gates, and the move of dispatcher configuration into your Git repo are all established features, not 2026 launches. The 2026 items build on them. Teams that still treat the pipeline as a black box will get less out of the Beta features above.
Bottom line
For most teams, managed secrets and a permissions audit are the lowest-risk wins today. Smart Build, canary deployments, and OpenTelemetry are worth piloting in a non-production environment, but they're Beta, so keep them out of your delivery commitments until they reach GA.
Has anyone tried Smart Build or Canary Deployments on a real pipeline? Build-time numbers before and after, repo size, and any limitations you hit would be useful to see here.