Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

.openpublishing.redirection.json

@@ -6559,6 +6559,11 @@
       "source_path": "articles/dns/dns-sdk.md",
       "redirect_url": "https://learn.microsoft.com/dotnet/api/overview/azure/resourcemanager.dns-readme",
       "redirect_document_id": false
+    },
+    { 
+      "source_path": "articles/oracle/oracle-db/exadata-vm-clusters.md",
+      "redirect_url": "/azure/oracle/oracle-db/database-overview",
+      "redirect_document_id": false
     }
 
   ]

articles/load-balancer/load-balancer-health-event-logs.md

@@ -43,7 +43,9 @@ Each event log is published with a timestamp that indicates the time that Azure
 | **GA** | *NoHealthyBackends* | Critical | This event is published per Load Balancer frontend IP, when an associated backend pool has no backend instances responding to the configured health probes. As a result, the load balancer has no healthy backends to distribute traffic to. | On-demand | 60 minutes | Frontend IP address, Pairwise list of protocol and frontend ports associated with affected load balancing rules |
 | **GA** | *HighSnatPortUsage* | Warning | This event is published on a per backend instance-level, when a backend instance utilizes more than 75% of its allocated ports from a single frontend IP. | On-demand | 5 minutes | Backend IP address, Frontend IP address |
 | **GA** | *SnatPortExhaustion* | Critical | This event is published on a per backend instance-level. Publication occurs when a backend instance exhausts all allocated ports and fails any further outbound connections. This event continues until ports are released or more ports are allocated. | On-demand | 5 minutes | Backend IP address, Frontend IP address |
-| **Public Preview** | *NetworkPlatformThrottlingActive* | Critical | This event is published per Load Balancer frontend IP, when the platform bandwidth and/or throughput limits have been reached due to traffic destined to this frontend IP. | On-demand | 60 minutes | Frontend IP address |
+| **GA** | *ApproachingMaxRulesPerNicLimit* | Warning | This event is published per affected Load Balancer frontend IP, when one or more associated backend instances has more than 300 load balancing and inbound NAT rules configured in total. | 24 hours | 24 hours | Frontend IP address |
+| **GA** | *GatewayLoadBalancerNoHealthyBackends* | Critical | This event is published per affected Load Balancer frontend IP, when there is a chained Gateway Load Balancer that is unreachable due to having no backend instances responding to its health probes. | On-demand | 60 minutes | Frontend IP address |
+| **GA** | *NetworkPlatformThrottlingActive* | Critical | This event is published per Load Balancer frontend IP, when the platform bandwidth and/or throughput limits have been reached due to traffic destined to this frontend IP. | On-demand | 60 minutes | Frontend IP address |
 
 For more information on the properties published with each health event log, refer to the Azure Log Analytics reference documentation for the log table [*ALBHealthEvent*](/azure/azure-monitor/reference/tables/albhealthevent).
 

articles/oracle/oracle-db/exadata-vm-clusters.md

@@ -27,8 +27,6 @@ items:
       href: oracle-db/manage-oracle-transparent-data-encryption-azure-key-vault.md
     - name: Oracle Exadata Database on Dedicated Infrastructure Logs on Azure for Enhanced Observability
       href: oracle-db/oracle-exadata-database-dedicated-infrastructure-logs.md
-    - name: Onboard Oracle Exadata VM Clusters to Microsoft Defender for Cloud using Azure Arc 
-      href: oracle-db/exadata-vm-clusters.md
   - name: Onboarding
     items:
     - name: Onboard Oracle Database@Azure

articles/oracle/oracle-db/media/environment-settings.png

@@ -108,7 +108,7 @@ The following features are currently in gated public preview. After working with
 |9| Spoke Virtual Network address space updates not picked up by Virtual WAN | Multiple concurrent updates on spoke Virtual Network address spaces aren't properly synced with the Virtual hub. | November 2024 | Ensure address space updates in a single Virtual Network are done serially. Wait until the first address update is properly reflected in the Virtual hub's effective routes before updating the address space of the spoke Virtual Network again. If this issue has already occurred, make sure to update the address space of the affected Virtual Network with a nonimpacting address space (wait about 20 minutes before attempting again). Once this is reflected in the Virtual Network AND in the Virtual hub, update the Virtual Network address space to the preferred Virtual Network address space.|
 |10 |Unable to update route tables and routing configuration (propagated route table and label)  for on-premises (VPN, ExpressRoute, NVA) connections. | When a Virtual WAN hub and its gateway(s) are in different Azure resource groups, updating routing configuration results in a "resource not found" error. | March 2025| This issue is caused by a code defect in Azure portal. Use Terraform, PowerShell, CLI or REST API to manage your Virtual WAN deployment.|
 |11| Hub won't advertise routes to VPN sites | When a customer uses Route-Maps for the first time it triggers an upgrade. After the upgrade is complete, If VPN sites aren't advertising routes to the hub, the hub won't advertise routes to the VPN sites. | December 2024 | If the VPN sites start adverting any routes to the hub, the hub will start adverting routes again.|
-|12| Virtual Hub router does not select local routes over remote when Hub Routing Preference is set to ExpressRoute or VPN. | When the same route is advertised from on-premises to Azure to multiple Virtual WAN hubs and [hub routing preference](about-virtual-hub-routing-preference.md) is set to ExpressRoute or VPN, the local Virtual WAN hub may experience a race condition where a route learnt from a remote hub may be selected over a route learnt from a local on-premises site. This happens in scenarios where the local route's AS-PATH length is 2 or more AS-PATH lengths **longer** than that of the remote hub. For example, the race condition is triggered when the local VPN route has AS-PATH length 4 and the remote VPN route has AS-PATH length 2.| | Ensure the difference in AS-PATH length between local and remote routes is at most 1. In the example provided in the description of this known issue, you can increase the AS-PATH length of the remote VPN route, or decrease the length of the local VPN route by modifying on-premises AS-PATH pre-pending or applying [route maps](route-maps-about.md).   |
+|12| Virtual Hub router does not select local routes over remote. | When the same route is advertised from on-premises to Azure to multiple Virtual WAN hubs, the local Virtual WAN hub may experience a race condition where a route learnt from a remote hub may be selected over a route learnt from a local on-premises site. This happens in scenarios where the local route's AS-PATH length is 2 or more AS-PATH lengths **longer** than that of the remote hub. For example, the race condition is triggered when the local VPN route has AS-PATH length 4 and the remote VPN route has AS-PATH length 2.| | Ensure the difference in AS-PATH length between local and remote routes is at most 1. In the example provided in the description of this known issue, you can increase the AS-PATH length of the remote VPN route, or decrease the length of the local VPN route by modifying on-premises AS-PATH pre-pending or applying [route maps](route-maps-about.md).   |
 
 ## Next steps