Skip Ribbon Commands
Skip to main content

How does UploaderWiz overcome Microsoft restrictions to Azure container names?

Last Update: 7/21/2017 11:32 AM
This article has been moved to our new Help Center. Please update your bookmarks.

How does UploaderWiz overcome Microsoft restrictions to Azure container names?

Answer:

Azure containers cannot contain many special characters; examples include spaces and uppercase characters. 

To overcome these restrictions, the UploaderWiz utility includes code to filter out all illegal characters for the container name, and then uses the converted name, when creating the container on Azure. For example, a home directory named John Smith will be converted to johnsmith.

The UploaderWiz utility also contains code to handle home directory names that do not meet the  character length requirements for Azure containers. For example, if a home directroy is named "de" or "es" then it will not meet Azure container name requirements; these must be at least three (3) characters long. In those cases, UploaderWiz utility will prepend the name with "bt-"; so those names will become "bt-de" and "bt-es". Note: For this reason, it is important to check the name of the container within Azure, and then set the MigrationWiz project Advanced Option for the container name to match the Azure container.

For this reason, the container name may not always match the home directory name on the Source file server. Therefore, it is important to check the container name in Azure before setting the MigrationWiz project Advanced Option for Container name for a home directory to OneDrive for Business migration project. (In the example above, the MigrationWiz container name should be set to johnsmith, not John Smith). If the container name in MigrationWiz Advanced Options does not match the container name in Azure, the migration will not find any files in the container because it will be looking for the wrong container name.

In some rare cases, the entire folder and file name for the home directory could be entirely made up of special characters. In such cases, the discovery by the UploaderWiz utility will fail. This will be reported in the command line interface, and in the log files, which can be located under this directory:  %LOCALAPPDATA%\BitTitan

 

The log file will contain information similar to the data below: (Note: In this example, the home directory name was @@@####)

-----------------------------------------------

UploaderWiz Error: 0 : 2016-07-21 13:00:21.009 -07:00 [Error] Failed to execute
System.Exception: Cannot create container names for the following folder names:
  @@@####

Please review the Azure Naming Convention Rules for container names:
  https://msdn.microsoft.com/library/dd135715.aspx
  ---------------------------------------------

In such cases, the home directory name on the file server should be changed to a format that meets Microsoft guidelines. Those guidelines are stated here.

Here is how UploaderWiz command line will display the error:

special char error message.png 

Once the home directory name has been changed in compliance with Microsoft guidelines, the upload should be repeated, and the migration process continued as per the migration guide.‚Äč

Note: If the container name in Azure has been changed to meet Microsoft restrictions, then the MigrationWiz project Advanced Option for container name needs to match the adjusted container name in Azure. If following steps within migration guides that use PowerShell scripts for automation, then these scripts will call the name change algorithm within the script, and then automatically add the adjusted container name to the MigrationWiz project Advanced Option for container name.