MWPRO IMPACT SCORE
OPERATIONAL IMPACT
63
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
The wildcard column setting for Power Pages Web API will no longer be supported after 14 September 2026, with removal starting soon after. Admins must review all sites using this configuration, define explicit fields, and validate functionality or request exemptions. This requires configuration changes and testing but is mostly invisible to end users, making admin effort and urgency high with minimal direct user impact.
78
Admin Impact
15
User Impact
72
Urgency
70
Effort
WHAT YOU NEED TO KNOW
AT A GLANCE
Wildcard (*) support in Power Pages Web API fields settings ends soon. Use explicit column lists to avoid unexpected data exposure and service issues.
END USERS
No major end-user change expected.
IT ADMINS
Update any sites using wildcard (*) to explicit column lists before 14 September 2026 or request an exemption.
ROLLOUT TIMELINE
Upcoming:
14 September 2026
14 September 2026
📢 Official Microsoft Message Center Announcement
Power Pages – Information regarding the end of support for the web API wildcard value
Message ID: MC1469940
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.
Source: Microsoft Message Center • Analysed by MWPro
