Release notes for Cloud Manager 2026.7.0 in Adobe Experience Manager as a Cloud Service release-notes

Bring Your Own Git (BYOG) — secret-based authentication for Git clone

You can now authenticate Git clone requests to your Bring Your Own Git repository using the byogit secret that Cloud Manager generates, in addition to an IMS token. This functionality lets Edge Delivery Services customers use the same credential that helix-admin already stores for code sync. Existing IMS-authenticated clone workflows are unaffected.

See Authenticate git clone requests.

VPN Network Infrastructure — BGP routing and multiple connections
The Advanced Networking VPN network infrastructure API now supports BGP (Border Gateway Protocol) dynamic routing alongside the existing static routing. Teams can configure BGP per connection by providing the customer-side BGP Autonomous System Number and peering address; Cloud Manager handles route learning dynamically — no static prefixes required.

The previous limit of one VPN connection per infrastructure has also been removed. Multiple connections are now supported within the same infrastructure, and static and BGP connections can coexist. This gives enterprise networking teams more flexibility when designing VPN topologies for AEM Cloud Service environments.

Improved build performance with module caching
A new build model compiles only changed modules (rather than the entire repository) using module-level caching to improve build performance. It applies to production pipelines. You control which production pipelines use Smart Build.

For more information, see the following:

• About using Smart Build in a production pipeline and About using Smart Build in a non-production pipeline
• Add a production pipeline and Add a non-production pipeline.

Content Copy: Cross Program and Forward Flow
Cloud Manager Content Copy, which lets teams copy content between AEM environments without a deployment, includes two capabilities available to all programs. Cross Program support allows content to be copied across different Cloud Manager programs, not just within the same program. Forward Flow removes the directional restriction, allowing content to be copied from any environment to any other — including from lower environments upward.

Edge Delivery Services with AEM Authoring
You can now deliver sites using Edge Delivery Services while continuing to author content in AEM Author mode. Depending on your workflow preferences, you can choose from the following authoring approaches:

• Document-based authoring
• AEM-based authoring

Core credits not released when both prod-group environments complete soft delete concurrently. This issue has been resolved. Credits are now correctly released regardless of the order in which concurrent deletions complete. (CMGR-77845)

Content Hub credit orphaned after environment soft delete followed by hard delete. Cloud Manager now correctly releases the Content Hub credit when the associated environment is fully removed. (CMGR-77585)

aio cloudmanager:tail-log CLI command disconnects at log rotation instead of reconnecting. The command now reconnects automatically when a log rotation is detected. (CMGR-76557)

Go-Live complete dialog content not scrollable in Program Overview. The dialog box now scrolls correctly, ensuring all content is accessible regardless of screen size. (CMGR-76405)

Custom domain mapping fails on newly created RDE environments. After creating a new Rapid Development Environment (RDE), customers encountered the error, “Environment status is not valid for domain config change,” when attempting to add a custom domain mapping immediately after provisioning.
Cloud Manager now correctly reflects the environment’s ready state before any domain mapping is attempted. (CMGR-75904)

Deleting a DV certificate and recreating it for the same domain fails with “existing certificate” error. When customers deleted a domain-validated (DV) certificate and then tried to create a new one for the same domain, Cloud Manager returned the error “There’s an existing certificate that covers all the domains.” As a result, it blocked the new certificate from being issued. The deletion appeared successful in the UI but the certificate was not fully removed internally, leaving the domain locked. This issue is now resolved. (CMGR-72784)