I think I found an Problem with the Content Search PST-Export and the PST-Import "Service" as well as Powershell "New-Mailboximportrequest" from own Azure Blob storage.
There is an Support-Case open, but I realy believe that they don't want or maybe can't help me. But it shows no process in about 2 Weeks now. The always ask me the same questions again and again.... Like they are not reading what I am writing. Thats realy exhausting. (the Case is [Case #:24556679] if someones interested)
Because of that I am writing here, to get some help, or just to reach people who can actualy do something to solve it.
I am an IT-Admin and migrating our company to an completely new Active-Directory Domain + New Tenant. The Admins befor did not realy have any glue what they did, and they messed up the whole AD-Config.
To get this all done with an minimum of User noticable impact, I think the PST-Way would be great for my situation.
So I started to do an Content Search in Tenant A and exported everything as PST-Files.
I choosed all settings which can be found in the help docs. I searched with "Exchange Online" only (No sharepoint etc marked) and it found the correct amount of mailboxes.
So I created the Export job with "One PST-File PER MAILBOX" and nothing more. The exported PST-Files all downloaded well and I startet to try the Import in Tenant B.
so the Transfer itself will happen like this:
So first I tried with the known Import-Service and the config.csv file. The import itself worked. BUT even the Alias of the 2 mailboxes are identical, the Import was not able to match the existing Rootfolders correctly and imported everything inside the new Mailbox, but with the whole Root-Structure attached.
With EWS-Editor it looks like this:
What I think is happening here is somethink like the Import-Job ist not fully matched the to the Files which are exported with Contentsearch.
It looks like an Array. The Import-Job should look in the First key of the "Subarray" like ARRAY->-SUBARRAY->DATA-TO-IMPORT
But instead it takes the "Array" and writes it to the completely wrong place.
This import was made for example with an Config like this:
After that I tried it out with powershell and the pst-files hosted on an Azure-Blob storage. With commands like this:
New-MailboxImportRequest -Name "mailbox_import_testuser" -Mailbox "michael.hahn" -TargetRootFolder "/" -AzureBlobStorageAccountUri "...." -AzureSharedAccessSignatureToken "?sv=......."
The result was the same. It also ignores any try with commands like: -TargetRootFolder "/" -IncludeFolders "#INBOX#"
The names of the added Folders are messed up too. It looks like there is just the next foldername added to the firstone
like the imported INBOX shows the Name "Oberste Ebene des Informationsspeichers Michael.firstname.lastname@example.org (primary) Oberste Ebene des...." and so on.
Now the question of the question. WHO Can help me here? Is it a "Bug"? If it is not the right behaviour, which person should know about it?
To replicate you have to: Create an discovery search -> only exchange only -> export with option "one pst file per mailbox"
Thats the very minimal export you could do. and it should import the mailbox just right to the new mailbox. That the folders are matched. But somehow it doesnt...
I tried every possible combination of the powershell commands. But nothing chances the result. Thank you for your time.