Merge pull request #218791 from v-jbasden/jbasden-change-blade-to-pane-across-azure-monitor

[BULK UPDATE #1] Changing "blade" to "pane"

Author: prmerger-automator[bot]

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-linux-vm.md

@@ -20,7 +20,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
 1. **Carefully review the [prerequisites here](./azure-monitor-agent-manage.md#prerequisites).**  
 
 2. **Verify that the extension was successfully installed and provisioned, which installs the agent binaries on your machine**:  
-	1. Open Azure portal > select your virtual machine > Open **Settings** : **Extensions + applications** blade from left menu > 'AzureMonitorLinuxAgent'should show up with Status: 'Provisioning succeeded'  
+	1. Open Azure portal > select your virtual machine > Open **Settings** : **Extensions + applications** from the pane on the left > 'AzureMonitorLinuxAgent'should show up with Status: 'Provisioning succeeded'  
 	2. If you don't see the extension listed, check if machine can reach Azure and find the extension to install using the command below:  
 		```azurecli
 		az vm extension image list-versions --location <machine-region> --name AzureMonitorLinuxAgent --publisher Microsoft.Azure.Monitor
@@ -43,7 +43,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
 
 4. **Verify that the DCR exists and is associated with the virtual machine:**  
 	1. If using Log Analytics workspace as destination, verify that DCR exists in the same physical region as the Log Analytics workspace.  
-	2. Open Azure portal > select your data collection rule > Open **Configuration** : **Resources** blade from left menu > You should see the virtual machine listed here. 
+	2. Open Azure portal > select your data collection rule > Open **Configuration** : **Resources** from the pane on the left > You should see the virtual machine listed here. 
 	3. If not listed, click 'Add' and select your virtual machine from the resource picker. Repeat across all DCRs. 
 	4. If none of the above helps, [file a ticket](#file-a-ticket) with **Summary** as 'DCR not found or associated' and **Problem type** as 'I need help configuring data collection from a VM'.
 

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-windows-arc.md

@@ -20,7 +20,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
 1. **Carefully review the [prerequisites here](./azure-monitor-agent-manage.md#prerequisites).**  
 
 2. **Verify that the extension was successfully installed and provisioned, which installs the agent binaries on your machine**:  
-	1. Open Azure portal > select your Arc-enabled server > Open **Settings** : **Extensions** blade from left menu > 'AzureMonitorWindowsAgent'should show up with Status: 'Succeeded'  
+	1. Open Azure portal > select your Arc-enabled server > Open **Settings** : **Extensions** from the pane on the left > 'AzureMonitorWindowsAgent'should show up with Status: 'Succeeded'  
 	2. If not, check if the Arc agent (Connected Machine Agent) is able to connect to Azure and the extension service is running. 
 		```azurecli
 		azcmagent show
@@ -51,7 +51,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
 4. **Verify that the DCR exists and is associated with the Arc-enabled server:**  
 	1. If using Log Analytics workspace as destination, verify that DCR exists in the same physical region as the Log Analytics workspace.  
 	2. On your Arc-enabled server, verify the existence of the file `C:\Resources\Directory\AMADataStore\mcs\mcsconfig.latest.xml`. If this file doesn't exist, the Arc-enabled server may not be associated with a DCR. 
-	3. Open Azure portal > select your data collection rule > Open **Configuration** : **Resources** blade from left menu > You should see the Arc-enabled server listed here  
+	3. Open Azure portal > select your data collection rule > Open **Configuration** : **Resources** from the pane on the left > You should see the Arc-enabled server listed here  
 	4. If not listed, click 'Add' and select your Arc-enabled server from the resource picker. Repeat across all DCRs.
 	5. If none of the above helps, [file a ticket](#file-a-ticket) with **Summary** as 'DCR not found or associated' and **Problem type** as 'I need help configuring data collection from a VM'.
 

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-windows-vm.md

@@ -19,7 +19,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
 1. **Carefully review the [prerequisites here](./azure-monitor-agent-manage.md#prerequisites).**  
 
 2. **Verify that the extension was successfully installed and provisioned, which installs the agent binaries on your machine**:  
-	1. Open Azure portal > select your virtual machine > Open **Settings** : **Extensions + applications** blade from left menu > 'AzureMonitorWindowsAgent'should show up with Status: 'Provisioning succeeded'  
+	1. Open Azure portal > select your virtual machine > Open **Settings** : **Extensions + applications** from the pane on the left > 'AzureMonitorWindowsAgent'should show up with Status: 'Provisioning succeeded'  
 	2. If not, check if machine can reach Azure and find the extension to install using the command below:  
 		```azurecli
 		az vm extension image list-versions --location <machine-region> --name AzureMonitorWindowsAgent --publisher Microsoft.Azure.Monitor
@@ -44,7 +44,7 @@ Follow the steps below to troubleshoot the latest version of the Azure Monitor a
 		- The virtual machine may not have Managed Identity enabled. [See here](../../active-directory/managed-identities-azure-resources/qs-configure-portal-windows-vm.md#enable-system-assigned-managed-identity-during-creation-of-a-vm) on how to enable. 
 		- IMDS service is not running/accessible from the virtual machine. [Check if you can access IMDS from the machine](../../virtual-machines/windows/instance-metadata-service.md?tabs=windows). If not, [file a ticket](#file-a-ticket) with **Summary** as 'IMDS service not running' and **Problem type** as 'I need help configuring data collection from a VM'.
 		- AMA cannot access IMDS. Check if you see IMDS errors in `C:\WindowsAzure\Resources\AMADataStore.<virtual-machine-name>\Tables\MAEventTable.tsf` file. If yes, [file a ticket](#file-a-ticket) with **Summary** as 'AMA cannot access IMDS' and **Problem type** as 'I need help configuring data collection from a VM'.
-	3. Open Azure portal > select your data collection rule > Open **Configuration** : **Resources** blade from left menu > You should see the virtual machine listed here  
+	3. Open Azure portal > select your data collection rule > Open **Configuration** : **Resources** from the pane on the left > You should see the virtual machine listed here  
 	4. If not listed, click 'Add' and select your virtual machine from the resource picker. Repeat across all DCRs.
 	5. If none of the above helps, [file a ticket](#file-a-ticket) with **Summary** as 'DCR not found or associated' and **Problem type** as 'I need help configuring data collection from a VM'.
 

articles/azure-monitor/agents/data-sources-event-tracing-windows.md

@@ -46,9 +46,9 @@ Ensure the *Windows diagnostics extension* is [installed](./diagnostics-extensio
 
 ### Step 3: Configure ETW log collection
 
-1. Navigate to the **Diagnostic Settings** blade of the virtual machine
+1. From the pane on the left, navigate to the **Diagnostic Settings** for the virtual machine
 
-2. Select the **Logs** tab
+2. Select the **Logs** tab.
 
 3. Scroll down and enable the **Event tracing for Windows (ETW) events** option
 ![Screenshot of diagnostics settings](./media/data-sources-event-tracing-windows/enable-event-tracing-windows-collection.png)

articles/azure-monitor/alerts/alerts-logic-apps.md

@@ -179,7 +179,7 @@ To trigger your Logic app, create an action group, then create an alert that use
 1. Select **OK**.
 1. Enter a name in the **Name** field.
 1. Select **Review + create**, the **Create**.
-:::image type="content" source="./media/alerts-logic-apps/create-action-group-actions.png" alt-text="A screenshot showing the Logic Apps blade of a create action group, actions tab.":::
+:::image type="content" source="./media/alerts-logic-apps/create-action-group-actions.png" alt-text="A screenshot showing the Logic Apps pane of a create action group, actions tab.":::
 
 ## Test your action group
 
@@ -204,7 +204,7 @@ The following email will be sent to the specified account:
 1. Select your action group from the list.
 1. Select **Select**.
 1. Finish the creation of your rule.
- :::image type="content" source="./media/alerts-logic-apps/select-action-groups.png" alt-text="A screenshot showing the actions tab of the create rules page and the select action groups blade.":::
+ :::image type="content" source="./media/alerts-logic-apps/select-action-groups.png" alt-text="A screenshot showing the actions tab of the create rules page and the select action groups pane.":::
 
 ## Next steps
 

articles/azure-monitor/alerts/alerts-smart-detections-migration.md

@@ -34,7 +34,7 @@ A new set of alert rules is created when migrating an Application Insights resou
 | Potential security issue detected (preview)        | *discontinued* <sup>(3)</sup>  |
 | Abnormal rise in daily data volume (preview)       | *discontinued* <sup>(3)</sup>  |
 
-<sup>(1)</sup> Name of rule as appears in smart detection Settings blade  
+<sup>(1)</sup> Name of rule as appears in smart detection Settings pane  
 <sup>(2)</sup> Name of new alert rule after migration  
 <sup>(3)</sup> These smart detection capabilities aren't converted to alerts, because of low usage and reassessment of detection effectiveness. These detectors will no longer be supported for this resource once its migration is completed. 
 

articles/azure-monitor/alerts/proactive-diagnostics.md

@@ -15,7 +15,7 @@ ms.reviewer: yagil
 
 Smart detection automatically warns you of potential performance problems and failure anomalies in your web application. It performs proactive analysis of the telemetry that your app sends to [Application Insights](../app/app-insights-overview.md). If there is a sudden rise in failure rates, or abnormal patterns in client or server performance, you get an alert. This feature needs no configuration. It operates if your application sends enough telemetry.
 
-You can access the detections issued by smart detection both from the emails you receive, and from the smart detection blade.
+You can access the detections issued by smart detection both from the emails you receive, and from the smart detection pane.
 
 ## Review your smart detections
 You can discover detections in two ways:
@@ -25,7 +25,7 @@ You can discover detections in two ways:
     ![Email alert](./media/proactive-diagnostics/03.png)
 
     Click the large button to open more detail in the portal.
-* **The smart detection blade** in Application Insights. Select **Smart detection** under the **Investigate** menu to see a list of recent detections.
+* **The smart detection pane** in Application Insights. Select **Smart detection** under the **Investigate** menu to see a list of recent detections.
 
 ![View recent detections](./media/proactive-diagnostics/04.png)
 
@@ -45,7 +45,7 @@ Smart detection detects and notifies about various issues, such as:
 
 All smart detection rules, except for rules marked as _preview_, are configured by default to send email notifications when detections are found.
 
-Configuring email notifications for a specific smart detection rule can be done by opening the smart detection **Settings** blade and selecting the rule, which will open the **Edit rule** blade.
+Configuring email notifications for a specific smart detection rule can be done by opening the smart detection **Settings** pane and selecting the rule, which will open the **Edit rule** pane.
 
 Alternatively, you can change the configuration using Azure Resource Manager templates. For more information, see [Manage Application Insights smart detection rules using Azure Resource Manager templates](./proactive-arm-config.md) for more details.
 

articles/azure-monitor/alerts/proactive-performance-diagnostics.md

@@ -42,7 +42,7 @@ The notifications include diagnostic information. Here's an example:
 2. **Scope**. Is the problem affecting all traffic, or just some pages? Is it restricted to particular browsers or locations? This information can be obtained from the notification.
 3. **Diagnose**. Often, the diagnostic information in the notification will suggest the nature of the problem. For example, if response time slows down when request rate is high, it may indicate that your server or dependencies are beyond their capacity. 
 
-    Otherwise, open the Performance blade in Application Insights. You'll find there [Profiler](../profiler/profiler.md) data. If exceptions are thrown, you can also try the [snapshot debugger](../snapshot-debugger/snapshot-debugger.md).
+    Otherwise, open the Performance pane in Application Insights. You'll find there [Profiler](../profiler/profiler.md) data. If exceptions are thrown, you can also try the [snapshot debugger](../snapshot-debugger/snapshot-debugger.md).
 
 ## Configure Email Notifications
 

articles/azure-monitor/containers/container-insights-enable-arc-enabled-clusters.md

@@ -156,11 +156,11 @@ az k8s-extension create --name azuremonitor-containers --cluster-name <cluster-n
 >[!IMPORTANT]
 >  If you are deploying Azure Monitor on a Kubernetes cluster running on top of Azure Stack Edge, then the Azure CLI option needs to be followed instead of the Azure portal option as a custom mount path needs to be set for these clusters.    
 
-### Onboarding from the Azure Arc-enabled Kubernetes resource blade
+### Onboarding from the Azure Arc-enabled Kubernetes resource pane
 
 1. In the Azure portal, select the Azure Arc-enabled Kubernetes cluster that you wish to monitor.
 
-2. Select the 'Insights' item under the 'Monitoring' section of the resource blade.
+2. From the resource pane on the left, select the 'Insights' item under the 'Monitoring' section.
 
 3. On the onboarding page, select the 'Configure Azure Monitor' button
 
@@ -210,7 +210,7 @@ Once you have successfully created the Azure Monitor extension for your Azure Ar
 
 ### [Azure portal](#tab/verify-portal)
 1. In the Azure portal, select the Azure Arc-enabled Kubernetes cluster with the extension installing
-2. Select the 'Extensions' item under the 'Settings' section of the resource blade
+2. From the resource pane on the left, select the 'Extensions' item under the 'Settings' section.
 3. You should see an extension with the name 'azuremonitor-containers' listed, with the listed status in the 'Install status' column
 ### [CLI](#tab/verify-cli)
 Run the following command to show the latest status of the `Microsoft.AzureMonitor.Containers` extension

articles/azure-monitor/essentials/collect-custom-metrics-guestos-vm-classic.md

@@ -38,7 +38,7 @@ The process that's outlined in this article only works on classic virtual machin
 
 1. When you're creating this VM, choose the option to create a new classic storage account. We use this storage account in later steps.
 
-1. In the Azure portal, go to the **Storage accounts** resource blade. Select **Keys**, and take note of the storage account name and storage account key. You need this information in later steps.
+1. In the Azure portal, go to the **Storage accounts** resource pane. Select **Keys**, and take note of the storage account name and storage account key. You need this information in later steps.
    ![Storage access keys](./media/collect-custom-metrics-guestos-vm-classic/storage-access-keys.png)
 
 ## Create a service principal
@@ -185,7 +185,7 @@ Give this app “Monitoring Metrics Publisher” permissions to the resource tha
 
 1.	On the left menu, select **Monitor.**
 
-1.	On the **Monitor** blade, select **Metrics**.
+1.	On the **Monitor** pane on the left, select **Metrics**.
 
     ![Navigate metrics](./media/collect-custom-metrics-guestos-vm-classic/navigate-metrics.png)