Office 365 Migrated User can Send Email External but not receive and can't receive internal/external

Where is your MX pointing it should be pointing to Office 365

- Rancy

No currently it is pointing to our external spam filter gateway and then internal as we have everyone internal and are only testing a few mail boxes right now internal and external to make sure mail flows before we repoint.  Is this not possible to test without pointing the MX record.  So it's all or nothing?

Ohk ok but to be able to receive emails on Office365 mailboxes you will have to have some pointing to Office365 as well ..... as if not how will that work

- Rancy

Sounds like you have an MX error, as others have pointed. As part of Office 365, you can open a ticket with them. They are very responsive and will guide you to the proper configuration necessary to make things work in your environment.

can you not test before pointing MX to office 365?

Only way i can think is Adding additional Email address and having forwarding from the current mailbox to Office365 user

- Rancy

Do you have a send connector set up between your environment and Office 365? Hybrid coexistence utilizes proxy addresses when MX records point to your environment. The proxy address is usually set up as user@o365tenantname.onmicrosoft.com. This is normally added to the user account when they are migrated to Office 365, but it might not have been done correctly. Check the proxy addresses attribute on the user and make sure it's set to include the .onmicrosoft.com domain. The send connector should also be set up to send all email that includes the .onmicrosoft.com domain to the office 365 servers.

I do see other e-mail addresses:
budc@tbqc.mail.onmicrosoft.com and budc@tbqc.onmicrosoft.com is that what you mean?
How can I confirm the send connector?

Blah, I'm sorry. I didn't mean proxyaddress. The later of those two should be listed as the TargetAddress property for the user account. If it isn't, you'll need to add it manually. The send connector should just be a send connector that is set up on your exchange transport server that has a scope of tbqc.onmicrosoft.com and is set to send to the Microsoft Online smarthost. Usually that will be domain-com.mail.eo.outlook.com.

So why dont you have contacts for which the Primary email be "@tbqc.onmicrosoft.com" and secondary your own

This will work as a routing of emails to that mailbox

- Rancy

@acbrown2010 how can I confirm it's listed as a TargetAddress property.

I do confirm a connector to exchange online tbqc.mail.microsoftonline.com

You may want to add tbqc.mail.microsoftonline.com to that connector. You can only change the targetaddress attribute authoritatively through ADSI edit, but it can be viewed through the attribute editor tab on the user's account properties in ADUC if you have the advanced features view enabled on a Windows 2008 or later DC. Windows 2003 requires the use of ADSIEdit to view that property.

do you have any instructions on adding tbqc.mail.microsoftonline.com to the connector?
The one I have is Outbound to Office 365

address space tbqc.mail.onmicrosoft.com
Use domain name system DNS "MX"

You are thinking to add to this?

You should either copy that connector with a new one or add tbqc.onmicrosoft.com (note the lack of the word mail there) to the address space.

so on outbound to office 365 properties under address space I have

smtp tbqc.mail.onmicrosoft.com cost 1
smtp tbqc.onmicrosoft.com cost 1 (just added)

is this correct?

Do I need an internal one?

yes, that should work fine. Also, I think having the .onmicrosoft.com addresses in the proxyaddress attribute on your user might be screwing things up. Remove those email addresses from that users' list of addresses and see if mail gets to office 365 for them.

ok done but to clarify under user E-Mail Options
Primary: budc@bergquistcompany.com

other
budc@tbqc.mail.onmicrosoft.com
budc@tbqc.onmicrosoft.com

you say to remove these both?

Yes, remove those and see if mail flows to office 365. If it doesn't, run adsiedit to check his user's account's targetaddress attribute to see if either of those addresses are listed there.

so much closer I can receive from outside now (prior could only send out)

only problem now is cant send/receive to existing on-premise colleagues tracking shows
In Deferral: 451 4.4.0 Primary target IP address responded with: "421 4.2.1 Unable to connect." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or

Ok I think I found a couple things that may be missing:
1. Accepted domains I have 3 listed bergquistcompany.com, tbqc.mail.onmicrosoft.com, tbqc.onmicrosoft.com.  One of these are to be internal relay and the first 2 are false for default so should tbqc.onmicrosoft.com be the relay?  It says to manually configure hybrid routing domain type to internal relay in order for mail flow to work between on-premise and exchange online

ok at the point I can send internally but now can't receive from on-premise or external so can't receive and could receive external at one time