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> #4-Get-AzureRmLocation
I review this flexera KB - and all tests successful.
Diagnosing Inventory Beacon PowerShell Connection issues community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/Diagnosing-Inventory-Beacon-Powershell-Connection-issues/ta-p/153542
‎Feb 24, 2021 12:39 PM
‎Feb 24, 2021 12:48 PM
we are on FNMS 2020 R1
‎Feb 24, 2021 12:49 PM
@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?
‎Feb 24, 2021 01:34 PM