Skip to content

Commit ce99176

Browse files
Learn Build Service GitHub AppLearn Build Service GitHub App
authored andcommitted
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents 8d20378 + 2fa1417 commit ce99176

26 files changed

Lines changed: 311 additions & 554 deletions

articles/api-management/credentials-how-to-user-delegated.md

Lines changed: 47 additions & 44 deletions
Large diffs are not rendered by default.
Lines changed: 22 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,58 +1,59 @@
11
---
2-
title: Edit an API with the Azure portal | Microsoft Docs
3-
description: Learn how to use API Management to edit an API. Add, delete, or rename operations in the APIM instance, or edit the API's swagger.
2+
title: Edit an API in the Azure Portal | Microsoft Docs
3+
description: Learn how to use API Management to edit an API or its swagger.
44
services: api-management
55
author: dlepow
66
ms.service: azure-api-management
77
ms.topic: how-to
8-
ms.date: 01/19/2022
8+
ms.date: 10/07/2025
99
ms.author: danlep
1010
ms.custom: sfi-image-nochange
11+
# Customer intent: As an API developer, I want to use API Management to edit an API or its swagger.
1112
---
1213
# Edit an API
1314

1415
[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
1516

16-
The steps in this tutorial show you how to use API Management to edit an API.
17+
This article describes how to use Azure API Management to edit an API.
1718

1819
+ You can add, rename, or delete operations in the Azure portal.
1920
+ You can edit your API's swagger.
2021

2122
## Prerequisites
2223

2324
+ [Create an Azure API Management instance](get-started-create-service-instance.md)
24-
+ [Import and publish your first API](import-and-publish.md)
25+
+ [Import and publish an API](import-and-publish.md)
2526

2627
[!INCLUDE [api-management-navigate-to-instance.md](../../includes/api-management-navigate-to-instance.md)]
2728

2829
## Edit an operation
2930

30-
![Screenshot that highlights the process for editing an API in API Management.](./media/edit-api/edit-api001.png)
31+
1. Under **APIs**, select **APIs**.
32+
1. Select an API that you have imported.
33+
1. Select the **Design** tab.
34+
1. Select the operation that you want to edit.
35+
1. To rename the operation, select the pencil button in the **Frontend** pane.
3136

32-
1. Click the **APIs** tab.
33-
2. Select one of the APIs that you previously imported.
34-
3. Select the **Design** tab.
35-
4. Select an operation, which you want to edit.
36-
5. To rename the operation, select a **pencil** in the **Frontend** window.
37+
:::image type="content" source="./media/edit-api/edit-api001.png" alt-text="Screenshot that shows the process for editing an API in API Management.":::
3738

3839
## Update the swagger
3940

40-
You can update your backend API from the Azure portal by following these steps:
41+
You can update your API's swagger from the Azure portal by completing these steps:
4142

42-
1. Select **All operations**
43-
2. Click pencil in the **Frontend** window.
43+
1. On the **APIs** page, select **All operations**.
44+
1. Select the pencil button in the **Frontend** pane.
4445

45-
![Screenshot that highlights the pencil icon in the Frontend screen.](./media/edit-api/edit-api002.png)
46+
:::image type="content" source="./media/edit-api/edit-api002.png" alt-text="Screenshot that shows the pencil button in the Frontend pane.":::
4647

4748
Your API's swagger appears.
4849

49-
![Edit an api](./media/edit-api/edit-api003.png)
50+
:::image type="content" source="./media/edit-api/edit-api003.png" alt-text="Screenshot that shows an API's swagger.":::
5051

51-
3. Update the swagger.
52-
4. Press **Save**.
52+
1. Update the swagger.
53+
1. Select **Save**.
5354

5455
> [!CAUTION]
55-
> If you are editing a non-current revision of an API, you cannot change the following properties:
56+
> If you're editing a non-current revision of an API, you can't change the following properties:
5657
>
5758
> * Name
5859
> * Type
@@ -63,7 +64,7 @@ You can update your backend API from the Azure portal by following these steps:
6364
> * Path
6465
> * Protocols
6566
>
66-
> If your edits change any of the above properties of a non-current revision, the error message
67-
> `Can't change property for non-current revision` will be displayed.
67+
> If your edits change any of these properties in a non-current revision, you'll see the error message
68+
> `Can't change property for non-current revision`.
6869
6970
[!INCLUDE [api-management-define-api-topics.md](../../includes/api-management-define-api-topics.md)]
49.8 KB
Loading
651 Bytes
Loading
71.2 KB
Loading

articles/azure-vmware/azure-vmware-solution-known-issues.md

Lines changed: 15 additions & 14 deletions
Large diffs are not rendered by default.

articles/azure-vmware/native-introduction.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ The following table summarizes the differences between Gen 1 and Gen 2 private c
2525
|-----------------------|-----------------------------------------------|--------------------------------------------------|
2626
| Supported SKU type | <ul><li>AV36, AV36P, AV52, AV48</li><li>AV64 (with seed cluster of at least three AV36, AV36P, AV48, or AV52 nodes)</li></ul>| <ul><li>Minimum 3-host AV64 cluster</li></ul>|
2727
| Network Attach Model | <ul><li>ExpressRoute</li></ul> | <ul><li>Virtual Network</li></ul> |
28+
| vSAN Architecture | <ul><li>OSA</li></ul> | <ul><li>ESA</li></ul> |
2829

2930
## Benefits
3031
With the Azure VMware Solution Gen 2 private clouds offering, you get the following benefits:

articles/backup/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -352,6 +352,8 @@
352352
href: ../business-continuity-center/manage-protection-policy.md?toc=/azure/backup/toc.json&bc=/azure/backup/breadcrumb/toc.json
353353
- name: Configure protection for datasources
354354
href: ../business-continuity-center/tutorial-configure-protection-datasource.md?toc=/azure/backup/toc.json&bc=/azure/backup/breadcrumb/toc.json
355+
- name: Reconfigure backup in an alternate vault
356+
href: ../business-continuity-center/tutorial-reconfigure-backup-alternate-vault.md?toc=/azure/backup/toc.json&bc=/azure/backup/breadcrumb/toc.json
355357
- name: Recover item
356358
href: ../business-continuity-center/tutorial-recover-deleted-item.md?toc=/azure/backup/toc.json&bc=/azure/backup/breadcrumb/toc.json
357359
- name: View protected items and perform actions

articles/business-continuity-center/tutorial-reconfigure-backup-alternate-vault.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Tutorial - Reconfigure backup for data sources in an alternate vault using Azure Business Continuity Center
33
description: Learn how to reconfigure backup in an alternate vault for your datasources - Azure Virtual Machine (VM), Azure Files, SQL databases in Azure VM, SAP HANA database in Azure VM.
44
ms.topic: tutorial
5-
ms.date: 09/24/2025
5+
ms.date: 10/06/2025
66
ms.service: azure-business-continuity-center
77
ms.custom:
88
- ignite-2023
@@ -22,6 +22,7 @@ Azure Business Continuity Center allows you to suspend backup for a datasource i
2222
This tutorial describes how to reconfigure backup for data sources in Azure Business Continuity Center by switching to an alternate Recovery Services vault, called re-registration. The feature is available for all datasources supported in Recovery Services vault.
2323

2424
> [!NOTE]
25+
> - Backup reconfiguration to alternate vault isn't supported for SQL Always On Availability Groups (AG) and SAP HANA System Replication (HSR).
2526
> - Recovery Services vault doesn't allow active multi-protection.
2627
> - The alternate vault has no limitations on redundancy, security settings, or policy retention, including for immutable vaults. However, the migration from Enhanced to Standard tier isn't allowed.
2728
> - Old recovery points remain protected with the original configurations and retention. You can use the recovery points stored in the old vault for recovery until they're retained as per the backup policy. This capability also applies to immutable vaults.

articles/container-apps/.openpublishing.redirection.container-apps.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,11 @@
114114
"source_path_from_root": "/articles/container-apps/vnet-custom-internal.md",
115115
"redirect_url": "/azure/container-apps/vnet-custom",
116116
"redirect_document_id": false
117+
},
118+
{
119+
"source_path_from_root": "/articles/container-apps/services.md",
120+
"redirect_url": "/azure/container-apps",
121+
"redirect_document_id": false
117122
}
118123
]
119124
}

0 commit comments

Comments
 (0)