Bad filter in "Disable access to Exchange Online PowerShell" document

[tomdan-MSFT]

Prerequisites

• Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
• Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Typo in Get-Foo cmdlet" instead of "Typo."
• Verify Version: If there is a mismatch between documentation and the behavior on your system, ensure that the version you are using is the same as the documentation. Check this box if they match or the issue you are reporting is not version specific.

Links

https://learn.microsoft.com/en-us/powershell/exchange/disable-access-to-exchange-online-powershell?view=exchange-ps&preserve-view=true

Summary

There's a bad filter listed in this article in the PowerShell examples :

https://learn.microsoft.com/en-us/powershell/exchange/disable-access-to-exchange-online-powershell?view=exchange-ps&preserve-view=true

Details

The PowerShell example listed in the article does not work :

Get-User -ResultSize unlimited -Filter 'EXOModuleEnabled -eq $false'

This is an invalid filter for get-user and needs to be updated.

Suggested Fix

Please update the example with the correct filter

[sdwheeler]

That content is not maintained in this repository. You can find the source of that article at https://github.com/MicrosoftDocs/office-docs-powershell/blob/main/exchange/docs-conceptual/disable-access-to-exchange-online-powershell.md.

[chrisda]

@tomdan-MSFT, I confirmed your findings in my plain M365 E5 tenant. I also did some testing:

• The older RemotePowerShellEnabled parameter is still available on Set-User (for how much longer, who knows).
• Whether you use the RemotePowerShellEnabled parameter or the EXOModuleEnabled parameter on Set-User, the value that you specify is used/copied to the other property (I tried them both). Therefore, the values of the RemotePowerShellEnabled and EXOModuleEnabled properties in the output of Get-User are always the same: both True or both False; never one True and the other False.

So, the Get-User commands that use the Filter parameter must use the RemotePowerShellEnabled property. I updated the examples accordingly in PR 12417.

The updated article should publish today W 12/11 at ~11:00AM PST (GMT-8).