review comments

Author: gitName

articles/api-center/includes/configure-managed-identity-apim-reader.md

@@ -19,9 +19,9 @@ To allow import of APIs, assign your API center's managed identity the **API Man
 1. In the left menu, select **Access control (IAM)**.
 1. Select **+ Add role assignment**.
 1. On the **Add role assignment** page, set the values as follows: 
-    1. On the **Role** tab - Select **API Management Service Reader**.
+    1. On the **Role** tab, select **API Management Service Reader**.
     1. On the **Members** tab, in **Assign access to** - Select **Managed identity** > **+ Select members**.
-    1. On the **Select managed identities** page - Select the system-assigned managed identity of your API center that you added in the previous section. Click **Select**.
+    1. On the **Select managed identities** page, select the system-assigned managed identity of your API center that you added in the previous section. Click **Select**.
     1. Select **Review + assign**.
 
 #### [Azure CLI](#tab/cli)

articles/api-center/includes/configure-managed-identity-kv-secret-user.md

@@ -19,9 +19,9 @@ To allow import of APIs, assign your API center's managed identity the **Key Vau
 1. In the left menu, select **Access control (IAM)**.
 1. Select **+ Add role assignment**.
 1. On the **Add role assignment** page, set the values as follows: 
-    1. On the **Role** tab - Select **Key Vault Secrets User**.
+    1. On the **Role** tab, select **Key Vault Secrets User**.
     1. On the **Members** tab, in **Assign access to** - Select **Managed identity** > **+ Select members**.
-    1. On the **Select managed identities** page - Select the system-assigned managed identity of your API center that you added in the previous section. Click **Select**.
+    1. On the **Select managed identities** page, select the system-assigned managed identity of your API center that you added in the previous section. Click **Select**.
     1. Select **Review + assign**.
 
 #### [Azure CLI](#tab/cli)

articles/api-center/includes/delete-api-integration.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 12/23/2024
+ms.date: 01/08/2025
 ms.author: danlep
 ms.custom: Include file
 ---
@@ -18,8 +18,22 @@ While an API source is integrated, you can't delete synchronized APIs from your
 * The synchronized APIs in your API center inventory are deleted
 * The environment and deployments associated with the API source are deleted
 
