DocumentationAEM as a Cloud ServiceUser Guide

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

Last update: Wed Jun 11 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.5.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.5.0 in AEM as a Cloud Service is Thursday, May 8, 2025.

The next planned release is Thursday, June 5, 2025.

What’s new what-is-new

Configure the content source in one click for Edge Delivery Services

Adobe Experience Manager (AEM) Edge Delivery Services allows content delivery from multiple sources such as Google Drive, SharePoint, or AEM itself, using a fast, globally distributed edge network.

The content source configuration differs between Helix 4 and Helix 5. Learn the difference and follow the comprehensive configuration steps, examples, and validation instructions for both versions.

See Configure your content source.

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:

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

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

Bring Your Own Git - 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 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

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 Adobe 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 Bring Your Own Git

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).
recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab