diff --git a/src/content/docs/cloudflare-one/applications/configure-apps/self-hosted-public-app.mdx b/src/content/docs/cloudflare-one/applications/configure-apps/self-hosted-public-app.mdx
index d4f4861f129c654..e8bc31da56824ff 100644
--- a/src/content/docs/cloudflare-one/applications/configure-apps/self-hosted-public-app.mdx
+++ b/src/content/docs/cloudflare-one/applications/configure-apps/self-hosted-public-app.mdx
@@ -6,7 +6,7 @@ sidebar:
   label: Self-hosted public application
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 You can securely publish internal tools and applications by adding Cloudflare Access as an authentication layer between the end user and your origin server.
 
@@ -37,4 +37,7 @@ Users can now connect to your self-hosted application after authenticating with
 
 ## Product compatibility
 
- <Render file="access/self-hosted-app/product-compatibility" product="cloudflare-one" />
\ No newline at end of file
+<Render
+	file="access/self-hosted-app/product-compatibility"
+	product="cloudflare-one"
+/>
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains.mdx
index 0b805c0465a5495..252cdc307d5b105 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains.mdx
@@ -48,3 +48,8 @@ Local Domain Fallback configuration only impacts where DNS requests get resolved
 4. Find the domain in the list and select **Delete**.
 
 The domain will no longer be excluded from Gateway DNS policies, effective immediately.
+
+## Related resources
+
+- [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/) - Control which traffic goes through WARP by including or excluding specific IPs or domains.
+- [WARP with firewall](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/) - Learn which IPs, domains, and ports to allow so users can deploy and connect WARP successfully behind a firewall.
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels.mdx
index 94e92a1eeb8a408..a56f5c9b76f02dd 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels.mdx
@@ -100,3 +100,8 @@ Removing default Split Tunnel entries may cause users to lose Internet connectiv
 <Render file="warp/client-notification-lag" product="cloudflare-one" />
 
 If you need to revert to the default Split Tunnel entries recommended by Cloudflare, select **Restore default entries**.
