The File System connector The Azure Identity connector will crawl content from the file system location. Azure identities (users and groups) from the specified Azure Active Directory
Panel | ||
---|---|---|
| ||
|
The File System connector can scan and fetch the directories and documents of a file systemAzure Identity connector will fetch identities from the specified Azure Active Directory and store them on a identity cache.
Info |
---|
This component has been officially tested on local Windows and Linux. |
For the File System Azure Identity connector to be able to crawl the Aspire Worker nodes must be run with an account with read access to the directory to crawlidentities from the Azure AD that corresponds to the domain specified in the connection, it needs that the specified credentials have enough permissions to read said identities from the directory.
The Aspire Worker worker nodes must be running in the same machine where the file system repository is located or at least have access in the case of a file share. able to reach the Azure AD specified in the connection.
Info |
---|
This component has been officially tested on local Windows and Linux. |
Name | Supported |
---|---|
Content Crawling | yesno |
Identity Crawling | noyes |
Snapshot-based Incrementals | yesno |
Non-snapshot-based Incrementals | noyes |
Document Hierarchy | yesno |
The File System Azure Identity connector has the following features:
The Azure Identity
The File System connector is able to crawl the following objects:
Name | Type | Metadata | Content Fetch & Extraction | Description | |||
---|---|---|---|---|---|---|---|
User | document |
| Folder | container |
| NA | The directories users of the file system. Each directory will be scanned to retrieve more directories or filesAzure AD. |
GroupFile | document |
| yes | The files contained by the directories in the crawled file system. |
The File System Connector has the following limitations:
The connector does not retrieve the acls of the crawled documentsgroups of the Azure AD. |
Info |
---|
Attributes for users typically contain the user GUID but may contain additional data. Attributes for groups typically contain their display name but may contain additional data. |