Compatibility
The deployed managed application is authoritative for its platform and Elastic versions. Do not select a client, Agent, integration, or feature from the documentation site's publication date.
Record the deployment baseline
| Surface | Authoritative location | Required check |
|---|---|---|
| Managed platform | Managed application outputs or deployment details | Record the platform version exposed by the deployment |
| Elasticsearch | GET / or an approved Kibana view |
Record the exact Elasticsearch version |
| Kibana | Kibana help or status view | Confirm it matches the managed stack |
| Elastic Agent and Fleet | Fleet compatibility guidance for the deployed stack | Confirm both the Agent and integration package versions |
| OpenTelemetry | Elasticsearch and Collector documentation for the deployed versions | Confirm OTLP protocol, paths, exporter, and semantic-convention behavior |
| Azure region and plan | Approved Marketplace offer | Confirm the selected plan is available in the deployment region |
| Elastic license | Kibana license view or supported managed action | Confirm that every required feature is entitled |
Apply the compatibility rule
Before enabling a feature or changing a component:
- record the exact deployed versions;
- read the corresponding Elastic compatibility and upgrade guidance;
- confirm the feature is exposed by the managed application;
- test the change with representative non-production data;
- record rollback and support ownership.
The documentation intentionally does not publish an unverified global version matrix. A platform release must add its approved version range here before the release is described as supported.
See release notes for documentation changes and prepare for upgrades for managed upgrade planning.