Merge pull request #314095 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-functions/functions-mcp-foundry-tools.md

@@ -288,7 +288,7 @@ When you use OAuth identity passthrough, the agent prompts the user to sign in a
     | **Token URL** | The endpoint your server app calls to exchange an authorization code or credential for an access token. | `https://login.microsoftonline.com/aaaabbbb-0000-cccc-1111-dddd2222eeee/oauth2/v2.0/token` |
     | **Auth URL** | The endpoint where users are redirected to authenticate and grant authorization to your server app. | `https://login.microsoftonline.com/aaaabbbb-0000-cccc-1111-dddd2222eeee/oauth2/v2.0/authorize` |
     | **Refresh URL** | The endpoint used to obtain a new access token when the current one expires. | `https://login.microsoftonline.com/aaaabbbb-0000-cccc-1111-dddd2222eeee/oauth2/v2.0/token` |
-    | **Scopes** | The specific permissions or resource access levels your server app requests from the authorization server | `api://00001111-aaaa-2222-bbbb-3333cccc4444` |
+    | **Scopes** | The specific permissions or resource access levels your server app requests from the authorization server | `api://00001111-aaaa-2222-bbbb-3333cccc4444/user_impersonation` |
 
 1. Select **Connect** to create a connection to your MCP server endpoint. 
 
@@ -358,4 +358,4 @@ These additional articles can help you build your agent and function app capabil
 
 - [Register your MCP server in the organizational tool catalog](./register-mcp-server-api-center.md)
 
----
+---

articles/azure-vmware/request-host-quota-azure-vmware-solution.md

@@ -16,8 +16,9 @@ If you have an existing Azure VMware Solution private cloud and want more hosts
 
 > [!IMPORTANT]
 > It can take up to five business days to allocate the hosts, depending on the number requested. Therefore, request the amount needed for provisioning to avoid delays associated with making host increase requests.
-> 
-> **NEW** A new process for requesting host quota, except for our Azure Government regions. Instructions for each scenario are provided.
+ 
+> [!NOTE]
+> The instructions for requesting host quota for our Azure Government regions is provided further below.
 
 ## Eligibility criteria
 
@@ -37,22 +38,23 @@ You need an Azure account in an Azure subscription that adheres to one of the fo
    - **Request Details**: Select **Enter details**, which opens up a side pane. Provide details based on your needs.
    - **Region**: Update with your Azure Preferred Region.
    - **SKU**: Update with your preferred SKU.
-   - **Number of nodes**: Update the total number of hosts for that SKU to reflect the new absolute value. For instance, if you currently have three hosts and require 3 more, the updated total should be 6. 
+   - **Number of nodes**: Update the total number of hosts for that SKU to reflect the **new absolute value**. For instance, if you currently have three hosts and require 3 more, the updated total should be 6. 
    - **File Upload**: Leave blank.
    - **Allow collection of advanced diagnostic information?**: Select **Yes** (recommended)
    - **Support plan**: Auto populated based on your plan.
 1. Select **Save and Continue** to submit the request.
 
 
 > [!NOTE]
