Visual Studio not finding my Azure subscriptions

Question

I have a working Azure account with various services already running. I receive monthly bills for these.

Now, I created a workerrole in Visual Studio that I want to

Answer 1

So I stumbled upon this question and I had the latest Azure SDK (2.8.2 at this time) installed. My default directory and subscription would show up and not the other ones I had access to. I was using VS 2015 Enterprise. So clicking on the top right Corner on my account inside Visual Studio 2015 and clicking on "Account settings" took me here:

I located the option "Apply Filter". This option only appears if your Visual Studio credentials are not stale. Otherwise, it says "Renenter your credentials" and only after that this option re-appears on the "Account Settings" inside Visual Studio 2015.

Click on the "Apply Filter" and a new form shows up as shown below:

Please note that it might take a while for Visual Studio to query and populate all the azure directories to which you have access to. Clicking the dropdown list a few times might help if you are eager enough. Select the directory you want to set as default. and Click the "Apply" button.

A window might appear asking you to re-enter your Microsoft Account credentials. Enter the Credentials and click signin to complete the process.

Visual Stdio might do some processing before the switch process completes as shown.

Once that is done, you are taken back to the form where you applied the filter. Now the filtered directory should be shown as below:

Close the form and restart Visual Studio. Hope that this helps.

Answer 2

In my case, I just had to log in to VS using the sign in button in the upper-right corner. Attempting to log in to Azure via the Cloud Explorer window while not being signed in to VS itself will apparently yield the "No subscriptions found" message.

Answer 3

You found the solution to your problem. I had the same symptom, but the solution was another:

You need to go to Extensions and Updates and then update the Microsoft Azure SDK 2.8. After that, I could login and see the subscription (for my case it was a DreamSpark subscription)

This following site, which is about free Azure for DreamSpark (students), actually says that Visual Studio 2013 is not supported, only VS 2015 Community, but it works for me - if I update the Azure SDK as written above. http://blogs.msdn.com/b/microsoft_student_developer_blog/archive/2015/04/09/using-microsoft-azure-for-students.aspx

Microsoft Azure SDK 2.8 (if you cannot find it in Extensions and Updates some time from now): https://azure.microsoft.com/en-us/blog/announcing-the-azure-sdk-2-7-for-net/

Answer 4

All methods here did not work for me. What did finaly do the trick was connecting through Server Explorer tab.

Answer 5

After trying every solution in this question, I was still not seeing my subscription. My solution:

1. Log into Azure subscription
2. Create a new Web App
3. Open the new Web App
4. In the top menu select Get publish profile

5. Open the web app project in Visual Studio 2017 that you wish to publish
6. Right click the Project in Solution Explorer, and select publish
7. Scroll right to find Import Profile and select the file downloaded in step 4
8. Click Publish

Now when I go into publish, the subsription is displayed, and all the connection information is saved.

Answer 6

I realise VS Code isn't the same as Visual Studio, but this question comes up first when searching for Visual Studio Code so I thought I'd post my findings here.

I had the same symptoms with VS Code on Ubuntu and I think it's to do with the 2FA that Azure uses (i.e. when it sends you an SMS to verify).

What happened was that VS Code fired up the default browser for me to log in, I put in my username and password and the screen said "you can now close this window" but it never prompted for 2FA. After that, VS Code always said "you have no subscriptions".

How I fixed it was:

1. sign out of Azure from inside VS Code (use control-shift-p and search for "Azure: sign out"

2. Open up the web browser manually and sign in properly using 2FA

3. go back to VS Code and sign in again