4

Idea / Suggestion

Currently, customers who want to evaluate Power Pages may use a Developer environment when they do not have enough Dataverse database capacity to create a Production or Sandbox environment. This can help them start building and testing a Power Pages site.

However, when the customer later tries to apply a custom domain, they may be required to use a different environment type. This creates confusion and additional complexity, especially for small businesses or non-technical customers who are only trying to evaluate whether Power Pages is suitable for their business.

It would be very helpful if Microsoft could provide one of the following improvements:

  1. Allow custom domain testing in Developer environments for evaluation purposes, possibly with clear limitations.
  2. Provide a simplified Power Pages evaluation environment that supports custom domain testing without requiring the customer to first meet the full Production/Sandbox Dataverse capacity requirement.
  3. Improve the product messaging so customers clearly understand environment limitations before they invest time building the site.
  4. Provide clearer guidance in the Power Pages setup flow explaining which environment types support custom domains and what capacity/licensing requirements are needed.

Business Impact

This limitation can create friction during product evaluation. In this case, the customer was evaluating Microsoft 365 and Power Pages for business use. The customer was able to move forward after using a Developer environment, but later found that applying a custom domain required a different environment. Because the setup became too complex, the customer decided to abandon the use of Power Pages and cancel the purchase.

For small businesses, a difficult or unclear trial experience may lead to product abandonment before the customer can fully understand the value of Power Pages.


Current Behavior

A customer without sufficient Dataverse database capacity may be unable to create a Production or Sandbox environment with Dataverse enabled due to the 1 GB capacity requirement. A Developer environment can be used as an alternative for initial testing, but custom domain setup may require a different environment type.


Expected Behavior

Customers should have a simple and clear path to evaluate Power Pages end to end, including custom domain testing, without needing advanced environment or capacity knowledge. If custom domains are not supported in Developer environments, the product should clearly explain this limitation earlier in the setup process and provide a recommended path for trial/evaluation scenarios.


Why this matters

Power Pages is often evaluated by small businesses or non-technical users who want to quickly test whether the product can meet their website needs. A smoother evaluation experience would reduce confusion, improve adoption, and help prevent customers from abandoning Power Pages due to environment and capacity complexity.

Category: Dataverse
STATUS DETAILS
New

Comments

L

Good idea, highly recommend this suggestion idea to be implemented in Microsoft product in the future.

Category: Dataverse

L

Strongly agree with this suggestion. I’ve seen the same confusion multiple times from customers during evaluation.The current experience creates a disconnect between “what you can build” and “what you can actually validate end‑to‑end.” Customers are able to invest time building a Power Pages site in a Developer environment, but only later discover that key scenarios like custom domain configuration require a different environment type. This feels like a hidden constraint rather than an intentional design, especially for non-technical users.

Category: Dataverse