Available stack versions
New Opsflw Managed Elasticsearch Platform deployments use Elastic Stack 9.5.0. The Azure Marketplace deployment experience does not provide a stack version selector. The approved version is part of the managed platform release, not a capacity, topology, or Marketplace plan choice.
Available version for new deployments
| Deployment type | Elastic Stack version | Availability |
|---|---|---|
| New managed deployment | 9.5.0 | Current approved version |
| Existing managed deployment | Deployment-specific | Check the deployed version before planning a change |
The stack version applies to Elasticsearch, Kibana, Fleet Server, Elastic Agent, the Elastic Distribution of OpenTelemetry Collector, Logstash, and Elastic connectors when those components are included in the deployment. A component can have its own release cycle, but Opsflw validates the managed combination rather than offering independent component version selection.
Note
The version policy for Elastic Cloud Hosted does not apply to this Azure managed application. In particular, do not assume that every non-EOL release or the latest two minor releases can be selected for a new deployment.
How versions become available
A new Elastic release is not automatically available in the managed platform. Before changing the new-deployment target, Opsflw validates the coordinated component versions, upgrade sequence, recovery evidence, known issues, and representative platform functions. The approved version is then applied to new deployments and recorded on this page.
Release candidates and other pre-GA builds are not available as Marketplace deployment choices. Use a separately approved non-production process if Opsflw support asks you to validate a preview build.
Check an existing deployment
Do not infer an existing deployment's version from this page. Record the exact versions from the managed application deployment details and from the product:
- use
GET /or an approved Kibana view for Elasticsearch; - use the Kibana help or status view for Kibana;
- check Fleet for Elastic Agent and integration versions;
- record the managed platform version from deployment details or outputs.
Use compatibility to validate clients, integrations, features, and licenses against that deployment baseline.
Plan a version change
Existing deployments do not change merely because the version for new deployments changes. Use only the managed upgrade or maintenance process approved for your deployment. Do not upgrade Elasticsearch, Kibana, Elastic Agent, or managed Kubernetes resources directly.
Before an upgrade:
- Record the current versions and target version.
- Review Elastic breaking changes, known issues, and client compatibility for the complete path.
- Verify a recent successful snapshot and recovery plan.
- Test representative ingestion, search, dashboards, authentication, and integrations in non-production.
- Agree on the maintenance window, validation owner, and recovery decision.
Follow prepare for upgrades for the complete checklist. Elasticsearch does not support downgrades; recovery is a managed service decision rather than a package rollback.
Maintenance and end of life
Availability in this managed platform does not extend Elastic's maintenance or support period. Review the Elastic version maintenance and support policy when planning a deployment or upgrade. If the deployed version is approaching the end of its maintenance or support period, contact Opsflw support to plan a supported target and maintenance path.