Link to home
Start Free TrialLog in
Avatar of dougdog
dougdog

asked on

shared mailbox cant receive external email or be opened in outlook

we are running exchange online and onprem however we have all mailboxes migrated
we still keep on prem exchange for management relay etc
when we create a new shared mailbox online it cant receive external email and when users are given delegate access they cant open it in outlook and the inbox cant expand
the only way it works is to create the shared mailbox on prem then migrate it to the cloud
this is a lot of extra work and time
is there a better way
can this just be created online
Avatar of Vasil Michev (MVP)
Vasil Michev (MVP)
Flag of Bulgaria image

In general you should have no issues with either cloud-created or migrated shared mailboxes. Can you provide more info on any error messages you are seeing, such as the NDR when sending mail or the Autodiscover query results? Where are you MX and autodiscover records pointing at? If they point on-premises, you will need to have a recipient object representing the shared mailbox there, be it a mail user or contact or whatever. Or you can just create the shared mailbox using the default @tenant.onmicrosoft.com domain.
Avatar of dougdog
dougdog

ASKER

it says the mailbox cannot be found
autodiscover is pointing internal
mx records are at our mail filtering company
So you most likely need to have an object representing the newly created mailbox on the mail filtering company side, right? How are you provisioning those? Did you try with the @tenant.onmicrosoft.com address?
Avatar of dougdog

ASKER

but we need it to accept mail on @company.com
if your MX record is pointing to your 3rd party hosted company, where is the 3rd party pointing, are they pointing to your on-prem exchange or O365?
Avatar of dougdog

ASKER

they are pointing at hosted
By hosted, I'm guessing you mean that your inbound mail 3rd party company is pointing to O365. If that is the case then the shared mailbox should receive mail just fine from external domains, but if your 3rd party inbound company is pointing to your on-prem exchange then you may need an AD object mentioned by @Vasil Michev (MVP) for the shared mailbox so that your on-prem exchange will know where to send the mail.
Avatar of dougdog

ASKER

no sorry 3rd party is pointing at our firewall and internal exchange
Wherever it's pointing, the idea is that you need to have a valid recipient object for it, otherwise mail will probably be rejected. This should easily be verified by checking the actual NDR message received, if any, or doing a message trace.
oh ok, then you will want to create an mailuser object or contact for that shared mailbox so exchange will know where to send it.
Follow Vasil Michev initial advice and that should correct your issue.
Avatar of dougdog

ASKER

so i just need to point now at 365 since all mailboxes migrated?
yes you can point your 3rd party to O365 and that will also correct this issue. that way your on-prem exchange will not get involved. you can also just point your MX record to o365 and not use the 3rd party company. either way.
Avatar of dougdog

ASKER

and if i dont i need to create it on prem first?
are there any gotchas i need to know about before changing
ASKER CERTIFIED SOLUTION
Avatar of timgreen7077
timgreen7077

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial