none
Cannot connect to local TFS Server when VS originally set up using partner license RRS feed

  • Question

  • I have a user who installed VS2017 and is using it as part of the Action Pack Subscription obtained via MS Partner program. This requires that the VS account for licensing be an Office365 account. We use EOP on Office365, so our accounts there have the same email domain as our AD domain.

    The the user tries to connect to our internal TFS server, he gets a Not Authorized message. This is because it is using the Office365 account information and not a user on the local domain. When we try to set up a local domain account on VS to access our local TFS, it keeps trying to validate it against the Office365 users, and that user does not exist there.

    How do we get VS to not go to Office365 and use the local domain AD instead?

    Monday, January 28, 2019 4:51 PM

All replies

  • Hi Mike,

    In general, you can access TFS when the user account is only one in the domain. Unfortunately, since our forum mainly focus on VS IDE issue, have no an appropriate environment to test it for you. 

    Based on your description, it is possible to be associated between the domain setting. We suspect the cause of issue is account conflict between o365 and local account.

    Could you create a local domain account that not to associated with O365 email address and account itself to test it?

    Br

    May 


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com


    Tuesday, January 29, 2019 5:41 AM
    Moderator
  • I already have two different accounts. On o365, it has the person's first and last name @domain name (FirstLast@domain). On our internal server, it is first name last initial @domain name (FirstL@domain). The problem is that when it tries to validate the credentials, o365 cannot find it (FirstL@domain) and gives an error that the user does not exist. I need for it to go to our domain controller and not o365 to validate the user. 

    Given that it has to know where to go to do an AD lookup, what determines which domain controller to use when the same domain name is used at o365 and internal?


    Tuesday, January 29, 2019 2:33 PM
  • Hi Mike,

    The discussion for TFS has moved! Report a problem with TFS itself on Developer Community, provide a suggestion on UserVoice, get advice on Stack Overflow, and get support on TFS Support.

    Best Regards,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, February 11, 2019 3:03 AM
    Moderator