more deletions

Author: mbender-ms

articles/virtual-network-manager/create-virtual-network-manager-template.md

@@ -77,10 +77,7 @@ The template defines multiple Azure resources:
     :::image type="content" source="media/create-virtual-network-manager-template/template-resources.png" alt-text="Screenshot of all deployed resources in Azure portal.":::
 
 1. Select the **avnm-EastUS** resource.
-1. In the **Network Groups** page,  select **Settings>NetworkGroups>ng-EastUS-static**.
-   
-   :::image type="content" source="media/create-virtual-network-manager-template/static-network-group.png" alt-text="Screenshot of deployed network groups in Azure portal.":::
-
+1. In the **Network Groups** page,  select **Settings** > **NetworkGroups** > **ng-EastUS-static**.
 1. On the **ng-EastUS-static** page, select **Settings>Group Members** and verify a set of virtual networks are deployed.
 
     :::image type="content" source="media/create-virtual-network-manager-template/mesh-group-members.png" alt-text="Screenshot of static members in network group for a static topology deployment.":::

articles/virtual-network-manager/how-to-block-network-traffic-portal.md

@@ -26,24 +26,12 @@ Before you start to configure security admin rules, confirm that you've done the
 1. Select **Security configuration** from the drop-down menu.
 1. On the **Basics** tab, enter a *Name* to identify this security configuration and select **Next: Rule collections**.
 
-    :::image type="content" source="./media/how-to-block-network-traffic-portal/security-configuration-name.png" alt-text="Screenshot of security configuration name field.":::
-
-## Add a rule collection
+## Add a rule collection and security rule
 
 1. Enter a *Name* to identify this rule collection and then select the *Target network groups* you want to apply the set of rules to.
-
-    :::image type="content" source="./media/how-to-block-network-traffic-portal/rule-collection-target.png" alt-text="Screenshot of rule collection name and target network groups.":::
-
-## Add a security rule
-
 1. Select **+ Add** from the *Add a rule collection page*.
-
-    :::image type="content" source="./media/how-to-block-network-traffic-portal/add-rule-button.png" alt-text="Screenshot of add a rule button.":::
-
 1. Enter or select the following information, then select **Add** to add the rule to the rule collection.
 
-    :::image type="content" source="./media/how-to-block-network-traffic-portal/add-rule.png" alt-text="Screenshot of add a rule page.":::
-
     | Setting | Value |
     | ------- | ----- |
     | Name | Enter the name **Deny_RDP** for the rule name. |
@@ -66,9 +54,6 @@ Before you start to configure security admin rules, confirm that you've done the
 1. Repeat steps 1-3 again if you want to add more rules to the rule collection.
 
 1. Once you're satisfied with all the rules you wanted to create, select **Add** to add the rule collection to the security admin configuration.
-
-    :::image type="content" source="./media/how-to-block-network-traffic-portal/save-rule-collection.png" alt-text="Screenshot of a rule collection.":::
-
 1. Then select **Review + Create** and **Create** to complete the security configuration.
 
 
@@ -77,13 +62,7 @@ Before you start to configure security admin rules, confirm that you've done the
 If you just created a new security admin configuration, make sure to deploy this configuration to apply to virtual networks in the network group.
 
 1. Select **Deployments** under *Settings*, then select **Deploy configuration**.
-
-    :::image type="content" source="./media/how-to-block-network-traffic-portal/deploy-configuration.png" alt-text="Screenshot of deploy a configuration button.":::
-
 1. Select the **Include security admin in your goal state** checkbox and choose the security configuration you created in the last section from the dropdown menu. Then choose the region(s) you would like to deploy this configuration to.
-
-    :::image type="content" source="./media/how-to-block-network-traffic-portal/deploy-security-configuration.png" alt-text="Screenshot of deploy a security configuration page.":::
-
 1. Select **Next** and **Deploy** to deploy the security admin configuration.
 
 ## Update existing security admin configuration

articles/virtual-network-manager/how-to-configure-cross-tenant-portal.md

@@ -37,12 +37,10 @@ In this task, you set up a scope connection to add a subscription from a target
 1. Log in to the Azure portal on the central management tenant.
 1. Search for **Virtual network managers** and select your network manager from the list.
 1. Under **Settings**, select **Cross-tenant connections**, and then select **Create cross-tenant connection**.
-
-   :::image type="content" source="media/how-to-configure-cross-tenant-portal/create-cross-tenant-connection.png" alt-text="Screenshot of cross-tenant connections in a network manager.":::
-
 1. On the **Create a connection** page, enter the connection name and target tenant information, and then select **Create**.
 
    :::image type="content" source="media/how-to-configure-cross-tenant-portal/create-connection-settings.png" alt-text="Screenshot of settings entered to create a connection.":::
+
 1. Verify that the scope connection is listed under **Cross-tenant connections** and the status is **Pending**.
 
 ## Create a network manager connection on a subscription in another tenant
@@ -51,13 +49,7 @@ After you create the scope connection, switch to the target managed tenant. Conn
 
 1. In the target tenant, search for **Virtual network manager** and select **Virtual Network Managers**.
 1. Under **Virtual Network Manager**, select **Cross-tenant connections**.
-
-   :::image type="content" source="media/how-to-configure-cross-tenant-portal/virtual-network-manager-overview.png" alt-text="Screenshot of network managers in Virtual Network Manager on a target tenant.":::
-
 1. Select **+ Create** or **Create a connection**.
-
-   :::image type="content" source="media/how-to-configure-cross-tenant-portal/create-connection-target.png" alt-text="Screenshot of the pane for cross-tenant connections.":::
-
 1. On the **Create a connection** page, enter the information for your central management tenant, and then select **Create**.
 
    :::image type="content" source="media/how-to-configure-cross-tenant-portal/create-connection-settings-target.png" alt-text="Screenshot of settings for creating a cross-tenant connection.":::
@@ -81,9 +73,6 @@ Now, add virtual networks from both tenants into a network group for static memb
 1. From your network manager, add a network group if needed.
 1. Select your network group, and then select **Add virtual networks** under **Manually add members**.
 1. On the **Manually add members** page, select **Tenant:...** next to the search box, select the linked tenant from the list, and then select **Apply**.
-
-   :::image type="content" source="media/how-to-configure-cross-tenant-portal/select-target-tenant-network-group.png" alt-text="Screenshot of available tenants to choose for static network group membership.":::
-
 1. To view the available virtual networks from the target managed tenant, select **Authenticate** and proceed through the authentication process. If you have multiple Azure accounts, select the one you're currently signed in with that has permissions to the target managed tenant.
 1. Select the virtual networks to include in the network group, and then select **Add**.