Utilize network upload to import your arrangement's PST files to Microsoft 365

  • Article
  • 29 minutes to read

Here are the footstep-by-stride instructions required to utilize network upload to bulk-import multiple PST files to Microsoft 365 mailboxes. For frequently asked questions about using network upload to majority-import PST files to Microsoft 365 mailboxes, see FAQs for using network upload to import PST files.

Step 1: Copy the SAS URL and download AzCopy

Step 2: Upload your PST files to Microsoft 365

(Optional) Step 3: View a listing of the PST files uploaded

Pace 4: Create the PST Import mapping file

Step 5: Create a PST Import job

Step 6: Filter data and offset the PST Import job

You accept to perform Step one only one time to import PST files to Microsoft 365 mailboxes. After y'all perform these steps, follow Step ii through Footstep 6 each time you lot want to upload and import a batch of PST files.

Before you lot import PST files

  • You lot take to exist assigned the Mailbox Import Export role in Commutation Online to create import jobs in the Microsoft 365 compliance center and import PST files to user mailboxes. By default, this role isn't assigned to any role group in Exchange Online. Yous can add the Mailbox Import Export role to the System Management role group. Or you tin create a function grouping, assign the Mailbox Import Export role, and so add yourself as a member. For more information, meet the "Add a role to a function group" or the "Create a role group" sections in Manage part groups.

    In add-on to the Mailbox Import Export role, yous also accept to be assigned the Post Recipients office in Exchange Online. Past default, this function is assigned to the Organization Management and Recipient Management roles groups in Exchange Online.

    Tip

    Consider creating a new role group in Commutation Online that'south specifically intended for importing PST files. For the minimum level of privileges required to import PST files, assign the Mailbox Import Consign and Mail Recipients roles to the new function group, and then add members.

  • The but supported method for importing PST files to Microsoft 365 is to use the AzCopy tool, every bit described in this article. Y'all tin can't utilize the Azure Storage Explorer to upload PST files straight to the Azure Storage surface area.

  • Large PST files may bear upon the functioning of the PST import process. So nosotros recommend that each PST file yous upload to the Azure Storage location in Step 2 should be no larger than 20 GB.

  • This procedure involves copying and saving a copy of a URL that contains an access cardinal. This information will be used in Pace 2 to upload your PST files, and in Pace iii if you want to view a list of the PST files uploaded to Microsoft 365. Be sure to take precautions to protect this URL like you would protect passwords or other security-related information. For instance, you might salve it to a password-protected Microsoft Word document or to an encrypted USB bulldoze. See the More information section for an case of this combined URL and fundamental.

  • Yous can import PST files to an inactive mailbox in Microsoft 365. Y'all practice this past specifying the GUID of the inactive mailbox in the Mailbox parameter in the PST Import mapping file. See Step four on the Instructions tab in this commodity for information.

  • In an Exchange hybrid deployment, you can import PST files to a cloud-based archive mailbox for a user whose primary mailbox is on-bounds. You do this past doing the following in the PST Import mapping file:

    • Specify the electronic mail accost for the user's on-premises mailbox in the Mailbox parameter.

    • Specify the TRUE value in the IsArchive parameter.

      Come across Step four for more than information.

  • After PST files are imported, the retention hold setting for the mailbox is turned on for an indefinite duration. This ways that the memory policy assigned to the mailbox won't be processed until you turn off the retention concur or fix a date to turn off the agree. Why do nosotros do this? If letters imported to a mailbox are onetime, they might be permanently deleted (purged) because their retention period has expired based on the retention settings configured for the mailbox. Placing the mailbox on retention hold gives the mailbox possessor time to manage these newly imported messages or give you time to modify the retention settings for the mailbox. See the More than information section in this commodity for suggestions about managing the retentiveness hold.

  • By default, the maximum message size that can exist received by a Microsoft 365 mailbox is 35 MB. That'southward because the default value for the MaxReceiveSize holding for a mailbox is set to 35 MB. All the same, the limit for the maximum message receive size in Microsoft 365 is 150 MB. So if y'all import a PST file that contains an item larger than 35 MB, the Microsoft 365 Import service we will automatically change the value of the MaxReceiveSize property on the target mailbox to 150 MB. This allows letters upwards to 150 MB to exist imported to user mailboxes.

    Tip

    To place the message receive size for a mailbox, you tin run this control in Exchange Online PowerShell: Become-Mailbox <user mailbox> | FL MaxReceiveSize.

  • For a high-level overview of the PST Import process, see How the import process works section in this article.