-> - Azure VMware Solution requires a minimum of three hosts and recommends redundancy of N+1 hosts.
-> - Any unused quota or extra quota not deployed will expire after 30 days. A new request needs to be submitted for more quotas.
-> - Customers with a valid VCF key and extra quota not deployed, quota won't expire and remain after 30 days.
-> - **NEW** If requesting quota to use Portable [VMware Cloud Foundation (VCF)](/azure/azure-vmware/vmware-cloud-foundations-license-portability) pricing, add the following statement as is, by replacing (N) with the Number of VCF cores you purchased from Broadcom for license portability to Azure VMware Solution. **"I acknowledge that I have procured portable VCF license from Broadcom for (N) cores to use with Azure VMware Solution."**  
-> - **VCF Disclaimer** Quota allocation is processed upon request. If you didn't submit the VCF license through [email protected] and create the hosts, you're subject to Azure VMware Solution pay-as-you-go pricing.
-> - **NEW** If you have an Availability Zone requirement for integrating with other Azure services; for example, Azure NetApp Files, create a technical **[New support request](https://portal.azure.com/#create/Microsoft.Support)** once the quota is allocated and before provisioning.
->   - Summary: Need a specific availability zone.
->   - Problem type:  Azure VMware Service Quota request. 
+> - **Azure VMware Solution requires a minimum of three hosts** and recommends redundancy of N+1 hosts.
+> - Any unused or undeployed quota expires after 30 days. A new request is required to obtain additional quota.  This does not apply to customers with a valid VCF license key and/or Azure VMware Solution Reserved Instances, for whom quota equivalent to the reserved instance count does not expire after 30 days.
+> - **NEW** Azure VMware Solution no longer includes VMware licenses for new deployments and now requires Portable [VMware Cloud Foundation (VCF)](/azure/azure-vmware/vmware-cloud-foundations-license-portability) licenses. 
+> - **VCF Disclaimer** For quota extensions to an existing Azure VMware Solution private cloud, a Portable VMware Cloud Foundation (VCF) license must be configured before quota is allocated.  For net-new Azure VMware Solution deployments, quota is allocated automatically, and the Portable VCF license must be configured during deployment.
+
+> [!NOTE]
+>If you have an Availability Zone requirement for integrating with other Azure services; for example, Azure NetApp Files, create a technical **[New support request](https://portal.azure.com/#create/Microsoft.Support)** once the quota is allocated and **before** provisioning.
+>   - **Summary**: Need a specific availability zone.
+>   - **Problem type**:  Azure VMware Service Quota request. 
 
 ## Request host quota for CSP customers 
 
@@ -93,21 +95,23 @@ Access the Azure portal using the **Admin On Behalf Of (AOBO)** procedure from P
    - **Request Details:** Select **Enter details** to open a side pane. Provide details based on your needs.
    - **Region**: Update with your Azure Preferred Region.
    - **SKU**: Update with your preferred SKU.
-   - **Number of nodes**: Update the total number of hosts for that SKU to reflect the new absolute value. For instance, if you currently have three hosts and require 3 more, the updated total should be 6.
+   - **Number of nodes**: Update the total number of hosts for that SKU to reflect the **new absolute value**. For instance, if you currently have three hosts and require 3 more, the updated total should be 6.
    - **File Upload**: Leave blank.
    - **Allow collection of advanced diagnostic information?**: Select **Yes** (recommended).
    - **Support plan**: Auto populated based on your plan.
 
 1. Select **Save and Continue** to submit the request.
 
 > [!NOTE]
-> - Azure VMware Solution requires a minimum of three hosts and recommends redundancy of N+1 hosts.
-> - Any unused quota expires after 30 days. A new request needs to be submitted for more quotas.
-> - **NEW** If requesting quota to use Portable [VMware Cloud Foundation (VCF)](/azure/azure-vmware/vmware-cloud-foundations-license-portability) pricing, add the following statement as is, by replacing (N) with the Number of VCF cores you purchased from Broadcom for license portability to Azure VMware Solution. **"I acknowledge that I have procured portable VCF license from Broadcom for (N) cores to use with Azure VMware Solution."**  
-> - **VCF Disclaimer** Quota allocation is processed upon request. If you didn't submit the VCF license through [email protected] and create the hosts, you're subject to Azure VMware Solution pay-as-you-go pricing.
-> - **NEW** If you have an Availability Zone requirement for integrating with other Azure services; for example, Azure NetApp Files, create a technical **[New support request](https://portal.azure.com/#create/Microsoft.Support)** once the quota is allocated and before creating.
->   - Summary: Need a specific availability zone
->   - Problem type:  AVS Quota request
+> - **Azure VMware Solution requires a minimum of three hosts** and recommends redundancy of N+1 hosts.
+> - Any unused or undeployed quota expires after 30 days. A new request is required to obtain additional quota.  This does not apply to customers with a valid VCF license key and/or Azure VMware Solution Reserved Instances, for whom quota equivalent to the reserved instance count does not expire after 30 days.
+> - **NEW** Azure VMware Solution no longer includes VMware licenses for new deployments and now requires Portable [VMware Cloud Foundation (VCF)](/azure/azure-vmware/vmware-cloud-foundations-license-portability) licenses.
+> - **VCF Disclaimer** For quota extensions to an existing Azure VMware Solution private cloud, a Portable VMware Cloud Foundation (VCF) license must be configured before quota is allocated.  For net-new Azure VMware Solution deployments, quota is allocated automatically, and the Portable VCF license must be configured during deployment.
+
+> [!Note]
+>If you have an Availability Zone requirement for integrating with other Azure services; for example, Azure NetApp Files, create a technical **[New support request](https://portal.azure.com/#create/Microsoft.Support)** once the quota is allocated and before creating.
+>   - **Summary**: Need a specific availability zone
+>   - **Problem type**:  AVS Quota request
 
 
 

includes/azure-virtual-network-limits.md

@@ -77,7 +77,7 @@ The following limits apply only for networking resources managed through **Azure
 | Network Security Groups (NSGs) |200 |200 |
 | NSG rules per NSG |200 |1,000 |
 | User-defined route tables |200 |200 |
-| User-defined routes per route table |400 |400 |
+| User-defined routes per route table |600 |600 |
 | Public IP addresses (dynamic) |500 |500 |
 | Reserved public IP addresses |500 |500 |
 | Public IP per deployment |5 |Contact support |