Merge pull request #294910 from maud-lv/ml-amgworkspace3

Bulk wording fix

Author: v-ccolin

articles/managed-grafana/encryption.md

@@ -37,4 +37,4 @@ In this model, all key management aspects such as key issuance, rotation, and ba
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Monitor your Azure Managed Grafana instance](how-to-monitor-managed-grafana-workspace.md)
+> [Monitor Azure Managed Grafana](how-to-monitor-managed-grafana-workspace.md)

articles/managed-grafana/faq.md

@@ -19,7 +19,7 @@ No. Azure Managed Grafana hosts a commercial version called [Grafana Enterprise]
 > [!NOTE]
 > [Grafana Enterprise plugins](https://grafana.com/grafana/plugins/?enterprise=1&orderBy=weight&direction=asc) aren't included in the base service. They're purchasable as a separately licensed [add-on option](./how-to-grafana-enterprise.md) for Azure Managed Grafana.
 
-## Does Managed Grafana encrypt my data?
+## Does Azure Managed Grafana encrypt my data?
 
 Yes. Azure Managed Grafana always encrypts all data at rest and in transit. It supports [encryption at rest](./encryption.md) using Microsoft-managed keys. All network communication is over TLS 1.2. You can further restrict network traffic using a [private link](./how-to-set-up-private-access.md) for connecting to Grafana and [managed private endpoints](./how-to-connect-to-data-source-privately.md) for data sources.
 
@@ -33,7 +33,7 @@ No. Azure Managed Grafana uses its implementation for Microsoft Entra authentica
 
 ## Can I install more plugins?
 
-No. Currently all Grafana plugins are preinstalled. Managed Grafana supports all popular plugins for Azure data sources.
+No. Currently all Grafana plugins are preinstalled. Azure Managed Grafana supports all popular plugins for Azure data sources.
 
 ## In terms of pricing, what constitutes an active user in Azure Managed Grafana?
 

articles/managed-grafana/high-availability.md

@@ -11,28 +11,28 @@ ms.custom: references_regions, engagement-fy23
 
 # Azure Managed Grafana service reliability
 
-This article provides information on availability zone support, disaster recovery and availability of Azure Managed Grafana for instances in the Standard plan. The Essential plan (preview) doesn't offer the same reliability and isn't recommended for use in production.
+This article provides information on availability zone support, disaster recovery and availability of Azure Managed Grafana for workspaces in the Standard plan. The Essential plan (preview) doesn't offer the same reliability and isn't recommended for use in production.
 
-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.
+An Azure Managed Grafana workspace 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 Azure Managed Grafana workspace.
 
-:::image type="content" source="media/service-reliability/diagram.png" alt-text="Diagram of the Managed Grafana Standard tier instance setup.":::
+:::image type="content" source="media/service-reliability/diagram.png" alt-text="Diagram of the Azure Managed Grafana Standard tier workspace setup.":::
 
-The load balancer always keeps track of which Grafana servers are available. In a dual-server setup, if it detects that one server is down, the load balancer starts sending all requests to the remaining server. That server should be able to pick up the browser sessions previously served by the other one based on information saved in the shared database. In the meantime, the Managed Grafana service will work to repair the unhealthy server or bring up a new one.
+The load balancer always keeps track of which Grafana servers are available. In a dual-server setup, if it detects that one server is down, the load balancer starts sending all requests to the remaining server. That server should be able to pick up the browser sessions previously served by the other one based on information saved in the shared database. In the meantime, the Azure Managed Grafana service will work to repair the unhealthy server or bring up a new one.
 
-Microsoft is not providing or setting up disaster recovery for this service. In case of a region level outage, service will experience downtime and users can set up additional instances in other regions for disaster recovery purposes.
+Microsoft is not providing or setting up disaster recovery for this service. In case of a region level outage, service will experience downtime and users can set up additional workspaces in other regions for disaster recovery purposes.
 
 ## Zone redundancy
 
-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.
+The network load balancer, VMs and database that underpin an Azure Managed Grafana workspace 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](../reliability/availability-zones-overview.md). 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.
+In a zone-wide outage, no user action is required. An impacted Azure Managed Grafana workspace will rebalance itself to take advantage of the healthy zone automatically. The Azure Managed Grafana service will attempt to heal the affected workspaces during zone recovery.
 
 > [!NOTE]
