Example 1

The command shown in Example 1 returns information about all the partner applications configured for use in the organization

	Copy Code
Get-CsPartnerApplication

Example 2

Example 2 returns information for the partner application that has the Identity MicrosoftExchange.

	Copy Code
Get-CsPartnerApplication -Identity "MicrosoftExchange"

Example 3

In Example 3, information is returned for all the partner applications that have an application identifier equal to "microsoft.exchange." In order to do this, the command first calls the Get-CsPartnerApplication cmdlet without any parameters; that returns a collection of all the configured partner applications. That collection is then piped to the Where-Object cmdlet, which picks out only those partner applications where the ApplicationIdentifier property is equal to "microsoft.exchange."

	Copy Code
Get-CsPartnerApplication | Where-Object {$_.ApplicationIdentifier -eq "microsoft.exchange"}

Example 4

In Example 4, information is returned for all the partner applications that are currently disabled. To do this, the command first calls the Get-CsPartnerApplication cmdlet in order to return a collection of all the partner applications, both enabled and disabled. That collection is then piped to the Where-Object cmdlet, which selects only those applications where the Enabled property is equal to False.

	Copy Code
Get-CsPartnerApplication | Where-Object {$_.Enabled -eq $False}

In Lync Server 2013, server-to-server authentication (for example, the authentication that enables Lync Server 2013 and Exchange 2013 to share information) is carried out using the OAuth security protocol. This type of authentication typically requires three servers: the two servers that need to communicate with one another (Server A and B) and a third-party security token server. If Servers A and B need to communicate with one another, the two servers contact the token server (also known as an OAuth server) and obtain mutually-trusted security tokens that the two servers can exchange in order to prove their identities.

If you are using an on-premises version of Lync Server 2013 and you need to communicate with another server product that fully supports the OAuth protocol (for example, Exchange 2013 or Microsoft SharePoint 2013) then you typically do not need to use a token server; that's because these server products are able to issue their own security tokens. However, you will need to configure the other server product (e.g., Exchange 2013) as a partner application. (You will also need to configure Lync Server 2013 as a partner application for the other server product.) In Lync Server 2013, partner applications are managed by using the CsPartnerApplication cmdlets.

To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell command-line interface prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Get-CsPartnerApplication"}

Lync Server Control Panel: The functions carried out by the Get-CsPartnerApplication cmdlet are not available in the Lync Server Control Panel.

None. The Get-CsPartnerApplication cmdlet does not accept pipelined input.

The Get-CsPartnerApplication cmdlet returns instances of the Microsoft.Rtc.Management.WritableConfig.Settings.SSAuth.PartnerApplication#Decorated object.