Export (0) Print
Expand All

Configure Support for Blocked External Domains

Lync Server 2013
 

Topic Last Modified: 2012-09-08

If you have configured support for federated partners, you can manage which domains will be blocked from federating with your organization. The list of blocked domains will act as a block list (listing of explicit entries that are not to be allowed) and will apply in federated domain discovery, if you have this option enabled. For details, see Enable or Disable Discovery of Federation Partners.

Block one or more external domains from connecting to your organization. To do this, add the domain to the list of blocked domains.

  1. From a user account that is a member of the RTCUniversalServerAdmins group (or has equivalent user rights), or is assigned to the CsAdministrator role, log on to any computer in your internal deployment.

  2. Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.

  3. In the left navigation bar, click External User Access.

  4. Click Federated Domains, click New, and then click Blocked domain.

  5. In New Federated Domains, do the following:

    • In Domain name (or FQDN), type the name of the federated partner domain that you want to block.
      noteNote:
      The name cannot exceed 256 characters in length.
      The search on the federated partner domain name performs a suffix match. For example, if you type contoso.com, the search will also return the domain it.contoso.com.
      A federated partner domain cannot simultaneously be blocked and allowed. Lync Server 2013 prevents this from happening so that you do not have to synch up your lists.
    • (Optional) In Comment, type information that you want to share with other system administrators about this configuration.
  6. Click Commit.

  7. Repeat steps 4 through 6 for each federated partner that you want to block.

To enable federated user access, you must also enable support for federated user access in your organization. For details, see Enable or Disable Remote User Access.

Additionally, you must configure and apply the policy to users that you want to be able to collaborate with federated users. For details, see Configure Policies to Control Federated User Access.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft