Skip to content

Commit caee03a

Browse files
Merge pull request #284736 from abinetabate/patch-10
Update opentelemetry-overview.md
2 parents fd20bc3 + c31a89c commit caee03a

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

articles/azure-monitor/app/opentelemetry-overview.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,9 +23,6 @@ There are two methods to instrument your application:
2323

2424
**Autoinstrumentation** enables telemetry collection through configuration without touching the application's code. Although it's more convenient, it tends to be less configurable. It's also not available in all languages. See [Autoinstrumentation supported environments and languages](codeless-overview.md). When autoinstrumentation is available, it's the easiest way to enable Azure Monitor Application Insights.
2525

26-
> [!TIP]
27-
> Currently, [Microsoft Entra authentication](azure-ad-authentication.md) is not available with autoinstrumentation. If you require Microsoft Entra auth, you'll need to use manual instrumentation.
28-
2926
**Manual instrumentation** is coding against the Application Insights or OpenTelemetry API. In the context of a user, it typically refers to installing a language-specific SDK in an application. This means that you have to manage the updates to the latest package version by yourself. You can use this option if you need to make custom dependency calls or API calls that are not captured by default with autoinstrumentation. There are two options for manual instrumentation:
3027

3128
- [Application Insights SDKs](asp-net-core.md)

0 commit comments

Comments
 (0)