Skip to content

Commit 2d3d7bc

Browse files
Merge pull request #235055 from TheovanKraay/patch-39
Update network-rules.md
2 parents 8452f1b + 6919d53 commit 2d3d7bc

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

articles/managed-instance-apache-cassandra/network-rules.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,14 @@ ms.custom: ignite-fall-2021
1111

1212
# Required outbound network rules
1313

14-
The Azure Managed Instance for Apache Casandra service requires certain network rules to properly manage the service. By ensuring you have the proper rules exposed, you can keep your service secure and prevent operational issues.
14+
The Azure SQL Managed Instance for Apache Casandra service requires certain network rules to properly manage the service. By ensuring you have the proper rules exposed, you can keep your service secure and prevent operational issues.
15+
16+
> [!WARNING]
17+
> We recommend exercising caution when applying changes to firewall rules for an existing cluster. For example, if rules are not applied correctly, they might not be applied to existing connections, so it may appear that firewall changes have not caused any problems. However, automatic updates of the Cassandra Managed Instance nodes may subsequently fail. We recommend monitoring connectivity after any major firewall updates for some time to ensure there are no issues.
1518
1619
## Virtual network service tags
1720

18-
If you are using Azure Firewall to restrict outbound access, we highly recommend using [virtual network service tags](../virtual-network/service-tags-overview.md). Below are the tags required to make Azure Managed Instance for Apache Cassandra function properly.
21+
If you're using Azure Firewall to restrict outbound access, we highly recommend using [virtual network service tags](../virtual-network/service-tags-overview.md). Below are the tags required to make Azure SQL Managed Instance for Apache Cassandra function properly.
1922

2023
| Destination Service Tag | Protocol | Port | Use |
2124
|----------------------------------------------------------------------------------|----------|---------|------|
@@ -37,7 +40,7 @@ If you are using Azure Firewall to restrict outbound access, we highly recommend
3740
3841
## User-defined routes
3942

40-
If you are using a 3rd party Firewall to restrict outbound access, we highly recommend configuring [user-defined routes (UDRs)](../virtual-network/virtual-networks-udr-overview.md#user-defined) for Microsoft address prefixes, rather than attempting to allow connectivity through your own Firewall. See sample [bash script](https://github.com/Azure-Samples/cassandra-managed-instance-tools/blob/main/configureUDR.sh) to add the required address prefixes in user-defined routes.
43+
If you're using a third-party Firewall to restrict outbound access, we highly recommend configuring [user-defined routes (UDRs)](../virtual-network/virtual-networks-udr-overview.md#user-defined) for Microsoft address prefixes, rather than attempting to allow connectivity through your own Firewall. See sample [bash script](https://github.com/Azure-Samples/cassandra-managed-instance-tools/blob/main/configureUDR.sh) to add the required address prefixes in user-defined routes.
4144

4245
## Azure Global required network rules
4346

@@ -68,7 +71,7 @@ The system uses DNS names to reach the Azure services described in this article
6871

6972
## Internal port usage
7073

71-
The following ports are only accessible within the VNET (or peered vnets./express routes). Managed Instance for Apache Cassandra instances do not have a public IP and should not be made accessible on the Internet.
74+
The following ports are only accessible within the VNET (or peered vnets./express routes). SQL Managed Instance for Apache Cassandra instances do not have a public IP and should not be made accessible on the Internet.
7275

7376
| Port | Use |
7477
| ---- | --- |
@@ -80,7 +83,7 @@ The following ports are only accessible within the VNET (or peered vnets./expres
8083

8184
## Next steps
8285

83-
In this article, you learned about network rules to properly manage the service. Learn more about Azure Managed Instance for Apache Cassandra with the following articles:
86+
In this article, you learned about network rules to properly manage the service. Learn more about Azure SQL Managed Instance for Apache Cassandra with the following articles:
8487

85-
* [Overview of Azure Managed Instance for Apache Cassandra](introduction.md)
86-
* [Manage Azure Managed Instance for Apache Cassandra resources using Azure CLI](manage-resources-cli.md)
88+
* [Overview of Azure SQL Managed Instance for Apache Cassandra](introduction.md)
89+
* [Manage Azure SQL Managed Instance for Apache Cassandra resources using Azure CLI](manage-resources-cli.md)

0 commit comments

Comments
 (0)