Microsoft Azure connectors fail if the execution policy is not set to RemoteSigned

[#1]

To use Microsoft Azure connectors on your inventory beacon, your local machine policy must be set to RemoteSigned. If the policy is set to something else, you will see errors on the Systems Tasks page related to AuthorizationManager when the modules are loaded, such as the one below:

[INFO ] Failed to execute Reader 'Get Azure VM Instances' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\microsoft azure\Instance.xml, at step line 1 Error: Errors occurred while loading the format data file: Microsoft.PowerShell, , C:\Program Files\WindowsPowerShell\Modules\Az.Compute\4.27.0\Compute.format.ps1xml: The file was skipped because of the following validation exception: AuthorizationManager check failed.

Change the execution policy to RemoteSigned 

You can check your current policy using the following cmdlet: Get-ExecutionPolicy -List. If it returns something other than RemoteSigned, update the policy following the steps below.

1. Open PowerShell and run the following cmdlet as an administrator:

Set-ExecutionPolicy RemoteSigned -Scope LocalMachine

2. Rerun the Microsoft Azure connector.