There are scenarios in which you would like to utilize another method (for example, AZ Copy) to upload your Azure Turbo packages to Azure - the Defer Upload to Azure option is designed to provide you with that flexibility.
The option is only available when Enable Azure Turbo has been selected (User Provided Storage only) and configured, and you must specifiy a local file share location which has enough available disk space to accommodate the size of all combined packages.
When enabled, the Azure Turbo function will still read and create packages from the content in your source location, but rather than upload it immediately (or in parallel) the packages are saved to your local storage to processing at a later time. Once all packages have been created, you must then upload these files independent of the software. When all uploads are complete, use the software to queue the jobs to begin the import process.
Please review the steps below to properly enable and use the Defer Upload to Azure option:
1.Initiate the migration using the same method you perform when using Azure Turbo. (See the Azure Turbo Mode Migration section for more information)
2.Once successfully connected to your Azure storage account, check the Defer Upload to Azure option.
3.Click the Select button and choose a file location where the packages will be saved locally.
·During the process, two folders will be created for each package, one containing the content and a second containing the manifest files.
·Each package will be up to approximately 125MB in size (depending on the amount of content being migrated), so please remember that there must be enough available disk space to accommodate all the packages.
·The total number of packages and their average size depends entirely on the amount of content that was included with this specific migration. You will always have a minimum of 2 folders, but could have many, many more for larger migrations.
4.When the operation begins, you will observe the same migration process bar. After all packages have been created, you can choose to view the log file by selecting "View Log" from the Summary pop up window. This will open the Log Viewer window which displays the queued results.
5.Open the Azure Turbo Queue job list (See the Monitoring Azure Turbo Migration section on details about viewing the Azure Turbo Queue), all migrations that have been processed using the "Defer Upload to Azure" option will display a status of "Deferred".
6.At this time, you must now upload the content from your local drive to your Azure storage using your utility of choice.
NOTE: Job Status is not updated in real time, so you should select one or more jobs and choose the option "Reload Job Status" to view the current state.
7.After all the content from each folder has been successfully uploaded to the correct Azure storage container, refresh the Azure Turbo Queue job list again and the status should update from "Deferred" to "Pending".
8.Select one or more Pending jobs, right click and choose "Process Pending or Completed Jobs" to begin the import process.
9.As the job(s) become queued in Azure, the status will change to "Queued". Over time, each Queued job will begin processing and once it has completed, the status will switch to the final stage of "Completed" and the content should now be available in your destination location.
Microsoft is now making free Azure storage containers available for the purpose of migrating content into Office 365. If you are currently using Azure Turbo mode with your own Azure storage, you may continue to do so without interruption, or you may switch over to the Microsoft storage option.
With regards to migration performance and results, there is no difference between using either option.
The use of the Microsoft Provided Storage option has the following requirements or caveats:
·It requires the use of encryption. If you would like to use the Microsoft Storage option but it is disabled, please refer to the following section for additional steps: Alternate Framework
·The storage containers are only valid for 7 days. At the end of 7 days, all content in this Azure container will be deleted. This does not mean that the entire migration needs to be completed in 7 days, only that the individual packages that are imported (and their corresponding logs) will only remain in their specific storage containers for 7 days.
·You will not have access to the storage account name and key.
If you would like to use this option, simply select the "Enable Azure Turbo Mode" option in the Advanced section of the wizard and then choose "Microsoft Provided Storage".
By default, the content, manifest and log files associated to all Azure Turbo packages are stored in an unencrypted format within your Azure storage containers. The upload and transmission of this data is performed over a secure connection, however the data at rest is not encrypted.
There may be situations, regulations, or any number of reasons why you would like to increase the security around your Azure content by adding another layer of protection. For this purpose we now offer the ability to add encryption to your Azure Turbo upload - the encryption will apply to all content within your Azure containers including the content, all manifest files, and any logs that are generated.
In order to enable Azure Turbo Mode Encryption do the following:
1.Please be sure that no operations are currently in progress as the software will require a restart to complete.
2.Navigate to the Help tab, and select Profile Manager.
3.Select Global Variables from the left hand tab of the Profile Manager window.
4.Scroll down to the Advanced Options section located at the bottom. Click the check box located to the right of the "Encryption Azure" field, then click Apply.
NOTE: If you do not see this Encryption option in the list, please refer to the Alternate Framework section before you continue.
5.Close the Profile Manager Window. Restart the Essentials Application. After the software is restarted, you may proceed with your Azure Turbo based migration.
If you would like to verify the encryption, after any encrypted Azure Turbo migration has completed, connect to your Azure storage using your software of choice (i.e. Azure Explorer) and attempt to open any of your encrypted objects.
SharePoint uses three primary methods for categorizing content. The hierarchy of sites, lists and folders (which is similar to how file systems store files in folders), metadata (via content types and fields), and AutoTagging to tag or classify content for find-ability and filtering. The application has been designed to categorize content in bulk by leveraging one or all of these methods.
This section will walk you through the process of intelligently tagging content. Please refer to the section titled, Copy, Move, and Tag SharePoint, for additional information on moving or copying content into specific sites, lists, and folders.
1.Locate a list or library, containing the content you wish to classify, in the Navigator pane. Double-click on the list to load its contents into the Contents pane.
If the site containing your items or documents is not available in the Navigator pane, follow the instructions for Connecting to SharePoint in order to load it.
2.From the list of files located in the Contents pane, select all the files for tagging. Hold down the CTRL key to select multiple individual files or SHFT key to select multiple consecutive items.
3.Right-click on any of the selected files, and select the Tag option from the drop down menu. This will initiate the tagging wizard.
5.Once the tagging selections are made, press the Next button located at the bottom of the window. A summary screen will be generated asking you to confirm the operation. Press Finish to initiate the tagging. The application will complete the tagging process and provide a notification window.
·For the Migrator version of this wizard, users may select the "Create CSV File for Uploading, Tagging and Copying Files", which will create a CSV file that may be edited and used for tagging at a later time (see Copy and Tag SharePoint Items Using CSV).
·For Migrator version of this wizard, in the event any errors are thrown, you may reprocess any failed items after resolving the underlying issues.
·For lists with Content Approval enabled, an Approval Status field will be displayed. This field can be used to bulk approve/reject selected content.