Disabling Outlook Anywhere on Exchange 2013

Burgess, Tyler 1 Reputation point
2021-08-10T12:49:39.667+00:00

We'd like to disable Outlook Anywhere access on our Exchange 2013 DAG. We have cleared the "External Hostname" attribute for each server in the DAG under the Outlook Anywhere tab via ECP. However, our internal hostname is the same as the external host name, so I believe this is allowing OA to continue to function from outside of our network.

What are the proper steps in this case to disable Outlook Anywhere without disrupting internal access to Exchange?

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,669 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Andy David - MVP 149.2K Reputation points MVP
    2021-08-10T12:59:54.127+00:00

    There isnt a real good way of doing this.

    If you use this option, OA externally will still work given your using the same host name:

    https://learn.microsoft.com/en-us/powershell/module/exchange/set-casmailbox?view=exchange-ps
    -MAPIBlockOutlookExternalConnectivity
    This parameter is available only in on-premises Exchange.

    The MAPIBlockOutlookExternalConnectivity parameter enables or disables external access to the mailbox in Outlook by removing the external URLs from the Autodiscover response. This setting affects Outlook Anywhere, MAPI over HTTP, and Exchange Web Services (EWS). Valid values are:

    $true: External Outlook clients can't use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox.
    $false: External Outlook clients can use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox.
    Note: If your organization uses the same Autodiscover URL values for internal and external clients, setting this parameter to $true won't block access for external clients.

    Plus:
    https://ingogegenwarth.wordpress.com/2017/01/23/why-using-mapiblockoutlookexternalconnectivity-is-a-bad-idea/

    You probably need to look at a reverse proxy solution instead and do not publish Outlook Anywhere externally:
    https://www.petenetlive.com/KB/Article/0001548

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.