Skip to content

Commit ab67a1e

Browse files
author
Angela Fleischmann
authored
Apply suggestions from code review
Delete typo line 48 (checks > check) and extra blank lines 73-74 and 81-82.
1 parent 23a2920 commit ab67a1e

1 file changed

Lines changed: 1 addition & 5 deletions

File tree

windows-365/enterprise/health-checks-connectivity.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ If there is a problem with the Cloud PC's connection, the status will show as **
4545

4646
## Connectivity errors
4747

48-
When a connectivity checks fails, you'll see one of the following errors. Review the status pane to see more details. You can use the **Troubleshoot this connection** button to troubleshoot.
48+
When a connectivity check fails, you'll see one of the following errors. Review the status pane to see more details. You can use the **Troubleshoot this connection** button to troubleshoot.
4949

5050
- **Azure Resource Availability Check**: Azure resources are not up and running.
5151
- **DomainJoin**: This Cloud PC isn't joined to a domain.
@@ -72,15 +72,11 @@ Possible different view of this data:
7272
| VM Power Status Check | This Cloud PC is powered off and an issue is preventing it from turning back on. | If this persists, contact Microsoft support. |
7373
7474
75-
76-
7775
-->
7876
If any of these issues persist, contact Microsoft support.
7977

8078
Connectivity errors can occur even when all connectivity health checks have successfully passed.
8179

82-
83-
8480
## User connectivity history report
8581

8682
The user connectivity history report shows when a user started a connection and when the connection finished. There are different ways a connection can start/finish and these are logged as activities in the report.

0 commit comments

Comments
 (0)