Manage maintenance

The deployment can record a maintenance schedule for coordinated platform changes. Use the managed application action only when it is available for the deployed plan.

Prepare for maintenance

1. Confirm the occurrence, weekday, start time, time zone, and duration shown by the deployment.
2. Identify affected users, ingestion pipelines, and client retry behavior.
3. Review service health and active incidents.
4. Verify a recent usable snapshot when the change can affect data.
5. Communicate the expected impact through approved channels.

Update the schedule

1. Open the managed application in the Azure portal.
2. Open the supported maintenance configuration action.
3. Enter the approved schedule and time zone.
4. Review the value carefully; do not infer local time from UTC.
5. Submit the change and record its operation or change identifier.
6. Wait for the action to complete before submitting another schedule change.

Validate afterward

• Elasticsearch cluster health is acceptable.
• Kibana loads and users can authenticate.
• Ingestion and searches have recovered.
• No unexpected certificate, DNS, or license warning is present.
• The managed application shows the intended schedule.

If the maintenance action is missing, the schedule does not update, or service health degrades, collect safe evidence and get support.