The UseRPSSession switch requires Basic authentication in WinRM on your client computer.The UseRPSSession switch in Connect-ExchangeOnline grants access to all existing remote PowerShell cmdlets in Exchange Online PowerShell: Virtually all of the available remote PowerShell cmdlets in Exchange Online are now backed by the REST API. REST API cmdlets in Exchange Online PowerShell have the same cmdlet names and work just like their remote PowerShell equivalents, so you don't need to update any of your scripts. All cmdlets in Security & Compliance PowerShell still rely on the remote PowerShell session, so PowerShell on your client computer requires Basic authentication in WinRM to successfully use the Connect-IPPSSession cmdlet. Limited parameters and output properties availableĬurrently, no cmdlets in Security & Compliance PowerShell are backed by the REST API. The benefits of REST API cmdlets in Exchange Online PowerShell are described in the following table:Īll parameters and output properties available Better performance: The connection avoids setting up a PowerShell runspace in Exchange Online PowerShell.Delays due to large queries that take a long time to complete.More reliable: REST API cmdlets handle transient failures with built-in retries, so failures or delays are minimized.
REST API cmdlets have the following advantages over their historical counterparts: 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 Exchange Online PowerShell. 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.
0 kommentar(er)
