Skip to content

Hyperlint Automation: Meta Description Fixes #20648

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Hyperlint Automation: Meta Description Fixes #20648

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 1 addition & 19 deletions ...e-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,22 +1,4 @@
---
pcx_content_type: reference
title: Parameters
description: Explore parameters for deploying Cloudflare WARP via MDM, including organization setup and device registration for Zero Trust.
sidebar:
order: 2

---

import { GlossaryTooltip } from "~/components"

Each client supports the following set of parameters as part of their deployment, regardless of the deployment mechanism.

:::note

Most of the parameters listed below are also configurable in Zero Trust under **Settings** > **Devices**. In the event of conflicting settings, the WARP client will always give precedence to settings on the local device (for example, in your `mdm.xml` or `com.cloudflare.warp.plist` files).

:::

---\npcx_content_type: reference\ntitle: Parameters\ndescription: Discover parameters for deploying Cloudflare WARP via MDM, including organization setup, device registration, and DNS policy enforcement for Zero Trust.\nsidebar:\n order: 2\n\n---\n\nimport { GlossaryTooltip } from "~/components"\n\nEach client supports the following set of parameters as part of their deployment, regardless of the deployment mechanism.\n\n:::note\n\nMost of the parameters listed below are also configurable in Zero Trust under **Settings** > **Devices**. In the event of conflicting settings, the WARP client will always give precedence to settings on the local device (for example, in your `mdm.xml` or `com.cloudflare.warp.plist` files).\n\n:::\n
## Required for full Cloudflare Zero Trust features

For the majority of Cloudflare Zero Trust features to work, you need to specify a team name. Examples of Cloudflare Zero Trust features which depend on the team name are [HTTP policies](/cloudflare-one/policies/gateway/http-policies/), [Browser Isolation](/cloudflare-one/policies/browser-isolation/), and [device posture](/cloudflare-one/identity/devices/).
Expand Down
Loading