Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into dns-azdns

Author: greg-lindsay

articles/ai-services/document-intelligence/concept-composed-models.md

@@ -230,9 +230,12 @@ items:
     - name: Custom model overview
       displayName: table, label, ocr, confidence, template, neural
       href: concept-custom.md
-    - name: Custom model lifecycle
-      displayName: custom, train, modelId, model ID, expiration, train, build
-      href: concept-custom-lifecycle.md
+    - name: 🆕 Composed models
+      displayName: custom, assign, modelId, model ID
+      href:  concept-composed-models.md
+    - name: 🆕 Incremental classifier
+      displayName: custom, classification, training
+      href: concept-incremental-classifier.md  
     - name: Custom template model
       displayName: structure, selection, labels, tables, tabular, train, template, neural, build mode, signatures, custom
       href: concept-custom-template.md
@@ -242,18 +245,15 @@ items:
     - name: Custom classification model
       displayName: custom, train, classification, splitting
       href: concept-custom-classifier.md
-    - name: 🆕 Incremental classifier
-      displayName: custom, classification, training
-      href: concept-incremental-classifier.md
     - name: Custom labels
       displayName: structure, selection, labels, tables, tabular, train
       href: concept-custom-label.md
     - name: Custom labeling tips
       displayName: structure, selection, labels, tables, tabular, train, tips
       href: concept-custom-label-tips.md
-    - name: Composed models
-      displayName: custom, assign, modelId, model ID
-      href:  concept-composed-models.md
+    - name: Custom model lifecycle
+      displayName: custom, train, modelId, model ID, expiration, train, build
+      href: concept-custom-lifecycle.md
 - name: Code samples
   items:
   - name: "C#/.NET"
@@ -328,4 +328,4 @@ items:
   - name: Support and help options
     href: ../../ai-services/cognitive-services-support-options.md?context=/azure/ai-services/document-intelligence/context/context
   - name: Privacy and cookies
-    href: https://privacy.microsoft.com/en-US/privacystatement
+    href: https://privacy.microsoft.com/en-US/privacystatement

articles/ai-services/document-intelligence/overview.md

