Showing results for 
Show  only  | Search instead for 
Did you mean: 

Azure connection not working / works fine directly in Powershell

Anyone else experiencing an issue where the native Azure connection tests successful (in the beacon UI) but fails when actually executing? I can run all the same commands used by the connector directly in powershell, & all return data (so no access or firewall issues). I've opened a support case which was escalated to Engineering, but curious if others may have experienced this issue.

#1 -Connect-AzureRmAccount -Credential <credential> -TenantID <tenantid> -ServicePrincipal 
#2 - Get-AzureRmSubscription
#3-Get-AzureRmVmSize -Location <A specified Azure Location, e.g. US Central>


I review this flexera KB - and all tests successful.
Diagnosing Inventory Beacon PowerShell Connection issues
(3) Replies
By Level 8 Champion
Level 8 Champion
Which version of fnms are you using?
I think we had issues with proxy settings in 2019r2 depending if you entered the proxy by fqdn or ip-adress.

we are on FNMS 2020 R1

@Ralph_Crowley  - I have seen issues with the Azure connector if you enter your proxy information in FQDN format such as http://myproxy:8080/

As a test, can you enter your proxy information as an IP Address instead of the name?