Hélder Pinto

@jannickoeben @darrelmiller, this should work as a work-around while MSI is not an option: ``` Connect-AzAccount -Identity $token = Get-AzAccessToken -ResourceUrl "https://graph.microsoft.com" Connect-MgGraph -AccessToken $token.Token ```

This Policy definition is still broken. I am opening a Support ticket to increase visibility of the problem.

@sinbai Actually, when using the [REST API](https://github.com/Azure/azure-rest-api-specs/blob/3906fc7ebacfbdd0130957563f472d56e8ceda32/specification/security/resource-manager/Microsoft.Security/stable/2020-01-01/serverVulnerabilityAssessments.json), if you create a `Microsoft.Security/serverVulnerabilityAssessments` sub-resource under a Virtual Machine resource and give it the `MdeTvm` name, that VM will be using the...

@AmanuelAZ, the fix was not published to the main branch yet. We mistakenly closed this issue. I am reopening it. Thanks for letting us know. @arthurclares, when is this fix...

@AmanuelAZ, there is actually a simpler work-around, if you need to upgrade to 0.4 before the fix is released. You just need to edit the `config/settings.json` blob in the hubs...

@CaddyG, can you provide more details? The issue description does not provide any helpful context besides the title. Which operation were you trying when this error was raised? Was this...

Thanks for the suggestion, @rithinkumark1. Regarding these: > Idle VM for last 3months > Storage not accessed for last 3months As they require detailed historical usage data for a longer...

I confirm it is now working.

> Won't this happen if you use the daily schedule? Yes, it would happen at least 24h after the scope change, but the idea is to have recommendations results reflect...

@flanakin, I studied the `config_ConfigureExports` ADF activity and re-read the steps to configure managed exports and realized that we have a chicken and egg problem. If we want to define...