![]() ![]() Limited parameters and output properties available The benefits of REST API cmdlets are described in the following table:Īll parameters and output properties available Better performance: The connection avoids setting up a PowerShell runspace.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.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: For more information, see PowerShellGet for REST-based connections in Windows. In Exchange Online PowerShell and in Security & Compliance PowerShell, REST API connections are used by default and require the PowerShellGet and PackageManagement modules. Security & Compliance PowerShell: v3.2.0 or later.Exchange Online PowerShell: v3.0.0 or later.REST API connections in the EXO V3 moduleĪll available cmdlets in Exchange Online PowerShell and Security & Compliance PowerShell are backed by a REST API based on the version of the EXO V3 module: Version 2.0.5 and earlier (2021) was known as the Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module). Version 3.0.0 and later (2022) is known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module). ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |