Added Crontab instructions + Added more information for create monitor fields.

Author: mohitmakhija1

articles/sap/monitor/provider-linux.md

@@ -55,6 +55,20 @@ cd node_exporter-*.*-amd64
 nohup ./node_exporter --web.listen-address=":9100" &
 ```
 
+### Setting up cron job to start Node exporter on VM restart
+
+1. If the target virtual machine is restarted/stopped, node exporter is also stopped, and needs to be manually started again to continue monitoring.
+1. Run `sudo crontab -e` command to open cron file.
+1. Add the command `@reboot cd /path/to/node/exporter && nohup ./node_exporter &` at the end of cron file. This will start node exporter on VM reboot.
+
+```shell
+# if you do not have a crontab file already, create one by running the command: sudo crontab -e
+sudo crontab -l > crontab_new
+echo "@reboot cd /path/to/node/exporter && nohup ./node_exporter &" >> crontab_new
+sudo crontab crontab_new
+sudo rm crontab_new
+```
+
 ## Prerequisites to enable secure communication
 
 To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow the steps [mentioned here](https://prometheus.io/docs/guides/tls-encryption/)
@@ -104,19 +118,6 @@ When the provider settings validation operation fails with the code ‘Prometheu
 1. Run `nohup ./node_exporter &` command to enable node_exporter.
 1. Adding nohup and & to above command decouples the node_exporter from linux machine commandline. If not included node_exporter would stop when the commandline is closed.
 
-### Setting up cron job to start Node exporter on VM restart
-
-1. If the target virtual machine is restarted/stopped, node exporter is also stopped, and needs to be manually started again to continue monitoring.
-1. Run `sudo crontab -e` command to open cron file.
-1. Add the command `@reboot cd /path/to/node/exporter && nohup ./node_exporter &` at the end of cron file. This will start node exporter on VM reboot.
-
-```shell
-sudo crontab -l > crontab_new
-echo "@reboot cd /path/to/node/exporter && nohup ./node_exporter &" >> crontab_new
-sudo crontab crontab_new
-sudo rm crontab_new
-```
-
 ## Next steps
 
 > [!div class="nextstepaction"]

articles/sap/monitor/quickstart-portal.md

@@ -26,23 +26,33 @@ If you don't have an Azure subscription, create a [free](https://azure.microsoft
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
-1. In Azure **Search**, select **Azure Monitor for SAP solutions**.
+2. In Azure **Search**, select **Azure Monitor for SAP solutions**.
 
     ![Diagram that shows Azure Monitor for SAP solutions Quick Start.](./media/quickstart-portal/azure-monitor-quickstart-1-new.png)
 
 
+3. On the **Basics** tab, provide the required values.
+   1. **Workload Region** is the region where the monitoring resources are created, make sure to select a region which is same as your virtual network.
+   2. **Service Region** is automatically selected based on your Workload Region selection.
+   3. For **Virtual Network** field please select a virtual network which has connectivity to your SAP systems.
+   4. For the **Subnet** field, select a subnet which has connectivity to your SAP systems. You can use an existing subnet or create a new subnet. Make sure that you select a subnet which is an **IPv4/25 block or larger**.
+   5. For **Log Analytics Workspace**, you can use an existing Log Analytics workspace or create a new one. If you create a new workspace, it will created inside the managed resource group along with other monitoring resources.
+   6. When entering **managed resource group** name, make sure to use a unique name. This name will be used to create a resource group which will contain all the monitoring resources.
 
-1. On the **Basics** tab, provide the required values. If applicable, you can use an existing Log Analytics workspace.
- 
+   <br/>
 
     ![Diagram that shows Azure Monitor for SAP solutions Quick Start 2.](./media/quickstart-portal/azure-monitor-quickstart-2-new.png)
 
+4. On the **Providers** tab, you can start creating providers along with the monitoring resource. You can also create providers later by navigating to the **Providers** tab in the Azure Monitor for SAP solutions resource.
+5. On the **Tags** tab, you can add tags to the monitoring resource. Please make sure to add all the mandatory tags in case you have a tag policy in place.
+6. On the **Review + create** tab, review the details and click **Create**.
+
 
 ## Create Azure Monitor for SAP solutions (classic) monitoring resource
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
-1. In Azure **Marketplace** or **Search**, select **Azure Monitor for SAP solutions (classic)**.
+2. In Azure **Marketplace** or **Search**, select **Azure Monitor for SAP solutions (classic)**.
 
   ![Diagram shows Azure Monitor for SAP solutions classic quick start page.](./media/quickstart-portal/azure-monitor-quickstart-classic.png)
 
@@ -51,13 +61,12 @@ If you don't have an Azure subscription, create a [free](https://azure.microsoft
 
    :::image type="content" source="./media/quickstart-portal/azure-monitor-quickstart-2.png" alt-text="Screenshot that shows configuration options on the Basics tab." lightbox="./media/quickstart-portal/azure-monitor-quickstart-2.png":::
 
-   When you're selecting a virtual network, ensure that the systems you want to monitor are reachable from within that virtual network. 
+   When you're selecting a virtual network, ensure that the systems you want to monitor are reachable from within that virtual network.
 
    > [!IMPORTANT]
    > Selecting **Share** for **Share data with Microsoft support** enables our support teams to help you with troubleshooting. This feature is available only for Azure Monitor for SAP solutions (classic)
 
 
-
 ## Next steps
 
 Learn more about Azure Monitor for SAP solutions.