Skip to main content

Claude Desktop on managed devices

Your MDM pushes one profile that enrolls the Mac and manages Claude Desktop. The policy lives in the Anyray console, so an edit needs a Claude relaunch, not a redeploy.

This switches Claude Desktop to third-party inference

The claude.ai admin console stops delivering connectors, plugins, and model policy to these devices (what changes). Relying on it? Keep Claude Desktop first-party.

Before you start​

You needDetail
A public gateway URLANYRAY_GATEWAY_PUBLIC_URL set to the gateway's public HTTPS origin
MacsmacOS 13+, Claude Desktop 1.10628.0 or newer

The console builds the macOS profile. Windows and Linux are at the bottom of this page.

Deploy to Macs​

1
Open the Claude Desktop policy

Console Users → MDM Users → Add MDM profile → macOS → Claude Desktop policy.

2
Import your current settings (optional)

Configure the policy → Import from Claude Desktop… takes a .mobileconfig or JSON exported from Configure Third-Party Inference on an unmanaged Mac (authoring guide). Leave it empty to use Anyray's defaults.

Comes acrossDropped (the gateway owns these)
Models, connectors, plugin marketplaces and skills, workspace and tool restrictions, egress, app policyInference URL, helper path, API key, custom headers
3
Publish the policy

Click Publish.

4
Download the package and the profile

Under Download the files on the same tab, download anyray-connect-desktop-macos-universal.pkg, then Create & download anyray-enroll-claude-desktop.mobileconfig (shown once). The profile enrolls the Mac and pins /connect/claude-desktop/bootstrap?os=macos and the two helper paths. Its only secret is the enrollment link. Jamf Pro, Kandji, and Intune fill its $EMAIL; for other MDMs see the assigned email.

5
Push the package, then the profile

Both in device scope, to the same Macs. Test on one Mac first. Claude Desktop calls helpers the package installs, so on a Mac that gets the profile first it cannot reach Anyray until the package lands.

6
Relaunch Claude Desktop

Each user fully quits (⌘Q) and reopens. Claude reads the profile only at launch.

Confirm the profile was read

Help → Troubleshooting → Copy Managed Configuration Report lists the keys the app read. Trust it over the window.

What you seeWhat it means
macOS: Configure Third-Party Inference still opens editableNo recognized key reached the app, even when the MDM console reports the profile as delivered
Windows: the window is lockedAny value directly under HKLM\SOFTWARE\Policies\Claude locks it, read or not. A locked window proves nothing
The report shows the profile, but the app still signs into claude.aiThe profile predates disableDeploymentModeChooser. Redeploy the current one

Macs that already have two profiles​

Move Macs holding anyray-enroll.mobileconfig and anyray-claude-desktop.mobileconfig in this order, so they are never without a profile:

  1. Push anyray-enroll-claude-desktop.mobileconfig to them. Keep the old two.
  2. Once a test Mac lists it and passes the check above, remove the old two from your MDM.
  3. Then revoke the old profile's entry under MDM Users.

To keep two profiles instead, the console still offers each file on its own, below the main download.

Local MCP servers, skills, plugins, and Claude Code and Cowork sessions copy into the new profile on their own, finishing once each user has opened Code and Home in Claude Desktop and fully quit it (details). claude.ai chats come from an export: upload your organization's once in the console and Connect restores each user's chats while Claude Desktop is quit (details).

Sharing pages uses Connect's local anyray-share connector on managed Macs. Opening pages shared with a user needs no local connector, on Mac or Windows: the managed anyray server carries it.

On user subscriptions, each user approves once: a browser page opens the first time they open Claude (details).

Change the policy later​

No MDM push. Devices pick a change up at the next Claude launch.

To changeWhere
ConnectorsAccount menu → Connectors. Search the catalog or paste a server address. Claude Desktop gets all of them, and remote ones reach every managed tool. Developers authorize OAuth ones themselves
Built-in GitHub, Microsoft 365, Web searchSame panel. GitHub needs your GitHub OAuth app client ID, Microsoft 365 your Entra tenant ID and app client ID, and Web search a Brave, Tavily or Exa API key, which stays in the gateway (details)
Skills and guidanceSame panel, Skills tab. Upload each SKILL.md and write the shared Guidance (Sync team content)
Policy settingsEdit Configure the policy, then Publish. The profile does not change, so there is nothing to redeploy
Import from ClaudeSame panel, Your connectors tab. The Import from Claude switch is on by default, so people can bring their claude.ai chats over (Claude Desktop 1.28929.0 and newer). Turn it off to hide the wizard (details)
The console policy replaces your MDM profile's settings

Once Claude Desktop applies the policy, your MDM profile decides only the keys a bootstrap cannot set (list). Every other key follows the console policy, or Claude's default where the policy leaves it out. So Claude Desktop keeps auto-updating when a profile sets disableAutoUpdates, isLocalDevMcpEnabled is true unless the console policy sets false, and Import from Claude shows unless you turn it off (below).

The policy is readable without credentials

Anyone can fetch the policy and Skills & Guidance URLs. If connector URLs or instructions must stay private, use the static model.

Windows and Linux

Publish the policy above, then emit the profile for that OS with Connect:

Windows
anyray-connect desktop fleet bootstrap windows \
https://gateway.example.com/connect/claude-desktop/bootstrap claude-bootstrap.reg

Windows: the Anyray Connect MSI installs the helpers. Linux: deploy the file to /etc/claude-desktop/managed-settings.json and install the helpers with desktop helper --write (detail).

Limits to plan around
  • OAuth grants, cookies, sessions, and "Made by Anthropic" connectors do not import.
  • While content mode is off, the policy leaves out the anyray server, so trimmed output cannot be read back and shared pages cannot be opened in Claude Desktop (details).
How the policy fetch authenticates

Claude Desktop 1.34493.1+ sends Authorization: Bearer <client key> from bootstrapHeadersHelper; an invalid key gets 401. Anyray profiles (console, desktop fleet bootstrap, desktop fleet static) set disableDeploymentModeChooser, or a user signed into claude.ai never fetches the policy.

Local one-off test

Quit Claude, set deploymentMode to "3p" in ~/Library/Application Support/Claude-3p/claude_desktop_config.json, and relaunch.

Other routes: policy models compared, your own policy server or OIDC, undo an accidental switch, one Mac, no MDM. Coding tools: Bulk enrollment with your MDM.