Migration from Outlook To Google - Phased Approach

[MarieM]

Hi @All

I' supporting a small org with their migration to Google from Microsoft. Even though its small, I want to use dual delivery of emails. We are using the same email address, so from the outside there is no disruption. 

I know that the recommended approach is to set up Google as the primary server, but this is not possible yet.

How do I set up so that I could use the test environment in Google?

[MattDV]

Hi @MarieM 

As per your confirmation that Dual delivery using Google as primary, there is the alternate option that is to Legacy server as primary server

Please let me know if this proposed solution works for you

Regards

[MarieM]

Thank you @MattDV 

@

I want to use the legacy server solution, but the email is the same in Microsoft and Google (e.g. name@company.org) I thought that was an issue based on stuff I've read on Microsoft. The alternative solution says to use the test domain, that automatically got set up when we created our domain, but I can't add users there. TheTest Domain Alias is greyed out. Is it because we have a non-profit version, or is there something wrong with the set up?

[MattDV]

Thanks @MarieM for the update, your Workspace account comes with a test domain, but remember that the test is an Alias and not a Secondary domain, so each users in your Google Workspace account is automatically assigned a test domain email address, for more information about the differences you can take a look at Add a user alias domain or secondary domain

For example

• Test domain alias format: domain-name.test-google-a.com
• Test domain email format: username@domain-name.test-google-a.com

If your domain is supertest.com, your test domain aliases are:

Test domain alias: supertest.com.test-google-a.com
Test domain email: janedoe@supertest.com.test-google-a.com

Set up forwarding to users’ test domain alias:

1. Set up mail forwarding on your legacy server. Messages sent to legacy email addresses are forwarded to the person’s corresponding test domain alias. Typically, forwarding rules are set up on a per-user basis.
2. Set up the legacy server as an inbound gateway, following the steps Set up an inbound mail gateway:
   1. Set up Gmail to get a high volume of mail from the legacy server.
   2. Improve SPF check accuracy. Mail coming from an inbound gateway is treated as an internal message. SPF checks are made against the server that sent the message to your legacy server.
3. Send test messages to each user's legacy email address.
4. Verify that users get the test messages in both their legacy server inbox and their regular Gmail inbox.

Regards

[MarieM]

Thanks @MattDV  I have set forwarding, and sent a test email. It has not bounced back, but I don't see it in my inbox. Is there another step? Do I need to link the email?

[MattDV]

Hey @MarieM ,

My first question would be to ask you if you have checked the ELS from your organization

1. Check if the email was delivered to Google.
2. In the Admin console, go to Menu >  Reporting > Email Log Search.
3. Next to Date, select a date range from the list.
4. In the search fields, enter any information you have and click Search.
5. Under Subject (or Message ID), click any of the subjects to see message details and delivery status.

Do you have/see any clue there?

[MarieM]

@MattDV Nothing has been delivered. Could it be the IP addresses I have set up? 

[MattDV]

@MarieM Could be for different reasons,

PS CMDLETS WILL VARY DEPENDING ON EXCHANGE VERSION

Ensure that at least one of the mailbox have properly forwarding address configured

• Get-Mailbox "USER" | fl ForwardingSMTPAddress,DeliverToMailboxandForward

ensure that Exchange On-prem (I'm assuming because of the conversation) successfully delivered the email 

• From Exchange Shell run: Get-MessageTrackingLog -MessageSubject "Subject" -ResultSize Unlimited -Sender "SENDER_ADDRESS" -Start "DATE" -End "DATE"

If you confirm that have been successfully delivered:

• Ensure and double check this step Set up an inbound gateway

You can refer to the Troubleshooting section for inbound gateway

Regards

[MarieM]

Hi @MattDV Sorry for so many questions

We are not using on-prem exchange. The IP addresses came from a search for our domain. My understanding is Microsoft does not use a static IP address. Is that an issue?

[MattDV · Accepted solution]

@MarieM no problem at all!

That's a fair question, I would strongly suggest to check with them (MS) if there is an specific way to isolate at the minimum the sending IP's that some of your dual delivery users have, because I can see this IP's are published public, but adding the whole range will represent a risk

Office 365 URLs and IP address ranges 

Regards