This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Office 365 Exchange 2016

Trying to setup the connection between Office 365 and On-Premise Exchange 2016. In order to move from On-Premise to Office 365.

However, from Office 365 unable to reach On-Premise Exchange Server. I have setup the Exchange General Rule, using the SSL cert and configured path specific routing to point to the internal Exchange Server with Authentication = None

OWA from external is working just fine.

What am I missing?

This thread was automatically locked due to age.

0 Keyur over 5 years ago

Hi Paul Digby

I would request you to check with this article - https://community.sophos.com/kb/en-us/132291
Cancel
Vote Up 0 Vote Down

Cancel
0 Paul Digby over 5 years ago in reply to Keyur

Which one of the files do you think I should import for what is needed?
Cancel
Vote Up 0 Vote Down

Cancel
0 Paul Digby over 5 years ago in reply to Paul Digby

I have imported the 'all'

So of the 100 exceptions, which ones do I enable for what I am trying to do? Surely not all 100?
Cancel
Vote Up 0 Vote Down

Cancel
0 Paul Digby over 5 years ago in reply to Paul Digby

Also, are these Web Exceptions for LAN to WAN?

I do not see any traffic coming in for this issue.

Has anybody else got O365 to communicate to an on-Premise Exchange Server to allow migration of On_premises mailboxes to O365?
Cancel
Vote Up 0 Vote Down

Cancel
0 wineoh over 5 years ago in reply to Keyur

Are those exceptions updated since September 2019? Microsoft has certainly added more addresses by now?
Cancel
Vote Up 0 Vote Down

Cancel
0 Keyur over 5 years ago in reply to wineoh
Hi wineoh

Note:

The exception created does not bypass the policy checks. If it is required to bypass the policy checks, enable the Policy Checks option under the Skip the selected checks or actions section.

The exceptions provided in this article are the base exception. Microsoft continuously updates its IP addresses and domains. Please refer to Office 365 URLs and IP address ranges for an updated list and refers to the article Sophos UTM/Sophos XG Firewall: Regular expressions for defining URL patterns for information on regex commands.

How to use API to import web exceptions - https://community.sophos.com/kb/en-us/132760
Cancel
Vote Up 0 Vote Down

Cancel
0 Paul Digby over 5 years ago in reply to Keyur

From having looked at the link and looking at all the policy exceptions I imported Number 2 + Number 10 appear to be missing from the imported exceptions. So yes, it seems more have been added since September 2019.

I am trying to get Office 365 to connect to On=premise Exchange Server. I have found the three articles below which detail the Microsoft Requirements to get it to work. Am going to read again tonight to see if I can make any sense of it. I was hoping somebody would be able to say what exactly they did to get their migration to work from on-premise to O365. But alsa, not so far.

I may just create a Business Rule to allow Https in and point directly to the On-Premise Exchange Server as a test to see if that works.

Office 365 URLs and IP address ranges
https://docs.microsoft.com/en-gb/office365/enterprise/urls-and-ip-address-ranges?redirectSourcePath=%252fen-us%252farticle%252fOffice-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#BKMK_EXO

Hybrid deployment prerequisites

https://docs.microsoft.com/en-gb/exchange/hybrid-deployment-prerequisites?redirectedfrom=MSDN

Network ports for clients and mail flow in Exchange

https://docs.microsoft.com/en-gb/Exchange/plan-and-deploy/deployment-ref/network-ports?view=exchserver-2019
Cancel
Vote Up 0 Vote Down

Cancel