Optional updates"

Author: varunhari92

articles/azure-vmware/logs-via-logic-app.md

@@ -48,6 +48,27 @@ Make sure you have an Azure VMware Solution private cloud set up that is streami
     c. Select **RootManagerSharedAccessKey** and click on the copy icon next to **Primary connection string**.
     d. Navigate back to the browser tab with the Logic App and paste what you just copied into the **Connection String** field. Click **Add Connection**, then click **Next**. 
     e. Add the name of the event hub instance under **Event hub name**. The exact name of the Event hub can be found under **Entities**, then **Event Hubs** in your Event Hub tab.
-    f. Add the URI of the log server you intend to use under **Log destination URI**. Click **Next**, then click **Create**. This will now save the workflow 
+    f. Add the URI of the log server you intend to use under **Log destination URI**. Click **Next**, then click **Create**. This will now save the workflow that can be used to send the log messages from Azure VMware Solution to any syslog endpoint.
 
+## (Optional) Adding certificates, updating HTTP header, and configuring notifications
 
+### Certificates
+If Azure Logic Apps requires that the certificate from the log management server be recognizable, you may need to add this in the Logic Apps instance for the log transmission to work. This is a necessary step when using tools such as VMware Cloud Foundation Operations for Logs, for example. You may add this to the Azure Logic App instance using the following approach: 
+
+1. Export the certificate from the log management server and save it as a .cer file. 
+
+2. Under the Azure Logic App, select **Settings**, then click on **Certificates**. Navigate to the tab that says **Public key certificates (.cer)** and click on **Add certificate**. 
+
+3. Upload the certificate from Step 1 to **CER certificate file** and give the certificate a name, then click **Add** at the bottom. Once saved, copy the **Thumbprint** value. We will need that to for our environment variable in Step 4. 
+
+4. Under **Settings**, select **Environment variables**, then select **Add**. The name of the environment variable to add is **WEBSITE_LOAD_ROOT_CERTIFICATES** and the value is going to be the thumbprint you just copied. Select **Apply** at the bottom of the panel to save the changes and **Apply** again at the bottom of the list of environment variables to apply these changes. The new environment variable should take effect. 
+
+
+### HTTP Headers
+By default, the **HTTP-Trigger-to-Log-Destination** trigger in the workflow you created has the following key-value pairs under Headers: 
+ - **Content-Type** : **application/json**
+
+This will work by itself for log management tools such as VMware Cloud Foundation Operations for Logs. You may need to verify the log management server's ingestion cURL command to see if there are other headers that may need to be added. If you see other ones, please add them here and click **Save** at the top, so that the logs can be ingested properly into you log management server. 
+
+### Configuring Notifications
+You will notice in the last step of the workflow that there is an optional item called **Optional-Notification (README)**. You may replace this item with one of the plethora of triggers available in Azure Logic Apps, such as Outlook emails or Teams messages, to notify you in the event there is a failure sending your logs to your log management server.