Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into azure-operator-service-manager-best-practices

Author: ShawnJackson

articles/app-service/app-service-configure-premium-v4-tier.md

@@ -3,7 +3,7 @@ title: Configure Premium V4 tier
 description: Learn how to better performance for your web, mobile, and API app in Azure App Service by scaling to the new Premium V4 pricing tier.
 keywords: app service, azure app service, scale, scalable, app service plan, app service cost
 ms.topic: article
-ms.date: 06/18/2025
+ms.date: 07/17/2025
 ms.author: msangapu
 author: msangapu-msft
 ms.custom:
@@ -102,9 +102,11 @@ Premium V4 is available in the following regions:
 - East US
 - East US 2
 - France Central
+- Japan East
 - North Central US
 - North Europe
 - Norway East
+- Poland Central
 - Southeast Asia
 - Sweden Central
 - Switzerland North

articles/application-gateway/application-gateway-tls-version-retirement.md

@@ -5,7 +5,7 @@ services: application gateway
 author: jaesoni
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 05/15/2025
+ms.date: 07/18/2025
 ms.author: mbender
 ms.custom:
   - build-2025
@@ -84,7 +84,26 @@ You don't need to configure anything on your Application Gateway for the backend
 * For V2 SKUs: the connections to backend servers will always be with preferred TLS v1.3 and minimum up to TLS v1.2
 * For V1 SKUs: the connections to backend servers will always be with TLS v1.2
 
