Skip to content

Commit 2d3652a

Browse files
authored
Merge pull request #124999 from azarboon/patch-721843
Update get-started-create-service-instance.md
2 parents 6979a0c + bca80ab commit 2d3652a

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/api-management/get-started-create-service-instance.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -51,11 +51,9 @@ Sign in to the [Azure portal](https://portal.azure.com).
5151

5252
1. On the **Monitor + secure** tab, optionally select one or more recommended add-in services to use with API Management. These services incur extra costs. For example, select **Log Analytics** to define a Log Analytics workspace you can target for API Management logs.
5353

54-
1. On the **Managed identity** tab, we recommend selecting the checkbox to enable a system-assigned identity for your API Management instance. A managed identity generated by Microsoft Entra ID allows your API Management instance to easily and securely access other Microsoft Entra protected resources, such as Azure Key Vault. Azure manages this identity, so you don't have to provision or rotate any credentials.
54+
> [!TIP]
55+
> It can take 30 to 40 minutes or more to create and activate an API Management service in this tier. To quickly find a newly created service, select **Pin to dashboard**.
5556
56-
1. Optionally, on the **Tags** tab, add tags to your API Management instance. Tags are key-value pairs that help you organize and manage your Azure resources.
57-
58-
1. On the **Review + install** tab, review the settings you selected. If you need to make changes, go back to the previous tabs. If everything looks good, select **Create**.
5957

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

0 commit comments

Comments
 (0)