From 54b785f9f6d0bd2154a2ee8cb87c9d6ac7534feb Mon Sep 17 00:00:00 2001
From: Naoya Hiraide <61998629+NAO-MSFT@users.noreply.github.com>
Date: Wed, 18 Jun 2025 10:21:56 +0900
Subject: [PATCH] Update rds-azure-adds.md

As per discussion with PG via SR, we agreed with this is an unsupported configuration now. Please contact me for the specific SR#.
---
 .../remote/remote-desktop-services/rds-azure-adds.md           | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/WindowsServerDocs/remote/remote-desktop-services/rds-azure-adds.md b/WindowsServerDocs/remote/remote-desktop-services/rds-azure-adds.md
index db9bdd80a5..0416f1ded4 100644
--- a/WindowsServerDocs/remote/remote-desktop-services/rds-azure-adds.md
+++ b/WindowsServerDocs/remote/remote-desktop-services/rds-azure-adds.md
@@ -6,6 +6,9 @@ ms.date: 7/3/2024
 ms.topic: how-to
 author: dknappettmsft
 ---
+>[!IMPORTANT]
+>This is currently an unsupported configuration
+
 # Integrate Microsoft Entra Domain Services with your RDS deployment
 
 You can use [Microsoft Entra Domain Services](/azure/active-directory-domain-services/active-directory-ds-overview) in your Remote Desktop Services deployment in the place of Windows Server Active Directory. Microsoft Entra Domain Services lets you use your existing Microsoft Entra identities in with classic Windows workloads.