Merge pull request #301837 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit 11920ad6348a · 2025-06-26T00:45:11.000+08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/application-gateway/ingress-controller-autoscale-pods.md b/articles/application-gateway/ingress-controller-autoscale-pods.md
@@ -123,7 +123,7 @@ spec:
 Test your setup by using a load test tool like ApacheBench:
 
 ```bash
-ab -n10000 http://<applicaiton-gateway-ip-address>/
+ab -n10000 http://<application-gateway-ip-address>/
 ```
 
 ## Related content
diff --git a/articles/azure-sql-edge/deploy-onnx.md b/articles/azure-sql-edge/deploy-onnx.md
@@ -185,7 +185,7 @@ onnxmltools.utils.save_model(onnx_model, onnx_model_path)
 ```
 
 > [!NOTE]  
-> You may need to set the `target_opset` parameter for the skl2onnx.convert_sklearn function if there's a mismatch between ONNX runtime version in SQL Edge and skl2onnx packge. For more information, see the [SQL Edge Release notes](release-notes.md) to get the ONNX runtime version corresponding for the release, and pick the `target_opset` for the ONNX runtime based on the [ONNX backward compatibility matrix](https://github.com/microsoft/onnxruntime/blob/master/docs/Versioning.md#version-matrix).
+> You may need to set the `target_opset` parameter for the skl2onnx.convert_sklearn function if there's a mismatch between ONNX runtime version in SQL Edge and skl2onnx package. For more information, see the [SQL Edge Release notes](release-notes.md) to get the ONNX runtime version corresponding for the release, and pick the `target_opset` for the ONNX runtime based on the [ONNX backward compatibility matrix](https://github.com/microsoft/onnxruntime/blob/master/docs/Versioning.md#version-matrix).
 
 ## Test the ONNX model
 
diff --git a/articles/communication-services/support.md b/articles/communication-services/support.md
@@ -21,7 +21,7 @@ You can explore and review many [support options and plans](https://azure.micros
 
 ## Post a question to Microsoft Q&A
 
-For quick and reliable answers to product or technical questions you might have about Azure Communication Services, engage with us on [Microsoft Q&A](/answers/products/azure). You can get answers from:
+For quick and reliable answers to product or technical questions you might have about Azure Communication Services, engage with us on [Microsoft Q&A](/answers/tags/128/azure-communication-services). You can get answers from:
 
 - Microsoft engineers
 - Azure Most Valuable Professionals (MVPs)
diff --git a/articles/private-link/network-security-perimeter-concepts.md b/articles/private-link/network-security-perimeter-concepts.md
@@ -98,6 +98,7 @@ A network security perimeter-aware private link resource is a PaaS resource that
 | [Key Vault](/azure/key-vault/general/network-security#network-security-perimeter-preview)                 | Microsoft.KeyVault/vaults | - |
 | [SQL DB](/azure/azure-sql/database/network-security-perimeter)                    | Microsoft.Sql/servers | - |
 | [Storage](/azure/storage/common/storage-network-security#network-secuirty-perimeter-preview)               | Microsoft.Storage/storageAccounts | - |
+| [Azure OpenAI service](/azure/ai-services/openai/how-to/network-security-perimeter) | Microsoft.CognitiveServices | - |
 
 > [!NOTE]
 > Refer to the respective private link resource documentation for information on currently unsupported scenarios.
diff --git a/articles/spring-apps/basic-standard/concept-manage-monitor-app-spring-boot-actuator.md b/articles/spring-apps/basic-standard/concept-manage-monitor-app-spring-boot-actuator.md
@@ -69,7 +69,7 @@ In the Enterprise plan, there are two ways to secure the access:
 
 - You can disable the public endpoint of apps and configure a routing rule in VMware Spring Cloud Gateway to disable actuator access from the public. For more information, see [Configure VMware Spring Cloud Gateway](../enterprise/how-to-configure-enterprise-spring-cloud-gateway.md).
 
-- You can configure the actuator to listen on a different HTTP port from the main application. In a standalone application, the actuator HTTP port defaults to the same as the main HTTP port. For the application to listen on a different port, set the `management.server.port` property. The Application Live View is unable to automatically detect this port change, so you also need to configure the property on an Azure Spring Apps deployment. Then, the actuator isn't publically accessible, but the Application Live View can read from the actuator endpoint via another port. For more information, see [Use Application Live View with the Azure Spring Apps Enterprise plan](../enterprise/how-to-use-application-live-view.md).
+- You can configure the actuator to listen on a different HTTP port from the main application. In a standalone application, the actuator HTTP port defaults to the same as the main HTTP port. For the application to listen on a different port, set the `management.server.port` property. The Application Live View is unable to automatically detect this port change, so you also need to configure the property on an Azure Spring Apps deployment. Then, the actuator isn't publicly accessible, but the Application Live View can read from the actuator endpoint via another port. For more information, see [Use Application Live View with the Azure Spring Apps Enterprise plan](../enterprise/how-to-use-application-live-view.md).
 
 ## Next steps
 
diff --git a/articles/spring-apps/enterprise/how-to-use-accelerator.md b/articles/spring-apps/enterprise/how-to-use-accelerator.md
@@ -518,7 +518,7 @@ Use the following steps to view the list of App Accelerators in an Azure Spring
 
 ### Troubleshoot App Accelerator issues
 
-If you try to open App Accelerator for a service instance that hasn't enabled App Accelerator or exposed a public endpoint, you see the following error message: `Application Accelerator of Spring Apps <instance-name> is not enabled or publically accessible`.
+If you try to open App Accelerator for a service instance that hasn't enabled App Accelerator or exposed a public endpoint, you see the following error message: `Application Accelerator of Spring Apps <instance-name> is not enabled or publicly accessible`.
 
 To enable App Accelerator and expose public endpoints, use the following steps. For more information, see the [Manage App Accelerator in an existing Enterprise plan instance](#manage-app-accelerator-in-an-existing-enterprise-plan-instance) section.
 
diff --git a/articles/trusted-signing/how-to-signing-integrations.md b/articles/trusted-signing/how-to-signing-integrations.md
@@ -165,14 +165,25 @@ Each authentication method can be disabled individually to avoid unnecessary att
 
 For example, when authenticating with [EnvironmentCredential](/dotnet/api/azure.identity.environmentcredential) specifically, disable the other credentials with the following inputs:
 
-ExcludeEnvironmentCredential: false
-ExcludeManagedIdentityCredential: true
-ExcludeSharedTokenCacheCredential: true
-ExcludeVisualStudioCredential: true
-ExcludeVisualStudioCodeCredential: true
-ExcludeAzureCliCredential: true
-ExcludeAzurePowershellCredential: true
-ExcludeInteractiveBrowserCredential: true
+   ```json
+   {
+     "Endpoint": "<Trusted Signing account endpoint>",
+     "CodeSigningAccountName": "<Trusted Signing account name>",
+     "CertificateProfileName": "<Certificate profile name>",
+     "CorrelationId": "<Optional CorrelationId value>",
+     "ExcludeCredentials": [
+        "ManagedIdentityCredential",
+        "WorkloadIdentityCredential",
+        "SharedTokenCacheCredential",
+        "VisualStudioCredential",
+        "VisualStudioCodeCredential",
+        "AzureCliCredential",
+        "AzurePowerShellCredential",
+        "AzureDeveloperCliCredential",
+        "InteractiveBrowserCredential"
+    ]
+   }
+   ```
 
 Similarly, if using for example an [AzureCliCredential](/dotnet/api/azure.identity.azureclicredential) , then we want to skip over attempting to authenticate with the several methods that come before it in order.
 
