Merge pull request #310789 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-host-json.md

@@ -325,13 +325,21 @@ A list of functions that the job host runs. An empty array means run all functio
 
 ## functionTimeout
 
-Indicates the timeout duration for all function executions. It follows the timespan string format. A value of `-1` indicates unbounded execution, but keeping a fixed upper bound is recommended.
+Indicates the timeout duration for all function executions. It follows the [timespan string format](/dotnet/fundamentals/runtime-libraries/system-timespan-parse). A value of `-1` indicates unbounded execution, but keeping a fixed upper bound is recommended.
 
 ```json
 {
     "functionTimeout": "00:05:00"
 }
 ```
+The format of the timespan string needs to follow the syntax `[d.]hh:mm:ss` and the valid values are:
+- d = days (optional)
+- hh = hours (0–23)
+- mm = minutes (0–59)
+- ss = seconds (0–59)
+
+> [!TIP]
+> When you need to set a 24-hour timeout, you must define it as one day (`"1.00:00:00"`) instead of 24 hours (`"24:00:00"`). You might also use `"23:59:59"`.
 
 For more information on the default and maximum values for specific plans, see [Function app timeout duration](./functions-scale.md#timeout).
 

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

@@ -46,7 +46,8 @@ You need an Azure account in an Azure subscription that adheres to one of the fo
 
 > [!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 quota.
+> - Any unused quota or extra quota not deployed will expire after 30 days. A new request needs to be submitted for more quota.
+> - Customers with a valid VCF key and extra quota not deployed, quota will not 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 provision the hosts, you're subject to Azure VMware Solution pay-as-you-go (PayGo) 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.

articles/partner-solutions/elastic/overview.md

@@ -32,7 +32,7 @@ The Elastic integration with Azure includes the following technical capabilities
 
 - **Integrated onboarding** – Deploy Elastic resources directly from Azure portal using the Microsoft.Elastic resource provider.
 - **Azure billing integration** – Track Elastic resource consumption and charges through the Azure billing system.
-- **Azure Active Directory authentication** – Access Elastic services using Azure AD credentials for single sign-on.
+- **Microsoft Entra ID authentication** – Access Elastic services using Entra ID credentials for single sign-on.
 - **Log forwarding** – Route Azure subscription activity and resource logs to Elastic for indexing and analysis. For more information, see [Monitor & Observe Azure resources with Azure Native Integrations](../metrics-logs.md).
 - **Centralized management** – Configure and monitor log shipping from Azure services to Elastic through a unified interface.
 - **Flexible deployment options** – Choose between serverless projects for usage-based scaling and cloud-hosted projects for dedicated, managed clusters.