Merge branch 'main' into matternst7258/cluster-resource-hydration

matternst7258 · matternst7258 · commit 832af3da7b0d · 2024-10-30T11:02:56.000-05:00
merge main
diff --git a/articles/azure-cache-for-redis/cache-remove-tls-10-11.md b/articles/azure-cache-for-redis/cache-remove-tls-10-11.md
@@ -13,12 +13,12 @@ ms.devlang: csharp
 
 # Remove TLS 1.0 and 1.1 from use with Azure Cache for Redis
 
-To meet the industry-wide push toward the exclusive use of Transport Layer Security (TLS) version 1.2 or later, Azure Cache for Redis is moving toward requiring the use of the TLS 1.2 in November 2024. TLS versions 1.0 and 1.1 are known to be susceptible to attacks such as BEAST and POODLE, and to have other Common Vulnerabilities and Exposures (CVE) weaknesses.
+To meet the industry-wide push toward the exclusive use of Transport Layer Security (TLS) version 1.2 or later, Azure Cache for Redis is moving toward requiring the use of the TLS 1.2 in March 2025. TLS versions 1.0 and 1.1 are known to be susceptible to attacks such as BEAST and POODLE, and to have other Common Vulnerabilities and Exposures (CVE) weaknesses.
 
 TLS versions 1.0 and 1.1 also don't support the modern encryption methods and cipher suites recommended by Payment Card Industry (PCI) compliance standards. This [TLS security blog](https://www.acunetix.com/blog/articles/tls-vulnerabilities-attacks-final-part/) explains some of these vulnerabilities in more detail.
 
 > [!IMPORTANT]
-> Starting November 1, 2024, the TLS 1.2 requirement will be enforced.
+> Starting March 1, 2025, the TLS 1.2 requirement will be enforced.
 >
 >
 
@@ -29,14 +29,14 @@ TLS versions 1.0 and 1.1 also don't support the modern encryption methods and ci
 As a part of this effort, you can expect the following changes to Azure Cache for Redis:
 
 - _Phase 1_: Azure Cache for Redis stops offering TLS 1.0/1.1 as an option for _MinimumTLSVersion_ setting for new cache creates. Existing cache instances won't be updated at this point. You can't set the _MinimumTLSVersion_ to 1.0 or 1.1 for your existing cache.
-- _Phase 2_: Azure Cache for Redis stops supporting TLS 1.1 and TLS 1.0 starting November 1, 2024. After this change, your application must use TLS 1.2 or later to communicate with your cache. The Azure Cache for Redis service remains available while we update the _MinimumTLSVerion_ for all caches to 1.2.
+- _Phase 2_: Azure Cache for Redis stops supporting TLS 1.1 and TLS 1.0 starting March 1, 2025. After this change, your application must use TLS 1.2 or later to communicate with your cache. The Azure Cache for Redis service remains available while we update the _MinimumTLSVerion_ for all caches to 1.2.
 
 | Date             | Description                                                                                                                                                                                                                                                                    |
 | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | September 2023   | TLS 1.0/1.1 retirement announcement                                                                                                                                                                                                                                            |
 | March 1, 2024    | Beginning March 1, 2024, you can't create new caches with the Minimum TLS version set to 1.0 or 1.1 and you can't set the _MinimumTLSVersion_ to 1.0 or 1.1 for your existing cache. The minimum TLS version won't be updated automatically for existing caches at this point. |
 | October 31, 2024 | Ensure that all your applications are connecting to Azure Cache for Redis using TLS 1.2 and Minimum TLS version on your cache settings is set to 1.2.                                                                                                                          |
-| Starting November 1, 2024 | Minimum TLS version for all cache instances is updated to 1.2. This means Azure Cache for Redis instances reject connections using TLS 1.0 or 1.1 at this point.                                                                                                               |
+| Starting March 1, 2025 | Minimum TLS version for all cache instances is updated to 1.2. This means Azure Cache for Redis instances reject connections using TLS 1.0 or 1.1 at this point.                                                                                                               |
   
   > [!IMPORTANT]
   > The content in this article does not apply to Azure Cache for Redis Enterprise/Enterprise Flash because the Enterprise tiers only support TLS 1.2.
diff --git a/articles/operator-nexus/TOC.yml b/articles/operator-nexus/TOC.yml
@@ -32,18 +32,27 @@
           href: concepts-network-fabric-read-write-commands.md
         - name: Disable Border Gateway Protocol neighbors
           href: concepts-disable-border-gateway-protocol-neighbors.md
