Skip to content

Commit ff90266

Browse files
authored
Merge pull request #191478 from pizzaz93/patch-5
Add a note to clarify the length of time it takes to propagate account changes
2 parents 8231050 + e672d9a commit ff90266

File tree

2 files changed

+9
-1
lines changed

2 files changed

+9
-1
lines changed

articles/azure-monitor/logs/api/errors.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,10 @@ Code: 403 Response:
108108

109109
Details: The token you have presented for authorization belongs to a user who does not have sufficient access to this privilege. Verify your workspace GUID and your token request are correct, and if necessary grant IAM privileges in your workspace to the Azure AD Application you created as Contributor.
110110

111+
> [!NOTE]
112+
> When using Azure AD authentication, it may take up to 60 minutes for the Azure Application Insights REST API to recognize new
113+
> role-based access control (RBAC) permissions. While permissions are propagating, REST API calls may fail with error code 403.
114+
111115
## Bad Authorization Code
112116

113117
Code: 403 Response:

articles/azure-monitor/logs/api/overview.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,10 @@ After receiving a token, the process for calling the Log Analytics API is identi
3131

3232
To quickly explore the API without using Azure AD authentication, we provide a demonstration workspace with sample data, which allows [authenticating with an API key](authentication-authorization.md#authenticating-with-an-api-key).
3333

34+
> [!NOTE]
35+
> When using Azure AD authentication, it may take up to 60 minutes for the Azure Application Insights REST API to recognize new
36+
> role-based access control (RBAC) permissions. While permissions are propagating, REST API calls may fail with [error code 403](./errors.md#insufficient-permissions).
37+
3438
## Log Analytics API Query Limits
3539

3640
See [the **Query API** section of this page](../../service-limits.md#la-query-api) for information about query limits.
@@ -41,4 +45,4 @@ To try the API without writing any code, you can use:
4145
- Your favorite client such as [Fiddler](https://www.telerik.com/fiddler) or [Postman](https://www.getpostman.com/) to manually generate queries with a user interface.
4246
- [cURL](https://curl.haxx.se/) from the command line, and then pipe the output into [jsonlint](https://github.com/zaach/jsonlint) to get readable JSON.
4347

44-
Instead of calling the REST API directly, you can also use the Azure Monitor Query SDK. The SDK contains idiomatic client libraries for [.NET](/dotnet/api/overview/azure/Monitor.Query-readme), [Java](/java/api/overview/azure/monitor-query-readme), [JavaScript](/javascript/api/overview/azure/monitor-query-readme), and [Python](/python/api/overview/azure/monitor-query-readme). Each client library is a wrapper around the REST API that allows you to retrieve log data from the workspace.
48+
Instead of calling the REST API directly, you can also use the Azure Monitor Query SDK. The SDK contains idiomatic client libraries for [.NET](/dotnet/api/overview/azure/Monitor.Query-readme), [Java](/java/api/overview/azure/monitor-query-readme), [JavaScript](/javascript/api/overview/azure/monitor-query-readme), and [Python](/python/api/overview/azure/monitor-query-readme). Each client library is a wrapper around the REST API that allows you to retrieve log data from the workspace.

0 commit comments

Comments
 (0)