Monitor the Microsoft Tunnel VPN solution for Microsoft Intune - Microsoft Intune | Microsoft Learn
In brief
The documentation now explains how to run `mst-cli diagnose` on a Tunnel Gateway, review logging checks, use the generated `diagnosticReport.txt`, and troubleshoot missing logs or failed uploads.
What Intune admins need to know
Administrators have documented steps to identify logging prerequisites, verify upload status, apply corrective guidance, and provide diagnostic details to Microsoft Support.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
For more information and command-line examples, see mst-cli command-line tool for Microsoft Tunnel.
Run diagnostics on the Tunnel server
Use mst-cli diagnose on an installed Tunnel server to check known prerequisites and configuration requirements, including those required for logging. Run diagnostics when expected logs are missing or a log upload fails.
To run diagnostics and review the logging checks:
Connect to the Linux server that hosts the affected Tunnel Gateway.
Run the following command on the server:
mst-cli diagnoseReview the logging results. Each logging check reports a pass or fail status and the expected result. The output also includes fixes for some common failures. Checks and corrective steps vary with the server's operating system and installation.
For a failed check, compare the result with the expected result and follow the corrective guidance provided for your configuration. Run
mst-cli diagnoseagain after making changes.View the Tunnel logs to check whether the expected entries are present. If you're investigating an upload failure, follow Troubleshoot missing logs or failed uploads to verify collection and upload separately.
The command creates a report named diagnosticReport.txt in /etc/mstunnel/diagnostic. You can share this report with Microsoft support for further analysis.
Diagnostics identify known unmet prerequisites. They don't identify or interpret every operating system customization or hardening setting that might affect Tunnel. A pass result applies to the check performed; it doesn't confirm that every customization is compatible or that logs were uploaded successfully.
View Microsoft Tunnel logs
Microsoft Tunnel logs information to the Linux server logs in the syslog format. To view log entries, use the journalctl -t command followed by one or more tags that are specific to Microsoft Tunnel entries:
The ocserv-access logs aren't collected or uploaded.
Troubleshoot missing logs or failed uploads
If expected Tunnel logs are missing or Send logs reports a failed upload, use the following steps:
- Run diagnostics on the affected Tunnel server. Review the logging checks and address failures using the guidance in the output.
- Check the logging prerequisites, including access to the required upload endpoints. If the server uses a customized or hardened operating system, review whether those changes affect the requirements identified by diagnostics.
- View the local Tunnel logs. Local log entries and passing diagnostic checks don't confirm that logs reached Microsoft.
- After addressing the identified failures, repeat the Send logs procedure. Reproduce the issue during the eight-hour verbose collection period, and check the status of each log set in the admin center. An in progress status isn't a completed upload. The second log set is collected and uploaded after the eight-hour period.
- If collection or upload still fails, contact Microsoft support. Include the diagnostic report, the failed checks, and the collection times and statuses shown in the admin center.
Known issues
The following are known issues for Microsoft Tunnel.
@@ -2,8 +2,8 @@ layout: Conceptual title: Monitor the Microsoft Tunnel VPN solution for Microsoft Intune - Microsoft Intune | Microsoft Learn canonicalUrl: https://learn.microsoft.com/en-us/intune/device-security/microsoft-tunnel/monitor-author: OluchiC-ms.author: ochukwunyere+author: CharlotteChristenson-MSFT+ms.author: CharlotteChristenson-MSFT breadcrumb_path: /intune/breadcrumb/toc.json uhfHeaderId: MSDocsHeader-Intune feedback_system: Standard@@ -14,8 +14,10 @@ ms.collection: ms.reviewer: ochukwunyere ms.subservice: protect description: Monitor the status of Microsoft Tunnel Gateway, a VPN server that runs on Linux. Microsoft Tunnel enables your Intune managed cloud-based devices to reach your on-premises infrastructure.-ms.date: 2024-10-14T00:00:00.0000000Z+ms.date: 2026-11-16T00:00:00.0000000Z ms.topic: how-to+ai-usage: ai-assisted+ms.custom: msecd-doc-authoring-1032 locale: en-us document_id: 6e710c6a-c6f2-2fc2-6e2a-d1fd6560a404 document_version_independent_id: 6e710c6a-c6f2-2fc2-6e2a-d1fd6560a404@@ -194,6 +196,26 @@ Use the **mst-cli** command-line tool to get information about the Microsoft Tun
For more information and command-line examples, see [mst-cli command-line tool for Microsoft Tunnel](ref-file-commands#mst-cli-command-line-tool-for-microsoft-tunnel-gateway).
+### Run diagnostics on the Tunnel server
+
+Use `mst-cli diagnose` on an installed Tunnel server to check known prerequisites and configuration requirements, including those required for logging. Run diagnostics when expected logs are missing or a log upload fails.
+
+To run diagnostics and review the logging checks:
+
+1. Connect to the Linux server that hosts the affected Tunnel Gateway.
+2. Run the following command on the server:
+
+ ```bash
+ mst-cli diagnose
+ ```
+3. Review the logging results. Each logging check reports a pass or fail status and the expected result. The output also includes fixes for some common failures. Checks and corrective steps vary with the server's operating system and installation.
+4. For a failed check, compare the result with the expected result and follow the corrective guidance provided for your configuration. Run `mst-cli diagnose` again after making changes.
+5. View the Tunnel logs to check whether the expected entries are present. If you're investigating an upload failure, follow Troubleshoot missing logs or failed uploads to verify collection and upload separately.
+
+The command creates a report named `diagnosticReport.txt` in `/etc/mstunnel/diagnostic`. You can share this report with Microsoft support for further analysis.
+
+Diagnostics identify known unmet prerequisites. They don't identify or interpret every operating system customization or hardening setting that might affect Tunnel. A pass result applies to the check performed; it doesn't confirm that every customization is compatible or that logs were uploaded successfully.
+
## View Microsoft Tunnel logs
Microsoft Tunnel logs information to the Linux server logs in the *syslog* format. To view log entries, use the **journalctl -t** command followed by one or more tags that are specific to Microsoft Tunnel entries:
@@ -285,6 +307,16 @@ After you reproduce an issue during verbose log collection phase, Microsoft can
The *ocserv-access* logs aren't collected or uploaded.
+### Troubleshoot missing logs or failed uploads
+
+If expected Tunnel logs are missing or **Send logs** reports a failed upload, use the following steps:
+
+1. Run diagnostics on the affected Tunnel server. Review the logging checks and address failures using the guidance in the output.
+2. Check the [logging prerequisites](prerequisites#validate-logging-prerequisites), including access to the required upload endpoints. If the server uses a customized or hardened operating system, review whether those changes affect the requirements identified by diagnostics.
+3. View the local Tunnel logs. Local log entries and passing diagnostic checks don't confirm that logs reached Microsoft.
+4. After addressing the identified failures, repeat the Send logs procedure. Reproduce the issue during the eight-hour verbose collection period, and check the status of each log set in the admin center. An **in progress** status isn't a completed upload. The second log set is collected and uploaded after the eight-hour period.
+5. If collection or upload still fails, contact Microsoft support. Include the diagnostic report, the failed checks, and the collection times and statuses shown in the admin center.
+
## Known issues
The following are known issues for Microsoft Tunnel.