The

...

Azure Identity Connector can be configured by using the Aspire Admin UI.

...

The following  pages describe the necessary objects to be created:

• Connection
• Connector
• Seed

Bellow are the examples of how to create the Connection and the Seed. For the Connector please check this page.

Create Connection

...

1. Base Path: Path of the base directory to crawl. All the seeds will be prefixed with this value to form the full path. All the seeds will be prefixed with this value to form the full path
2. Ignore Symbolic Links: If enabled symbolic links will not be processed and links in the root items will cause an error.
3. Index directories: Enable to index the directories.
4. Scan recursively: Enable to scan discovered directories recursively.

...

1. Scan excluded items: Enable to force the scan of excluded directories, so child items within the scope can be found.
2. Include patterns: Patterns to match against document URL, if any of them match, the document will be included in the crawl.
3. Exclude patterns: Patterns to match against document URL, if any of them match, the document will be excluded from the crawl.

Credentials

Configure the Credentials to be used by the Connection object  when using the Aspire Admin UI.

Connection

Configure the Connection to be used by the Azure Identity Connector when using the Aspire Admin UI.

Connector

Configure the Azure Identity Connector properties when using the Aspire Admin UI.

Seed

Configure the Seed for the different Azure Identity Connectors when using the Aspire Admin UI

...

1. Static ACLs: These ACLs will be added to all of the documents.
   1. Name: Name of the ACL.
   2. Domain: Domain to which the ACL belongs to.
   3. Entity: Whether or not this ACL is for a group or a user.
   4. Access: Whether or not this ACL will have access to crawled files.

...

.