Update Azure AI Foundry and Azure AI services references

Author: JKirsch1

articles/azure-web-pubsub/quickstart-serverless.md

@@ -793,7 +793,7 @@ Use the following commands to create these items.
 
    [!INCLUDE [Connection string security comment](includes/web-pubsub-connection-string-security-comment.md)]
 
-   First, find your Web PubSub resource from **Azure Portal** and copy out the connection string under **Keys**. Then, navigate to Function App settings in **Azure Portal** -> **Settings** -> **Environment variables**. And add a new item under **App settings**, with name equals `WebPubSubConnectionString` and value is your Web PubSub resource connection string.
+   First, find your Web PubSub resource from **Azure portal** and copy out the connection string under **Keys**. Then, navigate to Function App settings in **Azure portal** -> **Settings** -> **Environment variables**. And add a new item under **App settings**, with name equals `WebPubSubConnectionString` and value is your Web PubSub resource connection string.
 
 ## Configure the Web PubSub service `Event Handler`
 

articles/azure-web-pubsub/reference-server-sdk-java.md

@@ -75,7 +75,7 @@ WebPubSubServiceClient webPubSubServiceClient = new WebPubSubServiceClientBuilde
 ```java
 WebPubSubServiceClient webPubSubServiceClient = new WebPubSubServiceClientBuilder()
     .credential(new AzureKeyCredential("{access-key}"))
-    .endpoint("<Insert endpoint from Azure Portal>")
+    .endpoint("<Insert endpoint from Azure portal>")
     .hub("chat")
     .buildClient();
 ```

articles/azure-web-pubsub/tutorial-serverless-notification.md

@@ -735,7 +735,7 @@ Use the following commands to create these items.
     ```
 
     > [!NOTE]
-    > Here we are deploying local settings `local.settings.json` together with command parameter `--publish-local-settings`. If you're using Microsoft Azure Storage Emulator, you can type `no` to skip overwriting this value on Azure following the prompt message: `App setting AzureWebJobsStorage is different between azure and local.settings.json, Would you like to overwrite value in azure? [yes/no/show]`. Besides, you can update Function App settings in **Azure Portal** -> **Settings** -> **Configuration**.
+    > Here we are deploying local settings `local.settings.json` together with command parameter `--publish-local-settings`. If you're using Microsoft Azure Storage Emulator, you can type `no` to skip overwriting this value on Azure following the prompt message: `App setting AzureWebJobsStorage is different between azure and local.settings.json, Would you like to overwrite value in azure? [yes/no/show]`. Besides, you can update Function App settings in **Azure portal** -> **Settings** -> **Configuration**.
 
 1. Now you can check your site from Azure Function App by navigating to URL: `https://<FUNCIONAPP_NAME>.azurewebsites.net/api/index`.
 

articles/cost-management-billing/manage/manage-billing-across-tenants.md

@@ -111,13 +111,13 @@ Choosing to assign roles to users from associated billing tenants might be the r
 |Security     |  The users that you invite to share your billing account follow their tenant's security policies.      |  The users that you invite to share your billing account follow your tenant's security policies.       |
 |Access    | The users get access to your billing account in their own tenant and can manage billing and make purchases without switching tenants.        |  External guest identities are created for users in your tenant and these identities get access to your billing account. Users would have to switch tenant to manage billing and make purchases.     |
 
-## Understanding Guest Users in Azure Portal
+## Understanding Guest Users in Azure portal
 
 A guest user (also known as guested user or B2B user) is an external user who has been invited to access resources within an Azure Active Directory (Azure AD) tenant. Typically, this user has a primary identity in another Azure AD tenant or identity provider and receives access via Azure AD B2B (business-to-business) collaboration features. Once invited, the guest user appears in the inviting organization’s directory and can be assigned roles and permissions just like any other user.
 
-### Accessing the Azure Portal
+### Accessing the Azure portal
 
