Get started with Datadog - An Azure Native ISV Service by creating new instance

• 
  

Prerequisites

Before creating your first instance of Datadog in Azure, configure your environment. These steps must be completed before continuing with the next steps in this quickstart.

Find offer

Use the Azure portal to find Datadog.

1. Go to the Azure portal and sign in.

2. If you've visited the Marketplace in a recent session, select the icon from the available options. Otherwise, search for Marketplace.

   

3. In the Marketplace, search for Datadog.

4. In the plan overview screen, select Subscribe.

   

Create a Datadog resource in Azure

The portal displays a selection asking whether you would like to create a Datadog organization or link Azure subscription to an existing Datadog organization.

If you're creating a new Datadog organization, select Create under the Create a new Datadog organization

The portal displays a form for creating the Datadog resource.

Provide the following values.

Property	Description
Subscription	Select the Azure subscription you want to use for creating the Datadog resource. You must have owner access.
Resource group	Specify whether you want to create a new resource group or use an existing one. A resource group is a container that holds related resources for an Azure solution.
Resource name	Specify a name for the Datadog resource. This name will be the name of the new Datadog organization, when creating a new Datadog organization.
Location	Select West US 2. Currently, West US 2 is the only supported region.
Pricing plan	When creating a new organization, select from the list of available Datadog plans.
Billing Term	Monthly.

Configure metrics and logs

Use Azure resource tags to configure which metrics and logs are sent to Datadog. You can include or exclude metrics and logs for specific resources.

Tag rules for sending metrics are:

• By default, metrics are collected for all resources, except virtual machines, Virtual Machine Scale Sets, and App Service plans.
• Virtual machines, Virtual Machine Scale Sets, and App Service plan with Include tags send metrics to Datadog.
• Virtual machines, Virtual Machine Scale Sets, and App Service plan with Exclude tags don't send metrics to Datadog.
• If there's a conflict between inclusion and exclusion rules, exclusion takes priority.

Tag rules for sending logs are:

• By default, logs are collected for all resources.
• Azure resources with Include tags send logs to Datadog.
• Azure resources with Exclude tags don't send logs to Datadog.
• If there's a conflict between inclusion and exclusion rules, exclusion takes priority.

For example, the following screenshot shows a tag rule where only those virtual machines, Virtual Machine Scale Sets, and App Service plan tagged as Datadog = True send metrics to Datadog.

There are three types of logs that can be sent from Azure to Datadog.

1. Subscription level logs - Provide insight into the operations on your resources at the control plane. Updates on service health events are also included. Use the activity log to determine the what, who, and when for any write operations (PUT, POST, DELETE). There's a single activity log for each Azure subscription.

2. Azure resource logs - Provide insight into operations that were taken on an Azure resource at the data plane. For example, getting a secret from a Key Vault is a data plane operation. Or, making a request to a database is also a data plane operation. The content of resource logs varies by the Azure service and resource type.

3. Microsoft Entra logs - As an IT administrator, you want to monitor your IT environment. The information about your system's health enables you to assess potential issues and decide how to respond.

The Microsoft Entra admin center gives you access to three activity logs:

• Sign-in – Information about sign-ins and how your resources are used by your users.
• Audit – Information about changes applied to your tenant such as users and group management or updates applied to your tenant's resources.
• Provisioning – Activities performed by the provisioning service, such as the creation of a group in ServiceNow or a user imported from Workday.

To send subscription level logs to Datadog, select Send subscription activity logs. If this option is left unchecked, none of the subscription level logs are sent to Datadog.

To send Azure resource logs to Datadog, select Send Azure resource logs for all defined resources. The types of Azure resource logs are listed in Azure Monitor Resource Log categories. To filter the set of Azure resources sending logs to Datadog, use Azure resource tags.

You can request your IT Administrator to route Microsoft Entra logs to Datadog. For more information, see Microsoft Entra activity logs in Azure Monitor.

The logs sent to Datadog will be charged by Azure. For more information, see the pricing of platform logs sent to Azure Marketplace partners.

Once you have completed configuring metrics and logs, select Next: Single sign-on.

Configure single sign-on

If your organization uses Microsoft Entra ID as its identity provider, you can establish single sign-on from the Azure portal to Datadog. If your organization uses a different identity provider or you don't want to establish single sign-on at this time, you can skip this section.

To establish single sign-on through Microsoft Entra ID, select the checkbox for Enable single sign-on through Microsoft Entra ID.

The Azure portal retrieves the appropriate Datadog application from Microsoft Entra ID. The app matches the Enterprise app you provided in an earlier step.

Select the Datadog app name.

Select Next: Tags.

Add custom tags

You can specify custom tags for the new Datadog resource. Provide name and value pairs for the tags to apply to the Datadog resource.

When you've finished adding tags, select Next: Review+Create.

Review + Create Datadog resource

Review your selections and the terms of use. After validation completes, select Create.

Azure deploys the Datadog resource.

When the process completes, select Go to Resource to see the Datadog resource.