internal external url exchange mac office 365

If you have configured split DNS, you can use the same URLs as externally

You can use this tip for internal servers as well, just use the server FQDN and you'd probably have to ignore the certificate warning (if the server FQDN is not included in the certificate, which is highly probable).

If a server has an issue, you can expect other types of responses than '200 OK' or just a timeout.

Depending on the load balancer configuration resubmitting the request a moment later could result in another server responding.

If you have multiple Exchange (CAS) servers behind a load balancer, you will only get a response from one server at a time.

For instance: if your organization won't allow OWA, then the /owa path is probably not published and this test won't work (externally).

The paths need to be published to the internet, some proxies (like the late TMG) can limit access based on the URL path.

This is something the Managed Availability feature in Exchange 2013 does and the results are indicated in the health check response.

Previously with Exchange 2010, only simple tests were possible, which didn't always tell you if a service was behaving correctly.

This is actually a health check that can be used by Load Balancers in order to check server health, or in this case even protocol health. So, be sure to check whether you separated each protocol per FQDN. While for Outlook Web App this could be something like: if you want to test ActiveSync the URL could be something like: If you've chosen to use a separate FQDN for each Exchange protocol, the external FQDN is then dependent on the protocol. The is something you should know and has to be externally accessible. MAPI for the new MAPI/HTTPS (successor to the RPC over HTTPs protocol used in Outlook Anywhere).Microsoft-Server-ActiveSync for Exchange ActiveSync.Also used by Lync clients, Outlook for Mac etc.)

AutoDiscover for the Autodiscover process (also something that is used by Lync clients).The format would be: If the specific protocol is working correctly, the Exchange server will respond with: 200 OK Well, in some cases you can check this with just a browser.įor each Exchange protocol, there is an URL you can use to check the health. Sometimes you're not at work and you suspect there is something wrong with your Exchange 2013 servers and you can't access your environment remotely for whatever reason.

Internal external url exchange mac office 365