Published Oct 14, 2024
The message details changes in Microsoft Exchange Online PowerShell V3.7, where the Help file will not load by default, and a new parameter '-LoadCmdletHelp' will be needed to use 'Get-Help'. This update will be globally available in late November 2024. Users must update documentation accordingly.
Updated November 19, 2024: We have updated the timeline below. Thank you for your patience.
In Exchange Online PowerShell (EXO) V3.0, we introduced the Connect-ExchangeOnline cmdlet to connect to the Microsoft Exchange Online environment through Microsoft PowerShell, which loads the help file by default. This help file is required for running the Get-Help cmdlet. However, not many customers used the Get-Help cmdlet. In EXO V3.3, we added the -SkipLoadingCmdletHelp parameter. When -SkipLoadingCmdletHelp is used with Connect-ExchangeOnline, help files do not load the on the customer system, which saves resources.
However, starting with EXO V3.7, we are changing this default behavior. The Help file will not be loaded by default, and a new parameter -LoadCmdletHelp will be required to load the cmdlet help and use the Get-Help cmdlet. To avoid breaking existing scripts, the -SkipLoadingCmdletHelp parameter will continue exist, but will not function.
When this will happen:
General Availability (Worldwide): The changes will be available in EXO V3.7 (the next release of our EXO V3 module) in late November 2024 (previously early November).
How this will affect your organization:
Starting with EXO V3.7, if you want to use the Get-Help cmdlet, you will have to use the parameter -LoadCmdletHelp along with Connect-ExchangeOnline.
What you need to do to prepare:
This message only applies to customers who upgrade their EXO module version to 3.7.0. Earlier versions will not be affected by these changes.
This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.
Learn more