Hi
@CU10091842-0,
I would be careful not to treat appUris.documentUri as an App Builder export API.
The current Power Platform inventory documentation does identify App Builder apps as:
type = microsoft.powerapps/apps
properties.subType = appBuilderApp
and exposes inventory metadata such as owner, environment, created/modified information, and quarantine state. However, the documented App Builder resource schema does not describe an API that returns the complete prototype definition, UI structure, data model, actions/logic, etc.
So I would distinguish the two concepts:
Power Platform Admin / Inventory API
↓
App Builder resource metadata
↓
appBuilderApp
↓
ID, owner, environment, timestamps, status...
versus:
App Builder prototype artifact
↓
UI definition
data schema
actions / logic
configuration
other reconstruction metadata
The latter is not currently documented as a supported export/import contract.
In particular, I would not assume that:
properties.appUris.documentUri
is a downloadable, versioned App Builder source artifact simply because it is exposed as a URI. Unless Microsoft explicitly documents that URI as an artifact/export endpoint, consuming it from an external system would be relying on an internal implementation detail.
That also means I wouldn't build an integration around parsing whatever content happens to be returned from documentUri. There is currently no documented schema/versioning contract that would make that a safe programmatic ingestion mechanism.
For the questions in the post, my interpretation would therefore be:
1. Does documentUri provide the complete serialized App Builder app?
There is no current Microsoft documentation establishing that it does.
2. Is consuming it externally supported?
I wouldn't consider it a supported integration unless Microsoft explicitly documents the URI for that purpose.
3. Is the artifact format documented/versioned?
I haven't found a Microsoft-published artifact schema/versioning contract for reconstructing an appBuilderApp.
4. Is there another supported API to export the complete prototype?
I don't see a currently documented Admin/Inventory API that provides the complete App Builder prototype source/artifact. The documented inventory API is intended for resource discovery and administration rather than source export.
5. Roadmap?
I would avoid stating that this is or isn't on the roadmap unless Microsoft has provided a public roadmap item specifically covering App Builder artifact export. I couldn't find a public commitment that would make that claim safe.
If the requirement is for backup, migration, CI/CD, or external programmatic reconstruction, I'd raise this with Microsoft as a product capability request and explicitly ask:
"Is there a supported, documented export format/API for appBuilderApp resources that can be used for programmatic backup and reconstruction?"
That's a better question than asking specifically whether documentUri can be consumed, because it forces clarification of whether Microsoft intends the underlying artifact to be a supported integration surface.
The important takeaway is: being able to discover an App Builder resource through the Power Platform Admin/Inventory API does not imply that its underlying design artifact is exposed as a supported export format. The current published schema supports the former, not the latter.
