AEM firewall migration and IP address change: Adobe allowlisting requirements
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article describes how to manage firewall IP address changes for Azure environments in Adobe Experience Manager and clarifies Adobe’s allowlisting requirements.
Description description
Environment
Adobe Experience Manager (all versions)
Symptoms
A firewall migration in an Azure environment results in changes to both non-production and production IP addresses. There is a concern about whether the new IP addresses need to be allowlisted on Adobe systems to maintain connectivity and avoid service disruption. Outbound firewall rules for HTTPS are already in place for the relevant endpoints.
Cause
Adobe services are accessed via outbound HTTPS to specific hostnames, and static IP allowlisting is not required unless IP-based access controls are enabled in the Adobe Admin Console.
Resolution resolution
Follow the steps below to resolve the issue:
- Review Adobe’s network requirements: Adobe Experience Manager and related services require outbound HTTPS (TCP/443) access to specific hostnames, not static IP addresses. The required hostnames include
platform.adobe.ioandims-na1.adobelogin.com. Refer to the Adobe network endpoints documentation for the full list. - Check if your organization uses IP-based access controls in the Adobe Admin Console. If so, review and update the allowlist as needed. Refer to the documentation on restricting product access by IP address.
- No inbound allowlisting is required on Adobe’s side for customer outbound IP addresses for standard service access.
- Ensure outbound HTTPS access to the required Adobe hostnames is permitted from the new firewall IP addresses.
- No further action is required from Adobe unless IP-based access controls are in use.