Merge pull request #10127 from MicrosoftDocs/main

learn-build-service-prod[bot] · web-flow · commit 896d7ae19a94 · 2025-11-05T22:03:37.000Z
Auto Publish – main to live - 2025-11-05 22:00 UTC
diff --git a/SharePoint/OneDrive/storage/check-storage-increase-eligibility.md b/SharePoint/OneDrive/storage/check-storage-increase-eligibility.md
@@ -4,7 +4,7 @@ description: Check if your storage is eligible to be increased to greater than 5
 author: Cloud-Writer
 ms.author: meerak
 manager: dcscontentpm
-ms.date: 11/04/2024
+ms.date: 11/05/2025
 audience: Admin
 ms.topic: troubleshooting
 ms.custom: 
@@ -44,10 +44,6 @@ Admins can request Microsoft to increase the default storage space up to 25 TB p
 
 1. After the user's OneDrive storage limit is increased, you can [set a different limit for the user's storage space](/onedrive/change-user-storage) from the Microsoft 365 admin center or SharePoint Online Management Shell.
 
-> [!NOTE]  
-> - Users who reach at least 90 percent of their 25 TB capacity of OneDrive storage will be provided additional cloud storage in the form of a 25 TB SharePoint team site. For more information and assistance, contact [Microsoft Support](https://go.microsoft.com/fwlink/?linkid=869559).
-> - The maximum amount of OneDrive storage provided to any single Education user with OneDrive for Business Plan 2 is 25 TB. Pooled storage limits still apply at the tenant level.
-
 ## References
 
 For more information about the storage that’s available for Microsoft 365 subscriptions, see the [OneDrive service description](https://go.microsoft.com/fwlink/?linkid=826071).
diff --git a/support/azure/partner-solutions/index.yml b/support/azure/partner-solutions/index.yml
@@ -63,5 +63,9 @@ landingContent:
     linkLists:
       - linkListType: how-to-guide
         links:
+          - text:  Can't install or uninstall the agent on a VM
+            url:  new-relic/install-uninstall-extension-vm.md
           - text:  Update ingestion key after rotation
             url: ingestion-key-rotation-log-flow.md
+          - text: Resource monitoring stopped working
+            url: new-relic/resource-monitoring-troubleshoot.md
diff --git a/support/azure/partner-solutions/new-relic/install-uninstall-extension-vm.md b/support/azure/partner-solutions/new-relic/install-uninstall-extension-vm.md
@@ -0,0 +1,65 @@
+---
+title: Can't Install or Uninstall the Agent on a Virtual Machine
+description: Resolve problems with installing or uninstalling the New Relic agent on a virtual machine. 
+author: shijojoy
+ms.author: jarrettr
+ms.reviewer: v-ryanberg
+ms.service: partner-services
+ms.topic: troubleshooting-problem-resolution
+ms.custom: New Relic troubleshooting
+ms.date: 09/18/2025
+ai-usage: ai-assisted
+
+#customer intent: As an Azure administrator or user, I want to resolve problems with installing or uninstalling the New Relic agent on virtual machines.
+
+---
+
+# Can't install or uninstall the agent on a virtual machine
+
+This article explains how to resolve problems with installing or uninstalling the New Relic agent on a virtual machine (VM). Specifically, it describes what to do if you select VMs and the **Install Extension** or **Uninstall Extension** button is unavailable.
+
+## Prerequisites
+
+- An Azure account with permissions to manage VM extensions (Contributor or Owner on the subscription or resource group, or a role with explicit extension management permissions).
+- The target VMs must be visible in the Azure portal on the **Virtual machines** page.
+
+## Symptoms
+
+- On the **Virtual Machines** page of the New Relic resource, the **Install Extension** button is unavailable (dimmed) after you select one or more VMs.
+- On the **Virtual Machines** page of the New Relic resource, the **Uninstall Extension** button is unavailable (dimmed) after you select one or more VMs.
+
+## Cause
+
+The portal enables the **Install Extension** or **Uninstall Extension** button only when the entire selection of VMs matches the required state for that action:
+
+- **Install Extension** is enabled only when none of the selected VMs has the New Relic agent installed.
+- **Uninstall Extension** is enabled only when every selected VM already has the New Relic agent installed.
+
+The Azure portal displays the agent/extension state in the **Agent status** column:
+
+- VMs on which the New Relic agent is installed show **Running** or **Shutdown**.
+- VMs on which the New Relic agent isn't installed show **Not Installed**.
+
+If your selection includes VMs in different states (some that have the agent and some that don't), neither **Install Extension** nor **Uninstall Extension** will be enabled.
+
+## Solution 
+
+1. In the Azure portal, go to the **Virtual Machines** page of the New Relic resource.
+1. To install the New Relic agent:
+   1. Select only VMs that show an **Agent status** of **Not Installed**.
+   1. Deselect any VMs that show a status of **Running** or **Shutdown**. (These VMs already have the agent.)
+   1. Confirm that the **Install Extension** button is active and then proceed.
+1. To uninstall the New Relic agent:
+   1. Select only VMs that show an **Agent status** of **Running** or **Shutdown**. (These VMs have the agent installed.)
+   1. Deselect any VMs that show a status of **Not Installed**.
+   1. Confirm that the **Uninstall Extension** button is active and then proceed.
+
+## Related content
+
+- [Manage extensions on Azure virtual machines](/azure/virtual-machines/extensions/overview)
+- [Troubleshoot VM Agent issues](../../virtual-machines/windows/windows-azure-guest-agent.md)
+- [Introduction to the Azure Native New Relic Service](https://docs.newrelic.com/docs/infrastructure/microsoft-azure-integrations/get-started/azure-native/)
+
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/partner-solutions/new-relic/resource-monitoring-troubleshoot.md b/support/azure/partner-solutions/new-relic/resource-monitoring-troubleshoot.md
@@ -0,0 +1,59 @@
+---
+title: Resource Monitoring Stopped Working 
+description: Troubleshoot situations in which New Relic stops receiving logs or metrics from Azure resources.
+author: shijojoy
+ms.author: jarrettr
+ms.reviewer: v-ryanberg
+ms.service: partner-services
+ms.topic: troubleshooting-general
+ms.custom: New Relic troubleshooting
+ms.date: 09/19/2025
+ai-usage: ai-assisted
+
+#customer intent: As an Azure administrator or user, I want to troubleshoot situations in which New Relic monitoring stops working.
+
+---
+
+# Resource monitoring stopped working 
+
+This article helps you troubleshoot situations in which New Relic stops receiving telemetry (logs, metrics, or events) from Azure resources like virtual machines (VMs) and app services. 
+
+## Prerequisites
+
+- Access to the New Relic account that owns the ingest API key (API key admin or owner).
+- Access to the Azure subscription and resource group that contain the affected resources (Reader to view, Contributor/Owner to remediate or change billing).
+ 
+## Causes and solutions
+
+### Cause: Ingest API key is revoked
+
+Resource monitoring in New Relic is enabled through the *ingest API key*, which you set up at the time of resource creation. Revoking the ingest API key from the New Relic portal disrupts monitoring of logs and metrics for all resources, including virtual machines and app services. You shouldn't revoke the ingest API key.
+
+#### Solution
+
+- If the API key is revoked, contact [New Relic support](https://support.newrelic.com/).
+
+### Cause: Azure subscription suspended or deleted 
+
+If your Azure subscription is suspended or deleted for payment-related issues, resource monitoring in New Relic automatically stops. 
+
+#### Solution
+
+- If the subscription is suspended or deleted for payment-related reasons, either update the payment method or move resources to an active subscription. For more information, see [Add, update, or delete a payment method](/azure/cost-management-billing/manage/change-credit-card).
+
+### Cause: New Relic service issues
+
+New Relic manages the APIs for creating and managing resources, and for the storage and processing of telemetry data. The New Relic APIs might be on or outside of Azure. Some issues can originate outside of Azure.  
+
+#### Solution
+
+If your Azure subscription and resource are working correctly but the New Relic portal shows problems with monitoring data, contact [New Relic support](https://support.newrelic.com/).
+
+## Related content
+
+- [Add, update, or delete a payment method](/azure/cost-management-billing/manage/change-credit-card)
+- [New Relic support](https://support.newrelic.com/)
+
+[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
+
+[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/partner-solutions/toc.yml b/support/azure/partner-solutions/toc.yml
@@ -49,6 +49,8 @@ items:
       href: informatica/resource-creation.md
 - name: New Relic
   items:
+    - name: Can't install or uninstall the agent on a VM
+      href: new-relic/install-uninstall-extension-vm.md
     - name: Diagnostic settings manual update
       href: diagnostic-settings-manual-update.md
     - name: Diagnostic settings not created
@@ -59,5 +61,5 @@ items:
       href: log-forwarding-persists.md
     - name: Log limitations
       href: log-limitations.md
-
-
+    - name: Resource monitoring stopped working
+      href: new-relic/resource-monitoring-troubleshoot.md
diff --git a/support/azure/virtual-machines/linux/swap-file-not-recreated-linux-vm-restart.md b/support/azure/virtual-machines/linux/swap-file-not-recreated-linux-vm-restart.md
@@ -130,8 +130,8 @@ Now, create a VM with [az vm create](/cli/azure/vm) and specify the cloud-init f
 ```azurecli-interactive
 az vm create \
   --resource-group myResourceGroup \
-  --name centos74 \
-  --image OpenLogic:CentOS:7-CI:latest \
+  --name redhat810 \
+  --image  RedHat:RHEL:8_10:latest \
   --custom-data cloud_init_swappart.txt \
   --generate-ssh-keys 
 ```
@@ -154,7 +154,7 @@ The output from this command should look like this:
 
 ```output
 Filename                Type        Size    Used    Priority
-/dev/sdb2  partition   2494440 0   -1
+/dev/sdb2             partition   2494440     0      -1
 ```
 
 > [!NOTE]
diff --git a/support/azure/virtual-machines/linux/troubleshoot-linux-rhui-certificate-issues.md b/support/azure/virtual-machines/linux/troubleshoot-linux-rhui-certificate-issues.md
@@ -882,7 +882,7 @@ Trying other mirror.
 
 ---
 
-## Cause 5: Verification error in RHEL version 8 or 9 ("CA certificate key too weak")
+## Cause 5: Verification error in RHEL version 8, 9, or 10 ("CA certificate key too weak")
 
 The system tries to connect to a server that contains a certificate that's signed by using 2048-bit RSA keys. However, the system has a `FUTURE` policy setting that prohibits that cryptographic algorithm. The following error messages are shown in the */var/log/messages* or */var/log/dnf.log* file:
 
diff --git a/support/azure/virtual-machines/windows/toc.yml b/support/azure/virtual-machines/windows/toc.yml
@@ -243,8 +243,6 @@ items:
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-installation-error-corruption.md
     - name: Error Code 0x8007045b
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md
-    - name: Error Code 0x800f0831
-      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-installation-error.md
 
 - name: My VM is not booting
   items:
diff --git a/support/windows-client/toc.yml b/support/windows-client/toc.yml
@@ -1089,6 +1089,8 @@ items:
       href: ../windows-server/system-management-components/open-client-can-not-connect-server.md?context=/troubleshoot/windows-client/context/context
     - name: OpenSSH Server Service Doesn't Start and Generates Error 1053
       href: ../windows-server/system-management-components/openssh-server-service-wont-start-error-1053.md?context=/troubleshoot/windows-client/context/context
+    - name: Troubleshoot common SFTP issues when using OpenSSH
+      href: ../windows-server/system-management-components/troubleshoot-sftp-issues-using-openssh.md?context=/troubleshoot/windows-client/context/context
     - name: Use "MaxStartups" and "MaxSessions" to troubleshoot OpenSSH connection issues
       href: ../windows-server/system-management-components/troubleshoot-openssh-connection-issues-maxstartups-maxsessions.md?context=/troubleshoot/windows-client/context/context
   - name: PowerShell
diff --git a/support/windows-server/admin-development/events-not-forwarded-by-windows-server-collector.md b/support/windows-server/admin-development/events-not-forwarded-by-windows-server-collector.md
@@ -37,7 +37,7 @@ The forwarder is having a problem communicating with subscription manager at add
 This behavior is caused by the permissions that are configured for the following URLs:
 
 - `http://+:5985/wsman/`
-- `http://+:5986/wsman/`
+- `https://+:5986/wsman/`
 
 On the event collector computer, both the Windows Event Collector service (WecSvc) and the Windows Remote Management service (WinRM) use these URLs. However, the default access control lists (ACLs) for these URLs allow access for only the svchost process that runs WinRM.
 In the default configuration of Windows Server 2016, a single svchost process runs both WinRM and WecSvc. Because the process has access, both services function correctly. However, if you change the configuration so that the services run on separate host processes, WecSvc no longer has access and event forwarding no longer functions.
diff --git a/support/windows-server/system-management-components/troubleshoot-sftp-issues-using-openssh.md b/support/windows-server/system-management-components/troubleshoot-sftp-issues-using-openssh.md
@@ -0,0 +1,132 @@
+---
+title: Troubleshoot Common SFTP Issues
+description: Explains how to resolve common SFTP issues when you use OpenSSH for Windows.
+ms.date: 11/05/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, warrenw, v-appelgatet
+ms.custom:
+- sap:system management components\openssh (including sftp)
+- pcy:WinComm User Experience
+appliesto:
+  - ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
+  - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
+---
+# Troubleshoot common SFTP issues when using OpenSSH
+
+OpenSSH on Windows provides secure file transfer protocol (SFTP) capabilities. This article describes how to resolve the most common issues that you might encounter when you use SFTP and OpenSSH to administer Windows Server and Windows Client.
+
+## Best practices and additional resources
+
+- Use the latest supported OpenSSH version.
+- Avoid configuring OpenSSH to use a network share for the chroot directory.
+- Every time that you change the OpenSSH Server configuration, validate the change by running `sshd -t`.
+- When you start troubleshooting, check Event Viewer for relevant events.
+
+For more information about how to configure OpenSSH on Windows and Windows Server, see the following articles:
+
+- [Get started with OpenSSH for Windows](/windows-server/administration/openssh/openssh_install_firstuse)
+- [OpenSSH Server configuration for Windows Server and Windows](/windows-server/administration/openssh/openssh-server-configuration)
+
+### How to enable SFTP logging
+
+To enable SFTP logging for the OpenSSH Server service, modify the sshd_config file, and then restart the OpenSSH Server service. Follow these steps:
+
+1. Use an administrator-level account to open a text editor, and then open **%ProgramData%\ssh\sshd_config**. The default text of the "Logging" section should resemble the following excerpt:
+
+   ```output
+   # Logging
+   #SyslogFacility AUTH
+   #LogLevel INFO
+   ```
+
+1. To enable SFTP logging, edit the text to resemble the following excerpt:
+
+   ```output
+   # Logging
+   SyslogFacility LOCAL0
+   LogLevel DEBUG3
+   ```
+
+   Also, add (or modify) the following text:
+
+   ```output
+   Subsystem sftp sftp-server.exe -f LOCAL0 -l DEBUG3
+   ```
+
+1. Save and close the sshd_config file.
+
+1. To restart the OpenSSH Server service, open a Windows Command Prompt window, and then run the following command:
+
+   ```console
+   NET STOP "OpenSSH SSH Server" && NET START "OpenSSH SSH Server"
+   ```
+
+After the service restarts, it generates SFTP log data in %ProgramData%\ssh\logs. For more information about OpenSSH logging, see [How to enable OpenSSH verbose logging](enable-openssh-verbose-logging.md).
+
+## Common SFTP issues on Windows and Windows Server
+
+### SFTP users land in the wrong directory or outside the chroot jail
+
+When correctly configured, the chroot directory restricts (jails) users to a specific directory tree. This restriction prevents users from accessing the rest of the file system.
+
+Check the following settings:
+
+- In the sshd_config file, make sure that `ChrootDirectory` points to a local directory and doesn't use a UNC path.
+- Make sure that SYSTEM/Administrators has owner permissions on the chroot directory.
+- Make sure that each user has a writeable directory within the chroot directory, and that the directory has the correct permissions. Secure the /.ssh/authorized_keys files.
+
+  > [!NOTE]  
+  > To verify and fix NTFS permissions, use the [icacls](/windows-server/administration/windows-commands/icacls) command in an administrative Command Prompt window.
+
+- In the sshd_config file, use`ForceCommand internal-sftp`, and use the `-d` switch together with the `Subsystem sftp sftp-server.exe` command to set an upload directory. You can use these settings in `Match` blocks to specify users.
+
+### Specific users can't use SFTP or they receive "Access denied" errors
+
+This behavior indicates ownership or permissions issues. Check the following settings:
+
+- Make sure that SYSTEM/Administrators has owner permissions on the chroot directory.
+- Make sure that each user has a writeable directory within the chroot directory, and that the directory has the correct permissions. Secure the /.ssh/authorized_keys files.
+
+  > [!NOTE]  
+  > To verify and fix NTFS permissions, use the [icacls](/windows-server/administration/windows-commands/icacls) command in an administrative Command Prompt window.
+
+### Users can't sign in or they receive "Authentication failed" or "Server refused our key"
+
+This behavior indicates public key or password issues. Check the following configurations:
+
+- Use C:\ProgramData\ssh\administrators_authorized_keys to store keys, and use `icacles` to check the file and folder permissions.
+- If the server refuses the key, add the following lines to sshd_config:
+
+  ```console
+  PubkeyAcceptedKeyTypes +ssh-rsa
+  HostKeyAlgorithms +ssh-rsa
+  ```
+
+  > [!NOTE]  
+  > After you make these changes, restart the OpenSSH Server service.
+
+### OpenSSH Server service doesn't start, or SFTP connections hang
+
+To resolve these issues, try the following actions:
+
+- To validate the sshd_config settings, run the `sshd -t` command.
+- Review Event Viewer for any relevant events.
+- To check and repair Access Control Lists (ACLs) on the chroot directory tree, run the `icacles` command.
+- Review the sshd_config settings. Make sure that the entries don't have any trailing spaces, and make sure that the `Subsystem sftp sftp-server.exe` command is present.
+
+If none of these actions resolve the issue, uninstall and reinstall OpenSSH Server.
+
+### SFTP logs are missing or incomplete
+
+Review the log settings in ssdh_config. SFTP log data is stored in %ProgramData%\ssh\logs.
+
+To check and repair ACLs on the log folder, run the `icacles` command.
+
+###  Users can't upload or download files
+
+- In the sshd_config file, make sure that `ChrootDirectory` points to a local directory and doesn't use a UNC path.
+- Make sure that SYSTEM/Administrators has owner permissions on the chroot directory.
+- Make sure that each user has a writeable directory within the chroot directory, and that the directory has the correct permissions. To check and repair ACLs, run the `icacles` command.
+- Make sure that users don't have writer permission on the chroot directory.
diff --git a/support/windows-server/toc.yml b/support/windows-server/toc.yml
@@ -2608,6 +2608,8 @@ items:
       href: ./system-management-components/openssh-server-service-wont-start-error-1053.md
     - name: OpenSSH client can't connect to a server via SSH
       href: ./system-management-components/open-client-can-not-connect-server.md
+    - name: Troubleshoot common SFTP issues when using OpenSSH
+      href: ./system-management-components/troubleshoot-sftp-issues-using-openssh.md
     - name: Use "MaxStartups" and "MaxSessions" to troubleshoot OpenSSH connection issues
       href: ./system-management-components/troubleshoot-openssh-connection-issues-maxstartups-maxsessions.md
   - name: PowerShell
diff --git a/support/windows-server/virtualization/merge-checkpoints-with-many-differencing-disks.md b/support/windows-server/virtualization/merge-checkpoints-with-many-differencing-disks.md
