Skip to content

Commit fa1d8b8

Browse files
authored
Merge pull request #9001 from MicrosoftDocs/main
Auto push to live 2025-05-26 10:06:00
2 parents f16ff6a + 4e184d3 commit fa1d8b8

24 files changed

+144
-98
lines changed

support/azure/virtual-machines/windows/understand-vm-reboot.md

Lines changed: 13 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ ms.service: azure-virtual-machines
1010
ms.topic: troubleshooting
1111
ms.tgt_pltfrm: na
1212
ms.workload: infrastructure-services
13-
ms.date: 10/14/2024
13+
ms.date: 05/26/2025
1414
ms.author: genli
15-
ms.reviewer: yutorigo, sinhamanisha, v-weizhu
15+
ms.reviewer: yutorigo, sinhamanisha, justingross, v-weizhu
1616
ms.custom: sap:VM restarted or stopped unexpectedly
1717
---
1818
# Understand a system reboot for Azure VM
@@ -98,13 +98,13 @@ The VM is hosted on a physical server that is running inside an Azure datacenter
9898

9999
Server faults are usually caused by hardware failure, such as the failure of a hard disk or solid-state drive. Azure continuously monitors these occurrences, identifies the underlying bugs, and rolls out updates after the mitigation has been implemented and tested.
100100

