![]() ![]() Find the key: \SOFTWARE\Policies\Microsoft\Windows\WinRM\Client.Verify this in the local Windows Registry (regedit.exe): We don’t send the username and password combination, but the Basic authentication header is required to send the session’s OAuth token, since the client-side WinRM implementation has no support for OAuth.” “ WinRM needs to allow Basic authentication (it’s enabled by default). This indicate that the Basic authentication setting of WinRM is disabled, which prevents the client from properly authenticating.Īmong the prerequisites for the EXO V2 module is that Basic authentication should be enabled for WinRM on the connecting client: In some case the connection result in this error:Ĭreate Powershell Session is failed using OAuth. When connecting to Exchange Online using the EXO V2 module, the following cmdlet may be used: Connect-ExchangeOnline -UserPrincipalName -ShowProgress $true ![]() ![]() The added support for modern authentication in Exchange Online PowerShell V2 module (EXO V2) include all cmdlets and replaces Basic Authentication, although the client is still required to have Basic authentication enabled for WinRM.ĭownload EXO V2 module from PowerShell gallery: Connecting to the Exchange Online service using the recent Exchange Online PowerShell V2 module presents a series of new features, including the option for using modern authentication and have the sign-in protected by Multi-Factor Authentication (MFA). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |