Skip to content

Commit 2c221b5

Browse files
authored
Changed azure to Azure
1 parent 471221d commit 2c221b5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/hdinsight/hdinsight-plan-virtual-network-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -238,7 +238,7 @@ If you use network security groups or user-defined routes to control traffic, se
238238
239239
## <a id="hdinsight-ports"></a> Required ports
240240
241-
If you plan on using a **firewall** and access the cluster from outside on certain ports, you might need to allow traffic on those ports needed for your scenario. By default, no special whitelisting of ports is needed as long as the azure management traffic explained in the previous section is allowed to reach cluster on port 443.
241+
If you plan on using a **firewall** and access the cluster from outside on certain ports, you might need to allow traffic on those ports needed for your scenario. By default, no special whitelisting of ports is needed as long as the Azure management traffic explained in the previous section is allowed to reach cluster on port 443.
242242
243243
For a list of ports for specific services, see the [Ports used by Apache Hadoop services on HDInsight](hdinsight-hadoop-port-settings-for-services.md) document.
244244

0 commit comments

Comments
 (0)