POWERSHELL / EXCHANGEONLINEMANAGEMENT
ProAdvancedRead-onlylow

Export Exchange connectors

Export Exchange Online inbound and outbound mail-flow connector configuration to CSV with PowerShell.

Generated securely after server-side Pro license validation · Review before running · Opselith does not connect to your tenant

What this PowerShell script does

Exports inbound and outbound mail flow connector metadata.

Requirements

  • CSV output path - Example: C:\Temp\report.csv

Environment

  • Module: ExchangeOnlineManagement
  • Permissions: View-Only Configuration
  • Output: CSV report
  • Context: PowerShell 7 · Exchange Online
  • Risk: Low
Review before you run The script is generated securely after server-side Pro license validation. Test outside production first.
NEXT STEP

Ready to generate

Configure Export Exchange connectors in the Builder, review the generated PowerShell and run it yourself in your own PowerShell session.

More about this script

Why use this template?

Use this PowerShell template when you need to export inbound and outbound mail flow connector metadata. It can be previewed in the Builder; Pro access is required to generate it for your own environment.

The template uses ExchangeOnlineManagement and requires View-Only Configuration. Output: CSV report. Level: Advanced. Action: Read-only. Risk: Low.

Review before running

The script remains preview-only until Pro access is enabled. Review it before running it, and test it outside production first. “Read-only” describes the script itself; anything you add around it can still change data.

Preview the script

  1. Open the template in the PowerShell Builder.
  2. Review the purpose, requirements, permissions, output and risk.
  3. Activate Pro when you are ready to generate the full script, then test it outside production.

Pro templates remain previewable before purchase or activation. No tenant connection is required. When you generate a Pro script, only the configuration values needed for that template are sent to Opselith after license validation.Preview Export Exchange connectors →

How to use this result

Use this report to inventory the inbound and outbound connectors that shape mail flow between Exchange Online and remote systems or domains.

When this helps

  • Document connectors before a migration, gateway change or mail-flow review.
  • Find old or unexpected connector configuration that needs separate validation.
  • Compare inbound and outbound connector inventory during troubleshooting.

How to read the result

  • Inbound and outbound connectors serve different directions of mail flow, so review them as separate configuration paths.
  • Connector presence and settings describe configuration; they do not prove that end-to-end message delivery is currently succeeding.

Things to check

  • Validate DNS, certificates, smart hosts and real message traces separately where those are relevant to the connector design.
  • This report reads connector configuration and does not send test messages or modify connectors.

What to do next: Compare each connector with your current mail-flow diagram and investigate entries that no longer have a documented purpose.

Related tasks

Official references

Before you runModule, permissions, inputs, compatibility and script checks
OPS / SCRIPT DETAILS

Script details

Exports inbound and outbound mail flow connector metadata. Review these details before generating or running the script.

exchangeexportconnectors
Generated here. Run by you.Opselith does not connect to your tenant or run PowerShell. After generating, review the script and run it in your own PowerShell session.

What it works with

Module: ExchangeOnlineManagement

ExchangeOnlineManagement lets PowerShell connect to and work with Exchange Online.

Context: PowerShell 7 · Exchange Online

Compatibility: PowerShell 7 is the supported target for this Microsoft 365 template.

Permissions and changes

Permissions: View-Only Configuration

Risk: Low

Read-only: designed to collect information without intentionally changing the target environment.

Changes: Read-only. The script reads data and does not intentionally change the target environment.

Inputs

  • CSV output path - Example: C:\Temp\report.csv (Required)

What to expect

Output: CSV report

Expect a CSV file at the path you choose. Open it in Excel or another CSV viewer and review the rows.

Example: C:\Temp\report.csv

This template is in the Pro library. Generating the full script requires eligible Pro or tester access. Opselith receives only the values needed to build the script; it does not connect to your tenant, run PowerShell or store the generated script. You review and run the result in your own PowerShell session.

Example use

Exports inbound and outbound mail flow connector metadata.

Enter the required values in the Builder, review the generated script and confirm the output before running it.

Before you run: Make sure your account has View-Only Configuration. Check that the ExchangeOnlineManagement PowerShell module is available and that you are using the supported PowerShell version. Review the generated script and output path, then test outside production first.
Script checksWhat has been verifiedQA reviewed
Static checksPassed
PSScriptAnalyzerPending
Real-world run testNot yet recorded
Last checkedNot yet recorded

Real-world run results are shown only after Opselith reviews and accepts a tester report.

Tester: report a result →
TEST STATUSWhat Opselith has checked

Last reviewed: 10 Sept 2026

PSScriptAnalyzer: Awaiting a release PSScriptAnalyzer gate that includes this script. No analyzer pass is claimed yet.

Pending or Not yet recorded means there is no accepted result on file yet. A passed analyzer check does not mean the script has been run in a real tenant.