In Visual Studio 2013 Update 4 (and Update 5 CTP 2), Tools / Connect to Microsoft Azure Subscription is failing immediately for me with an error:
"An error occurred during the sign in process: authentication_ui_failed: The browser based authentication dialog failed to complete for an unkown reason"
Any idea how to solve this problem? I can sign in through the Azure Portal just fine. I also tried adding a New Deployment in an Azure web project. It brings up the Deploy to Resource Group dialog but doesn't show anything in the Subscription pull-down. When I choose Manage in that menu, it brings up the Manage Microsoft Azure Descriptions dialog which shows I have a subscription with Subscription ID and User Account filled in with reasonable info.
There are several other places in VS to connect to Azure (eg, Server Explorer pane) but they all fail exactly the same way.
Someone else in my company is able to connect his VS 2013 to the same Azure subscription, though as a different user of course. His brings up a Connect to Visual Studio dialog. I think mine is trying to as I see a rectangular flash about the same size as this dialog an instant before getting the error message.
It appears that it is trying to access my Visual Studio account and that's failing. If I try to log out of it and back in, it displays a broken web page ("This page can't be displayed.") in a window with the URL: https://app.vssps.visualstudio.com. I tried visiting this page in Firefox, my default browser, and it loaded the page just fine. However, when I tried it in IE 11 I got the same "This page can’t be displayed" error page. I guess I need to focus on eliminating this problem first.
Any ideas on how to get past this?
I was able to resolve this problem by resetting Internet Explorer's settings to defaults. Then IE could load https://app.vssps.visualstudio.com. VS 2013 was then able to connect to Azure.
I got the same error. Issue was in IE Security settings TLS 1.x were unchecked.
Just selecting TLS 1.x solved the issue.
Try to turn off any Anti Virus softwares you have ON - that's what worked for me.
Related
I installed the Azure Tools plugin (version: 0.0.4) for VSCode (version: 1.27.2). I have no proxy setting in my system. I validated it by running the command in cmd : netsh winhttp show proxy and found
Direct access (no proxy server).
I tried to login into Azure using the Azure Tools option present in the side bar, which caused a pop up to open at the bottom right corner. I clicked on the button with Copy and Open option which opened a browser instance where I copied the password details, post which when I came back to the VSCode window and then I see that I am still not logged in. I tried the above process multiple times but see the same again and again.
Can anyone help me to get some guidance on this to fix the issue?
I had a similar problem and for me was the latest Azure Account plugin version 0.9.10. It doesn't work.
I reinstalled the previous version 0.9.9 and now the login works again.
I can't reproduce it with Azure Account extension (0.4.3) for VSCode (version: 1.27.2).
If azure cli is installed, please have a try to use az login to check whether it can login. If you can login with az command then close the VS code and open it to try again.
I had a similar problem.
I am a member of several tenants for various orgs.
By updating my tenant Id in the Azure Account extension settings I was able to sign in.
I suspect I will have to update it when I want to work in a subscription owned by another tenant.
I ran into a similar issue when trying to login and extract an API from API management. Using Azure Sign In or Azure Login would open up the popup but the callback URL would not trigger a sign in VS Code. I tried everything to the point of reinstalling VS Code.
After messing around with the different Azure Sign In options, I finally got an error when trying to sign in to Azure Cloud. The error mentioned that my admin requires the use of a device code. Unfortunately this error is neither shown nor handled when using the default Azure Sign In command.
The fix for me was to expressly sign in using Azure Sign In with Device Code.
I can reproduce, It does not work on Ubuntu,
no matter what I do.
I gave up, and moved to windows.
So 1:0 for Microsoft :-)
If something does not work with Azure:
try with windows
try with Edge
Its painful truth - they only support software they already own. Which make sense business-wise.
I have an azure webjob that was deployed few days ago and it seems that it was working normally. Since this morning, if I'm trying to access the azure webjob through the new portal, I'm getting a strange error message: Error loading part...
Does someone knows how this can be "debugged"?
Thank you
Evdin
Many of the Azure users are facing this issue due to migration from Old portal to New portal. As the new portal is still in preview it's better to use old portal if you face any issue in new portal.Also, raise a support ticket to inform microsoft so that they can work on your problem.
I have been experiencing numerous problems with the Azure portal today. First and foremost continous deployment stopped working so, I've been unable to update my web apps.
But I'm also getting: "Error loading part..." in several other areas. I can only recommend creating some buzz, so Azure is alerted to the issues.
If you see these type of errors in IE you can press F12 to see the errors.
Chrome/Firefox can also show HTTP message details.
I am also seeing errors in the new portal.
I was trying to see azure website and I saw "error loading part" errors.
Microsoft_Azure_Billing] 9:30:19 AM MsPortalFx.Base.Diagnostics.ErrorReporter 2 message: Access is denied.
[WebsitesExtension] 9:30:19 AM MsPortalFx.Base.Diagnostics.ErrorReporter 2 message: Access is denied.
New portal is in preview but is no longer optional as many of the services are only available in the new portal. Azure support should be informed to make them aware of this issue.
It seems that the issue is now fixed but I see another strange issue now - the webjob that I described above is showing as "running on demand" in the new portal (I didn't set it up like this) and is showing as "running every six hours" in the old portal (this is how I set it up)... So it seems that everything is screwed overthere...
Thank you for your responses and your help.
Evdin
I'm having a pretty strange issue with Azure tools for VS 2013 (version 2.6). Whenever I try to sign in to my Azure subscription (e.g. from Server explorer or creating a new web role project) I get the following error:
Server Explorer
An error occurred during the sign in process: User 'foo#gmail.com' returned by service does not match user 'bar#outlook.com' in the request
OK
My subscription owned by 'bar#outlook.com' and I can perfectly fine sign in either to management portal in a browser (IE, Spartan and Chrome) - as well as in the Power Shell. Tried everything - cleaning up browser caches/cookies, resetting IE settings, playing with different IE security settings - nothign works.
Any help is appreciated - this issue drives me crazy.
P.S. I'm on Windows 10...
I had the same problem. Imported the certificate manually and everything worked ok: https://social.technet.microsoft.com/Forums/en-US/9cdafeb4-f459-436d-b2b8-9bc5c01f0df1/azure-tools-for-vs-cant-sign-in-to-subscription?forum=windowsazuredevelopment
I had this issue, to resolve it I:
Added 'foo#gmail.com' as an alias in my 'bar#outlook.com' Microsoft account, via account.live.com
Made the 'foo#gmail.com' email address the primary alias for my Microsoft account
I could then log in successfully in to Azure by pressing the Connect to Microsoft Azure button in the toolbar of the Server Explorer in Visual Studio 2013 and see all of my websites under the App Service node.
(When I'd used the certificate method described in the other post and Microsoft documentation I'd been able to see all my sql databases etc. but not the websites.)
Once I'd done all that I then switched my primary alias back to 'bar#outlook.com' and server explorer carried on working.
NB: If you're experimenting with this beware that there is a limit on how many times you can switch your primary.. as I have just discovered.. and now my primary is stuck on the wrong email address for a week.
NB2: If your connecting in order to be able to remote debug the website, then this can still be done by going to Visual Studio>Main Menu>Debug>Attach To Process, and then enter the URL of the site (without the http bit, e.g. mysite.azurewebsites.net) as the Qualifier and then attach to the w3wp.exe process.
I am having the exact same issue. It seems that the Azure sign-in in Visual Studio is redirecting to our organizational Single Sign-On instead of the Microsoft one. I have managed to work around this problem by using a Microsoft account that is not tied to my organization:
Create new Microsoft account or use an existing account not associated with your organization
In https://manage.windowsazure.com select Subscriptions/Manage Administrators
Choose Add+ and add the new Microsoft account as administrator to your subscription
Log on to Azure using the new account from Visual Studio
/Morten
I changed my Microsoft account's email address and had this problem. Adding an alias did not help.
The problem is to do with the Azure Active Directory Library for DotNet. For whatever dumb reason, they throw an exception when Azure returns an ID different than the one requested (if the server isn't crying about it, why make up an error and make the client deal with it?).
Since Azures's support was no help, I had to build a custom copy of the ADAL with that moronic exception removed and an assembly version matching the one used in VS2013 (2.11). Also importantly, disable strong name verification for the custom assembly.
I'm following this tutorial here
http://www.windowsazure.com/en-us/develop/net/tutorials/get-started/#nextsteps
I'm at step 3. I click import, I can see I'm signed in with my MSDN ultimate account (I get $150 per month to spend on Azure). I then click New, and when the dialogue opens I cannot enter anything (all boxes are disabled), along with an error message in red:
http://gyazo.com/17eb15f07d54e2867cd5f21d377f04aa
Why is this? It is something with my MSDN account?
You can get also this problem if your MS account is registered with more than one Azure subscription. It appears Visual studio gets confused if your account is attached to more than one subscription and tries to use the wrong one for accessing the Azure API.
If it occurs you need to ignore the advice from #Dev Trails and instead do the following:
In Server Explorer, right-click Windows Azure node > Manage Subscriptions
In the Certificates tab Import a new subscription certificate (this will take you to the current link on the Azure portal to download your
certificate)
In the Subscriptions tab, on the specific subscription that fails,
select the drop-down and choose the certificate instead of the
username.
Refreshing the Azure explorer should now show your databases etc without error.
This is a bug in Visual Studio 2013. Found an answer posted here:
To workaround the issue, you can try the following:
In Server Explorer, right-click Windows Azure node > Manage Subscriptions
If you are signed-in to Azure, you will see the same subscription show up both in the Accounts tab and in the Certificates tab. Remove the one in the Certificates tab.
VS 2015: delete all MS Account from VS. Add once again.
Windows Azure Web Sites shows a red exclamation mark and when I hover over the exclamation mark I see 'The portal cannot load the management data for this resource type'. I am not able to click on Web Sites to add new web sites. I am able to manage other azure resources such as Cloud Services.
Any ideas on what could be causing this and how to rectify would be great.
EDIT: I have tried CTRL+F5, F5, signing out and back in and trying again after 24 hours and different browsers and the problem still occurs.
I contacted Microsoft about this and eventually they solved the problem. There was nothing that I could do, it was something they needed to fix on their side.
This happens from time to time with all the services. Just refresh the portal (Ctrl+F5) and shall be OK. Usually happens on slow internet connections, but I've seen this behavior on a decent speed also.