MWPRO IMPACT SCORE
OPERATIONAL IMPACT
68
0
25
50
75
100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
Review the update and plan any required actions before rollout.
What is MWPro Impact Score?
Watch our 60‑second explainer
Primary Audience
Power Platform AdminsDevelopersIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
Wildcard use in Power Pages Web API will stop being supported from 14 September 2026, with phased enforcement resulting in HTTP 403 errors if configurations are not updated. Admins must identify and replace * entries with explicit column lists and validate functionality, which is a significant configuration change. User impact is indirect but noticeable if apps relying on wildcard fail. Urgency is high due to a firm deadline and risk of broken workflows.
80
Admin Impact
35
User Impact
70
Urgency
75
Effort
WHAT YOU NEED TO KNOW
AT A GLANCE
Wildcard (*) in Web API field configuration for Power Pages will no longer be supported. You’ll need explicit column lists for security and to avoid failures.
END USERS
Users may see features break if sites rely on Web API requests using Wildcard (*).
IT ADMINS
Replace any Wildcard (*) configurations with explicit column lists and validate your builds before enforcement.
ROLLOUT TIMELINE
Upcoming:
September 14, 2026
September 14, 2026
📢 Official Microsoft Message Center Announcement
Power Pages- Information regarding the end of support for Wildcard (*) in the Web API field configuration
Message ID: MC1457694
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:
- 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.
Source: Microsoft Message Center • Analysed by MWPro
