ComfyUI is the node-based canvas many creative teams already use to chain generative models. Microsoft Foundry hosts state-of-the-art image generation models such as gpt-image, FLUX and MAI Image, and starting today, fal video models such as MiniMax H3 Max. This post shows how to bring them into ComfyUI with two small custom nodes. You don't need a GPU, and you don't need any API keys.

You will:

1. Deploy the models in one Foundry project.
2. Give ComfyUI keyless access to Foundry with Microsoft Entra ID.
3. Add the Foundry nodes to ComfyUI, step by step. All the code is in this post.
4. Build a pipeline that turns a text prompt into a realistic, cinematic 5-second shot.

This post assumes you already have ComfyUI installed and know how to open its UI. It can run on your own Windows, macOS or Linux machine, or on a VM or other compute in Azure.

How it works

The nodes call the Foundry APIs directly. Generation runs in Foundry, and ComfyUI only orchestrates the calls, so a CPU-only machine is enough. The nodes get a Microsoft Entra ID token from the identity already available where ComfyUI runs: your az login sign-in on your own machine, or a managed identity on Azure. There are no API keys to store, rotate or leak in a shared workflow.

Step 1 – Deploy the models in your Foundry project

First, deploy at least one image model and the fal video model to the Foundry resource behind your project. You can deploy them from the Foundry portal or from the command line. Both give the same result.

Option A: Deploy from the Foundry portal

1. Open the model catalog in the Foundry portal.
2. Find the model. You can filter Inference tasks by Text to image, or search for the model by name.
3. Select the model, select Deploy, and keep the default settings.

Option B: Deploy with the Azure CLI

If you prefer the command line, run the following command once for each model, and replace the placeholders with your own values:

Use these values for <model-name> and <model-format>:

A few things to keep in mind:

• To find the available <model-version>, run az cognitiveservices account list-models -g <resource-group> -n <foundry-resource> --query "[?name=='<model-name>'].version" -o tsv.
• Name each image deployment after its model, for example FLUX.2-pro. The nodes use the name to detect the model family automatically.
• The video deployment can have any name. This post uses minimax-h3.

When you're done, your project lists all the deployments:

Copy your project endpoint

Finally, copy your project endpoint from the project's Overview page in the Foundry portal. You need it in Step 3. It looks like https://<foundry-resource>.services.ai.azure.com/api/projects/<project>.

Step 2 – Give ComfyUI keyless access to Foundry

The nodes use DefaultAzureCredential, which picks up whichever Microsoft Entra ID identity is available on the machine that runs ComfyUI. That identity needs the Cognitive Services User role on the Foundry resource. The Foundry User role works too. Follow the section that matches where ComfyUI runs.

If ComfyUI runs on your own machine

In this case, ComfyUI uses your own Azure account through the Azure CLI:

1. Install the Azure CLI on the machine that runs ComfyUI.
2. Sign in with az login, as the same OS user that starts ComfyUI.
3. Grant your account the role on the Foundry resource with these commands:

The role assignment commands use Bash syntax. On Windows, you can run them in Git Bash or in Azure Cloud Shell. Only az login must run on the ComfyUI machine itself.

If ComfyUI runs on Azure compute

In this case, use a managed identity instead of a personal sign-in. Turn on the managed identity of the compute resource, then grant it the same role. For example, on a VM:

To create role assignments, you need the Owner or User Access Administrator role on the resource. If you don't have either, ask your Azure admin to run the az role assignment create command. Role assignments can take a few minutes to propagate. If the first run returns 401 or 403, wait and try again.

Step 3 – Add the Foundry nodes to ComfyUI

A ComfyUI custom node is just a Python folder inside ComfyUI's custom_nodes folder. ComfyUI loads every folder there when it starts. To add the nodes, you create one folder with two files, install two Python packages, set one environment variable, and restart ComfyUI.

3.1 Find your ComfyUI folder and its Python

Open a terminal in your ComfyUI folder. With a manual install, activate your virtual environment first. Then check that python is ComfyUI's own Python, not the system one:

The printed path must be inside your ComfyUI installation. If it isn't, use the full path from the table instead of python in the commands below.

3.2 Create the node folder and files

When you're done, the folder looks like this:

1. In custom_nodes, create a folder named ComfyUI-Foundry. Use File Explorer, Finder or mkdir.
2. In that folder, create a file named __init__.py with this single line. It tells ComfyUI which nodes the folder provides:

3. In the same folder, create nodes.py and paste the code below.

