Document transport level customization (#7056)

Co-authored-by: danielmarbach <[email protected]>

Author: danielmarbach

Snippets/ASBS/ASBS_5/AccessToNativeMessage.cs

@@ -42,6 +42,16 @@ async Task AccessNativeOutgoingMessageFromHandler(IMessageHandlerContext context
             #endregion
         }
 
+        void Customize(AzureServiceBusTransport transport)
+        {
+            #region access-native-outgoing-message-over-transport
+            transport.OutgoingNativeMessageCustomization = (operation, message) =>
+            {
+                // Customize the outgoing message based on the operation
+            };
+            #endregion
+        }
+
         class MyCommand { }
         class MyEvent { }
     }

transports/azure-service-bus/native-message-access.md

@@ -8,7 +8,6 @@ reviewed: 2024-02-09
 
 partial: supported-versions
 
-
 ## Access to the native Azure Service Bus incoming message
 
 It can sometimes be useful to access the native Service Bus incoming message from behaviors and handlers. When a message is received, the transport adds the native Service Bus [`Message`](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.servicebus.message) to the message processing context. Use the code below to access the message details from a [pipeline behavior](/nservicebus/pipeline/manipulate-with-behaviors.md):

transports/azure-service-bus/native-message-access_snippets_asbs_[2,).partial.md transports/azure-service-bus/native-message-access_snippets_asbs_[2,5).partial.md

@@ -0,0 +1,5 @@
+snippet: access-native-outgoing-message
+
+Or on a more global level directly on the transport
+
+snippet: access-native-outgoing-message-over-transport