-> Zone redundancy can only be enabled when creating the Azure Managed Grafana instance, and can't be modified subsequently. The zone redundancy option comes with an additional cost. Go to [Azure Managed Grafana pricing](https://azure.microsoft.com/pricing/details/managed-grafana/) for details.
+> Zone redundancy can only be enabled when creating the Azure Managed Grafana workspace, and can't be modified subsequently. The zone redundancy option comes with an additional cost. Go to [Azure Managed Grafana pricing](https://azure.microsoft.com/pricing/details/managed-grafana/) for details.
 
 ### With zone redundancy disabled
 
@@ -48,7 +48,7 @@ Zone redundancy support is enabled in the following regions:
 | South Central US |                   |                   | East Asia         |
 | West US 3        |                   |                   |                   |
 
-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)
+For a complete list of regions where Azure 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-api-calls.md

@@ -24,16 +24,16 @@ In this tutorial, you learn how to:
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/).
-- An Azure Managed Grafana workspace. [Create an Azure Managed Grafana instance](./quickstart-managed-grafana-portal.md).
-- A Microsoft Entra application with a service principal. [Create a Microsoft Entra application and service principal](../active-directory/develop/howto-create-service-principal-portal.md). For simplicity, use an application located in the same Microsoft Entra tenant as your Azure Managed Grafana instance.
+- An Azure Managed Grafana workspace. [Create an Azure Managed Grafana workspace](./quickstart-managed-grafana-portal.md).
+- A Microsoft Entra application with a service principal. [Create a Microsoft Entra application and service principal](../active-directory/develop/howto-create-service-principal-portal.md). For simplicity, use an application located in the same Microsoft Entra tenant as your Azure Managed Grafana workspace.
 
 ## Sign in to Azure
 
 Sign in to the Azure portal at [https://portal.azure.com/](https://portal.azure.com/) with your Azure account.
 
 ## Assign an Azure Managed Grafana role to the service principal of your application
 
-1. In the Azure portal, open your Managed Grafana instance.
+1. In the Azure portal, open your Azure Managed Grafana workspace.
 1. Select **Access control (IAM)** in the navigation menu.
 1. Select **Add**, then **Add role assignment**.
 1. Select the **Grafana Editor** role and then **Next**.
@@ -77,7 +77,7 @@ You now need to gather some information, which you'll use to get a Grafana API a
 1. Find the Grafana endpoint URL:
 
    1. In the Azure portal, enter *Azure Managed Grafana* in the **Search resources, services, and docs (G+ /)** bar.
-   1. Select **Azure Managed Grafana** and open your Managed Grafana workspace.
+   1. Select **Azure Managed Grafana** and open your Azure Managed Grafana workspace.
    1. Select **Overview** from the left menu and save the **Endpoint** value.
 
     :::image type="content" source="media/tutorial-api/endpoint-url.png" alt-text="Screenshot of the Azure platform. Endpoint displayed in the Overview page.":::
@@ -145,7 +145,7 @@ curl -X GET \
 https://<grafana-url>/api/user
 ```
 
-Replace `<access-token>` and `<grafana-url>` with the access token retrieved in the previous step and the endpoint URL of your Grafana instance. For example `https://my-grafana-abcd.cuse.grafana.azure.com`.
+Replace `<access-token>` and `<grafana-url>` with the access token retrieved in the previous step and the endpoint URL of your Grafana workspace. For example `https://my-grafana-abcd.cuse.grafana.azure.com`.
 
 ## Clean up resources
 

articles/managed-grafana/how-to-connect-azure-data-explorer.md

@@ -18,7 +18,7 @@ Azure Data Explorer is a logs & telemetry data exploration service. In this guid
 
 ## Prerequisites
 
-* [An Azure Managed Grafana instance](./quickstart-managed-grafana-portal.md) in the Standard plan.
+* [An Azure Managed Grafana workspace](./quickstart-managed-grafana-portal.md) in the Standard plan.
 * [An Azure Data Explorer database](/azure/data-explorer/create-cluster-database)
 
 ::: zone pivot="aro-azureportal"
@@ -27,7 +27,7 @@ Azure Data Explorer is a logs & telemetry data exploration service. In this guid
 
 Add an Azure Data Explorer data source to Grafana by following the steps below.
 
-1. Open an Azure Managed Grafana instance in the Azure portal.
+1. Open an Azure Managed Grafana workspace in the Azure portal.
 1. In the **Overview** section, open the **Endpoint** URL.
 1. In the Grafana portal, go to **Connections** > **Data sources** > **Add new data source**, then search and select **Azure Data Explorer Datasource**.
 

articles/managed-grafana/how-to-connect-azure-monitor-workspace.md

@@ -15,7 +15,7 @@ In this guide, learn how to connect an Azure Monitor workspace to Grafana direct
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free).
-- An Azure Managed Grafana instance in the Standard tier. [Create a new instance](quickstart-managed-grafana-portal.md) if you don't have one.
+- An Azure Managed Grafana workspace in the Standard tier. [Create a new workspace](quickstart-managed-grafana-portal.md) if you don't have one.
 - An [Azure Monitor workspace with Prometheus data](/azure/azure-monitor/containers/monitor-kubernetes).
 
 ## Add a new role assignment

