After you have synchronized the data, the integration of the Azure Data Lake Storage file system is completed, and the resulting assets are available in the domain that was specified in the crawler.
Warning Do not move the assets to another domain. Doing so may lead to errors during future synchronizations.
Tip ADLS synchronization relies on UUIDs.
Note In case of a partial synchronization caused by a temporary communication issue, the status of the assets that cannot be synchronized is set to Missing from source. Their previous status is restored, if they are found in the source system during the next fully successful synchronization.
By default, the assets are shown in a plain list, but you can enable a multi-path hierarchy to show it in a tree structure. The resulting assets depend on whether you use Microsoft Purview.
Synchronization results without Microsoft Purview
For the best result, use the following relations when you define a multi-path hierarchy:
- File Storage contains File Container
- File Container contains File Container
- Directory contains Directory
- File Container contains File
Synchronization results with Microsoft Purview
For the best result, use the following relations when you define a multi-path hierarchy:
- File Storage contains File Container
- File Container contains File Container
- Directory contains Directory
- File Container contains File
- File contains Table
- Table contains Column
Synchronized metadata per asset type
This table shows the metadata for each ADLS asset type.
| Asset type | Synchronized metadata |
|---|---|
| File storage |
|
| ADLS File System |
|
| ADLS Storage Account |
|
| ADLS Container |
|
| Directory |
|
| File |
|