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/azure-monitor/app/azure-ad-authentication.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ The following Software Development Kits (SDKs) and features are unsupported for
50
50
51
51
For more information on how to create a Microsoft Entra application and service principal that can access resources, see [Create a service principal](../../active-directory/develop/howto-create-service-principal-portal.md).
52
52
53
-
1. Assign the required RBAC role to the Azure identity, service principal, or Azure user account.
53
+
1. Assign the required Role-based access control (RBAC) role to the Azure identity, service principal, or Azure user account.
54
54
55
55
Follow the steps in [Assign Azure roles](../../role-based-access-control/role-assignments-portal.yml) to add the Monitoring Metrics Publisher role to the expected identity, service principal, or Azure user account by setting the target Application Insights resource as the role scope.
56
56
@@ -250,7 +250,7 @@ You can disable local authentication by using the Azure portal or Azure Policy o
250
250
251
251
### Azure portal
252
252
253
-
1. From your Application Insights resource, select **Properties** under the **Configure** heading in the menu on the left. Select **Enabled (click to change)** if the local authentication is enabled.
253
+
1. From your Application Insights resource, select **Properties** under **Configure** in the menu on the left. Select **Enabled (click to change)** if the local authentication is enabled.
254
254
255
255
:::image type="content" source="./media/azure-ad-authentication/enabled.png" alt-text="Screenshot that shows Properties under the Configure section and the Enabled (select to change) local authentication button.":::
256
256
@@ -427,7 +427,7 @@ Now that your app is registered and has permissions to use the API, grant your a
427
427
428
428
Before you begin, make sure you have all the values required to make the request successfully. All requests require:
429
429
- Your Microsoft Entra tenant ID.
430
-
- Your App Insights App ID - If you are currently using API Keys, this is the same app ID.
430
+
- Your App Insights App ID - If you're currently using API Keys, it's the same app ID.
431
431
- Your Microsoft Entra client ID for the app.
432
432
- A Microsoft Entra client secret for the app.
433
433
@@ -735,13 +735,13 @@ The main OAuth2 flow supported is through [authorization codes](/azure/active-di
735
735
&resource=https://api.applicationinsights.io
736
736
```
737
737
738
-
When a request is made to the authorize URL, the client\_id is the application ID from your Microsoft Entra app, copied from the app's properties menu. The redirect\_uri is the homepage/login URL from the same Microsoft Entra app. When a request is successful, this endpoint redirects you to the sign-in page you provided at sign-up with the authorization code appended to the URL. See the following example:
738
+
When a request is made to the authorized URL, the client\_id is the application ID from your Microsoft Entra app, copied from the app's properties menu. The redirect\_uri is the homepage/login URL from the same Microsoft Entra app. When a request is successful, this endpoint redirects you to the sign-in page you provided at sign-up with the authorization code appended to the URL. See the following example:
At this point, you've obtained an authorization code, which you need now to request an access token.
744
+
At this point, you obtain an authorization code, which you now use to request an access token.
745
745
746
746
##### Authorization code token URL (POST request)
747
747
@@ -776,7 +776,7 @@ Response example:
776
776
}
777
777
```
778
778
779
-
The access token portion of this response is what you present to the Application Insights API in the `Authorization: Bearer` header. You can also use the refresh token in the future to acquire a new access\_token and refresh\_token when yours have gone stale. For this request, the format and endpoint are:
779
+
The access token portion of this response is what you present to the Application Insights API in the `Authorization: Bearer` header. You can also use the refresh token in the future to acquire a new access\_token and refresh\_token when yours go stale. For this request, the format and endpoint are:
780
780
781
781
```http
782
782
POST /YOUR_AAD_TENANT/oauth2/token HTTP/1.1
@@ -807,7 +807,7 @@ Response example:
807
807
808
808
The Application Insights API supports the OAuth2 [implicit flow](/azure/active-directory/develop/active-directory-dev-understanding-oauth2-implicit-grant). For this flow, only a single request is required, but no refresh token can be acquired.
809
809
810
-
##### Implicit code authorize URL
810
+
##### Implicit code authorization URL
811
811
812
812
```http
813
813
GET https://login.microsoftonline.com/YOUR_AAD_TENANT/oauth2/authorize?
@@ -823,7 +823,7 @@ A successful request produces a redirect to your redirect URI with the token in
0 commit comments