Have you ever wondered how you can connect to 2 Exchange Online sessions, in the same PowerShell window?
For example, if you want to run a script that connects to 2 tenants, exports all mailbox permissions from one tenant and imports them into the other. Same thing applies to Distribution groups and memberships.
With the Microsoft Tenant 2 Tenant Migrations in high demand, and because there are so much that you might want to bring from one Exchange Online to the other, I thought I should write a quick blog article on how to connect and manage 2 Exchange Online tenants in one PowerShell window, ideal for scripting.
Before you look at the code below, let me outline two key parameters, of the Import-PSSession cmdlet to achieve your goal:
- Prefix – Specifies a prefix to the nouns in the names of imported commands.
Use this parameter to avoid name conflicts that might occur when different commands in the session have the same name.
For instance, if you specify the prefix Remote and then import a Get-Date cmdlet, the cmdlet is known in the session as Get-RemoteDate, and it is not confused with the original Get-Date cmdlet.
- AllowClobber – Indicates that this cmdlet imports the specified commands, even if they have the same names as commands in the current session.
If you import a command with the same name as a command in the current session, the imported command hides or replaces the original commands. For more information, see about_Command_Precedence.
By default, Import-PSSession does not import commands that have the same name as commands in the current session.
Note: Both the definitions above were taken from the Import-PSSession cmdlet official Microsoft article, that you can see by clicking here.
So how does this work actually? Have a look at the code below:
<# .NOTES Author: firstname.lastname@example.org,uk Date: October 4th 2017 Version: 1 .SYNOPSIS This lines of code will connect 2 PowerShell Exchange Online sessions to 2 different tenants. .DESCRIPTION By opening 2 PowerShell sessions, using the PREFIX parameter for each one of those sessions it will allow you to manage both tenants at the same time (ideal for tasks where you want to migrate configurations from one tenant to the other) #> ### Input source and destination credentials $SourceCred = Get-credential -message "Please Enter your SOURCE tenant credentials" $DestCred = Get-credential -message "Please Enter your DESTINATION tenant credentials" ### Create Source EXO Session $SourceSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -AllowRedirection -Authentication Basic -Credential $SourceCred $result = Import-PSSession $SourceSession -prefix SRC -AllowClobber ### Create Destination EXO Session $DestSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -AllowRedirection -Authentication Basic -Credential $DestCred $result = Import-PSSession $DestSession -prefix DST -AllowClobber ### Run a get-mailbox to validate connection to both tenants Write-Host "Listing mailboxes in the source tenant" -ForegroundColor Green Start-Sleep -s 5 Get-SRCMailbox -resultsize unlimited |ft alias, *smtp* Write-Host "Listing mailboxes in the destination tenant" -ForegroundColor Green Start-Sleep -s 5 Get-DSTMailbox -resultsize unlimited |ft alias, *smtp* ### Showing a count of mailboxes in source and destination Write-Host "Counting mailboxes in the source tenant" -ForegroundColor Green Start-Sleep -s 5 (Get-SRCMailbox -resultsize unlimited).count Write-Host "Counting mailboxes in the destination tenant" -ForegroundColor Green Start-Sleep -s 5 (Get-DSTMailbox -resultsize unlimited).count ### LISTING PS SESSIONS Write-Host "Your list of active PS Sessions" -ForegroundColor Green Get-PSSession |fl
Some considerations of the code above:
- There’s no logging or error handling in the code. The purpose of the code above is to provide you the insight on how to connect to 2 sessions with the same cmdlets.
- The code is provided as is and you should test it before you run it in production.
- The code includes blocks to perform the following:
- Request input for source and destination credentials
- Create the source Exchange Online session
- Create the destination Exchange Online session
- Code to demonstrate how to run cmdlets in the source and destination tenant (example with get-mailbox)
- Code to list both PS Sessions created
Now lets see the output of the code:
Simple, right? Again this can be very useful for tenant to tenant migrations.