From 5681049c047595d02265a5112f58c1a218ae96f6 Mon Sep 17 00:00:00 2001
From: Amit Chauhan <70937115+achauhan-scc@users.noreply.github.com>
Date: Fri, 28 Feb 2025 10:14:14 +0530
Subject: [PATCH] Update README.md (#3527)

---
 cli/jobs/single-step/on-behalf-of/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cli/jobs/single-step/on-behalf-of/README.md b/cli/jobs/single-step/on-behalf-of/README.md
index 3cdf32b7c38..948f04c6e24 100644
--- a/cli/jobs/single-step/on-behalf-of/README.md
+++ b/cli/jobs/single-step/on-behalf-of/README.md
@@ -10,7 +10,7 @@ description: An official sample showcasing use of on-behalf-of feature in AzureM
 
 # AzureML - On Behalf of Feature
 AzureML On Behalf of (OBO) is a powerful feature which allows AzureML users to use their AAD Identity within the training script of a remote Job (a job that runs on a remote compute). 
-
+*AzureML - On Behalf of* only supported on AMLCompute (Compute Cluster)
 ## Why should you use it ?
 
 AzureML makes your AAD identity available inside training script. Any resource you can access when running code on your machine can be accessed from the training script running on a remote compute.