The EXO V2 module uses modern authentication for all cmdlets. How the Exchange Online PowerShell v2 module (EXO V2 module) works You can download the Microsoft Exchange Online PowerShell v2 module (EXO V2 module) from the PowerShell gallery at: Exchange Online PowerShell v2 module download The best way to avoid this issue is to use the CommandName parameter on the Connect-ExchangeOnline cmdlet to limit the cmdlets that are used in the session. The latest version of EXO V2 module and frequent use of the Connect-ExchangeOnline and Disconnect-ExchangeOnline cmdlets in a single PowerShell session or script might lead to a memory leak. Properties and property sets in the EXO V2 module.Troubleshoot installing the EXO V2 module.Install the EXO V2 module Only for the current user account:.Install the EXO V2 module for All users:.Close and re-open the Windows PowerShell window.Install Exchange Online PowerShell v2 module (EXO V2 module).Get Execution Policy PowerShell (Set-Execution Policy to RemoteSigned).How to check PowerShell version in Windows 10.Supported operating systems for the EXO V2 module.Install Exchange Online PowerShell v2 module requirements.How the Exchange Online PowerShell v2 module (EXO V2 module) works.Exchange Online PowerShell v2 module download.The matter is that other available Exchange Online cmdlets (over 750) are imported into your PowerShell session after connecting to a tenant.Table Of Contents – Install Exchange Online PowerShell v2 module

Note that there is no Set-Mailbox cmdlet in the ExchangeOnlineManagement module. If -like Name=ExchangeOnlineInternalSession*').Count -gt 0) -ne $true) | Get-EXOMailboxStatistics $PSSessions = Get-PSSession | Select-Object -Property State, Name It will allow to avoid extra PowerShell sessions with Microsoft 365. You can use the following code in your PowerShell scripts to make sure that the connection to Exchange Online through the EXOv2 module is active. If you try to open a sixth one, the following error appears: Fail to create a runspace because you have exceeded the maximum number of connections allowed. The matter is that Exchange Online supports only 5 concurrent PowerShell sessions. In our example, the connection to is active (State= Opened).Īfter you finish working with Exchange Online, exit your session correctly using the Disconnect-ExchangeOnline cmdlet. You can make sure if there is an active connection to Exchange Online as shown below: If Modern Authentication is disabled for the account, you can connect as follows:Ĭonnect-ExchangeOnline -Credential $cred -UserPrincipalName -ShowProgress $true Connect-ExchangeOnline -UserPrincipalName -ShowProgress $true -DelegatedOrganization

Download exchangeonlinemanagement