Starting two weeks ago i cannot not login to vso using my account, i got this message
"VS400664: Sorry, we were unable to retrieve a configured identity provider for you to use when creating an account. If the problem persists, check your web browser security settings. You may need to add https://tfsprodch1acs01.accesscontrol.windows.net to your trusted zones.
Refresh"
Note that i can access using google chrome, but this error come just in internet explorer (8) or from visual studio when try to login,
when i try to browse to https://tfsprodch1acs01.accesscontrol.windows.net using IE i get "Internet explorer cannot display the webpage" but i can browse using chrome.
IE8 is not supported by VSO or TFS 2012+.
Related
I recently did fresh installs of Windows 10 and installed the latest Office 2019 (Office 365). All of my google accounts (free gmail accounts and corporate account) have IMAP disabled and app passwords disabled. I only allow oauth connections to my google accounts. Outlooks refuses to try oauth and only tries IMAP. Prior to Win 10 installs I had Win 8.1 with Office 2016 and it connected via oauth to google emails without issue. I tried on 2 separate Win 10 instances, and then created a fresh Win 10 VM with a fresh Office 2019 install (changed no settings) and behavior across all 3 instances is the same. If I put in a google address it immediately goes to the IMAP page and asks for a password instead of bringing up an authentication to my google account using 2 factor (2FA). Additionally I check the box "Advanced options -> Let me set up my account manually" and click on the G (Google) icon and it still doesn't try the oauth authentication - it just goes to the IMAP setup page.
Luckily I was able to get in touch with an MS Office support team - if anyone else experiences this issue it has to do with the Office updates channel. If you are a developer it defaults to a channel that doesn't support oauth. To fix add the registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate]
"updatebranch"="Monthly"
After adding the registry key close all office apps, restart them, go to File -> Office Account -> Update Options - > Update Now and it'll install the missing files.
I have TFS 2018. I'm trying to connect visual studio 2019. I can already use tfs via web browser. I can log in and everything is fine. But when I try to connect through vs, I can't get authorized. I get
Server 'https://Myserver:8080/tfs' was not added. TF30063. You are not authorized to access https://myserver:8080/tfs
I researched the error code and tried all the fixes including deleting the windows credentials, running vs as admin and others. Like I said, I can log in via my web browser with no problem.
When I try to connect to project, It has my Microsoft account. I enter the above url and I'm prompted for my windows login (same for the browser) and I keep getting the error. I thought maybe I add the account before connecting, but when I try to add an account, the only popup wants me to use a Microsoft account or GitHub account. I can't add my Windows account.
So how do I connect my visual studio to my tfs server?
Thank you.
You should not get a Microsoft Account Prompt if you are trying to connect locally. The prompt is to validate your instance of VS towards your MSDN subscription. You would need to "login" with you Microsoft or Azure AD user that can validate your VS license and to be able to synchronize your settings from one VS to another. This login is the one here
Notice the account settings there, if you click on this you can also add your Visual Studio 2019 Static Key and then you don't need to login every month unless you want to sync your settings.
Bottom line, when connecting to TFS 2018 it will not ask you for Microsoft Credentials.
Please check whether you use the correct URL, and use http instead of https. Also, try the following items:
Close all Visual Studio instances, delete %LOCALAPPDATA%.IdentityService.
Clear TFS caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache
Click Add Azure DevOps Server and add the server URL:
I have a simple task-pane Outlook add-in. When I install it manually (uploading the manifest file) to one account, it works well : on Outlook Desktop, Outlook online, OWA, and the iOS Outlook app.
When I install it to the whole organization through the Microsoft Exchange Admin Center (Organization --> Add-ins --> Add), two stranges behaviors occur :
1) It is immediately deployed to all accounts ; except for the administrator himself (~3 hours of delay before it is deployed !). Why ?
2) Once deployed, the Outlook iOS app support disappears, whereas the uploaded manifest is the exact same file. Desktop, Web, and OWA apps works well. The add-in indeed appears in the "Parameters > Manage add-ins > My add-ins" of each user.
I can't find or explain this problem. Did anyone find a solution or an explanation ?
The delay can actually affect all users. We cache installed add-ins server side for performance improvements.
In terms of the add-in on ios, the scenario of admin installing add-in to mobile is currently not supported. This is in our backlog, and we'll be getting to this soon.
Having trouble adding a Team Explorer server (visualstudio.com) in Xamarin Studio. I enter my credentials (Microsoft account) but nothing happens, and the server is not added in the list of servers. I am using this addin
It seems that you need to enable alternate credentials to be able to log into the server as per this post. See the "Basic auth" section.
I have VS 2008 and Team Explorer, and TFS.
I open VS 2008 using a local administrator (MACHINE\admin). I open Team Explorer to connect to TFS Server using domain user (DOMAIN\user). The login dialog appears when I connect to TFS in Team Explorer (I put login and password).
Now, in my addin, programatically I want connect to TFS.
How can I get the credentials (that I introduce in login dialog in Team Explorer) to connect to TFS ?
Reference:
How to get the active Team Foundation Server and Project from an Add-In
http://blogs.msdn.com/b/hippietim/archive/2006/03/29/563988.aspx
Have you tried:
System.Net.NetworkCredential credential = (System.Net.NetworkCredential)System.Net.CredentialCache.DefaultCredentials;
Aside from that, you could setup an account that the addin could run under using :
new NetworkCredential(username,password,domain)
System.Net.CredentialCache.DefaultCredentials may pass back the admin creds though. In which case, creating an account for the addin to run under would still be an option.