ALAppExtensions is being retired - extensibility requests move to BCApps on 1 September 2026

This repository is being retired. Extensibility requests move to BCApps, which is becoming the single home for everything Business Central business application — code, bugs, BC Ideas, and extensibility requests including event requests.

What is changing, and when

What this means for you

Opening a new extensibility request? From 1 September, use BCApps → Create an extensibility request. The form is the same one you know, and requests are triaged by the same team.

Already have an open request here? Do nothing. We will process it in this repository before archiving. You do not need to re-file it in BCApps, and we ask that you don't — duplicates slow triage down for everyone.

Requests we have already accepted but not yet shipped are tracked internally and will be delivered as planned. Archiving this repository does not cancel them.

What happens to the repository

It will be archived, not deleted. Every issue, comment, and link keeps working — including links from Microsoft Learn and existing forks. It simply becomes read-only.

Why

Extensibility requests were the last activity still happening here. Consolidating into BCApps means one place to search, one backlog, and one set of notifications — instead of asking you to know which repository owns which kind of request.

Questions? Comment below while this issue is still open.

Read the issue body and the BCApps issue form linked there; this repository is being retired and no code change is requested. Done means directing any new extensibility request to BCApps and leaving existing requests here for processing before the archive date.