diff --git a/docs/platforms/dotnet/common/configuration/disable-integrations.mdx b/docs/platforms/dotnet/common/configuration/disable-integrations.mdx
index 6260d0b63d89cf..a339774f820c15 100644
--- a/docs/platforms/dotnet/common/configuration/disable-integrations.mdx
+++ b/docs/platforms/dotnet/common/configuration/disable-integrations.mdx
@@ -6,7 +6,9 @@ description: "Learn more about the methods that disable integrations."
 
 All of Sentry’s SDKs provide integrations, which extend functionality of the SDK. Most integrations are enabled by default, though you can disable them if needed.
 
-To disable an integration, for example, the automatic capture of unhandled exceptions:
+# Options
+
+Most integrations can be disabled via the options when initializing the SDK. For example, to disable the automatic capture of unhandled exceptions:
 
 ```csharp
 // Add it to your Sentry SDK initialization block:
@@ -39,3 +41,15 @@ Disables adding the list of .NET Frameworks installations into events.
 ## DisableAppDomainProcessExitFlush
 
 Disables flushing events upon `AppDomain.ProcessExit` event handler.
+
+# Sentry Native
+
+On many platforms, the .NET SDK for Sentry includes Sentry Native, which lets you capture crash reports for native (unmanaged) code. If you are experiencing difficulties, you can disable Sentry Native by setting the `SentryNative` build property to `false`:
+
+```xml
+<PropertyGroup>
+  <SentryNative>false</SentryNative>
+</PropertyGroup>
+```
+
+Note: Sentry Native is disabled by default for applications targeting WASM.