Merge pull request #210335 from yegu-ms/main

Removed reference to Grafana Enterprise from index page

Author: Court72

articles/managed-grafana/high-availability.md

@@ -6,11 +6,12 @@ ms.author: malev
 ms.service: managed-grafana 
 ms.topic: conceptual
 ms.date: 7/27/2022 
+ms.custom: references_regions
 ---
 
 # Azure Managed Grafana service reliability
 
-An Azure Managed Grafana instance in the Standard tier is hosted on a dedicated set of virtual machines (VMs). By default, two VMs are deployed to provide redundancy. Each VM runs a Grafana server. A network load balancer distributes browser requests amongst the Grafana servers. On the backend, the Grafana servers are connected to a shared database that stores the configuration and other persistent data for an entire Managed Grafana instance.
+An Azure Managed Grafana instance in the Standard tier is hosted on a dedicated set of virtual machines (VMs). By default, two VMs are deployed to provide redundancy. Each VM runs a Grafana server. A network load balancer distributes browser requests amongst the Grafana servers. On the backend, the Grafana servers are connected to a common database that stores the configuration and other persistent data for an entire Managed Grafana instance.
 
 :::image type="content" source="media/service-reliability/diagram.png" alt-text="Diagram of the Managed Grafana Standard tier instance setup.":::
 
@@ -20,11 +21,11 @@ Microsoft is not providing or setting up disaster recovery for this service. In
 
 ## Zone redundancy
 
-Normally the network load balancer, VMs and database that underpin a Managed Grafana instance are located in a region based on system resource availability, and could end up being in a same Azure datacenter
+Normally the network load balancer, VMs and database that underpin a Managed Grafana instance are located in a region based on system resource availability, and could end up being in a same Azure datacenter.
 
 ### With zone redundancy enabled
 
-When the zone redundancy option is enabled, VMs are spread across [availability zones](../availability-zones/az-overview.md#availability-zones) and other resources with availability zone enabled.
+When the zone redundancy option is enabled, VMs are spread across [availability zones](../availability-zones/az-overview.md#availability-zones). Other resources such as network load balancer and database are also configured for availability zones.
 
 In a zone-wide outage, no user action is required. An impacted Managed Grafana instance will rebalance itself to take advantage of the healthy zone automatically. The Managed Grafana service will attempt to heal the affected instances during zone recovery.
 
@@ -33,7 +34,20 @@ In a zone-wide outage, no user action is required. An impacted Managed Grafana i
 
 ### With zone redundancy disabled
 
-Zone redundancy is disabled in the Managed Grafana Standard tier by default. In this scenario, virtual machines are created as regional resources and should not be expected to survive zone-downs scenarios as they can go down at same time.
+Zone redundancy is disabled in the Managed Grafana Standard tier by default. In this scenario, virtual machines are created as single-region resources and should not be expected to survive zone-downs scenarios as they can go down at same time.
+
+## Supported regions
+
+Zone redundancy support is enabled in the following regions:
+
+
+| Americas         | Europe            | Africa            | Asia Pacific      |
+|------------------|-------------------|-------------------|-------------------|
+| East US          | West Europe       |                   | Australia East    |
+| South Central US |                   |                   |                   |
+
+
+For a complete list of regions where Managed Grafana is available, see [Products available by region - Azure Managed Grafana](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=managed-grafana&regions=all)
 
 ## Next steps
 

articles/managed-grafana/how-to-authentication-permissions.md

@@ -83,7 +83,7 @@ System-assigned managed identity is the default authentication method provided t
 
 1. Under **Grafana administrator role**, the box **Include myself** is checked by default. Optionally select **Add** to grant the Grafana administrator role to more members.
 
-:::image type="content" source="media/authentication/create-form-permission.png" alt-text="Screenshot of the Azure portal. Create workspace form. Permission.":::
+    :::image type="content" source="media/authentication/create-form-permission.png" alt-text="Screenshot of the Azure portal. Create workspace form. Permission.":::
 
 ##### With managed identity disabled
 

articles/managed-grafana/index.yml

@@ -43,7 +43,7 @@ landingContent:
     linkLists:
       - linkListType: how-to-guide
         links:
-          - text: Configure permissions
+          - text: Modify permissions
             url: how-to-permissions.md
           - text: Share an instance
             url: how-to-share-grafana-workspace.md
@@ -55,11 +55,9 @@ landingContent:
         links:
           - text: Service reliability
             url: high-availability.md
-          - text: Control Plane
+          - text: Control plane APIs
             url: /rest/api/managed-grafana
-          - text: Data Plane
-            url: https://aka.ms/managed-grafana-dataplane
-          - text: Grafana Enterprise
-            url: https://grafana.com/docs/grafana/latest/enterprise
+          - text: Data plane APIs
+            url: https://aka.ms/managed-grafana/docs/http-api
           - text: Grafana UI
             url: grafana-app-ui.md

articles/managed-grafana/known-limitations.md

@@ -0,0 +1,32 @@
+---
+title: Azure Managed Grafana limitations
+description: List of known limitations in Azure Managed Grafana
+ms.service: managed-grafana
+ms.topic: troubleshooting
+ms.date: 08/31/2022
+ms.author: malev
+author: maud-lv
+---
+
+# Limitations of Azure Managed Grafana
+
+Azure Managed Grafana delivers the native Grafana functionality in the highest possible fidelity. There are some differences between what it provides and what you can get by self-hosting Grafana. As a general rule, Azure Managed Grafana disables features and settings that may affect the security or reliability of the service and individual Grafana instances it manages.
+
+## Current limitations
+
+Managed Grafana has the following known limitations:
+
+* All users must have accounts in an Azure Active Directory. Microsoft (also known as MSA) and 3rd-party accounts aren't supported. As a workaround, use the default tenant of your Azure subscription with your Grafana instance and add other users as guests.
+
+* Installing, uninstalling and upgrading plugins from the Grafana Catalog aren't allowed.
+
+* Data source query results are capped at 80 MB. To mitigate this constraint, reduce the size of the query, for example, by shortening the time duration.
+
+* Querying Azure Data Explorer may take a long time or return 50x errors. To resolve these issues, use a table format instead of a time series, shorten the time duration, or avoid having many panels querying the same data cluster that can trigger throttling.
+
+* API key usage isn't included in the audit log.
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Troubleshooting](./troubleshoot-managed-grafana.md)

articles/managed-grafana/toc.yml

@@ -39,12 +39,14 @@ items:
     href: how-to-monitor-managed-grafana-workspace.md
   - name: Create and manage API keys
     href: how-to-create-api-keys.md
-  - name: Troubleshoot common issues
-    href: troubleshoot-managed-grafana.md
   - name: Enable zone redundancy
     href: how-to-enable-zone-redundancy.md
   - name: Use deterministic outbound IPs
     href: how-to-deterministic-ip.md
+  - name: Troubleshoot common issues
+    href: troubleshoot-managed-grafana.md
+  - name: Known limitations
+    href: known-limitations.md
 - name: Reference
   items:
   - name: Azure CLI