27 AUGUST 2026
Welcome to the Orchestration AI Release Notes.
As they become available, additions and updates to these release notes can be found here.
What's in the Release Notes?
- About Orchestration AI
- What's new in Orchestration AI?
- New features
- General enhancements
- Resolved issues
- Breaking changes
- Limitations
- Deployment
About Orchestration AI
Orchestration AI solution facilitates Agentic AI capabilities, bringing intelligent, context-aware assistance into rapid creation of business process applications that work on top of legacy systems to orchestrate best-of-breed digital solutions, and harness human expertise.
Orchestration AI combines process orchestration with Agentic AI and enables organizations to automate tasks, support decision-making, and dynamically adapt to changing business conditions. Built on cloud infrastructure and enhanced for Azure and Power Platform, the solution delivers increased value not just in the case management but other domains too.
With Orchestration AI, an organization can transform customers’ experience, increase self-service actions, and gain greater operational visibility. The Agentic AI capabilities further enhance these outcomes by providing real-time insights, guiding users through complex processes, and reducing manual effort. The solution enables companies to respond to evolving business and regulatory requirements with greater agility, while lowering development time and cost.
What's new in Orchestration AI?
Orchestration AI V11.4 introduces new capability to expose Workflows as MCP tools for AI Agents (available for SaaS offering with Agentic Fabric enabled), new deployment tool for implementation and continued platform improvements.
New features
- Workflows as MCP tools: You can now integrate the workflow engine with AI Agents over standard MCP and enhance agentic solutions.
For details, see this article. - Deployment Set Tool: You can now export and deploy complete implementations using Azure DevOps, shorten the setup time for new implementation releases, and improve the PDLC processes.
For details, see this article. - File Listener with subfolders: You can now configure the File Listener activity to detect new files in subfolders under the source path.
For details, see this article.
General enhancements
- Two-step delete in App Studio: As a workflow developer, you can delete activities and containers only after having those items disconnected and disabled. The first step is to move the items to an intermediate, reversible, state, and allow the permanent deletion as a deliberate second action from that state. Gating the hard delete behind "must be disabled first" serves as a guardrail that prevents one-click destructive actions.
- List Files activity extended data model: As a workflow developer, you can use expressions to check the execution result of the "List Files" activity and inspect the success of the selected command per each file. This is useful for applying conditional logic in workflows based on whether the file operation succeeded or not.
- Automatic removal and duplication of jobs related to listener activities: The system now automatically removes jobs that reference a deleted activity and automatically duplicates a job when its related activity is getting copied or its workflow is getting duplicated. This saves the manual work during development and deployment and ensures system consistency with valid job configuration.
- Visual warning about forced persistence mode: The Administration site homepage now shows a warning when the default persistence mode is forced, so that system owners can quickly identify and responsibly disable this setting to avoid risks of degraded performance and excessive database consumption before it impacts the system.
- Optimized translation for Conversation View: The translation service connection setting now supports optimization that removes embedded images so that the message content will meet the 50K character limit.
- Portal UI refinements: Grid header filter icon was moved to the column menu to allow more space for column header text and improve readability. We also did some general UI alignments for consistent styling.
Resolved issues
| Component | Issue | Ticket # |
|---|---|---|
| In-Process Consumer | Unauthorized exception had an issue when executing the In Process Consumer with "one way" configuration.
In Process consumer with "one way" configuration is now running the invoked workflow on a parallel OS thread. This has a positive effect on performance. |
- |
| Workflow Export | Duplicate detention of system tables in export packages had issue. | - |
| Attachment View | The file name filter had an issue. | - |
| Manage Organization | Issue with showing HTML encoded white space characters in user name fields. | 5460676 |
Known issue
For details, see this article.
Breaking changes
- Exporting solutions: Note that the solution package (export) was changed to include only the reference to a ConfigSet, instead of the content of the ConfigSet object.
- This resolves unexpected overrides of ConfigSet documents.
- The expected usage is to export Solution and ConfigSet items separately and then deploy them per need.
- Limitation of form Grid export functionality on AKS: The built-in export functionality of the form Grid control to Xlsx format is not available on AKS deployments (SaaS offering).
For available workarounds, see this article. - FTP file connection deprecation: FTP is being deprecated as a supported file connection type due to its inherently low security profile, in line with industry trends moving away from this protocol.
- The Administration App UI now displays a deprecation warning wherever FTP connections are configured.
- FTP connections remain functional in this release; however, availability is no longer guaranteed, and feature parity with other storage types will not be maintained going forward. FTP support is expected to be removed in a future release.
- Action required: Migrate any existing FTP-based implementations to a supported file connection type as soon as possible to avoid service disruption.
Limitations
The Deployment Set feature in the Phase 1 (V11.4) release has some known technical limitations.
Refer to the Limitations and workarounds section in the article to understand current behavior and recommended workarounds.
Deployment
Download the release package from the Orchestration AI repository.
NOTE
If the files you are looking for are not in the repository, then contact Support to get access to the new repository location and to obtain credentials to access the repository.
There are six pre-built application deployment packages available, depending on the type of application that you are deploying. You install each Orchestration AI application separately.
| Site applications | Service applications |
|---|---|
|
|
Click here to see how to deploy pre-built applications.
For more details on installing and deploying applications, see this article.
Check if you need to upgrade your database for this version.
For more information on database upgrade and post-upgrade procedures, see this article.
Before upgrade, make sure that you update the PowerShell modules to the relevant version.
For more information, see this article.
Click here to view a sample PowerShell script. Consider this sample for reference only, and do not copy paste from it.
IMPORTANT
Use Microsoft SQL Server Developer Edition for development purposes only.
During upgrade, all product application folders are deleted and redeployed:
- Web and App config files are overwritten in each release. You need to reapply your custom configuration settings after the upgrade.
- All custom files located in the application folders are also deleted. Custom files should be packaged as a custom application NuGet.
Files in the central configuration location are not changed.
For more details, see this article.
For details on Orchestration AI platform support, see this article.
