ÃÛ¶¹ÊÓÆµ

Release notes for Cloud Manager 2025.6.0 in ÃÛ¶¹ÊÓÆµ Experience Manager as a Cloud Service release-notes

Learn about the release of Cloud Manager 2025.6.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.6.0 in AEM as a Cloud Service is Thursday, June 5, 2025.

The next planned release is Thursday, July 10, 2025.

What’s new what-is-new

  • License dashboard now includes Edge Delivery Services license

    Edge Delivery Services license usage is now displayed in the License dashboard, providing you with clearer visibility into your entitlements and status.

    License Dashboard

    See License dashboard.

  • Edge Delivery site configuration updated

    Simplified the flow for adding an Edge Delivery site by requesting the Edge Delivery Origin instead of the Repository URL, making onboarding and setup faster and more intuitive

    Add Edge Delivery site dialog box

    See Add an Edge Delivery Site.

  • Pipeline favorites

    In this release, Cloud Manager introduces the ability to pin favorite pipelines, allowing you to mark specific pipelines as favorites so they appear at the top of the list on the Pipelines page. This enhancement makes frequently accessed pipelines easier to find and run.

    Pipelines marked as favorites Two pipelines marked as favorites.

    See Mark pipeline favorites.

Private beta program private-beta-program

Participate in Cloud Manager’s private Beta Program to get exclusive access to upcoming features before their general release.

The following private beta opportunities are currently available:

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.

See Add a Specialized Testing Environment.

Add environment dialog box with Specialized Testing Environment radio button selected

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) - now with support for Azure DevOps 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.

Add Repository dialog box

If you are interested in testing this new feature and sharing your feedback, send an email to Grp-CloudManager_BYOG@adobe.com from your email address associated with your ÃÛ¶¹ÊÓÆµ ID. Be sure to include which Git platform you want to use and whether you are on a private/public or enterprise repository structure.

Frequently asked questions about BYOG

Question
Answer
How can a project switch back to the ÃÛ¶¹ÊÓÆµ-managed Git repository if needed?
Switching back is straightforward. Update the pipelines to point to the ÃÛ¶¹ÊÓÆµ 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 ÃÛ¶¹ÊÓÆµ 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 ÃÛ¶¹ÊÓÆµ 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.

If you are interested in testing this new feature and sharing your feedback, send an email to Grp-CloudManager_BYOG@adobe.com from your email address associated with your ÃÛ¶¹ÊÓÆµ ID.

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.

Add Edge Delivery pipeline in Add Pipeline drop-down list Adding an Edge Delivery pipeline from the Program Overview page, Pipelines card.

Add Edge Delivery pipeline dialog box Add Edge Delivery pipeline dialog box.

If you are interested in testing this new feature and sharing your feedback, send an email to grp-aemeds-config-pipeline-adopter@adobe.com from your email address associated with your ÃÛ¶¹ÊÓÆµ ID.

Bug fixes

  • Sandbox environments previously marked as HIBERNATED no longer remain stuck in that state, allowing pipeline execution or deployment to proceed as expected.
  • AEM Cloud Manager now correctly maps Maven build failures caused by 409 errors (conflicts) when fetching customer artifacts to a customer-caused failure. This change improves error messaging by distinguishing between internal errors and issues related to customer environment setup.
recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab