MC1457694 Medium
Power Pages- Information regarding the end of support for Wildcard (*) in the Web API field configuration
Summary AI-generated
Wildcard (*) support in Power Pages Web API field configuration ends September 14, 2026; specify columns explicitly to ensure continued access and avoid HTTP 403 errors.
Suggested actions AI-generated
- Review tables exposed via Power Pages Web API.
- Replace wildcard (*) with explicit columns list in Webapi/<table>/fields.
- Validate website functionality after configuration update.
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1265724 Power Pages – Control Power Pages components using client APIs
- MC1224376 Power Pages – Control Power Pages components using client APIs
- MC1551122 Power Platform - Information regarding the end of support for SharePoint temporary authentication URLs
- MC1217651 Power BI: End of support for on-prem SharePoint web part
- MC1474128 Power Platform - Information regarding the end of support for Global Discovery Service (GDS) API
- MC1253577 Power Platform - Information regarding the end of support for Global Discovery Service (GDS) API
Original post from Microsoft
Starting on September 14, 2026, Wildcard (*) in the Web API field configuration will have reached end of support.
How does this affect me?
After September 14, 2026, support for the Wildcard value (*) in the Web API field configuration will be removed in phases over the following weeks.
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 details, please refer to Power Pages portals Web API overview.
What action do I need to take?
If your websites currently use the wildcard value (*) in any Webapi//fields site setting, please perform the below steps:
Please contact Microsoft support if you need further assistance.
How does this affect me?
After September 14, 2026, support for the Wildcard value (*) in the Web API field configuration will be removed in phases over the following weeks.
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/
What action do I need to take?
If your websites currently use the wildcard value (*) in any Webapi/
- 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's functionality after updating the configuration.
Please contact Microsoft support if you need further assistance.