Resource menu replaced with service menu

ProfessorKendrick · ProfessorKendrick · commit 07c231fd2c29 · 2025-05-28T14:00:52.000-04:00
diff --git a/articles/partner-solutions/datadog/manage.md b/articles/partner-solutions/datadog/manage.md
@@ -53,11 +53,11 @@ A summary of resources is also displayed in the working pane.
 
 To change the configuration rules for metrics and logs:
 
-1. Select **Datadog organization configurations > Metrics and Logs** from the Resource menu.
+1. Select **Datadog organization configurations > Metrics and Logs** from the service menu.
 
 ## View monitored resources
 
-To view the list of resources emitting logs to Datadog, select **Datadog organization configurations > Monitored Resources** in the Resource menu.
+To view the list of resources emitting logs to Datadog, select **Datadog organization configurations > Monitored Resources** in the service menu.
 
 > [!TIP]
 > You can filter the list of resources by resource type, subscription, resource group name, location, and whether the resource is sending logs and metrics. 
@@ -91,7 +91,7 @@ Once the subscription is added, the status changes to *Active*.
 
 To unlink subscriptions from a Datadog resource:
 
-1. Select **Datadog organization configurations > Monitored Subscriptions** from the Resource menu. 
+1. Select **Datadog organization configurations > Monitored Subscriptions** from the service menu. 
 
 1. Select the subscription you want to remove.
 
@@ -103,7 +103,7 @@ To view the updated list of monitored subscriptions, select **Refresh** from the
 
 To view the list of API keys for your Datadog resource:
 
-1. Select **Settings > Keys** from the Resource menu.
+1. Select **Settings > Keys** from the service menu.
 
     The Azure portal provides a read-only view of the API keys. 
 
diff --git a/articles/partner-solutions/dynatrace/manage.md b/articles/partner-solutions/dynatrace/manage.md
@@ -39,13 +39,13 @@ Below the essentials, you can navigate to other details about your resource by s
 
 ## Reconfigure rules for metrics and logs
 
