Merge pull request #294938 from Mzamankhan/patch-16

Update howto-manage-secrets.md

Author: prmerger-automator[bot]

articles/iot-operations/secure-iot-ops/howto-manage-secrets.md

@@ -34,7 +34,7 @@ Secrets are used in asset endpoints and data flow endpoints for authentication.
 
 - **Create a new secret**: creates a secret reference in the Azure Key Vault and also automatically synchronizes the secret down to the edge using Secret Store extension. Use this option if you didn't create the secret you require for this scenario in the key vault beforehand. 
 
-- **Add from Azure Key Vault**: synchronizes an existing secret in key vault down to the edge if it wasn't synchronized before. Selecting this option shows you the list of secret references in the selected key vault. Use this option if you created the secret in the key vault beforehand.
+- **Add from Azure Key Vault**: synchronizes an existing secret in key vault down to the edge if it wasn't synchronized before. Selecting this option shows you the list of secret references in the selected key vault. Use this option if you created the secret in the key vault beforehand. *Only the latest version of the secret is synced to the edge*.
 
 When you add the username and password references to the asset endpoints or data flow endpoints, you then need to give the synchronized secret a name. The secret references will be saved in the edge with this given name as one resource. In the example from the screenshot below, the username and password references are saved to the edge as *edp1secrets*.
 
@@ -47,4 +47,4 @@ You can use **Manage secrets** for asset endpoints and data flow endpoints to ma
 You can delete synced secrets as well in manage secrets. When you delete a synced secret, it only deletes the synced secret from the edge, and doesn't delete the contained secret reference from key vault. 
 
 > [!NOTE]
-> Before deleting a synced secret, make sure that all references to the secret from Azure IoT Operations components are removed.
+> Before deleting a synced secret, make sure that all references to the secret from Azure IoT Operations components are removed.