Merge branch 'main' into docs-editor/cannot-connect-rds-no-license-1736963868

Author: Simonx Xu

.openpublishing.redirection.developer.json

@@ -5842,6 +5842,10 @@
     {
       "source_path": "support/developer/webapps/iis/www-administration-management/http-bad-request-response-kerberos.md",
       "redirect_url": "/troubleshoot/developer/webapps/iis/www-authentication-authorization/http-bad-request-response-kerberos"
+    },
+    {
+      "source_path": "support/developer/webapps/iis/health-diagnostic-performance/troubleshoot-native-memory-leak-iis-7x-application-pool.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/troubleshoot-native-memory-leak-iis-7x-application-pool"
     }
   ]
 }

support/azure/automation/updates/find-azurermresource-fails.md

@@ -25,6 +25,6 @@ Starting in Microsoft AzureRM 6.0.0, the `Find-AzureRmResource` cmdlet functiona
 
 ## Resolution
 
-To fix this issue, update your runbooks to use `Get-AzureRmResource` instead of `Find-AzureRmResource`. For more information, see the [usage of Get-AzureRmResource](/powershell/module/azurerm.resources/get-azurermresource?view=azurermps-6.1.0&preserve-view=true).
+To fix this issue, update your runbooks to use `Get-AzureRmResource` instead of `Find-AzureRmResource`. For more information, see the [usage of Get-AzureRmResource](/previous-versions/powershell/module/azurerm.resources/get-azurermresource).
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/azure-functions/monitoring/functions-monitoring-appinsightslogs.md

@@ -1,8 +1,8 @@
 ---
 title: Application Insights logs are missing or incorrect
 description: Ths article helps you resolve issues related to missing or incorrect logs for Application Insights logs in Azure Functions.
-ms.date: 08/24/2023
-ms.reviewer: gasridha, v-jayaramanp
+ms.date: 01/16/2025
+ms.reviewer: gasridha, v-jayaramanp, agaltrai, jarrettr 
 ms.custom: sap:Monitoring using Application Insights, Metrics and Alerts
 ---
 
@@ -30,6 +30,23 @@ If the Application Insights logs are missing, or if the data appears to be parti
 
   **Recommendation**: The function app should be on version 4 and the runtime version should be at least 4.15.2*xx*. This is because, from this version onwards, you can track the log flows from Azure Functions to the Application Insights service. By monitoring the log flows, you can check for missing logs.
 
