Skip to content

Commit fb7882f

Browse files
committed
Updated syntax
1 parent f6907a2 commit fb7882f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

azure-local/update/update-troubleshooting-23h2.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ This scenario occurs when preparing to install system updates in Azure Update Ma
4949
Follow the remediation instructions to resolve the failures.
5050

5151
> [!NOTE]
52-
> The system health checks run every 24 hours, so it may take up to 24 hours for the new results to sync to the Azure portal after remediating the failures. To initiate a new system health check immediately or further troubleshoot, see the [PowerShell](update-troubleshooting-23h2.md#using-powershell) section.
52+
> The system health checks run every 24 hours, so it may take up to 24 hours for the new results to sync to the Azure portal after remediating the failures. To initiate a new system health check immediately or further troubleshoot, see the [PowerShell](#using-powershell) section.
5353
5454
**Scenario 2: Update readiness checks**
5555

@@ -67,7 +67,7 @@ This scenario occurs when installing and tracking system updates in Azure Update
6767

6868
Follow the remediation instructions to resolve the failures and then select the **Try again** button to retry the pre-update readiness checks and **Resume the update**.
6969

70-
To further troubleshoot, see the [PowerShell](#using-powershell) section.
70+
To further troubleshoot, see the [PowerShell](#powershell) section.
7171

7272
### Using PowerShell
7373

@@ -239,7 +239,7 @@ If there is an issue that causes an update to fail, reviewing the detailed step
239239
240240
- Failure message string (may pinpoint the issue to a specific known issue with documented remediation).
241241
242-
Microsoft recommends using the Azure portal to identify the failing step information as shown at [Resume an update](./update-troubleshooting-23h2.md#the-azure-portal). Alternatively, see the next section for how view similar details in PowerShell using `Start-MonitoringActionplanInstanceToComplete`.
242+
Microsoft recommends using the Azure portal to identify the failing step information as shown at [Resume an update](#the-azure-portal). Alternatively, see the next section for how view similar details in PowerShell using `Start-MonitoringActionplanInstanceToComplete`.
243243
244244
See the table below for update failure scenarios and remediation guidelines.
245245
@@ -253,7 +253,7 @@ See the table below for update failure scenarios and remediation guidelines.
253253
254254
You can also collect diagnostic logs to help Microsoft identify and fix the issues.
255255
256-
To collect logs for updates using the Azure portal, see [Resume an update](./update-troubleshooting-23h2.md#the-azure-portal).
256+
To collect logs for updates using the Azure portal, see [Resume an update](#the-azure-portal).
257257
258258
To collect logs for the update failures see [Collect diagnostic logs for Azure Local, version 23H2](../manage/collect-logs.md?tabs=azureportal.md).
259259

0 commit comments

Comments
 (0)