Repository navigation
Basic Authorization fails on some piped commands in Office365 remote #7266
Description
Steps to reproduce
$Office365 = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://outlook.office365.com/powershell-liveid" -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $Office365
Get-Mailbox|Get-MailboxRegionalConfigurationExpected behavior
Output of a listing of regional settings for all mailboxes.
Actual behavior
Sending data to a remote command failed with the following error message: Basic Authorization failed for user foo@bar.de For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OperationStopped: (outlook.office365.com:String) [], PSRemotingTransportException
+ FullyQualifiedErrorId : JobFailure
+ PSComputerName : outlook.office365.com
Environment data
> $PSVersionTable
Name Value
---- -----
PSVersion 6.0.2
PSEdition Core
GitCommitId v6.0.2
OS Darwin 17.6.0 Darwin Kernel Version 17.6.0: Tue May 8 15:22:16 PDT 2018; root:xnu-4570.61.1~1/RELEASE_X86_64
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0 Additional information
This commands work
Get-Mailbox|select Alias
Get-MailboxRegionalConfiguration fooGet-Mailbox piped to any Get-MailBox* command fail with the above error.
Reacted by Scott Buchanan and Oleksii Sachek
Activity
raysn0w commentedon Aug 19, 2018
I have the same issue, did you find any workaround?
mrclmh commentedon Aug 19, 2018
No, Ray Olivero (@raysn0w). In my use case it were just a few mail boxes so I called
Get-MailboxRegionalConfigurationon them one by one, which is of course not a solution when you have many mailboxes. I am a powershelll beginner myself but I would try something like a foreach loop over the output ofGet-Mailboxwhen you have many mailboxes.raysn0w commentedon Aug 19, 2018
mmoehring, Bummer. I have over 2,000 users in my org and I was trying to automate a report of users with OOO enabled.
MaximoTrinidad commentedon Aug 19, 2018
If I'm not mistaken, this issue still floating around for some time. I think this module hasn't been converted to .NET Core yet.
And I'm sure is on there list to do.
So, for now you can only run it in Windows PowerShell only.
:)
mrclmh commentedon Aug 30, 2018
Maximo Trinidad (@MaximoTrinidad) Which module has to converted to .Net Core for this to work?
Jvekka commentedon Oct 28, 2019
In my case, the easiest workaround was to use
foreachstatement.$AllUserMailboxesStats = ($AllUserMailboxes | ? { Get-MailboxStatistics -Identity $_.Name } )Original code
Semptra commentedon Aug 23, 2021
Could we expect this issue to be fixed any time soon? Our customer has a lot of user scripts with pipes inside and after moving to a Linux with PS Core they observe this issue with
Basic Authorization failed.$PSVersionTable
Fabi1Sc commentedon Oct 21, 2021
I have the same issue
Tolgon commentedon Nov 4, 2021
Same here
PaulHigin commentedon Apr 7, 2022
@WG-Remoting
Remoting working group:
New-PSSessionis no longer supported for non-Windows platforms, because the OMI bridge used on Non-Windows platforms is no longer supported (#15310). It is hoped that community members will provide support for this via the new custom remoting connections (#16923) feature.However, I am not sure if Exchange endpoints were ever supported through the previous WinRM/OMI implementation on non-Windows platforms.
PaulHigin commentedon Apr 7, 2022
Resolved as 'answered' and closing.