PowerShell - Connecting to ExchangeOnline - Can no longer add/enable Remote Routing

Question

PowerShell - Connecting to ExchangeOnline - Can no longer add/enable Remote Routing

HoughtonJason-4020 50

First time posting,

Last year I could use the following command on an account without issues (we are a hybrid migration of O365):

Enable-RemoteMailbox TEST -RemoteRoutingAddress ******@OurDomain.mail.onmicrosoft.com -PrimarySmtpAddress ******@OurDomain.org

nor can I even try to set the remote routing with this command:

set-remotemailbox -identity ******@OurDomain.org -RemoteRoutingAddress ******@OurDomain.mail.onmicrosoft.com

Now I cant, I get some error about it not knowing the command or some other rubbish.

For obvious reasons I need to have those remote routing addresses added to the account, which is a lot easier than having to get into the Admin Center and type them in one by one.

I know all about the initial set up (not that I have received a new computer or anything, its the same Windows Laptop), as I still haev all of that documented. With the initial set up being:

install-module exchangeonlinemanagement

install-module msonline

install-module azuread

Not that I needed the azuread part, as this the accounts were going to be cloud only accounts via an Import into O365 and then a license assignment that included EOL.

When I open up PowerShell as Admin, and run the command "connect-exchangeonline" I get the box for username, password and the authenticator app passcode, and it signs me in without issue, so I am connected to ExchangeOnline.

So, any ideas why this suddenly doesn't work?

Ive tried using the built in Terminal, powershell 7, and one older version of PS and still get the same error.

Any ideas how I can set the remote routing added to an account once connected to ExchangeOnline

because Im bloody lost as to why this no longer works, even though I obviously get authenticated on connection to it.

Any help is appreciated,

JH

Joseph Tran 665 Reputation points

2025-06-10T12:46:59.9233333+00:00
The reason lead to old commands stopped working may in some of this situation

Enable-RemoteMailbox and Set-RemoteMailbox are classic on-premises Exchange cmdlets. They worked when you were connected to an on-prem Exchange Management Shell or a hybrid session.

In Exchange Online PowerShell (EXO V2 module), many of these older on-prem commands aren’t available or have been replaced.

When you run Connect-ExchangeOnline and connect only to Exchange Online, you don’t get those on-prem cmdlets, so it throws errors like “command not recognized.”

So I have 2 options to recommend for you :

Option 1: Use Exchange Hybrid Management Shell

For managing remote mailboxes in a hybrid scenario, Microsoft recommends using the Exchange Hybrid PowerShell session that connects to your on-prem Exchange Server.

If your hybrid Exchange on-premises server is still available, connect to it and run the Enable-RemoteMailbox and Set-RemoteMailbox cmdlets there.

Option 2: Use the Azure AD or Exchange Online cmdlets with Set-MailUser

In pure Exchange Online, to set or update the RemoteRoutingAddress, you typically modify a mail user or a mail-enabled user attribute.

For example to update the proxy address and external routing you can use :

*Enable-MailUser -Identity ****@ourdomain.org -ExternalEmailAddress user@ourdomain.mail.onmicrosoft.com

This sets the external address to where mail should be routed.

But RemoteRoutingAddress is not a parameter exposed directly in Exchange Online anymore.

Link for references :
-https://learn.microsoft.com/en-us/powershell/module/exchange/new-remotemailbox?view=exchange-ps
-https://learn.microsoft.com/en-us/powershell/module/exchange/enable-remotemailbox?view=exchange-ps

-https://learn.microsoft.com/en-us/powershell/exchange/connect-to-exchange-servers-using-remote-powershell?view=exchange-ps

-https://learn.microsoft.com/en-us/exchange/exchange-hybrid
-https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps

-https://learn.microsoft.com/en-us/powershell/module/exchange/enable-mailuser?view=exchange-ps
HoughtonJason-4020 50 Reputation points

2025-06-10T17:48:18.9733333+00:00

@Joseph Tran Thank you so much, I appreciate you and your answer. I was just about to update this post when I saw your post. But am certainly going through your answers and the links - THANK YOU, seriously thank you. Below is what I was about to post then saw your post:

I opened up PowerShell as admin on my work laptop, then I ran the connect-exchangeonline command and authenticated, and then ran these two commands to add the two MS routes I needed added to the original mailbox:

