Pipelining cmdlets

Working with PowerShell we have many cmdlets that can perform tasks such as queries, configuration changes and more.  By themselves, single cmdlets are useful, but being able to feed information from one cmdlet to another is an incredibly useful feature of PowerShell.  PowerShell uses a concept called pipelining to combine two or more cmdlets to perform a cohesive task. The pipeline character ‘|’ separates the cmdlets.

When creating a pipeline between cmdlets, information passes from the cmdlet on the left to the cmdlet on the right.  Keep in mind that when the information passes from left to right, PowerShell stores the data as objects for the next cmdlet to process and not as plain text. Using objects means that PowerShell has maximum flexibility when the next cmdlet in the pipeline processes the data it receives.

Practical Use

Those with PowerShell for the first time often end up using single cmdlets to construct one-liners to query information like Get-EXOMailbox to list Exchange Online mailboxes or change settings with Set-EXOMailbox. Using a pipeline between these cmdlets expands what we can do. Although no limit exists for the number of cmdlets in a pipeline, be careful not to make it too complex as this could lead to unintended consequences.

These examples show how to use the pipeline in different ways to list Exchange Online mailboxes that are archive enabled:

Get-EXOMailbox -PropertySets Minimum,Archive | Where ArchiveName -ne $Null

Same example, but another Pipeline is used to add sorting by the DisplayName Property:

Get-EXOMailbox -PropertySets Minimum,Archive | Where ArchiveName -ne $Null | Sort-Object DisplayName

Taking the previous example and adding additional Pipelines to adjust formatting of the output:

Get-EXOMailbox -PropertySets Minimum,Archive | Where ArchiveName -ne $Null | Sort-Object DisplayName | ft -Auto

There is an order of operations for the use of cmdlets to process information properly.  For example, formatting cmdlets (Ft, Fl ,Fw) should be added to the end of the pipeline. If not, PowerShell generates an error:

"out-lineoutput : The object of type "Microsoft.PowerShell.Commands.Internal.Format.FormatEntryData" is not valid or not in the correct sequence."

DON’T attempt to format output in the middle of the pipeline:

Get-EXOMailbox -PropertySets Minimum,Retention | Ft DisplayName,Retention* | Sort-Object DisplayName

DO this instead (formatting at the end):

Get-EXOMailbox -PropertySets Minimum,Retention | Sort-Object DisplayName | Ft DisplayName,Retention*

Compatible Cmdlets

Not all PowerShell cmdlets can pipeline information from one cmdlet to another, usually because the objects generated by one cmdlet cannot be processed by the next in the pipeline.  For example, we cannot pipeline objects from the Get-EXOMailbox Cmdlet to the Get-Remote Domain cmdlet because the second cmdlet will attempt to process mailbox identities as remote domains and will therefore fail.

On the other hand, cmdlets that process similar objects like Get-EXOMailbox and Get-MailboxSpellingConfiguration can pipeline data between them because the second cmdlet can accept the mailbox identities to process.

Understanding what cmdlets work together takes some experience. Logically, we need to understand what a cmdlet accepts for input before piping information from another cmdlet.

The $_ Pipeline Variable

Piping supports the special $_ variable to identify the current object being processed by PowerShell.  We can use the object and work with its properties by adding a ‘.’ and the property we want such as DisplayName or Identity.

A common usage of the $_ variable is to reference a property of the object being queried and filter all objects matching this property.  This can be done in a one-liner as well as in a Foreach loop:

In this example, we look for mailboxes updated within the last 14 days:

$Date = (Get-Date).AddDays(-14)
Get-EXOMailbox -InactiveMailboxOnly | Where {$_.WhenChanged -lt $Date}  | Ft

We can also use the $_ variable to perform other common tasks. In this example we search for mailboxes located in the US and that have an assigned Retention Policy:

Get-EXOMailbox -PropertySets All | Where {$_.RetentionPolicy -ne $Null} | Where {$_.UsageLocation -eq 'United States'} | Ft DisplayName,PrimarySMTPAddress,RetentionPolicy -Auto

