Another Office 365 question, this one concerning domain names and client access urls.
We currently use the following (and obviously modified) domain names / urls for Exchange client access:
- outlook.abc.cc (for Exchange 2010 CAS array - not resolvable from the Internet per best practices)
In fact, this domain is not resolvable at all from the Internet in general.
Internal use only (although it is a valid top-level domain (not .local or .private)).
You have to connect to the internal network via multiple forms of authentication and only then can you access your virtual desktop (and Outlook in particular).
Web access (OWA) is not used (internally or externally).
Mobile devices are managed with 3rd party software which I will not address in this post.
So... how do we receive email if the domain "abc.cc" is not resolvable?
We use domain name "xyz.org" which is associated with MX/A records for mail delivery.
The (gradual) move to Office 365 requires us to use a domain name that can be resolved externally so we will use our xyz.org domain.
Internally, we have added a UPN suffix for xyz.org so users can logon as email@example.com as well as the pre-Window 2000 logon: abc\jdoe
As for Exchange client access, I am planning to use the following urls:
We would add these names to our SSL certificate (in fact, obtain a NEW SSL certificate with the additional names).
I would then make these the external url in OWA (etc.) although it will be a moot point for OWA - unused -but maybe necessary for Exchange Web Services depending how that all interacts with Office 365.
What about Outlook Anywhere?
I'm thinking of simply using: mail.xyz.org
Exchange 2016 apparently allows us to specify a different internal and external url (like OWA) but with Exchange 2010 this is not the case.
Does that make sense? Look doable?
I understand there's much more to do (ensure communication between O365 and on-premises via our firewall) but for now I just wanted to run the url choice by the
forum embers to see if I was not overlooking something.