diff --git a/content/en/getting_started/integrations/azure.md b/content/en/getting_started/integrations/azure.md
index f47125267eac7..72c20c6ec5738 100644
--- a/content/en/getting_started/integrations/azure.md
+++ b/content/en/getting_started/integrations/azure.md
@@ -54,9 +54,14 @@ The `Datadog Admin Role`, or any other role with the `azure_configurations_manag
 
 {{% /collapse-content %}}
 
-<div class="alert alert-danger"><a href="https://docs.datadoghq.com/cloud_cost_management/setup/azure/?tab=billingaccounts&site=us3#overview">Cloud Cost Management</a> and <a href="https://docs.datadoghq.com/logs/log_configuration/archives/?tab=azurestorage">log archives</a> are only supported with the app registration setup method. If you set up the Datadog Azure Native integration for a US3 Datadog account, use the instructions on this page to create an app registration.
+{{< site-region region="us3" >}}
+
+<div class="alert alert-danger"><a href="https://docs.datadoghq.com/cloud_cost_management/setup/azure/?tab=billingaccounts&site=us3#overview">Cloud Cost Management</a> and <a href="https://docs.datadoghq.com/logs/log_configuration/archives/?tab=azurestorage">Log Archives</a> require the app registration setup method. For Datadog accounts using the Azure Native integration, follow the setup steps on this page to create an app registration. If a subscription is connected through both methods, a redundancy warning appears in the Azure integration tile. This warning can be safely ignored for Cloud Cost Management and Log Archives.
 </div>
 
+{{< /site-region >}}
+
+
 ## Setup
 
 Follow the instructions on this page to set up the **Azure integration** through an app registration, available for all Datadog sites.
@@ -254,10 +259,13 @@ Datadog recommends using the Agent or DaemonSet to send logs from Azure. If dire
 4. Acknowledge deployment warnings on the [Deployment tab][32].
 5. Start the deployment process on the [Review + create tab][33].
 
+{{< site-region region="us3" >}}
 
-<div class="alert alert-danger"><a href="https://docs.datadoghq.com/logs/log_configuration/archives/?tab=azurestorage">Log archives</a> are only supported with the app registration setup method. If you set up the Datadog Azure Native integration for a US3 Datadog account, you need to create an <a href="https://docs.datadoghq.com/integrations/guide/azure-manual-setup/?tab=manual#create-an-app-registration">App registration</a> to access this functionality.
+<div class="alert alert-danger"><a href="https://docs.datadoghq.com/logs/log_configuration/archives/?tab=azurestorage">Log Archives</a> require the app registration setup method. For Datadog accounts using the Azure Native integration, follow the steps on this page to create an app registration.
 </div>
 
+{{< /site-region >}}
+
 See [Azure Automated Log Forwarding Architecture][34] for more details.
 
 {{% /collapse-content %}}
diff --git a/layouts/shortcodes/azure-log-archiving.md b/layouts/shortcodes/azure-log-archiving.md
index 77aae785bc02c..b9b3dc9153cdb 100644
--- a/layouts/shortcodes/azure-log-archiving.md
+++ b/layouts/shortcodes/azure-log-archiving.md
@@ -4,8 +4,8 @@ Archiving logs to Azure Blob Storage requires an App Registration. If you haven'
 
 After configuring an App Registration, [create a log archive][1002] that writes to Azure Blob Storage.
 
-**Note**: If your storage bucket is in a subscription being monitored through the Azure Native integration, a warning is displayed in the Azure Integration Tile about the App Registration being redundant. You can ignore this warning.
+**Note**: If your storage bucket is in a subscription being monitored through the Azure Native integration, a redundancy warning appears in the Azure integration tile. This warning can be safely ignored for log archiving.
 
 [1000]: /logs/guide/azure-automated-log-forwarding
 [1001]: /logs/guide/azure-manual-log-forwarding
-[1002]: /logs/log_configuration/archives/?tab=azurestorage#configure-an-archive
\ No newline at end of file
+[1002]: /logs/log_configuration/archives/?tab=azurestorage#configure-an-archive