Hacker News Reader

PST export using the Exchange module for PowerShell has been a thing since Exchange 2010, see "New-MailboxExportRequest": https://learn.microsoft.com/en-us/powershell/module/exchange...

EDIT: Oh, nvm - it's on-prem only - huh... that's asinine.

View on HN

PSTs can be exported from Exchange Online via eDiscovery, although I'm curious why you'd want to, since it will only include whatever's in the mailbox anyway, which can presumably be accessed directly from the cloud when the mail client signs in.

What's the use case with PST import in Thunderbird? Outlook clients with an IMAP/POP3 mailbox storing a local archive of mail that's since been deleted from the server? This can be uploaded to the Exchange Online mailbox through Outlook which would be more resilient and less brittle than a local PST. What scenario am I missing?

Just noting that mail exported through ediscovery doesn't look like you'd expect - mail data is several folders deep. It's fine to say "just a few more clicks" but having inbox not be in an inbox folder is jarring breaks any idea of automated imports.

the docs might be misleading - New-MailboxImportRequest is "only supported on-prem", but it's used by the PST import UI and works just fine with EXO

Reply on news.ycombinator.com