Azure R3 M19 Pre-ship environment While Testing EDS - Secret Service API is not behaving, Intermittently it comes up with a message of 502 Bad Gateway

@Srini [EPAM Azure] @Saketh Somaraju [EPAM] - When I am trying to execute the Secret Service API to create Secret Client ID for EDS testing, The service seems to be hanging and after long delay 5+ mins comes up with 502 Bad Gateway. This was seen around 4:30 pm CST, Then again it starts working for a while and then again it gives the 502 message
The problem appears to be showing up only when one is trying to access Secret Service APIs, Specially while creating/updating the sceret keys.

curl --location 'https://osdu-ship.msft-osdu-test.org/api/secret/v1/secrets' \
--header 'Authorization: Bearer eyJ0eXAiOi...Truncated...gvsfiq5r2WjILZG0NoA' \
--header 'Content-Type: application/json' \
--header 'data-partition-id: opendes' \
--data '{
  "key": "GC-test-clientID-KTAug102023",	
  "value": "605457357143-6h6uq...Truncated...googleusercontent.com",
  "enabled": true
}'

Response 502 Bad Gateway
<html>

<head>
	<title>502 Bad Gateway</title>
</head>

<body>
	<center>
		<h1>502 Bad Gateway</h1>
	</center>
	<hr>
	<center>Microsoft-Azure-Application-Gateway/v2</center>
</body>

</html>

@chad @debasisc @AshishSaxenaAccenture @Srinivasan_Narayanan

It allows me to create couple of keys and then again it runs into 502 Bad Gateway message. Again after a while I can create few and then same issue.

Edited by Kamlesh Todai