Skip to content

Commit cc71304

Browse files
Update routine-maintenance.md
1 parent 71170ee commit cc71304

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/app-service/routine-maintenance.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Since a typical cloud solution consists of multiple applications, databases, sto
2727

2828
[Safe deployment practices - Azure DevOps | Microsoft Learn](/devops/operate/safe-deployment-practices)
2929

30-
:::image type="content" source="/media/routine-maintenance/routine-maintenance.png" alt-text="A sample maintenance event in the Azure Portal":::
30+
:::image type="content" source="./media/routine-maintenance/routine-maintenance.png" alt-text="Screenshot of a maintenance event in the Azure Portal":::
3131

3232
In order from top to bottom we see:
3333
- A descriptive title of the maintenance event
@@ -46,7 +46,7 @@ A typical scenario is that customers have multiple applications, and they are up
4646

4747
### How is routine maintenance related to SLA?
4848

49-
Platform maintenance isn't expected to impact application uptime or availability. Applications continue to stay online while platform maintenance occurs. Platform maintenance may cause applications to be cold started on new virtual machines, which can lead to cold start delays. An application is still considered to be online, , even while cold-starting. For best practices to minimize/avoid cold starts, consider using [local cache for Windows apps](overview-local-cache.md) as well as [Health check](monitor-instances-health-check.md). It's not expected that sites would incur any SLA violation during maintenance windows.
49+
Platform maintenance isn't expected to impact application uptime or availability. Applications continue to stay online while platform maintenance occurs. Platform maintenance may cause applications to be cold started on new virtual machines, which can lead to cold start delays. An application is still considered to be online, even while cold-starting. For best practices to minimize/avoid cold starts, consider using [local cache for Windows apps](overview-local-cache.md) as well as [Health check](monitor-instances-health-check.md). It's not expected that sites would incur any SLA violation during maintenance windows.
5050

5151
### How does the upgrade work how does it ensure the smooth operation of my apps?
5252

@@ -58,7 +58,7 @@ Maintenance operations are optimized to run outside standard business hours (9-5
5858

5959
### What are my options to control routine maintenance?
6060

61-
If you run your workloads in Isolated SKU via App Service Environment v3, you can also schedule the upgrades when needed. This is described with details at Control and automate planned maintenance for App Service Environment v3 - Azure App Service .
61+
If you run your workloads in Isolated SKU via App Service Environment v3, you can also schedule the upgrades when needed. This is described with details at Control and automate planned maintenance for App Service Environment v3 - Azure App Service.
6262

6363
### Can I prepare my apps better for restarts?
6464

@@ -68,7 +68,7 @@ If your applications need extra time during restarts to come online (a typical p
6868

6969
Updates and maintenance events have been happening to the platform since its inception. The frequency of updates decreased over time, so the number of interruptions also decreased and uptime increases. However, there is an increased level of visibility into all changes which can cause the perception that more changes are being made.
7070

71-
## Links
71+
## Next steps
7272

7373
[Control and automate planned maintenance for App Service Environment v3 - Azure App Service](https://azure.github.io/AppService/2022/09/15/Configure-automation-for-upgrade-preferences-in-App-Service-Environment.html)
7474

0 commit comments

Comments
 (0)