[DOCS-13908] Add Configure Log Forwarding flow and Log Analytics Workspaces docs#35930
Open
[DOCS-13908] Add Configure Log Forwarding flow and Log Analytics Workspaces docs#35930
Conversation
…spaces section Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
benjjs
reviewed
Apr 15, 2026
Comment on lines
242
to
+243
|
|
||
| Datadog recommends using the Agent or DaemonSet to send logs from Azure. If direct streaming isn't possible, you can use an Azure Resource Manager (ARM) template to [automate log forwarding setup][19] across your Azure environment with no manual configuration. This feature automatically manages and scales log forwarding services. | ||
| Datadog recommends using the Agent or DaemonSet to send logs from Azure. If direct streaming isn't possible, use the **Configure Log Forwarding** flow in the [Azure integration][20] to set up and manage automated log forwarding directly in Datadog. You can also deploy log forwarding with an [Azure Resource Manager (ARM) template][19]. Both methods automatically manage and scale log forwarding services. |
Contributor
There was a problem hiding this comment.
Once @MikeCronk is back I want to double check if we still recommend using the Agent or Daemonset above LFO via the new flow.
benjjs
reviewed
Apr 15, 2026
pashneal
reviewed
Apr 15, 2026
benjjs
approved these changes
Apr 15, 2026
iadjivon
reviewed
Apr 15, 2026
Contributor
iadjivon
left a comment
iadjivon
left a comment
There was a problem hiding this comment.
Hi Bryce,
Added some clarifying questions. Please let me know if you have any questions.
Thanks so much!
iadjivon
approved these changes
Apr 15, 2026
Contributor
|
Thanks so much for the confirmation Bryce! All set! 🥳 |
pashneal
approved these changes
Apr 15, 2026
mshvartsberg
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Fixes DOCS-13908
Adds documentation for two new Azure automated log forwarding features:
Configure Log Forwarding flow — A new in-app UI flow for setting up and managing automated log forwarders directly from Datadog, replacing the need to re-run ARM templates for configuration changes. Added as the recommended method in both the Getting Started guide and the automated log forwarding guide.
Log Analytics Workspaces — Documents how to forward logs from Azure Log Analytics Workspace Log Tables to Datadog through Data Export Rules. Includes setup steps, restrictions, and troubleshooting.
Note: Tag filter documentation (item 3 from the update request) is being handled in a separate PR.
Merge instructions
Merge readiness:
Additional notes