-You must ensure that your servers in the backend pools are compatible with these updated protocol versions. This compatibility avoids any disruptions when establishing a TLS/HTTPS connection with those backend servers.
+You must ensure that your servers in the backend pools are compatible with these updated protocol versions. This compatibility avoids any disruptions when establishing an TLS/HTTPS connection with those backend servers.
+
+## Identification methods
+
+### Metrics
+To determine whether clients connecting to your Application Gateway resource are utilizing TLS 1.0 or 1.1, use the `Client TLS protocol` metric provided by Application Gateway. For more information, see the [metrics documentation](monitor-application-gateway-reference.md#metrics). You can view it from the Portal by following these steps.
+
+1. Go to the Application Gateway resource in the Azure portal.
+2. In the left menu pane, open the "Metrics" blade in Monitoring section.
+3. Select metric as `Client TLS protocol` from the dropdown.
+4. To view granular protocol version information, select "Apply splitting" and choose "TLS protocol".
+
+[![A diagram showing metrics page with TLS version split for application gateway traffic.](media/application-gateway-tls-version-retirement/metric-tls-version.png)](media/application-gateway-tls-version-retirement/metric-tls-version.png#lightbox)
+
+### Logs
+You can also check the [Application Gateway Access logs](monitor-application-gateway-reference.md#access-log-category) to view this information in log format.
+
+### Error information
+Once support for TLS versions 1.0 and 1.1 is discontinued, clients may encounter errors such as `curl: (35) error:0A000410:SSL routines::sslv3 alert handshake failure`. Depending on the browser being used, various messages indicating TLS handshake failures may be displayed.
+
 
 ## Next steps
 

articles/application-gateway/for-containers/faq.yml

@@ -30,6 +30,9 @@ sections:
       - question: Does Application Gateway for Containers support Kubenet?
         answer: No, Application Gateway for Containers doesn't support Kubenet in favor of [CNI Overlay](/azure/aks/azure-cni-overlay). [Learn more](/azure/aks/upgrade-aks-ipam-and-dataplane) about migrating from Kubenet to CNI Overlay.
 
+      - question: Why does the frontend resolve to an IP address with an ASN location outside the region Application Gateway for Containers is deployed to?
+        answer: Application Gateway for Containers frontends resolve to any anycast IP address. Anycast IP addresses are advertised globally, which may lead to the ASN location being different from Application Gateway for Containers. The resolved location of the IP address is cosmetic and has no bearing on availability or performance in how clients connect.
+
   - name: Performance
     questions:
       - question: How does Application Gateway for Containers support high availability and scalability?
@@ -67,4 +70,4 @@ sections:
         answer: No.  Each ALB controller must use its own unique managed identity.
 
       - question: Can I share the same frontend resource between multiple Gateway and/or Ingress resources in Kubernetes?
-        answer: No. A frontend should be unique to a single Ingress or Gateway resource. Multiple hostnames and routes can be defined in a given Gateway or Ingress resource to eliminate the need for numerous frontend resources.
+        answer: No. A frontend should be unique to a single Ingress or Gateway resource. Multiple hostnames and routes can be defined in a given Gateway or Ingress resource to eliminate the need for numerous frontend resources.

articles/application-gateway/media/application-gateway-tls-version-retirement/metric-tls-version.png

@@ -81,12 +81,16 @@
       href: quickstart-go-console-app.md
     - name: Dynamic configuration
       href: enable-dynamic-configuration-go-console-app.md
+    - name: Feature management
+      href: quickstart-feature-flag-go-console.md
   - name: Go Gin
     items:
     - name: Configuration
       href: quickstart-go-web-app.md
     - name: Dynamic configuration
       href: enable-dynamic-configuration-gin-web-app.md
+    - name: Feature management
+      href: quickstart-feature-flag-go-gin.md
   - name: Azure Functions
     items:
     - name: Configuration
@@ -431,6 +435,10 @@
       items:
       - name: Feature reference
         href: ./feature-management-javascript-reference.md
+    - name: Go
+      items:
+      - name: Feature reference
+        href: https://pkg.go.dev/github.com/microsoft/Featuremanagement-Go/featuremanagement
     - name: Telemetry
       items:
       - name: Feature flag telemetry reference

articles/azure-app-configuration/TOC.yml

@@ -43,6 +43,12 @@ Service account owners can manage consent requests and private endpoints through
 
 When creating a private endpoint, you must specify the App Configuration store to which it connects. If you enable the geo-replication for an App Configuration store, you can connect to all replicas of the store using the same private endpoint. If you have multiple App Configuration stores, you need a separate private endpoint for each store.
 
+### Considerations for geo-replicated App Configuration stores
+
+When geo-replication is enabled for your App Configuration store, you can use a single private endpoint to connect to all replicas. However, since private endpoints are regional resources, this approach may not ensure connectivity in the event of a regional outage.
+
+For enhanced resilience, consider creating private endpoints for each replica of your geo-replicated store, in addition to a private endpoint for the origin store. This ensures that if one region becomes unavailable, clients can access the store through private endpoints provisioned in the same region as a replica. Ensure the relevant [DNS changes](#dns-changes-for-private-endpoints) are made so the endpoint for each replica resolves to the relevant IP address for the private endpoint in the respective replica's region.
+
 ### Connecting to private endpoints
 
 Azure relies upon DNS resolution to route connections from the VNet to the configuration store over a private link. You can quickly find connections strings in the Azure portal by selecting your App Configuration store, then selecting **Settings** > **Access Keys**.  

articles/azure-app-configuration/concept-private-endpoint.md

@@ -151,6 +151,10 @@ landingContent:
           url: quickstart-feature-flag-python.md
         - text: Node.js app
           url: quickstart-feature-flag-javascript.md
+        - text: Go console app
+          url: quickstart-feature-flag-go-console.md
+        - text: Go Gin web app
+          url: quickstart-feature-flag-go-gin.md
       - linkListType: tutorial
         links: 
         - text: Enable conditional features with feature filters
@@ -179,6 +183,8 @@ landingContent:
           url: https://microsoft.github.io/FeatureManagement-Python/html/index.html
         - text: JavaScript feature management
           url: feature-management-javascript-reference.md
+        - text: Go feature management
+          url: https://pkg.go.dev/github.com/microsoft/Featuremanagement-Go/featuremanagement
 
   - title: Client libraries and tools
     linkLists: