<div>
you need to create send connector on exch 2016 server to point to gmail for same SMTP domain and under accepted domain, convert your SMTP domain to internal relay domain<br />
Also you need mail enabled users for all gmail users on exchange on premise servers where target address and user primary SMTP address is same<br />
Then if your migrated mailbox user send mail to mailbox on gmail, 1st exchange will try to resolve mailbox on premise, if on premise mailbox is not available and mail enabled user found, Exchange will relay that message to gmail via send connector<br />
Just ensure that gmail will allow mail from same SMTP domain (on premise) <br />
Internal relay connector<br />
<a href="https://technet.microsoft.com/de-de/library/bb124423(v=exchg.160).aspx" rel="ugc">https://technet.microsoft.com/de-de/library/bb124423(v=exchg.160).aspx</a>
</div>


<div>
That is the document we followed. &nbsp;All mail stopped delivering. &nbsp;I opened a case with MS and the tech says it was not possible to do.
</div>


<div>
which document you have followed, it talks only about relay domains?<br />
<br />
If you could explain what exact configuration you done so far?
</div>


<div>
We have Gmail set to send mail to Exchange. &nbsp;That works. &nbsp;We added another send connector. &nbsp;We added the domain relay.ourdomain.com and have it, our main domain and two other domains that we used for other parts of our business as acceptable domains. &nbsp;Any user that has been migrated to Exchange can send and receive externally, no issue. &nbsp;They can receive mail from users both migrated and still on Gmail. &nbsp;However, they can only send to the Exchange mailbox. &nbsp;It ignores the new send connector relaying through Gmail. &nbsp;Gmail has been configured to allow the relay. &nbsp;The connector has to be working in some fashion or else no mail would be transmitting.
</div>


<div>
have to changed your accepted domain to internal relay on exchange server under accepted domains?<br />
<br />
Else this scenario will not work
</div>


<div>
I don't know why your mail flow was not worked.<br />
<br />
Just I seen the below article and it is saying same thing which I post earlier<br />
<a href="https://blogs.technet.microsoft.com/weiyumao/2015/04/21/mail-flow-coexistence-between-gmail-and-exchange-online-during-mailbox-migration-phase/" rel="ugc">https://blogs.technet.microsoft.com/weiyumao/2015/04/21/mail-flow-coexistence-between-gmail-and-exchange-online-during-mailbox-migration-phase/</a><br />
The internal relay domain type is discovered because of cross platform migrations only with same SMTP name space at source and target
</div>


<div>
We completed the migration, so no further assistance was needed.
</div>


<div>
<div class="content wysiwyg-content">
We are moving from G-suite to an on-premises Exchange server. &nbsp;I was able to configure Gmail to sent mail to both the Gmail account and the Outlook account, so incoming messages are in both mailboxes. &nbsp;The issue we're having is when a user that has been migrated sends a message to someone who has not, the message is not delivered to the recipients Gmail account so they never receive the message. I've attempted using a send connector to relay to Gmail, still only delivers to the Exchange mailbox. &nbsp;I've attempted to redirect, but since both have the same domain, it still only delivers via the Exchange to Exchange mailbox. &nbsp;<br />
<br />
Does anyone have a solution that would allow internal messages to be delivered to both the Exchange mailbox and the Gmail inbox? &nbsp;We are using O365 licensing and are having trouble rolling out to users who do not have admin rights to their PC's. &nbsp;So we've been delayed on getting this pushed out. &nbsp;Our corporate office has been manually upgraded but we still have 31 remote sites to find a way to roll out.
</div>
</div>


We are moving from G-suite to an on-premises Exchange server.  I was able to configure Gmail to sent mail to both the Gmail account and the Outlook account, so incoming messages are in both mailboxes.  The issue we're having is when a user that has been migrated sends a message to someone who has not, the message is not delivered to the recipients Gmail account so they never receive the message. I've attempted using a send connector to relay to Gmail, still only delivers to the Exchange mailbox.  I've attempted to redirect, but since both have the same domain, it still only delivers via the Exchange to Exchange mailbox.  

Does anyone have a solution that would allow internal messages to be delivered to both the Exchange mailbox and the Gmail inbox?  We are using O365 licensing and are having trouble rolling out to users who do not have admin rights to their PC's.  So we've been delayed on getting this pushed out.  Our corporate office has been manually upgraded but we still have 31 remote sites to find a way to roll out.

Gmail to Exchange On-prem 2016 migration

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite. Although often used mainly as an email application, it also includes a calendar, task manager, contact manager, note-taker, journal, and web browser.

Outlook

Google’s Gmail is a free email service that allows users to access their email on the web or by using third-party programs that synchronize email content through POP or IMAP protocols.

Gmail

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.