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

Learn about the release of Cloud Manager 2025.11.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.11.0 in AEM as a Cloud Service is Thursday, November 6, 2025.

The next planned release is Thursday, December 4, 2025.

What’s new - Experience Hub experience-hub-whats-new

  • Simplified access to Experience Hub

    User role selection was removed and a guide added for Preset selection (Content Author, Asset Librarian, Admin & IT).

  • Announcements and Product updates

    You can switch and iterate between the available announcements, but also dismiss them.

  • Recents

    Added support for additional pages and resources, including page editor, assets, programs, and pipeline execution details, security pages.

  • Programs list

    Showing the AEM Cloud Manager programs in your organization with quick access into the Cloud Manager details page.

  • AEM Guides

    Quick action and Shortcut for the Authoring Environments that have AEM Guides add-ons enabled.

What’s new - Cloud Manager cloud-manager-whats-new

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.

Edit Non-Production Pipeline dialog box showing the two Build Strategy options which are Full Build and Smart Build
Edit Non-Production Pipeline dialog box showing the two Build Strategy options which are Full Build and Smart Build.

In the Add/Edit Pipeline dialog box, under the Source Code tab, a new Build Strategy section lets you choose one of the following build options:

  • Full Build — builds all modules in the repository on every run.
  • Smart Build — builds only modules that changed since the last commit, which shortens overall build time.

You control which pipelines use Smart build. During the beta, this option appears only for Code Quality and Dev Deployment pipelines.

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

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 November 2025 Cloud Manager release.

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