-The guest user must sign in to the [Azure Portal](https://portal.azure.com/) using their own organization’s credentials. Upon successful authentication, they should select the host directory (the client organization) from the top-right user menu in the Azure Portal if they are members of multiple tenants.
+The guest user must sign in to the [Azure portal](https://portal.azure.com/) using their own organization’s credentials. Upon successful authentication, they should select the host directory (the client organization) from the top-right user menu in the Azure portal if they are members of multiple tenants.
 
 ### Navigation and User Interface
 
@@ -129,7 +129,7 @@ Once inside the client’s directory, the guest user will see the resources and
 ## Troubleshooting Common Issues for Guest Users
 
 - Access Denied Errors: Ensure correct roles are assigned and the guest has accepted the invitation. 
-- Directory Not Found: Instruct the user to switch directories in the Azure Portal. 
+- Directory Not Found: Instruct the user to switch directories in the Azure portal. 
 - Resource Visibility: Confirm that the user’s roles map to the correct billing profiles or invoice sections. 
 
 ## Move Microsoft 365 subscriptions to a billing tenant

articles/cost-management-billing/microsoft-customer-agreement/manage-tenants.md

@@ -67,11 +67,11 @@ There are three ways users with billing owner access can assign roles to users t
 - Assign billing roles to external users (outside of your primary tenant) if they are part of an associated tenant 
 - If tenants are not associated, [create guest users in primary tenant and assign roles](#add-guest-users-to-your-microsoft-customer-agreement-tenant). 
 
-## Understanding Guest Users in Azure Portal
+## Understanding Guest Users in Azure portal
 
 A guest user (also known as guested user or B2B user) is an external user who has been invited to access resources within an Azure Active Directory (Azure AD) tenant. Typically, this user has a primary identity in another Azure AD tenant or identity provider and receives access via Azure AD B2B (business-to-business) collaboration features. Once invited, the guest user appears in the inviting organization’s directory and can be assigned roles and permissions just like any other user.
 
-### Accessing the Azure Portal
+### Accessing the Azure portal
 
 The guest user must sign in to the [Azure portal](https://portal.azure.com/) using their own organization’s credentials. Upon successful authentication, they should select the host directory (the client organization) from the top-right user menu in the Azure portal if they are members of multiple tenants.
 
@@ -117,7 +117,7 @@ Authorization to invite guest users is controlled by your Microsoft Entra settin
 ## Troubleshooting Common Issues for Guest Users
 
 - Access Denied Errors: Ensure correct roles are assigned and the guest has accepted the invitation. 
-- Directory Not Found: Instruct the user to switch directories in the Azure Portal. 
+- Directory Not Found: Instruct the user to switch directories in the Azure portal. 
 - Resource Visibility: Confirm that the user’s roles map to the correct billing profiles or invoice sections. 
 
 ## Manage multiple Microsoft cloud services under a Microsoft Entra tenant

articles/cost-management-billing/reservations/agent-pre-purchase.md

@@ -12,9 +12,9 @@ ms.author: primittal
 
 # Optimize Microsoft Foundry and Copilot Credit costs with Microsoft Agent pre-purchase plan 
 
-Save on your Copilot Credit and Microsoft Foundry costs when you buy a pre-purchase plan. Pre-purchase plans are commit units (CUs) bought at discounted tiers in your purchasing currency for a specific product. The more you buy, the greater the discount. Purchased CUs pay down qualifying costs in US dollars (USD). So, for example if Microsoft Copilot Studio or Microsoft Foundry generates a retail cost of $100 based on Copilot Credit and Microsoft Foundry usage, then 100 Agent CUs (ACUs) are consumed.
+Save on your Copilot Credit and Microsoft Foundry costs when you buy a pre-purchase plan. Pre-purchase plans are commit units (CUs) bought at discounted tiers in your purchasing currency for a specific product. The more you buy, the greater the discount. Purchased CUs pay down qualifying costs in US dollars (USD). So, for example if Microsoft Copilot Studio or Foundry generates a retail cost of $100 based on Copilot Credit and Foundry usage, then 100 Agent CUs (ACUs) are consumed.
 
-Your Microsoft Agent pre-purchase plan automatically uses your ACUs to pay for eligible Copilot and AI Foundry usage during its one-year term or until Agent CUs run out. Your pre-purchase plan Agent CUs start paying for your Copilot Credit and Microsoft Foundry usage without having to redeploy or reassign the plan. By default, plans are configured to renew at the end of the one-year term.
+Your Microsoft Agent pre-purchase plan automatically uses your ACUs to pay for eligible Copilot and Foundry usage during its one-year term or until Agent CUs run out. Your pre-purchase plan Agent CUs start paying for your Copilot Credit and Foundry usage without having to redeploy or reassign the plan. By default, plans are configured to renew at the end of the one-year term.
 
 ## Prerequisites
 
@@ -27,13 +27,13 @@ To buy a pre-purchase plan, you must have one of the following Azure subscriptio
 
 ## Determine the right size to buy
 
-To get started, estimate your expected Copilot Credit and Microsoft Foundry usage for the term. This helps you determine the appropriate size for your pre-purchase plan. Each pre-purchase plan has a one-year term.
+To get started, estimate your expected Copilot Credit and Foundry usage for the term. This helps you determine the appropriate size for your pre-purchase plan. Each pre-purchase plan has a one-year term.
 
 **Example calculation:**
 
 Consider a hypothetical scenario where your organization plans to use:
 - **Copilot Credit**: 1,500,000 credits for custom agents in Microsoft Copilot Studio
-- **Microsoft Foundry PTUs**: 5,000 PTU hours for AI model deployments in Microsoft Foundry
+- **Foundry PTUs**: 5,000 PTU hours for AI model deployments in Foundry
 
 **Assumed pay-as-you-go rates (for illustration purposes):**
 - Copilot Credit at hypothetical $0.01 per credit = $15,000
@@ -75,21 +75,21 @@ You can't split or merge a **Microsoft Agent Pre-Purchase Plan**. For more infor
 
 When you have multiple AI-related purchasing options, understanding how benefits are applied helps you maximize your cost savings. You might have several types of purchases for your AI workloads:
 
-- [Microsoft Foundry Provisioned Throughput reservation](microsoft-foundry.md) - Covers Microsoft Foundry PTU (Provisioned Throughput Units) usage
+- [Microsoft Foundry Provisioned Throughput reservation](microsoft-foundry.md) - Covers Foundry PTU (Provisioned Throughput Units) usage
 - [Copilot Credit pre-purchase plan](copilot-credit-p3.md) - Covers Copilot Credit-specific usage  
-- Microsoft Agent pre-purchase plan - Covers broader AI workloads including both Copilot Credit and Microsoft Foundry
+- Microsoft Agent pre-purchase plan - Covers broader AI workloads including both Copilot Credit and Foundry
 
 ### Understanding benefit overlap
 
 **What is overlap?** Overlap occurs when multiple benefits can cover the same usage. For example:
 - Copilot credits are eligible for both Copilot Credit pre-purchase plan and Microsoft Agent pre-purchase plan
-- Microsoft Foundry PTU workloads are eligible for both Microsoft Foundry PTU reservations and Microsoft Agent pre-purchase plan
+- Foundry PTU workloads are eligible for both Foundry PTU reservations and Microsoft Agent pre-purchase plan
 
 ### Benefit application order (precedence)
 
 When overlap occurs, Microsoft applies benefits in this specific order to maximize your savings:
 
-1. **Microsoft Foundry PTU Reservations**
+1. **Foundry PTU Reservations**
    - Always applied first to PTU usage
    - PTU-specific and most cost-effective for provisioned throughput
 
@@ -99,7 +99,7 @@ When overlap occurs, Microsoft applies benefits in this specific order to maximi
 
 3. **Microsoft Agent Pre-Purchase Plan**
    - Applied last to remaining AI usage across both platforms
-   - Broader coverage for heterogeneous AI workloads for Copilot Credit and Microsoft Foundry usage
+   - Broader coverage for heterogeneous AI workloads for Copilot Credit and Foundry usage
 
 > [!IMPORTANT]
 > Microsoft Agent pre-purchase plan does not cover the purchase cost of other reservations or pre-purchase plans - only actual usage costs.
@@ -108,10 +108,10 @@ When overlap occurs, Microsoft applies benefits in this specific order to maximi
 
 These scenarios show how benefits work together in different purchasing combinations:
 
-#### Scenario 1: Microsoft Foundry reservation only
+#### Scenario 1: Foundry reservation only
 
 **What you have:**
-- Microsoft Foundry PTU reservation for 10 PTUs
+- Foundry PTU reservation for 10 PTUs
 
 **How benefits apply:**
 1. Reservation covers first 10 PTUs at discounted rate
@@ -127,12 +127,12 @@ These scenarios show how benefits work together in different purchasing combinat
 **How benefits apply:**
 1. Copilot workloads consume Copilot Credit pre-purchase plan first (up to 5,000 CCCUs)
 2. Additional Copilot usage draws from Microsoft Agent pre-purchase plan
-3. Microsoft Foundry usage draws from Microsoft Agent pre-purchase plan
+3. Foundry usage draws from Microsoft Agent pre-purchase plan
 
-#### Scenario 3: Microsoft Foundry reservation + Microsoft Agent pre-purchase plan
+#### Scenario 3: Foundry reservation + Microsoft Agent pre-purchase plan
 
 **What you have:**
-- Microsoft Foundry PTU reservation: 15 PTUs
+- Foundry PTU reservation: 15 PTUs
 - Microsoft Agent pre-purchase plan: 25,000 CUs
 
 **How benefits apply:**
@@ -143,7 +143,7 @@ These scenarios show how benefits work together in different purchasing combinat
 #### Scenario 4: Complete coverage (all three benefits)
 
 **What you have:**
-- Microsoft Foundry PTU reservation: 10 PTUs
+- Foundry PTU reservation: 10 PTUs
 - Copilot Credit pre-purchase plan: 3,000 CUs
 - Microsoft Agent pre-purchase plan: 15,000 CUs
 

articles/cost-management-billing/understand/review-partner-agreement-bill.md

@@ -17,7 +17,7 @@ In the billing account for a Microsoft Partner Agreement, an invoice is generate
 
 For more information, see [how to download invoices from the Azure portal](download-azure-invoice.md).
 
-This tutorial applies only to Azure partners with an Microsoft Partner Agreement.
+This tutorial applies only to Azure partners with a Microsoft Partner Agreement.
 
 In this tutorial, you learn how to:
 

articles/digital-twins/concepts-data-ingress-egress.md

@@ -52,7 +52,7 @@ Once the data has been historized, you can query this data in Azure Data Explore
 
 You can also use data history in combination with [Azure Synapse Analytics](../synapse-analytics/overview-what-is.md) to aggregate data from disparate sources. This can be useful in many scenarios. Here are two examples:
 * Combine information technology (IT) data from ERP or CRM systems (like Dynamics 365, SAP, or Salesforce) with operational technology (OT) data from IoT devices and production management systems. For an example that illustrates how a company might combine this data, see the following blog post: [Integrating IT and OT Data with Azure Digital Twins, Azure Data Explorer, and Azure Synapse](https://techcommunity.microsoft.com/t5/internet-of-things-blog/integrating-it-and-ot-data-with-azure-digital-twins-azure-data/ba-p/3401981).
-* Integrate with the Azure AI and Azure AI services [Multivariate Anomaly Detector](/azure/ai-services/anomaly-detector/overview), to quickly connect your Azure Digital Twins data with a downstream AI/machine learning solution that specializes in anomaly detection. The [Azure Digital Twins Multivariate Anomaly Detection Toolkit](/samples/azure-samples/digital-twins-mvad-integration/adt-mvad-integration/) is a sample project that provides a workflow for training multiple Multivariate Anomaly Detector models for several scenario analyses, based on historical digital twin data. It then leverages the trained models to detect abnormal operations and anomalies in modeled Azure Digital Twins environments, in near real-time. 
+* Integrate with the Azure AI and Foundry Tools [Multivariate Anomaly Detector](/azure/ai-services/anomaly-detector/overview), to quickly connect your Azure Digital Twins data with a downstream AI/machine learning solution that specializes in anomaly detection. The [Azure Digital Twins Multivariate Anomaly Detection Toolkit](/samples/azure-samples/digital-twins-mvad-integration/adt-mvad-integration/) is a sample project that provides a workflow for training multiple Multivariate Anomaly Detector models for several scenario analyses, based on historical digital twin data. It then leverages the trained models to detect abnormal operations and anomalies in modeled Azure Digital Twins environments, in near real-time. 
 
 ### Security and delivery details
 

articles/digital-twins/concepts-security.md

@@ -84,7 +84,7 @@ If a user attempts to perform an action not allowed by their role, they may rece
 
 ## Managed identity for accessing other resources
 
-Setting up an [Microsoft Entra ID](../active-directory/fundamentals/active-directory-whatis.md) *managed identity* for an Azure Digital Twins instance can allow the instance to easily access other Microsoft Entra protected resources, such as [Azure Key Vault](/azure/key-vault/general/overview). The identity is managed by the Azure platform, and doesn't require you to provision or rotate any secrets. For more about managed identities in Microsoft Entra ID, see [Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md). 
+Setting up a [Microsoft Entra ID](../active-directory/fundamentals/active-directory-whatis.md) *managed identity* for an Azure Digital Twins instance can allow the instance to easily access other Microsoft Entra protected resources, such as [Azure Key Vault](/azure/key-vault/general/overview). The identity is managed by the Azure platform, and doesn't require you to provision or rotate any secrets. For more about managed identities in Microsoft Entra ID, see [Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md). 
 
 Azure Digital Twins supports both types of managed identities, *system-assigned* and *user-assigned*. 
 

articles/digital-twins/how-to-create-app-registration.md

@@ -12,7 +12,7 @@ ms.custom: sfi-image-nochange
 
 # Create an app registration to use with Azure Digital Twins
 
-This article describes how to create an [Microsoft Entra ID](../active-directory/fundamentals/active-directory-whatis.md) *app registration* that can access Azure Digital Twins. This article includes steps for the [Azure portal](https://portal.azure.com) and the [Azure CLI](/cli/azure/what-is-azure-cli).
+This article describes how to create a [Microsoft Entra ID](../active-directory/fundamentals/active-directory-whatis.md) *app registration* that can access Azure Digital Twins. This article includes steps for the [Azure portal](https://portal.azure.com) and the [Azure CLI](/cli/azure/what-is-azure-cli).
 
 When working with Azure Digital Twins, it's common to interact with your instance through client applications. Those applications need to authenticate with Azure Digital Twins, and some of the [authentication mechanisms](how-to-authenticate-client.md) that apps can use involve an app registration.