-To delete an integration:
+You can delete an integration using the portal or the Azure CLI. 
+
+#### [Portal](#tab/portal)
 
 1. In the [portal](https://portal.azure.com), navigate to your API center.
 1. Under **Assets**, select **Environments** > **Integration (preview)**.
 1. Select the integration, and then select **Delete** (trash can icon). 
+
+#### [Azure CLI](#tab/cli)
+
+Run the `az apic integration delete` command to delete an integration. Provide the names of the resource group, API center, and integration.
+
+```azurecli
+az apic integration delete \
+    --resource-group <resource-group-name> \
+    --service-name <api-center-name> \
+    --integration-name <integration-name> \
+```
+---

articles/api-center/includes/install-apic-extension.md

@@ -14,4 +14,4 @@ ms.custom: Include file
 > [!NOTE]
 > `az apic` commands require the `apic-extension` Azure CLI extension. If you haven't used `az apic` commands, the extension can be installed dynamically when you run your first `az apic` command, or you can install the extension manually. Learn more about [Azure CLI extensions](/cli/azure/azure-cli-extensions-overview).
 >
-> See the [release notes](https://github.com/Azure/azure-cli-extensions/blob/main/src/apic-extension/HISTORY.rst) for the latest changes and updates in the `apic-extension`.
+> See the [release notes](https://github.com/Azure/azure-cli-extensions/blob/main/src/apic-extension/HISTORY.rst) for the latest changes and updates in the `apic-extension`. Certain features may require a specific version of the extension.

articles/api-center/includes/synchronized-properties-api-source.md

@@ -6,13 +6,13 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 01/02/2025
+ms.date: 01/08/2025
 ms.author: danlep
 ms.custom: Include file
 ---
 You can add or update metadata properties and documentation to the synchronized APIs in your API center to help stakeholders discover, understand, and consume the APIs. Learn more about Azure API Center's [built-in and custom metadata properties](../add-metadata-properties.md).
 
-The following table shows entity properties that can be modified in Azure API Center and properties that are determined based on their values in an integrated API source. Also, entities' resource or system identifiers in Azure API Center are generated automatically and can't be modified.
+The following table shows entity properties that can be modified in Azure API Center and properties that are set based on their values in an integrated API source. 
 
 | Entity       | Properties configurable in API Center                     | Properties determined in integrated API source                                           |
 |--------------|-----------------------------------------|-----------------|
@@ -21,4 +21,5 @@ The following table shows entity properties that can be modified in Azure API Ce
 | Environment  | title<br/>description<br/>kind</br>server.managementPortalUri<br/>onboarding<br/>customProperties      | server.type
 | Deployment   |  title<br/>description<br/>server<br/>state<br/>customProperties    |      server.runtimeUri |
 
-For property details, see the [Azure API Center REST API reference](/rest/api/apicenter).
+> [!NOTE]
+> Resource and system IDs for entities synchronized to Azure API Center are automatically generated and can't be changed.

articles/api-center/media/synchronize-aws-gateway-apis/key-vault-secrets.png

@@ -27,8 +27,10 @@ When you integrate an API Management instance as an API source, the following ha
 API Management APIs automatically synchronize to the API center whenever existing APIs' settings change (for example, new versions are added), new APIs are created, or APIs are deleted. This synchronization is one-way from API Management to your Azure API center, meaning API updates in the API center aren't synchronized back to the API Management instance.
 
 > [!NOTE]
+> * Integration of Azure API Management is currently in preview.
 > * There are [limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#api-center-limits) for the number of integrated API Management instances (API sources).
 > * API updates in API Management typically synchronize to your API center within minutes but synchronization can take up to 24 hours.
+> * API definitions also synchronize to the API center if you select the option to include them during integration.
 
 ### Entities synchronized from API Management
 
@@ -76,10 +78,16 @@ You can integrate an API Management instance using the portal or the Azure CLI.
 
 #### [Azure CLI](#tab/cli)
 
-Run the `az apic integration create apim` command to integrate an API Management instance to your API center. Provide the... If the API Management instance and the API center are in the same resource group, you can provide the API Management instance name as the value of `azure-apim`; otherwise, provide the Azure resource ID. 
+Run the `az apic integration create apim` command to integrate an API Management instance to your API center. 
+
+* Provide the names of the resource group, API center, and integration.  
+
+* If the API Management instance and the API center are in the same resource group, you can provide the API Management instance name as the value of `azure-apim`; otherwise, provide the Azure resource ID. 
 
 ```azurecli
-az apic integration create apim --name <api-center-name> \
+az apic integration create apim \
+    --resource-group <resource-group-name> \
+    --service-name <api-center-name> \
     --integration-name <apim-integration-name> \
     --azure-apim <apim-instance-name>
 ``` 

articles/api-center/synchronize-api-management-apis.md

@@ -4,7 +4,7 @@ description: Integrate an Amazon API Gateway to Azure API Center for automatic s
 author: dlepow
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 01/02/2025
+ms.date: 01/08/2025
 ms.author: danlep 
 ms.custom: devx-track-azurecli
 # Customer intent: As an API program manager, I want to integrate my Azure API Management instance with my API center and synchronize API Management APIs to my inventory.
@@ -29,8 +29,8 @@ Synchronization is one-way from Amazon API Gateway to your Azure API center, mea
 > [!NOTE]
 > * Integration of Amazon API Gateway is currently in preview.
 > * There are [limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#api-center-limits) for the number of integrated API sources.
-> * API updates in Amazon API Gateway synchronize to your API center once per hour.
-> * API definitions are also synchronized to the API center only if you select the option to include them during integration. Only definitions from deployed APIs are synchronized.
+> * APIs in Amazon API Gateway synchronize to your API center once per hour. Only REST APIs are synchronized.
+> * API definitions also synchronize to the API center if you select the option to include them during integration. Only definitions from deployed APIs are synchronized.
 
 ### Entities synchronized from Amazon API Gateway
 
@@ -40,7 +40,7 @@ Synchronization is one-way from Amazon API Gateway to your Azure API center, mea
 
 * An API center in your Azure subscription. If you haven't created one, see [Quickstart: Create your API center](set-up-api-center.md).
 
-* An Azure key vault. If you need to create one, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal).
+* An Azure key vault. If you need to create one, see [Quickstart: Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal). To add or manage secrets in the key vault, at least the **Key Vault Secrets Officer** role or equivalent permissions are required. 
 
 * An [Amazon API Gateway](https://docs.aws.amazon.com/apigateway/). 
 
@@ -69,12 +69,18 @@ Save your access keys in a safe location. You'll store them in Azure Key Vault i
 
 Manually upload and securely store the two IAM user access keys in Azure Key Vault using the configuration recommended in the following table. For more information, see [Quickstart: Set and retrieve a secret from Azure Key Vault using the Azure portal](/azure/key-vault/secrets/quick-create-portal). 
 
+#### [Portal](#tab/portal)
+
 | AWS secret | Upload options | Name | Secret value | 
 |------------|----------------|------|--------------|
 | Access key | Manual | *aws-access-key* | Access key ID retrieved from AWS |
 | Secret access key | Manual | *aws-secret-access-key* | Secret access key retrieved from AWS |
 
-Take note of the **Secret identifier** URI of each secret. You'll use these identifiers in the next steps.
+:::image type="content" source="media/synchronize-aws-gateway-apis/key-vault-secrets.png" alt-text="Screenshot of secrets list in Azure Key Vault in the portal.":::
+
+---
+
+Take note of the **Secret identifier** of each secret, a URI similar to `https://<key-vault-name>.vault.azure.net/secrets/<secret-nam>.`. You'll use these identifiers in the next steps.
 
 
 [!INCLUDE [enable-managed-identity](includes/enable-managed-identity.md)]
@@ -86,8 +92,9 @@ Take note of the **Secret identifier** URI of each secret. You'll use these iden
 
 ## Integrate an Amazon API Gateway 
 
-You can integrate an Amazon API Gateway to your API center using the portal or the Azure CLI.
+You can integrate an Amazon API Gateway to your API center using the Azure CLI.
 
+<!--
 #### [Portal](#tab/portal)
 
 1. In the [portal](https://portal.azure.com), navigate to your API center.
@@ -102,20 +109,24 @@ You can integrate an Amazon API Gateway to your API center using the portal or t
         1. Optionally, select whether to include API definitions.
 1. Select **Create**.
 
-<!----
-Add image of integrating AWS g/w?
+Add image of integrating AWS g/w in portal
 --->
 
 #### [Azure CLI](#tab/cli)
 
-Run the `az apic integration create aws` command to integrate an Amazon API Gateway to your API center. Provide the Key Vault secret identifiers for the AWS access key and secret access key, and the AWS region where the Amazon API Gateway is deployed.
+Run the `az apic integration create aws` command to integrate an Amazon API Gateway to your API center. 
 
-```azurecli
+* Provide the names of the resource group, API center, and integration. 
 
-az apic integration create aws --name <api-center-name> \
+* Provide the Key Vault secret identifiers for the AWS access key and secret access key, and the AWS region where the Amazon API Gateway is deployed.
+
+```azurecli
+az apic integration create aws \
+    --resource-group <resource-group-name> \
+    --service-name-name <api-center-name> \
     --integration-name <aws-integration-name> \
     --aws-access-key-reference <access-key-uri> \
-    --aws-secret-access-key-reference <secret-access-key-uri> \
+    --aws-secret-access-key-reference <secret-access-key-uri> 
     --aws-region-name <aws-region>
 ``` 
 ---