[ZT] Deploy mdm.xml on macOS (#23904)

* add new mdm macOS option

* update switch org examples

* apply review suggestions

* Update src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/index.mdx

Co-authored-by: Pedro Sousa <[email protected]>

* Update src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/index.mdx

Co-authored-by: Pedro Sousa <[email protected]>

* Update src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/index.mdx

Co-authored-by: Pedro Sousa <[email protected]>

---------

Co-authored-by: Pedro Sousa <[email protected]>

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/index.mdx

@@ -24,7 +24,7 @@ This page provides generic instructions for an automated deployment. If you want
 
 ## Windows
 
-The WARP Client for Windows allows for an automated install via tools like Intune, AD, or any script or management tool that can execute a `.msi` file.
+The WARP client for Windows allows for an automated install via tools like Intune, AD, or any script or management tool that can execute a `.msi` file.
 
 ### Install WARP
 
@@ -89,33 +89,42 @@ The WARP client will now launch WebView2 when the user is registering their devi
 
 ## macOS
 
-The Cloudflare WARP macOS client allows for an automated install via tools like Jamf, Intune, Kandji, or JumpCloud or any script or management tool that can place a `com.cloudflare.warp.plist` file in `/Library/Managed Preferences` on a supported macOS device. Additionally this plist can be wrapped in a `.mobileconfig`.
+The WARP client for macOS allows for an automated install via tools like Jamf, Intune, Kandji, or JumpCloud or any script or management tool that can place a `com.cloudflare.warp.plist` file in `/Library/Managed Preferences`. The plist can also be wrapped in a `.mobileconfig`.
 
-### Create `plist` file
+If you do not wish to use a management tool, you can manually place an `mdm.xml` file in `/Library/Application Support/Cloudflare`.
 
-1. [Download](/cloudflare-one/static/mdm/com.cloudflare.warp.plist) an example `com.cloudflare.warp.plist` file.
-
-2. Modify the file with your desired [deployment arguments](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/).
+### Prepare file for MDM deployment
 
-3. (Optional) If you want to manually place the file in `/Library/Managed Preferences` (rather than use a management tool), convert the `plist` into binary format:
+#### `plist` file
 
-```sh
-plutil -convert binary1 com.cloudflare.warp.plist
-```
+1. [Download](/cloudflare-one/static/mdm/com.cloudflare.warp.plist) an example `com.cloudflare.warp.plist` file.
 
-The plist must be pushed by an MDM tool in order to persist after reboot. Manually-placed files will be automatically deleted by the OS.
+2. Modify the file with your desired [deployment parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/).
 
-### Create `mobileconfig` file
+#### `mobileconfig` file
 
 1. [Download](/cloudflare-one/static/mdm/CloudflareWARP.mobileconfig) an example `.mobileconfig` file.
 
 2. Run `uuidgen` from your macOS Terminal. This will generate a value for `PayloadUUID`, which you can use to replace the default value used for `PayloadUUID`.
 
-3. Modify the file with your desired [deployment arguments](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/).
+3. Modify the file with your desired [deployment parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/).
+
+### Place an unmanaged `mdm.xml` file
+
+You can configure [WARP deployment parameters](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/) on macOS by manually placing an `mdm.xml` file in `/Library/Application Support/Cloudflare`. This deployment method is an alternative to pushing a `plist` or `mobileconfig` using an MDM tool.
+
+The format of `/Library/Application Support/Cloudflare/mdm.xml` is as follows:
+
+```xml
+<dict>
+  <key>organization</key>
+  <string>your-team-name</string>
+</dict>
+```
 
 ## Linux
 
-The WARP Client for Linux allows for an automated install via the presence of an `mdm.xml` file in `/var/lib/cloudflare-warp`.
+The WARP client for Linux allows for an automated install via the presence of an `mdm.xml` file in `/var/lib/cloudflare-warp`.
 
 The format of `/var/lib/cloudflare-warp/mdm.xml` is as follows:
 

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations.mdx

@@ -39,11 +39,9 @@ To enable multiple organizations, administrators need to modify their [MDM file]
 
 An MDM file supports a maximum of 25 configurations. The following example includes three configurations.
 
-<Tabs>
+### XML
 
-<TabItem label="Windows">
-
-```xml
+```xml title="mdm.xml"
 <dict>
 	<key>configs</key>
 	<array>
@@ -75,56 +73,14 @@ An MDM file supports a maximum of 25 configurations. The following example inclu
 </dict>
 ```
 
-</TabItem>
-
-<TabItem label="macOS">
-
-**plist**
+### plist
 
-[Download](/cloudflare-one/static/mdm/multiple-orgs/com.cloudflare.warp.plist) an example `.plist` file. If placing the file manually, be sure to [convert the file into binary format](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/#create-plist-file).
+[Download](/cloudflare-one/static/mdm/multiple-orgs/com.cloudflare.warp.plist) an example `.plist` file.
 
-**mobileconfig**
+### mobileconfig
 
 [Download](/cloudflare-one/static/mdm/multiple-orgs/CloudflareWARP.mobileconfig) an example `.mobileconfig` file.
 
-</TabItem>
-
-<TabItem label="Linux">
-
-```xml
-<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>mycompany</string>
-			<key>override_api_endpoint</key>
-			<string>203.0.113.0</string>
-			<key>override_doh_endpoint</key>
-			<string>203.0.113.0</string>
-			<key>override_warp_endpoint</key>
-			<string>203.0.113.0:0</string>
-			<key>display_name</key>
-			<string>China employees</string>
-		</dict>
-		<dict>
-			<key>organization</key>
-			<string>test-org</string>
-			<key>display_name</key>
-			<string>Test environment</string>
-		</dict>
-	</array>
-</dict>
-```
-
-</TabItem> </Tabs>
-
 ## Switch organizations in WARP
 
 <Tabs> <TabItem label="Windows, macOS, and Linux">