Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Users, automatically | Oct 2025 | Oct 2025 |
Business value
With the introduction of the interactive Copilot as well as agent features and capabilities, both from Microsoft and partners, it can be a challenge to get an overview of which of these are billed based on consumption and by who. To help, we're introducing a new Billing Type column in the Copilot and Agent Capabilities page, indicating whether consumption billing is handled by Microsoft or a partner, or if the feature isn't consumption-billed.
Feature details
A new Billing Type column is added in the Copilot and Agent Capabilities page. This indicates whether consumption is billed by Microsoft, custom-billed by a partner, or not consumption-billed. A capability can be billed by Microsoft either if it's delivered by Microsoft, or if the partner building the capability has chosen to opt in to using Business Central AI resources. Learn more in Business Central AI resources.
The following example shows billing types for various capabilities. Note that the individual billing type for the example capabilities is subject to change in the future.
The billing information is set up manually by the app developer—it's not automatically inferred at runtime. Therefore, it's up to the developer to ensure that the correct billing type is set in the app and also corresponds to what actually happens. The billing type can be set in the RegisterCapability() and ModifyCapability() procedures.
At runtime, the billing type setting is validated against which Azure OpenAI resources the capability actually tries to use. Partners will likely use their own Azure OpenAI subscription during development, testing, and troubleshooting, but might opt in to use Business Central AI resources in customer production environments. Therefore, there may be some inconsistency in the defined billing type for the app versus the actual API call to Azure OpenAI in sandboxes.
The following table summarizes the supported combinations. If the combination isn't allowed, the user gets an error message that usage of AI resources isn't authorized with the chosen billing type.
Learn more on managing consumption-based billing.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.
Tell us what you think
Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at https://aka.ms/bcideas.