Running this new module with WinRM basic authentication disabled still yields error:
New-ExoPSSession : Connecting to remote server outlook.office365.com failed with the following error message : The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration.
Isn't this module supposed to get rid of basic auth?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@officedocsbot assign @yogkumgit
I have the same issue, and cannot change my WinRM authentication setting due to a corporate group policy.
Hi @felinepc and @eric-ash-1, thank you for your feedback.
As you can read in the article Exchange Online PowerShell V2 cmdlets always use Modern Authentication. You cannot use basic authentication here. But WinRM basic authentication is a requirement to connect.
I have tried this on my lab but let me double check it.
Well WinRM basic auth is a big problem with the old module because many of us have GPO or Intune policies that forbid it for valid reasons. Microsoft itself discourages it with the Intune security baselines. So we'd assume a new module should not have to depend on it.
Please also provide this feedback to the email address you can find in the first tip of the article.
@dariomws306 Thank you very much for the contribution and updating the documentation with PR. @felinepc Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.
I would like to point out that the AzureAD module (I'm using 2.0.2.76) worked on my computer even though I have WinRM Basic Auth disabled. Perhaps the Exchange Online module could adopt the same methodology.
Most helpful comment
I would like to point out that the AzureAD module (I'm using 2.0.2.76) worked on my computer even though I have WinRM Basic Auth disabled. Perhaps the Exchange Online module could adopt the same methodology.