Generally Available: ExpressRoute - Auto-assigned Public IP for ExpressRoute Gateways

Generally Available: ExpressRoute - Auto-assigned Public IP for ExpressRoute Gateways
All newly deployed ExpressRoute Virtual Network Gateways will use auto-assigned Public IPs. This change simplifies gateway configuration by removing the requirement to explicitly assign a Public IP address.
This model streamlines deployment and improves consistency across gateway types. This feature eliminates the need for customers to manually manage Public IPs for new gateways, helping reduce operation effort and overhead.
Existing gateways are not impacted by this change.

Generally Available: Search Job Enhancements in Log Analytics
A Search Job is an asynchronous query that runs on any data in your Log Analytics workspace, including data from the long-term retention period, making the results available for further queries in a new Analytics table within your workspace.

We’ve recently improved Search Job capabilities with the following updates:

• Intuitive and streamlined UI experience for easier setup.
• Cost estimation preview before running a Search Job.
• Enhanced concurrency, allowing more jobs to run in parallel and removing additional limits.
• Increased result limits, supporting up to 100 million results - coming soon.
• Expanded KQL support and other enhancements are coming soon.

Public Preview: Modernizing Azure Resource Manager Throttling for Sovereign Clouds
Following our 2024 announcement to modernize Azure Resource Manager throttling, we are announcing that Azure Resource Manager will be bringing parity between public and sovereign clouds by the end of 2026. This update will ensure that the same throttling limits and architecture apply across all Azure environments, enhancing consistency and reliability for our customers.
As mentioned in 2024, throttling limits have increased by roughly 30 times for writes, 2.4 times for deletes, and 7.5 times for reads. These represent significant increases compared to previous limits.
The subscription limits apply per subscription, per service principal, and per operation type. There are also global subscription limits that are equivalent to 15 times the individual service principal limits for each operation type. Tenant requests don't include your subscription ID, such as retrieving valid Azure locations.
We will begin the rollout in July 2025, with estimated completion by end of 2026. The migration to the new architecture will be gradual, with a certain percentage of tenants being migrated at a time.
We're dedicated to ensuring your Azure experience is productive and reliable

Generally Available: Azure CNI static block allocation for pod subnet
Kubernetes network solutions are challenging to plan due to rapidly evolving business needs. AKS users often face difficulties balancing simplicity, security, and scalability, while environmental changes further increase management costs.

Many AKS users need a flat network architecture, pods with direct inbound connectivity, and Azure-native solution integrations, but traditional flat networks couldn't scale beyond 65K pods. Until the launch of static block, customers either choose overlay networks to achieve massive scale or sacrifice the benefits of flat networking.
Azure CNI Pod Subnet - Static Block Allocation enables VNET routed IP addresses that can scale to over 1M pods, providing the simplicity and low latency of a flat network. Each node receives pre-allocated CIDR blocks, and all pods on that node obtain IP addresses from these ranges. This approach delivers massive scale, previously only available with overlay networks (up to 1M pods) while maintaining all the benefits of a flat network architecture. It also works seamlessly alongside existing dynamic IP allocation for pod subnet – simply deploy it on new node pools with dedicated subnets.
AKS users can scale up AKS network solutions with minimal effort while maintaining enterprise-grade reliability and security.