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

Author: Learn Build Service GitHub App

SharePoint/SharePointOnline/sharing-and-permissions/request-access-to-resource.md

@@ -1,6 +1,6 @@
 ---
-title: User without permission to resource can't receive the option to request access
-description: This article describes an issue that users without permissions to a SharePoint Online resource don't receive the option to request access to the resource, and provides a solution.
+title: Users without permissions to a SharePoint Online resource can't request access
+description: Describes an issue in which users without permissions to a SharePoint Online resource don't receive the option to request access to the resource, and provides a solution.
 author: Cloud-Writer
 manager: dcscontentpm
 search.appverid: 
@@ -11,40 +11,43 @@ ms.custom:
   - sap:Sharing\Access requests
   - CSSTroubleshoot
 ms.author: meerak
+ms.reviewer: prbalusu, nirupme
 appliesto: 
   - SharePoint Online
-ms.date: 12/17/2023
+ms.date: 12/04/2025
 ---
 
-# Users without permissions to a SharePoint Online resource don't receive the option to request access to the resource
+# Users without permissions to a SharePoint Online resource can't request access
 
-## Problem
+## Symptoms
 
-When an existing user in an organization tries to access a SharePoint Online resource in Microsoft 365 for enterprises and the user doesn't have permission to the resource, they receive one of the following error messages:
+When existing users in an organization try to access a SharePoint Online resource, but they don't have permissions to the resource, they receive one of the following error messages:
 
-- **Sorry, this site hasn't been shared with you.**
-- **Error: Access Denied**
+- Sorry, this site hasn't been shared with you.
+- Error: Access Denied.
+- You can't access this item.
+- You don't have permission to access this item.
 
-This message is expected. However, in this scenario, users don't have an option to request access to the resource and you want users who receive the message to have an option to request access.
+However, users don't have an option to request access to the resource. 
 
-## Solution
+## Cause
 
-This occurs if access requests aren't enabled for the affected site collection. If this feature is turned off, it must enabled by site collection admins.
+The errors occur because access requests aren't enabled for the site collection that's associated with the resource.
 
-To fix this issue, enable the access requests for the site collection. To do this, follow these steps:
+## Resolution
 
-1. On the affected SharePoint Online site collection, click the gear icon for the **Settings** menu, and then click **Site Settings**.
+To resolve the errors, enable access requests for the affected site collection. You must be a site collection administrator to enable this feature. 
 
-1. On the **Site Settings** page, under **Users and Permissions**, select **Site permissions**.
+As a site collection administrator, use the following steps to enable access requests:
 
-1. Select **Access Request Settings**.
+1. On the affected SharePoint Online site collection, select **Settings** > **Site Settings**.
 
-1. Click to select the **Allow Access Requests** check box.
+1. On the **Site Settings** page, under **Users and Permissions**, select **Site permissions**.
 
-1. In the **Send all requests for access to the following email address**, type your email address, and then click **OK**.
+1. Select **Access Request Settings**.
 
-After you follow these steps, users who don't have permission to a SharePoint Online resource are directed to a page where they can request access. Requests for access are sent to the email address that you specified in step 5.
+1. Select the **Allow Access Requests** check box.
 
-## More information
+1. In the **Send all requests for access to the following email address**, enter the email address of the user acount that approves access requests, and then select **OK**.
 
