Use network upload to import PST files into Office

Microsoft has advised its a known issue and they are working on it... looks like its a global problem.. just have to seat tight.,.

We've had this bug while doing a cutover migration with PST import over the azcopy Tool and we've found that using the Mailbox GUID instead of the SMTP Address in the csv file is a functioning workaround!

You can get the GUIDs of the existing Exchange Online Mailboxes with the Cmdlet Get-Mailbox | ft GUID, alias

At least in our small migration of 18 Mailboxes this has worked nicely for all of them.

Since the message on Monday or Tuesday stating that it should be fixed worldwide,

I have been re-running the import jobs over and over about 5 times a day.

From original 100 failed, i am now down to last 20 remaining ..

It seems to be getting better as some batches at start completed as little as 2 and the best one I had so far which was my last try completed 20.

Hoping 2-3 more tries max and I will have all the emails up to date.

as mentioned in one of the previous posts, using GUID instead of UPN as target didn't make a difference for me with the error mentioned, but it did resolve other issues where report was claiming UPN is matching multiple entries. This was because i had some soft deleted mailboxes and mailusers which you can only see in PowerShell.

All the best to everyone, hopefully eventually you all manage to get all the needed imports done!

Same problem here migrating PST to M365.

I send 18 PST correctly but 6 are failing with same error, hangs at 0% before failing.

Hello,

We are having the same issue it seems, at least since 7/19. We are unable to successfully import ANY PST files in Compliance Center > Data Lifecycle Management > Import. Import stays at 0% a long time and then fails with "Completed with errors" status message. However, upon inspection of job details, it shows Status "Failed" with 0 items imported.

Error log contains the following information:

Failed,MRSRemoteTransientError,0,0,0,Microsoft.Exchange.Net.CommunicationErrorTransientException
The call to 'net.tcp://XXXXXXXXXXXXX.XXXXXXX.prod.outlook.com/Microsoft.Exchange.MailboxReplicationService XXXXXXXXXXXXX.XXXXXXX.prod.outlook.com (15.20.5482.6 ServerCaps:3FFFFFFF
ProxyCaps:03FFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF,MailboxCaps:legacyCaps:3FFFFFFF)' failed. Error details: Could not load file or assembly 'Azure.Core

Status: ProtocolError
Status code: InternalServerError (500)
X-Psws-ErrorCode: 841101
X-Psws-Exception: Microsoft.Exchange.Net.CommunicationErrorTransientException

What's very interesting is that if I run the command "Get-MailboxImportRequestStatistics ******@domain.com" to check on the status of the Import, it doesn't even register the Import Request at all.

The result is:

Write-ErrorMessage : Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException No such request exists in the specified index.

And if i run "Get-MailboxImportRequest" to show a list of requested imports, there is NOTHING in the list after 7/11.

So it's as if these Import requests are just not registering at all.

I have tried using different admin accounts, different PST files, and different mailboxes - using both UPN and GUID. Everything fails. I have a support case open with Microsoft on this, but so far they have not been able to figure it out. I think this is a wider issue than they know, but hasn't been well reported yet.

Thank you,

Dave