Update Azure AI Foundry and Azure AI services references

Author: JKirsch1

articles/api-center/register-discover-mcp-server.md

@@ -18,7 +18,7 @@ ms.custom:
 This article describes how to use Azure API Center to maintain an inventory (or *registry*) of remote model context protocol (MCP) servers and help stakeholders discover them through the API Center portal. MCP servers expose backend APIs or data sources in a standard way to AI agents and models that consume them.
 
 > [!NOTE]
-> New! MCP servers registered in your API Center can now be integrated with Azure AI Foundry's tool catalogs, enabling you to govern MCP tools and make them available to AI agents. Learn more in  [Tool catalog for agents in Azure AI Foundry](/azure/ai-foundry/agents/concepts/tool-catalog) and [Private tool catalogs for Azure AI Foundry agents](/azure/ai-foundry/agents/how-to/private-tool-catalog).
+> New! MCP servers registered in your API Center can now be integrated with Microsoft Foundry's tool catalogs, enabling you to govern MCP tools and make them available to AI agents. Learn more in  [Tool catalog for agents in Foundry](/azure/ai-foundry/agents/concepts/tool-catalog) and [Private tool catalogs for Foundry agents](/azure/ai-foundry/agents/how-to/private-tool-catalog).
 
 [!INCLUDE [about-mcp-servers](includes/about-mcp-servers.md)]
 

articles/app-testing/load-testing/resource-supported-azure-resource-types.md

@@ -28,7 +28,7 @@ This section lists the Azure resource types that Azure Load Testing supports for
 * Azure Application Gateway
 * Azure Batch Service
 * Azure Cache for Redis
-* Azure AI services
+* Foundry Tools
 * Azure Container Apps
 * Azure Container Instances
 * Azure Cosmos DB

articles/automation/shared-resources/modules.md

@@ -61,7 +61,7 @@ The following table lists the modules that Azure Automation imports by default w
 
 The default modules are also known as global modules. In the Azure portal, the **Global module** property will be **true** when viewing a module that was imported when the account was created.
 
-![Screenshot of global module property in Azure Portal](../media/modules/automation-global-modules.png)
+![Screenshot of global module property in Azure portal](../media/modules/automation-global-modules.png)
 
 > [!NOTE]
 > We don't recommend altering modules and runbooks in Automation accounts used for deployment of the [Start/Stop VMs during off-hours](../../azure-functions/start-stop-vms/overview.md)

articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md

@@ -125,7 +125,7 @@ There are some important best practices to follow for optimal performance of NFS
 - Based on your performance requirements, select the correct service level needed for the Azure NetApp Files capacity pool. See [Service levels for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-service-levels.md) to understand the throughput allowed per provisioned TiB for each service level. 
 
     >[!IMPORTANT]
-    > If you've changed the Azure NetApp Files volumes performance tier or the volume size after creating the volume and datastore, see [Service level change for Azure NetApp files datastore](#service-level-change-for-azure-netapp-files-datastore) to ensure that volume/datastore metadata is in sync to avoid unexpected behavior in the portal or the API due to metadata mismatch. To do any kind of change to the volume you can use Azure Portal or any other supported solution (CLI\Powershell\API).
+    > If you've changed the Azure NetApp Files volumes performance tier or the volume size after creating the volume and datastore, see [Service level change for Azure NetApp files datastore](#service-level-change-for-azure-netapp-files-datastore) to ensure that volume/datastore metadata is in sync to avoid unexpected behavior in the portal or the API due to metadata mismatch. To do any kind of change to the volume you can use Azure portal or any other supported solution (CLI\Powershell\API).
     
 - Create one or more volumes based on the required throughput and capacity. See [Performance considerations](../azure-netapp-files/azure-netapp-files-performance-considerations.md) for Azure NetApp Files to understand how volume size, service level, and capacity pool QoS type determines volume throughput. For assistance calculating workload capacity and performance requirements, contact your Azure VMware Solution or Azure NetApp Files field expert. The default maximum number of Azure NetApp Files datastores is 64.
 
@@ -228,7 +228,7 @@ az vmware datastore netapp-volume create \
 
 You can use the instructions provided to delete an Azure NetApp Files-based datastore using either Azure portal or Azure CLI. There's no maintenance window required for this operation. The delete action only removes the Azure NetApp Files volume as a datastore and it doesn't delete the data or the Azure NetApp Files volume.
 
-**Delete an Azure NetApp Files datastore using the Azure Portal**
+**Delete an Azure NetApp Files datastore using the Azure portal**
 
 1. Select the datastore you want to delete from.
 

articles/azure-vmware/native-network-design-consideration.md

