Microsoft Azure

First, log in to the Azure account you want to integrate with Datadog:

az login

Run the account show command:

az account show

Enter the generated Tenant ID value in the Datadog Azure Integration tile under Tenant name/ID.

Create an application as a service principal using the format:

az ad sp create-for-rbac --role reader --scopes /subscriptions/{subscription_id}

• This command grants the Service Principal the reader role for the subscription you would like to monitor.
• The appID generated from this command must be entered in the Datadog Azure Integration tile under Client ID.
• Add --name <CUSTOM_NAME> to use a hand-picked name, otherwise Azure generates a unique one. The name is not used in the setup process.
• Add --password <CUSTOM_PASSWORD> to use a hand-picked password. Otherwise Azure generates a unique one. This password must be entered in the Datadog Azure Integration tile under Client Secret.

First, log in to the Azure account you want to integrate with Datadog:

azure login

Run the account show command:

az account show

Enter the generated Tenant ID value in the Datadog Azure Integration tile under Tenant name/ID.

Create a name and password:

azure ad sp create -n <NAME> -p <PASSWORD>

• The <NAME> is NOT used but is required as part of the setup process.
• The <PASSWORD> you choose must be entered in the Datadog Azure Integration tile under Client Secret.
• The Object Id returned from this command is used in place of <OBJECT_ID> in the next command.

Create an application as a service principal using the format:

azure role assignment create --objectId <OBJECT_ID> -o Reader -c /subscriptions/<SUBSCRIPTION_ID>/

• This command grants the Service Principal the reader role for the subscription you would like to monitor.
• The Service Principal Name generated from this command must be entered in the Datadog Azure Integration tile under Client ID.
• <SUBSCRIPTION_ID> is the Azure subscription you would like to monitor, and is listed as ID with azure account show or in the portal.

First, log in to the Azure account you want to integrate with Datadog:

azure login

Run the account show command:

az account show

Enter the generated Tenant ID value in the Datadog Azure Integration tile under Tenant name/ID.

Create a name, home-page, identifier-uris, and password:

azure ad app create --name "<NAME>" --home-page "<URL>" --identifier-uris "<URL>" --password "<PASSWORD>"

• The name, home-page, and identifier-uris are NOT used but are required as part of the setup process.
• The password you choose must be entered in the Datadog Azure Integration tile under Client Secret.
• The AppId returned from this command is used in the next command and must be entered in the Datadog Azure Integration tile under Client ID.

Create a Service Principal using:

Azure cli <0.10.2:

azure ad sp create {app-id}

Azure cli >= 0.10.2:

azure ad sp create -a {app-id}

• The Object Id returned from this command is used in place of <OBJECT_ID> in the next command.

Create an Active Directory application using the format:

azure role assignment create --objectId <OBJECT_ID> --roleName Reader --subscription <SUBSCRIPTION_ID>

• This command grants the Service Principal the reader role for the subscription you would like to monitor.
• <SUBSCRIPTION_ID> is the Azure subscription you would like to monitor, and is listed as ID with azure account show or in the portal.

To send logs from Azure to Datadog, follow this general process:

1. Create an Azure Event Hub.
2. Setup the Datadog-Azure function with an Event hub trigger to forward logs to Datadog.
3. Configure your Azure services to stream logs to the Event Hub by creating a diagnostic setting.

The instructions below walk through a basic, initial setup using the Azure Portal. All of these steps can be performed with the CLI, Powershell, or resource templates by referring to the Azure documentation.

Azure Event Hub

Create an Azure Event Hub:

1. In the Azure portal, navigate to the Event Hubs overview and click Add.
2. Enter the name, pricing tier, subscription, and resource group.
3. Select Location. Note: The Event Hub must be in the same Location as the resource you want to submit logs from. For activity logs or other account-wide log sources, you can choose any region.
4. Select your desired options for Kafka, zone-redundancy, throughput, and auto-inflation.
5. Click Create.

Datadog-Azure function

Set up the Datadog-Azure Function with an Event Hub trigger to forward logs to Datadog:

1. In the Azure portal, navigate to your Function Apps -> Functions and click Add.
2. Select a subscription, resource group, region, and enter a name for your function.
3. Select Publish Code and Runtime stack Node.js.
4. Click Next:Hosting.
5. Select a storage account and plan type, then select Operating System Windows.
6. Review and create the new function.
7. Once deployment has finished, select your new function from the function apps list.
8. Select to build your function in-portal and use the Event Hub trigger template under More templates…. If prompted, install the Microsoft.Azure.WebJobs.Extensions.EventHubs extension.
9. Select or add your Event Hub connection, consumer group, and name to pull logs from, then click Create.
10. Create an index.js file and add the Datadog-Azure Function code (replace <DATADOG_API_KEY> with your Datadog API key).
11. Save the function.
12. Under Integrate, check the following settings:
    a. Event Parameter Name is set to eventHubMessages.
    b. Event Hub Cardinality is set to Many.
    c. Event Hub Data Type is set to Default (Json).
    Note: If this option is not available in the standard editor, use the advanced editor to manually remove the setting for dataType entirely. This may not be reflected in the standard editor, but this should not be of concern.
13. Click Save.
14. Verify your setup is correct by running the function and then checking the Datadog log explorer for the test message.

Diagnostic setting

Configure your Azure services to forward their logs to the Event Hub by creating a diagnostic setting.

1. In the Azure portal, navigate to the resource of the logs you want to send to Datadog.
2. Under the monitoring section of the resource blade, click Diagnostic settings.
3. Click Add diagnostic setting.
4. Under category details, select the categories of logs you want to send to Datadog.
5. Under destination details, select Stream to an event hub.
6. Set the Event Hub namespace and name. These should match the Event Hub namespace and name in the binding defined in Step 9 of the previous section.
7. Set the shared access key. This key should be configured with send or manage access.
8. Click Save.
9. Verify your setup is correct by checking the Datadog log explorer for logs from this resource.

To collect logs from all of your Azure App Services, follow this general process:

1. Set up Azure Blob Storage from the Azure portal, Azure Storage Explorer, Azure CLI, or Powershell.
2. Set up the Datadog-Azure Function which forwards logs from your blob storage to Datadog.
3. Configure your Azure App Services to forward their logs to the Blob Storage.

Create a new Azure Blob Storage function

If you are unfamiliar with Azure functions refer to Create your first function in the Azure portal.

1. In the Azure portal, navigate to your Function Apps -> Functions and click Add.
2. Select a subscription, resource group, region, and enter a name for your function.
3. Select Publish Code and Runtime stack Node.js.
4. Click Next:Hosting.
5. Select a storage account and plan type, then select Operating System Windows.
6. Review and Create the new function.
7. Once deployment has finished, select your new function from the Function Apps list.
8. Select to build your function In-portal and use the Blog Storage trigger template (under More templates…). If prompted, install the Microsoft.Azure.WebJobs.Extensions.EventHubs extension.
9. Select or add your Storage account connection and click Create.
10. Create an index.js file and add the Datadog-Azure Function code (replace <DATADOG_API_KEY> with your Datadog API Key).
11. Save the function.
12. Under Integrate, set the Blob Parameter Name to blobContent and click Save.
13. Verify your setup is correct by checking the Datadog Log explorer for your logs.