Back to blog

Low-code agents: plan the move to production

Created on November 7, 2026 · Publication analysed: November 5, 2026 · Source: Microsoft Inside Track

Microsoft’s account of its internal practices provides a starting point for organizing low-code agents. For Belgian and French companies, we propose making the move from prototype to production a documented decision: who owns the workflow, which data can it use and which actions are allowed?

1. What Microsoft describes internally

On November 5, 2026, Microsoft described its internal governance of Power Platform and Copilot Studio. It distinguishes individual developer environments, team sandboxes and production environments. The account describes identified ownership, connector policies and review before wider distribution. It stresses that environments do not replace identity, data and activity controls. This is an internal account, rather than a guarantee that automatically applies to customers.

2. What this changes for Belgian and French companies

We recommend requiring a production approval record before widening access to an agent. For an SME, this can be brief: process, business owner, data, permitted actions and stopping procedure. For mid-market companies and large groups, plan a joint review by IT, security and business teams, with an exception list. For a public administration, retain decision criteria and acceptance evidence to support reviews of procurement and the operating service.

3. Underside analysis: the decisive boundary is permission to act

Our proposal distinguishes three levels: consulting information, preparing a draft and executing an action. A document retrieval agent should start with read permissions limited to the selected corpus. Before allowing it to change a record, require business approval and test separation between users. A dedicated environment should not be accepted as sufficient evidence: also check the account each tool actually uses and the data returned in responses.

4. Prepare the connection to Odoo Enterprise

For a quotation scenario, we recommend first generating a proposal in a test database with fictitious customers. Define read, draft creation and confirmation permissions separately. Replay an access denial, a repeated request and a missing human approval. Check that the workflow retains evidence of approval and does not confirm the quotation without it. This is an Underside integration recommendation; Microsoft’s account demonstrates no Odoo integration.

5. Check connectors and sovereignty across the workflow

We recommend an inventory linking each connector to its owner, destination, technical identity and business need. For RAG, add document sources and the access rules to test. Compare local and cloud options on processing locations, logs, support access and export options, retaining contractual answers. Test a prohibited destination with fictitious data. The decision should cover the entire workflow, including retrieval and telemetry.

6. Test departure scenarios and return to manual processing

Before launch, we propose simulating the creator’s departure, removal of a connector and suspension of the execution account. Check that an owner can find the workflow, take over its management and stop new actions. Define which cases return to a manual queue and have business users validate that recovery. Retain a dated acceptance record, the configuration version and an explicit decision on exceptions. Revisit this record whenever a tool or data category is added.

Operational priority: select one pilot agent and approve its data, connectors, action permissions and stopping procedure before opening it for production use.

Scope the move to production

Read Microsoft’s official November 5 account