Skip to content

Commit e6ef041

Browse files
committed
Add difference with Grafana in Azure Monitor
1 parent ddb184e commit e6ef041

File tree

1 file changed

+8
-1
lines changed
  • articles/managed-grafana

1 file changed

+8
-1
lines changed

articles/managed-grafana/faq.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,8 @@ author: maud-lv
55
ms.author: malev
66
ms.service: azure-managed-grafana
77
ms.topic: reference
8-
ms.date: 04/05/2024
8+
ms.date: 04/30/2025
9+
ai-usage: ai-assisted
910
---
1011

1112
# Azure Managed Grafana FAQ
@@ -51,6 +52,12 @@ Charges for active users are prorated during the first and the last calendar mon
5152
- On February 28, the full monthly charge applies for 20 users.
5253
- Upon deletion on March 25, the charge for March would be prorated for 15 users for 25 days out of 31 days, totaling a charge for 12.09 active users.
5354

55+
## What's the difference between Azure Managed Grafana and Grafana in Azure Monitor?
56+
57+
Azure Monitor includes native support for Grafana dashboards directly within the Azure portal. This built-in capability allows you to quickly access prebuilt dashboards and create custom visualizations for monitoring your Azure resources without leaving Azure Monitor. It's ideal for users who primarily rely on Azure Monitor data sources and prefer a streamlined, integrated experience within the Azure portal.
58+
59+
Azure Managed Grafana, on the other hand, provides a dedicated, fully managed Grafana instance with broader flexibility. Choose Azure Managed Grafana when you need advanced user management, customization, integration with a wide variety of Azure and non-Azure data sources, or when you require Grafana's full feature set, such as advanced alerting, reporting, and enterprise plugins. Azure Managed Grafana is also the recommended choice if you prefer managing dashboards and visualizations in a standalone Grafana environment, separate from the Azure portal.
60+
5461
## Next steps
5562

5663
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)