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/applications.md
+29-5Lines changed: 29 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: dlepow
7
7
8
8
ms.service: azure-api-management
9
9
ms.topic: how-to
10
-
ms.date: 05/19/2025
10
+
ms.date: 07/11/2025
11
11
ms.author: danlep
12
12
ms.custom:
13
13
- build-2025
@@ -22,9 +22,9 @@ API Management now supports built-in OAuth 2.0 application-based access to produ
22
22
> Applications are currently in limited preview. To sign up, fill [this form](https://aka.ms/apimappspreview).
23
23
24
24
With this feature:
25
-
26
25
* API managers set a product property to enable application-based access.
27
26
* API managers register client applications in Microsoft Entra ID to limit access to specific products.
27
+
* Developers can access client application credentials using the API Management developer portal.
28
28
* Using the OAuth 2.0 client credentials flow, developers or apps obtain tokens that they can include in API requests
29
29
* Tokens presented in API requests are validated by the API Management gateway to authorize access to the product's APIs.
30
30
@@ -61,7 +61,8 @@ Follow these steps to enable **Application based access** for a product. A produ
61
61
62
62
The following example uses the **Starter** product, but choose any published product that has at least one API assigned to it.
63
63
64
-
1. Sign in to the [portal](https://portal.azure.com) and navigate to your API Management instance.
64
+
1. Sign in to the portal at the following custom URL for the applications feature: [https://portal.azure.com/?feature.customPortal=false&Microsoft_Azure_ApiManagement=applications](https://portal.azure.com/?feature.customPortal=false&Microsoft_Azure_ApiManagement=applications)
65
+
1. Navigate to your API Management instance.
65
66
1. In the left menu, under **APIs**, select **Products**.
66
67
1. Choose the product that you want to configure, such as the **Starter** product.
67
68
1. In the left menu, under **Product**, select **Properties**.
@@ -103,10 +104,13 @@ To review application settings in **App registrations**:
103
104
Now register a client application that limits access to one or more products.
104
105
105
106
* A product must have **Application based access** enabled to be associated with a client application.
106
-
* Each client application has a single user (owner) in the API Management instance. One the owner can access product APIs through the application.
107
+
* Each client application has a single user (owner) in the API Management instance. Only the owner can access product APIs through the application.
107
108
* A product can be associated with more than one client application.
108
109
109
-
1. Sign in to the [portal](https://portal.azure.com) and navigate to your API Management instance.
110
+
To register a client application:
111
+
112
+
1. Sign in to the portal at the following custom URL for the applications feature: [https://portal.azure.com/?feature.customPortal=false&Microsoft_Azure_ApiManagement=applications](https://portal.azure.com/?feature.customPortal=false&Microsoft_Azure_ApiManagement=applications)
113
+
1. Navigate to your API Management instance.
110
114
1. In the left menu, under **APIs**, select **Applications** > **+ Register application**.
111
115
1. In the **Register an application** page, enter the following application settings:
112
116
***Name**: Enter a name for the application.
@@ -152,6 +156,16 @@ To review application settings in **App registrations**:
152
156
153
157
:::image type="content" source="media/applications/client-api-permissions.png" alt-text="Screenshot of API permissions in the portal.":::
154
158
159
+
## Get application settings in developer portal
160
+
161
+
Users can sign in to the developer portal to view the client applications that they own.
162
+
163
+
1. Sign in to the developer portal (`https://<your-apim-instance-name>.developer.azure-api.net`) using a user account that was set as the owner of a client application.
164
+
1. In the top navigation menu, select **Applications**.
165
+
1. Applications that the user owns appear in the list.
166
+
1. Select an application to view its details, such as the **Client ID**, **Client secret**, and **Scope**. These values are needed to generate a token to call the product APIs.
167
+
168
+
:::image type="content" source="media/applications/applications-developer-portal.png" alt-text="Screenshot of client applications in the developer portal.":::
155
169
156
170
## Create token and use with API call
157
171
@@ -204,6 +218,16 @@ Write-Host "Response:"
204
218
$getresponse | ConvertTo-Json -Depth 5
205
219
```
206
220
221
+
## Troubleshooting
222
+
223
+
### Internal server error when registering applications in the portal
224
+
225
+
If you're unable to list applications, or you receive an internal server error when registering applications in the portal, check the following:
226
+
227
+
* The **Application Administrator** role is assigned to the API Management instance's managed identity in Microsoft Entra ID.
228
+
* You're signed in to the portal at the following custom URL for the applications feature: [https://portal.azure.com/?feature.customPortal=false&Microsoft_Azure_ApiManagement=applications](https://portal.azure.com/?feature.customPortal=false&Microsoft_Azure_ApiManagement=applications). This URL is required to access the applications feature in API Management.
229
+
230
+
207
231
## Related content
208
232
209
233
*[Create and publish a product](api-management-howto-add-products.md)
Copy file name to clipboardExpand all lines: articles/azure-functions/configure-monitoring.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -290,7 +290,7 @@ For a function app to send data to Application Insights, it needs to connect to
290
290
|**[`APPLICATIONINSIGHTS_CONNECTION_STRING`](functions-app-settings.md#applicationinsights_connection_string)**| This setting is recommended and is required when your Application Insights instance runs in a sovereign cloud. The connection string supports other [new capabilities](/azure/azure-monitor/app/migrate-from-instrumentation-keys-to-connection-strings#new-capabilities). |
291
291
|**[`APPINSIGHTS_INSTRUMENTATIONKEY`](functions-app-settings.md#appinsights_instrumentationkey)**| Legacy setting, which Application Insights has deprecated in favor of the connection string setting. |
292
292
293
-
When you create your function app in the [Azure portal](./functions-get-started.md) from the command line by using [Azure Functions Core Tools](./create-first-function-cli-csharp.md) or [Visual Studio Code](./create-first-function-vs-code-csharp.md), Application Insights integration is enabled by default. The Application Insights resource has the same name as your function app, and is created either in the same region or in the nearest region.
293
+
When you create your function app in the [Azure portal](./functions-get-started.md) from the command line by using [Azure Functions Core Tools](./how-to-create-function-azure-cli.md?pivots=programming-language-csharp) or [Visual Studio Code](./create-first-function-vs-code-csharp.md), Application Insights integration is enabled by default. The Application Insights resource has the same name as your function app, and is created either in the same region or in the nearest region.
+ If you use another [supported version of Java](supported-languages.md?pivots=programming-language-java#languages-by-runtime-version), you must update the project's pom.xml file.
36
-
+ The `JAVA_HOME` environment variable must be set to the install location of the correct version of the JDK.
37
-
+[Apache Maven 3.8.x](https://maven.apache.org)
38
-
::: zone-end
39
-
::: zone pivot="programming-language-javascript,programming-language-typescript"
+ A [secure HTTP test tool](functions-develop-local.md#http-test-tools) for sending requests with JSON payloads to your function endpoints. This article uses `curl`.
0 commit comments