> ## Documentation Index
> Fetch the complete documentation index at: https://developer.box.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft MXC

> Use Box Mount to give an agent running in a Microsoft Execution Containers (MXC) sandbox governed access to a Box folder.

[Microsoft Execution Containers (MXC)](https://learn.microsoft.com/en-us/windows/apps/develop/mxc/) provides policy-driven sandbox execution across Windows, Linux, and macOS. Box Mount exposes a Box folder inside that sandbox as a standard POSIX workspace with two-way sync, so your agent works with ordinary file operations while Box remains the system of record.

## Before you begin

On the Box side, you need:

* Access to the Box Mount developer preview, including the Box Mount binary. To request access, complete the [Box Mount developer preview form](https://bit.ly/box-mount-preview).
* A Box app configured for OAuth 2.0 or JWT. See [Configure credentials](https://developer.box.com/guides/box-mount#configure-credentials).
* The ID of the Box folder you want to mount. This is the number at the end of the folder URL on Box.

## Demo video

This demo mounts a Box folder, runs an agent inside MXC that reconciles invoices, purchase orders, and payments, and syncs a review memo and an exception workbook back to Box. Box credentials stay outside the MXC sandbox, and model traffic goes through the MXC proxy.

[Microsoft MXC + Box Mount: Running an AI Agent in a Local Sandbox](https://www.youtube.com/embed/c0aJQP3t6us)

## Next steps

* Review [Secure your credentials](https://developer.box.com/guides/box-mount#secure-your-credentials) to keep Box credentials outside the agent sandbox.
* Review the Box Mount [known limitations](https://developer.box.com/guides/box-mount#known-limitations) before you build on the preview.