An Azure personalized recommendation engine that helps users follow best practices to optimize Azure deployments.
Hello @SimonA Connexionz
The fact that Get-AzAdvisorRecommendation still returns your expected recommendations is an important diagnostic result. Microsoft documents that this cmdlet retrieves the cached Advisor recommendations, so the recommendations still exist on the Advisor service side.
Because the PowerShell/API data is present while the Azure Advisor portal shows every category as healthy, I would focus on the Advisor portal scope/configuration or UI layer rather than Defender for Cloud policies.
One thing I would check specifically is:
Azure Advisor → Configuration → Resources
Verify that the affected subscriptions and resource groups are still selected under Include. Advisor only displays recommendations for subscriptions/resource groups selected there, and Microsoft notes that these configuration settings apply at subscription/resource-group level rather than being merely a browser-local preference.
I would also compare the portal against Azure CLI:
az advisor recommendation list \
--subscription "<subscription-id>" \
--output table
You can force Advisor to generate/refresh recommendations as another test:
az advisor recommendation list \
--subscription "<subscription-id>" \
--refresh \
--output table
Microsoft documents --refresh as generating new recommendations.
If PowerShell and CLI continue returning recommendations after the refresh while the portal still reports:
Cost ✓
Security ✓
Reliability ✓
Operational excellence ✓
Performance ✓
then I would consider that strong evidence of a portal/backend presentation issue, rather than assuming that all recommendations genuinely disappeared.
It's also worth testing the Advisor blade in an InPrivate/Incognito browser session, although you've already cleared the browser cache and signed out/in, so I wouldn't spend much more time on browser troubleshooting.
Microsoft notes that Advisor normally runs in the background and that recommendations for newly created resources can take up to 24 hours to appear. However, that doesn't really explain this case because these are existing recommendations that remain retrievable programmatically.
I also wouldn't change your Microsoft Cloud Security Benchmark configuration or start modifying Advisor exemptions based on the portal display alone. Your PowerShell results indicate that Advisor still has recommendation data.
At this point, if Configuration → Resources confirms that the subscriptions/resource groups are included and the CLI/PowerShell continue returning recommendations, I think Microsoft should investigate.
Microsoft Moderator Harshitha Eligeti: Could you please help escalate this to the Azure Advisor team? The portal shows zero recommendations across all categories, while Get-AzAdvisorRecommendation continues to return existing recommendations for the same environment. This appears to warrant investigation of the Advisor portal/API presentation path.
Simona, if possible, I would provide the moderator privately with:
Subscription ID
Tenant ID
Region(s) of affected resources
Approximate UTC time the issue first appeared
Example recommendation ID returned by PowerShell
Screenshot of Advisor → Configuration → Resources
You can also capture a sanitized comparison using:
Get-AzAdvisorRecommendation |
Select-Object Name, Category, Impact, ResourceGroupName
References:
Microsoft – Azure Advisor portal basics
Microsoft – Configure Azure Advisor recommendations
Microsoft – Get-AzAdvisorRecommendation
Microsoft – Azure CLI Advisor recommendation commands
Based on the evidence you've provided, I wouldn't interpret the green checks as confirmation that the environment suddenly has no Advisor findings. The PowerShell results strongly suggest a discrepancy between the Advisor service data and what the portal is rendering.
Please "Accept the Answer" if this information helped you. This will help us and others in the community.