edit pass: six-azure-managed-instance-for-apache-cassandra-articles

Author: ShawnJackson

articles/managed-instance-apache-cassandra/jaeger.md

@@ -11,27 +11,27 @@ ms.date: 12/08/2023
 
 # Run Jaeger with Azure Managed Instance for Apache Cassandra
 
-Jaeger, a distributed tracing platform for monitoring microservices, enables the fast identification of performance challenges and optimization. Through features, like tracing instrumentation and logging integration.
-
-The article specifically details the use of the sample application HotROD and Jaeger alongside Azure Managed Instance for Apache Cassandra for efficient storage monitoring.
+Jaeger is a distributed tracing platform for monitoring microservices. It enables the fast identification of performance challenges and optimization through features like tracing instrumentation and logging integration.
 
+The article details the use of the sample application HotROD and Jaeger alongside Azure Managed Instance for Apache Cassandra for efficient storage monitoring.
 
 ## Prerequisites and setup
-* [Create an Azure Managed Instance for Apache Cassandra cluster](create-cluster-cli.md).
-* [Ensure Docker is installed](https://www.docker.com/get-started/).
 
+* [Create an Azure Managed Instance for Apache Cassandra cluster](create-cluster-cli.md).
+* [Ensure that Docker is installed](https://www.docker.com/get-started/).
 
 ## Use Jaeger with Azure Managed Instance for Apache Cassandra
+
 1. [Download the Jaeger repository](https://github.com/jaegertracing/jaeger.git).
-1. Navigate to the docker-compose folder `cd jaeger\docker-compose`.
-1. Add your Azure Managed Instance Cassandra cluster credentials to the `jaeger-collector and jaeger-query` section within the `jaeger-docker-compose.yml` file:
+1. Go to the *docker-compose* folder: `cd jaeger\docker-compose`.
+1. In the *jaeger-docker-compose.yml* file, add your Azure Managed Instance for Apache Cassandra cluster credentials to the `jaeger-collector` and `jaeger-query` sections:
 
     ```yml
         command: ["--cassandra.port=9042", "--cassandra.servers=seed_nodes_mi_datacenters", "--cassandra.username=cassandra", "--cassandra.password=cassandra_mi_password","--cassandra.tls.skip-host-verify","--cassandra.tls.enabled", 
         "--cassandra.keyspace=jaeger_v1_dc1" ]
-    ``` 
+    ```
 
-1. Additionally, add the environment variables to the `cassandra-schema and jaeger-collector`:`
+1. Add the environment variables to the `cassandra-schema` and `jaeger-collector` sections:
 
     ```yml
     environment: 
@@ -41,7 +41,9 @@ The article specifically details the use of the sample application HotROD and Ja
         - CQLSH_SSL=--ssl
         ...
     ```
-1. To connect your Azure Managed Instance Cassandra cluster, add the Cassandra sign-in credentials to the `cassandra-schema`:
+
+1. To connect your Azure Managed Instance Cassandra cluster, add the Cassandra sign-in credentials to the `cassandra-schema` section:
+
     ```yml
       environment:
         ...
@@ -51,25 +53,30 @@ The article specifically details the use of the sample application HotROD and Ja
         - CASSANDRA_USERNAME=cassandra
         ...
     ```
+
 1. Run `docker-compose -f jaeger-docker-compose.yml up -d` to start the application.
 
-    :::image type="content" source="./media/jaeger/jaeger-running.png" alt-text="Screenshot of running jaeger." lightbox="./media/jaeger/jaeger-running.png" border="true":::
+    :::image type="content" source="./media/jaeger/jaeger-running.png" alt-text="Screenshot of a running Jaeger application." lightbox="./media/jaeger/jaeger-running.png" border="true":::
 
     > [!TIP]
-    > Five containers are created, and you should be able to access the test application at http://localhost:8080/ to generate traces that can be viewed at http://localhost:16686/search.
+    > Five containers are created, and you should be able to access the test application at `http://localhost:8080/` to generate traces that can be viewed at `http://localhost:16686/search`.
 
 1. Once the containers are running, access the Jaeger UI to view traces from the application.
+
     :::image type="content" source="./media/jaeger/jaeger-page-1.png" alt-text="Screenshot of jaeger web interface." lightbox="./media/jaeger/jaeger-page-1.png" border="true":::
 
 1. Verify by inspecting your Azure Managed Instance cluster.
+
     :::image type="content" source="./media/jaeger/jaeger-table-1.png" alt-text="Screenshot of jaeger tables in managed instance cluster." lightbox="./media/jaeger/jaeger-table-1.png" border="true":::
 
-1.  Refer to the traces table to view the data related to step 7.
+1. Refer to the traces table to view the data related to step 7.
+
     :::image type="content" source="./media/jaeger/jaeger-table-2.png" alt-text="Screenshot of jaeger trace table." lightbox="./media/jaeger/jaeger-table-2.png" border="true":::
 
+## Support
 
-## FAQs
-If you encounter issues running or testing Jaeger, open a support ticket. Provide the subscription ID and account name where your Jaeger test is running.
+If you have problems running or testing Jaeger, open a support ticket. Provide the subscription ID and account name where your Jaeger test is running.
 
 ## Next steps
-- Learn about [hybrid cluster configuration](configure-hybrid-cluster.md) in Azure Managed Instance for Apache Cassandra.
+
+* Learn about [hybrid cluster configuration](configure-hybrid-cluster.md) in Azure Managed Instance for Apache Cassandra.

articles/managed-instance-apache-cassandra/use-vpn.md

@@ -1,6 +1,6 @@
 ---
-title: Use VPN with Azure Managed Instance for Apache Cassandra
-description: Discover how to secure your cluster with vpn when you use Azure Managed Instance for Apache Cassandra.
+title: Use a VPN with Azure Managed Instance for Apache Cassandra
+description: Discover how to secure your cluster with a VPN when you use Azure Managed Instance for Apache Cassandra.
 author: IriaOsara
 ms.author: iriaosara
 ms.service: managed-instance-apache-cassandra
@@ -9,20 +9,18 @@ ms.date: 02/08/2024
 ms.devlang: azurecli
 
 ---
-# Use VPN with Azure Managed Instance for Apache Cassandra
+# Use a VPN with Azure Managed Instance for Apache Cassandra
 
-Azure Managed Instance for Apache Cassandra nodes requires access to many other Azure services when injected into your VNet. Normally this is enabled by ensuring your VNet has outbound access to the internet. If your security policy prohibits outbound access, you can also configure firewall rules or UDRs for the appropriate access, for more information, see [here](network-rules.md).
+Azure Managed Instance for Apache Cassandra nodes require access to many other Azure services when they're injected into your virtual network. Normally, you enable this access by ensuring that your virtual network has outbound access to the internet. If your security policy prohibits outbound access, you can configure firewall rules or user-defined routes for the appropriate access. For more information, see [Required outbound network rules](network-rules.md).
 
-However, if you have internal security concerns around data exfiltration, your security policy might also even prohibit direct access to these services from your VNet. By using a VPN with your Azure Managed Instance for Apache Cassandra, you can ensure that data nodes in the VNet communicate only to a single secure VPN endpoint, with no direct access to any other services.
+However, if you have internal security concerns about data exfiltration, your security policy might prohibit direct access to these services from your virtual network. By using a virtual private network (VPN) with Azure Managed Instance for Apache Cassandra, you can ensure that data nodes in the virtual network communicate with only a single VPN endpoint, with no direct access to any other services.
 
 > [!IMPORTANT]
-> Using VPN with Azure Managed Instance for Apache Cassandra is in public preview.
-> This feature is provided without a service level agreement, and it's not recommended for production workloads.
-> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+> The ability to use a VPN with Azure Managed Instance for Apache Cassandra is in public preview. This feature is provided without a service-level agreement, and we don't recommend it for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-## How to use VPN with Azure Managed Instance for Apache Cassandra
+## How to use a VPN with Azure Managed Instance for Apache Cassandra
 
-1. Create a cluster of Cassandra Managed Instance using "VPN" as the value for the `--azure-connection-method` option:
+1. Create an Azure Managed Instance for Apache Cassandra cluster by using `"VPN"` as the value for the `--azure-connection-method` option:
 
     ```bash
     az managed-cassandra cluster create \
@@ -33,26 +31,28 @@ However, if you have internal security concerns around data exfiltration, your s
     --initial-cassandra-admin-password "password"
     ```
 
-1. Use the following command to see the cluster properties. From the output, make a copy of the `privateLinkResourceId` ID:
+1. Use the following command to see the cluster properties:
 
     ```bash
     az managed-cassandra cluster show \
     --resource-group "vpn-test-rg" \
     --cluster-name "vpn-test-cluster"
     ```
 
-1. On the portal, [create a private endpoint](../cosmos-db/how-to-configure-private-endpoints.md)
-    1. On the Resource tab, select "Connect to an Azure resource by resource ID or alias." as the connection method and `Microsoft.Network/privateLinkServices` as the resource type. Enter the `privateLinkResourceId` from step (2).
-    1. On the Virtual Network tab, select your virtual network's subnet and make sure to select the option for "Statically allocate IP address."
+    From the output, make a copy of the `privateLinkResourceId` ID.
+
+1. In the Azure portal, [create a private endpoint](../cosmos-db/how-to-configure-private-endpoints.md) by using these details:
+    1. On the **Resource** tab, select **Connect to an Azure resource by resource ID or alias** as the connection method and **Microsoft.Network/privateLinkServices** as the resource type. Enter the `privateLinkResourceId` value from the previous step.
+    1. On the **Virtual Network** tab, select your virtual network's subnet, and select the **Statically allocate IP address** option.
     1. Validate and create.
 
    > [!NOTE]
-   > At the moment, the connection between our management service and your private endpoint requires the Azure Managed Instance for Apache Cassandra team [email protected] to approve it.
-    
-1. Get the IP address of your private endpoint NIC.
+   > At the moment, the connection between the management service and your private endpoint requires approval from the [Azure Managed Instance for Apache Cassandra team](mailto:[email protected]).
 
-1. Create a new data center using the IP address from (5) as the `--private-endpoint-ip-address` parameter.
+1. Get the IP address of your private endpoint's network interface.
 
+1. Create a new datacenter by using the IP address from the previous step as the `--private-endpoint-ip-address` parameter.
 
 ## Next steps
+
 - Learn about [hybrid cluster configuration](configure-hybrid-cluster.md) in Azure Managed Instance for Apache Cassandra.