Skip to content
FlowonFlowonLogic Fabric DocsLogic Fabric Docs
flowon.com

AI & agents

Deploy the AI products

Plan and prepare the deployment of Logic Foundry, the Logic Agents and Logic Conductor into your Azure subscription.

Applies toDataverse

You deploy the Logic Fabric AI products into your own Azure subscription, and they work with your own Dataverse environment and Microsoft Entra tenant. Flowon provides ready-made deployment templates for the Azure Developer CLI (azd). One command creates the hosting, the sign-in registrations and the Dataverse access each product needs. These pages are for the Azure and Power Platform administrator who runs the deployment.

Two templates

Section titled “Two templates”
Template Deploys Guide
Foundry and agents Logic Foundry and all six Logic Agents (Assist, Assurance, Context, Guard, Insights, Sentinel), connected to each other Deploy Logic Foundry and the Logic Agents
Conductor Logic Conductor on its own Deploy Logic Conductor

Deploy each template once per Dataverse environment you want to use it with, for example once for development and once for production. The two templates are independent: deploy one, the other or both.

What lands in your subscription

Section titled “What lands in your subscription”

Each deployment creates one resource group with:

  • An Azure Container Apps environment that hosts the products as container apps, with HTTPS addresses.
  • Managed identities that the products use to reach Dataverse and to sign users in without any stored passwords.
  • Application Insights for monitoring (optional; you can reuse an existing resource or turn it off).
  • For Foundry and the agents only: an internal cache (Redis) and a small storage account that keeps the cache’s data across restarts. Neither is reachable from outside the environment.

It also creates app registrations in Microsoft Entra ID (one for each product, plus one for desktop AI clients such as Visual Studio Code) and a Dataverse application user for the product’s managed identity, with the Flowon Customizer security role by default.

Every call a user makes runs with that user’s own Dataverse permissions: the products act on behalf of the signed-in user.

Prerequisites

Section titled “Prerequisites”
You need Why
The Azure Developer CLI and the Azure CLI, signed in with azd auth login Runs the deployment.
An Azure subscription where you can create resource groups Hosts the products.
Application Administrator or Cloud Application Administrator in Microsoft Entra ID Creates the app registrations.
Global Administrator or Privileged Role Administrator (or another role that can grant tenant-wide admin consent) The deployment grants admin consent for the products to access Dynamics 365 on the user’s behalf. Without it, that step fails and users see a consent error later.
Logic Fabric installed in the Dataverse environment, including the Flowon Customizer security role The products work with your Logic Fabric projects. The deployment assigns this role by name and stops if it doesn’t exist.
The environment’s address, for example https://contoso.crm.dynamics.com/ Each deployment connects to one environment.
A setup identity: an existing user-assigned managed identity that has the System Administrator role in that Dataverse environment During deployment it creates the product’s Dataverse application user and assigns its role. See below.
For the agents: an AI model service The agents’ AI features need a model. See AI model.

Prepare the setup identity

Section titled “Prepare the setup identity”

The deployment can’t give itself access to Dataverse, so you prepare one identity in advance and grant it access once.

  1. Create a user-assigned managed identity in Azure, in any resource group:

    Terminal window
    az identity create --name logic-fabric-setup --resource-group <your-resource-group>

  2. In the Power Platform admin center, open the target environment, go to Settings > Users + permissions > Application users, and add a new app user for this identity using its client ID (az identity show --name logic-fabric-setup --resource-group <your-resource-group> --query clientId -o tsv). Give it the System Administrator role.

  3. Copy the identity’s resource ID. You pass it to the deployment as setupManagedIdentityId:

    Terminal window
    az identity show --name logic-fabric-setup --resource-group <your-resource-group> --query id -o tsv

You can reuse the same setup identity for several deployments into the same environment.

Get the templates

Section titled “Get the templates”

The templates are in the Logic Fabric deployment templates, which Flowon provides on request (contact Flowon). Clone or download them to the machine you deploy from. Each template has its own folder, and you run every azd command from inside that folder.

Deployment environments

Section titled “Deployment environments”

azd keeps the settings of each deployment in an environment stored in a .azure folder next to the template. It holds the values you set and some values it generates, such as the internal cache password. Keep that folder (for example, in a secure location your team can reach) so that later updates reuse the same settings. Don’t commit it to source control.

Section titled “Related”