Skip to content

Commit f6ebbeb

Browse files
authored
Merge pull request #307086 from v-thpra/ff-488533-azure-apimgmt-009
Freshness - Azure API Management Center - 009
2 parents f3b2af8 + 3b6e99b commit f6ebbeb

3 files changed

Lines changed: 13 additions & 19 deletions

File tree

articles/api-management/quickstart-arm-template.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Quickstart - Create Azure API Management instance - ARM template
2+
title: Quickstart - Create Azure API Management Instance - ARM Template
33
description: Use this quickstart to create an Azure API Management instance in the Developer tier by using an Azure Resource Manager template (ARM template).
44
services: azure-resource-manager
55
author: dlepow
66
ms.service: azure-api-management
77
ms.topic: quickstart-arm
88
ms.author: danlep
9-
ms.date: 03/25/2024
9+
ms.date: 10/17/2025
1010
ms.custom:
1111
- subject-armqs
1212
- mode-arm
@@ -24,7 +24,7 @@ This quickstart describes how to use an Azure Resource Manager template (ARM tem
2424

2525
[!INCLUDE [About Azure Resource Manager](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-introduction.md)]
2626

27-
If your environment meets the prerequisites and you're familiar with using ARM templates, select the **Deploy to Azure** button. The template will open in the Azure portal.
27+
If your environment meets the prerequisites and you're familiar with using ARM templates, select the **Deploy to Azure** button. The template opens in the Azure portal.
2828

2929
:::image type="content" source="~/reusable-content/ce-skilling/azure/media/template-deployments/deploy-to-azure-button.svg" alt-text="Button to deploy the Resource Manager template to Azure." border="false" link="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.apimanagement%2Fazure-api-management-create%2Fazuredeploy.json":::
3030

@@ -56,7 +56,7 @@ More Azure API Management template samples can be found in [Azure Quickstart Tem
5656
- **Subscription**: select an Azure subscription.
5757
- **Resource group**: select **Create new**, enter a unique name for the resource group, and then select **OK**.
5858
- **Region**: select a location for the resource group. Example: **Central US**.
59-
- **Publisher Email**: enter an email address to receive notifications.
59+
- **Publisher Email**: enter an email address for receiving notifications.
6060
- **Publisher Name**: enter a name you choose for the API publisher.
6161
- **Sku**: accept the default value of **Developer**. Alternatively, choose another value.
6262
- **Sku Count**: accept the default value.
@@ -69,7 +69,7 @@ More Azure API Management template samples can be found in [Azure Quickstart Tem
6969
> [!TIP]
7070
> It can take between 30 and 40 minutes to create and activate an API Management service in the Developer tier. Times vary by tier.
7171
72-
1. After the instance has been created successfully, you get a notification:
72+
1. After the instance is successfully created, you get a notification:
7373

7474
:::image type="content" source="media/quickstart-arm-template/deployment-notification.png" alt-text="Deployment notification":::
7575

@@ -95,6 +95,7 @@ If you plan to continue working with subsequent tutorials, you might want to lea
9595
1. On the resource group page, select **Delete resource group**.
9696

9797
:::image type="content" source="media/quickstart-arm-template/delete-resource-group.png" alt-text="Delete resource group":::
98+
9899
1. Type the name of your resource group, and then select **Delete**.
99100

100101
## Next steps

articles/api-management/security-controls-policy.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,18 @@
11
---
2-
title: Azure Policy Regulatory Compliance controls for Azure API Management
2+
title: Azure Policy Regulatory Compliance Controls for Azure API Management
33
description: Lists Azure Policy Regulatory Compliance controls available for Azure API Management. These built-in policy definitions provide common approaches to managing the compliance of your Azure resources.
4-
ms.date: 03/18/2024
4+
ms.date: 10/17/2025
55
ms.topic: sample
66
author: dlepow
77
ms.author: danlep
88
ms.service: azure-api-management
99
ms.custom: subject-policy-compliancecontrols
1010
---
11-
# Azure Policy Regulatory Compliance controls for Azure API Management
12-
11+
# Azure Policy Regulatory Compliance controls for Azure API Management2
1312
[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
1413

1514
[Regulatory Compliance in Azure Policy](../governance/policy/concepts/regulatory-compliance.md)
16-
provides Microsoft created and managed initiative definitions, known as _built-ins_, for the
17-
**compliance domains** and **security controls** related to different compliance standards. This
18-
page lists the **compliance domains** and **security controls** for Azure API Management. You can
19-
assign the built-ins for a **security control** individually to help make your Azure resources
20-
compliant with the specific standard.
15+
provides Microsoft created and managed initiative definitions, known as _built-ins_, for the **compliance domains** and **security controls** related to different compliance standards. This page lists the **compliance domains** and **security controls** for Azure API Management. You can assign the built-ins for a **security control** individually to help make your Azure resources compliant with the specific standard.
2116

2217
[!INCLUDE [azure-policy-compliancecontrols-introwarning](../../includes/policy/standards/intro-warning.md)]
2318

articles/reliability/reliability-api-center.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,9 @@ ms.author: danlep
66
ms.topic: reliability-article
77
ms.custom: subject-reliability
88
ms.service: azure-api-management
9-
ms.date: 04/15/2024
9+
ms.date: 10/17/2025
1010
---
1111

12-
1312
# Reliability in Azure API Center
1413

1514
This article describes reliability support in Azure API Center, including availability zones, zone redundancy, data residency, and what customers should expect during zone or regional outages. For a more detailed overview of reliability in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
@@ -20,14 +19,13 @@ This article describes reliability support in Azure API Center, including availa
2019

2120
In each [region](../api-center/overview.md) where it's available, Azure API Center supports zone redundancy by default. The Azure API Center service runs in a multitenant environment on availability zone-enabled components. You don't need to set it up or reconfigure for availability zone support.
2221

23-
2422
### Zone down experience
2523

26-
During a zone-wide outage, the customer should expect a brief degradation of performance, until the service's self-healing rebalances underlying capacity to adjust to healthy zones. This isn't dependent on zone restoration; it's expected that the Microsoft-managed service self-healing state compensates for a lost zone, using capacity from other zones.
24+
During a zone-wide outage, the customer should expect a brief degradation of performance, until the service's self-healing rebalances underlying capacity to adjust to healthy zones. This period of performance degradation isn't dependent on zone restoration; the Microsoft-managed service self-healing state is expected to compensate for a lost zone, by using capacity from other zones.
2725

2826
## Cross-region disaster recovery limitations
2927

30-
Currently, Azure API Center supports only a single-region configuration. There is no capability for automatic or customer-enabled cross-region failover for Azure API Center. Should a regional disaster occur, the service will be unavailable until the region is restored.
28+
Currently, Azure API Center supports only a single-region configuration. There's no capability for automatic or customer-enabled cross-region failover for Azure API Center. Should a regional disaster occur, the service is unavailable until the region is restored.
3129

3230
## Data residency
3331

0 commit comments

Comments
 (0)