Merge pull request #10219 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-19 18:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -13923,6 +13923,10 @@
     {
       "source_path": "support/dynamics-365/commerce/payments/adyen-support.md",
       "redirect_url": "/dynamics365/commerce/dev-itpro/payments-retail#what-is-the-service-level-agreement-sla-for-out-of-box-payment-connectors-like-adyen"
+    },
+    {
+      "source_path": "support/power-platform/power-automate/desktop-flows/ui-automation/ui-sap-automation/sap-click-element-dpi.md",
+      "redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/sap-automation/sap-click-element-dpi"
     }
   ]
 }

support/azure/azure-monitor/log-analytics/billing/set-up-a-daily-cap.md

@@ -15,7 +15,7 @@ This article helps you learn how to set up a daily cap limit for a Log Analytics
 
 ## Strategies for safeguarding against unexpected data ingestion surges
 
-The daily cap on a Log Analytics workspace enables you to avoid unexpected increases in charges for data ingestion by stopping the collection of billable data for the rest of the day whenever a specified threshold is reached. Daily caps are typically used by organizations that are particularly cost-conscious. They shouldn't be used as a method to reduce costs but, instead, as a preventative measure to make sure that you don't exceed a particular budget.
+The daily cap on a Log Analytics workspace enables you to avoid unexpected increases in charges for data ingestion by stopping the collection of billable data for the rest of the day whenever a specified threshold is reached. Daily caps are typically used by organizations that are particularly cost-conscious. They shouldn't be used as a method to reduce costs but, instead, as a preventative measure to make sure that you don't exceed a particular budget. Learn more in the Log Analytics Daily Cap documentation.
 
 When data collection stops, you effectively have no monitoring of features or resources that rely on that workspace. Instead of relying on the daily cap alone, you can create an alert rule to notify yourself when data collection reaches a specified level before the daily cap is reached. Notification enables you to address any increases before data collection shuts down, or even to temporarily disable collection for less critical resources.
 
@@ -37,9 +37,9 @@ When data collection stops, you effectively have no monitoring of features or re
 1. On the **Usage and estimated costs** page, select **Daily Cap** at the top of the page.
 
     :::image type="content" source="media/set-up-a-daily-cap/open-daily-cap.png" alt-text="Screenshot that shows how to open Daily Cap." lightbox="media/set-up-a-daily-cap/open-daily-cap.png":::
-1. Configure the Daily Cap settings. Notice that security data types aren't affected by the daily cap. 
+1. Configure the Daily Cap settings.  
 
-    1. Select **ON** to enable the daily cap.
+1. Select **ON** to enable the daily cap.
     1. Set the data volume limit (in GB per day). 
 
     :::image type="content" source="media/set-up-a-daily-cap/configure-daily-cap.png" alt-text="Screenshot that shows how to configure Daily Cap settings." lightbox="media/set-up-a-daily-cap/configure-daily-cap.png":::

…-dpi/mutli-monitor-scaling-awareness.png …-dpi/mutli-monitor-scaling-awareness.pngsupport/power-platform/power-automate/desktop-flows/ui-automation/ui-sap-automation/media/sap-click-element-dpi/mutli-monitor-scaling-awareness.png renamed to support/power-platform/power-automate/desktop-flows/sap-automation/media/sap-click-element-dpi/mutli-monitor-scaling-awareness.png support/power-platform/power-automate/desktop-flows/ui-automation/ui-sap-automation/media/sap-click-element-dpi/mutli-monitor-scaling-awareness.png renamed to support/power-platform/power-automate/desktop-flows/sap-automation/media/sap-click-element-dpi/mutli-monitor-scaling-awareness.png

@@ -28,6 +28,8 @@ This issue occurs because the SAP application isn't fully DPI aware and might no
 
    :::image type="content" source="media/sap-click-element-dpi/mutli-monitor-scaling-awareness.png" alt-text="Screenshot of the Multi-monitor scaling awareness option in SAP Theme Settings.":::
 
-2. On Windows, go to **System** > **Display** and set the **Scale** to 100%.
+1. Terminate all SAP processes.
 
-[!INCLUDE [Third-party disclaimer](../../../../../includes/third-party-disclaimer.md)]
+1. On Windows, go to **System** > **Display** and set the **Scale** to 100%.
+
+[!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]

…-sap-automation/sap-click-element-dpi.md …/sap-automation/sap-click-element-dpi.mdsupport/power-platform/power-automate/desktop-flows/ui-automation/ui-sap-automation/sap-click-element-dpi.md renamed to support/power-platform/power-automate/desktop-flows/sap-automation/sap-click-element-dpi.md support/power-platform/power-automate/desktop-flows/ui-automation/ui-sap-automation/sap-click-element-dpi.md renamed to support/power-platform/power-automate/desktop-flows/sap-automation/sap-click-element-dpi.md

