Skip to content

Commit 354f2e9

Browse files
committed
deactivated link
1 parent 1737b22 commit 354f2e9

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/azure-monitor/logs/api/authentication-authorization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Before beginning, make sure you have all the values required to make OAuth2 call
2929

3030
In the client credentials flow, the token is used with the ARM endpoint. A single request is made to receive a token, using the application permissions provided during the Azure AD application setup.
3131
The resource requested is: <https://management.azure.com/>.
32-
You can also use this flow to request a token to [https://api.loganalytics.io](https://api.loganalytics.io/). Replace the "resource" in the example.
32+
You can also use this flow to request a token to `https://api.loganalytics.io`. Replace the "resource" in the example.
3333

3434
#### Client Credentials Token URL (POST request)
3535

articles/azure-monitor/logs/api/request-format.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: article
99
# Azure Monitor Log Analytics API request format
1010

1111
There are two endpoints through which you can communicate with the Log Analytics API:
12-
- A direct URL for the API: [api.loganalytics.io](https://api.loganalytics.io/)
12+
- A direct URL for the API: `https://api.loganalytics.io`
1313
- Through Azure Resource Manager (ARM).
1414

1515
While the URLs are different, the query parameters are the same for each endpoint. Both endpoints require authorization through Azure Active Directory (Azure AD).

0 commit comments

Comments
 (0)