Set-Mailbox -Identity @MyDomain.org -EmailAddresses @{add="@MyDomain.onmicrosoft.com"}

Set-Mailbox -Identity @MyDomain.org -EmailAddresses @{add="@MyDomain.onmicrosoft.com"}

So my primary is still ******@MyDomain.org and I now have the above two "alias's" now on that Test account. I tested mailflow internally and externally and it works! I was able to login to Test, send and receive email internally and externally.

Is that a good way to do it? Is that better or worse than the Enable-MailUser command you posted about? It did work, so are there disadvantages on using the commands I used?

Basically I want to import/create a bunch of users into O365 and no longer give them an AD account that has to sync over EntraConnect (or whatever its called now), but want/need the mailflow to be just like every other user thats in AD (they have all three alias's) and sync'd via the connect app. Meaning if I import those users from my .csv file and they all get created, I still have to run those two commands against every darn user that was created by the import of that spreadsheet (.csv file), thats a lot of work and no where in that "example sheet" ive downloaded does it have fields for those alternate routes. So im guessing the above is the only way to do it, import/create from the .csv file, and then run those two commands for each and every user in the spreadsheet, correct?

Thanks again, you are a star, J.

Accepted answer

3 additional answers

Your answer

HoughtonJason-4020 50 Reputation points

2025-06-10T17:48:18.9733333+00:00

@Joseph Tran Thank you so much, I appreciate you and your answer. I was just about to update this post when I saw your post. But am certainly going through your answers and the links - THANK YOU, seriously thank you. Below is what I was about to post then saw your post:

I opened up PowerShell as admin on my work laptop, then I ran the connect-exchangeonline command and authenticated, and then ran these two commands to add the two MS routes I needed added to the original mailbox:

Set-Mailbox -Identity @MyDomain.org -EmailAddresses @{add="@MyDomain.onmicrosoft.com"}

Set-Mailbox -Identity @MyDomain.org -EmailAddresses @{add="@MyDomain.onmicrosoft.com"}

So my primary is still ******@MyDomain.org and I now have the above two "alias's" now on that Test account. I tested mailflow internally and externally and it works! I was able to login to Test, send and receive email internally and externally.

Is that a good way to do it? Is that better or worse than the Enable-MailUser command you posted about? It did work, so are there disadvantages on using the commands I used?

Basically I want to import/create a bunch of users into O365 and no longer give them an AD account that has to sync over EntraConnect (or whatever its called now), but want/need the mailflow to be just like every other user thats in AD (they have all three alias's) and sync'd via the connect app. Meaning if I import those users from my .csv file and they all get created, I still have to run those two commands against every darn user that was created by the import of that spreadsheet (.csv file), thats a lot of work and no where in that "example sheet" ive downloaded does it have fields for those alternate routes. So im guessing the above is the only way to do it, import/create from the .csv file, and then run those two commands for each and every user in the spreadsheet, correct?

Thanks again, you are a star, J.

Answer 1

You're absolutely on the right track and it's great to hear mail flow is working internally and externally after your change.

And here is how to Automating This for Bulk Users (CSV Import) by custom CSV template, like this :

DisplayName,UserPrincipalName,Password,Email1,Email2

Test User1,@mydomain.org,YourSecurePwd123,@mydomain.mail.onmicrosoft.com,**@mydomain.onmicrosoft.com

Then Create the users and mailboxes using New-MsolUser or New-MgUser + Set-Mailbox

After import, loop through and add aliases like so:


Import-Csv "users.csv" | ForEach-Object {
    $UPN = $_.UserPrincipalName
    $Email1 = $_.Email1
    $Email2 = $_.Email2

    Set-Mailbox -Identity $UPN -EmailAddresses @{add=$Email1}
    Set-Mailbox -Identity $UPN -EmailAddresses @{add=$Email2}
}

This will bulk-assign aliases automatically.

Link for references :

-https://learn.microsoft.com/en-us/microsoft-365/enterprise/create-user-accounts-with-microsoft-365-powershell?view=o365-worldwide

-https://learn.microsoft.com/en-us/exchange/recipients/user-mailboxes/email-addresses

If you find my answer is helpful for everyone that face the same issye, you could make this answer always on top for everybody to see it when they click in this Q/A

Answer 2

HoughtonJason-4020 50

@ Joseph Tran,

Thank you so much. First things first, of course that second line should have been this:

Set-Mailbox -Identity @MyDomain.org -EmailAddresses @{add="@MyDomain.onmicrosoft.com"}

Just for clarity, when I posted about importing a csv to create the users, I didnt mean via a PS script. Basically I'm using the sample template that you get on the Admin>> Active Users>>Add multiple >> id like to upload a csv file with the user information. I get sent a spreadsheet, and then I copy and paste into the sample sheet I downloaded from the admin center, then upload it.

So Id do that, and then create the csv file and populate it with the data that matches the fields you said?

I did have a question about that. below are the field names, and underneath that is the data fields:

DisplayName,UserPrincipalName,Password,Email1,Email2

User1,@mydomain.org,YourSecurePwd123,@mydomain.mail.onmicrosoft.com,**@mydomain.onmicrosoft.com

Im not sure why I need DisplayName or the Password in either the field name or data. Why do I? Dont I just need the UPN and then Email1 &2 ?

Next, is the script, I get what its doing, looping through using the UPN (ie. ******@MyDomain.org) to identify the account to which the script will add the two routes, but where you have in your script "@{add=$Email1}" and 2, I would still need add the display name to the data field for Email1 and Email2, right? Meaning those two fields I would still need to enter the full ******@mydomain.mail.onmicrosoft.com and ******@mydomain.onmicrosoft.com in the fields of that cvs file, correct?

Sorry if Im being slow, its a lot of accounts and I want to get it right first time. Again, thank you, I appreciate you taking time out of your day to help a stranger figure this out, its very kind and I appreciate it. Best, JH

HoughtonJason-4020 50 Reputation points

2025-06-11T16:23:58.49+00:00

OMGOSH you are A STAR! Yup, did all that, and imported all my users into O365 which didnt give me a single screw up, then created a CSV file using the fields you said, adding both the "new" alias's, and it worked! That is AMAZING...... WOW, very, very HAPPY! :)

Now I have to figure out how to bulk reset passwords to what I want instead of what MS assigns... we have younger people who will never (heck I wouldn't be able to) remember the password... 16 characters of everything.....

Two things I know, because they are now cloud only accounts, I cant use the set-adaccountpassword command i used before. Also, another old script I had wont work because I cant use the Set-MsolUserPassword command anymore. Maybe Update-MgUser No idea why MS removes command, changes commands. I get it if its a vulnerability, but seems its change for changes sake, and thats never good. <sigh... But even if I havr o change them one by one, its still a LOT better than having to create all those accounts one by one... what would have been a HUGE pain in the bum!

I cant thank you enough, and I know it took time out of your day/night to write all that, so please know I appreciate you, and its great to know there are still good guys (and gals) in the world, who would take time out of their life to help a stranger. You are a good human being.

Thank you for being you, and never let the world change or diminish the good in you. I appreciate you SO very much for all your help, being patient and spelling out what I needed to do. Means a lot. My best, and sincerely, JH
Joseph Tran 665 Reputation points

2025-06-11T16:28:15.5+00:00

I'm so happy to hear that from you, but to let the other come and make sure my comment is always on top with them. You can make a move to it that will keep my instruction always on top for the other who is lack out of ideas and find to here but with your verification about my comments, that will help them less painful alot. Also that will support me alot to do this more regularly btw ;)
HoughtonJason-4020 50 Reputation points

2025-06-11T17:55:27.2333333+00:00

Well I can verify that your instructions worked, are very clear, easy to understand and VERY much appreciated. Anything I can do to make this post of more value to you, you only have to ask. Thanks again for being one of the good ones! Best, JH
Joseph Tran 665 Reputation points

2025-06-11T18:57:50.8166667+00:00

I'm glad to hear it from you.

If the reply above helped solve your problem, you can mark it as the Accepted Answer by clicking the "Accept Answer" button located below the response.

Doing this helps others in the community easily find the right solution in the future and also raise my reputation poitn to look more professional.
HoughtonJason-4020 50 Reputation points

2025-06-12T14:59:13.3466667+00:00

Done and done, and as far as Im concerned you really and truly helped me out. Because of Microsoft constantly changing things, making commands no longer work, or just making it harder for tech to do their job, it makes it difficult to do anything. Especially when you know how to do it one way (it was all you were taught or learned by yourself), and now you try what you know and it doesn't work! Thats stressful enough, but then thinking you are going to have to do things one by one and there are many hundreds of accounts that you have to do that to, and only have "x" amount of time... Thats enough to put anyone over the edge.

But then someone steps in and helps and they not only explain how to do it, but also includes the PS script needed, thats AMAZING. So I hope me clicking on that "Accept Answer" does raise it up, but if I could, Id click on it for a hour if it helped you out; and thats because you are good, and helped out a fellow human.

Thank you again. JH

PS: I did figure out how to automate resetting passwords.... Im very happy with myself right now. LOL. Have a happy day. JH
Joseph Tran 665 Reputation points

2025-06-12T16:13:27.0166667+00:00

Well, I like it because when people look at my answer with my high reputation point, it will be more legit for them to believe in and also it may made me look more professional and feel proud too you know ;)
HoughtonJason-4020 50 Reputation points

2025-06-12T17:32:56.5966667+00:00

"More legit", that makes me think there are a lot of people that post either fake junk, potentially malicious items or very misleading stuff, am I right? On the other side of things, you should be proud of yourself, you helped out a complete stranger, who can now do a very laborious task more effectively and with a LOT LESS manual effort... that is a VERY good thing. If there was an appreciate button for you, id click on that too! ;) thanks again, have a happy day, JH

Answer 3

I have scoped down you answer and make it clearly for you question :

-> Do You Need DisplayName or Password?

No — not in the second CSV that’s only used by PowerShell to add aliases.

You only needed DisplayName and Password in the first CSV when uploading to the Admin Center (which handles creating the users and assigning passwords).

Once the users are created, you only need the fields relevant for the script — so your second CSV can be trimmed to just:

UserPrincipalName,Email1,Email2

@mydomain.org,@mydomain.mail.onmicrosoft.com,*****@mydomain.onmicrosoft.com*

...

-> Is the script correct? And how does the data fit?

Yes, this script is correct:

Import-Csv "alias-list.csv" | ForEach-Object {

$UPN = $_.UserPrincipalName

$Email1 = $_.Email1

$Email2 = $_.Email2

Set-Mailbox -Identity $UPN -EmailAddresses @{add=$Email1}

Set-Mailbox -Identity $UPN -EmailAddresses @{add=$Email2}

}

-> And What goes in the CSV?

As your note:

Yes, each Email1 and Email2 value should be the full address (e.g., ******@mydomain.mail.onmicrosoft.com).
There’s no need to include a display name in this second CSV.
Each row is one user; just make sure the values are accurate.

-> So your Workflow it should looks like this steps:

Step 1 — Create users in M365 Admin Center:

Download and populate Microsoft’s sample CSV with fields like DisplayName, Username, and Password.
Upload that CSV in Admin Center > Users > Add Multiple.

Step 2 — Prepare second CSV (for PowerShell):

Create a simple alias-list.csv like this:

UserPrincipalName,Email1,Email2

@mydomain.org,@mydomain.mail.onmicrosoft.com,*****@mydomain.onmicrosoft.com*

...

Step 3 — Run the PowerShell script:

Open PowerShell as admin, connect to Exchange Online:

Connect-ExchangeOnline

Then run the alias update:

Import-Csv "alias-list.csv" | ForEach-Object {

$UPN = $_.UserPrincipalName

$Email1 = $_.Email1

$Email2 = $_.Email2

Set-Mailbox -Identity $UPN -EmailAddresses @{add=$Email1}

Set-Mailbox -Identity $UPN -EmailAddresses @{add=$Email2}

}

-> This will add the two aliases for each user automatically

You don’t need to set @mydomain.mail.onmicrosoft.com as a secondary alias (Exchange Online routes via UPN by default), but it's good practice for hybrid-like consistency.

You can confirm aliases with:

*Get-Mailbox *****@mydomain.org | Select-Object -ExpandProperty EmailAddresses

If aliases already exist, Set-Mailbox won’t overwrite — it just appends.

I hope this information will help you

Answer 4

HoughtonJason-4020 50

Come on, someone else must have run into this issue? How else are you adding a remote route for a user you created in O365? dont tell me you are okay with people having an @mail.onmicrosoft.com email address???????

Share via

PowerShell - Connecting to ExchangeOnline - Can no longer add/enable Remote Routing

3 additional answers

Your answer