List of all Inactive Mailboxes from the United States, sorted by the last changed date and the output formatted:

Get-EXOMailbox -InactiveMailboxOnly -PropertySets All | Where {$_.UsageLocation -eq 'United States'} | Sort-Object WhenChanged | Ft DisplayName, WhenCreated, WhenChanged

This example exposes the Recoverable Items stored in all mailboxes located in the United States. Foreach-Object is used to convert the Mailbox GUID to a Display Name for better output readability:

Get-EXOMailbox -Properties UsageLocation | Where {$_.UsageLocation -eq 'United States'} | Get-ExOMailboxFolderStatistics -FolderScope RecoverableItems | Select-Object ContentMailboxGuid, FolderAndSubfolderSize, ItemsInFolderAndSubfolders | ForEach-Object { $Mailbox = $_.ContentMailboxGuid; $Name = (Get-ExOMailbox $Mailbox).DisplayName;$_.ContentMailboxGuid = $Name ; Return $_}

Real World Examples

Foreach loops are another way where we can utilize the $_ special variable to manipulate data.

When gathering mailbox data, one common task is to review email addresses to make sure that Exchange Online data is correct.  For example, perhaps there were object conflicts or aliases were incorrect when the user object synced to Azure AD and the end user’s onmicrosoft.com email address was created incorrectly or not as expected.  Listing the EmailAddresses property reveals proxy email addresses with prefixes of ‘SIP:’ or ‘SMTP:’ or ‘smtp:’.  We can use $_ to remove the pretext to reveal just the email address:

Get-ExOMailbox  | Select-Object DisplayName,RecipientTypeDetails,EmailAddresses | Foreach-Object { $EmailAddresses = $_.EmailAddresses;$TrimmedEmails = @();Foreach ($EmailAddress in $EmailAddresses) { $Email = $EmailAddress.split(':')[1]; $TrimmedEmails += $Email}; $_.EmailAddresses = $TrimmedEmails;Return $_}

With some changes, we can use the code to create lists for SMTP, SIP, and SharePoint Online proxy addresses:


Get-ExOMailbox  | Select-Object DisplayName, RecipientTypeDetails,EmailAddresses | Foreach-Object { $EmailAddresses = $_.EmailAddresses;$TrimmedEmails = @();Foreach ($EmailAddress in $EmailAddresses) { if ($EmailAddress -like 'smtp*') { $Email = $EmailAddress.split(':')[1]; $TrimmedEmails += $Email}}; $_.EmailAddresses = $TrimmedEmails;Return $_}
PowerShell, Piping and Exchange Online Mailbox Management
Figure 1: Email address with ‘smtp’ prefix.

SIP Only

SIP Addresses are used for Teams communications, including phones (Figure 2:)

Get-ExOMailbox | Select-Object DisplayName, RecipientTypeDetails,EmailAddresses | Foreach-Object { $EmailAddresses = $_.EmailAddresses;$TrimmedEmails = @();Foreach ($EmailAddress in $EmailAddresses) { if ($EmailAddress -like 'sip*') { $Email = $EmailAddress.split(':')[1]; $TrimmedEmails += $Email}}; $_.EmailAddresses = $TrimmedEmails;Return $_}
PowerShell, Piping and Exchange Online Mailbox Management
Figure 2: Email address with ‘sip’ prefix.

At the very end of the data formatting, note the usage of ‘Return $_’ which allows for the literal return of the reformatted data back to the object in the pipe.  In our examples, we return only formatted proxy addresses instead of the values held in the EmailAddresses property of the mailbox object.


PowerShell pipelines can format output to a file to be used for reporting purposes. For example, we can create a list of all Inactive Mailboxes from the United States, sorted by the last changed date and the output formatted:

Get-EXOMailbox -InactiveMailboxOnly -PropertySets All | Where UsageLocation -eq 'United States' | Sort-Object WhenChanged | Select-Object DisplayName,WhenCreated,WhenChanged | Export-CSV c:\reports\InactiveUSMailboxes.csv -NoType


