Azure updates: File Sync onboarding and networking changes

Key insights

• Arc-enabled Windows file servers can join Azure File Sync groups through a simpler onboarding flow; the feature is in preview.
• Static Web Apps support for .NET 8 and .NET 9 is ending; the update points users toward a newer version such as .NET 10.
• Azure Functions support for .NET 11 is generally available in isolated worker mode.
• Azure Route Server dual-stack support and AKS Distributed Accelerator for Cloud Storage are in preview.
• Azure Front Door edge actions are generally available; gRPC and WAF rate-limit grouping are in preview.

Azure’s latest update covers simpler Azure File Sync onboarding for Arc-enabled Windows file servers, .NET support changes, and new networking and storage capabilities. The changes matter to Azure administrators and teams managing hybrid file servers, cloud applications, AKS AI workloads, or Azure Front Door deployments. John Savill’s [MVP] demonstrates and summarizes these updates in a YouTube video.

What's new

The update spans compute, storage-related infrastructure, and networking, with a mix of generally available features and previews. For hybrid file services, onboarding Arc-enabled Windows file servers to Azure File Sync is now described as easier, although the feature is in preview. Azure Functions also adds .NET 11 support in isolated worker mode, which is generally available.

There is also a runtime change for Static Web Apps: .NET 8 and .NET 9 support is ending, and the update recommends moving to a newer version, such as .NET 10. On AKS, the preview of Distributed Accelerator for Cloud Storage (DACS) uses hosts’ local NVMe storage to cache frequently used blob data. The aim is to reduce storage latency and accelerate operations such as model training.

Networking updates include dual-stack support for Azure Route Server in preview, allowing it to work with IPv4 and IPv6. Azure Front Door edge actions are generally available, while gRPC support and Web Application Firewall rate-limit grouping are in preview. These features address different needs: running JavaScript at the edge, routing gRPC traffic, and applying rate limits across groups of requests rather than judging each IP address alone.

Who it is for and what you need

The File Sync onboarding change is relevant to organizations with Windows file servers connected to Azure Arc that want to add them to an Azure File Sync group. The described setup synchronizes through a cloud endpoint in Azure Files. The update does not state specific licensing, region, prerequisites, or a rollout schedule beyond identifying this onboarding capability as a preview.

Application teams should check their Static Web Apps workloads for dependencies on .NET 8 or .NET 9 and plan a move to a newer supported version. Azure Functions teams can consider .NET 11 when using the isolated worker model; the update does not describe support for other worker modes. AKS operators may be interested in DACS if their AI workloads use blob data and their nodes have local NVMe storage, but the item is marked preview.

Network teams managing Azure Route Server can assess the dual-stack preview if their network designs require IPv4 and IPv6 routing. Front Door administrators and application owners may want to evaluate edge actions, gRPC, or grouped WAF rate limits according to their traffic patterns. The update does not provide plan, license, region, or configuration details for these capabilities.

How it works

Azure File Sync uses a cloud endpoint in Azure Files to synchronize data with a file server. The announced improvement makes it easier to add an Arc-enabled Windows file server to a sync group; the update does not give a portal menu path or a step-by-step setup procedure. For teams evaluating it, the central task is onboarding the server into the relevant File Sync group.

DACS keeps recently and frequently used blob data on local NVMe storage hosted by AKS nodes. This local cache is intended to reduce the latency of repeated access to that data. The update does not specify configuration steps, supported node types, or cache controls.

Azure Route Server acts as a BGP proxy so network virtual appliances can exchange network reachability information with virtual networks without administrators manually adding routes. Dual-stack support extends that capability to IPv4 and IPv6. In Azure Front Door, edge actions run JavaScript functions as requests arrive or responses leave, enabling actions such as blocking or routing traffic; the update says each action runs in an isolated microVM.

Front Door gRPC support adds a way to route gRPC traffic, and the preview includes health probes so traffic can be sent only to healthy endpoints. WAF rate-limit grouping changes the basis for evaluating request volume: instead of relying only on individual IP addresses, a selected grouping can include factors such as a client fingerprint, routing prefix, country, or region.

Limitations and open questions

Several announcements are previews, not general availability: Arc-enabled File Sync onboarding, AKS DACS, dual-stack Azure Route Server, Front Door gRPC, and WAF rate-limit grouping. The update does not provide deployment instructions, support matrices, regional availability, or preview limitations for them. Teams should verify those details in current Azure documentation before making production plans.

The .NET support change is also presented briefly: the update says .NET 8 and .NET 9 support for Static Web Apps is ending and suggests .NET 10, but it does not explain migration steps or identify affected app configurations. For Azure Functions, .NET 11 support is explicitly limited to isolated worker mode. The video does not provide a date or process for moving existing applications.

Azure Front Door edge actions are the one Front Door feature in this roundup identified as generally available. The publisher’s summary does not include pricing or limits, nor does it give configuration paths for any of the services. Treat the summary as a change checklist, then confirm technical and rollout specifics in the service documentation.

Sources

• John Savill’s Azure Weekly Update

Frequently asked questions

Is Azure File Sync onboarding for Arc-enabled servers generally available?

No. The update identifies the simpler onboarding for Arc-enabled Windows file servers as a preview. It does not state regional availability or prerequisites.

Does Azure Functions support .NET 11?

The update says .NET 11 support is generally available for Azure Functions in isolated worker mode. It does not claim support for other worker modes.

What changes for .NET 8 and .NET 9 in Static Web Apps?

The update says support is ending and recommends moving to a newer version, giving .NET 10 as an example. It does not provide migration instructions or further timing details.

Which Azure Front Door updates are in preview?

gRPC support and WAF rate-limit grouping are in preview. Edge actions are identified as generally available.