Merging changes synced from https://github.com/MicrosoftDocs/SupportArticles-docs-pr (branch live)

Author: Learn Build Service GitHub App

support/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry.md

@@ -33,19 +33,6 @@ Run Performance Diagnostics directly from the Azure portal, where you can also r
 
 This article explains how to use Performance Diagnostics and what the continuous and on-demand modes offer.
 
-## Known issues
-
-### Existing user-assigned managed identities removed from VM
-
-**Issue**<br>
-If system-assigned managed identity is disabled on a VM, installing Performance Diagnostics using system-assigned managed identity will unintentionally remove any existing user-assigned managed identities from the VM.<br><br>
-**Cause**<br>
-If system-assigned managed identity is disabled on a VM and the authentication method selected during installation is system-assigned managed identity, Performance Diagnostics attempts to enable the system-assigned managed identity with an ARM template deployment. ARM treats the identity property as a complete object rather than a partial update. Because the deployment template specified only `SystemAssigned` as the identity type, it overwrites any existing user-assigned managed identities. This results in the removal of all user-assigned managed identities since both identity types weren' t explicitly defined in the template. This issue does not occur if system-assigned managed identity is already enabled on the VM before installing Performance Diagnostics using system-assigned managed identity.<br><br>
-**Status**<br>
-The product team is actively working on a fix and will update the status once the fix is available.<br><br>
-**Workaround**<br>
-To install Performance Diagnostics using a system-assigned managed identity on a VM that already has user-assigned managed identities, you must enable the system-assigned managed identity on the VM before installation to avoid overwriting existing identities. Alternatively, you can install Performance Diagnostics using other authentication methods such as user-assigned managed identity or storage account access keys.
-
 ## Prerequisites
 
 * To run continuous and on-demand diagnostics on Windows, you need [.NET SDK](/dotnet/core/install/windows) version 4.5 or a later version installed.

support/azure/virtual-machines/windows/performance-diagnostics.md

@@ -1,8 +1,8 @@
 ---
 title: Issues when creating and deploying Azure resource groups
 description: Provides a resolution for issues that might occur when you try to create and deploy Azure resource groups through Visual Studio.
-ms.date: 10/22/2024
-ms.reviewer: jgao, puichan, v-sidong
+ms.date: 10/21/2025
+ms.reviewer: jgao, puichan
 ms.custom: sap:Integrated Development Environment (IDE)\Other
 ---
 
@@ -11,7 +11,7 @@ ms.custom: sap:Integrated Development Environment (IDE)\Other
 _Applies to:_ Visual Studio
 
 > [!NOTE]
-> The Azure Resource Group project is now in extended support. We will continue to support existing features and capabilities but won't prioritize adding new features.
+> The Azure Resource Group project has been in extended support since October 2024 and only ships in Visual Studio 2022 and older versions. This feature isn't available in Visual Studio 2026 and newer versions.
 
 This article helps you solve issues related to creating and deploying Azure resource groups.
 
