Environment File in Notebook

Hi Anonymous , thank you for reaching out to the Microsoft Fabric Community Forum.

Microsoft Fabric does not natively support attaching .env files to notebooks. However, you can manage environment variables in different ways:

1. Fabric provides NotebookUtils (mssparkutils), which allows you to store and retrieve environment variables but this works only for variables already configured in Fabric.:

from notebookutils import mssparkutils

# Get an environment variable

value = mssparkutils.env.getVariable("MY_ENV_VAR")

print(value)

2. If you need to customize values per environment (Dev, Test, Prod), you can use Deployment Rules but this is not a direct .env file solution.:
3. Navigate to Deployment Pipelines.
4. Create a Deployment Rule to set specific values.
5. This allows modifying Lakehouse paths, parameters, etc. dynamically.

 

3. Store a .env File in a Lakehouse and Read It in the Notebook. This works for custom environment variables but less secure if the .env file contains sensitive data:

import os

 

# Read .env file from Lakehouse Files

file_path = "/lakehouse/default/Files/config/.env"

 

with open(file_path, "r") as f:

    for line in f:

        key, value = line.strip().split("=")

        os.environ[key] = value

 

# Access an environment variable

print(os.getenv("MY_CUSTOM_VAR"))

 

4. If your .env file contains API keys, credentials, or secrets, store them in Azure Key Vault and retrieve them in your notebook. This way you can have Secure credentials & secrets but Requires Azure Key Vault setup

from notebookutils import mssparkutils

 

# Get a secret from Azure Key Vault

secret_value = mssparkutils.credentials.getSecret("my-key-vault", "MY_SECRET_KEY")

print(secret_value)

 

If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.

Hi Anonymous , thank you for reaching out to the Microsoft Fabric Community Forum.

To attach an ENV file to notebooks when migrating through both deployment pipeline and DevOps, and to re-tag different environments in the notebook, you can follow these steps:

1. Ensure your ENV file is included in your repository. This file should contain the necessary environment variables. In your deployment pipeline, add a step to copy the ENV file to the appropriate location in your notebook's directory. This can be done using a script or a task in your pipeline configuration.
2. To re-tag different environments in the notebook, you can use deployment rules to specify environment-specific configurations. For example, you can define different configurations for development, staging, and production environments. In your deployment pipeline, use environment variables or parameters to dynamically set the environment tags. This can be done by modifying the notebook's metadata or configuration files during the deployment process.
3. In your deployment rules, specify the environment-specific configurations.
4. In your DevOps pipeline configuration, add steps to handle the ENV file and set environment variables. This can be done using tasks or scripts in your pipeline YAML file.

If this helps, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details.
Thank you.