Unable to enable or use Brand Portal in lower (non-production) environments
You expect Adobe Experience Manager Brand Portal to be available in your Stage or Dev environments but find it enabled only for Production, or you see a staging Brand Portal URL that behaves like Production. This happens because Brand Portal is provisioned as a single tenant per IMS Org by default, and non-production tenants are not created automatically. Connecting multiple AEM environments to one Brand Portal tenant leads to mirrored content and unsupported behavior.
To fix the issue, confirm how many tenants exist for your IMS Org, validate the Brand Portal URL in use, and request a separate IMS Org and tenant if you require a dedicated non-production Brand Portal.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- AEM Managed Services
- AEM Brand Portal
Issue/Symptoms
- Stage or Dev AEM does not show the Brand Portal option, while Production does.
- Assets published from Stage do not appear in Stage or Production Brand Portal, and the staging URL aliases the Production tenant.
- A Stage Brand Portal domain appears but mirrors Production and does not function independently.
- A temporary or non-production Brand Portal is requested, but none exists.
Root cause
Brand Portal is provisioned as a single environment per IMS Org by default. This is a product-level licensing and provisioning constraint, not a configuration defect. Stage and Dev Brand Portal tenants do not exist unless an additional Brand Portal instance is purchased and provisioned in a separate IMS Org. Connecting multiple AEM environments to a single Brand Portal tenant leads to mirrored content and unsupported configurations.
Steps to reproduce
- Sign in to the Adobe Admin Console and go to Products. Look for Adobe Experience Manager Brand Portal – Brand Portal. You typically see only one Brand Portal entry.
- From Products
>Adobe Experience Manager Brand Portal - Brand Portal, select Go to Brand Portal and compare the tenant URL with any Stage or Dev URLs in use. - In AEM, go to Tools
>Deployment>Distribution>Publish to Brand Portal. A distribution agent (bpdistributionagent0) appears only where Brand Portal is correctly configured.
Resolution resolution
To resolve the issue:
- If no Stage or Dev Brand Portal exists, recognize that Brand Portal is provided as one tenant per IMS Org by default, and non-production tenants are not automatically provisioned.
- If a Stage URL mirrors Production, note that the Stage URL is not a separate tenant; it aliases Production. This is expected when only one Brand Portal tenant is provisioned and is not supported as an independent environment.
- Temporary Brand Portal instances cannot be created. If testing requires a separate environment, request a permanent non-production tenant instead.
- To obtain a permanent non-production Brand Portal tenant, provide the proposed IMS Org name, the Brand Portal system administrator name and email, and the region (NA, EMEA, or APAC). A new IMS Org and Brand Portal tenant are provisioned after licensing entitlement is confirmed.
- After the new tenant is created, in AEM go to Tools
>Cloud Services>AEM Brand Portal and create a configuration using the new tenant URL. The configuration should save successfully and the distribution agent should appear under Tools>Deployment>Distribution. - In the distribution agent view, select Test Connection and confirm the test package is delivered successfully. If it fails, review the error queue and the AEM error logs.
- Validate the fix: confirm you can sign in to the correct Brand Portal tenant, the tenant URL matches the expected environment, and the distribution agent shows a successful test connection with no persistent failures in the error queue.