Hi Team,

This is the idea from Jerry C.W. Wang(王嘉煒):

Scenario

We are evaluating the use of Copilot Studio and have identified a product design concern related to the current dependency on a Dataverse-enabled environment for core Copilot Studio usage.

During our investigation, we understood that Dataverse is currently a key dependency for creating and operating Copilot Studio agents in many scenarios, and that environments used for agent creation generally require a Dataverse data store or database to be available.

From the customer perspective, this introduces additional environment planning, governance, and operational considerations. It also creates extra complexity for organizations that would prefer to adopt Copilot Studio in a lighter-weight manner without needing to enable Dataverse in the target environment. In some cases, this also leads to additional Azure subscription considerations as part of the broader customer environment design, which may not always align with the customer’s preferred deployment model.

At the moment, there does not appear to be a straightforward supported way to use Copilot Studio without having Dataverse enabled in the environment for the relevant scenarios we reviewed. As a result, customers who want to use Copilot Studio in a more minimal or simplified architecture have limited options.

Expected behavior

We expect Copilot Studio to support a configurable or supported method to:

Allow customers to use Copilot Studio in selected scenarios without requiring Dataverse to be enabled in the environment Provide a simpler deployment option for customers who do not need Dataverse-backed capabilities Reduce environment setup complexity for organizations that want to adopt Copilot Studio with a lighter operational footprint Provide a supported and operationally manageable design for this scenario without requiring customers to enable Dataverse when it is not needed for their intended use case

Actual result

Copilot Studio usage is closely tied to environments that have a Dataverse data store. If an environment does not have a Dataverse enabled, it may not appear as usable for agent creation in Copilot Studio until the database is created. There is no clear supported product capability to allow customers to use Copilot Studio in a way that avoids this Dataverse dependency for the scenarios we reviewed

As a result, customers are unable to adopt Copilot Studio in a simplified environment model without enabling Dataverse, even when their intended business scenario may not require broader Dataverse-backed functionality.

Ask

Could the Product Group consider a future enhancement so that:

• Customers can optionally use Copilot Studio for suitable scenarios without requiring Dataverse to be enabled in the environment
• Organizations can adopt a supported lightweight design pattern for Copilot Studio where full Dataverse enablement is not necessary Administrators have a clearer and more manageable way to deploy Copilot Studio in environments where they want to minimize setup, governance, and operational overhead
• Customers have more flexibility to align Copilot Studio deployment with their environment strategy and architecture preferences

This enhancement would help customers reduce implementation complexity, improve deployment flexibility, and avoid being forced into a broader platform dependency when their scenario may not require it.

Thank you for your help.