Skip to content

Commit e8b02fc

Browse files
authored
Merge pull request #229463 from paulth1/autoscale-articles-batch-2
[AQ] edit pass: Autoscale articles batch 2
2 parents 7731510 + e45aed6 commit e8b02fc

File tree

5 files changed

+324
-348
lines changed

5 files changed

+324
-348
lines changed

articles/azure-monitor/app/azure-ad-authentication.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.reviewer: rijolly
1111

1212
Application Insights now supports [Azure Active Directory (Azure AD) authentication](../../active-directory/authentication/overview-authentication.md#what-is-azure-active-directory-authentication). By using Azure AD, you can ensure that only authenticated telemetry is ingested in your Application Insights resources.
1313

14-
Using various authentication systems can be cumbersome and risky because it's difficult to manage credentials at scale. You can now choose to [opt out of local authentication](#disable-local-authentication) to ensure only telemetry exclusively authenticated by using [managed identities](../../active-directory/managed-identities-azure-resources/overview.md) and [Azure AD](../../active-directory/fundamentals/active-directory-whatis.md) is ingested in your resource. This feature is a step to enhance the security and reliability of the telemetry used to make critical operational ([alerting](../alerts/alerts-overview.md#what-are-azure-monitor-alerts)and [autoscale](../autoscale/autoscale-overview.md#overview-of-autoscale-in-microsoft-azure)) and business decisions.
14+
Using various authentication systems can be cumbersome and risky because it's difficult to manage credentials at scale. You can now choose to [opt out of local authentication](#disable-local-authentication) to ensure only telemetry exclusively authenticated by using [managed identities](../../active-directory/managed-identities-azure-resources/overview.md) and [Azure AD](../../active-directory/fundamentals/active-directory-whatis.md) is ingested in your resource. This feature is a step to enhance the security and reliability of the telemetry used to make critical operational ([alerting](../alerts/alerts-overview.md#what-are-azure-monitor-alerts)and [autoscale](../autoscale/autoscale-overview.md#overview-of-autoscale-in-azure)) and business decisions.
1515

1616
## Prerequisites
1717

@@ -42,11 +42,11 @@ The following SDKs and features are unsupported for use with Azure AD authentica
4242

4343
1. If you don't already have an identity, create one by using either a managed identity or a service principal.
4444

45-
1. We recommend using a managed identity:
45+
- We recommend using a managed identity:
4646

4747
[Set up a managed identity for your Azure service](../../active-directory/managed-identities-azure-resources/services-support-managed-identities.md) (Virtual Machines or App Service).
4848

49-
1. We don't recommend using a service principal:
49+
- We don't recommend using a service principal:
5050

5151
For more information on how to create an Azure AD application and service principal that can access resources, see [Create a service principal](../../active-directory/develop/howto-create-service-principal-portal.md).
5252

@@ -469,7 +469,7 @@ You can inspect network traffic by using a tool like Fiddler. To enable the traf
469469
}
470470
```
471471

472-
Or add the following JVM args while running your application:`-Djava.net.useSystemProxies=true -Dhttps.proxyHost=localhost -Dhttps.proxyPort=8888`
472+
Or add the following JVM args while running your application: `-Djava.net.useSystemProxies=true -Dhttps.proxyHost=localhost -Dhttps.proxyPort=8888`
473473

474474
If Azure AD is enabled in the agent, outbound traffic will include the HTTP header `Authorization`.
475475

0 commit comments

Comments
 (0)