Skip to content

Configure domain settings in NCC Portal

Domain settings in NCC Portal allow administrators to centrally manage and configure key components of your environment. Use the Domain Settings interface to organize workspaces, manage data storage, orchestrate pipelines, structure notebooks, and set up variables.

Domain settings overview

The Domain Settings page includes the following tabs:

  • Workspaces
    Create, configure, and update workspaces to organize resources and users.

  • Lakehouses
    Set up and manage lakehouses for scalable data storage and analytics.

  • Pipelines
    View and manage pipelines with the PL_ prefix to automate data workflows.

  • Notebooks
    Access and organize notebooks with the NB_ prefix for collaborative data exploration.

  • Variables
    Configure variables at the environment, domain, or tenant level to support secure and flexible data extraction.

Workspaces tab

The Workspaces tab displays all workspaces integrated within the domain. For each workspace, you can view details such as Fabric ID, name, description, associated environment, SQL Server endpoint, and available actions.

TIP
If you have the required permissions, use the SQL Server endpoint to connect to workspace data from compatible SQL client tools.

Workspace actions include:

  • Configure
    Modify the domain, environment, name, or description of the workspace.

  • Update
    Change the domain. For step-by-step instructions, see Update environment.

  • Delete
    Remove the workspace from the domain.

IMPORTANT
Deleting a workspace is irreversible. All data stored in the workspace will be permanently deleted.

Lakehouses tab

The Lakehouses tab lists all lakehouses integrated within the domain. For each lakehouse, you can view the Fabric ID, name, description, associated workspace, and available actions.

Lakehouse actions include:

  • Configure
    Change the workspace, medallion layer, name, or description of the lakehouse.

  • Delete
    Remove the lakehouse from the workspace.

IMPORTANT
Deleting a lakehouse is irreversible. All data stored in the lakehouse will be permanently deleted.

Pipelines tab

The Pipelines tab lists all pipelines with the PL_ prefix integrated within the domain. For each pipeline, you can view the Fabric ID, name, description, and associated workspace.

Notebooks tab

The Notebooks tab lists all notebooks with the NB_ prefix integrated within the domain. For each notebook, you can view the Fabric ID, name, description, and associated workspace.

Variables tab

The Variables tab displays all configured variables related to the domain and its environments. You can also view an overview of all tenant variables.

Variables provide flexibility for storing and retrieving information, such as secrets from Azure Key Vault. The tenant variables section describes the default Azure Key Vault that NCC uses to retrieve secrets.

In Nitrogen Control Center, you can set up variables for notebooks and pipelines. There are three levels of variables:

  1. Tenant
  2. Environment
  3. Domain

Tenant variables

At the tenant level, some variables are set during first-time usage of NCC.

Domain variables

A domain variable is set at the domain level and applies to all environments and workspaces within that domain.
For example: For an HR or Finance domain, you can set a variable to a custom Key Vault that only specific users can access.

Environment variables

An environment variable can be set if, for example, a pipeline or notebook needs to use a different secret between development and production environments.

If a variable name is reused, the higher-level variable overwrites a lower-level one.

The following diagram illustrates the variable resolution process:

graph TD
    A[Tenant Variable] 
    X[Which variable to use?] --> B{Environment Variable configured?}
    B -- Yes --> C[Environment Variable]
    B -- No --> D{Domain Variable configured?}
    D -- Yes --> E[Domain Variable]
    D -- No --> A

TIP
Hierarchy for variable resolution:

  1. If an environment variable is configured, it is used.
  2. If not, the domain variable is checked and used if configured.
  3. If neither is configured, the tenant variable (default) is used.

Example 1: One domain

The following diagram illustrates variable resolution for a single domain scenario:

graph TD
    T[**Tenant**: <br>key_vault= kv-fab-con-sal-p-euw-01]
    D[Domain: SalesA<br>key_vault= not configured]
    E1[Environment: Development<br>key_vault= kv-fab-con-sal-d-euw-01]
    E2[Environment: Production<br>key_vault= not configured]

    T --> D
    D --> E1
    D --> E2

    subgraph Variable Resolution
        V1[Development uses:<br>kv-fab-con-sal-d-euw-01]
        V2[Production uses:<br>kv-fab-con-sal-p-euw-01]
    end

    E1 --> V1
    E2 --> V2

Explanation:

  • The tenant variable kv-fab-con-p-euw-01 is the default.
  • The domain SalesA does not override the tenant variable.
  • The Development environment sets its own key_vault variable (kv-fab-con-sal-d-euw-01), so it uses this value.
  • The Production environment does not set a variable, so it inherits the tenant default.

Example 2: Multiple domains

The following diagram illustrates variable resolution for multiple domains:

graph TD
    T[**Tenant**: <br>key_vault= kv-fab-con-sal-p-euw-01]
    D1[Domain: SalesA<br>key_vault= not configured]
    E11[Environment: Development<br>key_vault= kv-fab-con-sal-d-euw-01]
    E12[Environment: Production<br>key_vault= not configured]
    D2[Domain: SalesB<br>key_vault= kv-fab-con-sab-p-euw-01]
    E21[Environment: Development<br>key_vault= kv-fab-con-sab-d-euw-01]
    E22[Environment: Production<br>key_vault= not configured]

    T --> D1
    D1 --> E11
    D1 --> E12
    T --> D2
    D2 --> E21
    D2 --> E22

    subgraph Variable Resolution SalesA
        V11[Development uses:<br>kv-fab-con-sal-d-euw-01]
        V12[Production uses:<br>kv-fab-con-sal-p-euw-01]
    end

    subgraph Variable Resolution SalesB
        V21[Development uses:<br>kv-fab-con-sab-d-euw-01]
        V22[Production uses:<br>kv-fab-con-sab-p-euw-01]
    end

    E11 --> V11
    E12 --> V12
    E21 --> V21
    E22 --> V22

Explanation:

For domain SalesA:

  • The tenant variable kv-fab-con-p-euw-01 is the default.
  • The domain SalesA does not override the tenant variable.
  • The Development environment sets its own key_vault variable (kv-fab-con-sal-d-euw-01), so it uses this value.
  • The Production environment does not set a variable, so it inherits the tenant default.

For domain SalesB:

  • The tenant variable kv-fab-con-p-euw-01 is the default.
  • The domain SalesB overrides the tenant variable with kv-fab-con-sab-p-euw-01.
  • The Development environment sets its own key_vault variable (kv-fab-con-sab-d-euw-01), so it uses this value.
  • The Production environment does not set a variable, so it inherits the domain default because that has been configured.