@@ -25,11 +25,15 @@ When you try to [create and deploy Azure resource groups through Visual Studio](
 
 ## Cause
 
-These issues occur when you use unsupported older versions of Visual Studio.
+These issues occur when using an unsupported version of Visual Studio.
 
 ## Resolution
 
-To solve this issue, upgrade your Visual Studio installation to the latest [Long-Term Support (LTS) version](/visualstudio/install/update-visual-studio). Upgrading to the latest version can enhance the reliability and overall experience of your Visual Studio environment.
+Make sure you're using a supported version of Visual Studio. This feature is available in:
+
+- Visual Studio 2017
+- Visual Studio 2019
+- Visual Studio 2022
 
 ## More information
 

support/developer/visualstudio/ide/troubleshoot-create-deploy-resource-group.md

@@ -0,0 +1,67 @@
+---
+title: SQL Server Agent Startup Fails with Error 17156 Could Not Initiate the EventLog Service
+description: Learn how to troubleshoot error 17156 "Could not initiate the EventLog Service" when you start SQL Server Agent.
+ms.reviewer: v-shaywood
+ms.date: 10/10/2025
+ms.custom: sap:Startup, shutdown, restart issues (instance or database)\Cannot start SQL Server
+---
+
+# Error 17156 "Could not initiate the EventLog Service" when starting SQL Server Agent
+
+This article provides troubleshooting guidance for error 17156, "Could not initiate the EventLog Service," that might occur when you start SQL Server Agent. This error can appear after you install or upgrade to Windows Server 2022 or 2025. It prevents SQL Server Agent from starting.
+
+## Symptoms
+
+After you install or upgrade Microsoft SQL Server on Windows Server 2025 or 2022, SQL Server Agent doesn't start. When the startup process fails, it adds an entry to the SQL Server error log that resembles the following example:
+
+```log
+2025-10-02 08:24:32.26 Server      Error: 17156, Severity: 16, State: 1.
+2025-10-02 08:24:32.26 Server      initeventlog: Could not initiate the EventLog Service for the key 'MSSQL$SQL2022',  or last error code is 5.
+2025-10-02 08:24:32.26 Server      Microsoft SQL Server 2022 (RTM-CU21) (KB5065865) - 16.0.4215.2 (X64)
+                                   Aug 11 2025 13:24:21
+                                   Copyright (C) 2022 Microsoft Corporation
+                                   Developer Edition (64-bit) on Windows Server 2025 Datacenter 10.0 <X64> (Build 26100: ) (Hypervisor)
+```
+
+## Cause
+
+Error code 5 is [OS error 5](/windows/win32/debug/system-error-codes--0-499-#:~:text=ERROR_ACCESS_DENIED,Access%20is%20denied.) "Access is denied," which means a permission restriction. This error can occur if SQL Server Agent is blocked from writing to the Application event log. During startup, the SQL Server Agent tries to register its own event source to the Application event log. However, without write access, registration fails. If SQL Server Agent doesn't register the event source, the startup process terminates.
+
+An incorrect configuration in the **Configure log access** group policy can prevent SQL Server Agent from writing to the Application event log. If the **Configure log access** policy doesn't grant write access to the account that's used by SQL Server Agent, the agent doesn't start.
+
+This error can appear after you install or upgrade to Windows Server 2025 or 2022 because of a change in how the **Configure log access** policy is enforced. In Windows Server 2019 and earlier versions, the **Configure log access** policy wasn't enforced correctly: SQL Server Agent would be able to write to the Application event log even without being granted access through Group Policy. In Windows Server 2022 and later versions, the **Configure log access** policy is enforced correctly: SQL Server Agent can't write to the Application event log unless it's configured correctly in Group Policy.
+
+## Solution
+
+To resolve this error, either disable the **Configure log access** Group Policy policy or update it to grant write access to the account that's used by SQL Server Agent.
+
+1. Locate the **Configure log access** policy settings:
+
+   1. Open the Local Group Policy Editor.
+
+      :::image type="content" source="./media/error-17156-event-log-service/group-policy-editor.png" alt-text="The Local Group Policy Editor window is shown.":::
+
+   1. Select **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Event Log Service** > **Application**.
+
+      :::image type="content" source="./media/error-17156-event-log-service/event-log-service-policies.png" alt-text="The Local Group Policy Editor window showing the Application folder as selected.":::
+
+1. Open the **Configure log access** setting.
+
+   :::image type="content" source="./media/error-17156-event-log-service/configure-log-access-setting.png" alt-text="The Configure log access settings window.":::
+
+1. Update the policy setting using one of these two methods:
+
+   1. To disable the policy, set its value to either **Disabled** or **Not Configured**.
+
+      :::image type="content" source="./media/error-17156-event-log-service/disable-log-access-policy.png" alt-text="The Configure log access settings window shows the Disabled setting as selected.":::
+
+   1. To update the policy, append the following text to the Security Descriptor Definition Language (SDDL) string in the **Options** panel:
+
+      > (A;;0x7;;;\<SQL-Server-Agent-Account-SID\>)
+
+      :::image type="content" source="./media/error-17156-event-log-service/update-log-access-policy.png" alt-text="The Configure log access settings window showing the additional Security Descriptor Definition Language (SDDL) string that's appended in the Options panel":::
+
+## References
+
+- [How to set event log security locally or by using Group Policy](~/windows-server/group-policy/set-event-log-security-locally-or-via-group-policy.md)
+- [View the SQL Server error log](/sql/tools/configuration-manager/viewing-the-sql-server-error-log)

support/sql/database-engine/startup-shutdown/error-17156-event-log-service.md

@@ -7,6 +7,8 @@ items:
   href: agent-service-fails-start-stand-alone-server.md
 - name: Error 1069 when starting SQL Server
   href: error-1069-service-cannot-start.md
+- name: Error 17156 when starting SQL Server Agent
+  href: error-17156-event-log-service.md
 - name: Error 17182 when you start SQL Server service
   href: error-17182-protocols-disabled-start-failure.md
 - name: Event ID 17058 and SQL Server doesn't start