Get-InboundConnector

This cmdlet is available only in the cloud-based service. Use the Get-InboundConnector cmdlet to view the settings for an Inbound connector in your cloud-based organization. For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).

Syntax

Get-InboundConnector
   [[-Identity] <InboundConnectorIdParameter>]
   [<CommonParameters>]

Description

Inbound connectors accept email messages from remote domains that require specific configuration options.

You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx).

Examples

-------------------------- Example 1 --------------------------

Get-InboundConnector "Inbound Connector for Contoso.com" | Format-List

This example displays detailed configuration information for the Inbound connector named Inbound Connector for Contoso.com.

-------------------------- Example 2 --------------------------

Get-InboundConnector

This example lists all the Inbound connectors configured in your cloud-based organization.

Optional Parameters

-Identity

The Identity parameter specifies the name or GUID of the Inbound connector. If the Identity name contains spaces, enclose the name in quotation marks ("). You can omit the Identity parameter label.

Type:InboundConnectorIdParameter
Position:1
Default value:None
Accept pipeline input:True
Accept wildcard characters:False
Applies to:Exchange Online Protection

Inputs

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types (https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data.

Outputs

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types (https://go.microsoft.com/fwlink/p/?linkId=616387). If the Output Type field is blank, the cmdlet doesn't return data.