@@ -84,6 +84,8 @@
       items:
         - name: Can't open SAP
           href: desktop-flows/sap-automation/scripting-permissions-launch-sap.md
+        - name: SAP UI element click issue
+          href: desktop-flows/sap-automation/sap-click-element-dpi.md
     - name: UI automation
       items:    
         - name: A desktop application crashes due to UI automation
@@ -100,8 +102,6 @@
           href: desktop-flows/ui-automation/ui-automation-action-fails-errors.md
         - name: Interactions with RDP or Citrix applications take a long time and fail
           href: desktop-flows/ui-automation/ui-rdp-automation/interactions-with-rdp-citrix-takes-long-and-fails.md
-        - name: SAP UI element click issue
-          href: desktop-flows/ui-automation/ui-sap-automation/sap-click-element-dpi.md
         - name: Set drop-down list value in window/on web page action fails
           href: desktop-flows/ui-automation/set-drop-down-list-value-fails.md
         - name: UI element highlighting or hovering issues in virtual desktops

support/power-platform/power-automate/toc.yml

@@ -0,0 +1,68 @@
+---
+title: Can't Power on Hyper-V VM and Merges Fail
+description: Resolves issues that prevent you from powering on Hyper-V VM because of insufficient free disk space.
+ms.date: 10/06/2025
+author: kaushika-msft
+ms.author: kaushika
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika
+ms.custom:
+- sap: virtualization and hyper-v\virtual machine state
+- pcy: Virtualization\virtual machine state
+appliesto:
+  - <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
+---
+
+# Can't power on Hyper-V VM and merge operations fail
+
+## Summary
+
+This article discusses an issue in which a virtual machine (VM) that runs on Hyper-V can't power on because of insufficient free disk space. This problem is often associated with checkpoint disks and failed merge operations that cause critical I/O alerts. The following steps help you to resolve this issue effectively.
+
+## Prerequisites
+
+- Make sure that you have access to the Hyper-V environment.
+- Back up all essential data from the VM before you try any of the solutions.
+- Verify that you have sufficient permissions to perform the resolutions.
+
+## Symptoms
+
+You might encounter the following symptoms:
+
+- The VM can't power on. Merge operations for checkpoint disks fail.
+- Critical I/O alerts appear in the Hyper-V Manager or event logs.
+- A snapshot of approximately 800GB (or other large sizes) doesn't merge.
+
+## Cause
+
+The root cause of the issue is insufficient free disk space on the drive that hosts the VM. This lack of space prevents the merge operation of checkpoint disks. That condition, in turn, prevents the VM from powering on. This issue is observed in environments that run Windows Server 2019.
+
+## Solution 1: Export the VM to a temporary location
+
+1. Export the affected VM to a Network Attached Storage (NAS) appliance or any other storage device that has sufficient free space.
+2. Verify that the export process completes successfully.
+3. Run the VM from the NAS appliance temporarily until permanent storage is ready.
+
+## Solution 2: Upgrade the existing storage
+
+1. Upgrade the current drives that host the VM. Replace them with larger-capacity drives.
+2. Rebuild the storage array to accommodate the new drives.
+3. Create a new Logical Unit Number (LUN) to allocate storage for the VM.
+
+## Solution 3: Migrate the VM back to local storage
+
+1. After the new storage is configured, restore the VM from the NAS appliance to the local storage that has expanded capacity.
+2. Start the merge operation for the checkpoint disks by using the increased storage space.
+3. Monitor the merge process to make sure that it finishes successfully.
+
+These steps should help you to resolve the issue and enable the VM to power on without any more disk space-related errors.
+
+## Determine the cause of the problem
+
+If the issue persists, or if you encounter additional problems, review the following items:
+
+- Check the available disk space on the drive hosting the VM and make sure it meets the requirements.
+- Review Hyper-V Manager logs for any further details regarding the merge failures or I/O alerts.
+- Verify the configuration of the storage array to make sure it's optimized for VM operations.

support/windows-server/virtualization/cannot-power-on-hyper-v-vm.md