Step 1: Copy the SAS URL and download AzCopy

The outset footstep is to download the AzCopy tool, which is the tool that y'all run in Footstep 2 to upload PST files to Microsoft 365. You also re-create the SAS URL for your organization. This URL is a combination of the network URL for the Azure Storage location in the Microsoft deject for your organization and a Shared Access Signature (SAS) key. This key provides you with the necessary permissions to upload PST files to an Azure Storage location. Exist certain to have precautions to protect the SAS URL. It'due south unique to your organisation and will exist used in Step 2.

Important

To import PST files using the network upload method and command syntax documented in this article, y'all must use the version of AzCopy that tin exist downloaded in pace 6b in the post-obit process. You can as well download that same version of AzCopy from here. Using a different version of AzCopy isn't supported.

  1. Get to https://compliance.microsoft.com and sign in using the credentials for an administrator account in your organisation.

  2. In the left pane of the Microsoft 365 compliance middle, click Information governance > Import.

    Note

    You accept to be assigned the advisable permissions to access the Import folio in the Microsoft 365 compliance center. Meet the Before you brainstorm section for more data.

  3. On the Import tab, click Add Icon. New import job.

    The import task wizard is displayed.

  4. Type a name for the PST import task, and so click Next. Use lowercase letters, numbers, hyphens, and underscores. You can't employ uppercase letters or include spaces in the name.

  5. On the Practice you want to upload or ship information? page, click Upload your data and and then click Next.

    Click Upload your data to create a network upload import job.

  6. On the Import information page, do the post-obit two things:

    Copy the SAS URL and download the AzCopy tool on the Import data page.

    1. In step 2, click Show network upload SAS URL. Subsequently the SAS URL is displayed, click Copy to clipboard then paste information technology and salvage it to a file so you can access information technology subsequently.

    2. In step three, click Download Azure AzCopy to download the AzCopy tool to your local estimator. This version of AzCopy is only an executable file, so there'southward nothing to install.

    Note

    You can exit the Import data page open up (in case yous demand to copy the SAS URL over again) or click Cancel to shut information technology.

Step 2: Upload your PST files to Microsoft 365

Now you're ready to use the AzCopy tool to upload PST files to Microsoft 365. This tool uploads and stores PST files in a Microsoft-provided Azure Storage location in the Microsoft cloud. As previously explained, the Azure Storage location that you upload your PST files to is located in the same regional Microsoft datacenter where your organization is located. To complete this stride, the PST files take to be located in a file share or file server in your arrangement or in an Azure Storage location managed by your organisation. The PST storage location is known every bit the source location in this process. Each time y'all run the AzCopy tool, you can specify a dissimilar source location.

Annotation

