Deploy the Adobe Experience Manager Assets Microsoft 365 Copilot connector

The Adobe Experience Manager (AEM) Assets Copilot connector integrates AEM Assets content into the Microsoft 365 ecosystem, enabling Copilot and Microsoft Search to surface published assets. This article describes the steps to deploy and customize the connector.

Prerequisites

Before you deploy the Adobe Experience Manager Assets connector, make sure that you meet the following prerequisites:

• You must be the search admin for your organization's Microsoft 365 tenant.
• You have your organization's Adobe Experience Cloud instance author environment URL and publish environment URL:
  • Author URL format: https://author-p<PROGRAM_ID>-e<ENVIRONMENT_ID>.<REGION>.adobeaemcloud.com
  • Publish URL format: https://publish-p<PROGRAM_ID>-e<ENVIRONMENT_ID>.<REGION>.adobeaemcloud.com
• You have a technical account for Adobe Experience Manager Assets with credentials to access published assets and metadata. This account is a secure, service-based account for external access. For details, see Generating access tokens for server-side APIs.

Deploy the connector

To add the Adobe Experience Manager Assets connector for your organization:

1. In the Microsoft 365 admin center, in the left pane, choose Copilot > Connectors.
2. Go to the Connectors tab, and in the left pane, choose Gallery.
3. From the list of available connectors, choose Adobe Experience Manager Assets.

Set display name

The display name identifies references in Copilot responses and acts as a content source filter. You can accept the default display name or customize it to a name that users in your organization recognize.

For more information, see Enhance Copilot discovery of connector content.

Set instance URL

Provide both the author and publish environment URLs for your Adobe Experience Manager Assets instance.

Choose authentication type

The connector supports technical account authentication for Adobe Experience Cloud. Configure the technical account as described in Generate access tokens for server-side APIs.

Roll out

To validate the connector before deployment, use a staged rollout. To roll out to a limited audience, choose the toggle next to Rollout to limited audience and specify the users and groups to roll the connector out to. For more information, see Staged rollout for Copilot connectors.

Choose Create to deploy the connection. The connector starts indexing published assets immediately.

The following table lists the default values that are set.

To customize these values, choose Custom setup. For more information, see Customize settings.

After you create your connection, you can review the status in the Connectors section of the Microsoft 365 admin center.

Customize settings (optional) 

You can customize the default values for the Adobe Experience Manager Assets connector settings. To customize settings, on the connector page in the admin center, choose Custom setup. 

Customize user settings

Access permissions

Currently, only published assets from your AEM Assets are indexed. All data indexed using the Adobe Experience Manager Assets Copilot connector is visible to all Microsoft 365 users in your tenant, from Microsoft Search or Copilot.

User identity mapping 

The connector maps Adobe Experience Cloud user accounts to Microsoft 365 (Microsoft Entra ID) identities. If Adobe Experience Cloud users' emails match their Entra ID user principal names (UPNs), this mapping is automatic. If they differ, you can provide a mapping rule to map identities in Adobe Experience Cloud to identities in Microsoft 365. Mapping rules ensure that the system provides appropriate activity signal to Adobe Experience Cloud content in responses.

Customize content settings 

Content ingestion filters 

Content ingestion filters allow you to control which assets are indexed by defining inclusion and exclusion rules based on paths and metadata properties.

You can choose to include or exclude certain content paths.

Content paths that should be fetched Only exact paths are supported. A valid content path must contain at least two levels, with /content as the root path.

Content paths that should not be fetched Only support input Java regular expression for paths. Excluded paths take priority over included paths.

You can also set ingestion filters based on the value of metadata properties, including both standard and custom metadata properties:

1. Input the JSON path of the property.
2. Select an Operator from the dropdown (=, !=, In, Not In).
3. Enter the target value.

To find and verify the property path, see Query builder API.

1. Open the query builder debugger at http://<host>:<port>/libs/cq/search/content/querydebug.html.

2. Input the following query.

   p.limit=10  
   p.guessTotal=true  
   p.hits=full  
   type=dam:Asset  
   p.nodedepth=2  
   property=jcr:content/cq:lastReplicationAction  
   property.value=Activate
   

3. Choose search.

4. After the results are returned, choose JSON query builder link to see the JSON content with all properties.

   

5. Find the property and JSON path of the property. For example, the JSON path of the property dc:format is hits.jcr:content.metadata.dc:format.

   

Operators
The operator defines the type of comparison applied to a property during content filtering. The supported operators are:

• =: Equals
• !=: Not Equals
• In: Matches any value in a list
• Not In: Excludes any value in a list

Target values
Target values specify what the property should match.

Manage properties

To check available standard properties from your Adobe Experience Manager Assets, assign a schema to the property (define whether a property is searchable, queryable, retrievable, or refinable), change the semantic label, and add an alias to the property. The following standard properties are indexed by default.

To add more custom properties:

1. Select Add property.
2. Fill in the following fields: a. Property name b. Type c. JSON path
3. Define the schema (searchable, queryable, retrievable, or refinable).

Customize sync intervals 

The refresh interval determines how often your data is synchronized between the data source and the Adobe Experience Manager Assets connector index. Copilot connectors use two types of refresh intervals: 

• Full crawl: Default value is every day.
• Incremental crawl: Default value is every 15 minutes.

You can change the default values of the refresh intervals. For more information, see Guidelines for sync settings.

Related content

• Adobe Experience Manager Assets connector overview
• Troubleshoot issues with the Adobe Experience Manager Assets connector