Skip to content

Commit 564511a

Browse files
ProfessorKendrickProfessorKendrick
committed
Update link-to-existing-organization.md
1 parent 195fb16 commit 564511a

File tree

1 file changed

+98
-37
lines changed

1 file changed

+98
-37
lines changed

‎articles/partner-solutions/datadog/link-to-existing-organization.md

Lines changed: 98 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Link to existing Datadog
33
description: This article describes how to use the Azure portal to link to an existing instance of Datadog.
44
ms.topic: quickstart
5-
ms.date: 12/05/2024
5+
ms.date: 12/11/2024
66

77

88
ms.custom: references_regions
@@ -36,78 +36,139 @@ If you're linking to an existing Datadog organization, select **Create** under t
3636

3737
You can link your new Datadog resource in Azure to an existing Datadog organization in **US3**.
3838

39-
The portal displays a form for creating the Datadog resource.
39+
The portal displays the Create a Datadog resource pane.
4040

41-
Provide the following values.
41+
## Create a Datadog resource
4242

43-
|Property | Description
44-
|-----------|-------- |
45-
| Subscription | Select the Azure subscription you want to use for creating the Datadog resource. You must have owner access. |
46-
| Resource group | Specify whether you want to create a new resource group or use an existing one. A [resource group](../../azure-resource-manager/management/overview.md#resource-groups) is a container that holds related resources for an Azure solution. |
47-
| Resource name | Specify a name for the Datadog resource. This name is the name of the new Datadog organization, when creating a new Datadog organization. |
48-
| Location | Select West US 2. Currently, West US 2 is the only supported region. |
43+
The Create a Datadog resource pane opens to the *Basics* tab by default.
44+
45+
:::image type="content" source="media/create-new-datadog-resource.png" alt-text="A screenshot of the Azure portal with the Create a a new Datadog resource options displayed. The menu has multiple tabs: Basics, Metrics and logs, Security, Single sign-on, Tags, and Review + Create.":::
46+
47+
### Basics tab
48+
49+
The *Basics* tab has three sections:
50+
51+
- Project details
52+
- Azure resource details
53+
- Datadog organization details
54+
55+
There are required fields in each section that you need to fill out.
56+
57+
1. Enter the values for each required setting under *Project details*.
58+
59+
|Setting |Action |
60+
|-------------------|-------------------------------------------------------------|
61+
|Subscription |Select a subscription from your existing subscriptions. |
62+
|Resource group |Use an existing resource group or create a new one. |
63+
64+
1. Enter the values for each required setting under *Resource details*.
65+
66+
|Setting |Action |
67+
|-------------------|-------------------------------------------------------------|
68+
|Resource name |Specify a unique name for the resource. |
69+
|Location |Select the [region](https://azure.microsoft.com/explore/global-infrastructure/geographies/) where you want to enable this service and its child resources to be located. |
70+
71+
1. Enter the values for each required setting under *Datadog organization details*.
4972

5073
Select **Link to Datadog organization**. The link opens a Datadog authentication window. Sign in to Datadog.
5174

5275
By default, Azure links your current Datadog organization to your Datadog resource. If you would like to link to a different organization, select the appropriate organization in the authentication window.
5376

5477
Select **Next: Metrics and logs** to configure metrics and logs.
5578

56-
If the subscription is already linked to an organization through a Datadog resource, an attempt to link the subscription to the same organization through a different Datadog resource would be blocked. It's blocked to avoid scenarios where duplicate logs and metrics get shipped to the same organization for the same subscription.
79+
> [!NOTE]
80+
> If the subscription is already linked to an organization through a Datadog resource, an attempt to link the subscription to the same organization through a different Datadog resource would be blocked. It's blocked to avoid scenarios where duplicate logs and metrics get shipped to the same organization for the same subscription.
5781
58-
## Configure metrics and logs
82+
### Metrics and logs tab
5983

6084
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.
6185

62-
Tag rules for sending **metrics** are:
86+
Enter the names and values for each *Action* listed under Metrics and Logs.
87+
88+
<!--Metrics-->
89+
<!--Silence monitoring for expected Azure VM Shutdowns-->
90+
<!--Collect custom metrics from App Insights-->
91+
92+
<!--Logs-->
93+
<!--Send subscription activity logs-->
94+
<!--Send Azure resource logs for all defined sources.-->
95+
96+
97+
<!--This information should not be in this quickstart. Move to conceptual article. Also, review the information UI: To send Microsoft Entra ID logs to Datadog – enable Datadog as a destination in Microsoft Entra ID diagnostic settings.
98+
Learn more-->
6399

64-
- By default, metrics are collected for all resources, except **Virtual Machines, Virtual Machine Scale Sets, and App Service Plans**.
65-
- **Virtual Machines, Virtual Machine Scale Sets, and App Service Plans** with *Include* tags send metrics to Datadog.
66-
- **Virtual Machines, Virtual Machine Scale Sets, and App Service Plans** with *Exclude* tags don't send metrics to Datadog.
67-
- If there's a conflict between inclusion and exclusion rules, exclusion takes priority
100+
> [!NOTE]
101+
> If there's a conflict between inclusion and exclusion rules, exclusion takes priority.
68102
69-
Tag rules for sending **logs** are:
103+
Metrics are collected for all resources, except virtual machines, Virtual Machine Scale Sets, and App Service plans which can be filtered by tags.
70104

71-
- By default, logs are collected for all resources.
72-
- Azure resources with *Include* tags send logs to Datadog.
73-
- Azure resources with *Exclude* tags don't send logs to Datadog.
74-
- If there's a conflict between inclusion and exclusion rules, exclusion takes priority.
105+
- Virtual machines, Virtual Machine Scale Sets, and App Service plan with _Include_ tags send metrics to Datadog.
106+
- Virtual machines, Virtual Machine Scale Sets, and App Service plan with _Exclude_ tags don't send metrics to Datadog.
75107

76-
For example, the screenshot shows a tag rule where only those **Virtual Machines, Virtual Machine Scale Sets, and App Service Plans** tagged as *Datadog = True* send metrics to Datadog.
108+
Logs for all defined sources will be sent to Datadog based on the tags inclusion/exclusion criteria. By default, logs are collected for all resources.
77109

78-
There are two types of logs that can be emitted from Azure to Datadog.
110+
- Azure resources with _Include_ tags send logs to Datadog.
111+
- Azure resources with _Exclude_ tags don't send logs to Datadog.
79112

80-
- **Subscription level logs** - Provide insight into the operations on your resources at the [control plane](../../azure-resource-manager/management/control-plane-and-data-plane.md). 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.
113+
There are three types of logs that can be sent from Azure to Datadog.
81114

82-
- **Azure resource logs** - Provide insight into operations that were taken on an Azure resource at the [data plane](../../azure-resource-manager/management/control-plane-and-data-plane.md). 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.
115+
1. **Subscription level logs** - Provide insight into the operations on your resources at the [control plane](../../azure-resource-manager/management/control-plane-and-data-plane.md). 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.
116+
117+
1. **Azure resource logs** - Provide insight into operations that were taken on an Azure resource at the [data plane](../../azure-resource-manager/management/control-plane-and-data-plane.md). 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.
118+
119+
1. **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.
120+
121+
The Microsoft Entra admin center gives you access to three activity logs:
122+
123+
- [Sign-in](../../active-directory/reports-monitoring/concept-sign-ins.md) – Information about sign-ins and how your resources are used by your users.
124+
- [Audit](../../active-directory/reports-monitoring/concept-audit-logs.md) – Information about changes applied to your tenant such as users and group management or updates applied to your tenant's resources.
125+
- [Provisioning](../../active-directory/reports-monitoring/concept-provisioning-logs.md) – Activities performed by the provisioning service, such as the creation of a group in ServiceNow or a user imported from Workday.
83126

84127
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.
85128

86-
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](/azure/azure-monitor/essentials/resource-logs-categories). To filter the set of Azure resources sending logs to Datadog, use Azure resource tags.
129+
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](/azure/azure-monitor/essentials/resource-logs-categories). To filter the set of Azure resources sending logs to Datadog, use Azure resource tags.
130+
131+
You can request your IT Administrator to route Microsoft Entra logs to Datadog. For more information, see [Microsoft Entra activity logs in Azure Monitor](../../active-directory/reports-monitoring/concept-activity-logs-azure-monitor.md).
132+
133+
Azure charges for the logs sent to Datadog. For more information, see the [pricing of platform logs](https://azure.microsoft.com/pricing/details/monitor/) sent to Azure Marketplace partners.
134+
135+
<!--end-->
87136

88-
The logs sent to Datadog are charged by Azure. For more information, see the [pricing of platform logs](https://azure.microsoft.com/pricing/details/monitor/) sent to Azure Marketplace partners.
137+
Once you complete the configuration for metrics and logs, select **Next: Security**.
89138

90-
Once you have completed configuring metrics and logs, select **Next: Single sign-on**.
139+
## Security tab
91140

92-
## Configure single sign-on
141+
To enable Datadog Cloud Security Posture management, select the checkbox.
93142

94-
If you're linking the Datadog resource to an existing Datadog organization, you can't set up single sign-on at this step. Instead, you set up single sign-on after creating the Datadog resource. For more information, see [Reconfigure single sign-on](manage.md#reconfigure-single-sign-on).
143+
## Configure single sign-on tab (optional)
144+
145+
If your organization uses Microsoft Entra ID as its identity provider, you can establish single sign-on from the Azure portal to Datadog.
146+
147+
To establish single sign-on through Microsoft Entra ID, select the checkbox.
148+
149+
The Azure portal retrieves the appropriate Datadog application from Microsoft Entra ID, which matches the Enterprise app you provided previously.
150+
151+
Select the Datadog app name.
95152

96153
Select **Next: Tags**.
97154

98-
## Add custom tags
155+
## Tags tab (optional)
156+
157+
If you wish, you can optionally create tags resource, then select the **Next: Review + create** button at the bottom of the page.
158+
159+
## Review + create tab
99160

100-
You can specify custom tags for the new Datadog resource. Provide name and value pairs for the tags to apply to the Datadog resource.
161+
If the review identifies errors, a red dot appears next each section where errors exist. Fields with errors are highlighted in red.
101162

102-
When you've finished adding tags, select **Next: Review+Create**.
163+
1. Open each section with errors and fix the errors.
103164

104-
## Review + Create Datadog resource
165+
1. Select the **Review + create** button again.
105166

106-
Review your selections and the terms of use. After validation completes, select **Create**.
167+
1. Select the **Create** button.
107168

108-
Azure deploys the Datadog resource.
169+
Once the resource is created, select **Go to Resource** to navigate to the Datadog resource.
109170

110-
When the process completes, select **Go to Resource** to see the Datadog resource.
171+
:::image type="content" source="media/go-to-resource.png" alt-text="A screenshot of the Overview for a newly-created Datadog resource with the Go to Resource button emphasized.":::
111172

112173
## Next steps
113174

0 commit comments

Comments
 (0)