Checkout my blog posting on Copying Emails from Exchange to ProjectWise. Hopefully you find this useful.
I have been advised that basic authentication support is ending for Exchange Online:
Support should have been ending in Oct 2020, but due to COVID that date has been pushed back to some time in 2021.
Are there plans to accommodate this authentication change in the Postman Service and Copy-PWMailMessagesFromExchange ?
We have many projects using this currently.
We've got 14 datasources worldwide using that cmdlet which is a pretty small number. We probably won't do anything until it is completely broken or more widely adopted. Have you looked at the Flow (Power Automate) connector for email? I think this will be Bentley's solution to this problem long term.
Thanks for the info Dave. As we purchased Postman Service I will raise a Support Ticket to ask for more detailed information about how to create the same result using Flow.
Do you have a support contract with that? If not, an ST won't go anywhere. We'd have to rewrite the service to support any new authentication that MSFT may implement. You can have your Account Manager contact me to set up a meeting.
I just stumbled upon this thread.. we're heavy users of the Postman service as well Dave. I think we've been using it since 2013!
If I'm reading this correctly - the authentication method that's in place is soon to be retired?
Have we confirmed that the retirement of basic authentication will impact the postman service? Dave BrumbaughBrian Flaherty
Somebody just made this work the other day with hotmail and basic auth. Probably works with Google, too. I don't know about Exchange 365. I really haven't messed with it in years. However, I suspect MSFT will provide some PowerShell support for interacting with your Exchange 365 with their new auth mechanism. I'd recommend using their module to extract mail messages and then using something like Import-PWDocuments or New-PWDocument to import the messages. We merely leverage some .NET classes to access the mail store, extract messages, and then do exactly that internally. The power of PowerShell is its ability to mix and match modules from different vendors so I'd recommend that approach if it turns out the auth is broken.