Import-Module -DisableNameCheckingĬonnect-SPOService -Url -credential $credentialĬonnect-MicrosoftTeams -Credential $credentialĬonnect-ExchangeOnline -ShowProgress $trueĬonnect-IPPSSession -UserPrincipalName $acctName $credential = Get-Credential -UserName $acctName -Message 'Type the account's password.' To use anything on O365/M365, you must login to the service first.Ĭonnect to all Microsoft 365 services in a single PowerShell window should be in there as well as in all your scripts that are distributed. (New-Object ).Proxy.Credentials = ::DefaultNetworkCredentials Lastly, install the modules you need/want, and have them autoloaded by using your PowerShell profile. Install-Module -Name PackageManagement -Force -MinimumVersion 1.4.6 -Scope CurrentUser -AllowClobber command alone to update package management or a specific module, Find-Module -Name 'ExchangeOnlineManagement' | Update-Help -Force -ErrorAction Silentl圜ontinue Then you update, the PowerShell help files. Installing PSCore does not upgrade or replace Windows PowerShell, which is part of the OS.

The only other option for install is to install a cross-platform PowerShell Core (though not required for what you are after, but it is a choice and you can use either, even at the same time.) So, powershell.exe or powershell_ise.exe are the executables. However, if you are on legacy Windows, then you are on legacy PowerShell unless you upgraded the Windows Powershell version to the latest. Just use the start menu to fire either the console host or the ISE (integrated scripting environment). It is there by default, as it is part of the OS. There is no reason to install PowerShell on Windows. You are not saying, what WinOS you are running, nor which version of PowerShell you are running.

Available modules and cmdlets are PowerShell version-specific.

Exchange online powershell download