Merge pull request #106965 from winthrop28/patch-93

Removing mention of no mixed backend pools.

Author: PRMerger8

articles/application-gateway/configuration-overview.md

@@ -337,7 +337,7 @@ For example, if *www.contoso.com* is specified in the **Host name** setting, the
 
 ## Back-end pool
 
-You can point a back-end pool to four types of backend members: a specific virtual machine, a virtual machine scale set, an IP address/FQDN, or an app service. Each back-end pool can point to multiple members of the same type. Pointing to members of different types in the same back-end pool isn't supported.
+You can point a back-end pool to four types of backend members: a specific virtual machine, a virtual machine scale set, an IP address/FQDN, or an app service. 
 
 After you create a back-end pool, you must associate it with one or more request-routing rules. You must also configure health probes for each back-end pool on your application gateway. When a request-routing rule condition is met, the application gateway forwards the traffic to the healthy servers (as determined by the health probes) in the corresponding back-end pool.