articles/managed-grafana/how-to-connect-to-data-source-privately.md

@@ -1,6 +1,6 @@
 ---
 title: How to connect to a data source privately in Azure Managed Grafana
-description: Learn how to connect an Azure Managed Grafana instance to a data source using Managed Private Endpoint
+description: Learn how to connect an Azure Managed Grafana workspace to a data source using Managed Private Endpoint
 ms.service: azure-managed-grafana
 ms.topic: how-to
 author: maud-lv
@@ -10,7 +10,7 @@ ms.date: 02/05/2024
 
 # Connect to a data source privately
 
-In this guide, you learn how to connect your Azure Managed Grafana instance to a data source using Managed Private Endpoint. Azure Managed Grafana’s managed private endpoints are endpoints created in a Managed Virtual Network that the Azure Managed Grafana service uses. They establish private links from that network to your Azure data sources. Azure Managed Grafana sets up and manages these private endpoints on your behalf. You can create managed private endpoints from your Azure Managed Grafana to access other Azure managed services (for example, Azure Monitor private link scope or Azure Monitor workspace) and your own self-hosted data sources (for example, connecting to your self-hosted Prometheus behind a private link service).
+In this guide, you learn how to connect your Azure Managed Grafana workspace to a data source using Managed Private Endpoint. Azure Managed Grafana’s managed private endpoints are endpoints created in a Managed Virtual Network that the Azure Managed Grafana service uses. They establish private links from that network to your Azure data sources. Azure Managed Grafana sets up and manages these private endpoints on your behalf. You can create managed private endpoints from your Azure Managed Grafana to access other Azure managed services (for example, Azure Monitor private link scope or Azure Monitor workspace) and your own self-hosted data sources (for example, connecting to your self-hosted Prometheus behind a private link service).
 
 When you use managed private endpoints, traffic between your Azure Managed Grafana and its data sources traverses exclusively over the Microsoft backbone network without going through the internet. Managed private endpoints protect against data exfiltration. A managed private endpoint uses a private IP address from your Managed Virtual Network to effectively bring your Azure Managed Grafana workspace into that network. Each managed private endpoint is mapped to a specific resource in Azure and not the entire service. Customers can limit connectivity to only resources approved by their organizations.
 
@@ -33,7 +33,7 @@ Managed private endpoints work with Azure services that support private link. Us
 - Azure Data Explorer
 - Azure Monitor private link scope (for example, Log Analytics workspace)
 - Azure Monitor workspace, for Managed Service for Prometheus
-- Azure SQL managed instance
+- Azure SQL managed workspace
 - Azure SQL server
 - Private link services
 - Azure Databricks
@@ -44,7 +44,7 @@ Managed private endpoints work with Azure services that support private link. Us
 To follow the steps in this guide, you must have:
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free).
-- An Azure Managed Grafana instance in the Standard tier. If you don't have one yet, [create a new instance](quickstart-managed-grafana-portal.md).
+- An Azure Managed Grafana workspace in the Standard tier. If you don't have one yet, [create a new instance](quickstart-managed-grafana-portal.md).
 
 ## Create a managed private endpoint for Azure Monitor workspace