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-management/api-management-howto-developer-portal.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ This article describes the differences between self-hosted and managed versions
35
35
You can build your developer portal in two ways:
36
36
37
37
-**Managed version** - by editing and customizing the portal, which is built into your API Management instance and is accessible through the URL `<your-api-management-instance-name>.developer.azure-api.net`. Refer to [this documentation article](api-management-howto-developer-portal-customize.md) to learn how to access and customize the managed portal.
38
-
-**Self-hosted version** - by deploying and self-hosting your portal outside of an API Management instance. This approach allows you to edit the portal's codebase and extend the provided core functionality. You also need to upgrade the portal to the latest version yourself. For details and instructions, refer to the [GitHub repository with the source code of the portal][1]. The [tutorial for the managed version](api-management-howto-developer-portal-customize.md) walks through the portal's administrative panel, which is also featured in the self-hosted version.
38
+
-**Self-hosted version** - by deploying and self-hosting your portal outside of an API Management instance. This approach allows you to edit the portal's codebase and extend the provided core functionality. You also need to upgrade the portal to the latest version yourself. For details and instructions, refer to the [GitHub repository with the source code of the portal][1] and [the tutorial on implementing a widget][4]. The [tutorial for the managed version](api-management-howto-developer-portal-customize.md) walks through the portal's administrative panel, which is also featured in the self-hosted version.
39
39
40
40
## Portal architectural concepts
41
41
@@ -98,6 +98,10 @@ The old developer and publisher portals are now *legacy* features - they will be
98
98
99
99
Deprecation of the legacy portals will be announced separately. If you have questions, concerns, or comments, raise them [in a dedicated GitHub issue](https://github.com/Azure/api-management-developer-portal/issues/121).
100
100
101
+
### Functionality I need isn't supported in the portal
102
+
103
+
Use the self-hosted version and [implement your own widget][4].
104
+
101
105
### How can I automate portal deployments?
102
106
103
107
You can programmatically access and manage the developer portal's content through the REST API, regardless if you're using a managed or a self-hosted version.
@@ -212,6 +216,7 @@ Learn more about the new developer portal:
212
216
213
217
-[Access and customize the managed developer portal](api-management-howto-developer-portal-customize.md)
0 commit comments