Power Pages - Information regarding the end of support for the web API wildcard value

Beginning on September 14, 2026, support for the wildcard value (*) in the Webapi/<table-name>/fields site setting will have reached end of support. After this date, support will be removed in a phased manner in the subsequent weeks.

How does this affect me?
The wildcard (*) configuration exposes all columns in a Dataverse table through the Power Pages Web API. To improve security and align with least-privilege access principles, Power Pages now requires an explicit list of columns to be specified in the Webapi//fields site setting. This change helps prevent unintended exposure of additional columns and provides greater control over data accessible through the Web API. For more information, please refer to Web API Requests Fail After Wildcard Column Deprecation.

What action do I need to take?
If any of your websites currently uses the wildcard value (*) in any Webapi//fields site setting:

• Review the tables exposed through the Power Pages Web API.
• Replace the wildcard value (*) with an explicit comma-separated list of columns that should be accessible.
• Validate your website functionality after updating the configuration.
• Complete these updates before September 14, 2026, to avoid potential disruption when the retirement takes effect.
• If you cannot complete these updates by September 14, 2026, request an extension in the Power Platform Admin Center using the Manage exemptions tool: Manage > Power Pages > Manage exemptions. Review and select the websites that need more time and then confirm your request. A Microsoft Support request is not required. Complete the migration before the extension expires. For more details, refer to Manage Exemptions for Power Pages sites.