Skip to content

Commit 3085736

Browse files
author
gitName
committed
pencil edits
1 parent 91f9ec3 commit 3085736

File tree

3 files changed

+6
-4
lines changed

3 files changed

+6
-4
lines changed

articles/api-management/api-management-key-concepts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -89,9 +89,9 @@ The open-source [developer portal][Developer portal] is an automatically generat
8989

9090
API providers can customize the look and feel of the developer portal by adding custom content, customizing styles, and adding their branding. Extend the developer portal further by [self-hosting](developer-portal-self-host.md).
9191

92-
Users such as app developers access the open-source developer portal to discover the APIs, onboard to use them, and learn how to consume them in applications. (APIs can also be exported to the [Power Platform](export-api-power-platform.md) for discovery and use by citizen developers.)
92+
API consumers such as app developers access the open-source developer portal to discover the APIs, onboard to use them, and learn how to consume them in applications. (APIs can also be exported to the [Power Platform](export-api-power-platform.md) for discovery and use by citizen developers.)
9393

94-
Using the developer portal, users can:
94+
Using the developer portal, API consumers can:
9595

9696
* Read API documentation
9797
* Call an API via the interactive console
@@ -167,7 +167,7 @@ When a product is ready for use by consumers, it can be published. Once publishe
167167

168168
### Users and groups
169169

170-
Users can be created or invited to join by service administrators, or they can sign up from the [developer portal][Developer portal]. Each user is a member of one or more groups, and can subscribe to the products that grant visibility to those groups.
170+
Users (API consumers) can be created or invited to join by service administrators, or they can sign up from the [developer portal][Developer portal]. Each user is a member of one or more groups, and can subscribe to the products that grant visibility to those groups.
171171

172172
API Management has the following built-in groups:
173173

articles/api-management/import-and-publish.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ ms.author: danlep
1616

1717
This tutorial shows how to import an OpenAPI specification backend API in JSON format into Azure API Management. For this example, you import the open source [Petstore API](https://petstore3.swagger.io/).
1818

19+
[!INCLUDE [api-management-workspace-try-it](../../includes/api-management-workspace-try-it.md)]
20+
1921
Once you import the backend API into API Management, your API Management API becomes a façade for the backend API. You can customize the façade to your needs in API Management without touching the backend API. For more information, see [Transform and protect your API](transform-api.md).
2022

2123
In this tutorial, you learn how to:

articles/api-management/workspaces-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.author: danlep
1616

1717
[!INCLUDE [api-management-availability-premium](../../includes/api-management-availability-premium.md)]
1818

19-
Today, organizations are increasingly facing challenges in managing a proliferation of APIs. As the number of APIs and API development teams grows, so does the complexity of managing them. This complexity can lead to increased operational overhead, security risks, and reduced agility. On the one hand, organizations want to establish a centralized API infrastructure to ensure API governance, security, and compliance. On the other hand, they want their API teams to innovate and respond quickly to business needs, without the overhead of managing an API platform.
19+
Today, organizations increasingly face challenges in managing a proliferation of APIs. As the number of APIs and API development teams grows, so does the complexity of managing them. This complexity can lead to increased operational overhead, security risks, and reduced agility. On the one hand, organizations want to establish a centralized API infrastructure to ensure API governance, security, and compliance. On the other hand, they want their API teams to innovate and respond quickly to business needs, without the overhead of managing an API platform.
2020

2121
In API Management, *workspaces* bring a new level of autonomy to an organization's API teams, enabling them to create, manage, and publish APIs faster, more reliably, securely, and productively within an API Management service. By providing isolated administrative access and API runtime, workspaces empower API teams while allowing the API platform team to retain oversight. This includes central monitoring, enforcement of API policies and compliance, and publishing APIs for discovery through a unified developer portal.
2222

0 commit comments

Comments
 (0)