101-
Because some host server faults can be specific to that server, a repeated VM reboot situation might be improved by manually redeploying the VM to another host server. This operation can be triggered by using the **redeploy** option on the details page of the VM, or by stopping and restarting the VM in the Azure portal.
101+
Because some host server faults can be specific to that server, a repeated VM reboot situation might be improved by manually redeploying the VM to another host server. This operation can be triggered by using the [redeploy](redeploy-to-new-node-windows.md#use-the-azure-portal) option on the details page of the VM, or by stopping and restarting the VM in the Azure portal.
102102

103103
### Auto-recovery
104104

105-
The Azure platform is designed to handle host node issues with minimal impact on VM performance. When a host node encounters a problem, Azure first attempts the least disruptive recovery method, which is to reboot the host. If rebooting the host isn't possible or if the original issue is hardware-related, the platform service heals all VMs on the affected host to a healthy node. While rebooting a host generally has a lower impact, service healing VMs can be more complex and time-consuming, depending on the number of VMs, their deployment constraints, and local resource availability. Service healing is typically used as a last resort for hardware failures because it ensures that VMs continue to operate without significant downtime.
105+
The Azure platform is designed to handle host node issues with minimal impact on VM performance. When a host node encounters a problem, Azure first attempts the least disruptive recovery method, which is to reboot the host. If rebooting the host isn't possible or the issue is hardware-related, Azure initiates an automatic recovery action to take the faulty host out of rotation for further investigation. As part of this automatic recovery, a process known as service healing will automatically relocate all VMs on the faulty host to another healthy one. This process is usually completed within 15 minutes, although the recovery time can vary depending on factors such as the host's memory size and recovery methods used. Service healing is typically used as a last resort for hardware failures to ensure that VMs continue to operate without significant downtime.
106106

107-
If a host server can't reboot, Azure initiates an automatic recovery action to take the faulty host out of rotation for further investigation. During this auto-recovery process, all VMs on the host are automatically relocated to another healthy host server. While this process usually completes within 15 minutes, the recovery time can vary based on factors such as the host's memory size and the recovery methods used. For more details about how Azure handles these scenarios, see [Service Healing – Auto-recovery of Virtual Machines](https://azure.microsoft.com/blog/service-healing-auto-recovery-of-virtual-machines/).
107+
For more details about how Azure handles these scenarios, see [Service Healing – Auto-recovery of Virtual Machines](https://azure.microsoft.com/blog/service-healing-auto-recovery-of-virtual-machines/).
108108

109109
### Unplanned maintenance
110110

@@ -117,7 +117,12 @@ Unplanned maintenance include the following:
117117

118118
### VM crashes
119119

120-
VMs might restart because of issues within the VM itself. The workload or role that's running on the VM might trigger a bug check within the guest operating system. For help determining the reason for the crash, view the system and application logs for Windows VMs, and the serial logs for Linux VMs.
120+
VMs might restart due to internal VM issues or hardware issues, such as an OS disk issue, as described earlier. The workload or role running on the VM might trigger a bug check in the guest OS. To find the reason for the crash, check the system and application logs for Windows VMs and the serial logs for Linux VMs. Collecting a memory dump is usually the best way to identify the root cause.
121+
122+
For more information, see the following articles:
123+
124+
- [Windows crash dump information](../../..//windows-server/performance/memory-dump-file-options.md)
125+
- [Linux crash dump information](../linux/serial-console-nmi-sysrq.md#distribution-specific-documentation)
121126

122127
### Storage-related forced shutdowns
123128

@@ -127,8 +132,8 @@ VMs in Azure rely on virtual disks for operating system and data storage that is
127132

128133
In rare circumstances, a widespread issue can affect multiple servers in an Azure datacenter. If this issue occurs, the Azure team sends email notifications to the affected subscriptions. You can check the [Azure Service Health dashboard](https://azure.microsoft.com/status/) and the Azure portal for the status of ongoing outages and past incidents.
129134

130-
## Diagnose VM Restarts
135+
## Diagnose VM restarts
131136

132-
You can use the Diagnose and Solve blade on the VM blade to run additional diagnostics. This may uncover more specific reasons for your recent VM restart. If there is any Guest OS issue, collect memory dump and contact support.
137+
You can use the **Diagnose and Solve** blade on the VM blade to run additional diagnostics. This may uncover more specific reasons for your recent VM restart. If there is any guest OS issue, collect a memory dump and contact support.
133138

134139
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/dynamics-365/commerce/welcome-commerce.yml

Lines changed: 1 addition & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ metadata:
99
ms.service: dynamics-365-commerce
1010
author: bstorie
1111
ms.author: brstor
12-
ms.date: 04/30/2025
12+
ms.date: 05/26/2025
1313

1414
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
1515

@@ -45,8 +45,6 @@ landingContent:
4545
links:
4646
- text: Items without inventory can be checked out
4747
url: ecommerce-storefront/items-without-inventory-checked-out.md
48-
- text: Pick this up option doesn't appear on cart or product details pages
49-
url: ecommerce-storefront/pickup-store-link-missing.md
5048
- text: Retail store doesn't appear in the list of stores to pick up from
5149
url: ecommerce-storefront/pickup-store-missing.md
5250
- text: Restrict access to a storefront during testing or development
@@ -61,8 +59,6 @@ landingContent:
6159
links:
6260
- text: Fix common statement posting issues by editing transactions
6361
url: financial-statements/fix-common-posting-issues.md
64-
- text: Issues with the data reconciliation of a Z report
65-
url: financial-statements/z-report-issues.md
6662
- text: Statement posting errors due to unavailable inventory or update conflicts
6763
url: financial-statements/inventory-errors-posting.md
6864

@@ -85,8 +81,6 @@ landingContent:
8581
url: order-management/payment-type-credit-card-error.md
8682
- text: Taxes on online orders are incorrectly calculated
8783
url: order-management/tax-miscalculated-online-order.md
88-
- text: Troubleshoot issues with the online store transaction creation process
89-
url: order-management/online-order-transaction-creation-failures.md
9084

9185
# Card
9286
- title: Payments
@@ -95,14 +89,10 @@ landingContent:
9589
links:
9690
- text: A card payment fails due to an unsupported card type
9791
url: payments/card-payments-fail-with-unsupported-card-type.md
98-
- text: Credit card entry page shows an error at checkout
99-
url: payments/credit-card-entry-form-error.md
10092
- text: Payments are automatically settled before orders are invoiced or shipped
10193
url: payments/payments-auto-settled.md
10294
- text: Refund on a return order is declined
10395
url: payments/refund-declined.md
104-
- text: Refundable charges are miscalculated based on returned quantity
105-
url: payments/refund-miscalculated-partial-return.md
10696
- text: Save for my next payment option doesn't appear
10797
url: payments/next-payment-link-not-appearing.md
10898
- text: Troubleshoot Dynamics 365 Payment Connector for Adyen issues
@@ -117,17 +107,3 @@ landingContent:
117107
url: point-of-sale/store-commerce-app-pos-deactivated.md
118108
- text: Troubleshoot Store Commerce extension issues
119109
url: point-of-sale/store-commerce-extensions.md
120-
- text: Troubleshoot Store Commerce performance issues
121-
url: point-of-sale/store-commerce-performance.md
122-
- text: Troubleshoot Store Commerce setup and installation issues
123-
url: point-of-sale/store-commerce-setup-installation.md
124-
- text: Troubleshoot Store Commerce sign-in issues
125-
url: point-of-sale/store-commerce-sign-in.md
126-
127-
# Card
128-
- title: Pricing, discounts, and taxes
129-
linkLists:
130-
- linkListType: how-to-guide
131-
links:
132-
- text: Price change tracking issues
133-
url: pricing-discounts-taxes/price-track-issues.md

support/sql/database-engine/security/antivirus-and-sql-server.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article describes how to configure antivirus software on compu
44
author: pijocoder
55
ms.author: jopilov
66
ms.reviewer: jopilov
7-
ms.date: 01/10/2025
7+
ms.date: 05/26/2025
88
ms.custom: sap:Security, Encryption, Auditing, Authorization
99
---
1010

@@ -222,11 +222,11 @@ If you back up the database to a disk or back up the transaction log to a disk,
222222

223223
For more information about antivirus considerations on a cluster, see [Antivirus software that isn't cluster-aware may cause problems with Cluster Services](../../../windows-server/high-availability/not-cluster-aware-antivirus-software-cause-issue.md).
224224

225-
### Arc enabled SQL Server
225+
### Arc-enabled SQL Server
226226

227-
You might see the following files and executables (also referred to as system objects) being flagged when running antivirus software on an [Arc enabled SQL Server](/sql/sql-server/azure-arc/connect). Consider excluding these [necessary system objects](/sql/sql-server/azure-arc/agent-extension-files) from antivirus scanning.
227+
When you run antivirus software on an [Arc-enabled SQL Server](/sql/sql-server/azure-arc/connect) instance, some files and executables (also referred to as system objects) might be flagged. However, these [system objects](/sql/sql-server/azure-arc/agent-extension-files) are necessary for Arc-enabled SQL Server to function properly. To ensure optimal performance and stability, we recommend that you exclude these [necessary system objects](/sql/sql-server/azure-arc/agent-extension-files) from antivirus scanning.
228228

229-
Starting with SQL Server 2025, SQL Server instances can use the Azure Arc machine's managed identity. You might need to add an exemption for the token folder. Follow the steps in [Setup managed identity for Arc enabled SQL Server](/sql/sql-server/azure-arc/managed-identity) for the proper setup and the folder path.
229+
Starting with SQL Server 2025, SQL Server instances can use the Azure Arc machine's managed identity. You might need to add an exemption for the token folder. Follow the steps in [Configure a managed identity for Arc-enabled SQL Server](/sql/sql-server/azure-arc/managed-identity) for the proper setup and the folder path.
230230

231231
We also recommend that you keep the extension up to date, as it includes ongoing security and feature updates. For more information, see the [latest extension release](/sql/sql-server/azure-arc/release-notes).
232232

support/windows-365/connection-error-interactive-window-not-shown.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,9 @@ manager: dcscontentpm
55
ms.date: 04/02/2025
66
ms.topic: troubleshooting
77
ms.reviewer: kaushika, erikje, v-lianna
8+
ms.custom:
9+
- pcy:Session connectivity\Users see random or intermittent disconnects
10+
- sap:WinComm User Experience
811
---
912
# Windows 365 Link connection fails with error "an interactive window could not be shown"
1013

support/windows-365/connection-errors.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,13 @@
11
---
2-
# required metadata
32
title: Troubleshoot connection errors
43
description: Troubleshoot connection errors in Windows 365.
54
manager: dcscontentpm
65
ms.date: 01/20/2025
76
ms.topic: troubleshooting
87
ms.reviewer: traceyadams, erikje
9-
ms.custom: intune-azure, get-started
8+
ms.custom:
9+
- pcy:Session connectivity\Users are not able to make a connection
10+
- sap:WinComm User Experience
1011
ms.collection:
1112
- M365-identity-device-management
1213
- tier2

support/windows-365/connection-fails-with-cloud-pc-does-not-support-entra-id-single-sign-on-sso.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@ manager: dcscontentpm
66
ms.date: 04/02/2025
77
ms.reviewer: wincicuex, erikje
88
ms.topic: troubleshooting
9+
ms.custom:
10+
- pcy:Session connectivity\Users are not able to make a connection
11+
- sap:WinComm User Experience
912
---
1013
# Windows 365 Link connection fails with "Cloud PC does not support Entra ID single sign-on"
1114

support/windows-365/connection-fails-with-connection-to-the-remote-pc-was-lost.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@ manager: dcscontentpm
66
ms.date: 04/02/2025
77
ms.reviewer: wincicuex, erikje
88
ms.topic: troubleshooting
9+
ms.custom:
10+
- pcy:Session connectivity\Users see random or intermittent disconnects
11+
- sap:WinComm User Experience
912
---
1013
# Windows 365 Link connection fails with "connection to the remote PC was lost"
1114

support/windows-365/connection-fails-with-failed-to-open-a-microsoft-entra-id-credential-prompt.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@ manager: dcscontentpm
66
ms.date: 04/02/2025
77
ms.reviewer: wincicuex, erikje
88
ms.topic: troubleshooting
9+
ms.custom:
10+
- pcy:Session connectivity\Users are not able to make a connection
11+
- sap:WinComm User Experience
912
---
1013
# Windows 365 Link connection fails with "Failed to open a Microsoft Entra ID credential prompt"
1114

support/windows-365/health-checks.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,9 @@ manager: dcscontentpm
55
ms.date: 01/20/2025
66
ms.topic: troubleshooting
77
ms.reviewer: mattsha, erikje
8-
ms.custom: intune-azure, get-started
8+
ms.custom:
9+
- pcy:Azure Network Connection\Health Check Issues
10+
- sap:WinComm User Experience
911
ms.collection:
1012
- M365-identity-device-management
1113
- tier2

support/windows-365/known-issues-enterprise.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,9 @@ manager: dcscontentpm
55
ms.date: 05/23/2025
66
ms.topic: troubleshooting
77
ms.reviewer: ivivano, erikje, scottduf
8-
ms.custom: get-started
8+
ms.custom:
9+
- pcy:Onboarding issues
10+
- sap:WinComm User Experience
911
ms.collection:
1012
- M365-identity-device-management
1113
- tier2

0 commit comments

Comments
 (0)