+## Custom application logs
+
+By default, custom application logs you write are sent to the Functions host, which then sends them to Application Insights under the [Worker category](/azure/azure-functions/configure-monitoring#configure-categories). However, some language stacks allow you to send the logs directly to Application Insights, which gives you full control over how logs you write are emitted. In this case, the logging pipeline changes from `worker > Functions host > Application Insights` to `worker > Application Insights`.
+
+The following table summarizes the configuration options available for each stack:
+
+| Language stack | Where to configure custom logs |
+|-|-|
+| .NET (in-process model) | `host.json` |
+| .NET (isolated model) | Default (send custom logs to the Functions host): `host.json`<br/>To send logs directly to Application Insights, see [Configure Application Insights in the HostBuilder](/azure/azure-functions/dotnet-isolated-process-guide#application-insights).  |
+| Node.JS | `host.json` |
+| Python | `host.json` |
+| Java | Default (send custom logs to the Functions host): `host.json`<br/>To send logs directly to Application Insights, see [Configure the Application Insights Java agent](/azure/azure-monitor/app/monitor-functions#distributed-tracing-for-java-applications). |
+| PowerShell | `host.json` |
+
+When you configure custom application logs to be sent directly, the host no longer emits them, and `host.json` no longer controls their behavior. Similarly, the options exposed by each stack apply only to custom logs, and they don't change the behavior of the other runtime logs described in this article. In this case, to control the behavior of all logs, you might need to make changes in both configurations.
+
 ## Logs are missing or partial
 
 Application Insights collects log, performance, and error data. [Sampling configuration](/azure/azure-functions/configure-monitoring#configure-sampling) is used to reduce the volume of telemetry. The Sampling feature is enabled by default with the settings shown in the following [host.json](/azure/azure-functions/functions-host-json#applicationinsights) example. Excluded types aren't sampled.

support/azure/azure-kubernetes/extensions/troubleshoot-failed-kubernetes-deployment-offer.md

@@ -132,7 +132,7 @@ You can use the Azure CLI commands that are described in the [Azure CLI legal te
 
 #### [PowerShell](#tab/PowerShell)
 
-To accept the legal terms through PowerShell, run the cmdlets that are described in the [PowerShell legal terms](/powershell/module/azurerm.marketplaceordering).
+To accept the legal terms through PowerShell, run the cmdlets that are described in the [PowerShell legal terms](/powershell/module/az.marketplaceordering).
 
 ---
 

support/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting.md

@@ -154,9 +154,13 @@ Having to reenter credentials is most likely the result of Conditional Access po
 
 To reduce the frequency of having to reenter credentials because of errors like the preceding ones, talk to your Microsoft Entra admin.
 
-### Conditional access policies
+### Other conditional access policy issues
 
-If you have conditional access policies that need to be satisfied for your account, make sure you're using the **Default Web Browser** value for the **Sign in with** setting. For information on that setting, see [Changing where sign-in happens](/azure/storage/common/storage-explorer-sign-in#changing-where-sign-in-happens).
+If you have other conditional access policies that need to be satisfied for your account, try using either the **Authentication Broker** or **Default Web Browser** value for the **Sign in with** setting. For information on that setting, see [Changing where sign-in happens](/azure/storage/common/storage-explorer-sign-in#changing-where-sign-in-happens).
+
+### Issues with authentication broker on Windows
+
+The Windows operating system uses the Web Account Manager (WAM) as its authentication broker. If you're using the **Authentication Broker** sign-in method on Windows and experience issues, see [this guide](/entra/msal/dotnet/advanced/exceptions/wam-errors) for steps to resolve common errors.
 
 ### Browser complains about HTTP redirect or insecure connection during sign-in
 

support/azure/synapse-analytics/dedicated-sql/connectivity/dsql-conn-dropped-connections.md

@@ -38,7 +38,7 @@ The following PowerShell script downloads and runs the latest version of the Azu
 
 > [!NOTE]
 > - To run the tests in Linux, from computers that have no Internet access, or from a containerized environment, see [SQL connectivity checker on GitHub](https://github.com/Azure/SQL-Connectivity-Checker).
-> - For more PowerShell commands, see [Available PowerShell commands](/powershell/module/azurerm.sql#sql).
+> - For more PowerShell commands, see [Available PowerShell commands](/powershell/module/az.sql#sql).
 
 1. Open Windows PowerShell ISE (in **Administrator** mode if possible).
    > [!NOTE]

support/azure/virtual-machines/linux/how-to-use-perfInsights-linux.md

@@ -19,8 +19,6 @@ ms.author: genli
 
 **Applies to:** :heavy_check_mark: Linux VMs
 
-[!INCLUDE [CentOS End Of Life](../../../includes/centos-end-of-life-note.md)]
-
 [PerfInsights Linux](https://aka.ms/perfinsightslinuxdownload) is a self-help diagnostics tool that collects and analyzes the diagnostic data, and provides a report to help troubleshoot Linux virtual machine performance problems in Azure. PerfInsights can be run on supported virtual machines as a standalone tool, or directly from the portal by using [Performance Diagnostics for Azure virtual machines](../windows/performance-diagnostics.md).
 
 If you are experiencing performance problems with virtual machines, before contacting support, run this tool.
@@ -199,11 +197,10 @@ The following categories of rules are currently supported:
     | Distribution               | Version                                         |
     |----------------------------|-------------------------------------------------|
     | Oracle Linux Server        | 6.10 [`*`], 7.3, 7.5, 7.6, 7.7, 7.8, 7.9 |
-    | CentOS                     | 6.5 [`*`], 7.6, 7.7, 7.8, 7.9                                    |
-    | RHEL                       | 7.2, 7.5, 8.0 [`*`], 8.1, 8.2, 8.6, 8.8                               |
-    | Ubuntu                     | 14.04, 16.04, 18.04, 20.04, 22.04                               |
-    | Debian                     | 8, 9, 10, 11 [`*`]                                    |
-    | SLES                       | 12 SP4 [`*`], 12 SP5 [`*`], 15 [`*`], 15 SP1 [`*`], 15 SP2 [`*`], 15 SP4 [`*`]                                      |
+    | RHEL                       | 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 8.0 [`*`], 8.1, 8.2, 8.4, 8.5, 8.6, 8.7, 8.8, 8.9                               |
+    | Ubuntu                     | 16.04, 18.04, 20.04, 22.04                               |
+    | Debian                     | 9, 10, 11 [`*`]                                    |
+    | SLES                       | 12 SP5 [`*`], 15 SP1 [`*`], 15 SP2 [`*`], 15 SP3 [`*`], 15 SP4 [`*`], 15 SP5 [`*`], 15 SP6 [`*`]                                     |
     | AlmaLinux                  | 8.4, 8.5                                               |
     | Azure Linux               | 2.0                                                   |
 
@@ -217,8 +214,6 @@ The following categories of rules are currently supported:
 
 - RHEL 8 doesn't have Python installed by default because both Python 2 and Python 3.6 are available. To install Python 3.6, run the `yum install python3` command.
 
-- Guest Agent information collection may fail on CentOS 6.x.
-
 - PCI devices information is not collected on Debian based distributions.
 
 - LVM information is partially collected on some distributions.

support/azure/virtual-machines/windows/extension-version-2.2-not-supported.md

@@ -26,7 +26,7 @@ To work around this problem, use one of the following methods.
 
 ### Method 1
 
-Revert to using the Microsoft Entra parameters in the syntax for [Set-AzureRmVmDiskEncryptionExtension](/powershell/module/azurerm.compute/set-azurermvmdiskencryptionextension?view=azurermps-6.2.0&preserve-view=true).
+Revert to using the Microsoft Entra parameters in the syntax for [Set-AzVMDiskEncryptionExtension](/powershell/module/az.compute/set-azvmdiskencryptionextension).
 
 The parameters are the following:
 
@@ -40,7 +40,7 @@ The parameters are the following:
 Opt in to the "UnifiedDiskEncryptionForVMs" feature for your subscription by running the following script before you try again to enable encryption:
 
 ```powershell
-Register-AzureRmProviderFeature -ProviderNamespace "Microsoft.Compute" -FeatureName "UnifiedDiskEncryptionForVMs" # Wait 10 minutes until state transitions to 'Registered' Register-AzureRmResourceProvider -ProviderNamespace Microsoft.Compute
+Register-AzProviderFeature -ProviderNamespace "Microsoft.Compute" -FeatureName "UnifiedDiskEncryptionForVMs" # Wait 10 minutes until state transitions to 'Registered' Register-AzResourceProvider -ProviderNamespace Microsoft.Compute
 ```
 
 ## More Information
@@ -50,18 +50,18 @@ Register-AzureRmProviderFeature -ProviderNamespace "Microsoft.Compute" -FeatureN
 Run the following script:
 
 ```
-Set-AzureRmVMDiskEncryptionExtension -ResourceGroupName $resourceGroupName -VMName $vmName -DiskEncryptionKeyVaultUrl $diskEncryptionKeyVaultUrl -DiskEncryptionKeyVaultId $keyVaultResourceId -KeyEncryptionKeyUrl $keyEncryptionKeyUrl -KeyEncryptionKeyVaultId $keyVaultResourceId -VolumeType 'All';
+Set-AzVMDiskEncryptionExtension -ResourceGroupName $resourceGroupName -VMName $vmName -DiskEncryptionKeyVaultUrl $diskEncryptionKeyVaultUrl -DiskEncryptionKeyVaultId $keyVaultResourceId -KeyEncryptionKeyUrl $keyEncryptionKeyUrl -KeyEncryptionKeyVaultId $keyVaultResourceId -VolumeType 'All';
 DEBUG: 10:47:22 AM - SetAzureDiskEncryptionExtensionCommand end processing.
-Set-AzureRmVMDiskEncryptionExtension : Azure Disk Encryption extension version '2.2' is not supported.
+Set-AzVMDiskEncryptionExtension : Azure Disk Encryption extension version '2.2' is not supported.
 ErrorCode: NotSupported
 ErrorMessage: Azure Disk Encryption extension version '2.2' is not supported.
 StatusCode: 409
 ReasonPhrase: Conflict
 OperationID : 2cb4ac35-e2a5-4cd4-84d9-3174663e0a46
 At line:1 char:1
-+ Set-AzureRmVMDiskEncryptionExtension -ResourceGroupName $resourceGrou ...
++ Set-AzVMDiskEncryptionExtension -ResourceGroupName $resourceGrou ...
 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-    + CategoryInfo          : CloseError: (:) [Set-AzureRmVMDiskEncryptionExtension], ComputeCloudException
+    + CategoryInfo          : CloseError: (:) [Set-AzVMDiskEncryptionExtension], ComputeCloudException
 ```
 
 ## Status