RemotePowerShellEnabled disabled for every user

[Sartharon]

Description
Using -or comparison inside the Where-clause to exclude specified admins leads to having RemotePowerShell disabled for those users as well.
Example:
admin1 -ne admin1 -or admin1 -ne admin2
-> $false -or $true
-> $true

Using the -and comparison fixes this behavior, since neither admin1 nor (-ne + -and) admin2 should have their RemotePowerShell disabled.

Real world tests

• Default State:
  
• After running the suggested cmdlet with [email protected] and [email protected] exempt
  Get-User | Where-Object {$_.UserPrincipalName -ne '[email protected]' -or $_.UserPrincipalName -ne '[email protected]'} | Set-USer -RemotePowerShellEnabled $false
  
• Using the corrected cmdlet with an -and comparison:
  

[opbld30]

Learn Build status updates of commit 08b9f1b:

✅ Validation status: passed

File	Status	Preview URL	Details
exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md	✅Succeeded	View (exchange-ps)

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[chrisda]

Already fixed yesterday #10027, thus now this PR results in merge conflicts.

Closing.