In Exchange Online PowerShell, virtually all of the available remote PowerShell cmdlets are backed by the REST API. REST API cmdlets have the same cmdlet names and work just like their remote PowerShell equivalents, so you don't need to update any of your scripts. Limited parameters and output properties available
The benefits of REST API cmdlets are described in the following table:Īll parameters and output properties available
More secure: REST API cmdlets have built-in support for modern authentication and don't rely on the remote PowerShell session, so PowerShell on your client computer doesn't need Basic authentication in WinRM.REST API cmdlets have the following advantages over their historical counterparts: Security & Compliance PowerShell: v3.2.0-Preview4 or later.Exchange Online PowerShell: v3.0.0 or later.The EXO V3 module improves upon the historical capabilities of the EXO V2 module (version 2.0.5 and earlier) with the following features:Ĭertificate based authentication (also known as CBA or app-only authentication) is available for Security & Compliance PowerShell.Ĭmdlets backed by the REST API are available in the following PowerShell environments based on the version of the EXO V3 module: Version 3.0.0 or later is known as the EXO V3 module. The rest of this article explains how the module works, how to install and maintain the module, and the optimized Exchange Online cmdlets that are available in the module. Connect to Exchange Online Protection PowerShell.Connect to Security & Compliance PowerShell.
Version 3.0.0 and later is known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module).įor connection instructions using the module, see the following articles:
Version 2.0.5 and earlier is known as the Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module).
0 kommentar(er)