We can also pipe output to the Out-GridView cmdlet to see the data in a pop-up window:

Get-EXOMailBox | Out-GridView
PowerShell, Piping and Exchange Online Mailbox Management
Figure 3: Basic output using Out-GridView.

A useful feature of Out-GridView is to use the PassThru switch which allows an operator to select values and pass only those back to PowerShell for further processing by the next cmdlet in the pipeline.

Get-EXOMailbox | Out-GridView -PassThru | Get-EXOCasMailbox | Ft DisplayName,*Enabled
PowerShell, Piping and Exchange Online Mailbox Management
Figure 4: Out-GridView selections to be passed back to the pipeline.

Clicking OK on the pop-up box passes the selected mailboxes for processing by Get-EXOCasMailbox to display which properties a mailbox is allowed to connect on:

PowerShell, Piping and Exchange Online Mailbox Management
Figure 5: Get-ExoMailbox output for the mailboxes selected from Out-GridView
PowerShell, Piping and Exchange Online Mailbox Management
Figure 6: Get-EXOMailbox output for the mailboxes selected from Out-GridView


The PowerShell pipeline combines singularly useful cmdlets together to process data. Used intelligently, the pipeline is a great way to process data through a series of steps to automate common administrative operations. Mastering the pipeline, or at least becoming comfortable with pipelining cmdlets, is an essential skill for anyone using PowerShell to manage Microsoft 365 tenants.

About the Author

Damian Scoles

Damian Scoles is an eight-time Microsoft MVP, specializing in Exchange, Office 365 and PowerShell. He is currently based out of the Chicago area and started out managing Exchange 5.5 and Windows NT. He has worked with Office 365 since BPOS and has experience with Azure AD, Security and Compliance Admin Centers, and Exchange Online. Contributions to the community include helping on TechNet forums, creating PowerShell scripts that are located in the TechNet Gallery, writing detailed PowerShell / Office365 / Exchange blog articles (https://www.powershellgeek.com), tweets (https://twitter.com/PPowerShell) and creating PowerShell videos on YouTube (https://www.youtube.com/channel/UClxHtLF0c_VAkjw5rzsV1Vg). He has written five PowerShell books and is actively working on the Microsoft 365 Security for IT Pros book as well.


  1. jeff

    I don’t believe the set-exomailbox cmdlet exists, unless I can’t find it in the documentation.

  2. Vic

    I’ve figured it out. Thank you so much for your help!

    Get-EXOMailbox -ResultSize unlimited | Foreach-Object { $EmailAddresses = $_.EmailAddresses;$TrimmedEmails = @();Foreach ($EmailAddress in $EmailAddresses) { if ($EmailAddress -like ‘sip*’) { $Email = $EmailAddress.split(‘:’)[1]; $TrimmedEmails += $Email}}; $_.EmailAddresses = $TrimmedEmails;Return $_} | Select-Object DisplayName, RecipientTypeDetails,@{N=”EmailAddresses”;E={[string]::Join(“,”,$_.EmailAddresses)}} | Export-CSV “C:\Reports\SIP_Address_Report.csv” -NoTypeInformation

  3. Vic

    The following script is working great when viewing the output as a grid:

    Get-ExOMailbox -ResultSize unlimited | Select-Object DisplayName, RecipientTypeDetails,EmailAddresses | Foreach-Object { $EmailAddresses = $_.EmailAddresses;$TrimmedEmails = @();Foreach ($EmailAddress in $EmailAddresses) { if ($EmailAddress -like ‘sip*’) { $Email = $EmailAddress.split(‘:’)[1]; $TrimmedEmails += $Email}}; $_.EmailAddresses = $TrimmedEmails;Return $_} | Out-GridView

    However, I’m struggling to figure out how to properly export the output to a CSV file. Under the EmailAddresses column, the output is the following:


    The values under DisplayName and RecipientTypeDetails are correct. Does the join operator need to be utilized somewhere or am I on the wrong track?

Leave a Reply