-    - name: Isolation Domains
-      expanded: false
-      items:
-        - name: Isolation Domains overview
-          href: concepts-isolation-domain.md
-        - name: Isolation Domain configuration
-          href: reference-isolation-domain-configuration.md
-        - name: Technical requirements for Isolation Domains
-          href: reference-isolation-domain-technical-requirements.md
-    - name: Access Control Lists
-      href: concepts-access-control-lists.md
-    - name: Nexus Kubernetes
+        - name: Network Packet Broker
+          href: concepts-nexus-network-packet-broker.md
+        - name: Route Policy
+          expanded: false
+          items:
+          - name: Route Policy Overview
+            href: concepts-nexus-route-policies-overview.md
+          - name: IP Prefixes Overview
+            href: concepts-nexus-ip-prefix.md
+        - name: Isolation Domains
+          expanded: false
+          items:
+          - name: Isolation Domains overview
+            href: concepts-isolation-domain.md
+          - name: Isolation Domain configuration
+            href: reference-isolation-domain-configuration.md
+          - name: Technical requirements for Isolation Domains
+            href: reference-isolation-domain-technical-requirements.md
+        - name: Access Control Lists
+          href: concepts-access-control-lists.md
+    - name: Nexus Kubernetes Cluster
       expanded: false
       items:
         - name: Overview
@@ -71,17 +80,8 @@
       href: concepts-rack-resiliency.md
     - name: Access and Identity
       href: concepts-security-access-identity.md
-    - name: Route Policy
-      expanded: false
-      items:
-        - name: Route Policy Overview
-          href: concepts-nexus-route-policies-overview.md
-        - name: IP Prefixes Overview
-          href: concepts-nexus-ip-prefix.md
     - name: Availability
       href: concepts-nexus-availability.md
-    - name: Network Packet Broker
-      href: concepts-nexus-network-packet-broker.md
 - name: Quickstarts
   items:
     - name: Before you start workload deployment
diff --git a/articles/service-bus-messaging/service-bus-geo-replication.md b/articles/service-bus-messaging/service-bus-geo-replication.md
@@ -29,19 +29,21 @@ This feature allows promoting any secondary region to primary, at any time. Prom
 > - The below regions are currently supported in the public preview.
 >
 > | Region              | Region               | Region             |
-> |---------------------|----------------------|--------------------|
-> | Australia Central   | Germany West Central | Poland Central     |
-> | Australia East      | Israel Central       | South Africa North |
-> | Australia Southeast | Italy North          | Southeast Asia     |
-> | Canada Central      | Japan East           | South India        |
-> | Canada East         | Japan West           | Spain Central      |
-> | Central India       | Jio India West       | Sweden Central     |
-> | Central US          | Korea Central        | Switzerland North  |
-> | Central US EUAP     | Korea South          | UAE North          |
-> | East Asia           | Mexico Central       | UK South           |
-> | East US 2           | North Central US     | UK West            |
-> | France Central      | North Europe         |                    |
-> | Germany North       | Norway East          |                    |
+> |--------------------|--------------------|------------------|
+> | AustraliaCentral   | GermanyNorth       | NorwayWest       |
+> | AustraliaCentral2  | GermanyWestCentral | PolandCentral    |
+> | AustraliaEast      | IsraelCentral      | SouthAfricaNorth |
+> | AustraliaSoutheast | ItalyNorth         | SouthAfricaWest  |
+> | BrazilSoutheast    | JapanEast          | SoutheastAsia    |
+> | CanadaCentral      | JapanWest          | SouthIndia       |
+> | CanadaEast         | JioIndiaCentral    | SpainCentral     |
+> | CentralIndia       | JioIndiaWest       | SwedenCentral    |
+> | CentralUS          | KoreaCentral       | SwitzerlandNorth |
+> | CentralUSEUAP      | KoreaSouth         | SwitzerlandWest  |
+> | EastAsia           | MexicoCentral      | UAECentral       |
+> | EastUS2            | NorthCentralUS     | UAENorth         |
+> | FranceCentral      | NorthEurope        | UKSouth          |
+> | FranceSouth        | NorwayEast         | UKWest           |
 > 
 > - This feature is currently available on new namespaces. If a namespace had this feature enabled before, it can be disabled (by removing the secondary regions), and re-enabled.
 > - The following features currently aren't supported. We're continuously working on bringing more features to the public preview, and will update this list with the latest status.
