DocumentationAEM as a Cloud ServiceUser Guide

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

Last update: Fri Oct 10 2025 00:00:00 GMT+0000 (Coordinated Universal Time)
  • Applies to:
  • Experience Manager as a Cloud Service

CREATED FOR:

  • Admin

Learn about the release of Cloud Manager 2025.10.0 in AEM (Adobe Experience Manager) as a Cloud Service.

See also the current release notes for Adobe Experience Manager as a Cloud Service.

Release dates release-date

The release date for Cloud Manager 2025.10.0 in AEM as a Cloud Service is Thursday, October 2, 2025.

The next planned release is Thursday, November 6, 2025.

What’s new what-is-new

  • Dedicated stage-only and production-only deployment pipelines

    Cloud Manager now offers dedicated stage-only and production-only deployment pipelines, providing greater flexibility for managing deployments to staging and production environments independently. See Split Stage-Only and Production-Only Pipelines.

  • AEM Cloud Health Assessment Service

    Adobe introduces the AEM Cloud Health Assessment Service, an automated, non-invasive checkup tool that keeps your AEM as a Cloud Service environment optimized, secure, and aligned with best practices.

    This service does the following:

    • Scans environments to surface performance bottlenecks, inefficiencies, and potential risks.
    • Analyzes content structures (blueprints, live copies) and custom configurations.
    • Identifies outdated dependencies (AEM SDK, third-party libraries).
    • Flags code quality issues (improper annotations, inefficient patterns).
    • Delivers actionable guidance through dashboards such as Actions Center.
    • Supports proactive optimization through early issue detection and remediation.

    Teams can continuously monitor and improve their AEM environments for smoother performance, stronger security, and long-term maintainability.

    See Health Assessment for Production and Stage Environments.

  • Config Pipeline support

    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 CDN configuration, including traffic filter rules and origin selectors. See Supported Configurations.

    Edge Delivery config pipelines also support secrets through Cloud Manager pipeline variables.

    See Add Edge Delivery Pipeline.

  • Domain Mapping-CDN setup dialog box streamlined

    Cloud Manager has simplified the Map Domain to CDN flow to reduce confusion and speed configuration. The dialog box now emphasizes Adobe managed CDN (with a “Recommended” badge).

    Map Domain to CDN dialog box with Adobe managed CDN radio button selected .

    See Add a domain mapping.

    The dialog box also presents a single, concise checklist for the Other CDN provider card, focusing on instructional content with the following:

    • Point your CDN origin to publish-p<PROGRAM_ID>-e<ENV_ID>.adobeaemcloud.com.
    • Set Host/SNI to forward the original host.
    • Add X-AEM-Edge-Key (after deploying the key in Cloud Manager).
    • Set X-Forwarded-Host to your customer-facing domain.
    • Clear other X-Forwarded-* headers before reaching AEM.

    Map Domain to CDN dialog box with Other CDN provider radio button selected

    The accompanying footer provides two helpful links: sample configurations for major CDNs and a link to full documentation. A single confirmation button–I've Configured My CDN–completes the flow.

    See CDN in AEM as a Cloud Service.

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:

Experience Hub Extensibility and Customization exp-hub-extensibility

Experience Hub serves as your entry point to AEM, customized for your organization’s needs. Tell Adobe about your existing AEM UI extensions so they can help you enable them in Experience Hub with minimal effort.

Diagram of Experience Hub extensibility and customization workflow

Embed custom experiences in Experience Hub to extend and personalize your organization’s dashboard. In addition to Adobe’s built-in widgets, add your own using the UI Extensibility framework. Build JavaScript-based UI apps and surface them to your users to meet business-specific requirements and workflows.

Interested in the beta? Email beta_exphubextensibility@adobe.com with your Adobe OrgID and a short description of the customization you intend to create.

Faster builds with module caching quick-build-cm-pipelines

A new build model compiles only changed modules (rather than the entire repo) using module-level caching to shorten build times. It applies to code-quality, full-stack, and stage-only pipelines.

Interested? Email beta_quickbuild_cmpipelines@adobe.com with your Adobe OrgID and Program ID.

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.

Restore customer source code from the Environments card Environments card above showing the Restore > Previous code deployed option for a selected environment.

Restore previous code deployed dialog box
In the Restore previous code deployed dialog box, review the currently deployed version and the version you want to restore, then click Confirm.

Restoring activation
Cloud Manager rolls the environment back to the earlier build, keeps content and configuration intact, and marks the environment Restoring until deployment completes.

Source code version in use The Environment details view, as seen above, now also shows the active source-code version in use.

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 Adobe 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.

Add environment dialog box with Specialized Testing Environment radio button selected

NOTE
Adobe has closed beta access requests for Specialized Testing Environments, having reached a sufficient number of participants. The feature is now in preparation for general availability.

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 Adobe 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.

Add Repository dialog box

Frequently asked questions about BYOG

Question
Answer
How can a project switch back to the Adobe-managed Git repository if needed?
Switching back is straightforward. Update the pipelines to point to the Adobe repository and remove the external repository if it is no longer required.
Is it possible to configure different repositories for different environments (for example, non-production versus production) to allow testing in non-production first?
Yes, different repositories can be configured for separate environments. For example, the dev or code quality pipeline can point to an external repository while the production pipeline remains connected to the Adobe repository. Make sure that the sync job between the two repositories remains active during this configuration.
Do existing settings like IP Allow lists continue to work?
Yes, existing IP Allow lists continue to work as usual. However, if the external Git repository is protected by a firewall, the necessary Adobe IP addresses must be added to the allow list.
Do all GitLab repository URLs work? The repository URL in use follows the format https://gitlab_dedicated_url.com/path/repo-name.git, which differs from the example in the documentation.
Yes, any GitLab repository that supports API V3 or V4 is supported, including self-hosted GitLab URLs like the one described in Add external repositories in Cloud Manager (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.

Bug fixes bug-fixes

There are no significant bug fixes in the October Cloud Manager release.

recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab