Release notes for Cloud Manager 2025.8.0 in ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service release-notes
Learn about the release of Cloud Manager 2025.8.0 in AEM (ÃÛ¶¹ÊÓƵ Experience Manager) as a Cloud Service.
See also the current release notes for ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service.
Release dates release-date
The release date for Cloud Manager 2025.8.0 in AEM as a Cloud Service is Thursday, August 7, 2025.
The next planned release is Thursday, September 4, 2025.
What’s new what-is-new
-
Edge Delivery Services license can be included in a HIPAA program in a self-service manner
Organizations with healthcare or sensitive data requirements can now use Edge Delivery Services in a self-service manner, enabling HIPAA compliance to meet strict regulatory standards.
-
BYOG is now available for Edge Delivery Services
Cloud Manager now lets you configure external Git repositories, enabling flexible code-management workflows. It also lets you pull code from a chosen branch directly in the Cloud Manager UI, reducing manual repository tasks. See Configure Edge Delivery site to use an external Git repository
-
Automated provisioning for the new Forms Add‑on
Sites-only customers often need a lightweight, low-cost way to build marketing forms. The new AEM Forms Sites Add-On meets that need by adding limited Forms features to a Sites program. It also creates a clear upgrade path to the full AEM Forms offering.
The add-on:
-
Attaches to a Sites program and deploys alongside it—no separate Forms program or entitlement.
-
Targets simple marketing-form use cases.
-
Appears in the Solutions & Add-ons list during Production Program creation or Production Program edit, only when the IMS org holds available Forms add-on licenses.
For more information, see Create a production program.
-
Beta programs private-beta-program
Participate in Cloud Manager’s beta programs to get exclusive access to upcoming features before their general release.
The following opportunities are currently available:
One-click rollback for pipeline deployments one-click-rollback
Quickly revert to a previous deployment if the latest customer source code is not working as expected—no need to rerun the full pipeline or manually revert commits.
In the Restore previous code deployed dialog box, review the currently deployed version and the version you want to restore, then click Confirm.
Cloud Manager rolls the environment back to the earlier build, keeps content and configuration intact, and marks the environment Restoring until deployment completes.
If you are interested in testing this new feature and sharing your feedback, send an email to restorecode@adobe.com from your email address associated with your ÃÛ¶¹ÊÓƵ ID.
See Restore the Previous Code Deployed in AEM as a Cloud Service.
See also Content Restore in AEM as a Cloud Service.
Specialized Testing Environment specialized-test-environment
Cloud Manager now supports the addition of a new environment type called Specialized Testing Environment. The environment is designed to help teams validate features under near-production conditions before going live. This environment type is distinct from Production + Stage, Development, or Rapid Development environments and offers a focused space for running advanced validation scenarios.
Recent enhancements
- You can now configure a Specialized Testing Environment on a non-production pipeline through a simpler, more intuitive workflow. The streamlined setup speeds completion and reduces configuration errors.
- Copy Content is now supported in Specialized Testing Environments. You can now run Copy Content safely in isolated testing environments that mirror Production.
See Add a Specialized Testing Environment.
If you are interested in testing this new feature and sharing your feedback, send an email to grp-earlyadopter_cs_advtestenvironment@adobe.com from your email address associated with your ÃÛ¶¹ÊÓƵ ID.
Bring Your Own Git (BYOG) gitlab-bitbucket-azure-vsts
Customers can now onboard their Azure DevOps Git repositories into Cloud Manager, with support for both modern Azure DevOps and legacy VSTS (Visual Studio Team Services) repositories.
- For Edge Delivery Services users, the onboarded repository can be used to sync and deploy site code.
- For AEM as a Cloud Service and ÃÛ¶¹ÊÓƵ Managed Services (AMS) users, the repository can be linked to both full-stack and frontend pipelines.
Support for additional pipeline types and pull request validation through code quality pipelines is coming soon.
See Add external repositories in Cloud Manager.
Frequently asked questions about BYOG
IP Allow lists continue to work?IP Allow lists continue to work as usual. However, if the external Git repository is protected by a firewall, the necessary ÃÛ¶¹ÊÓƵ IP addresses must be added to the allow list.https://gitlab_dedicated_url.com/path/repo-name.git, which differs from the example in the documentation.https://git-vendor-name.com/org-name/repo-name.git).Manage Access Tokens manage-access-tokens
Use Manage Access Tokens in Cloud Manager to view, rename, and delete access tokens associated with external BYOG repositories, such as GitHub Enterprise, GitLab, Bitbucket, and Azure DevOps.
See Manage Access Tokens.
Add Edge Delivery Config Pipeline add-eds-pipeline
Config Pipelines are now supported for sites built with Edge Delivery Services, expanding this capability beyond just Cloud Service environments. You can use Config Pipelines to manage settings such as traffic filtering rules and Web Application Firewall (WAF) configurations, where applicable. See Supported Configurations.
Recent enhancement
-
Edge Delivery Services pipelines now display Configuration in the Deployed Code column, enabling instant identification of configuration-only deployments.
-
Cloud Manager shows Add Edge Delivery Pipeline once a program contains at least one Edge Delivery Services site and one mapped domain. Otherwise, the option appears disabled, and a tooltip explains missing requirements.
-
The Edge Delivery tab shows a new Edge Delivery pipelines widget that lists each pipeline’s Name, Status, Repository, and Branch.
-
The Filters panel adds a Delivery Type section; includes Edge delivery and Publish delivery checkboxes.
Bug fixes
- Pipelines now deliver variables only to the active Edge Delivery Services domain configuration, skipping any configuration removed during pipeline recreation.
- Pipeline execution now starts reliably; fixed an issue where some pipelines failed to start due to internal resource handling errors.
- Content Copy validates Cloud Manager permissions and blocks starts by users lacking Deployment Manager or Administrator rights.