-Still need help? Go to [SharePoint Community](https://techcommunity.microsoft.com/t5/sharepoint/ct-p/SharePoint).
+Now users who don't have permission to a SharePoint Online resource are directed to a page where they can request access. Requests for access are sent to the email address that's specified in step 5.

support/windows-client/toc.yml

@@ -1341,6 +1341,8 @@ items:
     items:
     - name: Enable diagnostic logging for the Windows Security app
       href: ./windows-security/how-to-enable-diagnostic-logging-for-windows-security-center.md
+    - name: Operations on confidential attributes produce unexpected results when using Windows Server 2025 DCs
+      href: ../windows-server/windows-security/confidential-attributes-unexpected-behavior-using-windows-server-2025-dc.md?context=/troubleshoot/windows-client/context/context
   - name: Zero Trust DNS
     items:
     - name: 'Troubleshooting Guidance: Zero Trust DNS'

support/windows-server/toc.yml

@@ -2776,6 +2776,8 @@ items:
       href: ./virtualization/cannot-change-configstorerootpath-value-hyperv-cluster.md
     - name: Users can't connect to virtual server after failover
       href: ./virtualization/mac-address-changes-for-virtual-server.md
+    - name: Windows updates don't install on VM cluster hosts
+      href: ./virtualization/windows-updates-dont-install-on-vm-cluster-hosts.md
   - name: Hyper-V Replica
     items:
     - name: Feature and performance optimization of HVR
@@ -3112,6 +3114,8 @@ items:
       href: ./windows-security/mark-attribute-as-confidential.md
     - name: Maximum number of access control entries
       href: ./windows-security/error-add-user-to-security-permissions.md
+    - name: Operations on confidential attributes produce unexpected results when using Windows Server 2025 DCs
+      href: ./windows-security/confidential-attributes-unexpected-behavior-using-windows-server-2025-dc.md
     - name: Security auditing settings aren't applied when you deploy domain-based policy
       href: ./windows-security/security-auditing-settings-not-applied-when-deploy-domain-based-policy.md
     - name: SeImpersonatePrivilege and SeCreateGlobalPrivilege

support/windows-server/virtualization/windows-updates-dont-install-on-vm-cluster-hosts.md

@@ -0,0 +1,98 @@
+---
+title: Windows Updates Don't Install on VM Cluster Hosts
+description: Discusses how to resolve issues that you might experience when you apply Windows updates to the hosts of a virtual machine (VM) cluster.
+ms.date: 12/04/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, simonw, v-appelgatet
+ms.custom:
+- sap:virtualization and hyper-v\high availability virtual machines
+- pcy:WinComm Storage High Avail
+appliesto:
+  - <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
+---
+
+# Windows updates don't install on VM cluster hosts
+
+This article discusses how to resolve issues that you might experience when you apply Windows updates to the hosts of a virtual machine (VM) cluster.
+
+## Symptoms
+
+You experience one or more of these symptoms:
+
+- Windows updates don't install on cluster hosts.
+- VMs intermittently don't migrate correctly.
+- Operations time out unexpectedly.
+
+## Cause
+
+These issues occur if checkpoints (sometimes known as snapshots) for the VMs in the cluster grow too large. Checkpoints generate large VMRS files. Such files consume disk space and can disrupt the migration process. Disruptions and insufficient disk space can further cause operations to time out and updates to fail to install.
+
+For more information about checkpoints, see [Using checkpoints to revert virtual machines to a previous state](/windows-server/virtualization/hyper-v/checkpoints).
+
+## Resolution
+
+Before you start, verify that you have admin access to the cluster hosts. Make sure you back up all critical data and configuration information.
+
+The following procedures assume that you're familiar with the Windows Update service and [Cluster-Aware Updating overview](/windows-server/failover-clustering/cluster-aware-updating).
+
+To resolve this issue, use one of the following solutions.
+
+### Solution 1: Manually update all hosts to the latest version
+
+> [!IMPORTANT]  
+> All hosts in a cluster should run the same version of Windows Server (including the same updates).
+
+Follow these steps on each cluster host:
+
+1. To identify the most recently installed update on the host computer, select **Settings** > **Update & Security** > **Windows Update** > **View update history**.
+1. Download and install the most recent compatible update for the host. You can use any of the following tools to access updates:
+
+   - Windows Update
+   - Windows Server Update Services (WSUS)
+   - The [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/)
+
+1. If it's necessary, restart the host.
+1. After the update process finishes, review the host's update history. Make sure that the update installed successfully.
+
+### Solution 2: Schedule CAU to occur during a maintenance window, and temporarily disable Windows Update services
+
+Use this solution to prevent conflicts between CAU and the Windows Update service.
+
+> [!IMPORTANT]  
+> Your systems might be vulnerable if you leave automatic updates disabled for an extended period. Schedule your maintenance window to be as brief as possible.
+
+1. In Failover Cluster Manager, select **Cluster-Aware Updating**.
+
+   > [!NOTE]  
+   > As an alternative method, you can open a Windows PowerShell Command Prompt window, and then run `Get-CauRun`.
+
+1. Review and modify the update schedule to align with your maintenance window.
+1. On each host, follow these steps to temporarily disable the Windows Update service:
+
+   1. Open the Services console (services.msc), and then select **Windows Update service**.
+   1. Right-click the service, select **Properties**, and then set **Startup type** to **Disabled**.
+   1. To stop the service, select **Stop**.
+
+1. After the subsequent maintenance window ends, check each host's update history to make sure that the updates installed successfully. To check a host's update history, select **Settings** > **Update & Security** > **Windows Update** > **View update history**.
+1. Use the Services console to re-enable the Windows Update service. In the service properties, set **Startup type** to **Automatic**, and then select **Start**.
+
+   > [!IMPORTANT]
+   > This final step makes sure that your hosts continue to receive security updates.
+
+### Solution 3: Remove checkpoints that you don't need
+
+Don't try to use VM checkpoints for long-term backup storage. Typically, checkpoints are useful for testing purposes.
+
+> [!NOTE]
+> Use this procedure during a maintenance window. When you delete a checkpoint, Windows merges the related differencing disk into the parent VHDX of the VM. For large VMs, this operation can be time-consuming and resource-intensive.
+
+When you no longer need the checkpoints, follow these steps to remove the checkpoints:
+
+1. Open the Hyper-V Manager or your preferred virtualization management tool.
+1. Go to the VM that has checkpoints.
+1. Review the checkpoints, and confirm that you don't need them.
+1. Delete each checkpoint. If it's necessary, confirm that you want to delete the checkpoint.
+1. Check the VM to make sure that the checkpoint is removed and the disk space is reclaimed.
+1. Try again to install the updates on the cluster hosts.