Skip to content

Commit 043bc2e

Browse files
Apply suggestions from code review
Co-authored-by: Craig Shoemaker <[email protected]>
1 parent f841328 commit 043bc2e

File tree

1 file changed

+22
-12
lines changed

1 file changed

+22
-12
lines changed

articles/container-apps/ingress.md

Lines changed: 22 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -102,8 +102,8 @@ You can get access to the environment's unique identifier by querying the enviro
102102

103103
By default, ingress doesn't filter traffic. You can add restrictions to limit access based on IP addresses. There are two ways to filter traffic:
104104

105-
* Allowlist - deny all inbound traffic, but allow access from a list of IP address ranges
106-
* Denylist - allow all inbound traffic, but deny access from a list of IP address ranges
105+
* **Allowlist**: Deny all inbound traffic, but allow access from a list of IP address ranges
106+
* **Denylist**: Allow all inbound traffic, but deny access from a list of IP address ranges
107107

108108
> [!NOTE]
109109
> If defined, all rules must be the same type. You cannot combine allow rules and deny rules.
@@ -113,32 +113,42 @@ By default, ingress doesn't filter traffic. You can add restrictions to limit ac
113113
To allow inbound traffic from a specified IP range, run the following Azure CLI command.
114114

115115
```azurecli
116-
az containerapp ingress access-restriction set -n MyContainerapp -g MyResourceGroup --rule-
117-
name restrictionName --ip-address 192.168.1.1/28 --description "Restriction description."
118-
--action Allow
116+
az containerapp ingress access-restriction set \
117+
--name MyContainerapp \
118+
--resource-group MyResourceGroup \
119+
--rule-name restrictionName \
120+
--ip-address 192.168.1.1/28 \
121+
--description "Restriction description." \
122+
--action Allow
119123
```
120124

121-
Add more allow rules by repeating the command with different IP address ranges. When one or more allow rules are configured, any traffic from an IP address that doesn't match any of the rules is denied.
125+
Add more allow rules by repeating the command with different IP address ranges in the `--ip-address` parameter. When you configure one or more allow rules, any traffic from an IP address that doesn't match any of the rules is denied.
122126

123127
### Configure a denylist
124128

125129
To deny inbound traffic from a specified IP range, run the following Azure CLI command.
126130

127131
```azurecli
128-
az containerapp ingress access-restriction set -n MyContainerapp -g MyResourceGroup --rule-
129-
name my-restriction --ip-address 192.168.1.1/28 --description "Restriction description."
130-
--action Deny
132+
az containerapp ingress access-restriction set \
133+
--name MyContainerapp \
134+
--resource-group MyResourceGroup \
135+
--rule-name my-restriction \
136+
--ip-address 192.168.1.1/28 \
137+
--description "Restriction description."
138+
--action Deny
131139
```
132140

133-
Add more deny rules by repeating the command with different IP address ranges. When one or more allow rules are configured, any traffic from an IP address that doesn't match any of the rules is allowed.
141+
Add more deny rules by repeating the command with different IP address ranges in the `--ip-address` parameter. When you configure one or more deny rules, any traffic from an IP address that doesn't match any of the rules is allowed.
134142

135143
### Remove access restrictions
136144

137145
To remove an access restriction, run the following Azure CLI command.
138146

139147
```azurecli
140-
az containerapp ingress access-restriction remove -n MyContainerapp -g MyResourceGroup
141-
--rule-name my-restriction
148+
az containerapp ingress access-restriction remove
149+
--name MyContainerapp \
150+
--resource-group MyResourceGroup \
151+
--rule-name my-restriction
142152
```
143153

144154
## Next steps

0 commit comments

Comments
 (0)