Forum Discussion

joyeldavis007's avatar
joyeldavis007
Frequent Visitor
1 year ago
Solved

Static Outbound IP for Notebook

Hey Team, I need to load data from Crowdstrike to Lakehouse. I was leveraging Notebook along with falconpy library for this. But Crowdstrike needs to whitelist the IP from Notebook. Since notebo...
data engineering
notebook
  • joyeldavis007's avatar
    joyeldavis007
    1 year ago

    Hi v-sgandrathi ,

    Thank you for the optional path provided. We have an Azure VM running and tried the method you shared.But we find it difficult to manage it. As, there is no monitoring option available. 
    The alternative approach we found was to connect the API using Pipeline and Web connector, where we can route the request through a data gateway. It is working fine for now.
    P.S: the support ticket is still on discussion . Will update here if any new possibilities are discussed.

v-sgandrathi's avatar
v-sgandrathi
Community Support
1 year ago

Hi joyeldavis007,

Thank you for the detailed update and for the efforts you've already taken, including raising a support ticket which is absolutely the right approach.

To address the issue with dynamic IPs when using a Notebook and the FalconPy library to connect to CrowdStrike, here's a recommended workaround based on commonly adopted enterprise patterns:

Deploy your FalconPy logic in an Azure environment that supports static outbound IP addresses, such as:

Azure Function App (Premium Plan), Azure Container Instance, or Azure Virtual Machine (VM)

Configure this environment to use an Azure NAT Gateway with a static public IP, then provide that IP to CrowdStrike for whitelisting.

Once the FalconPy script pulls the data successfully, you can push the results to your Microsoft Fabric Lakehouse using supported connectors or APIs (e.g., via OneLake REST API or Azure Data Lake Gen2 integration).

Please note that, as of now, Fabric Notebooks do not support VNet integration, so routing their traffic through a NAT Gateway is not currently feasible. Hosting your extraction logic externally ensures stable connectivity while aligning with CrowdStrike’s IP whitelisting requirement.

If you're constrained from using Azure Functions or Containers, a VM-based proxy remains a valid fallback option.

 

We hope this helps as a complementary path while the official support ticket is under review.

 

If this post was helpful, please consider marking Accept as solution to assist other members in finding it more easily.

If you continue to face issues, feel free to reach out to us for further assistance!

 

Happy to see you here in the Microsoft Fabric Community!