As previously stated, each PST file that you upload to the Azure Storage location should be no larger than xx GB. PST files larger than 20 GB may impact the functioning of the PST import procedure that you start in Step half-dozen. Too, each PST file must have a unique proper noun.

  1. Open a Command Prompt on your local figurer.

  2. Go to the directory where y'all downloaded the azcopy.exe file in Step 1.

  3. Run the post-obit control to upload the PST files to Microsoft 365.

                      azcopy.exe copy "<Source location of PST files>" "<SAS URL>"

    Important

    You tin specify a directory or an Azure Storage location as the source location in the previous command; you can't specify an individual PST file. All PST files in the source location will be uploaded.

    The following tabular array describes the azcopy.exe fields and their required values. The data you obtained in the previous step is used in the values for these fields.

    Field Clarification
    Source The first field specifies the source directory in your organization that contains the PST files that volition be uploaded to Microsoft 365. Alternatively, you tin specify an Azure Storage location as the source location of the PST files to upload.
    Be sure to surround the value of this field with double-quotation marks (" ").

    Examples:
    "\\FILESERVER01\PSTs"
    Or
    "https://storageaccountid.blob.core.windows.net/PSTs?sp=racwdl&st=2021-09-21T07:25:53Z&se=2021-09-21T15:25:53Z&sv=2020-08-04&sr=c&sig=xxxxxx"

    Destination Specifies the SAS URL that you obtained in Step 1.
    Be sure to surround the value of this parameter with double-quotation marks (" ").

    Note: If yous apply the SAS URL in a script or batch file, watch out for certain characters that need to exist escaped. For example, you have to alter % to %% and change & to ^&.

    Tip: (Optional) Y'all can specify a subfolder in the Azure Storage location to upload the PST files to. You lot do this past calculation a subfolder location (after "ingestiondata") in the SAS URL. The beginning example doesn't specify a subfolder. That means the PSTs are uploaded to the root (named ingestiondata) of the Azure Storage location. The second instance uploads the PST files to a subfolder (named PSTFiles) in the root of the Azure Storage location.

    Examples:
    "https://3c3e5952a2764023ad14984.blob.core.windows.net/ingestiondata?sv=2012-02-12&amp;se=9999-12-31T23%3A59%3A59Z&amp;sr=c&amp;si=IngestionSasForAzCopy201601121920498117&amp;sig=Vt5S4hVzlzMcBkuH8bH711atBffdrOS72TlV1mNdORg%3D"
    Or
    "https://3c3e5952a2764023ad14984.blob.cadre.windows.cyberspace/ingestiondata/PSTFiles?sv=2012-02-12&amp;se=9999-12-31T23%3A59%3A59Z&amp;sr=c&amp;si=IngestionSasForAzCopy201601121920498117&amp;sig=Vt5S4hVzlzMcBkuH8bH711atBffdrOS72TlV1mNdORg%3D"

    --recursive This optional flag specifies the recursive manner so that the AzCopy tool copies PSTs files that are located in subfolders in the source directory that is specified by the source field. The default value for this flag is true.
    Note: If you include this flag, PST files in subfolders will accept a different file pathname in the Azure Storage location after they're uploaded. You'll take to specify the verbal file pathname in the CSV file that you create in Step 4.
    --s2s-preserve-access-tier This optional flag is only required when the source location is a general-purpose v2 Azure Storage location that supports access tiers. For the PST Import scenario, there is no need to preserve the admission tier when y'all copy PST files from your Azure Storage account to the Microsoft-provided Azure Storage location. In this case, you can include this flag and use a value of false. You don't need to utilise this flag when copy PST files from a archetype Azure Storage account, which doesn't support access tiers.

For more information about the azcopy.exe copy command, see azcopy re-create.

Here's are examples of the syntax for the AzCopy tool using actual values for each parameter.

Example ane

This is an case for a source directory located on file server or local computer.

              azcopy.exe re-create "\\FILESERVER1\PSTs" "https://3c3e5952a2764023ad14984.blob.core.windows.cyberspace/ingestiondata?sv=2012-02-12&amp;se=9999-12-31T23%3A59%3A59Z&amp;sr=c&amp;si=IngestionSasForAzCopy201601121920498117&amp;sig=Vt5S4hVzlzMcBkuH8bH711atBffdrOS72TlV1mNdORg%3D"

Example 2

This is an example for a source directory located in a classic Azure Storage account with subdirectories.

              azcopy.exe copy "https://storageaccountid.blob.core.windows.net/PSTs?sp=racwdl&st=2021-09-21T07:25:53Z&se=2021-09-21T15:25:53Z&sv=2020-08-04&sr=c&sig=xxxxxx" "https://3c3e5952a2764023ad14984.blob.core.windows.net/ingestiondata?sv=2012-02-12&amp;se=9999-12-31T23%3A59%3A59Z&amp;sr=c&amp;si=IngestionSasForAzCopy201601121920498117&amp;sig=Vt5S4hVzlzMcBkuH8bH711atBffdrOS72TlV1mNdORg%3D" --recursive

Case 3

