I'm trying to test Azure by publishing a basic web app. After signing in to Azure from Visual Studio, I'm met with the following message:
Sorry but we didn't find any Windows Azure subscriptions associated with your account.
You can sign in with a different account or sign up for a Windows Azure subscription.
I use Windows 8 with an attached ecu account, and have signed up to a trial Azure account under the same credentials (which I can log in to normally fine).
Results[1] from a similar problem suggest the accounts are mixed up, and to contact an admin with the ticketing system to rectify[2]. However selecting "Having issues with sign in or signing up for an account?" links me to a page, which quickly redirects me to another broken page and I am unable to proceed.
What is the best course in action in either:
publishing the app to Azure
contacting Microsoft about fixing my trial Azure account
Thank you
[1] http://social.technet.microsoft.com/Forums/en-US/1b61b9a9-e763-4893-acc1-aa60a7d0b03d/msdn-subscriition-free-access-to-windows-azure-cannot-setup-account?forum=windowsazurepurchasing
[2] http://azure.microsoft.com/en-us/support/options/
Found the answer on social.technet.microsoft.com
I found this article first, so I hope this helps others that find this before the MS article.
https://social.technet.microsoft.com/Forums/azure/en-US/40ac7a3d-12f0-47c5-9cee-97dd5867ddf0/unable-to-sign-in-when-trying-to-publish-web-role-to-azure?forum=windowsazuredevelopment
I know this is an old thread, but I was recently having a problem with visual studio 2015 where I could not sign in to Azure. I came across this SO entry. It was not helpful, but I eventually did find the answer.
The answer was to repair Visual Studio. It takes awhile to run but once it finished I was back in business with Azure in Visual Studio.
https://msdn.microsoft.com/en-us/library/aa983433%28v=vs.90%29.aspx?f=255&MSPPError=-2147217396
Related
i've got multiple microsoft accounts linked to multiple tenants. I've registered my first teams app (using the Office Toolkit functionality "Configure for SSO...") on the wrong tenant.
Is there some way to remove the stored credentials? I even tried making a new solution, but visual studio seems to have stored those credentials somewhere, just can't find where.
I am the engineer of VS extension of Teams Toolkit. We have identified this requirement from GitHub issue https://github.com/OfficeDev/TeamsFx/issues/1685, and will treat it as a new feature in the following release. So far, you can follow the workaround in that GitHub issue thread and thanks for your patience.
Only solution I could find.
Open Visual studio and go to Extensions -> Manage Extensions
Uninstall Teams toolkit
Install toolkit again
It should allow you to sign in again when you configure SSO
I'm using the Visual Studio extension MAT 4.0 on VS2015 to localize some WPF and WinForms applications. As of May 1 (yesterday) the "Generate Machine Translations" feature stopped working. According to the exception message this is because the MS Translator service has been moved from DataMarket to Azure.
I've tried subscribing to the translation service on Azure (as instructed by the exception message), but I don't think MAT is using the logged in VS user's account. Still doesn't work.
TranslateApiException: Invalid authentication token. Microsoft DataMarket is retired. Please subscribe to Microsoft Translator, in the Cognitive Services section at https://portal.azure.com. Please visit https://cognitive.uservoice.com/knowledgebase/articles/1128340-announcements-action-required-before-april-30-20 to find detailed instructions. : ID=1230.V2_Soap.GetTranslations.4EAC0341
Apparently this move has been planned for some time, so I'm baffled as to why there isn't an update to the Toolkit.
Anybody have any insight on this?
The fix for MAT for VS 2017 is current in testing. The fix is being back ported to MAT for VS 2013 & VS 2015.
Please note that one key change is the need to have a Azure subscription as reported in the announcement. Setting up the free 2m char as it should cover the major of usage cases.
I will post here when the fix is ready as well as the instructions for connecting the provider to the Azure service.
UPDATE: The fix has been posted that uses the user provided Azure subscription. fixed versions is MAT 4.0.1610 (VS 2015/VS2013) and MAT 4.0.8610.0 (VS 2017).
After installing the update, you will need to supply the provider the access key or you will receive a message with a link to he instructions. The details are here: https://multilingualapptoolkit.uservoice.com/knowledgebase/articles/1167898
After Update 4 I am experiencing the following error message:
I am not even able to sign in to my Microsoft account but it was working ok before the update. Please let me know what I have to do to get it working again.
Licensing / Purchase
I signed into the IDE, but it’s still telling me that the trial will expire. What’s going on? The odds are that the account you signed
in with doesn’t have an MSDN subscription or Visual Studio Online
subscription associated with it. Sign in with an account that does and
the license should be issued automatically or apply a product key
Community Edition is telling me my trial has expired. Do I have to pay for Community edition? No, Community edition is free to use. We
use the same infrastructure that allows you to unlock VS w/ an online
subscription to manage the requirement of signing into Community
edition so some of our strings overlap cross these scenarios. Trial
here means the period you can use the community edition before you
must sign in to fully unlock the IDE.
Source
Emphasis is mine. Does your account have a MSDN or Visual Studio Online subscription?
The most common cause is having the system clock out-of-date. Make sure your date and time are set correctly, and sync them online if you have to. This should fix your issue.
I'm trying to follow a tutorial on Azure deployment. I'm stuck on one of the first steps creating the App Service. It seams that the form tries to find all App Service Plans but can't, so all of Visual Studio hangs. I had to kill it with Task Manager. Any clues on how I can fix this? Do I need to create something at the Azure management console?
Had the same issue, turned out I hadn't installed Azure SDK, you'd think there would be some kind of error message, but no. Installing the SDK fixed issue
I did the steps below to resolve the issue.
Login to your Azure account
Manually create an app service (use any dummy app service name). The service plan and resource group will be created while you're creating this app service
Once you see the dummy app service created on your Azure dashboard (it will take around 1-2 minutes), open your visual studio from your pc, create your web project and check api service
--- This time, the service plan and resource group will be brought in.---
Click "Create" to create your "real" web/api project in Azure
Now you can remove the dummy service from Azure
I had the same problem. It started to work after I logged into the Azure Dashboard and manually created an App Services Web App.
Ran into the same issue a few days ago and here is how I got it working.
I had yet to create any App Services in the Azure account I had tied to Visual Studio and when I got to the Create App Service window you posted, Visual Studio would freeze.
I logged into the Azure Portal, created an App Service with a different name than the project. Once it was created, I then deleted the newly created App Service.
After doing this had no problem freezing in Visual Studio. The fix appears to be to create at least one App Service in portal before it works in VS.
I did two things at once, not sure which one got through the lock up.
1) In Visual Studio, went to File -> Account Settings then under the "All Accounts" section of the Account Settings window I reentered my credentials for the Azure account I had linked the project to. This account had a notification raised saying "We need to refresh the credentials for this account."
2) As others have said, I created a new Web App. I'm not sure this was the problem, however - I had previously created a couple other web apps and these resources were still present in my dashboard.
I have to agree with the above comments, too - the error messages provided for this are really, really poor.
Check that there are no characters that it will not accept. For instance an underscore '_'
Azure built a dummy name for me to use including an underscore which it does not accept. It was trial and error for me to find this where a simple warning would have saved lots of time.
Login to Azure Portal and create necessary resources. VS screens do not seem to work properly.
I created Api App on azure portal and my problem solved.
Same problem, however I have 3 Azure subscriptions, but even after making sure all of'em has at least one App Service it still hangs on this step. No other option than to not check the option to host.
Updating Azure SDK on VS2015 fix the problem in my case
Back in March 2015, Microsoft announced that "Azure Mobile Apps" are replacing "Azure Mobile Services." A few days ago, I spotted the documentation explaining how to create an Azure Mobile App. I followed the doc and successfully got my "TestDroid" mobile app service running locally. However, I cannot publish the app to Azure from Visual Studio 2015 Community Edition.
To publish my "TestDroid" app, I right-clicked on the project and selected "publish."
This dialogue is already the "first sign of trouble." Technically my Mobile App service does not match any of the categories shown in the above dialogue. Still, because Web Apps and Mobile Services have been merged into one, the best choice is "Microsoft Azure Web Apps." So that is the choice I made...
Unfortunately, Visual Studio 2015 CE does not show my already-provisioned "TestDroid" app as an option:
However, I know that it exists because I created it a day earlier, per the instructions, and it does appear in a resource group blade on the Azure portal:
Also, in the Visual Studio "Server Explorer" I can see the "TestDroid" service:
The Server Explorer entry for "Mobile Services" is empty, but in this case I expect it to be empty because, as already stated, creating a "Mobile Service" is now considered the old way, and creating a "Mobile App" is the new way.
I'm guessing this is merely a glitch in preview material, but I would like to know how to resolve this.
I got this working. In the end I simply visited the Azure blade for my "TestDroid" mobile app, and selected "get publish profile". I used the "import" option on the VS 2015 publish dialogue to import the publish profile.
The original MS instructions did not mention that this slightly-round-about approach was necessary, so I did not assume at first to try it.
All is well that ends well. :)