---
id: post/thinkaboutit-be/7061
type: post
title: "Quick Tip: Say Goodbye to OData on Microsoft Pages in Business Central 2027 Wave 1 (version 30.0)"
summary: 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.
tier: community
language: en
tags:
  - odata
  - api design
  - deprecation
  - integration patterns
  - migration
  - extensibility
system: integration
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:00:16.469Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-post: 1
  input_hash: 1ee998b0c16010173c3ca6296c12a400af5100ff07fcb8eb15a35c2b746b5219
evidence:
  - kind: blog
    url: https://thinkaboutit.be/2025/08/quick-tip-say-goodbye-to-odata-on-microsoft-pages-in-business-central-2027-wave-1-version-30-0/
    title: "Quick Tip: Say Goodbye to OData on Microsoft Pages in Business Central 2027 Wave 1 (version 30.0)"
    date: "2025-08-04"
    commit: null
    t: null
    quote: null
  - kind: blog
    url: https://thinkaboutit.be/2025/08/quick-tip-say-goodbye-to-odata-on-microsoft-pages-in-business-central-2027-wave-1-version-30-0/
    title: "Quick Tip: Say Goodbye to OData on Microsoft Pages in Business Central 2027 Wave 1 (version 30.0)"
    date: "2025-08-04"
    commit: null
    t: null
    quote: UI pages are designed for human interaction - not for stable, long-term integration. They can change between releases without warning.
  - kind: blog
    url: https://thinkaboutit.be/2025/08/quick-tip-say-goodbye-to-odata-on-microsoft-pages-in-business-central-2027-wave-1-version-30-0/
    title: "Quick Tip: Say Goodbye to OData on Microsoft Pages in Business Central 2027 Wave 1 (version 30.0)"
    date: "2025-08-04"
    commit: null
    t: null
    quote: You cannot expose any Microsoft-authored page from apps like Base Application, System Application, or other first-party apps as an OData endpoint.
  - kind: blog
    url: https://thinkaboutit.be/2025/08/quick-tip-say-goodbye-to-odata-on-microsoft-pages-in-business-central-2027-wave-1-version-30-0/
    title: "Quick Tip: Say Goodbye to OData on Microsoft Pages in Business Central 2027 Wave 1 (version 30.0)"
    date: "2025-08-04"
    commit: null
    t: null
    quote: This change is part of a broader effort to make Business Central integrations more robust, predictable, and future-proof.
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
post_id: "7061"
source_id: thinkaboutit-be
source_name: think about IT - Steven Renders
url: https://thinkaboutit.be/2025/08/quick-tip-say-goodbye-to-odata-on-microsoft-pages-in-business-central-2027-wave-1-version-30-0/
published_at: "2025-08-04T08:52:19.000Z"
author: Steven Renders
full_text: false
words: 253
quotes:
  - text: UI pages are designed for human interaction - not for stable, long-term integration. They can change between releases without warning.
    why_it_matters: Explains why exposing pages as OData endpoints is fragile and leads to broken integrations with new releases
  - text: You cannot expose any Microsoft-authored page from apps like Base Application, System Application, or other first-party apps as an OData endpoint.
    why_it_matters: States the core enforcement rule in version 30.0 that developers must prepare for
  - text: This change is part of a broader effort to make Business Central integrations more robust, predictable, and future-proof.
    why_it_matters: Clarifies Microsoft's intent to improve integration stability by enforcing clear separation between UI and API layers
code_objects_mentioned: []
systems:
  - integration
  - development
  - platform
versions_mentioned:
  - "30.0"
  - 2027 Wave 1
preview:
  embeddable: true
  frame_url: https://thinkaboutit.be/2025/08/quick-tip-say-goodbye-to-odata-on-microsoft-pages-in-business-central-2027-wave-1-version-30-0/embed/
  image: https://i0.wp.com/thinkaboutit.be/wp-content/uploads/2025/08/NoODATA.jpg?fit=1200%2C800&ssl=1
  image_alt: null
  image_w: 1200
  image_h: 800
  site_name: think about IT
  favicon: https://i0.wp.com/thinkaboutit.be/wp-content/uploads/2026/02/cropped-SiteIcon2-1.png?fit=32%2C32&ssl=1
  probed_at: "2026-10-07T11:51:29.353Z"
---

# Quick Tip: Say Goodbye to OData on Microsoft Pages in Business Central 2027 Wave 1 (version 30.0)

[Read the post](https://thinkaboutit.be/2025/08/quick-tip-say-goodbye-to-odata-on-microsoft-pages-in-business-central-2027-wave-1-version-30-0/) · think about IT - Steven Renders (Steven Renders) · 2025-08-04 · 253 words · tier community · reviewed (checked by Opus)

> 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.

## 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.