This is an case for a source directory located in a general-purpose v2 Azure Storage account. Access tiers aren't preserved when the PST files are uploaded.

              azcopy.exe copy "https://storageaccountid.blob.core.windows.net/PSTs?sp=racwdl&st=2021-09-21T07:25:53Z&se=2021-09-21T15:25:53Z&sv=2020-08-04&sr=c&sig=xxxxxx" "https://3c3e5952a2764023ad14984.blob.cadre.windows.net/ingestiondata?sv=2012-02-12&amp;se=9999-12-31T23%3A59%3A59Z&amp;sr=c&amp;si=IngestionSasForAzCopy201601121920498117&amp;sig=Vt5S4hVzlzMcBkuH8bH711atBffdrOS72TlV1mNdORg%3D" --s2s-preserve-access-tier=false

Later on yous run the command, status messages are displayed that prove the progress of uploading the PST files. A concluding status message shows the total number of files that were successfully uploaded.

Tip

Later on you successfully run the azcopy.exe re-create command and verify that all the parameters are correct, save a re-create of the command line syntax to the same (secured) file where you copied the data you obtained in Pace ane. And so y'all can re-create and paste this control in a Command Prompt each fourth dimension that you desire to run the AzCopy tool to upload PST files to Microsoft 365. The simply value you might take to change is for the source field. This depends on the source directory where the PST files are located.

(Optional) Pace 3: View a list of the PST files uploaded to Microsoft 365

As an optional step, you can install and use the Microsoft Azure Storage Explorer (which is a free, open-source tool) to view the list of the PST files that you've uploaded to the Azure blob. There are two good reasons to do this:

  • Verify that PST files from the shared folder or file server in your system were successfully uploaded to the Azure blob.

  • Verify the filename (and the subfolder pathname if you included one) for each PST file uploaded to the Azure hulk. This is helpful when yous're creating the PST mapping file in the next step because you accept to specify both the folder pathname and filename for each PST file. Verifying these names tin can help reduce potential errors in your PST mapping file.

The Azure Storage Explorer standalone application is generally available. You tin download the latest version using the link in the following procedure.

Important

You lot tin can't employ the Azure Storage Explorer to upload or change PST files. The simply supported method for importing PST files is to use AzCopy. Also, you can't delete PST files that yous've uploaded to the Azure blob. If you try to delete a PST file, you'll receive an error virtually not having the required permissions. Note that all PST files are automatically deleted from your Azure storage expanse. If there are no import jobs in progress, then all PST files in the ingestiondata container are deleted thirty days later the near recent import job was created.

To install the Azure Storage Explorer and connect to your Azure Storage area:

  1. Download and install the Microsoft Azure Storage Explorer tool.

  2. Start the Microsoft Azure Storage Explorer.

  3. On the Select Resources page in the Connect to Azure Storage dialog, click Blob container.

  4. On the Select Authentication Method page, select the Shared access signature (SAS) option, and then click Next.

  5. On the Enter Connectedness Info page, paste the SAS URL that yous obtained in Step ane into the box under Blob container SAS URL, and so click Next. After you lot paste the SAS URL, the box under Brandish name is autopopulated with ingestiondata.

  6. On the Summary folio, y'all tin review the connection information, and then click Connect.

    The ingestiondata container is opened. It contains the PST files that you uploaded in Step two. The ingestiondata container is located nether Storage Accounts > (Attached Containers) > Blob Containers.

  7. When you're finished using the Microsoft Azure Storage Explorer, correct-click ingestiondata, and then click Detach to disconnect from your Azure Storage area. Otherwise, you'll receive an mistake the adjacent time y'all try to attach.

Step 4: Create the PST Import mapping file

