You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-center/tutorials/configure-environments-deployments.md
+13-15Lines changed: 13 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Augment the API inventory in your API center by adding information
4
4
author: dlepow
5
5
ms.service: azure-api-center
6
6
ms.topic: tutorial
7
-
ms.date: 10/15/2025
7
+
ms.date: 10/20/2025
8
8
ms.author: danlep
9
9
#customer intent: As the owner of an Azure API center, I want a step by step introduction to adding API environments and deployments to my inventory.
10
10
---
@@ -13,28 +13,26 @@ ms.author: danlep
13
13
14
14
This tutorial explains how to augment the inventory in your API center by adding information about API environments and deployments.
15
15
16
-
* An *environment* represents a location where an API runtime could be deployed, for example, an API management platform.
17
-
18
-
* A *deployment* is a location, or address, where users can access an API.
16
+
- An *environment* represents a location where an API runtime could be deployed, for example, an API management platform.
17
+
- A *deployment* is a location, or address, where users can access an API.
19
18
20
19
For more information about APIs, deployments, and other entities that you can inventory in Azure API Center, see [Key concepts](../key-concepts.md).
21
20
22
21
In this tutorial, you learn how to use the portal to:
23
22
> [!div class="checklist"]
24
-
> * Add information about API environments
25
-
> * Add information about API deployments
23
+
> - Add information about API environments
24
+
> - Add information about API deployments
26
25
27
26
## Prerequisites
28
27
29
-
* An API center in your Azure subscription. If you haven't created one already, see [Quickstart: Create your API center](../set-up-api-center.md).
30
-
31
-
* One or more APIs registered in your API center. If you haven't registered any APIs already, see [Tutorial: Register APIs in your API inventory](./register-apis.md). This tutorial uses the sample APIs you added from the previous tutorial.
28
+
- An API center in your Azure subscription. To create one, see [Quickstart: Create your API center](../set-up-api-center.md).
29
+
- One or more APIs registered in your API center. If you don't have any registered APIs, see [Tutorial: Register APIs in your API inventory](register-apis.md). This tutorial uses the sample APIs you added from the previous tutorial.
32
30
33
31
## Add an environment
34
32
35
33
Use your API center to keep track of your real-world API environments. For example, you might use Azure API Management or another solution to distribute, secure, and monitor some of your APIs. Or you might directly serve some APIs using a compute service or a Kubernetes cluster.
36
34
37
-
Here you add information about a fictitious Azure API Management environment to your API center. If you prefer, add information about one of your existing environments. You'll configure both built-in metadata and any custom metadata that you defined in a [previous tutorial](./add-metadata-properties.md).
35
+
Here you add information about a fictitious Azure API Management environment to your API center. If you prefer, add information about one of your existing environments. Configure both your built-in metadata and any custom metadata that you defined in a [previous tutorial](add-metadata-properties.md).
38
36
39
37
1. Sign in to the [Azure portal](https://portal.azure.com), then navigate to your API center.
40
38
@@ -74,7 +72,7 @@ Here you add a deployment by associating one of your APIs with the environment y
74
72
75
73
1. On the **Conference API** page, under **Details**, select **Deployments** > **+ Add deployment**.
76
74
77
-
1. In the **Add deployment** page, add the following information. If you previously defined the custom *Line of business* metadata or other metadata assigned to environments, you'll see them at the bottom of the page.
75
+
1. In the **Add deployment** page, add the following information. If you previously defined the custom *Line of business* metadata or other metadata assigned to environments, you can see them at the bottom of the page.
78
76
79
77
|Setting|Value|Description|
80
78
|-------|-----|-----------|
@@ -92,10 +90,10 @@ Here you add a deployment by associating one of your APIs with the environment y
92
90
93
91
In this tutorial, you learned how to use the portal to:
94
92
> [!div class="checklist"]
95
-
> * Add information about API environments
96
-
> * Add information about API deployments
93
+
> - Add information about API environments
94
+
> - Add information about API deployments
97
95
98
96
## Related content
99
97
100
-
*[Learn more about Azure API Center](../key-concepts.md)
101
-
*[Track API resource dependencies](../track-resource-dependencies.md)
98
+
-[Learn more about Azure API Center](../key-concepts.md)
99
+
-[Track API resource dependencies](../track-resource-dependencies.md)
* Complete the previous tutorial, [Define custom metadata](./add-metadata-properties.md), to define custom metadata for your APIs.
32
+
- Define custom metadata for your APIs by completing the previous tutorial, [Define custom metadata](add-metadata-properties.md).
33
33
34
34
## Register APIs
35
35
36
36
When you register (add) an API in your API center, the API registration includes:
37
-
* A title (name), type, and description
38
-
* Version information
39
-
* Optional links to documentation and contacts
40
-
* Built-in and custom metadata that you defined
37
+
- A title (name), type, and description
38
+
- Version information
39
+
- Optional links to documentation and contacts
40
+
- Built-in and custom metadata that you defined
41
41
42
42
After registering an API, you can add versions and definitions to the API.
43
43
@@ -47,7 +47,7 @@ The following steps register two sample APIs: Swagger Petstore API and Conferenc
47
47
48
48
1. In the sidebar menu, under **Assets**, select **APIs** > **+ Register an API**.
49
49
50
-
1. In the **Register an API** page, add the following information for the Swagger Petstore API. You'll see the custom *Line of business* and *Public-facing* metadata that you defined in the previous tutorial at the bottom of the page.
50
+
1. In the **Register an API** page, add the following information for the Swagger Petstore API. You should see the custom *Line of business* and *Public-facing* metadata that you defined in the previous tutorial at the bottom of the page.
51
51
52
52
|Setting|Value|Description|
53
53
|-------|-----|-----------|
@@ -97,15 +97,15 @@ Here you add a version to one of your APIs:
97
97
98
98
:::image type="content" source="./media/register-apis/add-version.png" alt-text="Screenshot of adding an API version in the portal." lightbox="./media/register-apis/add-version.png":::
99
99
100
-
1. On the **Add API version** page, under **Version details**, enter or select the following information:
100
+
1. On the **Add API version** page, enter or select the following information under **Version details**:
101
101
102
102
|Setting|Value|Description|
103
103
|-------|-----|-----------|
104
104
|**Version title**| Enter a version title of your choice, such as *v2*.|Name you choose for the API version |
105
105
|**Version identification**|After you enter the preceding title, Azure API Center generates this identifier, which you can override.| Azure resource name for the version |
106
106
|**Version lifecycle**| Make a selection from the dropdown, such as **Production**. | Lifecycle stage of the API version |
107
107
108
-
1. Azure API Center supports definitions in common text specification formats, such as OpenAPI 2 and 3 for REST APIs. To add an API definition, under **Select a specification**, enter or select the following information:
108
+
1. Azure API Center supports definitions in common text specification formats, such as OpenAPI 2 and 3 for REST APIs. To add an API definition, enter or select the following information under **Select a specification**:
This connector supports connecting to Microsoft Fabric Lakehouse in the workspace with a private link enabled. You can set up and use a private link in Microsoft Fabric by referring to this [article](/fabric/security/security-workspace-level-private-links-set-up).
39
+
40
+
To support workspace-level private link in the self-hosted integration runtime (version 5.58.9377.1 or above), you need to add `*.dfs.fabric.microsoft.com` to the allowlist to ensure Microsoft Fabric Lakehouse connector can access Onelake APIs through the network.
**What's the difference between Azure Container Storage and Azure CSI (Container Storage Interface) drivers?**
25
-
Azure Container Storage is built natively for containers and provides a storage solution that's optimized for creating and managing volumes for running production-scale stateful container applications. Other Azure CSI drivers provide a standard storage solution that can be used with different container orchestrators and support the specific type of storage solution per CSI driver definition.
25
+
Azure Container Storage supports backing storage options that other Azure CSI drivers don't support, such as Ephemeral Disk (Local NVMe). All of these drivers are designed to work seamlessly with AKS and are open source.
26
26
27
27
* <aid="azure-container-storage-regions"></a>
28
28
**In which Azure regions is Azure Container Storage available?**
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments