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

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

Author: prmerger-automator[bot]

articles/azure-monitor/app/status-monitor-v2-get-started.md

@@ -21,7 +21,7 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
 
 ### Install prerequisites
 
-- To enable monitoring you will require a connection string. A connection string is displayed on the Overview blade of your Application Insights resource. For more information, see page [Connection Strings](./sdk-connection-string.md?tabs=net#find-your-connection-string).
+- To enable monitoring you will require a connection string. A connection string is displayed on the Overview pane of your Application Insights resource. For more information, see page [Connection Strings](./sdk-connection-string.md?tabs=net#find-your-connection-string).
 
 > [!NOTE]
 > As of April 2020, PowerShell Gallery has deprecated TLS 1.1 and 1.0.

articles/azure-monitor/app/tutorial-asp-net-core.md

@@ -118,7 +118,7 @@ In order to provide globally unique names to resources, a six-character suffix i
     | Name  | APPLICATIONINSIGHTS_CONNECTION_STRING |
     | Value | Paste the Application Insights connection string value you copied in the preceding section. |
 
-    :::image type="content" source="media/tutorial-asp-net-core/add-edit-app-setting.png" alt-text="Screenshot of the Add/Edit application setting blade in the Azure portal with the preceding values populated in the Name and Value fields." lightbox="media/tutorial-asp-net-core/add-edit-app-setting.png":::
+    :::image type="content" source="media/tutorial-asp-net-core/add-edit-app-setting.png" alt-text="Screenshot of the Add/Edit application setting pane in the Azure portal with the preceding values populated in the Name and Value fields." lightbox="media/tutorial-asp-net-core/add-edit-app-setting.png":::
 
 4. On the App Service Configuration screen, select the **Save** button from the toolbar menu. When prompted to save the changes, select **Continue**.
 

articles/azure-monitor/change/change-analysis-visualizations.md

@@ -39,13 +39,13 @@ Select one or more subscriptions to view:
 - All of its resources' changes from the past 24 hours. 
 - Old and new values to provide insights at one glance.
 
-:::image type="content" source="./media/change-analysis/change-analysis-standalone-blade.png" alt-text="Screenshot of Change Analysis blade in Azure portal":::
+:::image type="content" source="./media/change-analysis/change-analysis-standalone-blade.png" alt-text="Screenshot of Change Analysis pane in Azure portal":::
 
 Click into a change to view full Resource Manager snippet and other properties.
 
 :::image type="content" source="./media/change-analysis/change-details.png" alt-text="Screenshot of change details":::
 
-Send feedback from the Change Analysis blade:
+Send feedback from the Change Analysis pane:
 
 :::image type="content" source="./media/change-analysis/change-analysis-feedback.png" alt-text="Screenshot of feedback button in Change Analysis tab":::
 

articles/azure-monitor/change/tutorial-outages.md

@@ -117,7 +117,7 @@ Since the connection string is a secret value, we hide this on the overview page
 
 :::image type="content" source="./media/change-analysis/view-change-details.png" alt-text="Screenshot of viewing change details for troubleshooting.":::
 
-The change details blade also shows important information, including who made the change. 
+The change details pane also shows important information, including who made the change. 
 
 Now that you've discovered the web app in-guest change and understand next steps, you can proceed with troubleshooting the issue. 
 

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

@@ -97,7 +97,7 @@ Run the following commands to locate the full Azure Resource Manager identifier
     In the output, find the workspace name of interest. The `id` field of that represents the Azure Resource Manager identifier of that Log Analytics workspace.
 
     >[!TIP]
-    > This `id` can also be found in the *Overview* blade of the Log Analytics workspace through the Azure portal.
+    > This `id` can also be found in the *Overview* pane of the Log Analytics workspace through the Azure portal.
 
 ## Create extension instance 
 
@@ -170,9 +170,9 @@ az k8s-extension create --name azuremonitor-containers --cluster-name <cluster-n
 
 6. Select the 'Configure' button to deploy the Azure Monitor Container Insights cluster extension.
 
-### Onboarding from Azure Monitor blade
+### Onboarding from Azure Monitor pane
 
-1. In the Azure portal, navigate to the 'Monitor' blade, and select the 'Containers' option under the 'Insights' menu.
+1. In the Azure portal, navigate to the 'Monitor' pane, and select the 'Containers' option under the 'Insights' menu.
 
 2. Select the 'Unmonitored clusters' tab to view the Azure Arc-enabled Kubernetes clusters that you can enable monitoring for.
 
@@ -267,7 +267,7 @@ az k8s-extension delete --name azuremonitor-containers --cluster-type connectedC
 ```
 
 ## Disconnected cluster
-If your cluster is disconnected from Azure for > 48 hours, then Azure Resource Graph won't have information about your cluster. As a result the Insights blade may display incorrect information about your cluster state.
+If your cluster is disconnected from Azure for > 48 hours, then Azure Resource Graph won't have information about your cluster. As a result the Insights pane may display incorrect information about your cluster state.
 
 ## Troubleshooting
 For issues with enabling monitoring, we have provided a [troubleshooting script](https://aka.ms/azmon-ci-troubleshooting) to help diagnose any problems.

articles/azure-monitor/containers/container-insights-transition-solution.md

@@ -35,7 +35,7 @@ The following table highlights the key differences between monitoring using the
 | Agent | Log Analytics Agent (deprecated in 2024) | [Azure Monitor Agent](../agents/azure-monitor-agent-overview.md)
 | Alerting | Log based alerts tied to Log Analytics Workspace | Log based alerting and [recommended metric-based](./container-insights-metric-alerts.md) alerts |
 | Metrics | Does not support Azure Monitor metrics | Supports Azure Monitor metrics |
-| Consumption | Viewable only from Log Analytics Workspace | Accessible from both Azure Monitor and AKS/Arc resource blade |
+| Consumption | Viewable only from Log Analytics Workspace | Accessible from both Azure Monitor and AKS/Arc resource pane |
 | Agent | Manual agent upgrades | Automatic updates for monitoring agent with version control through Azure Arc cluster extensions |
 
 ## Next steps

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

@@ -35,7 +35,7 @@ The process that's outlined in this article works only for performance counters
 
 1. Create and deploy a classic cloud service. A sample classic Cloud Services application and deployment can be found at [Get started with Azure Cloud Services and ASP.NET](../../cloud-services/cloud-services-dotnet-get-started.md). 
 
-2. You can use an existing storage account or deploy a new storage account. It's best if the storage account is in the same region as the classic cloud service that you created. In the Azure portal, go to the **Storage accounts** resource blade, and then select **Keys**. Take note of the storage account name and the storage account key. You'll need this information in later steps.
+2. You can use an existing storage account or deploy a new storage account. It's best if the storage account is in the same region as the classic cloud service that you created. In the Azure portal, go to the **Storage accounts** resource pane, and then select **Keys**. Take note of the storage account name and the storage account key. You'll need this information in later steps.
 
    ![Storage account keys](./media/collect-custom-metrics-guestos-vm-cloud-service-classic/storage-keys.png)
 
@@ -172,7 +172,7 @@ Set-AzureServiceDiagnosticsExtension -ServiceName <classicCloudServiceName> -Sto
 
 2. On the left menu, select **Monitor.**
 
-3. On the **Monitor** blade, select the **Metrics Preview** tab.
+3. On the **Monitor** pane, select the **Metrics Preview** tab.
 
 4. In the resources drop-down menu, select your classic cloud service.
 

articles/azure-monitor/essentials/resource-logs-blob-format.md

@@ -37,7 +37,7 @@ You are only impacted by this change if you:
 
 To identify if you have  diagnostic settings that are sending data to an Azure storage account, you can navigate to the **Monitor** section of the portal, click on **Diagnostic Settings**, and identify any resources that have **Diagnostic Status** set to **Enabled**:
 
-![Azure Monitor Diagnostic Settings blade](media/resource-logs-blob-format/portal-diag-settings.png)
+![Azure Monitor Diagnostic Settings pane](media/resource-logs-blob-format/portal-diag-settings.png)
 
 If Diagnostic Status is set to enabled, you have an active diagnostic setting on that resource. Click on the resource to see if any diagnostic settings are sending data to a storage account:
 

articles/azure-monitor/insights/ad-assessment.md

@@ -108,7 +108,7 @@ View the summarized compliance assessments for your infrastructure and then dril
 
 1. On the **Overview** page, click the **Active Directory Health Check** tile.
 
-2. On the **Health Check** page, review the summary information in one of the focus area blades and then click one to view recommendations for that focus area.
+2. On the **Health Check** page, review the summary information in one of the focus area panes and then click one to view recommendations for that focus area.
 
 3. On any of the focus area pages, you can view the prioritized recommendations made for your environment. Click a recommendation under **Affected Objects** to view details about why the recommendation is made.
 

articles/azure-monitor/insights/azure-key-vault-deprecated.md

@@ -89,7 +89,7 @@ After you click the **Key Vault Analytics** tile, you can view summaries of your
 
 ### To view details for any operation
 1. On the **Overview** page, click the **Key Vault Analytics** tile.
-2. On the **Azure Key Vault** dashboard, review the summary information in one of the blades, and then click one to view detailed information about it in the log search page.
+2. On the **Azure Key Vault** dashboard, review the summary information in one of the panes, and then click one to view detailed information about it in the log search page.
 
     On any of the log search pages, you can view results by time, detailed results, and your log search history. You can also filter by facets to narrow the results.