Advanced Networking migration blocked in AEM Cloud due to unsupported namespace type
This article describes how to address situations where migration to Advanced Networking in Adobe Experience Manager (AEM) Cloud is blocked because environments were provisioned under an unsupported namespace type.
Description description
Environment
- Adobe Experience Manager (AEM) as a Cloud Service environment using Legacy Egress Proxy and requiring migration to Advanced Networking Dedicated Egress IP
Issue/Symptoms
- Migration to Advanced Networking is blocked for a specific environment.
- The networking resources required for Advanced Networking aren’t deployed for the affected environment.
- An attempt to migrate from Legacy Egress Proxy to Advanced Networking Dedicated Egress IP fails.
Cause
The environment was provisioned with a namespace type that isn’t eligible for Advanced Networking. The matching support investigation identifies the namespace types as Sandbox and Tenant. No supported process converts an existing environment’s namespace type; the environment must be recreated under a namespace type confirmed to be eligible, and its content and configuration must be migrated.
Resolution resolution
Follow the steps below to resolve the issue:
- Contact Adobe Support to confirm which environments have an ineligible namespace type and are blocked from migrating to Advanced Networking.
- After Adobe confirms the supported provisioning path and Advanced Networking eligibility, create replacement environments in Cloud Manager under the eligible namespace type. Confirm the replacement environment’s eligibility before migrating content or configuration.
- Use the Content Copy Tool to transfer mutable content from the affected environment to its replacement when the source and destination meet the tool’s supported flow requirements. For large content volumes, create smaller content sets and copy them sequentially. The tool copies content between Author services in the same Cloud Manager program; it doesn’t migrate custom code or environment-specific settings. Note: Content Copy supports defined environment flows; the usual flow is from a higher environment to a lower environment. Use Forward Flow only where it’s enabled and supported for the non-production environments. If your source and replacement environments don’t meet the supported flow requirements, ask Adobe Support which migration method applies. See The Content Copy Tool.
- Redeploy your custom code and configuration to the replacement environment as you would for a newly created environment.
- Recreate or reassociate environment-specific settings in the replacement environment, including environment variables, secrets, pipelines, domains, allowlists, and Advanced Networking associations.
- Test the replacement environment and confirm that its content, configuration, and integrations work as expected. Don’t delete the original environment until validation is complete.
- After validating the replacement, contact Adobe Support to coordinate migration from Legacy Egress Proxy to Advanced Networking Dedicated Egress IP. Don’t treat this migration as a standalone self-service enablement step.
- Repeat the replacement, migration, and validation process for additional affected environments as needed.
recommendation-more-help
experience-cloud-kcs-help-kbarticles