@@ -27,7 +27,7 @@ The following functionality is limited during this time. These limitations will
 4. Your private cloud and virtual network for your private cloud must be in the ***same*** Resource Group.  
 5. You cannot ***move*** your private cloud from one Resource Group to another after the private cloud is created.  
 6. You cannot ***move*** your private cloud from one tenant to another after the private cloud is created.  
-1. If you require **ExpressRoute FastPath** or **Global Virtual Network Peering** for your AVS Private Cloud**,** create a Support Case through the Azure Portal. 
+1. If you require **ExpressRoute FastPath** or **Global Virtual Network Peering** for your AVS Private Cloud**,** create a Support Case through the Azure portal. 
 
 1. **Service Endpoints** direct connectivity from Azure VMware Solution workloads isn't supported.
 

articles/confidential-computing/confidential-ai.md

@@ -1,7 +1,7 @@
 ---
 title: Confidential AI
 titleSuffix: Azure Confidential Computing
-description: Confidential AI services and solutions
+description: Confidential Foundry Tools and solutions
 services: virtual-machines
 author: kapilv
 ms.service: azure-confidential-computing

articles/confidential-computing/quick-create-portal.md

@@ -1,6 +1,6 @@
 ---
 title: Quickstart - Create Intel SGX VM in the Azure Portal
-description: Get started with your deployments by learning how to quickly create an Intel SGX VM in the Azure Portal
+description: Get started with your deployments by learning how to quickly create an Intel SGX VM in the Azure portal
 author: cynthn
 ms.service: azure-confidential-computing
 ms.topic: quickstart
@@ -25,7 +25,7 @@ If you don't have an Azure subscription, [create an account](https://azure.micro
 
 ## Sign in to Azure
 
