DocumentationAEM as a Cloud ServiceUser Guide

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

Last update: Thu Jan 22 2026 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 2026.1.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 2026.1.0 in AEM as a Cloud Service is Thursday, January 22, 2026.

The next planned release is Thursday, February 5, 2026.

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

  • Configuration pipelines now support managed secrets

    Users can now add and manage secrets directly in Cloud Manager configuration pipelines. These secrets securely override values in the pipeline configuration spec and support flexible, environment-specific deployments.

    View/Edit variables option on the drop-down menu for a selected pipeline
    View/Edit variables option on the drop-down menu for a selected pipeline.

    Variables Configuration dialog box Variables Configuration dialog box.

  • Improved stability, performance, and reliability

    This release includes optimization and maintenance updates that improved the stability, performance, and reliability of Cloud Manager.

Beta programs private-beta-program

Participate in Cloud Manager’s beta programs to get exclusive access to upcoming features before their general release.

IMPORTANT
Beta releases may contain defects and are provided “AS IS” without warranty of any kind. Adobe has no obligation to maintain, correct, update, change, modify or otherwise support (by way of Adobe Support Services or otherwise) the beta releases. Adobe advises customers to use caution and not rely on the correct functioning or performance of beta releases, or on any accompanying documentation or materials. Features and APIs in beta are subject to change without notice. Accordingly, any use of the beta releases is entirely at the customer’s own risk.

See also AEM Beta programs

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.

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

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