Skip to main content
Level 1
Nov 19, 2026 5:43 AM UTC
Question

AJO Content Advisor shows “No repositories match the required enhanced-security (HIPAA) setting” for a non-healthcare PoC

Hi Community,

I am trying to integrate AEM Content Fragments with Adobe Journey Optimizer (AJO) for a non-healthcare PoC.

The AEM as a Cloud Service environment is available and I can successfully:

  • Access the AEM Author and Publish environments
  • Create and access Content Fragments
  • Access Content Fragment Models
  • Create a test Content Fragment in the AEM Author environment

However, when I try to select an AEM Content Fragment from AJO Content Advisor, no AEM repositories are displayed.

Instead, Content Advisor shows:

“No repositories match the required enhanced-security (HIPAA) setting.”

This is confusing because our PoC is not healthcare-related and does not involve PHI/HIPAA data.

Has anyone encountered this behavior?

Specifically, I would like to understand:

  1. Why would AJO Content Advisor require an enhanced-security (HIPAA) AEM repository for a non-healthcare use case?
  2. Could this indicate that Healthcare Shield / enhanced security is enabled at the AJO instance or organization level?
  3. Is there any additional AEM/AJO provisioning or configuration required before a standard AEM as a Cloud Service repository becomes available in Content Advisor?
  4. Can this requirement be controlled at the AJO sandbox level, or is it determined by the AJO instance/organization provisioning?
  5. If AJO is provisioned with Healthcare Shield, does the connected AEM environment also require AEM Extended Security for Healthcare, even when the specific PoC itself is non-healthcare?

The AEM Author and Publish environments are both accessible, so I am currently trying to determine whether this is a repository configuration issue or an AJO/AEM provisioning mismatch.

Any guidance on what configuration or entitlement I should verify would be helpful.

Thanks!

1 reply

SatheeskannaK
Adobe Champion, Community Advisor, UG Leader
Adobe Champion, Community Advisor, UG Leader
Nov 19, 2026 4:20 PM UTC

Hi ​@Giddy_mindee15 , I have some experience with AEM CF integration with AJO. Here are my thoughts,

1. Why would a non-healthcare PoC hit a HIPAA/enhanced-security requirement?

Adobe’s documentation on the AEM Content Fragment integration explicitly states that for healthcare customers, the integration is only enabled when both Journey Optimizer Healthcare Shield and Adobe Experience Manager Extended Security for Healthcare are licensed. This means that Content Advisor does not inspect the actual content of the Content Fragment for PHI. 

2. Does this indicate Healthcare Shield is enabled at the AJO org/instance level?

Likely, Yes. This is the most consistent explanation: your AJO seems to have Healthcare Shield and enhanced security turned on. Consequently, AJO now expects any connected AEM repository to have the matching Extended Security for Healthcare add-on.

3. Is there additional provisioning needed before a standard repo becomes available?

It’s all about the security add-on that complements both AEM and AJO.

4. Can this be controlled at the sandbox level, or is it org/instance-wide?

I believe that Healthcare Shield and Extended Security for Healthcare are both licensed, account-level add-ons, as per Adobe’s product description terms. My expectation is that these are provisioned at the organization level and not something that can be toggled per sandbox. Please reach out to Adobe CSM for more details.

5. If AJO has Healthcare Shield, does the connected AEM also need Extended Security for Healthcare, even for a non-healthcare PoC?

Yes, if AJO has healthcare shield enabled, connected AEMs also require extended security for healthcare.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/combine/aem/aem-fragments-gs
 

 

Translate
Thanks, Sathees