Merge pull request #216626 from KarlErickson/karler-fix-vnet

v-shils · web-flow · commit 462df9b96470 · 2022-10-31T14:12:49.000-07:00
vnet -&gt; virtual network
diff --git a/articles/spring-apps/concept-outbound-type.md b/articles/spring-apps/concept-outbound-type.md
@@ -30,7 +30,7 @@ By default, Azure Spring Apps provisions a Standard SKU Load Balancer that you c
 
 ## Limitations
 
-- You can only define `OutboundType` when you create a new Azure Spring Apps service instance, and you can't updated it afterwards. `OutboundType` works only with a VNet instance.
+- You can only define `OutboundType` when you create a new Azure Spring Apps service instance, and you can't updated it afterwards. `OutboundType` works only with a virtual network.
 - Setting `outboundType` to `UserDefinedRouting` requires a user-defined route with valid outbound connectivity for your instance.
 - Setting `outboundType` to `UserDefinedRouting` implies that the ingress source IP routed to the load-balancer may not match the instance's outgoing egress destination address.
 
@@ -50,7 +50,7 @@ The default `outboundType` value is `loadBalancer`. If `outboundType` is set to
 If `outboundType` is set to `userDefinedRouting`, Azure Spring Apps won't automatically configure egress paths. You must set up egress paths yourself. You could still find two load balancers in your resource group. They're only used for internal traffic and won't expose any public IP. You must prepare two route tables associated with two subnets: one to service the runtime and another for the user app.
 
 > [!IMPORTANT]
-> An `outboundType` of `userDefinedRouting` requires a route for `0.0.0.0/0` and the next hop destination of a network virtual appliance in the route table. For more information, see [Customer responsibilities for running Azure Spring Apps in VNET](vnet-customer-responsibilities.md).
+> An `outboundType` of `userDefinedRouting` requires a route for `0.0.0.0/0` and the next hop destination of a network virtual appliance in the route table. For more information, see [Customer responsibilities for running Azure Spring Apps in a virtual network](vnet-customer-responsibilities.md).
 
 ## See also
 
diff --git a/articles/spring-apps/how-to-access-app-from-internet-virtual-network.md b/articles/spring-apps/how-to-access-app-from-internet-virtual-network.md
@@ -25,7 +25,7 @@ If you don't want to use Application Gateway for advanced operations, you can ex
 
 - An Azure Spring Apps service instance deployed in a virtual network and an app created in it. For more information, see [Deploy Azure Spring Apps in a virtual network](./how-to-deploy-in-azure-virtual-network.md).
 
-## Assign a public fully qualified domain name (FQDN) for your application in a VNet injection instance
+## Assign a public fully qualified domain name (FQDN) for your application in a virtual network injection instance
 
 
 ### [Azure portal](#tab/azure-portal)
@@ -65,10 +65,10 @@ You can use a public URL to access your application both inside and outside the
 To ensure the security of your applications when you expose a public endpoint for them, secure the endpoint by filtering network traffic to your service with a network security group. For more information, see [Tutorial: Filter network traffic with a network security group using the Azure portal](../virtual-network/tutorial-filter-network-traffic.md). A network security group contains security rules that allow or deny inbound network traffic to, or outbound network traffic from, several types of Azure resources. For each rule, you can specify source and destination, port, and protocol.
 
 > [!NOTE]
-> If you couldn't access your application in VNet injection instance from internet after you have assigned a public FQDN, check your network security group first to see whether you have allowed such inbound traffic.
+> If you couldn't access your application in a virtual network injection instance from internet after you have assigned a public FQDN, check your network security group first to see whether you have allowed such inbound traffic.
 
 ## Next steps
 
 - [Expose applications with end-to-end TLS in a virtual network](./expose-apps-gateway-end-to-end-tls.md)
 - [Troubleshooting Azure Spring Apps in virtual networks](./troubleshooting-vnet.md)
