Skip to content

Commit c8b1f03

Browse files
committed
add toc node
1 parent f77daeb commit c8b1f03

2 files changed

Lines changed: 15 additions & 7 deletions

File tree

windows-365/enterprise/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -198,6 +198,8 @@ items:
198198
- name: Azure network connections
199199
href: troubleshoot-azure-network-connection.md
200200
- name: Azure network connection health checklist
201+
href: health-checks-connectivity.md
202+
- name: Connectivity health checks
201203
href: health-checks.md
202204
- name: Remote Desktop client
203205
href: /azure/virtual-desktop/troubleshoot-client?context=/windows-365/context/pr-context

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

Lines changed: 13 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -32,16 +32,11 @@ ms.collection: M365-identity-device-management
3232

3333
Connectivity health checks are run on individual Cloud PCs and give information on the state of the Cloud PC's connection. These checks are constantly run by the Windows 365 service in the backend. When any of these checks fail, the end user won’t be able to connect to their Cloud PC.
3434

35-
Connectivity errors can occur even when all connectivity health checks have successfully passed.
36-
3735
## View connectivity checks
3836

39-
1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **Azure network connections**.
37+
1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **All Cloud PCs**.
4038
2. Select a connection in the list > **Overview** > **Connectivity and usage (preview)**.
4139

42-
43-
An admin is also able to look at the connectivity history of a user to see if user might have experience failed connectivity check, or connectivity error in the last 14 days.
44-
4540
## Connectivity checks
4641

4742
| Check | Failure description | Troubleshooting |
@@ -57,9 +52,20 @@ An admin is also able to look at the connectivity history of a user to see if us
5752

5853
If any of these issues persist, contact Microsoft support.
5954

55+
Connectivity errors can occur even when all connectivity health checks have successfully passed.
56+
6057
## User connectivity history report
6158

62-
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. The report shows of the following activities:
59+
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.
60+
61+
### View Connectivity history report
62+
63+
1. Sign in to [windows365.microsoft.com](https://windows365.microsoft.com) > **Devices** > **Windows 365** > **All Cloud PCs**.
64+
2. Select a connection in the list > **Overview** > **Connectivity and usage (preview)** > **View connectivity history**.
65+
66+
### Activities
67+
68+
The report shows of the following activities:
6369

6470
| Activity | Description |
6571
| --- | --- | --- |

0 commit comments

Comments
 (0)