+
+## Related resources
+
+- [Local Domain Fallback](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/) - Resolve selected domains via local DNS instead of Cloudflare Gateway.
+- [WARP with firewall](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/) - Learn which IPs, domains, and ports to allow so users can deploy and connect WARP successfully behind a firewall.
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/index.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/index.mdx
index 0154482d0864044..705bddac9c0b11f 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/index.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/index.mdx
@@ -61,3 +61,7 @@ This mode is best suited for organizations that only want to enforce [WARP clien
 | DNS filtering | Network filtering | HTTP filtering | Features enabled                                                            |
 | ------------- | ----------------- | -------------- | --------------------------------------------------------------------------- |
 | No            | No                | No             | Device posture rules in [Access policies](/cloudflare-one/policies/access/) |
+
+## Related resources
+
+- [Connectivity status](/cloudflare-one/connections/connect-devices/warp/troubleshooting/connectivity-status/) - Learn about the status messages displayed by the WARP client during its connection process, and understand each stage as WARP establishes a secure tunnel to Cloudflare.
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-sessions.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-sessions.mdx
index 0f2d30684ce01fe..6024e3a5ef71ff7 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-sessions.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-sessions.mdx
@@ -58,3 +58,7 @@ If the user has an active browser session with the IdP, WARP will use the existi
 - **Only one user per device** — If a device is already registered with User A, User B will not be able to log in on that device through the re-authentication flow. To switch the device registration to a different user, User A must first log out from Zero Trust (if [Allow device to leave organization](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#allow-device-to-leave-organization) is enabled), or an admin can revoke the registration from **My Team** > **Devices**. User B can then properly [enroll](/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment/).
 - **Active connections are not terminated** — Active sessions such as SSH and RDP will remain connected beyond the timeout limit.
 - **Binding Cookie is not supported** - WARP authentication will not work for Access applications that have the [Binding Cookie](/cloudflare-one/identity/authorization-cookie/#binding-cookie) enabled.
+
+## Related resources
+
+- [Connectivity status](/cloudflare-one/connections/connect-devices/warp/troubleshooting/connectivity-status/) - Learn about the status messages displayed by the WARP client during its connection process, and understand each stage as WARP establishes a secure tunnel to Cloudflare.
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/captive-portals.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/captive-portals.mdx
index 4faca174e111de3..02853171b9f4e74 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/captive-portals.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/captive-portals.mdx
@@ -5,7 +5,7 @@ sidebar:
   order: 3
 ---
 
-import { Details, Badge } from "~/components";
+import { Details, Badge, Render } from "~/components";
 
 Captive portals are used by public Wi-Fi networks (such as airports, coffee shops, and hotels) to make a user agree to their Terms of Service or provide payment before allowing access to the Internet. When a user connects to the Wi-Fi, the captive portal blocks all HTTPS traffic until the user completes a captive portal login flow in their browser. This prevents the WARP client from connecting to Cloudflare. At the same time, WARP creates [firewall rules](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#ip-traffic) on the device to send all traffic to Cloudflare. The user is therefore unable to access the captive portal login screen unless they temporarily disable WARP.
 
@@ -38,7 +38,7 @@ If WARP cannot establish a connection to Cloudflare, it will:
 ## Limitations
 
 - Due to [how captive portal detection works](#how-captive-portal-detection-works), it may be possible for an employee to spoof a captive portal in order to turn off WARP.
-- Some captive portals, particularly those on airlines, may be slow to respond and exceed the captive portal detection timeout. Users will likely see a [CF_CAPTIVE_PORTAL_TIMED_OUT](/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/#cf_captive_portal_timed_out) error when they try to connect.
+- Some captive portals, particularly those on airlines, may be slow to respond and exceed the captive portal detection timeout. Users will likely see a [CF_CAPTIVE_PORTAL_TIMED_OUT](/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/#cf_captive_portal_timed_out) error when they try to connect. For context on the steps leading up to these errors, refer to [Connectivity status](/cloudflare-one/connections/connect-devices/warp/troubleshooting/connectivity-status/).
 - WARP may not be able to detect multi-stage captive portals, which redirect the user to different networks during the login process. Users will need to manually turn off WARP to get through the captive portal.
 - Some public Wi-Fi networks are incompatible with running WARP:
 
@@ -51,12 +51,12 @@ If WARP cannot establish a connection to Cloudflare, it will:
 
 | [WARP modes](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-modes/) | [Zero Trust plans](https://www.cloudflare.com/teams-pricing/) |
 | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------- |
-|  All modes   | All plans                                                     |
+| All modes                                                                                 | All plans                                                     |
 
 | System   | Availability | Minimum WARP version |
 | -------- | ------------ | -------------------- |
-| Windows  | ✅           | 2025.4.589.1        |
-| macOS    | ✅           | 2025.4.589.1        |
+| Windows  | ✅           | 2025.4.589.1         |
+| macOS    | ✅           | 2025.4.589.1         |
 | Linux    | ❌           |                      |
 | iOS      | ❌           |                      |
 | Android  | ❌           |                      |
@@ -73,4 +73,8 @@ To get captive portal logs:
 3. Select **Collect Captive Portal Diag**.
 4. The WARP client will ask if the device is connected (or attempting to connect) to the Wi-Fi network that is causing issues. Select **Yes** to confirm.
 
-Once the diagnostic finishes running, WARP will place a `warp-captive-portal-diag-<date>-<time>.zip` file on the user's desktop. The end user can now share this file with their IT administrator.
\ No newline at end of file
+Once the diagnostic finishes running, WARP will place a `warp-captive-portal-diag-<date>-<time>.zip` file on the user's desktop. The end user can now share this file with their IT administrator.
+
+## Related resources
+
+- [Connectivity status](/cloudflare-one/connections/connect-devices/warp/troubleshooting/connectivity-status/) - Learn about the status messages displayed by the WARP client during its connection process, and understand each stage as WARP establishes a secure tunnel to Cloudflare.
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/firewall.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/firewall.mdx
index 84d4a85200473ef..caf4cd900393507 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/firewall.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/firewall.mdx
@@ -153,3 +153,8 @@ To use the network connectivity tests built into the WARP GUI, you will need to
 
 - Windows: `C:\Program Files\Cloudflare\Cloudflare WARP\Cloudflare WARP.exe`
 - macOS: `/Applications/Cloudflare WARP.app`
+
+## Related resources
+
+- [Local Domain Fallback](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/) - Resolve selected domains via local DNS instead of Cloudflare Gateway.
+- [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/) - Control which traffic goes through WARP by including or excluding specific IPs or domains.
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment.mdx
index f6b2bd89a7a7541..6e141b1e697ceb0 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment.mdx
@@ -12,6 +12,7 @@ If you plan to direct your users to manually download and configure the WARP cli
 ## Prerequisites
 
 - [Set device enrollment permissions](/cloudflare-one/connections/connect-devices/warp/deployment/device-enrollment/) to specify which users can connect.
+- <Render file="warp/connectivity-status-check" />
 
 ## Windows, macOS, and Linux
 
@@ -89,9 +90,9 @@ The device is now protected by your organization's Zero Trust policies.
 | Windows  | ❌           |                      |
 | macOS    | ❌           |                      |
 | Linux    | ❌           |                      |
-| iOS      | ✅           | 1.10                  |
-| Android  | ✅           | 2.4                   |
-| ChromeOS | ✅           | 2.4                   |
+| iOS      | ✅           | 1.10                 |
+| Android  | ✅           | 2.4                  |
+| ChromeOS | ✅           | 2.4                  |
 
 </Details>
 
@@ -104,9 +105,9 @@ The WARP client supports URLs accessed through a direct link or with a URL handl
 To generate a URL for device enrollment:
 
 1. Copy the following link, replacing `<your-team-name>` with your Zero Trust <GlossaryTooltip term="team name">team name</GlossaryTooltip>:
-		```txt
-		cf1app://oneapp.cloudflare.com/team?name=<your-team-name>
-		```
+   `txt
+cf1app://oneapp.cloudflare.com/team?name=<your-team-name>
+`
 2. (Optional) Use any QR code generator to embed the link in a QR code.
 3. Distribute the link or QR code to users.
 
@@ -114,35 +115,35 @@ To generate a URL for device enrollment:
 
 To enroll a device using a login URL:
 
-1. [Download](/cloudflare-one/connections/connect-devices/warp/download-warp/) and install the Cloudflare One Agent app.
-2. Go to the [login URL](#generate-a-login-url) provided by your account administrator. To use a QR code, open the QR scanner app on your device and scan the QR code.
+1.  [Download](/cloudflare-one/connections/connect-devices/warp/download-warp/) and install the Cloudflare One Agent app.
+2.  Go to the [login URL](#generate-a-login-url) provided by your account administrator. To use a QR code, open the QR scanner app on your device and scan the QR code.
 
-		The Cloudflare One Agent app will open and start the onboarding flow.
+        The Cloudflare One Agent app will open and start the onboarding flow.
 
-		:::note
-		If the device is already enrolled in the account associated with this URL, Cloudflare One agent will bypass onboarding and show the **Connected** switch.
-		:::
+        :::note
+        If the device is already enrolled in the account associated with this URL, Cloudflare One agent will bypass onboarding and show the **Connected** switch.
+        :::
 
-3. To complete the onboarding flow:
+3.  To complete the onboarding flow:
 
-		a. Review the privacy policy and select **Accept**.
+        a. Review the privacy policy and select **Accept**.
 
     b. On the **Enter team name** screen, confirm that the pre-populated <GlossaryTooltip term="team name">team name</GlossaryTooltip> matches your organization.
 
-		:::note[`Already Authenticated` error]
-		If Cloudflare One Agent is logged in using another team name, you must first log out of that account. Go to **Settings** > **Account** to log out, and then retry the QR code or login link.
-		:::
+        :::note[`Already Authenticated` error]
+        If Cloudflare One Agent is logged in using another team name, you must first log out of that account. Go to **Settings** > **Account** to log out, and then retry the QR code or login link.
+        :::
 
     c. Complete the authentication steps required by your organization.
 
- 		d. After authenticating, select **Install VPN Profile**.
+        d. After authenticating, select **Install VPN Profile**.
 
-		e. In the **Connection request** popup window, select **OK**.
+        e. In the **Connection request** popup window, select **OK**.
 
-4. If you did not enable [auto-connect](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#auto-connect), manually turn on the switch to **Connected**.
+4.  If you did not enable [auto-connect](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#auto-connect), manually turn on the switch to **Connected**.
 
 The device is now protected by your organization's Zero Trust policies.
 
 ## Virtual machines
 
-By default, virtual machines (VMs) are subject to the WARP client settings of the host. If you want to deploy a separate instance of WARP in a VM, you must configure the VM to operate in bridged networking mode.
\ No newline at end of file
+By default, virtual machines (VMs) are subject to the WARP client settings of the host. If you want to deploy a separate instance of WARP in a VM, you must configure the VM to operate in bridged networking mode.
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/index.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/index.mdx
index 09e8a7f817447d7..a37fb62f525a2db 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/index.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/index.mdx
@@ -19,7 +19,8 @@ This page provides generic instructions for an automated deployment. If you want
 
 ## Prerequisites
 
-Visit the [Download page](/cloudflare-one/connections/connect-devices/warp/download-warp/#windows) to review system requirements and download the installer for your operating system.
+- Refer to the [Download page](/cloudflare-one/connections/connect-devices/warp/download-warp/#windows) to review system requirements and download the installer for your operating system.
+- <Render file="warp/connectivity-status-check" />
 
 ## Windows
 
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/fleet.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/fleet.mdx
index 962a2e4285a6c9e..f4bbb9c09f13408 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/fleet.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/fleet.mdx
@@ -5,6 +5,8 @@ sidebar:
   order: 1
 ---
 
+import { Render } from "~/components";
+
 This guide covers how to deploy the Cloudflare WARP client using [Fleet](https://fleetdm.com/) device management software.
 
 ## macOS
@@ -21,8 +23,8 @@ This guide covers how to deploy the Cloudflare WARP client using [Fleet](https:/
 3. Select **OS settings** > **Custom settings**.
 4. Select **Add profile** and upload the custom `.mobileconfig`.
 5. Select the hosts which require Cloudflare WARP:
-		- **All hosts**: Deploys WARP to all hosts in the team.
-		- **Custom**: Deploys WARP to a subset of the hosts in the team. Use [labels](https://fleetdm.com/guides/managing-labels-in-fleet#basic-article) to define the hosts that should be included or excluded.
+   - **All hosts**: Deploys WARP to all hosts in the team.
+   - **Custom**: Deploys WARP to a subset of the hosts in the team. Use [labels](https://fleetdm.com/guides/managing-labels-in-fleet#basic-article) to define the hosts that should be included or excluded.
 6. Select **Add profile**.
 
 The defined hosts will immediately receive the deployment profile, but WARP is not yet installed.
@@ -48,7 +50,7 @@ To deploy the uploaded `.pkg` file to your hosts:
 3. Go to **Software** and search for `Cloudflare`.
 4. Select **Actions** > **Install**.
 
-Installation will happen automatically when the host comes online. To deploy with REST API or GitOps, refer to the [Fleet documentation](https://fleetdm.com/guides/deploy-software-packages).
+Installation will happen automatically when the host comes online. To deploy with REST API or GitOps, refer to the [Fleet documentation](https://fleetdm.com/guides/deploy-software-packages). <Render file="warp/connectivity-status-check" />
 
 ### 6. Uninstall WARP with Fleet
 
@@ -106,7 +108,7 @@ To deploy the uploaded `.pkg` file to your hosts:
 3. Go to **Software** and search for `Cloudflare`.
 4. Select **Actions** > **Install**.
 
-Installation will happen automatically when the host comes online. To deploy with REST API or GitOps, refer to the [Fleet documentation](https://fleetdm.com/guides/deploy-software-packages).
+Installation will happen automatically when the host comes online. To deploy with REST API or GitOps, refer to the [Fleet documentation](https://fleetdm.com/guides/deploy-software-packages). <Render file="warp/connectivity-status-check" />
 
 ### 4. Uninstall WARP with Fleet
 
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/hexnode.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/hexnode.mdx
index 008831b031bec6c..b5dde57388c2ff1 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/hexnode.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/hexnode.mdx
@@ -6,6 +6,8 @@ sidebar:
 description: Deploy Cloudflare WARP with Hexnode MDM - Step-by-step guide for Windows, macOS, iOS, and Android.
 ---
 
+import { Render } from "~/components";
+
 ## Windows
 
 1. Create a script file with `.bat`, `.cmd`, and `.ps1` file formats to download, install and configure the Cloudflare WARP client Windows application on the device. Listed below is a sample script with all of the configurable parameters:
@@ -42,17 +44,19 @@ description: Deploy Cloudflare WARP with Hexnode MDM - Step-by-step guide for Wi
 
 5. Select **Actions** > **Execute Custom Script**.
 
-6. Choose the script file source as *Upload file*, then upload the script file.
+6. Choose the script file source as _Upload file_, then upload the script file.
 
 7. Select **Execute**.
 
+<Render file="warp/connectivity-status-check" />
+
 ## macOS
 
 1. [Download](/cloudflare-one/connections/connect-devices/warp/download-warp/#macos) the Cloudflare WARP client for macOS.
 
 2. On your Hexnode console, go to **Apps** > **Add Apps** > **Enterprise App**.
 
-3. Select *macOS* as the app platform.
+3. Select _macOS_ as the app platform.
 
 4. Add an app name, category and description.
 
@@ -90,17 +94,19 @@ description: Deploy Cloudflare WARP with Hexnode MDM - Step-by-step guide for Wi
 
 11. Go to **App Configurations** > **Add new configuration**.
 
-12. Select the *WARP client* app and upload the XML file from Step 6.
+12. Select the _WARP client_ app and upload the XML file from Step 6.
 
 13. Now go to **Policy Targets** and associate the policy with the target entities.
 
 This will push the app along with the configurations to the selected devices.
 
+<Render file="warp/connectivity-status-check" />
+
 ## iOS
 
 1. On your Hexnode console, go to **Apps** > **Add Apps** > **Store App**.
 
-2. Select *iOS* as the app platform.
+2. Select _iOS_ as the app platform.
 
 3. Search for [**Cloudflare One Agent**](https://apps.apple.com/us/app/cloudflare-one-agent/id6443476492) and **Add** the app.
 
@@ -122,6 +128,7 @@ This will push the app along with the configurations to the selected devices.
    ```
 
 5. Upload the app configurations in Hexnode:
+
    1. On your Hexnode console, go to the **Apps** tab.
    2. Find the Cloudflare One Agent app and select its name.
    3. Select the settings icon and choose **App Configuration**.
@@ -137,6 +144,8 @@ This will push the app along with the configurations to the selected devices.
 
 This will push the app along with the configurations to the selected devices.
 
+<Render file="warp/connectivity-status-check" />
+
 ## Android
 
 1. On your Hexnode console, go to **Apps** > **Add Apps** > **Managed Google Apps**.
@@ -149,3 +158,5 @@ This will push the app along with the configurations to the selected devices.
 8. Save the policy.
 
 This will push the app along with the configurations to the selected devices.
+
+<Render file="warp/connectivity-status-check" />
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/index.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/index.mdx
index 4b05376c69451ef..84067968197eea6 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/index.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/index.mdx
@@ -6,10 +6,9 @@ sidebar:
 head:
   - tag: title
     content: Deploy WARP with Technology Partners
-
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing } from "~/components";
 
 Cloudflare Zero Trust integrates with [Cloudflare Technology Partner](https://www.cloudflare.com/partners/technology-partners/) tools to help you deploy the WARP client to bigger fleets of devices. Thanks to these collaborations, you can distribute the WARP client application to end-user devices and remotely set up advanced configurations in real time.
 
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/intune.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/intune.mdx
index 38adeb90f719da9..2ebfe30fd0ec240 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/intune.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/intune.mdx
@@ -3,9 +3,10 @@ pcx_content_type: how-to
 title: Intune
 sidebar:
   order: 2
-
 ---
 
+import { Render } from "~/components";
+
 This guide covers how to deploy the Cloudflare WARP client using Microsoft Intune.
 
 ## Windows
@@ -17,13 +18,13 @@ To deploy WARP on Windows using Intune:
 1. [Download the `Cloudflare_WARP_<VERSION>.msi` installer](/cloudflare-one/connections/connect-devices/warp/download-warp/#windows).
 2. Log in to your Microsoft Intune account.
 3. Go to **Apps** > **All Apps** > **Add**.
-4. In **App type**, select *Line-of-business app* from the drop-down menu. Select **Select**.
+4. In **App type**, select _Line-of-business app_ from the drop-down menu. Select **Select**.
 5. Select **Select app package file** and upload the `Cloudflare_WARP_<VERSION>.msi` installer you downloaded previously.
 6. Select **OK**.
 7. In the **Name** field, we recommend entering the version number of the package being uploaded.
 8. In the **Publisher** field, we recommend entering `Cloudflare, Inc`.
-9. In the **Command-line arguments** field, enter a valid installation command. 
-	 For example:
+9. In the **Command-line arguments** field, enter a valid installation command.
+   For example:
    ```txt
    /qn ORGANIZATION="your-team-name" SUPPORT_URL="http://support.example.com"
    ```
@@ -40,68 +41,69 @@ You can use Intune to update [MDM parameters](/cloudflare-one/connections/connec
 
 To push a new `mdm.xml` file using Intune:
 
-1. Log in to your Microsoft Intune account.
-2. Go to **Devices** > **Scripts and remediations**.
-3. Select the **Platform scripts** tab and select **Add**.
-4. Select **Windows 10 and later**.
-5. Enter a name for the script (for example, `Deploy Cloudflare mdm.xml`).
-6. In **PowerShell script**, upload the following `.ps1` file. Be sure to modify the XML content with your desired [parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/).
-
-		```powershell title="mdm-template.ps1"
-		# Define the path to the file
-		$filePath = "C:\ProgramData\Cloudflare\mdm.xml"
-
-		# Create the XML content as a string
-		$xmlContent = @"
-		<dict>
-			<key>multi_user</key>
-			<true/>
-			<key>pre_login</key>
-			<dict>
-				<key>organization</key>
-				<string>mycompany</string>
-				<key>auth_client_id</key>
-				<string>88bf3b6d86161464f6509f7219099e57.access</string>
-				<key>auth_client_secret</key>
-				<string>bdd31cbc4dec990953e39163fbbb194c93313ca9f0a6e420346af9d326b1d2a5</string>
-			</dict>
-			<key>configs</key>
-			<array>
-				<dict>
-					<key>organization</key>
-					<string>mycompany</string>
-					<key>display_name</key>
-					<string>Production environment</string>
-				</dict>
-				<dict>
-					<key>organization</key>
-					<string>test-org</string>
-					<key>display_name</key>
-					<string>Test environment</string>
-				</dict>
-			</array>
-		</dict>
-		"@
-
-		# Ensure the directory exists
-		$directory = Split-Path $filePath -parent
-		if (-not (Test-Path $directory)) {
-			New-Item -ItemType Directory -Path $directory | Out-Null
-		}
-
-		# Write the XML content to the file
-		try {
-			$xmlContent | Out-File -Encoding UTF8 -FilePath $filePath
-			Write-Host "mdm.xml file created successfully at: $filePath"
-		}
-		catch {
-			Write-Error "Failed to create mdm.xml file: $_"
-		}
-		```
-7. In **Assignments**, select the Windows devices that should receive the new `mdm.xml` file.
-8. To deploy the script, select **Add**.
-
-Intune will now execute the Powershell script on the target devices and overwrite the previous `mdm.xml` file. Once the new `mdm.xml` file is created, WARP will immediately start using the new configuration.
+1.  Log in to your Microsoft Intune account.
+2.  Go to **Devices** > **Scripts and remediations**.
+3.  Select the **Platform scripts** tab and select **Add**.
+4.  Select **Windows 10 and later**.
+5.  Enter a name for the script (for example, `Deploy Cloudflare mdm.xml`).
+6.  In **PowerShell script**, upload the following `.ps1` file. Be sure to modify the XML content with your desired [parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/).
+
+        ```powershell title="mdm-template.ps1"
+        # Define the path to the file
+        $filePath = "C:\ProgramData\Cloudflare\mdm.xml"
+
+        # Create the XML content as a string
+        $xmlContent = @"
+        <dict>
+        	<key>multi_user</key>
+        	<true/>
+        	<key>pre_login</key>
+        	<dict>
+        		<key>organization</key>
+        		<string>mycompany</string>
+        		<key>auth_client_id</key>
+        		<string>88bf3b6d86161464f6509f7219099e57.access</string>
+        		<key>auth_client_secret</key>
+        		<string>bdd31cbc4dec990953e39163fbbb194c93313ca9f0a6e420346af9d326b1d2a5</string>
+        	</dict>
+        	<key>configs</key>
+        	<array>
+        		<dict>
+        			<key>organization</key>
+        			<string>mycompany</string>
+        			<key>display_name</key>
+        			<string>Production environment</string>
+        		</dict>
+        		<dict>
+        			<key>organization</key>
+        			<string>test-org</string>
+        			<key>display_name</key>
+        			<string>Test environment</string>
+        		</dict>
+        	</array>
+        </dict>
+        "@
+
+        # Ensure the directory exists
+        $directory = Split-Path $filePath -parent
+        if (-not (Test-Path $directory)) {
+        	New-Item -ItemType Directory -Path $directory | Out-Null
+        }
+
+        # Write the XML content to the file
+        try {
+        	$xmlContent | Out-File -Encoding UTF8 -FilePath $filePath
+        	Write-Host "mdm.xml file created successfully at: $filePath"
+        }
+        catch {
+        	Write-Error "Failed to create mdm.xml file: $_"
+        }
+        ```
+
+7.  In **Assignments**, select the Windows devices that should receive the new `mdm.xml` file.
+8.  To deploy the script, select **Add**.
+
+Intune will now execute the Powershell script on the target devices and overwrite the previous `mdm.xml` file. Once the new `mdm.xml` file is created, WARP will immediately start using the new configuration. <Render file="warp/connectivity-status-check" />
 
 If you prefer to use Intune's Win32 App tool to run the Powershell script, refer to the [Intune documentation](https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-app-management).
 
@@ -122,6 +124,7 @@ Per-app VPN is supported on Cloudflare One Agent version `1.8` or greater for iO
 :::
 
 Before proceeding with per-app VPN configuration, you must make sure Auto connect is disabled for your organization in the Cloudflare dashboard. To disable Auto connect:
+
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Select **Zero Trust** > **Settings** > **WARP Client**.
 3. Go to **Device Settings** > select your profile and select **Edit** > toggle **Auto Connect** off.
@@ -134,14 +137,14 @@ To configure per-app VPN:
 4. Give the configuration a name, and an optional description, if you desire, then select **Next**.
 5. Select _Custom VPN_ from the **Connection Type** dropdown menu.
 6. Expand the **Base VPN** section.
-	- Give the VPN connection a name.
-	- Enter "1.1.1.1" as the VPN server address (this value is not actually used.)
-	- Set _Username and password_ as the **Authentication method**.
-	- Enter "com.cloudflare.cloudflareoneagent" as the VPN identifier.
-	- Enter any Key and Value into the custom VPN attributes (Cloudflare One does not use these but Intunes requires at least one entry.)
+   - Give the VPN connection a name.
+   - Enter "1.1.1.1" as the VPN server address (this value is not actually used.)
+   - Set _Username and password_ as the **Authentication method**.
+   - Enter "com.cloudflare.cloudflareoneagent" as the VPN identifier.
+   - Enter any Key and Value into the custom VPN attributes (Cloudflare One does not use these but Intunes requires at least one entry.)
 7. Expand the **Automatic VPN** section.
-	- Select _Per-app VPN_ as the **Type of automatic VPN**.
-	- Select _packet-tunnel_ as the **Provider Type**. Select **Next**.
+   - Select _Per-app VPN_ as the **Type of automatic VPN**.
+   - Select _packet-tunnel_ as the **Provider Type**. Select **Next**.
 8. Add any Groups, Users, or Devices to which you want to distribute this configuration and select **Next**.
 9. Review the settings and select **Create**.
 10. Go to **Apps** > **iOS/iPadOS Apps** and select **+ Add**.
@@ -183,59 +186,59 @@ To deploy WARP on Android devices:
 6. Select _Managed devices_.
 7. In **Name**, enter `Cloudflare One Agent`.
 8. For **Platform**, select _Android Enterprise_.
-9. Choose your desired  **Profile Type**.
+9. Choose your desired **Profile Type**.
 10. For **Targeted app**, select **Cloudflare One Agent**. Select **Next**.
 11. For **Configuration settings format**, select _Enter JSON data_. Enter your desired [deployment parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/) in the `managedProperty` field. For example:
 
-	```json
-	{
-		"kind": "androidenterprise#managedConfiguration",
-		"productId": "app:com.cloudflare.cloudflareoneagent",
-		"managedProperty": [
-			{
-				"key": "app_config_bundle_list",
-				"valueBundleArray": [
-					{
-						"managedProperty": [
-							{
-								"key": "organization",
-								"valueString": "your-team-name"
-							},
-							{
-								"key": "display_name",
-								"valueString": "Production environment"
-							},
-							{
-								"key": "service_mode",
-								"valueString": "warp"
-							},
-							{
-								"key": "onboarding",
-								"valueBool": false
-							},
-							{
-								"key": "support_url",
-								"valueString": "https://support.example.com/"
-							}
-						]
-					},
-					{
-						"managedProperty": [
-							{
-								"key": "organization",
-								"valueString": "test-org"
-							},
-							{
-								"key": "display_name",
-								"valueString": "Test environment"
-							}
-						]
-					}
-				]
-			}
-		]
-	}
-	```
+    ```json
+    {
+    	"kind": "androidenterprise#managedConfiguration",
+    	"productId": "app:com.cloudflare.cloudflareoneagent",
+    	"managedProperty": [
+    		{
+    			"key": "app_config_bundle_list",
+    			"valueBundleArray": [
+    				{
+    					"managedProperty": [
+    						{
+    							"key": "organization",
+    							"valueString": "your-team-name"
+    						},
+    						{
+    							"key": "display_name",
+    							"valueString": "Production environment"
+    						},
+    						{
+    							"key": "service_mode",
+    							"valueString": "warp"
+    						},
+    						{
+    							"key": "onboarding",
+    							"valueBool": false
+    						},
+    						{
+    							"key": "support_url",
+    							"valueString": "https://support.example.com/"
+    						}
+    					]
+    				},
+    				{
+    					"managedProperty": [
+    						{
+    							"key": "organization",
+    							"valueString": "test-org"
+    						},
+    						{
+    							"key": "display_name",
+    							"valueString": "Test environment"
+    						}
+    					]
+    				}
+    			]
+    		}
+    	]
+    }
+    ```
 
     Alternatively, if you do not want to copy and paste the JSON data, you can change **Configuration settings format** to _Use configuration designer_ and manually configure each deployment parameter.
 
@@ -272,105 +275,109 @@ To configure your Cloudflare One Agent app policy:
 
 1. In the Microsoft Intune admin center, go to **Apps** > **App configuration policies** > select **Add** > **Managed Devices**.
 2. Fill out the basic details of your configuration policy:
-	1. Enter the **Name** of the profile. (For example: Cloudflare One Agent - configuration policy)
-	2. Select the Platform as **Android Enterprise**.
-	3. Select the desired **Profile Type**. (For example: Personally-Owned Work Profile Only)
-	4. Select **Cloudflare One Agent** as the **Targeted app**.
-	5. Select **Next**.
+
+   1. Enter the **Name** of the profile. (For example: Cloudflare One Agent - configuration policy)
+   2. Select the Platform as **Android Enterprise**.
+   3. Select the desired **Profile Type**. (For example: Personally-Owned Work Profile Only)
+   4. Select **Cloudflare One Agent** as the **Targeted app**.
+   5. Select **Next**.
 
 3. Fill out the settings for the configuration policy.
-	1. Select **Configuration setting format** as **Enter JSON data**.
-	2. Enter your desired deployment parameters in the `managedProperty` field. For example:
-
-		```sh
-			{
-			"kind": "androidenterprise#managedConfiguration",
-			"productId": "app:com.cloudflare.cloudflareoneagent",
-			"managedProperty": [
-				{
-					"key": "app_config_bundle_list",
-					"valueBundleArray": [
-						{
-							"managedProperty": [
-								{
-									"key": "organization",
-									"valueString": "${ORGANIZATION_NAME-1}"
-								},
-								{
-									"key": "service_mode",
-									"valueString": "warp"
-								},
-								{
-									"key": "onboarding",
-									"valueBool": true
-								},
-								{
-									"key": "display_name",
-									"valueString": "${UNIQUE_DISPLAY_NAME-1}"
-								},
-								{
-									"key": "warp_tunnel_protocol",
-									"valueString": "MASQUE"
-								},
-								{
-									"key": "tunneled_apps",
-									"valueBundleArray" :[
-										{
-											"managedProperty": [
-												{
-													"key": "app_identifier",
-													"valueString": "com.android.chrome" # Application package name/unique bundle identifier for the Chrome app browser
-												},
-												{
-													"key": "is_browser",
-													"valueBool": true
-												}
-											]
-										},
-										{
-											"managedProperty": [
-												{
-													"key": "app_identifier",
-													"valueString": "com.google.android.gm" # Application package name/unique bundle identifier for the Gmail app
-												},
-												{
-													"key": "is_browser",
-													"valueBool": false # Default value is false, if a user does not define `is_browser` property our app would not treat `app_identifier` package name as a browser.
-												}
-											]
-										}
-									]
-								}
-							]
-						},
-						{
-							"managedProperty": [
-								{
-									"key": "organization",
-									"valueString": "${ORGANIZATION_NAME-1}"
-								},
-								{
-									"key": "service_mode",
-									"valueString": "warp"
-								},
-								{
-									"key": "display_name",
-									"valueString": "${UNIQUE_DISPLAY_NAME-2}"
-								},
-								{
-									"key": "warp_tunnel_protocol",
-									"valueString": "wireguard"
-								}
-							]
-						}
-					]
-				}
-			]
-		}
-		```
-		Refer to [Per-app VPN parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/#per-app-vpn-parameters-android) to learn more about the MDM parameters introduced to support the per-app VPN for Android devices.
-
-	3. After you have configured the deployment parameters, click **Next**.
+
+   1. Select **Configuration setting format** as **Enter JSON data**.
+   2. Enter your desired deployment parameters in the `managedProperty` field. For example:
+
+      ```sh
+      	{
+      	"kind": "androidenterprise#managedConfiguration",
+      	"productId": "app:com.cloudflare.cloudflareoneagent",
+      	"managedProperty": [
+      		{
+      			"key": "app_config_bundle_list",
+      			"valueBundleArray": [
+      				{
+      					"managedProperty": [
+      						{
+      							"key": "organization",
+      							"valueString": "${ORGANIZATION_NAME-1}"
+      						},
+      						{
+      							"key": "service_mode",
+      							"valueString": "warp"
+      						},
+      						{
+      							"key": "onboarding",
+      							"valueBool": true
+      						},
+      						{
+      							"key": "display_name",
+      							"valueString": "${UNIQUE_DISPLAY_NAME-1}"
+      						},
+      						{
+      							"key": "warp_tunnel_protocol",
+      							"valueString": "MASQUE"
+      						},
+      						{
+      							"key": "tunneled_apps",
+      							"valueBundleArray" :[
+      								{
+      									"managedProperty": [
+      										{
+      											"key": "app_identifier",
+      											"valueString": "com.android.chrome" # Application package name/unique bundle identifier for the Chrome app browser
+      										},
+      										{
+      											"key": "is_browser",
+      											"valueBool": true
+      										}
+      									]
+      								},
+      								{
+      									"managedProperty": [
+      										{
+      											"key": "app_identifier",
+      											"valueString": "com.google.android.gm" # Application package name/unique bundle identifier for the Gmail app
+      										},
+      										{
+      											"key": "is_browser",
+      											"valueBool": false # Default value is false, if a user does not define `is_browser` property our app would not treat `app_identifier` package name as a browser.
+      										}
+      									]
+      								}
+      							]
+      						}
+      					]
+      				},
+      				{
+      					"managedProperty": [
+      						{
+      							"key": "organization",
+      							"valueString": "${ORGANIZATION_NAME-1}"
+      						},
+      						{
+      							"key": "service_mode",
+      							"valueString": "warp"
+      						},
+      						{
+      							"key": "display_name",
+      							"valueString": "${UNIQUE_DISPLAY_NAME-2}"
+      						},
+      						{
+      							"key": "warp_tunnel_protocol",
+      							"valueString": "wireguard"
+      						}
+      					]
+      				}
+      			]
+      		}
+      	]
+      }
+      ```
+
+      Refer to [Per-app VPN parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/#per-app-vpn-parameters-android) to learn more about the MDM parameters introduced to support the per-app VPN for Android devices.
+
+   3. After you have configured the deployment parameters, click **Next**.
+
 4. Fill out the assignments for the configuration policy. The admin can `Include` or `Exclude` specific groups of users to this policy. After you finish, select **Next**.
 5. Review the policy and select **Create**.
 
@@ -381,3 +388,5 @@ To configure your Cloudflare One Agent app policy:
 3. Add the groups of users in the assignments > select **Review + Save** > select **Save**.
 
 Intune will now deploy the Cloudflare One Agent application on a user's device with the managed parameters.
+
+<Render file="warp/connectivity-status-check" />
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/jamf.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/jamf.mdx
index a7a6e2248efb8ef..66f7b4e063d2bf9 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/jamf.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/jamf.mdx
@@ -5,16 +5,17 @@ sidebar:
   order: 2
 head: []
 description: Learn how to deploy Cloudflare WARP using Jamf.
-
 ---
 
+import { Render } from "~/components";
+
 ## macOS
 
 ### Prerequisites
 
-* [Download the `Cloudflare_WARP.pkg` file](/cloudflare-one/connections/connect-devices/warp/download-warp/#macos)
+- [Download the `Cloudflare_WARP.pkg` file](/cloudflare-one/connections/connect-devices/warp/download-warp/#macos)
 
-* [Create a `plist` file](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/#create-plist-file)
+- [Create a `plist` file](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/#create-plist-file)
 
 ### 1. Upload the WARP package
 
@@ -29,7 +30,7 @@ description: Learn how to deploy Cloudflare WARP using Jamf.
 
 1. Go to **Computers** > **Policies** > **+ New**.
 2. Enter a Display name such as `Cloudflare WARP Client`.\
-   For **Triggers**, our recommendation is to select *Startup*, *Login*, *Enrollment Complete* and *Recurring Check-in*, but you can select the value that works best for your organization.
+   For **Triggers**, our recommendation is to select _Startup_, _Login_, _Enrollment Complete_ and _Recurring Check-in_, but you can select the value that works best for your organization.
 3. Select **Packages** > **Configure**.
 4. Select **Add** next to the `Cloudflare_WARP_<VERSION>.pkg` file you previously uploaded.
 5. Select **Save**.
@@ -46,6 +47,8 @@ description: Learn how to deploy Cloudflare WARP using Jamf.
 
 Jamf is now configured to deploy the Cloudflare WARP client.
 
+<Render file="warp/connectivity-status-check" />
+
 ## iOS
 
 The Cloudflare One Agent allows for an automated install via Jamf.
@@ -58,15 +61,17 @@ Create an [XML file](/cloudflare-one/connections/connect-devices/warp/deployment
 
 1. Log in to your [Jamf](https://www.jamf.com/) account.
 2. Go to **Devices** > **Mobile Device Apps** > **+ New**.
-3. Select *App store app or apps purchased in volume* and select **Next**.
+3. Select _App store app or apps purchased in volume_ and select **Next**.
 4. In the search box, enter `Cloudflare One Agent`. Select **Next**.
-5. In the row for *Cloudflare One Agent by Cloudflare Inc.*, select **Add**. To verify that it is the correct application, view it in the [App Store](https://apps.apple.com/us/app/cloudflare-one-agent/id6443476492).
+5. In the row for _Cloudflare One Agent by Cloudflare Inc._, select **Add**. To verify that it is the correct application, view it in the [App Store](https://apps.apple.com/us/app/cloudflare-one-agent/id6443476492).
 6. Go to **Scope** and specify the devices in your organization that will receive the application.
 7. Go to **App Configuration** and copy/paste your XML file.
 8. Select **Save**.
 
 Jamf is now configured to deploy the Cloudflare One Agent.
 
+<Render file="warp/connectivity-status-check" />
+
 ### Per-app VPN
 
 :::note
@@ -74,6 +79,7 @@ Per-app VPN is supported on Cloudflare One Agent version `1.8` or greater for iO
 :::
 
 Before proceeding with per-app VPN configuration, you must make sure Auto connect is disabled for your organization in the Cloudflare dashboard. To disable Auto connect:
+
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Select **Zero Trust** > **Settings** > **WARP Client**.
 3. Go to **Device Settings** > select your profile and select **Edit** > toggle **Auto Connect** off.
@@ -84,9 +90,9 @@ To configure per-app VPN:
 2. Go to **Devices** > **Configuration Policies** > select **+ New**.
 3. Under **Options**, select **VPN**. Then:
    - Give the VPN a **Connection Name**.
-   - Select *Per-App VPN* from the **VPN Type** dropdown menu.
+   - Select _Per-App VPN_ from the **VPN Type** dropdown menu.
    - Check the box for **Automatically start Per-App VPN connection**.
-4. Under Per-App VPN Connection Type, set the **Connection Type** to _Custom SSL_ via the dropdown menu. Then, enter `com.cloudflare.cloudflareoneagent` as the **Identifier**,  `1.1.1.1` as the **Server**, and `com.cloudflare.cloudflareoneagent.worker` as the **Provider Bundle Identifier**.
+4. Under Per-App VPN Connection Type, set the **Connection Type** to _Custom SSL_ via the dropdown menu. Then, enter `com.cloudflare.cloudflareoneagent` as the **Identifier**, `1.1.1.1` as the **Server**, and `com.cloudflare.cloudflareoneagent.worker` as the **Provider Bundle Identifier**.
 5. Set the **Provider Type** to _Packet-Tunnel_ and select the checkboxes for **Include All Networks** and **Enable VPN on Demand**.
 6. Go to the **Scope** tab and add the devices that will use the Per-App VPN.
 7. Save the Configuration Profile.
@@ -118,4 +124,4 @@ Cloudflare One will continue to use a Safari window for initial authentication p
 
 :::note
 Cloudflare One cannot apply split tunnel setting for a per app VPN. Included or excluded domains can be added to the Configuration Profile under Safelisted Domains and Blocklisted Domains sections respectively.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/jumpcloud.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/jumpcloud.mdx
index f6ae273bf84143a..c5114dd39b34b25 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/jumpcloud.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/jumpcloud.mdx
@@ -5,9 +5,10 @@ sidebar:
   order: 2
 head: []
 description: Learn how to deploy Cloudflare WARP using JumpCloud.
-
 ---
 
+import { Render } from "~/components";
+
 ## Windows
 
 1. Log in to the [JumpCloud Admin Portal](https://console.jumpcloud.com).
@@ -32,8 +33,8 @@ description: Learn how to deploy Cloudflare WARP using JumpCloud.
 
 10. Select the device(s) you want to deploy the app to:
 
-    * **Single device**: Go to the **Devices** tab and select the target device.
-    * **Device group**: Go to the **Device Groups** tab and select the target device group.
+    - **Single device**: Go to the **Devices** tab and select the target device.
+    - **Device group**: Go to the **Device Groups** tab and select the target device group.
 
 11. Select **save**.
 
@@ -41,6 +42,8 @@ description: Learn how to deploy Cloudflare WARP using JumpCloud.
 
 Verify that Cloudflare WARP was installed by selecting the app and viewing the **Status** tab.
 
+<Render file="warp/connectivity-status-check" />
+
 ## macOS
 
 1. Log in to the [JumpCloud Admin Portal](https://console.jumpcloud.com).
@@ -57,9 +60,11 @@ Verify that Cloudflare WARP was installed by selecting the app and viewing the *
 
 6. Select the device(s) you want to deploy the app to:
 
-   * **Single device**: Go to the **Devices** tab and select the target device. To select all devices, select the checkbox next to **Type**.
-   * **Device group**: Go to the **Device Groups** tab and select the target device group. To select all device groups, select the checkbox next to **Type**.
+   - **Single device**: Go to the **Devices** tab and select the target device. To select all devices, select the checkbox next to **Type**.
+   - **Device group**: Go to the **Device Groups** tab and select the target device group. To select all device groups, select the checkbox next to **Type**.
 
 7. Select **save** to install the client.
 
 Verify that Cloudflare WARP was installed by selecting the app and viewing the **Status** tab.
+
+<Render file="warp/connectivity-status-check" />
diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/kandji.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/kandji.mdx
index 4d0b56ace0a903b..2bd8c88f03cebcc 100644
--- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/kandji.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/kandji.mdx
@@ -6,6 +6,8 @@ sidebar:
 description: Deploy Cloudflare WARP with Kandji on macOS using a custom configuration profile.
 ---
 
+import { Render } from "~/components";
+
 Kandji deploys Cloudflare WARP as a custom app. For an overview of how Kandji deploys custom apps, refer to their [knowledge base article](https://support.kandji.io/custom-apps-overview).
 
 ## macOS
@@ -56,6 +58,8 @@ For the simplest deployment, Kandji has created a downloadable configuration pro
 
 To verify that Cloudflare WARP was installed, select the app in the **Custom App** library and view its **Status** tab.
 
+<Render file="warp/connectivity-status-check" />
+
 ## Audit and Enforce Script
 
 The following audit script checks if the WARP client is installed and optionally enforces a minimum version number.
diff --git a/src/content/partials/cloudflare-one/warp/connectivity-status-check.mdx b/src/content/partials/cloudflare-one/warp/connectivity-status-check.mdx
new file mode 100644
index 000000000000000..ce57bb32700ddc8
--- /dev/null
+++ b/src/content/partials/cloudflare-one/warp/connectivity-status-check.mdx
@@ -0,0 +1,5 @@
+---
+{}
+---
+
+After deploying the WARP client, you can check its connection progress using the [Connectivity status](/cloudflare-one/connections/connect-devices/warp/troubleshooting/connectivity-status/) messages displayed in the WARP GUI.