Submitting a Release
Your application is the listing customers browse. A release is one version of it. You create the application once, then add a release each time you have a new version to publish.
Both live under App Store → App management in the Console.
1. Create the application
Create new app asks for one thing: the name.
Once created, this name cannot be changed or edited in the future.
Everything else about the application — its listing, description and category — you can edit later. Check the spelling and capitalisation before you select Create app.
A new application starts as a draft with no releases, and is not visible to customers until a release of it is published.
2. Add a release
Create new release takes everything about the version in one dialog.
General information
| Field | Notes |
|---|---|
| Release name | A label so you can tell releases apart, for example My App 1.0 launch |
| Bundle version | The version number of this release, for example 1.0.2 |
| Release notes | What is changing in this release |
The Bundle version must be three numbers separated by dots — 1.0.2, not 1.0 — and a version you have not used on this application before.
A failed release stays editable. Correct whatever went wrong — including the chart, the registry or the version itself — and submit it again. You do not need to create a new release or raise the Bundle version to retry.
You need a new Bundle version once a release has been through successfully: versions are unique per application, so publishing 1.0.2 means your next release has to be a different number.
Registry details
Image Registry is a dropdown of the registries already set up for your account, for example <my-registry>.azurecr.io. Its type — ACR, ECR, GCR, Docker Hub — is taken from the registry you pick, so there is nothing else to select.
If your registry is not listed, it has not been connected yet. See Application Secrets Management.
Helm Chart
Where to fetch your chart from:
| Field | Example |
|---|---|
| Chart name | my-chart |
| Repository | <my-registry>.azurecr.io/my-app/helm/my-chart |
| Tag | 1.0.0 |
| Digest | Optional, instead of a tag |
Chart.yaml exactlyTag is compared against the version line inside your chart, character for character. version: 1.0.0 and a Tag of 1.0.0 pass. A Tag of v1.0.0 does not — the leading v makes it a different string.
Tag and Bundle version are separate and need not match each other. Only the Tag has to agree with your chart.
The release page shows both, so you can check them at a glance — here the Bundle version is 1.0.2 while the chart Tag is 1.0.0:
Your chart needs Chart.yaml, values.yaml, and a templates folder, and it has to ask for at least one container image. See Application Packaging.
Customers install your chart as it comes — nobody edits it for them. If it will not start until a setting is changed by hand, it will not start for anyone. Ship defaults that run.
Save draft keeps the release editable. Nothing is checked until you submit.
3. Fill in the listing
The release page has two sections you can edit before submitting.
Release description and package details holds everything from the dialog above, editable again with Edit release — the card shown above.
Marketplace listing is what customers see. Edit listing opens it; Preview shows how it will look.
| Field | Notes |
|---|---|
| App name | Read-only — this is the permanent name from step 1 |
| Subtitle | One line under the name |
| Upload screenshots | Images of your application for the listing |
| App category | How customers find you when browsing |
| Supported platform | Which platforms your application runs on; you can pick more than one |
| Description | What your application does |
The categories are AI & Machine Learning, Compute & Developer Tools, Drilling & Field Operations, Core Operations & Industrial Platforms, Data Platforms & Integration, Safety, Security & Autonomous Operations, Asset Performance & Predictive Maintenance, Digital Twins & Simulation, Emissions & Environmental, and Logistics & Process Automation.
4. Submit for review
Submit for review starts the checks. While they are running, the release is locked — the chart, registry and version cannot be changed. If the checks fail, it unlocks and you can edit and resubmit it. The listing stays editable throughout.
Only one set of checks can run for the same application and version. Submitting again while the first is running is refused.
If a run looks stuck, cancel it rather than submitting again.
The release page then shows how far the checks have got. The last one installs your application for real, so expect it to take about as long as your application takes to start.
See Intake validation for what each check looks for.