@@ -0,0 +1,93 @@
+---
+title: Can't Restore VM From Checkpoint in Hyper-V on Windows Server 2016
+description: Resolves issues that occur during a planned cluster node drain operation if Cluster Shared Volumes stop responding. 
+ms.date: 10/06/2025
+author: kaushika-msft
+ms.author: kaushika
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika
+ms.custom:
+- sap: virtualization and hyper-v\snapshots, checkpoints, and differencing disks
+- pcy: Virtualization\snapshots, checkpoints, and differencing disks
+appliesto:
+  - <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
+---
+
+# Can't restore a VM from a checkpoint in Hyper-V on Windows Server 2016
+
+## Summary
+
+This article discusses an issue in which you can't restore a virtual machine (VM) from a checkpoint in a Hyper-V environment that runs on Windows Server 2016. The issue typically occurs after an operating system (OS) upgrade, and it often involves checkpoint corruption or misalignment.
+
+## Symptoms
+
+- Error message: "An error occurred while attempting to export the data from checkpoint."
+- The VM can't be restored from the latest checkpoint.
+- Multiple checkpoints are present, but none can be used to successfully restore the VM.
+- Data loss is reported, requiring urgent recovery.
+- The issue begins immediately after an OS upgrade, such as from Windows 10 to Windows 11.
+- Hyper-V VM Management Service (VMMS) admin logs and checkpoint chain integrity are analyzed, revealing irregularities.
+- Attempts to merge checkpoints fail, causing concerns about possible data loss.
+
+## Cause
+
+The issue occurs because of one or more of the following reasons:
+
+- The checkpoint wasn't merged correctly before you ran the OS upgrade, or the upgrade was run without using the latest checkpoint in the VM.
+- Changes were made directly to the original virtual hard disk (VHDX) file after creating a checkpoint, causing a misalignment in the checkpoint chain.
+- The VM became inconsistent with the checkpoint structure and caused corruption or breakage in the chain.
+- A corrupted or missing VM configuration file further contributed to the inability to restore the VM from the checkpoint.
+
+## Resolution
+
+To resolve the issue, follow these steps:
+
+1. Back up VM files:
+
+    - Before you try any recovery steps, back up all checkpoints and VHD files to a secure location. This step minimizes the risk of permanent data loss.
+1. Inspect the checkpoint chain:
+
+    - Run the following PowerShell script to verify the chain of differencing disks:
+
+    ```powershell
+    Get-VHDChain -Path <path to vhd file></path>
+    ```
+
+    - Analyze the output to identify any inconsistencies or corruption in the chain.
+
+1. Manually merge checkpoints:
+
+    - Try to manually merge the checkpoints by using PowerShell commands. For example:
+
+        ```powershell
+        Merge-VHD -Path <Path to AVHDX file> -DestinationPath <Path to merged VHDX file>
+        ```
+    - Notify the customer of potential risks, including data loss, before you proceed to merge.
+1. Re-create the VM:
+
+    - If merging checkpoints fails, re-create the VM by using the backed-up files. Make sure that you configure the new VM to point to the merged VHDX file.
+
+1. Follow proper checkpoint management practices:
+        - Always merge checkpoints before you perform OS upgrades.
+        - Avoid direct changes to the original VHDX file if checkpoints exist.
+        - Regularly maintain and verify checkpoints to make sure of integrity.
+1. Confirm resolution:
+
+    - After the recovery steps are completed, verify with the customer that the VM is operational and data was restored.
+
+By following these steps and recommendations, you can resolve the checkpoint restoration issue and prevent similar problems in the future.
+
+## Data collection
+
+Before you contact Microsoft Support, you can gather the following information about your issue.
+
+- Hyper-V VMMS admin logs. These logs can be collected from the Event Viewer under Applications and Services Logs > Microsoft > Windows > Hyper-V-VMMS.
+- Results from running the Get-VHDChain PowerShell command to inspect the integrity of the VHD chain.
+- Any additional error messages or logs that provide insight into the checkpoint issue.
+
+## References
+
+- [Using checkpoints to revert virtual machines to a previous state](/windows-server/virtualization/hyper-v/checkpoints?tabs=hyper-v-manager)
+- [Windows Server 2012 Hyper-V Best Practices](https://techcommunity.microsoft.com/blog/coreinfrastructureandsecurityblog/windows-server-2012-hyper-v-best-practices-in-easy-checklist-form/256060)

support/windows-server/virtualization/cannot-restore-vm-from-checkpoint-in-hyper-v.md

@@ -0,0 +1,102 @@
+---
+title: Host Guardian Service Troubleshooting Guide
+description: Resolves issues that occur when you configure HGS to use HTTPS for key protection and attestation in test environments.
+ms.date: 10/06/2025
+author: kaushika-msft
+ms.author: kaushika
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika
+ms.custom:
+- sap: virtualization and hyper-v\shielded virtual machines
+- pcy: Virtualization\shielded VMs
+appliesto:
+  - <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
+---
+
+# Can't configure HGS for HTTPS key protection and attestation
+
+## Summary
+
+This article helps you to handle issues that occur when you configure the Host Guardian Service (HGS) to use HTTPS for key protection and attestation in test environments. By following these steps and guidelines, you can resolve configuration issues that affect the HGS, and ensure secure communication for your VMs.
+
+## Symptoms
+
+The following symptoms occur when you try to enable HTTPS on the HGS:
+
+- Attestation and key unwrap operations for VMs fail.
+- TLS (Transport Layer Security) and certificate trust errors appear in browsers and clients.
+- The certificate’s Subject Alternative Name (SAN) includes only the DNS HGS service name and not individual node hostnames.
+- You receive the following error message:
+
+> TransientError Host Unreachable
+
+When this issue occurs, the following conditions apply:
+
+- Failures occur during attestation and key unwrap processes over HTTPS.
+- The configuration functions correctly when HTTP is used instead of HTTPS.
+- Network trace and Test-NetConnection confirm communication on required ports.
+- The certificate’s Subject Alternative Name (SAN) includes only the DNS HGS service name and not individual node hostnames.
+- The issue isn't reproducible in other test environments, such as the support engineer’s lab environment.
+
+## Cause
+
+The root cause of the problem is related to the HTTPS configuration and certificate requirements for HGS:
+
+- Nonmandatory HTTPS: HTTPS is optional for HGS. HTTP communications are already encrypted at the message level as part of the Key Protection Service (KPS) protocol.
+- Certificate issues: The certificate that's used for HTTPS doesn't meet the documented requirements, such as missing SAN entries for all HGS node hostnames.
+- Environment-specific factors: The issue might be caused by configuration or compatibility challenges that are specific to the environment, or from deprecated features in the Windows Server version that's used.
+- Feature design: Development confirms that HGS over HTTP provides adequate encryption, and HTTPS isn't required for security.
+
+## Resolution
+
+To resolve this issue, follow these steps:
+
+1. Use HTTP for HGS communication:
+
+Based on recommendations from the product and development teams, you should continue to use HTTP for HGS. HTTP provides message-level encryption, ensuring data security.
+
+2. Validate encryption:
+
+Collect network traces to verify that HTTP payloads are encrypted and not exposed in plain text.
+
+3. Certificate reconfiguration (if HTTPS is required):
+
+If HTTPS must be used, make sure that certificates meet all documented requirements, including SAN entries for all HGS node hostnames. Consult the HGS documentation for guidance to issue certificates correctly.
+
+4. Use available tools for troubleshooting and validation:
+
+Use the following tools and commands to troubleshoot and verify the configuration:
+
+- Test-NetConnection to verify required port connectivity
+- PowerShell cmdlets such as Set-HgsServer for configuring HGS
+- Network tracing tools to verify encryption of HTTP payloads
+- Browser-based validation to verify HTTPS endpoint and certificate trust
+
+5. Plan for future deployments:
+
+- Review feature deprecation notices for HGS and shielded VMs in newer Windows Server versions.
+- Consider alternatives, such as Azure Confidential Computing, for future deployments.
+
+6. Review documentation and guidelines:
+
+- Share relevant public documentation and internal guidelines with your team to ensure proper configuration and understanding of HGS.
+
+## Data collection
+
+Before you contact Microsoft Support, you can gather the following information about your issue.
+
+- Network traces: Perform network tracing during key protection exchanges to verify encryption of communications.
+- PowerShell diagnostic outputs: Collect outputs from HGS servers and guarded hosts by using HGS-related PowerShell commands.
+- HTTP and HTTPS traffic logs: Analyze logs for TLS-related errors and communication issues.
+- Configuration details: Record details about the environment, such as certificate attributes, HGS node hostnames, and DNS configuration.
+
+## References
+
+- [Host Guardian Service overview](/windows-server/security/guarded-fabric-shielded-vm/guarded-fabric-and-shielded-vms)
+- [Configure HGS](/windows-server/security/guarded-fabric-shielded-vm/guarded-fabric-setting-up-the-host-guardian-service-hgs)
+- [Certificate requirements for HGS](/windows-server/security/guarded-fabric-shielded-vm/guarded-fabric-obtain-certs)
+- [How to configure HTTPS](/windows-server/security/guarded-fabric-shielded-vm/guarded-fabric-configure-hgs-https)
+- [Frequently Asked Question About HGS Certificates](/archive/blogs/datacentersecurity/frequently-asked-questions-about-hgs-certificates)
+ [Azure Confidential Computing](/azure/confidential-computing/overview)