Quick Tip: Say Goodbye to OData on Microsoft Pages in Business Central 2027 Wave 1 (version 30.0)
Starting with Business Central version 30.0 (2027 Wave 1), Microsoft no longer allows exposing Microsoft-authored pages as OData endpoints. Developers using UI pages for integrations must migrate to custom extensions, query objects, or purpose-built APIs to maintain connectivity and ensure long-term stability.

post think about IT
"UI pages are designed for human interaction - not for stable, long-term integration. They can change between releases without warning."
Key points
- Microsoft-authored pages from Base Application and System Application cannot be exposed as OData endpoints in version 30.0
- UI pages are designed for human interaction and change between releases, making them unsuitable for stable integrations
- Developers must audit current integrations, migrate to custom extensions or query objects, and design purpose-built APIs
- This change enforces separation between user interface and API layers for more robust and predictable integrations
Quotes
- “UI pages are designed for human interaction - not for stable, long-term integration. They can change between releases without warning.” (Explains why exposing pages as OData endpoints is fragile and leads to broken integrations with new releases)
- “You cannot expose any Microsoft-authored page from apps like Base Application, System Application, or other first-party apps as an OData endpoint.” (States the core enforcement rule in version 30.0 that developers must prepare for)
- “This change is part of a broader effort to make Business Central integrations more robust, predictable, and future-proof.” (Clarifies Microsoft’s intent to improve integration stability by enforcing clear separation between UI and API layers)
Context
- Features: OData endpoints, Microsoft-authored pages, Query Objects, Query APIs, Per-tenant extensions
- Versions: 30.0, 2027 Wave 1
Source: think about IT - Steven Renders, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.