Skip to content

Commit 62a1997

Browse files
committed
improved title and description, updated filename and paths
1 parent 1eed7dd commit 62a1997

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

articles/api-management/deploy-service-updates.md renamed to articles/api-management/validate-service-updates.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
11
---
2-
title: Safely deploy Azure API Management service updates
3-
description: Apply the Azure safe deployment approach with your Azure API Management instances to validate service updates before they reach your production environments.
2+
title: Validate Azure API Management service updates
3+
description: Apply the Azure safe deployment approach with your Azure API Management instances to validate service updates and avoid disruptions to your production environments.
44
author: dlepow
55
ms.service: api-management
66
ms.topic: how-to
77
ms.date: 02/25/2022
88
ms.author: danlep
99
---
1010

11-
# Deploy service updates safely to your API Management instances
11+
# Validate service updates to avoid disruption to your production API Management instances
1212

1313
*"One of the value propositions of the cloud is that it’s continually improving, delivering new capabilities and features, as well as security and reliability enhancements. But since the platform is continuously evolving, change is inevitable." - Mark Russinovich, CTO, Azure*
1414

15-
Microsoft uses a *safe deployment practices framework* to thoroughly test, monitor, and validate service updates, and then deploy them to Azure regions using a phased approach. Even so, service updates that reach your API Management instances could introduce unanticipated risks to your production workloads and disrupt your API consumers. Learn how you can apply our safe deployment approach to reduce risks by validating the updates before they reach your production API Management environments.
15+
Microsoft uses a safe deployment practices framework*\ to thoroughly test, monitor, and validate service updates, and then deploy them to Azure regions using a phased approach. Even so, service updates that reach your API Management instances could introduce unanticipated risks to your production workloads and disrupt your API consumers. Learn how you can apply our safe deployment approach to reduce risks by validating the updates before they reach your production API Management environments.
1616

1717
## What is the Azure safe deployment practices framework?
1818

1919
Azure deploys updates for a given service in a series of pre-production and production steps using a [safe deployment practices (SDP) framework](https://azure.microsoft.com/blog/advancing-safe-deployment-practices/). This framework is shown in simplified form in the following image:
2020

21-
:::image type="content" source="media/deploy-service-updates/azure-sdp-framework.png" alt-text="Safe deployment practices framework":::
21+
:::image type="content" source="media/validate-service-updates/azure-sdp-framework.png" alt-text="Safe deployment practices framework":::
2222

2323
Deployment phases include:
2424

@@ -60,7 +60,7 @@ As a first step, ensure that you know about service updates that are expected or
6060

6161
* Monitor service updates that are taking place in your API Management instance by using the Azure [Activity log](../azure-monitor/essentials/activity-log.md). The "Scheduled maintenance" event is emitted when an update begins.
6262

63-
:::image type="content" source="media/deploy-service-updates/scheduled-maintenance.png" alt-text="Scheduled maintenance event in Activity log":::
63+
:::image type="content" source="media/validate-service-updates/scheduled-maintenance.png" alt-text="Scheduled maintenance event in Activity log":::
6464

6565
To receive notifications automatically, [set up an alert](../azure-monitor/alerts/alerts-activity-log.md) on the Activity log.
6666

0 commit comments

Comments
 (0)