** UPDATE 2 !!** [2020-06-05] Well, it looks like the module is back, now as version 1.0.1. Not entirely sure why it was pulled and put back, probably a bug of some type. Go get the new version here:
https://www.powershellgallery.com/packages/ExchangeOnlineManagement/1.0.1
** UPDATE ** This module has been pulled. Not sure why at the moment, but it’s not available for download at the moment. When it becomes available again I will re-update the blog
For those who manage Exchange Online, there is good news out there now. Microsoft has released the version 1.0.0 of the module as GA (Generally Available). This means that they are out of the purely testing phase and are recommending that these cmdlets be used in Production. So what do we do now?
First. For Reference.
PowerShell Gallery page for ExO v2 (v1.0.0)
https://www.powershellgallery.com/packages/ExchangeOnlineManagement/1.0.0 https://www.powershellgallery.com/packages/ExchangeOnlineManagement/1.0.0
Change Log (from previous version)
v1.0.0 :
1. This is the General Availability (GA) version of EXO PowerShell V2 Module. It is stable and ready for being used in production environments.
2. Get-ExoMobileDeviceStatistics cmdlet now supports Identity parameter.
3. Improved reliability of session auto-connect in certain cases where script was executing for ~50minutes and threw “Cmdlet not found” error due to a bug in auto-reconnect logic.
4. Fixed data-type issues of two commonly used attributed “User” and “MailboxFolderUser” for easy migration of scripts.
5. Enhanced support for filters as it now supports 4 more operators – endswith, contains, not and notlike support. Please check online documentation for attributes which are not supported in filter string.
Upgrading your ExO v2 from Beta to 1.0.0
Remove the old version
First. Verify the version you have is old:
Get-InstalledModule ExchangeOnlineManagement
Second. Remove the Module.
Get-InstalledModule exchangeOnlineManagement | Uninstall-Module
Third. Confirm it’s gone.
Whoops … Maybe we have other versions out there?
Remove this older one as well… Actually, let’s remove ALL versions:
Uninstall-Module ExchangeOnlineManagement -AllVersions
Now we install the new version
Install-Module -Name ExchangeOnlineManagement -RequiredVersion 1.0.0
Confirm it’s installed.
A little tip here, if you want some detailed information on the module, simply run Get-Module
Load the Module and Begin Using
Load ‘Er Up
Now you are all ready to run the new Exchange Online v2 cmdlets.
Having been dragged into ExO kicking and screaming, I’m dissatisfied with the the lack of management in some areas. The removal of this module doesn’t appear to be a step in the right direction. I was brought into a project recently to see if I could get S/MIME working with a Microsoft 365 installation in conjunction with a secure email to fax gateway. There is a dearth of documentation and management tools for this. Granted this is old technology, but it appears that the military is attempting to keep on using it and running into issues with Microsoft 365. For S/MIME to be seamlessly supported in a cloud, multi-device environment, certificate management has to improve and support third-party issued certificates for senders within the organization and recipients anywhere. Sender certificates need a cloud location certificate store to support multiple devices. I realize that Microsoft is pushing OME, but S/MIME is already a standard and heavily used by the military. I have been unable to find anything that works that allows me to to update GAL recipient records with certificate data short of the possibility of using AD Connect with an on premises AD installation and Azure AD. I don’t expect many users not at the enterprise level to have a hybrid on premises/cloud installation. All of this stuff should be able to be done in the cloud only.