-1. Sign in to the [Azure Portal](https://portal.azure.com/).
+1. Sign in to the [Azure portal](https://portal.azure.com/).
 
 1. At the top, select **Create a resource**.
 

articles/connectors/built-in.md

@@ -29,7 +29,7 @@ The following table lists the current and expanding galleries of built-in operat
 
 | Consumption | Standard |
 |-------------|----------|
-| Azure API Management <br>Azure App Service <br>Azure Functions <br>Azure Logic Apps <br>Batch Operations <br>Control <br>Data Operations <br>Date Time <br>Flat File <br>HTTP <br>Inline Code <br>Integration Account <br>Liquid Operations <br>Request <br>Schedule <br>Variables <br>XML Operations | AI Operations <br>AS2 (v2) <br>Azure AI Document Intelligence* <br>Azure AI Search* <br>Azure API Management <br>Azure Automation* <br>Azure Blob Storage* <br>Azure Container App (ACA) session* <br>Azure Cosmos DB* <br>Azure Event Grid Publisher* <br>Azure Event Hubs* <br>Azure File Storage* <br>Azure Functions <br>Azure Key Vault* <br>Azure OpenAI* <br>Azure Queue Storage* <br>Azure Service Bus* <br>Azure Table Storage* <br>Batch Operations <br>Confluent* <br>Control <br>Data Mapper Operations <br>Data Operations <br>Date Time <br>EDIFACT <br>File System* <br>Flat File <br>FTP* <br>HTTP <br>IBM 3270* <br>IBM CICS* <br>IBM DB2* <br>IBM Host File* <br>IBM IMS* <br>IBM MQ* <br>Inline Code <br>Integration Account <br>JDBC* <br>Liquid Operations <br>RabbitMQ <br>Request <br>RosettaNet <br>SAP* <br>Schedule <br>SFTP* <br>SMTP* <br>SQL Server* <br>SWIFT <br>Variables <br>Workflow Operations <br>X12 <br>XML Operations |
+| Azure API Management <br>Azure App Service <br>Azure Functions <br>Azure Logic Apps <br>Batch Operations <br>Control <br>Data Operations <br>Date Time <br>Flat File <br>HTTP <br>Inline Code <br>Integration Account <br>Liquid Operations <br>Request <br>Schedule <br>Variables <br>XML Operations | AI Operations <br>AS2 (v2) <br>Azure Document Intelligence in Foundry Tools* <br>Azure AI Search* <br>Azure API Management <br>Azure Automation* <br>Azure Blob Storage* <br>Azure Container App (ACA) session* <br>Azure Cosmos DB* <br>Azure Event Grid Publisher* <br>Azure Event Hubs* <br>Azure File Storage* <br>Azure Functions <br>Azure Key Vault* <br>Azure OpenAI* <br>Azure Queue Storage* <br>Azure Service Bus* <br>Azure Table Storage* <br>Batch Operations <br>Confluent* <br>Control <br>Data Mapper Operations <br>Data Operations <br>Date Time <br>EDIFACT <br>File System* <br>Flat File <br>FTP* <br>HTTP <br>IBM 3270* <br>IBM CICS* <br>IBM DB2* <br>IBM Host File* <br>IBM IMS* <br>IBM MQ* <br>Inline Code <br>Integration Account <br>JDBC* <br>Liquid Operations <br>RabbitMQ <br>Request <br>RosettaNet <br>SAP* <br>Schedule <br>SFTP* <br>SMTP* <br>SQL Server* <br>SWIFT <br>Variables <br>Workflow Operations <br>X12 <br>XML Operations |
 
 <a name="service-provider-interface-implementation"></a>
 
@@ -360,13 +360,13 @@ Azure Logic Apps provides the following built-in actions for working with data o
         [![Data Operations icon][data-operations-icon]][data-operations-doc]
         <br><br>[**Data Operations**][data-operations-doc]
         <br><br>Perform operations with data.
-        <br><br>**Chunk text**: Split up content into pieces to use in AI solutions or with AI service operations such as [Azure OpenAI and Azure AI Search operations](../logic-apps/connectors/azure-ai.md). For more information, see [Parse or chunk content](../logic-apps/parse-document-chunk-text.md).
+        <br><br>**Chunk text**: Split up content into pieces to use in AI solutions or with Foundry Tool operations such as [Azure OpenAI and Azure AI Search operations](../logic-apps/connectors/azure-ai.md). For more information, see [Parse or chunk content](../logic-apps/parse-document-chunk-text.md).
         <br><br>**Compose**: Create a single output from multiple inputs with various types.
         <br><br>**Create CSV table**: Create a comma-separated-value (CSV) table from an array with JSON objects.
         <br><br>**Create HTML table**: Create an HTML table from an array with JSON objects.
         <br><br>**Filter array**: Create an array from items in another array that meet your criteria.
         <br><br>**Join**: Create a string from all items in an array and separate those items with the specified delimiter.
-        <br><br>**Parse a document**: Create a tokenized string to use in AI solutions or with AI service operations such as [Azure OpenAI and Azure AI Search operations](../logic-apps/connectors/azure-ai.md). For more information, see [Parse or chunk content](../logic-apps/parse-document-chunk-text.md).
+        <br><br>**Parse a document**: Create a tokenized string to use in AI solutions or with Foundry Tool operations such as [Azure OpenAI and Azure AI Search operations](../logic-apps/connectors/azure-ai.md). For more information, see [Parse or chunk content](../logic-apps/parse-document-chunk-text.md).
         <br><br>**Parse JSON**: Create user-friendly tokens from properties and their values in JSON content so that you can use those properties in your workflow.
         <br><br>**Select**: Create an array with JSON objects by transforming items or values in another array and mapping those items to specified properties.
     :::column-end:::

articles/cyclecloud/release-notes/8-7-0.md

@@ -33,7 +33,7 @@ ms.author: bewatrou
 * The 'CycleCloud' settings section on the Settings page could not be changed. 
 * The `cyclecloud project upload` failed when CycleCloud was configured to use Entra Id user authentication 
 * Upgrading your CycleCloud installation from 8.6.0 to the latest version broke the ‘Edit Cluster’ page due to caching issues. 
-* Links to the Azure Portal were not valid 
+* Links to the Azure portal were not valid 
 * When Disk deletion failed on first attempt, node deletion also failed 
 * The *config/cycle_server.properties* file incorrectly declared it was auto-generated 
 * In some DNS settings, Jetpack would resolve storage accounts with private endpoints to the public IP 

articles/data-manager-for-agri/quickstart-install-data-manager-for-agriculture.md

@@ -26,7 +26,7 @@ In step 5 in the above documentation, search for `Microsoft.AgFoodPlatform` and
 ## 2: Search in marketplace
 
 > [!IMPORTANT]
-> Access the  Azure Portal using <a href="https://portal.azure.com/?microsoft_azure_marketplace_ItemHideKey=Microsoft_Azure_AgFoodPlatformHidden#create/hub" target="_blank">**this link**</a> . This link enables visibility of the Azure Data Manager for Agriculture installation card in the Marketplace for our preview customers.
+> Access the  Azure portal using <a href="https://portal.azure.com/?microsoft_azure_marketplace_ItemHideKey=Microsoft_Azure_AgFoodPlatformHidden#create/hub" target="_blank">**this link**</a> . This link enables visibility of the Azure Data Manager for Agriculture installation card in the Marketplace for our preview customers.
 
 Enter Data manager for agriculture in the marketplace search bar. Then select 'create' on the listing tile as shown below.