M
Mike Lusicic
Guest
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?
Continue reading...
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?
Continue reading...