Others

How to Configure Azure Diagnostic Settings for Log Forwarding

Chanuka GeekiyanageChanuka Geekiyanage Oct 7, 2026 870 views

Question details

The user needs to find out where to properly configure diagnostic settings in Azure to forward resource logs and metrics to designated destinations.

How to Configure Azure Diagnostic Settings for Log Forwarding
Product
Microsoft Azure
Device & OS
not provided
Scenario
Forwarding Azure resource logs and metrics to a Log Analytics workspace or a third-party application.
Observed behavior
Configuring diagnostics on a single workspace does not automatically collect logs from all connected resources; manual configuration is required.
Before you start

Ensure you have the required Azure role-based access control (RBAC) permissions, such as Monitoring Contributor, to create or modify diagnostic settings on your target resources.

Solution 1Recommended

Configure Diagnostic Settings on Each Individual Azure Resource

Since logs are not collected automatically across the environment, you must manually apply diagnostic settings to every individual resource you want to monitor.

A resource's diagnostic setting dictates which specific logs and metrics are sent to destinations like a Log Analytics workspace. Setting up a destination workspace alone does not trigger log collection from other connected resources without this explicit configuration.

1
Access the target resource

Sign in to the Azure Portal and navigate to the specific Azure resource from which you want to collect logs.

2
Open diagnostic settings

In the left-hand menu of the resource, scroll to the 'Monitoring' section and select 'Diagnostic settings'.

3
Add a new setting

Click 'Add diagnostic setting'. Select the specific log categories and metrics you wish to forward based on your monitoring needs.

4
Select destination and save

Choose your destination details (such as a Log Analytics workspace, Event Hub, or Storage Account) and click 'Save' to apply the configuration.

Configure Diagnostic Settings on Each Individual Azure Resource
Varying Log Categories: Available log categories and supported destinations vary depending on the specific resource type. Always refer to Azure documentation for resource-specific details.
Free Microsoft Office alternative

Document Your Azure Architecture with WPS Office

While you manage your cloud resources and log forwarding in the Azure Portal, maintaining clear documentation of your IT infrastructure is crucial. WPS Office is a free, lightweight, and highly compatible alternative to Microsoft Office, making it easy to create architecture reports, track monitoring policies, and share IT documentation.

  1. 1. Download and Install: Visit the official WPS Office website to download the free suite and follow the simple installation prompts.
  2. 2. Create IT Documentation: Open WPS Writer or Spreadsheet to start documenting your Azure diagnostic configurations and monitoring policies.
  3. 3. Save in MS Formats: Save your files directly in standard Microsoft Office formats (.docx, .xlsx) to ensure seamless sharing with your IT team.
Seamlessly compatible with Microsoft Office formats like DOCX, XLSX, and PPTX.Lightweight software footprint that opens large IT reports quickly without lagging.Familiar user interface allows for immediate productivity with zero learning curve.Free to download and use for creating professional cloud architecture documentation.
QA img-9

Frequently Asked Questions

Why aren't logs automatically forwarded to my Log Analytics workspace?

Configuring diagnostics on one workspace does not automatically collect logs from every connected Azure resource. You must explicitly configure diagnostic settings on each individual resource you wish to monitor.

Can I forward Azure logs to a third-party application?

Yes. To forward logs to a third-party application, you typically configure the diagnostic setting's destination to an Azure Event Hub, which your external application can then securely ingest from.

How can I apply diagnostic settings to multiple resources at once?

For managing multiple resources, you should use a centralized Azure monitoring and export solution, such as assigning Azure Policy definitions to automate the deployment of diagnostic settings across subscriptions or resource groups.