Virtual Machine is not getting marked as 'isVirtual' when running Discovery on AzureDescriptionVirtual Machine is not getting marked as "isVirtual" when running Windows os Discovery for Azure device/Virtual machine"IS Virtual" check box is not MarkedStep to run "ConfirmAzureVM.ps1" script fails with error: The term, is not recognized as the name of a, cmdlet, function, script file, or operable program Discovery runs via a MID Server that has a space in the nameSteps to Reproduce 1 - Open Windows OS - Server pattern2 - Open step: Windows - Cloud > Windows - Azure > 40.2.33 - Attempt to run the script by the command line:"powershell.exe -ExecutionPolicy Bypass " + $scriptPath"WorkaroundThis problem is under review and targeted to be fixed in a future release. To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form. The workaround is the following: Navigate to the "Windows OS" patternUpdate pattern step "Run the script" from library "Windows - Azure" as follows: "powershell.exe -ExecutionPolicy Bypass -File " +"\""+ $scriptPath+"\"" Save and publish the patternSync with MID Server Run the discovery and it will be updating the IS Virtual Check BoxRelated Problem: PRB1588559