Why does Azure Powershell script think I'm not logged-in?

306 views Asked by At

I'm building an Azure Powershell script to add a DB firewall rule.

I first of all login using Add-AzureRmAccount:

$userName = "[email protected]"
$securePassword = ConvertTo-SecureString -String "---------" -AsPlainText -Force
$cred = New-Object System.Management.Automation.PSCredential($userName, $securePassword)
Add-AzureRmAccount -Credential $cred

This returns the following, which I assume means that I have successfully logged-in:

Environment           : AzureCloud
Account               : [email protected]
TenantId              : [GUID]
SubscriptionId        : [GUID]
SubscriptionName      : Visual Studio Ultimate mit MSDN
CurrentStorageAccount : 

At this stage I can query for my subscription:

Get-AzureRmSubscription –SubscriptionName "Visual Studio Ultimate mit MSDN" | Select-AzureRmSubscription

Which returns

Account      : [email protected]
Environment  : AzureCloud
Subscription : [GUID]
Tenant       : [GUID]

So far, so good.

However, whenever the script calls anything at the resource-group level, such as

Find-AzureRmResource -ResourceNameContains "-----NorthEurope"

then it responds with

Run Login-AzureRmAccount to login.

The exception detail is

+ CategoryInfo : InvalidOperation: (:) [Find-AzureRmResource], PSInvalidOperationException

+ FullyQualifiedErrorId : InvalidOperation,Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.FindAzureResourceCmdlet

Which doesn't help me at all.

I've even explicitly called

Login-AzureRmAccount $cred

prior to the Find-AzureRmResource call, but this makes no difference.

Of course, what I'm ultimately looking to do is call

New-AzureRmSqlServerFirewallRule    -ResourceGroupName "-----NorthEurope" `
                                    -ServerName "-----.database.windows.net" `
                                    -FirewallRuleName "test1" `
                                    -StartIpAddress "-.-.-.-" `
                                    -EndIpAddress "-.-.-.-"

But that encounters the same exception.

Can anyone explain why I keep getting asked to run Login-AzureRmAccount after I've apparently successfully added the account?


Solution

What got it working for me, as @Tomer alluded to in the comments, was to forcefully re-get all AzureRm modules.

0

There are 0 answers