Understand Interactive Application Object Server (AOS) restarts

The interactive Application Object Server (AOS) might be restarted for several reasons. Here's an overview of these reasons:

• Routine maintenance activities – During routine maintenance activities, such as patching, there might be temporary interruptions to AOS services. To understand the effect of maintenance activities and access-known maintenance schedules, see the following articles:

  • Operating System Maintenance Schedule – Learn more about planned operating system maintenance schedules.
  • Experience during the nZDT Maintenance Window – Gain insights into system behavior during the nZDT maintenance window.

• Interactive AOS server failures ("crashes") – Failures on Interactive servers might occur because of application services that are currently running. Detailed failure information is available in Microsoft Dynamics Lifecycle Services. For more information about how to monitor failure information, see Monitoring and telemetry using Application Insights.

• Infrastructure failover – Restarts can occur if infrastructure issues lead to an internal failover. Autoscaling and capacity management are used to ensure optimal environmental performance and availability.