« Previous 1 2 3 4 Next »
Use PowerShell to manage Exchange Online
Its Master's Voice
In a PowerShell session, admins can configure settings for Exchange Online and on-premises Exchange servers in parallel. Therefore, hybrid environments also benefit from the scripting language's possibilities. In this article, I introduce you to managing Exchange Online.
To manage Exchange Online from a computer with PowerShell, the computer must have a cloud connection and the required PowerShell modules, unless you only want to administer Exchange Online without on-premises Exchange servers, in which case you would be working remotely across the board. If you want to work with on-premises Exchange servers in parallel, you need to install the latest version of the Exchange management tools on the appropriate computer.
Configuring Local Settings with PowerShell
To manage Exchange Online, the local execution policy for PowerShell must be set to RemoteSigned
instead of Restricted
. If it is set to Restricted
, PowerShell will not run any scripts. RemoteSigned
trusts the scripts required for a remote connection. The first step in managing Exchange Online with PowerShell is to set the execution policy accordingly. On Windows 10 computers, you do this by starting the PowerShell session with administrative privileges from the context menu.
Depending on the execution policy settings, PowerShell blocks unsigned scripts. You can use the Set-ExecutionPolicy
cmdlet to change the execution policy and Get-ExecutionPolicy
cmdlet to view it. For example, to customize the execution policy on a server or a computer, use the
Set-ExecutionPolicy RemoteSigned
command. The command
Set-ExecutionPolicy Unrestricted
disables the execution policy completely. However, this action is not recommended, because it means any script can be run. However, if certain scripts cause
...Buy this article as PDF
(incl. VAT)