-To change the configuration rules for logs, select **Metrics and logs** in the Resource menu on the left.
+To change the configuration rules for logs, select **Metrics and logs** in the service menu on the left.
 
 For more information, see [Configure metrics and logs](dynatrace-create.md#configure-metrics-and-logs).
 
 ## View monitored resources
 
-To view the list of resources emitting logs to Dynatrace, select **Dynatrace environment config > Monitored Resources** in the Resource menu.
+To view the list of resources emitting logs to Dynatrace, select **Dynatrace environment config > Monitored Resources** in the service menu.
 
 > [!TIP]
 > You can filter the list of resources by resource type, resource group name, region, and whether the resource is sending logs and/or metrics. 
diff --git a/articles/partner-solutions/elastic/manage.md b/articles/partner-solutions/elastic/manage.md
@@ -47,7 +47,7 @@ Make the needed changes to how logs are sent to Elastic.
 
 ## View monitored resources
 
-To view the list of resources emitting logs to Elastic, select **Elastic deployment configuration > Monitored resources** in the Resource menu.
+To view the list of resources emitting logs to Elastic, select **Elastic deployment configuration > Monitored resources** in the service menu.
 
 > [!TIP]
 > You can filter the list of resources by type, subscription, resource group, region, and whether the resource is sending logs to Elastic. 
@@ -77,7 +77,7 @@ Once the subscription is added, the status changes to *Active*.
 
 To unlink subscriptions from a Elastic resource:
 
-1. Select **Elastic deployment configuration > Monitored Subscriptions** from the Resource menu. 
+1. Select **Elastic deployment configuration > Monitored Subscriptions** from the service menu. 
 
 1. Select the subscription you want to remove.
 
@@ -91,7 +91,7 @@ You can install Elastic agents on virtual machines.
 
 ### Virtual machines
 
-To monitor resources for virtual machines, select **Elastic deployment configuration > Virtual machine agent** in the Resource menu.
+To monitor resources for virtual machines, select **Elastic deployment configuration > Virtual machine agent** in the service menu.
 
 [!INCLUDE [install-elastic-agent](../includes/agent.md)]
 
diff --git a/articles/partner-solutions/informatica/create-advanced-serverless.md b/articles/partner-solutions/informatica/create-advanced-serverless.md
@@ -25,7 +25,7 @@ In this quickstart, you use the Azure portal to create advanced serverless runti
 
 In this section, you see how to create an advanced serverless deployment of Informatica Intelligent Data Management Cloud (Informatica IDMC) using the Azure portal.
 
-In the Informatica organization,  select **Serverless Runtime Environment** from the resource menu to navigate to _Advanced Serverless_ section where the existing list of serverless runtime environments are shown.
+In the Informatica organization,  select **Serverless Runtime Environment** from the service menu to navigate to _Advanced Serverless_ section where the existing list of serverless runtime environments are shown.
 
 :::image type="content" source="media/informatica-create-advanced-serverless/informatica-serverless.png" alt-text="Screenshot of Informatica serverless runtime environments pane.":::
 
diff --git a/articles/partner-solutions/informatica/create.md b/articles/partner-solutions/informatica/create.md
@@ -71,7 +71,7 @@ You can specify custom tags for the new Informatica resource in Azure by adding
 
     :::image type="content" source="media/informatica-create/informatica-deploy.png" alt-text="Screenshot of a completed Informatica deployment.":::
 
-1. Select **Overview** in the Resource menu to see information on the deployed resources.
+1. Select **Overview** in the service menu to see information on the deployed resources.
 
     :::image type="content" source="media/informatica-create/informatica-overview-pane.png" alt-text="Screenshot of information on the Informatica resource overview.":::
 
diff --git a/articles/partner-solutions/informatica/manage-serverless.md b/articles/partner-solutions/informatica/manage-serverless.md
@@ -12,7 +12,7 @@ In this article, you learn various actions available for each of the serverless
 
 ## Actions
 
-1. Within your Informatica organization, select **Serverless Runtime Environment** from the Resource menu in your Informatica organization.
+1. Within your Informatica organization, select **Serverless Runtime Environment** from the service menu in your Informatica organization.
 
 1. Use actions from the context menu to manage your serverless runtime environments in **Serverless Runtime Environment** pane.
 
diff --git a/articles/partner-solutions/informatica/manage.md b/articles/partner-solutions/informatica/manage.md
@@ -30,7 +30,7 @@ Single sign-on (SSO) is already enabled when you created your Informatica Organi
 
 Once the Astro resource is deleted, all billing stops for that resource through Azure Marketplace. If you're done using your resource and would like to delete the same, follow these steps:
 
-1. From the Resource menu, select the Informatica deployment you would like to delete.
+1. From the service menu, select the Informatica deployment you would like to delete.
 
 1. On the working pane of the **Overview**, select **Delete**.
 
diff --git a/articles/partner-solutions/palo-alto/application-gateway.md b/articles/partner-solutions/palo-alto/application-gateway.md
@@ -39,7 +39,7 @@ Application Gateway is deployed in a dedicated virtual network with a front end
 
 Similar to spoke virtual networks, the Application Gateway virtual network must be peered with the hub virtual network to ensure that the traffic can be routed toward the destination spoke virtual network.
 
-To force incoming web traffic through the Cloud NGFW for Azure resource, you must create a user-defined route and associate it with the Application Gateway subnet. The next hop in this case is the private IP address of Cloud NGFW for Azure. You can find this address by selecting **Overview** from the resource menu in the Azure portal.
+To force incoming web traffic through the Cloud NGFW for Azure resource, you must create a user-defined route and associate it with the Application Gateway subnet. The next hop in this case is the private IP address of Cloud NGFW for Azure. You can find this address by selecting **Overview** from the service menu in the Azure portal.
 
 :::image type="content" source="media/palo-alto-app-gateway/palo-alto-resource.png" alt-text="Screenshot that shows the Cloud NGFW for Azure view in the Azure portal.":::
 
diff --git a/articles/partner-solutions/palo-alto/create.md b/articles/partner-solutions/palo-alto/create.md
@@ -99,7 +99,7 @@ Next, you must accept the Terms of Use for the new Palo Alto Networks resource.
 
 1. Once the create process is completed, select **Go to Resource** to navigate to the specific Cloud NGFW by Palo Alto Networks resource.
 
-1. Select **Overview** in the Resource menu to see information on the deployed resources.
+1. Select **Overview** in the service menu to see information on the deployed resources.
 
 ## Next steps
 
diff --git a/articles/partner-solutions/palo-alto/manage.md b/articles/partner-solutions/palo-alto/manage.md
@@ -20,11 +20,11 @@ Once your Cloud NGFW by Palo Alto Networks resource is created in the Azure port
 - [Rules](#rules)
 - [Delete a resource](#delete-a-resource)
 
-From the Resource menu, select your Cloud NGFW by Palo Alto Networks deployment. Use the Resource menu to move through the settings for your Cloud NGFW by Palo Alto Networks.
+From the service menu, select your Cloud NGFW by Palo Alto Networks deployment. Use the service menu to move through the settings for your Cloud NGFW by Palo Alto Networks.
 
 ## Networking and NAT
 
-1. Select **Networking & NAT** in the Resource menu.
+1. Select **Networking & NAT** in the service menu.
 
 1. Select the **Type** by checking the **Virtual Network** or **Virtual WAN** options.
 
@@ -36,15 +36,15 @@ From the Resource menu, select your Cloud NGFW by Palo Alto Networks deployment.
 
 ## Rulestack
 
-1. Select **Rulestack** in the Resource menu.
+1. Select **Rulestack** in the service menu.
 
 1. For the **Managed by**, select either **Azure Portal** or **"Palo Alto Networks Panorama** to determine the mechanism for managing Rulestack. You must have Palo Alto Networks Panorama set up in order to select it.
 
 1. For the **Local Rulestack**, select an existing Rulestack from the dropdown.
 
 ## Log settings
 
-1. Select **Log Settings** in the Resource menu.
+1. Select **Log Settings** in the service menu.
 
 1. Select **edit** to enable **Log Settings**.
 
@@ -54,7 +54,7 @@ From the Resource menu, select your Cloud NGFW by Palo Alto Networks deployment.
 
 ## DNS Proxy
 
-1. Select **DNS Proxy** in the Resource menu.
+1. Select **DNS Proxy** in the service menu.
 
 1. Select either **Enable** or **Disable**.
 
@@ -72,7 +72,7 @@ To change the Cloud NGFW's billing plan, go to **Overview** and select **Change
 
 To delete a Cloud NGFW by Palo Alto Networks resource
 
-1. Select **Overview** in the Resource menu.
+1. Select **Overview** in the service menu.
 
 1. Select **Delete**.
 
