Update on-premises-application-provisioning-architecture.md

Author: ArvindHarinder1

articles/active-directory/app-provisioning/on-premises-application-provisioning-architecture.md

@@ -7,7 +7,7 @@ manager: amycolannino
 ms.service: active-directory
 ms.workload: identity
 ms.topic: overview
-ms.date: 08/26/2022
+ms.date: 11/04/2022
 ms.subservice: hybrid
 ms.author: billmath
 ms.collection: M365-identity-device-management
@@ -93,6 +93,8 @@ You can define one or more matching attribute(s) and prioritize them based on th
 - The agent must communicate with both Azure and your application, so the placement of the agent affects the latency of those two connections. You can minimize the latency of the end-to-end traffic by optimizing each network connection. Each connection can be optimized by:
   - Reducing the distance between the two ends of the hop.
   - Choosing the right network to traverse. For example, traversing a private network rather than the public internet might be faster because of dedicated links.
+- The agent and ECMA Host rely on a certificate for communication. The certificate generated by the ECMA host should only be used for testing purposes. Please use a certificiate from a trusted CA for production use cases. The self-signed certificate has a two year expiry and cannot be revoked. 
+