-- [Customer responsibilities for running Azure Spring Apps in VNET](./vnet-customer-responsibilities.md)
+- [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md)
diff --git a/articles/spring-apps/how-to-appdynamics-java-agent-monitor.md b/articles/spring-apps/how-to-appdynamics-java-agent-monitor.md
@@ -237,9 +237,9 @@ The AppDynamics Agent will be upgraded regularly with JDK (quarterly). Agent upg
 * Existing applications using AppDynamics Agent before upgrade will be unchanged, but will require restart or redeploy to engage the new version of AppDynamics Agent.
 * Applications created after upgrade will use the new version of AppDynamics Agent.
 
-## Configure VNet injection instance outbound traffic
+## Configure virtual network injection instance outbound traffic
 
-For VNet injection instances of Azure Spring Apps, make sure the outbound traffic is configured correctly for AppDynamics Agent. For details, see [SaaS Domains and IP Ranges](https://docs.appdynamics.com/display/PAA/SaaS+Domains+and+IP+Ranges) and [Customer responsibilities for running Azure Spring Apps in VNET](vnet-customer-responsibilities.md).
+For virtual network injection instances of Azure Spring Apps, make sure the outbound traffic is configured correctly for AppDynamics Agent. For details, see [SaaS Domains and IP Ranges](https://docs.appdynamics.com/display/PAA/SaaS+Domains+and+IP+Ranges) and [Customer responsibilities for running Azure Spring Apps in a virtual network](vnet-customer-responsibilities.md).
 
 ## Understand the limitations
 
diff --git a/articles/spring-apps/how-to-configure-palo-alto.md b/articles/spring-apps/how-to-configure-palo-alto.md
@@ -22,7 +22,7 @@ This article describes how to use Azure Spring Apps with a Palo Alto firewall.
 
 For example, the [Azure Spring Apps reference architecture](./reference-architecture.md) includes an Azure Firewall to secure your applications. However, if your current deployments include a Palo Alto firewall, you can omit the Azure Firewall from the Azure Spring Apps deployment and use Palo Alto instead, as described in this article.
 
-You should keep configuration information, such as rules and address wildcards, in CSV files in a Git repository. This article shows you how to use automation to apply these files to Palo Alto. To understand the configuration to be applied to Palo Alto, see [Customer responsibilities for running Azure Spring Apps in VNET](./vnet-customer-responsibilities.md). 
+You should keep configuration information, such as rules and address wildcards, in CSV files in a Git repository. This article shows you how to use automation to apply these files to Palo Alto. To understand the configuration to be applied to Palo Alto, see [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md). 
 
 > [!Note]
 > In describing the use of REST APIs, this article uses the PowerShell variable syntax to indicate names and values that are left to your discretion. Be sure to use the same values in all the steps.
@@ -53,7 +53,7 @@ The rest of this article assumes you have the following two pre-configured netwo
 
 Next, create three CSV files.
 
-Name the first file *AzureSpringAppsServices.csv*. This file should contain ingress ports for Azure Spring Apps. The values in the following example are for demonstration purposes only. For all of the required values, see the [Azure Spring Apps network requirements](./vnet-customer-responsibilities.md#azure-spring-apps-network-requirements) section of [Customer responsibilities for running Azure Spring Apps in VNET](./vnet-customer-responsibilities.md).
+Name the first file *AzureSpringAppsServices.csv*. This file should contain ingress ports for Azure Spring Apps. The values in the following example are for demonstration purposes only. For all of the required values, see the [Azure Spring Apps network requirements](./vnet-customer-responsibilities.md#azure-spring-apps-network-requirements) section of [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md).
 
 ```CSV
 name,protocol,port,tag
diff --git a/articles/spring-apps/how-to-dynatrace-one-agent-monitor.md b/articles/spring-apps/how-to-dynatrace-one-agent-monitor.md
@@ -203,9 +203,9 @@ The Dynatrace OneAgent auto-upgrade is disabled and will be upgraded quarterly w
 * Existing applications using Dynatrace OneAgent before upgrade will be unchanged, but will require restart or redeploy to engage the new version of Dynatrace OneAgent.
 * Applications created after upgrade will use the new version of Dynatrace OneAgent.
 
-## VNet injection instance outbound traffic configuration
+## Virtual network injection instance outbound traffic configuration
 
-For a VNet injection instance of Azure Spring Apps, you need to make sure the outbound traffic for Dynatrace communication endpoints is configured correctly for Dynatrace OneAgent. For information about how to get `communicationEndpoints`, see [Deployment API - GET connectivity information for OneAgent](https://www.dynatrace.com/support/help/dynatrace-api/environment-api/deployment/oneagent/get-connectivity-info/). For more information, see [Customer responsibilities for running Azure Spring Apps in VNET](vnet-customer-responsibilities.md).
+For a virtual network injection instance of Azure Spring Apps, you need to make sure the outbound traffic for Dynatrace communication endpoints is configured correctly for Dynatrace OneAgent. For information about how to get `communicationEndpoints`, see [Deployment API - GET connectivity information for OneAgent](https://www.dynatrace.com/support/help/dynatrace-api/environment-api/deployment/oneagent/get-connectivity-info/). For more information, see [Customer responsibilities for running Azure Spring Apps in a virtual network](vnet-customer-responsibilities.md).
 
 ## Dynatrace support model
 
diff --git a/articles/spring-apps/how-to-self-diagnose-running-in-vnet.md b/articles/spring-apps/how-to-self-diagnose-running-in-vnet.md
@@ -1,6 +1,6 @@
 ---
-title: "How to self-diagnose Azure Spring Apps VNET"
-description: Learn how to self-diagnose and solve problems in Azure Spring Apps running in VNET.
+title: "How to self-diagnose Azure Spring Apps with virtual networks"
+description: Learn how to self-diagnose and solve problems in Azure Spring Apps running in virtual networks.
 author: karlerickson
 ms.author: karler
 ms.service: spring-apps
@@ -9,14 +9,14 @@ ms.date: 01/25/2021
 ms.custom: devx-track-java, event-tier1-build-2022
 ---
 
-# Self-diagnose running Azure Spring Apps in VNET
+# Self-diagnose running Azure Spring Apps in virtual networks
 
 > [!NOTE]
 > Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.
 
 **This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
 
-This article shows you how to use Azure Spring Apps diagnostics to diagnose and solve problems in Azure Spring Apps running in VNET.
+This article shows you how to use Azure Spring Apps diagnostics to diagnose and solve problems in Azure Spring Apps running in virtual networks.
 
 Azure Spring Apps diagnostics supports interactive troubleshooting apps running in virtual networks without configuration. Azure Spring Apps diagnostics identifies problems and guides you to information that helps troubleshoot and resolve them.
 
@@ -33,7 +33,7 @@ The following procedure starts diagnostics for networked applications.
 
 ## View a diagnostic report
 
-After you select the **Networking** category, you can view two issues related to Networking specific to your VNet injected Azure Spring Apps: **DNS Resolution** and **Required Outbound Traffic**.
+After you select the **Networking** category, you can view two issues related to Networking specific to your virtual-network injected Azure Spring Apps instances: **DNS Resolution** and **Required Outbound Traffic**.
 
    ![Self diagnostic options](media/spring-cloud-self-diagnose-vnet/self-diagostic-dns-req-outbound-options.png)
 
diff --git a/articles/spring-apps/reference-architecture.md b/articles/spring-apps/reference-architecture.md
@@ -35,10 +35,10 @@ Azure Spring Apps requires two dedicated subnets:
 * Service runtime
 * Spring Boot applications
 
-Each of these subnets requires a dedicated Azure Spring Apps cluster. Multiple clusters can't share the same subnets. The minimum size of each subnet is /28. The number of application instances that Azure Spring Apps can support varies based on the size of the subnet. You can find the detailed Virtual Network (VNET) requirements in the [Virtual network requirements][11] section of [Deploy Azure Spring Apps in a virtual network][17].
+Each of these subnets requires a dedicated Azure Spring Apps cluster. Multiple clusters can't share the same subnets. The minimum size of each subnet is /28. The number of application instances that Azure Spring Apps can support varies based on the size of the subnet. You can find the detailed virtual network requirements in the [Virtual network requirements][11] section of [Deploy Azure Spring Apps in a virtual network][17].
 
 > [!WARNING]
-> The selected subnet size can't overlap with the existing VNET address space, and shouldn't overlap with any peered or on-premises subnet address ranges.
+> The selected subnet size can't overlap with the existing virtual network address space, and shouldn't overlap with any peered or on-premises subnet address ranges.
 
 ## Use cases
 
@@ -235,7 +235,7 @@ The following list shows the CIS controls that address network security in this
 | 6.5            | Ensure that Network Watcher is 'Enabled'.                      |
 | 6.6            | Ensure that ingress using UDP is restricted from the internet. |
 
-Azure Spring Apps requires management traffic to egress from Azure when deployed in a secured environment. You must allow the network and application rules listed in [Customer responsibilities for running Azure Spring Apps in VNET](./vnet-customer-responsibilities.md).
+Azure Spring Apps requires management traffic to egress from Azure when deployed in a secured environment. You must allow the network and application rules listed in [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md).
 
 #### Application security
 
diff --git a/articles/spring-apps/toc.yml b/articles/spring-apps/toc.yml
@@ -234,7 +234,7 @@ items:
       href: how-to-create-user-defined-route-instance.md
     - name: Customize the ingress configuration in Azure Spring Apps
       href: how-to-configure-ingress.md
-    - name: Customer responsibilities running Azure Spring Apps in VNET
+    - name: Customer responsibilities running Azure Spring Apps in a virtual network
       href: vnet-customer-responsibilities.md
     - name: Troubleshooting Azure Spring Apps in virtual networks
       href: troubleshooting-vnet.md
@@ -274,7 +274,7 @@ items:
     items:
     - name: Self diagnose and solve problems
       href: how-to-self-diagnose-solve.md
-    - name: Self diagnose running in VNET
+    - name: Self diagnose running in virtual networks
       href: how-to-self-diagnose-running-in-vnet.md
     - name: Troubleshoot common issues
       href: troubleshoot.md
diff --git a/articles/spring-apps/troubleshooting-vnet.md b/articles/spring-apps/troubleshooting-vnet.md
@@ -38,7 +38,7 @@ To set up the Azure Spring Apps service instance by using the Resource Manager t
 | Error Message | How to fix |
 |------|------|
 | Resources created by Azure Spring Apps were disallowed by policy. | Network resources will be created when deploy Azure Spring Apps in your own virtual network. Please check whether you have [Azure Policy](../governance/policy/overview.md) defined to block those creation. Resources failed to be created can be found in error message. |
-| Required traffic is not allowlisted. | Please refer to [Customer Responsibilities for Running Azure Spring Apps in VNET](./vnet-customer-responsibilities.md) to ensure required traffic is allowlisted. |
+| Required traffic is not allowlisted. | Please refer to [Customer responsibilities for running Azure Spring Apps in a virtual network](./vnet-customer-responsibilities.md) to ensure required traffic is allowlisted. |
 
 ## My application can't be registered
 
diff --git a/articles/spring-apps/vnet-customer-responsibilities.md b/articles/spring-apps/vnet-customer-responsibilities.md
@@ -1,6 +1,6 @@
 ---
-title:  "Customer responsibilities running Azure Spring Apps in vnet"
-description: This article describes customer responsibilities running Azure Spring Apps in vnet.
+title:  "Customer responsibilities running Azure Spring Apps in a virtual network"
+description: This article describes customer responsibilities running Azure Spring Apps in a virtual network.
 author: karlerickson
 ms.author: karler
 ms.service: spring-apps
@@ -9,7 +9,7 @@ ms.date: 11/02/2021
 ms.custom: devx-track-java, event-tier1-build-2022
 ---
 
-# Customer responsibilities for running Azure Spring Apps in VNET
+# Customer responsibilities for running Azure Spring Apps in a virtual network
 
 > [!NOTE]
 > Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.
