Skip to main content

No subscription found in the context.


FRUSTRATION!!!
Don’t you just love it when you change nothing and then something breaks?  Working with VSCode and Azure, I do a lot of Infrastructure as Code.  I love the idea of being able to write code that builds exactly what I want, every time.  The problem is that on occasion, things change outside the scope of my code and now I am trying to solve a mystery.  The latest one involves whenever I run a simple Azure command.  For exam, Get-AZVM. This should not be hard.  Well, here is the result in VSCode.

No subscription found in the context. Please ensure that the credentials you provided are authorized to access an Azure subscription, then run Connect-AzAccount to login

So, I execute :


Connect-AzAccount

When you do this, it brings us to a website to go to and a code to enter.


PS C:\Connect-AzAccount


WARNING: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code FNTC88YR4 to authenticate. 

Once you enter the code into the website, you are asked to provide your credentials to access the Azure subscription that you want to program for.  Here is the response.


Account                 SubscriptionName TenantId                             Environment
-------                 ---------------- --------                             -----------
XXXXXXXX@ZZZZ.com                        VVVVVVVV-WWWW-XXXX-YYYY-ZZZZZZZZZZZZ AzureCloud 

All seams well until you run an Azure command and you get the same error.  Very frustrating.

When I run Get-AZSubscription, this is what I get.


PS C:\Get-AzSubscription

WARNING: Unable to acquire token for tenant 'AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE'
WARNING: Unable to acquire token for tenant 'FFFFFFFF-GGGG-HHHH-IIII-JJJJJJJJJJJJ'

Now, I have used several different subscriptions before.  Since I do teach Azure classes I use a temporary Azure account for the class can not my corporate account.  None of the TenantId numbers match my corporate account.

Using Set-AZContext did not yield any good results.

When using Set-AZSubscription with the correct subscription ID, I get this:


Set-AzContext: Please provide a valid tenant or a valid subscription.

Did I mention that Set-AZContext did not work?

Fortunately, I stumbled across this simple command.


PS C:\Clear-AzContext

Confirm
Remove all accounts and subscriptions in all sessions for the current user?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Yes"): y
PS C:\Connect-AzAccount

WARNING: To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code FZG9NDZD5 to authenticate.

Account                 SubscriptionName TenantId                             Environment
-------                 ---------------- --------                             -----------
JASON_YODER@hotmail.com MSDN Platforms   5fd82206-550e-4185-bbc6-7346fa9a0a47 AzureCloud  

Yep, that is all that it took.  I still have no idea why it would not accept my credentials after it accepts my credentials, but at least I have a quick fix and now, so do you.

As for accessing azure:


PS C:\get-azvm


ResourceGroupName       Name      Location          VmSize  OsType                NIC Provisio
                                                                                      ningStat
                                                                                             e 
-----------------       ----      --------          ------  ------                --- -------- 
NAVY1               DC-navy1 canadacentral   Standard_B2ms Windows   DCInterfacenavy1 cceeded 
NAVY1             SVR1-navy1 canadacentral Standard_DS1_v2 Windows SVR1Interfacenavy1 cceeded 

It works!

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...