![]() Therefore, I loaded the DLL and run the function New-ExoPSSession manually: It just fails, but don’t pass the origin error to the user. ![]() The module doesn’t show the actual error. I started comparing a lot of things, but couldn’t find the anything obvious and also the error wasn’t helpful. The problem is that in a scheduled task you need to use this parameter. Not when the interactive authentication flow was used. I was approached by several colleagues, that on some machines or servers there was no way of connecting to Exchange Online using the parameter -Credential. PSSession = New-ExoPSSession -ExchangeEnvironmentName $ExchangeEnviro …īut the issue existed ONLY when using the parameter -Credential… Symptom New-ExoPSSession : An error occurred while sending the request.Īt C:\Program Files\WindowsPowerShell\Modules\ExchangeOnlineManagement\0.3582.0\ExchangeOnlineManagement.psm1:401 char:30… ![]() On my transition to the new module, I was made aware of connectivity issues by some colleagues: ![]() It’s not perfect (yet!), but huge improvements and Microsoft is working hard to get the module improved. It’s been a while that the new module for managing Exchange Online using PowerShell.If not yet aware, please check out how to Use the Exchange Online PowerShell V2 module. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |