Skip to content

Commit 4920ff1

Browse files
committed
re-added screenshots and fixed links
1 parent 82f4ef7 commit 4920ff1

File tree

6 files changed

+2
-5
lines changed

6 files changed

+2
-5
lines changed

articles/virtual-network-manager/concept-security-admins.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Security admin rules allow or deny traffic on specific ports, protocols, and sou
4444
To enforce security policies across multiple virtual networks, you [create and deploy a security admin configuration](how-to-block-network-traffic-portal.md). This configuration contains a set of rule collections, and each rule collection contains one or more security admin rules. Once created, you associate the rule collection with the network groups requiring security admin rules. The rules are then applied to all virtual networks contained in the network groups when the configuration is deployed. A single configuration provides a centralized and scalable enforcement of security policies across multiple virtual networks.
4545

4646
> [!IMPORTANT]
47-
> Only one security admin configuration can be deployed to a region. However, multiple connectivity configurations can exist in a region. To deploy multiple security admin configurations to a region, you can [create multiple rule collections](how-to-block-network-traffic-portal.md#add-a-rule-collection) in a security configuration instead.
47+
> Only one security admin configuration can be deployed to a region. However, multiple connectivity configurations can exist in a region. To deploy multiple security admin configurations to a region, you can [create multiple rule collections](how-to-block-network-traffic-portal.md#add-a-rule-collection-and-security-rule) in a security configuration instead.
4848
4949
### How security admin rules and network security groups (NSGs) are evaluated
5050

articles/virtual-network-manager/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ Normally, security admin rules are defined to block traffic across virtual netwo
147147

148148
### How can I deploy multiple security admin configurations to a region?
149149

150-
You can deploy only one security admin configuration to a region. However, multiple connectivity configurations can exist in a region if you [create multiple rule collections](how-to-block-network-traffic-portal.md#add-a-rule-collection) in a security configuration.
150+
You can deploy only one security admin configuration to a region. However, multiple connectivity configurations can exist in a region if you [create multiple rule collections](how-to-block-network-traffic-portal.md#add-a-rule-collection-and-security-rule) in a security configuration.
151151

152152
### Do security admin rules apply to Azure private endpoints?
153153

articles/virtual-network-manager/how-to-block-high-risk-ports.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -113,9 +113,6 @@ In this section, you define the security rule to block high-risk network traffic
113113
In this section, the rules created take effect when you deploy the security admin configuration.
114114

115115
1. Select **Deployments** under *Settings*, then select **Deploy configuration**.
116-
117-
:::image type="content" source="./media/how-to-block-network-traffic-portal/deploy-configuration.png" alt-text="Screenshot of deploy a configuration button.":::
118-
119116
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.
120117
1. Select **Next** and **Deploy** to deploy the security admin configuration.
121118

36 KB
Loading
25.5 KB
Loading
32.9 KB
Loading

0 commit comments

Comments
 (0)