Azure Advisor Not Working? Fix Setup & Config Issues
Why Azure Advisor Isn't Doing What You Expect
I've helped dozens of Azure admins who open Azure Advisor for the first time, stare at a completely empty dashboard, and assume the service is broken. It's not broken. Nine times out of ten, the problem comes down to one of three things: wrong permissions on the subscription, missing scope filters that silently exclude all your resources, or a freshly configured resource that Advisor simply hasn't analyzed yet. The error messages , when there even are any, don't explain this at all. You just see a blank tile and wonder what you did wrong.
Azure Advisor is a cloud optimization service baked directly into the Azure platform. It monitors your resource configuration and usage telemetry, then surfaces actionable recommendations across five categories: Reliability, Security, Performance, Cost, and Operational Excellence. Think of it as a second set of eyes on your entire Azure environment, one that never sleeps and knows Microsoft's best practices cold. But when it goes quiet, your team is flying blind on cost overruns, security gaps, and performance bottlenecks.
Here's the honest truth about why the Azure Advisor dashboard shows nothing useful: the service depends entirely on having the correct role assignment at the right scope. If you're a Reader on only a single resource group but your VM is in a different one, Advisor will generate recommendations, you just won't see them. The scope mismatch is invisible to you. Similarly, if your subscription is brand new and you spun up resources in the last few hours, Advisor needs time to ingest telemetry. Recommendations won't appear instantly. Microsoft states it can take up to 24 hours after you act on a recommendation for Advisor to reflect the change. The same delay applies to new resources showing up in its analysis.
Then there's the filter problem. Advisor lets you filter by subscription, resource group, and resource type, which is genuinely useful in large environments. But if those filters were set by a previous admin and saved, you might be looking at a dashboard scoped to a resource group that no longer exists. No error. Just silence.
I know how frustrating this is, especially when leadership is asking why you're not acting on Azure cost recommendations and you can't even see what Advisor is flagging. Let's fix it, starting with the fastest path to a working dashboard. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before going through every configuration step, try this. It resolves the majority of "Azure Advisor showing no recommendations" cases in under two minutes.
Sign in to the Azure portal at portal.azure.com. In the left-hand navigation pane, look for Advisor. If you don't see it pinned, type "Advisor" in the top search bar under "All services" and select it from the results. You'll land on the Advisor dashboard.
Now look at the top of the dashboard for the Subscriptions filter, it's a dropdown near the top of the page. Click it. Check whether your subscription is actually selected. I've seen this blank out after a tenant-level permission change or after a support ticket resets your session defaults. Select your subscription explicitly, click Apply, and wait about ten seconds for the dashboard to reload.
If recommendations now appear across any of the five category tiles, Reliability, Security, Performance, Cost, Operational Excellence, you're good. The filter was the culprit. If the dashboard still looks empty after selecting your subscription, check the Resource Types filter directly below it. Make sure it's set to All rather than a specific service type.
Still empty after both filters are set correctly? Your account may not have the right permissions. Jump to Step 2 in the detailed walkthrough below, that's the next most common cause and takes about five minutes to diagnose.
One more quick check before you dig deeper: look at the individual category tiles. Sometimes Advisor has recommendations but they're all in one category, say, Security, while the others are clean. Click each tile individually (Reliability, Security, Performance, Cost, Operational Excellence) rather than relying on the top-level summary number. The summary can appear as zero when the real recommendations are sitting in a subcategory that isn't loading correctly due to a browser cache issue.
Do a hard refresh with Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) while on the Advisor page. Azure portal is a heavy single-page app and stale JavaScript cache causes display bugs that look like missing data.
Start at portal.azure.com and sign in with your Azure account. Once you're in, look at the left-side navigation panel. Azure Advisor should appear there if it's been pinned. If it hasn't been pinned by your organization, don't waste time looking for it, just type "Advisor" in the global search bar at the top of the portal. The search results split into Services, Resources, and Documentation. Under Services, click Advisor.
The Advisor dashboard opens with five category tiles arranged horizontally: Reliability, Security, Performance, Cost, and Operational Excellence. Each tile shows a count of active recommendations and a color-coded score. Green means you're in good shape for that category. Orange or red means Advisor has found issues that need attention.
If the dashboard loads but shows scores of zero across all five categories on a subscription that has live resources, that's your first signal that something is off with either the scope or your permissions, not with Advisor itself. Make a note of what you see: are the category tiles showing numbers but low scores, or are they showing dashes and "no data" placeholders? That distinction matters for the next steps.
If the page doesn't load at all and you get a generic "Something went wrong" error or an HTTP 403, that's a permissions issue, go straight to Step 2. If the page loads but the tiles are empty, continue through Step 3 (filter configuration) first.
What you should see when everything is working: five tiles with numeric recommendation counts, a summary score for each category, and a link at the bottom of each tile to "View all [category] recommendations." If that's what you're seeing, Advisor is working correctly and you can jump straight to Step 4 to start acting on the recommendations.
This is the step most guides skip over, and it's responsible for more Azure Advisor access problems than any other cause. Advisor uses Azure RBAC (Role-Based Access Control) to determine what you can see. You need at minimum a Reader role assignment on the subscription, resource group, or individual resource you want recommendations for. To actually implement recommendations, you'll need Contributor or Owner at the appropriate scope.
Here's how to check your current role assignment. In the Azure portal, navigate to Subscriptions (search for it in the top bar). Select your subscription, then go to Access control (IAM) in the left menu. Click View my access. This shows you exactly what roles you hold on this subscription. If your only assignment is at the resource group level, not the subscription level, Advisor will only show you recommendations for resources inside that specific resource group.
If you need to assign the Reader role to a user or service principal, click Add → Add role assignment in the IAM blade. Select Reader under the Role tab, then under Members, search for the account. Click Review + assign. Role assignments can take a few minutes to propagate across Azure's authorization system, wait about five minutes, then refresh Advisor.
# Check your current role assignments via Azure CLI
az role assignment list --assignee your-email@domain.com --all --output tableIf that command returns no subscription-level assignments (only resource-group-scoped ones), that's your problem. You need a subscription-level Reader assignment or higher to see the full Advisor recommendation set. After the role is assigned, sign out of the portal and sign back in to ensure the new permissions are picked up in your session token.
What you should see when permissions are correct: the Advisor dashboard loads with data, and clicking any recommendation shows you the full detail panel rather than an access denied message.
Azure Advisor's built-in filter system is genuinely powerful in large enterprises, but it's the number one cause of "I can't see my recommendations" confusion for everyone else. The filters remember your last selections, and if a previous session scoped everything down to a single test resource group, you'll keep seeing that narrow view until you reset it.
From the Advisor dashboard, find the filter bar near the top of the page. You'll see dropdown controls for Subscriptions, Resource Groups, and Resource Types. Here's the reset procedure:
First, click the Subscriptions dropdown. Check every subscription you want to monitor. If you manage multiple subscriptions and only one is selected, you're missing recommendations from the rest. Select all relevant subscriptions and click Apply.
Second, click the Resource Groups filter. If specific resource groups are selected rather than "All resource groups," widen the scope. Select all or clear the filter entirely, then click Apply.
Third, confirm the Resource Types filter is set to show all types, not filtered to a single service category like "Virtual Machines."
One thing that trips people up: Advisor also supports configuring it to only generate recommendations for specific subscriptions and resource groups, this is a more permanent setting than the dashboard filter, controlled under Advisor → Configuration in the left menu. Open that blade and check whether any subscriptions have been explicitly excluded. If a subscription row shows a status of "Excluded," Advisor won't generate recommendations for it at all, regardless of how you set the dashboard filter. Click the subscription name and toggle it back to included, then save the configuration.
After making these changes, give Advisor about 60 seconds to regenerate its view. The recommendation counts on the category tiles should update without requiring a full page reload.
Once Advisor is showing data, you need to know how to read it efficiently. The five categories each address a different aspect of your Azure environment, and they're not equal in urgency. Here's what each one is telling you and how to work through the findings.
Reliability recommendations focus on keeping your business-critical applications running. These often include things like enabling zone-redundant configurations for Azure SQL, adding health probes to load balancers, or upgrading older VM sizes that are approaching retirement. Click the Reliability tile, then click any recommendation to see the affected resources, the recommended action, and a direct link to implement the fix.
Security recommendations integrate with Microsoft Defender for Cloud. These highlight misconfigurations like publicly exposed storage accounts, missing disk encryption, or SQL servers without firewall rules. Security recommendations are the ones I'd prioritize first, they represent actual attack surface, not just efficiency improvements.
Cost recommendations are where Advisor saves real money. You might see idle virtual machines, underutilized ExpressRoute circuits, or reserved instance purchasing opportunities. The cost tile often shows an estimated monthly savings figure, click through to see which specific resources are flagged.
Performance covers application speed improvements: indexing recommendations for Azure SQL, throughput improvements for Azure Storage, or CPU/memory sizing suggestions for VMs under consistent load.
Operational Excellence is the catch-all for deployment hygiene: deprecated API versions, missing resource tags, subscription limits approaching capacity.
For each recommendation, you have three options: implement it (click the recommended action), postpone it (snooze for a defined time period, 1 day, 1 week, etc.), or dismiss it entirely. After you implement a recommendation and the configuration change is live, Advisor takes up to 24 hours to recognize the action and remove the item from your list. Don't panic if it doesn't disappear immediately.
Not every Azure Advisor recommendation is actionable right now. Maybe a cost recommendation suggests rightsizing a VM that your dev team is actively using for a major project. Maybe a reliability recommendation requires a maintenance window you haven't scheduled yet. Advisor has a built-in workflow for handling exactly this situation, and using it properly keeps your dashboard clean and focused on what actually needs attention today.
Postponing a recommendation: Open the recommendation detail page. Look for the Postpone button (it appears near the top of the detail panel alongside the recommended action button). Click it, select a snooze duration from the dropdown (options typically include 1 day, 3 days, 1 week, 2 weeks, 1 month), and confirm. The recommendation disappears from your active list and resurfaces automatically when the snooze period expires. This is perfect for items that are on your roadmap but blocked by a dependency or a change window.
Dismissing a recommendation permanently: If you've made a deliberate architectural decision that conflicts with what Advisor is suggesting, say, you intentionally have a single-instance VM because it's a non-critical dev environment and you've accepted the availability risk, use the Dismiss option instead. This removes the recommendation permanently. Be thoughtful here: dismissed recommendations don't come back automatically if conditions change.
Bulk actions: From the category list view (not the individual detail page), you can select multiple recommendations using the checkboxes on the left, then use the toolbar that appears to postpone or dismiss them in bulk. This is a huge time-saver when you have a batch of "low-priority" findings you want to snooze together.
# List all active Advisor recommendations via Azure CLI
az advisor recommendation list --output table
# Dismiss a specific recommendation by ID
az advisor recommendation disable --recommendation-id <recommendation-id>After working through the active list, your Advisor dashboard should show a clear picture of only the items you've chosen to keep visible. That's the state you want: a live, accurate signal of your Azure environment's health, not a noise-filled wall of items you've already reviewed.
Advanced Azure Advisor Troubleshooting
If the standard steps haven't resolved your issue, it's time to go deeper. The problems at this level tend to fall into a few buckets: service principal and managed identity permission gaps, API-level access issues, enterprise policy conflicts, and large-scale multi-subscription environments where Advisor's scope configuration becomes genuinely complex.
Service Principal Access to Azure Advisor: If you're automating Advisor workflows, pulling recommendations into a ticketing system, feeding them into a Power BI dashboard, or building a custom governance pipeline, you're likely using the Azure Advisor REST API. The service principal running those API calls needs the same RBAC assignments a human user would: at minimum, Reader on the subscriptions it needs to query. A common mistake is assigning Reader only at the resource group level when the API call targets the subscription endpoint. The REST API base path is https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/recommendations and it respects the same RBAC boundaries as the portal.
# Test Advisor API access with Azure CLI (uses your current login context)
az rest --method GET \
--url "https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/recommendations?api-version=2023-01-01" \
--output jsonIf that returns a 403, the authenticated identity lacks the required subscription-level role. If it returns an empty value: [] array on a subscription with known resources, either the subscription is excluded in Advisor's configuration blade or Advisor hasn't finished its analysis cycle yet, wait 24 hours and retry.
Azure Policy conflicts blocking Advisor configuration changes: In enterprise environments, Azure Policy often prevents direct configuration changes at the subscription level. If you're trying to modify Advisor's subscription-scoped configuration settings (under Advisor → Configuration) and getting an error or finding your changes don't persist, check whether a "Deny" policy assignment is blocking the Microsoft.Advisor/configurations/write operation. Use the Activity Log (search "Activity Log" in the portal) and filter to the Advisor resource provider to see any denied write operations.
Multi-tenant environments: If your Azure account is a guest in another organization's tenant, Advisor recommendations in that tenant require the hosting tenant admin to grant you at least Reader-level access explicitly. Guest accounts don't inherit subscription permissions automatically. Ask the tenant admin to check your external user's role assignment in their IAM blade.
Azure Advisor Score not updating: The Advisor Score, the aggregate health number for each category, is calculated separately from the individual recommendation list and has its own update cadence. Even after you implement fixes, the score update can lag behind the recommendation list clearing. If your score seems stuck, navigate to Advisor → Advisor Score in the left menu and check the "Last updated" timestamp shown at the top of the score page. If it's more than 48 hours old on an active subscription, open a support ticket, score calculation failures are a backend service issue that Microsoft needs to investigate on their end.
Recommendations for specific resource types not appearing: Azure Advisor doesn't cover every Azure service. If you're not seeing recommendations for a specific resource and wondering why, cross-check the supported services list, it includes services like Azure Kubernetes Service, Azure Key Vault, Azure Cosmos DB, Azure SQL, Azure Virtual Machines, Azure Storage, and many others, but not every service in the Azure catalog. If your resource type isn't supported, Advisor simply won't generate recommendations for it.
Prevention & Azure Advisor Best Practices
Once you have Azure Advisor working correctly, the goal shifts from fixing it to making it part of your regular operations rhythm. I've seen teams that check Advisor quarterly, and I've seen teams that act on recommendations within 24 hours of them appearing. The second group has significantly lower Azure bills, fewer security incidents, and more reliable applications. That difference comes down to process, not technical skill.
The single highest-impact thing you can do right now is set up Advisor alerts. These fire when new recommendations of a specific category and impact level appear, or when your Advisor Score drops below a threshold you define. To configure them, go to Advisor → Alerts (preview) in the left menu. Create an alert rule, set the condition to something like "New high-impact Security recommendation," and route it to an Action Group that sends email to your security team. This turns Advisor from a dashboard you remember to check into a proactive notification system.
For larger teams, consider exporting Advisor data into a centralized monitoring platform. You can integrate Advisor with Azure Monitor, stream recommendation data to a Log Analytics workspace, and build dashboards in Azure Workbooks or Power BI. This makes it easier to track recommendation trends over time, see whether your team's Advisor Score is improving, and report to management on cloud optimization progress.
Review the Advisor Configuration blade (Advisor → Configuration) on a quarterly basis. Subscriptions get added and removed. Resource groups get reorganized. If you configured Advisor to generate recommendations only for specific scopes six months ago and your architecture has changed, that configuration is now stale and you're missing recommendations for new workloads.
Train your team on the difference between dismissing and postponing recommendations. Dismissals are permanent and should require a written justification, especially for Security category items. Create a simple standard operating procedure: Security recommendations require a ticket before dismissal, Cost recommendations can be postponed up to 30 days by the resource owner, and Reliability recommendations require a review in your next architecture sync. This prevents the dashboard from becoming a graveyard of carelessly dismissed items that mask real risks.
- Set up Advisor email alerts for new high-impact Security and Reliability recommendations, takes five minutes and immediately improves your response time
- Review Advisor Cost recommendations every month before your Azure billing cycle closes, there's often low-hanging fruit like idle public IPs and oversized VMs that represent pure waste
- Assign a specific owner for each Advisor category in your team, one person owns Cost, another owns Security, another owns Reliability, so recommendations don't fall through the cracks
- After any significant infrastructure change (new workload, scaling event, architecture refactor), check Advisor within 48 hours, new misconfigurations show up fastest right after a change, while the context is still fresh
Frequently Asked Questions About Azure Advisor
How do I access Azure Advisor in the Azure portal?
Sign in to the Azure portal at portal.azure.com and look for Advisor in the left-hand navigation pane, it's often pinned there by default. If you don't see it, type "Advisor" into the search bar at the top of the portal and select it from the Services section of the results. You'll land directly on the Advisor dashboard showing your personalized recommendations organized into the five categories: Reliability, Security, Performance, Cost, and Operational Excellence. No additional setup is required to start reading recommendations, Advisor is always running in the background analyzing your Azure resources.
What permissions do I need to see Azure Advisor recommendations?
You need at least a Reader role assignment on the subscription, resource group, or individual resource you want to view recommendations for. To actually implement a recommendation, meaning to make the configuration change Advisor is suggesting, you'll need Contributor or Owner access at the appropriate scope. The key thing to understand is that your role assignment scope matters: if you're only a Reader on a specific resource group, you'll only see recommendations for resources inside that group. A subscription-level Reader assignment gives you the broadest view. Check your assignments by going to Subscriptions → Access control (IAM) → View my access in the portal.
What Azure resources does Advisor actually give recommendations for?
Azure Advisor covers a wide range of Azure services, far more than most people realize. The supported list includes Azure Virtual Machines, Azure Virtual Machine Scale Sets, Azure App Service, Azure Kubernetes Service, Azure SQL Server, Azure Storage accounts, Azure Cosmos DB, Azure Key Vault, Azure Cache for Redis, Azure Application Gateway, Azure Front Door, Azure ExpressRoute, Azure IoT Hub, Azure Data Factory, Azure HDInsight, Azure Cognitive Services, Azure Synapse Analytics, Azure Traffic Manager, Log Analytics workspaces, and more. That said, not every service in the Azure catalog is covered. If you're not seeing recommendations for a specific resource type, it's worth checking whether that service is on the supported list before assuming there's a configuration problem.
Why are my Azure Advisor recommendations not updating after I made a fix?
This is completely normal. After you implement a recommendation, whether that's resizing a VM, enabling encryption, or buying a reserved instance, Advisor can take up to 24 hours to recognize the change and remove the recommendation from your list. The Advisor Score (the overall health number per category) can take even longer to reflect your improvement. Don't re-apply the fix thinking it didn't work. If a recommendation is still showing after 48 hours despite your confirmed change being live, try clearing your browser cache and reloading the portal. If it persists beyond 48 hours, it's worth opening an Azure support ticket to rule out a backend analysis delay on Microsoft's side.
Can I configure Azure Advisor to only watch specific subscriptions or resource groups?
Yes, and this is a genuinely useful feature for large organizations where you don't want Advisor flooding you with recommendations from dev/test environments you don't actively manage. Go to Advisor → Configuration in the left navigation menu. You'll see a list of all subscriptions you have access to, with the option to include or exclude each one from Advisor's recommendation generation. You can also scope down to specific resource groups within a subscription. The important distinction: this Configuration setting affects which recommendations Advisor generates (not just displays). The subscription/resource group dropdowns on the main dashboard are just display filters, they don't stop Advisor from analyzing those resources in the background.
How do I get Azure Advisor cost recommendations to show up for reserved instances?
Reserved instance (RI) purchase recommendations under the Azure Advisor Cost category require your subscription to have at least 7 days of VM usage history for Advisor to calculate a meaningful recommendation. If your subscription is new or you recently migrated workloads, wait a week and then check the Cost category again. When RI recommendations do appear, they'll show you the estimated annual savings, the recommended reservation term (1-year or 3-year), and the specific VM size and region. You'll also need Owner-level access on the subscription to actually complete the purchase, Reader access lets you see the recommendation but not act on it. Navigate to the Cost tile, click any RI recommendation, and use the "Buy now" action to go directly to the reservation purchase flow.