Branded “This Week in Cloud” banner showing a cloud technology logo, floating news cards, network lines, and a weekly cloud news roundup theme on a blue digital background.

This Week in Cloud: Native Vectors, One-Way Migration Roads and Backups That Won’t Budge

Five items land this week that share an unglamorous thread: infrastructure quietly getting harder to break. A database absorbs a capability that used to need its own product, a migration tool draws a route out of AWS storage, and backups stop trusting anyone who wants to delete them early. None of it is flashy. All of it changes how you would architect the next system.

DynamoDB Adds Native Vector Search

Amazon DynamoDB now supports native vector search at general availability, letting you store embeddings alongside operational data and run similarity queries without replicating anything into a separate vector store. The index supports up to 4096 dimensions, Euclidean, cosine, and dot product distance functions, and returns results with single digit millisecond latency at what AWS states is 99%+ recall, scaling to trillions of vectors with no infrastructure to provision or patch.

Why it matters: If your operational data already lives in DynamoDB, this removes a synchronisation pipeline along with its cost and consistency risk. It is not a wholesale replacement for purpose built vector databases doing large scale ANN tuning, so validate recall and latency at your actual index size before retiring anything.

Azure Storage Mover Opens a Lane Out of AWS FSx

Azure Storage Mover now supports agentless migration from AWS FSx for Windows File Server SMB shares directly into Azure Files, currently in public preview. The service handles the cloud to cloud transfer without requiring a migration appliance or ongoing pipeline management on either side.

Why it matters: This lowers the operational cost of leaving AWS file storage, which matters more for procurement leverage than for any migration you have planned this quarter. It says nothing about egress charges, which remain the larger friction point in any AWS to Azure storage move.

Explicit Proxy Reaches GA on Azure Firewall

Azure Firewall’s explicit proxy mode has reached general availability, letting you point applications and browsers at the firewall directly through standard proxy configuration rather than relying on route based traffic interception. It sits alongside the existing transparent, route based model rather than replacing it.

Why it matters: For platform teams supporting legacy or third party apps that cannot honour UDRs cleanly, explicit proxy removes a category of workaround NVA chains. Expect this to simplify branch and hybrid topologies where transparent redirection has been unreliable.

Azure Virtual Network Routing Appliance Goes GA

Azure’s Virtual Network routing appliance is now generally available, delivering private connectivity across virtual networks using dedicated hardware rather than VM based network virtual appliances. Microsoft is pitching it on lower latency and higher throughput than the VM based equivalents it is meant to replace.

Why it matters: If your hub and spoke design currently leans on NVA VMs for cross VNet routing, this removes a class of instance you have to size, patch, and pay for continuously. Worth a look before your next NVA refresh cycle.

Azure SQL Backups Get Automatic Immutability

Azure SQL Database and Azure SQL Managed Instance now apply automatic immutability to the most recent seven days of backups. The protection is enabled by default across all databases regardless of the point in time retention configuration already in place.

Why it matters: This is default on ransomware and insider threat mitigation with no configuration required, which is unusual and welcome. Check how it interacts with any existing backup automation or retention tooling that assumed those backups were mutable, since that assumption no longer holds.

Taken together, these are not the announcements that get keynote time, but they are the ones platform teams actually live with. Hyperscalers keep pulling adjacent capability layers, vector search, cross cloud migration tooling, hardware routing, into core primitives, which squeezes the case for standalone products that only do one of those things well. The backup immutability default is a quiet admission that opt in security has failed often enough to warrant opt out instead. Expect more defaults to move in that direction before the year is out.