Connector inventory
Documentation: Microsoft Learn
Inventory Exchange Online inbound and outbound connectors, including enabled state, connector type, and outbound recipient domains.
The script
Script reader
Inspect before you run
Inspect the script below. It does not run in this browser.
Inspection only — no command has run.
Show reference output
Inspect this example’s structure
Read the command and its supplied arguments. This example requires real PowerShell or its module; this diagram does not execute it.
Get-InboundConnector | Select-Object Name,Enabled,ConnectorType; Get-OutboundConnector | Select-Object Name,Enabled,RecipientDomains- Stage 1Get-InboundConnector
Positional values or no named parameters - Stage 2Select-Object
Positional values or no named parameters - Stage 3Select-Object
Positional values or no named parameters
How it works
Two calls run back to back. Get-InboundConnector reports each inbound connector with its enabled state and ConnectorType, which says whether it was built for on-premises or partner mail, and Get-OutboundConnector adds the RecipientDomains each outbound connector claims responsibility for.
Adapting it
Add SmartHosts to the outbound projection and TlsSenderCertificateName to the inbound one, because those fields are where a certificate rotation on either side quietly breaks delivery.
Requirements
ExchangeOnlineManagement module with a Connect-ExchangeOnline session.
If the result is unexpected
Connector inventory does not explain a mail-flow failure.
Inbound and outbound connectors have different direction, matching and transport settings.
- Identify the message direction and compare its route with the relevant connector configuration.
Validate the result
The inspected connector matches the intended route and its validation results are recorded.
Keep the check reliable
Keep connector direction, domains and transport requirements in the inventory.
