Tenant Settings¶
The Tenant Settings page in Nitrogen Control Center (NCC) provides a centralized location for managing tenant-level configurations. These settings establish governance and control across the portal.
Domains¶
A Data Domain is a logical grouping of data assets with shared characteristics or management requirements. Organizing data into domains enhances discoverability and governance, allowing organizations to apply specific regulations, restrictions, and policies to each domain.
Domains offer a comprehensive view of your data estate, supporting data classification and lineage tracking. This helps identify sensitive data locations and ensures a secure environment for data consumers.
Structuring data into domains enables federated governance, empowering business units to manage their data according to their own needs. In Microsoft Fabric, domains help users filter and locate relevant content in OneLake and delegate governance functions from the tenant level to the domain level.
Domains integrate with Microsoft Purview for metadata visibility and information protection, supporting sensitivity labeling, data classification, and lineage tracking. This helps organizations manage data risks and maintain regulatory compliance.
On the Domains tab, you can view all configured domains, including their NCC identifier (GUID), name, and description.
Environments¶
An Environment represents a specific configuration of hardware, software, and settings used throughout the software development lifecycle. Each environment serves a distinct purpose, ensuring reliable code build, test, and release processes.
NCC supports up to 10 environments per tenant. Each domain shares the same set of environments. At minimum, configure Development and Production environments. It is recommended to use four: Development, Test, Acceptance, and Production.
- Development Environment: Used for writing, testing, and debugging code. Frequent changes are expected, and security requirements may be lower.
- Test Environment (Optional): Used for automated testing, including unit, integration, and regression tests. Mirrors development but focuses on quality assurance.
- Acceptance Environment (Optional): Acts as a staging or pre-production environment for user acceptance testing (UAT) and business validation. Closely resembles production.
- Production Environment: The live environment for end-users, with high security, performance, and reliability requirements.
On the Environments tab, you can view all configured environments, including order number, name, abbreviation, description, and state (Active or Inactive). You can also add or edit environments.
NOTE
When you create a new environment, it is not automatically created in Fabric. Use the Domain Wizard to add the new environment to the desired domain(s).
Data Sources¶
A Data Source defines the configuration that connects a Connection to an Environment. It specifies how data is accessed and transferred between systems within a given environment, enabling Landing Zone Entities to connect securely to internal or external data systems.
On the Data Sources tab, you can view all configured data sources, including name, Fabric connection, description, environment, namespace, code, and connection type. You can also add or edit data sources.
Before adding a data source, you may need to create a connection in Fabric.
NOTE
Not all connection types are currently integrated with NCC. For the latest list of supported connections, see Integrated Connection Types.
Connections¶
A Connection is a configured Fabric connection that links to a specific data source.
On the Connections tab, you can view all Fabric connections with the prefix CON_NCC, including connection ID, name, connection type, associated data sources, and state.
To add, edit, or remove connections, use the Fabric portal.
NOTE
For certain connections, you must configure private endpoints to enable secure connectivity to the data source.
Variables¶
Tenant Variables are variables set at the tenant level and apply to all domains and environments unless overridden.
TIP
You can overwrite variables on Environment or Domain level.
Default tenant variables include:
| Variable Name | Description |
|---|---|
| key_vault | Name of the key vault in the Azure environment |
| tenant_id | GUID of the tenant where Fabric runs |
| log_ncc_client_secret_secret_name | Name of the secret storing the client secret |
| log_ncc_client_id_secret_name | Name of the secret storing the client ID for logging warehouse access |
| api_ncc_client_id_secret_name | Name of the secret storing the client ID for NCC API |
| api_ncc_client_secret_secret_name | Name of the secret storing the client secret for NCC API |
| api_ncc_scope | Scope for NCC API |
| api_ncc_endpoint | Endpoint for NCC API |
| log_ncc_warehouse_endpoint | Connection string (URL) of the logging warehouse |
| log_ncc_warehouse_guid | GUID of the logging warehouse |
| log_ncc_database | Name of the warehouse for logging |
| log_ncc_workspace_guid | GUID of the logging workspace |
| data_privacy_key_vault | Name of the key vault used to store encryption keys for the data privacy module |
Retention¶
Work in progress
Logging¶
On the Logging tab, you can configure the logging workspace if it has not been set up.
NOTE
You must be a Fabric Admin to set up or edit logging.
NCC provides logging functionality for all primary modules and tools. Each pipeline and notebook writes logs to the WH_LOG warehouse in the NCC Logging workspace for reporting.
A default Power BI dataset and report are automatically deployed in the Logging workspace, providing insights into logged runs.
TIP
To refresh the logging dashboard regularly, you can add a schedule to the PL_LOGGING_METADATA pipeline.