[AZINTS-3739] Reference LFO install template in integrations-management repo (#32554)

gpalmz · web-flow · commit 56f06a209321 · 2025-10-31T16:49:10.000-04:00
diff --git a/content/en/getting_started/integrations/azure.md b/content/en/getting_started/integrations/azure.md
@@ -19,7 +19,7 @@ Datadog offers multiple configuration options for the Azure integration. This gu
 
 ## Prerequisites
 
-If you haven't already, create a [Datadog account][2]. 
+If you haven't already, create a [Datadog account][2].
 
 {{% collapse-content title="Permissions required for integration setup" level="h4" expanded=false id="required-permissions" %}}
 
@@ -56,7 +56,7 @@ The `Datadog Admin Role`, or any other role with the `azure_configurations_manag
 
 ## Setup
 
-Follow the instructions on this page to set up the **Azure integration** through an app registration, available for all Datadog sites. 
+Follow the instructions on this page to set up the **Azure integration** through an app registration, available for all Datadog sites.
 
 {{< img src="/getting_started/integrations/azure/GSwAzure_siteSelector.mp4" alt="Site selector for US3 site" video=true >}}
 
@@ -94,10 +94,10 @@ You can also click to enable custom metric collection from [Azure Application In
    3. Optionally, open **Log filtering options** to filter logs by tags, or apply filtering for specific information (such as PII) using regex.
 
    See the [Architecture section][34] of the automated log forwarding guide for more information about this architecture.
-    
+
 8. Click **Confirm** to finish the setup.
 
-{{% /collapse-content %}} 
+{{% /collapse-content %}}
 
 {{% collapse-content title="Terraform" expanded=false level="h4" id="terraform-setup" %}}
 
@@ -190,7 +190,7 @@ Datadog provides a monitor template to help you get started. To use the monitor
 4. Update the notification and re-notification messages as desired. Note that the events themselves contain pertinent information about the event and are included in the notification automatically. This includes detailed information about the scope, error response, and common steps to remediate.
 5. [Configure notifications][27] through your preferred channels (email, Slack, PagerDuty, or others) to make sure your team is alerted about issues affecting Azure data collection.
 
-{{% /collapse-content %}} 
+{{% /collapse-content %}}
 
 {{% collapse-content title="Use an existing app registration" level="h4" expanded=false id="existing-app-registration-setup" %}}
 
@@ -200,7 +200,7 @@ Datadog provides a monitor template to help you get started. To use the monitor
 
 If you need to set up an app registration for Datadog, see the [Quickstart](#quickstart-setup) or [Terraform](#terraform-setup) setup methods.
 
-### Instructions 
+### Instructions
 
 1. In the [Datadog Azure integration tile][20], select **Add Existing**.
 2. In the **Tenant ID** field, paste your Directory (tenant) ID.
@@ -219,17 +219,17 @@ You can also click to enable custom metric collection from [Azure Application In
 6. Optionally, click the resource collection toggle to disable the collection of configuration information from your Azure resources.
 7. Click **Create Configuration**.
 
-{{% /collapse-content %}} 
+{{% /collapse-content %}}
 
 ## Metric collection
 
-Datadog's Azure integration is built to collect all metrics from [Azure Monitor][8]. The [Integrations page][9] shows a curated list of predefined sub-integrations that provide additional out-of-the-box dashboards and monitors for specific Azure services. Many of these integrations are installed by default when Datadog recognizes data coming in from your Azure account. However, Datadog can ingest metrics from **any Azure Monitor-supported resource**, even if it doesn't have a dedicated sub-integration tile. 
+Datadog's Azure integration is built to collect all metrics from [Azure Monitor][8]. The [Integrations page][9] shows a curated list of predefined sub-integrations that provide additional out-of-the-box dashboards and monitors for specific Azure services. Many of these integrations are installed by default when Datadog recognizes data coming in from your Azure account. However, Datadog can ingest metrics from **any Azure Monitor-supported resource**, even if it doesn't have a dedicated sub-integration tile.
 
 You can find your Azure metrics in the metrics summary page in the Datadog platform by navigating to `Metrics > Summary` and searching for `Azure`.
 
 {{< img src="/getting_started/integrations/azure/GSwAzure_metricExplorer.png" alt="Metric summary image" style="width:100%;" >}}
 
-## Enable log collection 
+## Enable log collection
 
 You can use the automated log forwarding feature to setup and configure the services and diagnostic settings needed to forward logs to Datadog. If an automated log forwarding control plane already exists in the tenant, this flow modifies it and extends its scope to include the selected subscriptions or management groups. For more detail, see [Azure Automated Log Forwarding Setup][19].
 
@@ -257,7 +257,7 @@ Datadog recommends using the Agent or DaemonSet to send logs from Azure. If dire
 
 See [Azure Automated Log Forwarding Architecture][34] for more details.
 
-{{% /collapse-content %}} 
+{{% /collapse-content %}}
 
 {{% collapse-content title="Container App" level="h4" expanded=false id="container-app-log-forwarding-setup" %}}
 
@@ -275,18 +275,18 @@ See [Azure Automated Log Forwarding Architecture][34] for more details.
 
 **Note**: Resources can only stream to a Storage Account in the same Azure region.
 
-{{% /collapse-content %}} 
+{{% /collapse-content %}}
 
 {{% azure-log-archiving %}}
 
-## Get more from the Datadog Platform 
+## Get more from the Datadog Platform
 
 ### Install the Agent for greater visibility into your application
 
-After you set up your Azure integration, Datadog crawlers automatically collect Azure metrics, but you can gain even deeper visibility into your Azure instances with the [Datadog Agent][1]. Installing the Datadog Agent into your environment allows you to collect additional data including, but not limited to: 
-- **Application health** 
+After you set up your Azure integration, Datadog crawlers automatically collect Azure metrics, but you can gain even deeper visibility into your Azure instances with the [Datadog Agent][1]. Installing the Datadog Agent into your environment allows you to collect additional data including, but not limited to:
+- **Application health**
 - **Process utilization**
-- **System-level metrics** 
+- **System-level metrics**
 
 You can also use the built-in StatsD client to send custom metrics from your applications, to correlate what's happening with your applications, users, and system. See the guide on [_Why should I install the Datadog Agent on my cloud instances?_][15] for more information on the benefits of installing the Datadog Agent on your instances.
 
@@ -314,7 +314,7 @@ To install the Agent based on operating system or CI and CD tool, see the [Datad
 
 {{% tab "AKS Cluster Extension" %}}
 
-The Datadog AKS Cluster Extension allows you to deploy the Datadog Agent natively within Azure AKS, avoiding the complexity of third-party management tools. To install the Datadog Agent with the AKS Cluster Extension: 
+The Datadog AKS Cluster Extension allows you to deploy the Datadog Agent natively within Azure AKS, avoiding the complexity of third-party management tools. To install the Datadog Agent with the AKS Cluster Extension:
 
 1. Go to your AKS cluster in the Azure portal.
 2. From the left sidebar of the AKS cluster, select **Extensions + applications** under **Settings**.
@@ -353,7 +353,7 @@ Still need help? Contact [Datadog support][17].
 [26]: https://app.datadoghq.com/monitors/templates?q=Azure%20%22integration%20errors%22&origination=all&p=1
 [27]: /monitors/notify/#configure-notifications-and-automations
 [28]: /integrations/guide/azure-advanced-configuration/#enable-diagnostics
-[29]: https://portal.azure.com/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2FcreateUiDefinition.json
+[29]: https://portal.azure.com/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2FcreateUiDefinition.json
 [30]: /logs/guide/azure-automated-log-forwarding/#basics
 [31]: /logs/guide/azure-automated-log-forwarding/#datadog-configuration
 [32]: /logs/guide/azure-automated-log-forwarding/#deployment
diff --git a/content/en/logs/guide/azure-automated-log-forwarding.md b/content/en/logs/guide/azure-automated-log-forwarding.md
@@ -11,7 +11,7 @@ further_reading:
 
 ## Overview
 
-Use this guide to automate your Azure log forwarding setup with an Azure Resource Manager (ARM) template. 
+Use this guide to automate your Azure log forwarding setup with an Azure Resource Manager (ARM) template.
 
 The ARM template deploys resources from a series of Azure services (storage accounts and function apps) into your subscriptions, which collect and forward logs to Datadog. These services automatically scale up or down to match log volume. Scaling is managed by a control plane, which is a set of function apps deployed to a subscription and region of your choice. Storage accounts and function apps are deployed in each of the subscriptions forwarding logs to Datadog.
 
@@ -75,7 +75,7 @@ The sections below provide instructions for completing each page of the template
 
 ### Services used
 
-- [Azure Function][15] apps are used to discover resources in your Azure subscriptions, scale log forwarders, and configure diagnostic settings on the detected resources. 
+- [Azure Function][15] apps are used to discover resources in your Azure subscriptions, scale log forwarders, and configure diagnostic settings on the detected resources.
 - [Azure Container Apps][8] are used to collect resource logs generated by diagnostic settings, track which logs have been processed already, and submit them to Datadog.
 - [Azure Storage Accounts][9] are used to store logs generated by your resources, as well as a small cache of metadata such as subscription IDs, resource IDs, and regions.
 
@@ -85,19 +85,19 @@ The sections below provide instructions for completing each page of the template
 
 The deployment template sets up a [control plane](#control-plane) and [log forwarders](#log-forwarders) in your selected subscriptions.
 
-#### Control plane 
+#### Control plane
 
 The control plane is a set of Azure Function apps and a storage account for caching. One control plane is deployed in your chosen subscription and performs the following tasks:
 - Discovery of resources in your chosen subscriptions that are able to log through diagnostic settings.
 - Automatic configuration of diagnostic settings on discovered resources to flow logs into a storage account that the log forwarders are tracking.
 - Scaling of log forwarders in regions where your resources are located, enabling them to match log volume dynamically.
 
-#### Log forwarders 
+#### Log forwarders
 
 Log forwarders consist of an Azure Container Apps job and storage account for logs. They are deployed by the control plane in each subscription you select for log forwarding. The number of log forwarders deployed per subscription scales according to the volume of logs generated by your resources. Log forwarders perform the following tasks:
 - Temporarily store logs generated from your resources' diagnostic settings in a storage account.
-- Process the stored logs and forward them to Datadog. 
-   
+- Process the stored logs and forward them to Datadog.
+
 In Azure, a resource's diagnostic settings can only target storage accounts within the same region. As such, the forwarders are spun up in each region where resources with diagnostic settings exist.
 
 See Azure's [Diagnostic settings in Azure Monitor][13] page for more information.
@@ -117,7 +117,7 @@ The ARM template grants the control plane only the permissions needed to manage
 
 - [Contributor][11] role at the **resource group** level, for the log-forwarding resource groups in the selected subscriptions.
    - This is needed to manage (create and delete) forwarder storage accounts and Container Apps jobs.
-   
+
 - [Website Contributor][12] role at the **control plane resource group** level, for updating the control plane function apps.
 
 No information about your resources is exported. Datadog only requests the information required to enable log output, and the only output of this architecture is the logs sent to Datadog.
@@ -142,17 +142,17 @@ The script first discovers any instances running in each subscription, then prom
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: https://portal.azure.com/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2FcreateUiDefinition.json
+[1]: https://portal.azure.com/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2FcreateUiDefinition.json
 [2]: https://app.datadoghq.com/organization-settings/api-keys
 [4]: /getting_started/site/
 [5]: https://learn.microsoft.com/en-us/azure/cloud-shell/overview
-[6]: https://portal.azure.us/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2FcreateUiDefinition.json
-[7]: https://portal.azure.cn/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2FcreateUiDefinition.json
+[6]: https://portal.azure.us/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2FcreateUiDefinition.json
+[7]: https://portal.azure.cn/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2FcreateUiDefinition.json
 [8]: https://azure.microsoft.com/products/container-apps
 [9]: https://learn.microsoft.com/azure/storage/common/storage-account-overview
 [10]: https://learn.microsoft.com/azure/azure-monitor/roles-permissions-security#monitoring-contributor
 [11]: https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/privileged#contributor
 [12]: https://learn.microsoft.com/azure/role-based-access-control/built-in-roles/web-and-mobile#website-contributor
 [13]: https://learn.microsoft.com/azure/azure-monitor/essentials/diagnostic-settings
 [14]: https://app.datadoghq.com/integrations/azure/add?config_azure-new-onboarding=true
-[15]: https://learn.microsoft.com/azure/azure-functions/
+[15]: https://learn.microsoft.com/azure/azure-functions/
diff --git a/content/es/logs/guide/azure-automated-log-forwarding.md b/content/es/logs/guide/azure-automated-log-forwarding.md
@@ -9,7 +9,7 @@ title: Configuración del reenvío automatizado de logs de Azure
 
 ## Información general
 
-Utiliza esta guía para automatizar la configuración del reenvío de logs de Azure con una plantilla de Azure Resource Manager (ARM). 
+Utiliza esta guía para automatizar la configuración del reenvío de logs de Azure con una plantilla de Azure Resource Manager (ARM).
 
 La plantilla ARM despliega recursos de una serie de servicios Azure (cuentas de almacenamiento y aplicaciones de función) en tus suscripciones, que recopilan y reenvían logs a Datadog. Los escalados de estos servicios aumentan o disminuyen automáticamente para adaptarse al volumen de logs. El escalado se gestiona mediante un plano de control, que es un conjunto de aplicaciones de función desplegadas en una suscripción y región de tu elección. Las cuentas de almacenamiento y las aplicaciones de función se despliegan en cada una de las suscripciones que reenvían logs a Datadog.
 
@@ -56,6 +56,6 @@ Empieza abriendo la [plantilla Automated Log Forwarding ARM][1]. Las secciones s
 
 {{< partial name="whats-next/whats-next.html" >}}
 
-[1]: https://portal.azure.com/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fddazurelfo.blob.core.windows.net%2Ftemplates%2FcreateUiDefinition.json
+[1]: https://portal.azure.com/#create/Microsoft.Template/uri/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2Fazuredeploy.json/createUIDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FDataDog%2Fintegrations-management%2Fmain%2Fazure%2Flogging_install%2Fdist%2FcreateUiDefinition.json
 [2]: https://app.datadoghq.com/organization-settings/api-keys
 [4]: /es/getting_started/site/