Later the PST files have been uploaded to the Azure Storage location for your organization, the next step is to create a comma-separated value (CSV) file that specifies which user mailboxes the PST files will be imported to. You'll submit this CSV file in the next step when you create a PST Import chore.

  1. Download a copy of the PST Import mapping file.

  2. Open or save the CSV file to your local reckoner. The following example shows a completed PST Import mapping file (opened in NotePad). Information technology's much easier to use Microsoft Excel to edit the CSV file.

                      Workload,FilePath,Proper noun,Mailbox,IsArchive,TargetRootFolder,ContentCodePage,SPFileContainer,SPManifestContainer,SPSiteUrl Exchange,,annb.pst,annb@contoso.onmicrosoft.com,FALSE,/,,,, Exchange,,annb_archive.pst,annb@contoso.onmicrosoft.com,True,,,,, Substitution,,donh.pst,donh@contoso.onmicrosoft.com,Fake,/,,,, Exchange,,donh_archive.pst,donh@contoso.onmicrosoft.com,True,,,,, Exchange,PSTFiles,pilarp.pst,pilarp@contoso.onmicrosoft.com,FALSE,/,,,, Commutation,PSTFiles,pilarp_archive.pst,pilarp@contoso.onmicrosoft.com,TRUE,/ImportedPst,,,, Exchange,PSTFiles,tonyk.pst,tonyk@contoso.onmicrosoft.com,FALSE,,,,, Substitution,PSTFiles,tonyk_archive.pst,tonyk@contoso.onmicrosoft.com,TRUE,/ImportedPst,,,, Exchange,PSTFiles,zrinkam.pst,zrinkam@contoso.onmicrosoft.com,FALSE,,,,, Substitution,PSTFiles,zrinkam_archive.pst,zrinkam@contoso.onmicrosoft.com,TRUE,/ImportedPst,,,,

    The showtime row, or header row, of the CSV file lists the parameters that will be used by the PST Import service to import the PST files to user mailboxes. Each parameter proper noun is separated past a comma. Each row under the header row represents the parameter values for importing a PST file to a specific mailbox. Yous need a row for each PST file that you want to import to a user mailbox. You can take a maximum of 500 rows in the CSV mapping file. To import more than 500 PST files, yous'll take to create multiple mapping files and create multiple import jobs in Footstep 5.

    Note

    Don't modify anything in the header row, including the SharePoint parameters; they will be ignored during the PST Import process. Also, be sure to replace the placeholder data in the mapping file with your actual data.

  3. Utilize the data in the following tabular array to populate the CSV file with the required information.

    Parameter Description Example
    Workload
    		Specifies the service that data volition be imported to. To import PST files to user mailboxes, employ Commutation.
    		Exchange
    FilePath
    		Specifies the binder location in the Azure Storage location that you uploaded the PST files to in Step 2.
    If you didn't include an optional subfolder name in the SAS URL in the /Dest: parameter in Step 2, leave this parameter blank in the CSV file. If you included a subfolder name, specify it in this parameter (run across the 2nd example). The value for this parameter is instance-sensitive.
    Either style, don't include "ingestiondata" in the value for the FilePath parameter.

    Of import: The case for the file path proper name must exist the same as the instance you used if y'all included an optional subfolder name in the SAS URL in the destination field in Step two. For case, if y'all used PSTFiles for the subfolder proper name in Step 2 and and then use pstfiles in the FilePath parameter in CSV file, the import for the PST file volition neglect. Be sure to utilize the same case in both instances.

    		(leave blank)
    Or
    PSTFiles
    Name
    		Specifies the name of the PST file that will be imported to the user mailbox. The value for this parameter is case-sensitive. The file proper name of each PST file in the mapping file for an import chore must be unique.

    Important: The case for the PST file name in the CSV file must exist the same equally the PST file that was uploaded to the Azure Storage location in Step 2. For example, if y'all use annb.pst in the Proper noun parameter in the CSV file, but the name of the actual PST file is AnnB.pst, the import for that PST file will fail. Be sure that the name of the PST in the CSV file uses the same instance as the actual PST file.

    		annb.pst
    Mailbox
    		Specifies the electronic mail address of the mailbox that the PST file will be imported to. You tin can't specify a public folder because the PST Import Service doesn't support importing PST files to public folders.
    To import a PST file to an inactive mailbox, you have to specify the mailbox GUID for this parameter. To obtain this GUID, run the following PowerShell command in Substitution Online: Get-Mailbox <identity of inactive mailbox> -InactiveMailboxOnly | FL Guid

    Note: Sometimes you might take multiple mailboxes with the same email address, where one mailbox is an agile mailbox and the other mailbox is in a soft-deleted (or inactive) state. In these situations, you take to specify the mailbox GUID to uniquely place the mailbox to import the PST file to. To obtain this GUID for active mailboxes, run the post-obit PowerShell command: Get-Mailbox <identity of active mailbox> | FL Guid. To obtain the GUID for soft-deleted (or inactive) mailboxes, run this control Get-Mailbox <identity of soft-deleted or inactive mailbox> -SoftDeletedMailbox | FL Guid.

    		annb@contoso.onmicrosoft.com
    Or
    2d7a87fe-d6a2-40cc-8aff-1ebea80d4ae7
    IsArchive
    		Specifies whether to import the PST file to the user's archive mailbox. At that place are two options:

    Fake: Imports the PST file to the user'southward chief mailbox.
    TRUE: Imports the PST file to the user's archive mailbox. This assumes that the user'southward archive mailbox is enabled.

    If you lot set this parameter to TRUE and the user's archive mailbox isn't enabled, the import for that user volition neglect. If an import fails for ane user (because their annal isn't enabled and this holding is set to Truthful), the other users in the import task won't be affected.
    If you lot leave this parameter bare, the PST file is imported to the user'south primary mailbox.

    Annotation: To import a PST file to a cloud-based archive mailbox for a user whose primary mailbox is on-premises, just specify TRUE for this parameter and specify the email address for the user'due south on-premises mailbox for the Mailbox parameter.

    		FALSE
    Or
    Truthful
    TargetRootFolder
    		Specifies the mailbox folder that the PST file is imported to.

    If you leave this parameter bare, the PST file volition be imported to a new folder named Imported at the root level of the mailbox (the same level as the Inbox folder and the other default mailbox folders).

    If you specify /, the folders and items in the PST file are imported to the acme of the binder structure in the target mailbox or archive. If a folder exists in the target mailbox (for example, default folders such as Inbox, Sent Items, and Deleted Items), the items in that folder in the PST are merged into the existing folder in the target mailbox. For instance, if the PST file contains an Inbox folder, items in that folder are imported to the Inbox folder in the target mailbox. New folders are created if they don't be in the folder structure for the target mailbox.

    If you specify /<foldername>, items and folders in the PST file are imported to a folder named <foldername> . For example, if you apply /ImportedPst, items would be imported to a binder named ImportedPst. This folder volition be located in the user'southward mailbox at the same level as the Inbox folder.

    Tip: Consider running a few exam batches to experiment with this parameter so you tin can determine the all-time folder location to import PSTs files to.

    		(leave blank)
    Or
    /
    Or
    /ImportedPst
    ContentCodePage
    		This optional parameter specifies a numeric value for the code folio to use for importing PST files in the ANSI file format. This parameter is used for importing PST files from Chinese, Japanese, and Korean (CJK) organizations considering these languages typically use a double byte graphic symbol set (DBCS) for character encoding. If this parameter isn't used to import PST files for languages that use DBCS for mailbox folder names, the folder names are oftentimes garbled after they're imported.

    For a list of supported values to use for this parameter, see Lawmaking Page Identifiers.

    Note: As previously stated, this is an optional parameter and you lot don't take to include it in the CSV file. Or you tin include it and leave the value blank for one or more than rows.

    		(leave bare)
    Or
    932 (which is the lawmaking page identifier for ANSI/OEM Japanese)
    SPFileContainer
    		For PST Import, leave this parameter blank.
    		Not applicable
    SPManifestContainer
    		For PST Import, go out this parameter blank.
    		Not applicable
    SPSiteUrl
    		For PST Import, leave this parameter blank.
    		Not applicable

Stride 5: Create a PST Import chore

The next step is to create the PST Import job in the Import service in Microsoft 365. Every bit previously explained, you submit the PST Import mapping file that you created in Footstep 4. After you lot create the job, Microsoft 365 analyzes the information in the PST files and so gives you an opportunity to filter the data that actually gets imported to the mailboxes specified in the PST import mapping file (encounter Step 6).

  1. Get to https://compliance.microsoft.com and sign in using the credentials for an administrator business relationship in your organization.

  2. In the left pane of the Microsoft 365 compliance centre, click Information governance > Import.

  3. On the Import tab, click Add Icon. New import job.

    Note

    You lot have to be assigned the advisable permissions to access the Import folio in the Microsoft 365 compliance center to create an import job. Run across the Before you brainstorm section for more than information.

  4. Type a name for the PST import task, and then click Side by side. Utilize lowercase letters, numbers, hyphens, and underscores. Yous can't use capital letters or include spaces in the name.

  5. On the Do you want to upload or ship information? page, click Upload your information so click Next.

  6. In pace 4 on the Import information page, click the I'm done uploading my files and I have access to the mapping file check boxes, and and then click Side by side.

    Click the two check boxes in step 4.

  7. On the Select the mapping file page, click Select mapping file to submit the CSV mapping file that yous created in Step iv.

    Click Select mapping file to submit the CSV file you created for the import job.

  8. After the proper name of the CSV file appears under Mapping file name, click Validate to check your CSV file for errors.

    Click Validate to check the CSV file for errors.

    The CSV file has to be successfully validated to create a PST Import job. The file name is changed to dark-green after information technology'due south successfully validated. If the validation fails, click the View log link. A validation error report is opened, with an mistake message for each row in the file that failed.

    Note

    As previously explained, a mapping file can have a maximum of 500 rows. Validation will fail if the mapping file contains more 500 rows. To import more than 500 PST files, yous'll have to create multiple mapping files and multiple import jobs.

  9. Later the mapping file is successfully validated, read the terms and conditions document, and then click the checkbox.

  10. Click Save to submit the job, and then click Shut later on the job is successfully created.

    A status flyout page is displayed, with a condition of Analysis in progress and the new import task is displayed in the listing on the Import PST files page.

  11. Click Refresh Refresh icon. to update the status data that's displayed in the Status column. When the assay is consummate and the data is set up to exist imported, the condition is changed to Analysis completed.

    You can click the import job to display the status flyout page, which contains more detailed information about the import job such every bit the status of each PST file listed in the mapping file.

Step half dozen: Filter data and start the PST Import job

Afterward you create the import job in Pace five, Microsoft 365 analyzes the information in the PST files (in a prophylactic and secure manner) by identifying the age of the items and the different bulletin types included in the PST files. When the assay is completed and the data is ready to import, you have the pick to import all the data independent in the PST files or yous can trim the information that's imported by setting filters that control what information gets imported.

  1. On the Import tab in the Microsoft 365 compliance middle, select the import jobs that you lot created in Step 5 and then click Import to Microsoft 365.

    The Filter your data page is displayed. It contains the information insights resulting from the assay performed on the PST files past Microsoft 365, including information nigh the age of the data. At this signal, yous have the selection to filter the data that will exist imported or import all the data as is.

    You can trim the data in the PST files or import all of it.

  2. Practise one of the following:

    1. To trim the data that you import, click Yep, I want to filter information technology before importing.

      For detailed stride-by-pace instructions about filtering the information in the PST files so starting the import job, see Filter data when importing PST files to Microsoft 365.

      Or

    2. To import all data in the PST files, click No, I want to import everything, and click Side by side.

  3. If yous chose to import all the data, click Import data to start the import job.

    The status of the import chore is display on the Import PST files folio. Click Refresh icon. Refresh to update the status information that's displayed in the Status cavalcade. Click the import job to display the condition flyout page, which displays status data about each PST file being imported.

More than information

  • Why import PST files to Microsoft 365?

    • Information technology's a good way to import your organisation'southward archival messaging data to Microsoft 365.

    • The information is bachelor to the user from all devices considering it's stored in the deject.

    • It helps address compliance needs of your arrangement by letting you apply Microsoft 365 compliance features to the data from the PST files that you imported. This includes:

    • Enabling archive mailboxes and automobile-expanding archiving to give users boosted mailbox storage space to store the data that y'all imported.

    • Placing mailboxes on Litigation Hold to retain the data that yous imported.

    • Using Microsoft eDiscovery tools to search the data that you imported.

    • Using Microsoft 365 retentivity policies to control how long the information that you imported will be retained, and what action to take later on the retention period expires.

    • Searching the audit log for mailbox-related events that affect the data that you imported.

    • Importing information to inactive mailboxes to archive information for compliance purposes.

    • Using data loss prevention policies to foreclose sensitive data from leaking outside your organization.

  • As previously explained, the Microsoft 365 Import service turns on the retention hold setting (for an indefinite duration) subsequently PST files are imported to a mailbox. This means the RetentionHoldEnabled holding is ready to True so that the retention policy assigned to the mailbox won't exist candy. This gives the mailbox possessor time to manage the newly imported letters by preventing a deletion or archive policy from deleting or archiving older messages. Here are some steps you lot tin take to manage this memory hold:

    • After a certain time, you tin turn off the retention agree by running the Set-Mailbox -RetentionHoldEnabled $fake control. For instructions, encounter Place a mailbox on retention hold.

    • Yous can configure the retention hold so that it's turned off on some date in the futurity. You lot do this by running the Set-Mailbox -EndDateForRetentionHold date command. For example, assuming that today's date is June 1, 2016 and you want the memory hold turned off in thirty days, you would run the following command: Set-Mailbox -EndDateForRetentionHold seven/1/2016. In this scenario, yous would leave the RetentionHoldEnabled property set to Truthful. For more data, see Set-Mailbox.

    • You can modify the settings for the retentivity policy that'southward assigned to the mailbox so that older items that were imported won't be immediately deleted or moved to the user'due south annal mailbox. For case, you could lengthen the memory age for a deletion or annal policy that'southward assigned to the mailbox. In this scenario, you lot would plough off the retention hold on the mailbox after you inverse the settings of the retention policy. For more information, meet Set up an archive and deletion policy for mailboxes in your organization.

How the import process works

You lot tin can use the network upload option and the Microsoft 365 Import service to bulk-import PST files to user mailboxes. Network upload ways that you lot upload the PST files a temporary storage area in the Microsoft cloud. Then the Microsoft 365 Import service copies the PST files from the storage surface area to the target user mailboxes.

Hither's an analogy and description of the network upload procedure to import PST files to mailboxes in Microsoft 365.

Workflow of the network upload process to import PST files to Microsoft 365.

  1. Download the PST import tool and key to private Azure Storage location: The first step is to download the AzCopy command-line tool and an admission key used to upload the PST files to an Azure Storage location in the Microsoft cloud. Y'all obtain these from the Import page in the Microsoft 365 compliance center. The key (called a secure admission signature (SAS) key, provides you with the necessary permissions to upload PST files to a private and secure Azure Storage location. This access key is unique to your organization and helps prevent unauthorized access to your PST files subsequently they're uploaded to the Microsoft deject. Importing PST files doesn't require your organization to have a split Azure subscription.

  2. Upload the PST files to the Azure Storage location: The side by side step is to use the azcopy.exe tool (downloaded in step 1) to upload and store your PST files in an Azure Storage location that resides in the same regional Microsoft datacenter where your organization is located. To upload them, the PST files that you want to import take to be located in a file share or file server in your organization.

    There's an optional pace that you can perform to view the list of PST files after they're uploaded to the Azure Storage location.

  3. Create a PST import mapping file: Afterward the PST files have been uploaded to the Azure Storage location, the next pace is to create a comma-separated value (CSV) file that specifies which user mailboxes the PST files volition be imported to, notation that a PST file can be imported to a user's primary mailbox or their archive mailbox. The Microsoft 365 Import service uses the information in the CSV file to import the PST files.

  4. Create a PST import job: The next step is to create a PST import task on the Import PST files folio in the Microsoft 365 compliance center and submit the PST import mapping file created in the previous pace. Afterwards y'all create the import job, Microsoft 365 analyzes the information in the PST files and so gives you an opportunity to set filters that control what information really gets imported to the mailboxes specified in the PST import mapping file.

  5. Filter the PST data that will be imported to mailboxes: After the import job is created and started, Microsoft 365 analyzes the data in the PST files (safely and securely) by identifying the age of the items and the different message types included in the PST files. When the analysis is completed and the data is ready to import, yous have the option to import all the data contained in the PST files or you can trim the data that's imported past setting filters that control what data gets imported.

  6. Start the PST import task: Afterwards the import job is started, Microsoft 365 uses the information in the PST import mapping file to import the PSTs files from the Azure Storage location to user mailboxes. Status information near the import job (including information almost each PST file existence imported) is displayed on the Import PST files page in the Microsoft 365 compliance heart. When the import job is finished, the status for the job is gear up to Complete.