📄️ Calculate ancestors
This accelerator calculates and stores the source or target ancestors of CONTAINER and RECORD documents. The source ancestors are calculated by taking the objects with an empty source.parentIds array as a starting point. The target ancestors are calculated by taking the ROOT documents as a starting point.
📄️ Calculate hash
This accelerator calculates the hash (SHA-512) for the BINARY documents with a matching byteSize.
📄️ Calculate hierarchies
This accelerator calculates and stores the source or target hierarchies of CONTAINER and RECORD documents. The source hierarchies are calculated by taking the objects with an empty source.parentIds array as a starting point. The target hierarchies are calculated by taking the ROOT documents as a starting point.
📄️ Content Store Validator
This flow validates references between documents in the Content Store according to the structure of the Content Store as described in Content Store Structure.
📄️ Create Content Store batch
This flow helps you create Content Stores for your migration batches. For more information on migration batches please refer to the best practices
📄️ Deduplicate names
This accelerator deduplicates the target.name.systemName for RECORD and CONTAINER documents within each container. It does this by adding a underscore with a number at the end of the name. This ensures that all transformed hierarchies are unique. The flow does update the target.hierarchies of the object, but not for its children.
📄️ Extraction report
This accelerator creates an Excel report of the CONTAINER and RECORD documents in the Content Store. This accelerator will have the following columns out of the box:
📄️ Insights
Introduction
📄️ Load balancer
This accelerator flow will distribute the work of a flow over multiple workers. It will do this by splitting the work and assigning objects to the workers. The workers will then process the objects and report back to the load balancer. The load balancer will then assign the next object to the worker that reported back first.
📄️ Notifications
The notification accelerator flows let you send selected messages to email, Telegram, or Slack. They do not read stored Console logs. Instead, their Subscribe components listen for messages published by any flow in the same project.
📄️ Purview PII Scanner Insights
The Purview PII Scanner Insights accelerator loads the results of the on-premise Azure Information Protection (AIP) scanner into the Content Store for further processing with the Insights accelerator.
📄️ Remove invalid characters
This accelerator replaces invalid characters found in the target.name.systemName field of RECORD and CONTAINER documents. This is useful for ensuring that the target system does not encounter any incompatible characters that would cause issues in the load stage of the migration. The flow does update the target.hierarchies of the object, but not for its children.
📄️ Reports
This accelerator contains multiple report flows to support your migration process.
📄️ Retry flow
The retry flow allows you to retry parts of other flows if they have implemented the retry functionality. The retry flow will search for any failed messages and reinserts them into the flow configured at publish component. The receiving flow needs to have a Retry input.
📄️ Transformation
This accelerator contains multiple transformation flows that will help you kick-start your transformation. It contains flows that set the migration scope, transform the metadata, and handle long name and paths.