Mount Points
A Mount Point connects external file-based storage directly to a workspace file system. Unlike Data Buckets, which create point-in-time snapshots that are replicated to the cluster, Mount Points provide live access to the storage. Changes made inside the workspace are immediately visible to other workspaces sharing the same Mount Point, enabling real-time collaboration on shared files and datasets.
Mount Points are useful when teams need to:
- Share large datasets (for example, ML training data or model artifacts) without duplicating them across workspaces.
- Collaborate in real time on shared files without a manual snapshot-and-publish workflow.
- Access terabytes of data instantly, without waiting for replication.
Note
Mount Points are available only when a Platform Admin has enabled the feature in System Configuration > Integrations > Mount Point Storage. See Enable Mount Points for details.
Note
Mount Points are not supported in multi-region configurations.
- View Mount Points
-
Add a Mount Point
Permission: Resources::Manage - Attach a Mount Point to a workspace
View Mount Points
Mount Points configured for the current project are displayed on the Resources > Mount Points page.
Each Mount Point displays the following information:
- Name — A descriptive label for the Mount Point.
- Type — The storage type (for example, File).
- Status — The current state of the Mount Point (for example, Ready).
- Container Name / Server Address — The storage account or server address for the Mount Point.
-
Default Mount Path — The file system path where the share is mounted inside the workspace (for example,
/mnt/shared-data). - Actions — View details or manage the Mount Point.
Add a Mount Point Permission: _Resources::Manage_
To add a Mount Point, select Add Mount Point on the Resources > Mount Points page.
First, select a Storage Provider from the dropdown:
- Azure Files (Create New) — Provisions a new Azure file share.
- Azure Files (Attach Existing) — Connects to an existing Azure file share.
Azure Files (Create New)
Provide the following information:
- Name — A descriptive name to identify the Mount Point.
- Storage Class — Select a storage class from the available options.
-
Default Mount Path — The path where the share is mounted inside the workspace file system. The path is prefixed with
/mnt/(for example, enteringdataresults in/mnt/data). - Volume Capacity — The size of the file share in GB.
- Access Permissions — Select Read/Write or Read Only.
- Attach Asset Information (optional) — Add metadata to classify the Mount Point.
Azure Files (Attach Existing)
When attaching an existing Azure file share, provide a Name and select a Connection Method:
-
Manual Connection — Enter the storage credentials directly:
- Access Key — The storage account access key.
- File Share Name — The name of the file share to mount.
Then configure the Default Mount Path and Access Permissions as described above.
Note
Editing and deleting Mount Points is not available in this release.
Attach a Mount Point to a workspace
You can attach one or more Mount Points to a workspace during workspace creation or when creating a workspace template.
Mount Points appear in the Resource Access step alongside other resource types such as GitHub, GitLab, Secrets, and Connected Services.
When attaching a Mount Point:
- Expand the Mount Points section in the Resource Access step.
- Select a Mount Point from the Repository dropdown.
- Optionally, specify a Source SubPath to mount a specific subdirectory of the file share.
- Review or customize the Mount Path — the location in the workspace file system where the share is accessible. The path is prefixed with
/mnt/. - Review the Access Permissions assigned to the Mount Point.
- Select Attach Repository to add the Mount Point to the workspace.
Attached Mount Points are listed under Configured Repositories below the attachment form.
Important
Each Mount Point in a workspace must use a unique mount path. If a path conflict is detected, the system displays an error and prevents the workspace from being created until the conflict is resolved.
Note
Mount Points can only be added in the primary region. If the workspace is configured for a non-primary region, the Mount Points section is disabled.
Mount Points in workspace templates
When you create or update a workspace template, you can pre-configure Mount Points in the same way as during workspace creation. Workspaces created from the template automatically inherit the configured Mount Points and their mount paths.
Developers creating a workspace from a template can still customize the mount path for each attached Mount Point before launching the workspace.