I could connect to the Azure DevOps and the Organization through the browser, however if i browse through My Profile page it does not show up the access to the Organization that i have.
Also it does not list out the organizations while connecting to the Projects from Visual Studio.
Need advice on what has gone wrong.
Related
I am sometimes encountering "TF30063" errors in Visual Studio 2019 when connecting to an Azure DevOps (TFVC) repository.
I am using Visual Studio 2019 (v16.1.4 at the moment) on a Windows 10 Pro (version 1809) workstation. This workstation previously had Visual Studio 2017.
We have a department repository at dev.azure.com, configured as a TFVC repository (not Git). This repository was originally created when Azure DevOps was VSTS, but we weren't using it for anything until recently, after it had been converted to Azure DevOps.
When opening a project that has its source managed in Azure DevOps in Visual Studio 2019, I have been encountering an error like this at times:
TF30063: You are not authorized to access dev.azure.com/[ORG-NAME]
Sometimes the error occurred when opening the project, and at other times when attempting to get the latest version of files or checking files in or out from the Azure DevOps repository.
I have been searching for this issue online for a few weeks, and have tried various suggested solutions, such as clearing the ".IdentityService" folder, or clearing out some specific AppData local/temp folders, or logging out of and back into Azure DevOps, etc. Some of these seemed to resolve the issue temporarily, but the issue always returned.
However, I now believe I know how to reliably cause this issue (and how to resolve it in the short term).
I have discovered that I can reliably cause this TF30063 error in either of two ways:
If I have Visual Studio open with a project connected to our on-premises TFS server, and then I open another instance of Visual Studio with a project that is connected to Azure DevOps.
If I don’t have any other projects open, but the last time that I had Visual Studio open, I left the "Team Explorer" tab selected (for example, because I had just checked in some files), and I open a project connected to Azure DevOps.
In either of the above cases, I will encounter the TF30063 error when I open a project connected to Azure DevOps (either when I first open the project, or when I attempt to perform any source control operations). In either case, the solution is relatively simple, as follows:
If Visual Studio is showing the "Team Explorer" tab/panel, select the "Solution Explorer" tab/panel.
If Visual Studio had already been showing the "Solution Explorer" tab, select the "Team Explorer" tab and then select the "Solution Explorer" tab again.
Make sure that the "Solution Explorer" tab is currently selected, and close this instance of Visual Studio (if I have other Visual Studio instances open that are connected to the on-premises TFS server, I can leave those open).
Re-open the same project (connected to Azure DevOps) in Visual Studio, and now everything seems to be fine.
Does anyone else have any additional information on this TF30063 error with Azure DevOps repositories, or any additional suggestions for resolving or working around the issue?
Please try below and see if it helps.
Close all instances of VS
Delete %localappdata%.IdentityService
Restart VS
another approach:
Close all VS instances.
delete your VS appdata folder and then open VS
Though this will reset all your setting. Hope it helps.
If you still face the same issue , please raise a request in below link.
https://developercommunity.visualstudio.com/content/problem/post.html?space=8
you can do it from here too:
I set up an Azure site years ago and have been making only small changes since, but I've upgraded my PC and now Visual Studio no longer remembers the credentials to deploy the site.
I went into the Azure portal but everything is different now and much more complicated. How do I set up credentials to use webdeploy in the new interface?
If you sign in to visual studio using your azure AD credentials then you can easily deploy web app to azure.
Considering you are signed in to visual studio using your azure credentials then you can go to View->Cloud explorer
You should be able to see available subscriptions here
While creating a SharePoint (SharePoint online hosted) app in Visual Studio 2015, I used my organization-issued personal account. While signing-in I accidentally checked the Remember me box.
And now, for another project, I have to log-in again using different credentials, which has administrator privileges. But, the sign-in page never shows up now.
I tried clearing internet explorer cache, repairing Visual Studio, reinstalling/updating SharePoint plugin etc., but nothing worked. It automatically logs me in using my personal account.
I tried finding keys in Windows Credential Store in Control Panel, but was unable.
Any help is greatly appreciated.
We had a very similar problem as such you were not able to connect to Team Foundation Server with your own credentials.
To solve this problem
Open the Credential Manager in Control Panel
Edit the Generic Credentials to be your own account
Close and open Visual Studio 2015
Reconnect to TFS
Enter your credentials in prompt poping up
Note: Do not forgot to uncheck the option "Remember my credentials" to force to ask credentials for every TFS connections.
Now, you will be able to connect to Visual Studio 2015 with your account from now on.
We have On-Premises Team Foundation server 2013. We are planing to use the Visual Studio Team services.
Can we use the on-premises TFS user account for Visual Studio Team services?
On premise TFS accounts will be based on local active directory while VSTS you can have users with microsoft id or users in Azure Active directory. So if you migrate the users to azure active directory or sync local AD to Azure AD using Azure AD connect you should be able to achieve the functionality you are looking for.
Nowadays it is possible to use Visual Studio Team Services from Microsoft Azure with Organization account, without having to have Microsoft Account. This is nice feature and we use it in our organization. However it seems that we are not able to activate / use Sign in to visual studio button and login with Organization account, because only Microsoft account prompt is shown.
Is it possible, and if so, how to login/sign-in/activate Visual Studio 2013 desktop program with Azure Organization Account instead Microsoft Account ?
Visual Studio Team Services is different service from VIsual Studio Desktop.
As of Today I am not aware of the possibility to sign-in to Visual Studio Desktop with OrgID. However, you absolutely will have no problems signing in to your Team Services using OrgID and use the Team Services from within the Visual Studio Desktop IDE.
Last but not least, Sign-in to Visual Studio IDE provide service that is absolutely different and has nothing to do with the Team Services.
Just one of all the features the "Visual Studio Sign-in" provides, is to automatically sign you in to your Team Services account. But if your Team Services account is an OrgId, then you will have to use the OrgId when accessing the Team Projects. That's it. There is no restriction on accessing the team projects.
UPDATE
Almost two years after the original answer, it is now possible to login to Visual Studio Team Services using Organisational Accounts. Check more here.
You can now sign in to the Visual Studio client/IDE with Microsoft accounts or work/school accounts (formerly organizational accounts). Previously, you could only sign in to the Visual Studio client with a Microsoft account.
Set up Visual Studio with Team Services
I haven't tested it myself, but you should be able to do this. You just need to jump through a few hoops to do it.
Here is an excerpt from the MSDN FAQ:
Q. Can I use an Organizational account with my MSDN subscription?
You must use a Microsoft account to activate your MSDN subscription, but you can then link your benefits to your Organizational account through the My Account portal. This way, you can use your benefits with Visual Studio Team Services accounts that were either created or set up with Azure Active Directory to support Organizational accounts. You get the same level of benefits whether you use an Organizational account or a Microsoft account.
The FAQ also explains that there is actually a benefit to doing this, as it reduces risk for the business. The reason is that the business have control over the assets created by the organizational account, and as I understand it, it's easier for the business to transfer the MSDN benefit to another account when using organizational accounts.