@@ -225,6 +225,10 @@ For more information, see [Configure ASP.NET Core to work with proxy servers and
 
 ::: zone pivot="platform-linux"
 
+## Rewrite or redirect URL
+
+To rewrite or redirect URL, use the [URL rewriting middleware in ASP.NET Core](/aspnet/core/fundamentals/url-rewriting).
+
 ## Open SSH session in browser
 
 [!INCLUDE [Open SSH session in browser](../../includes/app-service-web-ssh-connect-builtin-no-h.md)]

articles/ai-services/document-intelligence/toc.yml

@@ -178,6 +178,22 @@ To deploy .ear files, [use FTP](deploy-ftp.md). Your .ear application is deploye
 
 Don't deploy your .war or .jar using FTP. The FTP tool is designed to upload startup scripts, dependencies, or other runtime files. It's not the optimal choice for deploying web apps.
 
+## Rewrite or redirect URL
+
+To rewrite or redirect URL, use one of the available URL rewriters, such as [UrlRewriteFilter](http://tuckey.org/urlrewrite/).
+
+::: zone pivot="java-tomcat"
+
+Tomcat also provides a [rewrite valve](https://tomcat.apache.org/tomcat-10.1-doc/rewrite.html).
+
+::: zone-end
+
+::: zone pivot="java-jboss"
+
+JBoss also provides a [rewrite valve](https://docs.jboss.org/jbossweb/7.0.x/rewrite.html).
+
+::: zone-end
+
 ## Logging and debugging apps
 
 Performance reports, traffic visualizations, and health checkups are available for each app through the Azure portal. For more information, see [Azure App Service diagnostics overview](overview-diagnostics.md).

articles/app-service/configure-language-dotnetcore.md

@@ -1,26 +1,30 @@
 ---
 title: Configure an internal load balancer (ILB) endpoint
 titleSuffix: Azure Application Gateway
-description: This article provides information on how to configure Application Gateway Standard v2 with a private frontend IP address
+description: This article provides information on how to configure Application Gateway Standard v1 with a private frontend IP address
 services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 02/07/2024
+ms.date: 08/09/2024
 ms.author: greglin
 ---
 
 # Configure an application gateway with an internal load balancer (ILB) endpoint
 
-Azure Application Gateway Standard v2 can be configured with an Internet-facing VIP or with an internal endpoint that isn't exposed to the Internet. An internal endpoint uses a private IP address for the frontend, which is also known as an *internal load balancer (ILB) endpoint*.
+Azure Application Gateway Standard v1 can be configured with an Internet-facing VIP or with an internal endpoint that isn't exposed to the Internet. An internal endpoint uses a private IP address for the frontend, which is also known as an *internal load balancer (ILB) endpoint*.
+
+> [!NOTE]
+> Application Gateway v1 is being retired. See the [v1 retiredment announcement](/azure/application-gateway/v1-retirement).<br>
+> To configure a v2 application gateway with a private frontend IP address, see [Private Application Gateway deployment](/azure/application-gateway/application-gateway-private-deployment).
 
 Configuring the gateway using a frontend private IP address is useful for internal line-of-business applications that aren't exposed to the Internet. It's also useful for services and tiers within a multi-tier application that are in a security boundary that isn't exposed to the Internet but:
 
 - still require round-robin load distribution
 - session stickiness
 - or Transport Layer Security (TLS) termination (previously known as Secure Sockets Layer (SSL)).
 
-This article guides you through the steps to configure a Standard v2 Application Gateway with an ILB using the Azure portal.
+This article guides you through the steps to configure a Standard v1 Application Gateway with an ILB using the Azure portal.
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
@@ -38,7 +42,7 @@ In this example, you create a new virtual network. You can create a virtual netw
 2. Select **Networking** and then select **Application Gateway** in the Featured list.
 3. Enter *myAppGateway* for the name of the application gateway and *myResourceGroupAG* for the new resource group.
 4. For **Region**, select **Central US**.
-5. For **Tier**, select **Standard V2**.
+5. For **Tier**, select **Standard**.
 6. Under **Configure virtual network** select **Create new**, and then enter these values for the virtual network:
    - *myVNet* - for the name of the virtual network.
    - *10.0.0.0/16* - for the virtual network address space.
@@ -59,7 +63,7 @@ In this example, you create a new virtual network. You can create a virtual netw
 9. Select **Next:Backends**.
 10. Select **Add a backend pool**.
 11. For **Name**, type *appGatewayBackendPool*.
-12. For **Add backend pool without targets**, select **Yes**. You'll add the targets later.
+12. For **Add backend pool without targets**, select **Yes**. Targets are added later.
 13. Select **Add**.
 14. Select **Next:Configuration**.
 15. Under **Routing rules**, select **Add a routing rule**.
@@ -80,9 +84,9 @@ In this example, you create a new virtual network. You can create a virtual netw
 
 ## Add backend pool
 
-The backend pool is used to route requests to the backend servers that serve the request. The backend can be composed of NICs, virtual machine scale sets, public IP addresses, internal IP addresses, fully qualified domain names (FQDN), and multi-tenant backends like Azure App Service. In this example, you use virtual machines as the target backend. You can either use existing virtual machines or create new ones. In this example, you create two virtual machines that Azure uses as backend servers for the application gateway.
+The backend pool is used to route requests to the backend servers that serve the request. The backend can be composed of NICs, virtual machine scale sets, public IP addresses, internal IP addresses, fully qualified domain names (FQDN), and multitenant backends like Azure App Service. In this example, you use virtual machines as the target backend. You can either use existing virtual machines or create new ones. In this example, you create two virtual machines that Azure uses as backend servers for the application gateway.
 
-To do this, you:
+To do this:
 
 1. Create two new virtual machines, *myVM* and *myVM2*, used as backend servers.
 2. Install IIS on the virtual machines to verify that the application gateway was created successfully.

articles/app-service/configure-language-java-deploy-run.md

@@ -151,6 +151,8 @@ The following list describes common words used with the Azure Maps services.
 
 ## G
 
+<a name="geobias"></a> **Geobias**:  A geospatial bias to improve the ranking of results. In some methods, this can be affected by setting the longitude and latitude parameters where available. In other cases it is purely internal.
+
 <a name="geocode"></a> **Geocode**: An address or location that has been converted into a coordinate that can be used to display that location on a map.
 
 <a name="geocoding"></a> **Geocoding**: Or _forward geocoding_, is the process of converting address of location data into coordinates.