Skype for Business – Resource Forest and Surface Hub sign-in

We recently came across an issue where a customer could not sign-in to a Microsoft Surface Hub.

There’s a great article here: explaining how a Resource Forest model works.

When you enable a SfB user, the proxyAddresses attribute is populated with the users SIP address in the format SIP:[email protected]  In a Resource Forest model this is populated on the disabled user object in the Resource Forest.   Usually the attribute flow is one way from the User Forest to the Resource Forest so the SIP: value never populates the proxyAddresses attribute in the User Forest.

To resolve we added the correct SIP: value to proxyAddresses on the Surface Hubs AD account in the User Forest.


Author: Chris Hayward

Share This Post On


  1. Hi Chris,
    have you created a LinkedRoom mailbox in this scenario?

    Post a Reply
    • Hello, no I haven’t although it could be a similar problem where the ProxyAddresses in the User Forest require configuring.

      Post a Reply
      • So how did you create the room mailbox for that account?

        Post a Reply
        • Room Mailbox was in Office 365, the Resource Forest only hosted Skype for Business. Architecture was:

          User Forest – Contained Surface Hub User Account
          Exchange Online – Azure AD Connect sync from User Forest, user enabled as a Room Mailbox
          Skype for Business Forest – Microsoft Identity Manager sync from User Forest, user enabled as a SfB Meeting Room

          Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.