Use a code editor such as Visual Studio Code. If you use Windows Notepad, set Save as type to All files, or Notepad saves the files as nodes.py.txt and ComfyUI ignores them.

nodes.py defines two nodes:

3.3 Install the Python packages

From the terminal you opened in 3.1, install the two packages the nodes need into ComfyUI's Python:

On the Windows portable build, run this from the ComfyUI_windows_portable folder instead:

3.4 Point the nodes at your Foundry project

The nodes read your project endpoint from the FOUNDRY_ENDPOINT environment variable. Because the endpoint lives in the environment, it doesn't end up in workflows you share. Set the variable where ComfyUI starts:

3.5 Restart ComfyUI and check that the nodes loaded

Restart ComfyUI. ComfyUI only loads custom nodes at startup. In the startup log, which is the console or the Desktop Terminal tab, look for ComfyUI-Foundry under Import times for custom nodes:

If the line says (IMPORT FAILED), scroll up to find the error. No module named 'azure' means the packages went into a different Python, so repeat 3.3 with the full Python path from the table.

Open the ComfyUI UI, or refresh the page if it's already open, and open the Nodes panel. Both nodes are in the Microsoft Foundry category.

Step 4 – Build a cinematic scene pipeline

Now that the nodes are loaded, you can chain an image model and the video model. The image model creates a cinematic keyframe, and the video model animates it.

Connect the nodes

Add three nodes to the canvas and connect them like this:

• Foundry Image Generate IMAGE → Save Image images
• Foundry Image Generate IMAGE → fal MiniMax H3 Max Video image

Configure the nodes and prompts

Set the node inputs to these values:

In the Foundry Image Generate node, enter a keyframe prompt that sets the look of the shot: lens, lighting and color grade.

Cinematic film still, shot on 35mm anamorphic lens. A lone lighthouse keeper in a weathered yellow raincoat stands on wet black rocks at dusk, facing a storm rolling in over the ocean. Huge waves crash and throw spray into the air, the lighthouse beam cuts through the rain behind him. Teal and orange color grade, volumetric light, shallow depth of field, subtle film grain, ultra realistic, 2.39:1 framing.

In the fal MiniMax H3 Max Video node, enter a motion prompt. It only needs to describe the camera move and the action, because the keyframe already defines the scene.

Slow cinematic dolly-in toward the lighthouse keeper. The lighthouse beam sweeps through the rain, waves crash against the rocks and spray drifts across the frame, his raincoat flutters in the wind. Subtle handheld camera movement, moody film look, natural motion.

Run the pipeline

Select Run. The keyframe comes back in a few seconds. The fal node then submits an image-to-video job and polls until it finishes. On our run, the whole pipeline took about 80 seconds.

The result

The keyframe from the Foundry image model (1536×1024):

The 5-second, 24 fps shot from fal MiniMax H3 Max:

The image model sets the look (lens, grade, lighting) and the video model only adds motion, so the shot stays consistent from frame to frame. Splitting the work into keyframe → motion is the easiest way to get a realistic, art-directed result.

Tips

• Swap image models. Set deployment to gpt-image-2.5-sunburst, FLUX.2-pro or MAI-Image-2.6. The node detects the model family from the name and calls the matching API. If your deployment has a custom name, set model_family yourself. MAI Image needs both sides to be at least 768 px.
• Use a model from another Foundry resource. Paste that resource's endpoint into the node's optional endpoint field, and grant the same identity (your account or the managed identity) the same role on that resource.
• Higher fidelity. Set resolution to 1080P on the video node for final renders.
• Text-to-video. Leave the fal node's image input unconnected, and it calls text-to-video.
• Iterate cheaply. Keep seed set to fixed. ComfyUI caches nodes whose inputs haven't changed, so you can tweak the motion prompt without regenerating the keyframe.

Learn more

• Explore Foundry Models sold directly by Azure
• Foundry Models from partners and community
• Deploy Foundry Models
• Azure OpenAI image generation models
• Deploy and use FLUX models in Foundry
• Deploy and use MAI image models in Foundry
• Configure keyless authentication with Microsoft Entra ID
• Authentication and authorization in Microsoft Foundry
• Role-based access control for Microsoft Foundry
• Sign in with the Azure CLI
• Managed identities for Azure resources
• Configure managed identities on Azure VMs
• Assign Azure roles with the Azure CLI
• DefaultAzureCredential (Azure Identity for Python)
• How to install custom nodes in ComfyUI
• Manage ComfyUI Desktop installations (Terminal, About, environment variables)
• ComfyUI custom nodes docs