Merge pull request #274992 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: TimShererWithAquent

articles/api-center/enable-api-center-portal.md

@@ -85,7 +85,8 @@ Follow these steps to build and test the API Center portal locally.
     ```bash
     git checkout main
     ```  
-1. To configure the service, edit the `public/config.json` file to point to your service. Update the values in the file as follows:
+1. To configure the service, copy or rename the `public/config.example` file to `public/config.json`.
+1. Then edit the `public/config.json` file to point to your service. Update the values in the file as follows:
     * Replace `<service name>` and `<region>` with the name of your API center and the region where it's deployed
     * Replace `<client ID>` and `<tenant ID>` with the **Application (client) ID** and **Directory (tenant) ID** of the app registration you created in the previous section.
     * Update the value of `title` to a name that you want to appear on the portal.

articles/azure-functions/analyze-telemetry-data.md

@@ -52,7 +52,7 @@ To open Application Insights from a function app in the [Azure portal](https://p
 
 ![Open Application Insights from the function app Overview page](media/functions-monitoring/ai-link.png)
 
-For information about how to use Application Insights, see the [Application Insights documentation](/azure/application-insights/). This section shows some examples of how to view data in Application Insights. If you're already familiar with Application Insights, you can go directly to [the sections about how to configure and customize the telemetry data](configure-monitoring.md#configure-log-levels).
+For information about how to use Application Insights, see the [Application Insights documentation](../azure-monitor/app/app-insights-overview.md). This section shows some examples of how to view data in Application Insights. If you're already familiar with Application Insights, you can go directly to [the sections about how to configure and customize the telemetry data](configure-monitoring.md#configure-log-levels).
 
 ![Application Insights Overview tab](media/functions-monitoring/metrics-explorer.png)
 

articles/azure-functions/configure-monitoring.md

@@ -477,6 +477,6 @@ For more information about monitoring, see:
 
 + [Monitor Azure Functions](functions-monitoring.md)
 + [Analyze Azure Functions telemetry data in Application Insights](analyze-telemetry-data.md)
-+ [Application Insights](/azure/application-insights/)
++ [Application Insights](../azure-monitor/app/app-insights-overview.md)
 
 [host.json]: functions-host-json.md

articles/azure-functions/functions-monitoring.md

@@ -165,5 +165,5 @@ To report an issue with Application Insights integration in Functions, or to mak
 
 For more information, see the following resources:
 
-* [Application Insights](/azure/application-insights/)
+* [Application Insights](../azure-monitor/app/app-insights-overview.md)
 * [ASP.NET Core logging](/aspnet/core/fundamentals/logging/)

articles/azure-monitor/logs/logs-dedicated-clusters.md

@@ -239,12 +239,12 @@ You need 'write' permissions to both the workspace and the cluster resource for
 - In the cluster resource: *Microsoft.OperationalInsights/clusters/write*
 
 Once Log Analytics workspace linked to a dedicated cluster, new data sent to workspace is ingested to your dedicated cluster, while previously ingested data remains in Log Analytics cluster. Linking a workspace has no effect on workspace operation, including ingestion and query experiences. Log Analytics query engine stitches data from old and new clusters automatically, and the results of queries are complete. 
- 
-When dedicated cluster is configured with customer-managed key (CMK), new ingested data is encrypted with your key, while older data remains encrypted with Microsoft-managed key (MMK). The key configuration is abstracted by Log Analytics and the query across old and new data encryptions is performed seamlessly.
 
-A cluster can be linked to up to 1,000 workspaces located in the same region with cluster. A workspace can't be linked to a cluster more than twice a month, to prevent data fragmentation.
+Clusters are regional and can be linked to up to 1,000 workspaces located in the same region as the cluster. A workspace can't be linked to a cluster more than twice a month, to prevent data fragmentation.
+
+Linked workspaces can be in different subscriptions than the subscription the cluster is located in. The workspace and cluster can be in different tenants if Azure Lighthouse is used to map both of them to a single tenant.
 
-The workspace and the cluster can be in different subscriptions. It's possible for the workspace and cluster to be in different tenants if Azure Lighthouse is used to map both of them to a single tenant.
+When a dedicated cluster is configured with a customer-managed key (CMK), the newly ingested data is encrypted with your key, while older data remains encrypted with a Microsoft-managed key (MMK). The key configuration is abstracted by Log Analytics and the query across old and new data encryptions is performed seamlessly.
 
 Use the following steps to link a workspace to a cluster. You can use automation for linking multiple workspaces:
 

articles/azure-vmware/enable-sql-azure-hybrid-benefit.md

@@ -26,7 +26,7 @@ To enable through the Azure CLI, reference [az vmware placement-policy vm-host](
 
 For the Azure portal step-by-step see: 
 
-1. From your Azure VMware Solution private cloud, select Azure Hybrid Benefit, then Create VM-Host placement policy.
+1. From your Azure VMware Solution private cloud, select Azure Hybrid Benefit, then Create VM-Host affinity placement policy.
     :::image type="content" source="media/sql-azure-hybrid-benefit/azure-hybrid-benefit.png" alt-text="Diagram that shows how to create a host new virtual machine placement policy.":::
 
 1. Fill in the required fields for creating the placement policy.

articles/trusted-signing/how-to-signing-integrations.md

@@ -53,20 +53,20 @@ To download and install SignTool:
 
 1. Install SignTool from the Windows SDK (minimum version: 10.0.2261.755).
 
-Another option is to use the latest *nuget.exe* file to download and extract the latest SDK Build Tools NuGet package by using PowerShell:
+Another option is to use the latest *nuget.exe* file to download and extract the latest Windows SDK Build Tools NuGet package by using PowerShell:
 
 1. Download *nuget.exe* by running the following download command:  
 
    ```powershell
    Invoke-WebRequest -Uri https://dist.nuget.org/win-x86-commandline/latest/nuget.exe -OutFile .\nuget.exe  
    ```
 
-1. Install *nuget.exe* by running the following installation command:
+1. Download and extract Windows SDK Build Tools NuGet package by running the following installation command:
 
    ```powershell
-   .\nuget.exe install Microsoft.Windows.SDK.BuildTools -Version 10.0.2261.755 
+   .\nuget.exe install Microsoft.Windows.SDK.BuildTools -Version 10.0.22621.3233 -x
    ```
-
+   
 ### Download and install .NET 8.0 Runtime
 
 The components that SignTool uses to interface with Trusted Signing require the installation of [.NET 8.0 Runtime](https://dotnet.microsoft.com/download/dotnet/8.0) You need only the core .NET 8.0 Runtime. Make sure that you install the correct platform runtime depending on the version of SignTool you intend to run. Or, you can simply install both
@@ -84,12 +84,18 @@ To download and install the Trusted Signing dlib package (a .zip file):
 
 1. Extract the Trusted Signing dlib zipped content and install it on your signing node in your choice of directory. The node must be the node where you'll use SignTool to sign files.
 
+Another option is to download the [Trusted Signing dlib package](https://www.nuget.org/packages/Microsoft.Trusted.Signing.Client) via NuGet similar like the Windows SDK Build Tools NuGet package:
+
+```powershell
+.\nuget.exe install Microsoft.Trusted.Signing.Client -Version 1.0.53 -x
+```
+
 ### Create a JSON file
 
 To sign by using Trusted Signing, you need to provide the details of your Trusted Signing account and certificate profile that were created as part of the prerequisites. You provide this information on a JSON file by completing these steps:
 
 1. Create a new JSON file (for example, *metadata.json*).
-1. Add the specific values for your Trusted Signing account and certificate profile to the JSON file. The Trusted Signing account is interchangeably called *code signing account*. For more information, see the *metadata.sample.json* file that’s included in the Trusted Signing dlib package or use the following example:
+1. Add the specific values for your Trusted Signing account and certificate profile to the JSON file. For more information, see the *metadata.sample.json* file that’s included in the Trusted Signing dlib package or use the following example:
 
    ```json
    {

articles/virtual-machines/workloads/oracle/oracle-third-party-storage.md

@@ -42,7 +42,7 @@ The following table provides other inputs to help you to determine the appropria
 | Other            | Flexible model at TiB granularity |
 | Provisioning Model          | Incremental snapshot for fast restore; Snapshot export for hardening. |
 | [BCDR](/azure/cloud-adoption-framework/scenarios/oracle-iaas/oracle-disaster-recovery-oracle-landing-zone)                        | See redundancy capabilities of Lightbits in redundancy requirements. |
-| Redundancy & Scale Targets  | Encryption at rest is supported. |
+| Redundancy & Scale Targets  | Built-in multi availability zone support via synchronous replication, and automatic cluster expansion based on storage usage. |
 | Encryption                  | Encryption at rest is supported. |
 ## Tessel: Performance best practices for Oracle on Azure VMs