---
title: "Branch Mapping"
slug: "branch-mapping"
updated: 2026-06-18T08:23:49Z
published: 2026-06-18T08:23:49Z
canonical: "support.controlup.com/branch-mapping"
---

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

# Branch Mapping

To access the **Branch Name Mapping Settings** page, click on **Settings** **> Branch Mapping**.

![Branch Name Mapping Settings page with Branch IP Configuration window open](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/VDIBranchmapping.png)

Here you can configure a list of IP subnets utilized on your network and map them to names of geographical locations, buildings or organizational branches. On the basis of this configuration, ControlUp assigns a source branch name to every user session and populates the **Branch Name** column in the **Sessions** view with this branch name. For best practice, we recommend you configure up to a maximum of 20,000 branch mappings in your network.

For example, in an organization in which the New York office uses the 10.1.0.0/16 subnet and the Chicago office uses the 10.2.0.0/16 subnet, the mapping table should be configured to map those subnet addresses to the branch names. As a result, the **Branch Name** column will be populated with the value of “New York” for all user sessions established from client IP addresses in the 10.1.0.0/16 range, and with the value of “Chicago” for the 10.2.0.0/16 range.

## Subnets and Sites

You can click **Add** to manually add a list of subnets and branch names, or click **Import** to import a list using a CSV file.

Here’s an example content of a supported CSV file:

```plaintext
10.1.0.0/16,Chicago
10.2.0.0/16,New York
192.168.1.0/24,London
172.16.0.0/12,Amsterdam
10.1.3.100-10.1.3.200,Servers Subnet
10.1.4.111,Test Workstation
```

To ensure a successful import, your CSV file must follow a specific format that matches the structure exported by Active Directory.

**Required CSV Format:**

- Column 1: Subnet/IP (e.g., `10.1.0.0/16`)
- Column 2: Branch/Site Name (e.g., `Chicago`)

When exporting from Active Directory Sites and Services, the default output uses the headers `Name` and `Site`, which aligns with ControlUp’s requirements. Note that the AD `Name` column contains the subnet, not a friendly name. Don’t reorder these columns to `Site,Name`, since placing the branch name in the first column will cause the import to fail.

## Export CSV File

If your Active Directory is already organized by subnets and sites, you can export that data as a CSV file from Active Directory Sites and Services and import it directly into ControlUp.

To export a CSV file, perform the following steps:

1. From a Windows Server or PC, open Active Directory Sites and Services.
2. In the tree view, expand the Sites container.
3. Right-click the Subnets container and click **Export List…**
4. Save the file as “Text (Comma Delimited) (*.csv)”.
5. From the Real-Time DX Console, click **Settings > Branch Mapping> Import**.
6. Browse to the file exported in step 4 above.

Removed AD DependencyYou can deploy ControlUp Monitors on machines that are not joined to a local Active Directory (AD) domain. For details, see [here](/v1/docs/removed-ad-dependency-for-monitors).

If the client IP address doesn’t belong to any of the subnets configured in the mapping table, the **Branch Name** column can be left empty or populated with a custom default value you provide. You can configure this setting under the **Unrecognized IP addresses** area.