🏠 taeyanghub.com ← All updates

Azure Update Digest (2026-07-06)

Period: today · Items: 2 · Source: Azure official updates RSS

Today's Intro

Today brings Azure updates that are immediately relevant to real-world operations. One is that Azure Blob Storage SFTP now generally supports Microsoft Entra ID-based authentication, and the other is that Azure Site Recovery now supports up to 5x churn (500 MB/s) per VM. Neither is a flashy new feature, but both are changes that raise the ceiling for security models and disaster recovery design in actual enterprise environments, making them well worth studying.

Today's learning points

· Microsoft Entra ID-based access for SFTP — a way to control SFTP access through centralized IAM (Identity and Access Management) instead of local accounts
· Azure Blob Storage SFTP — a capability that connects object storage with SFTP workloads to modernize legacy file transfer scenarios
· Azure Site Recovery churn — a key term referring to the rate of changed data generated on the source disk during disaster recovery replication
· High-IOPS workload DR — an important criterion for determining whether write-intensive systems such as databases can be included in DR scope
· Guest users / Entra External Identities — a B2B collaboration-oriented access control model that extends Entra ID-based integrated authentication to external users


Storage & File Transfer

2 items

GA Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP

· Azure Blob Storage SFTP now has Microsoft Entra ID-based access control generally available in all regions.
· Not only Entra ID user accounts, but also guest users from Entra External Identities can connect securely over SFTP.
· This points to a shift away from locally managed accounts toward centralized identity management.
· In the announcement, part of the text is truncated as “without pro...,” so some detailed wording is difficult to verify, but the key point is that SFTP authentication/access can now be integrated with Entra ID.

What it is: This feature allows you to use Entra ID identity-based authentication and access management when accessing Azure Blob Storage SFTP endpoints, rather than relying on separate local usernames and passwords. What is especially notable is that external partners and guest users can also be managed within the same identity system.

Why it matters: Many organizations still rely on SFTP for file collection and distribution, but fragmented account management makes security and operations more complex. Understanding this feature helps explain how Azure connects a legacy transfer protocol (SFTP) with modern IAM (Entra ID), and where Azure is heading in modernizing enterprise file transfer.

Try it: In the Azure portal, review the SFTP-related settings for Blob Storage and the identity-based access configuration, then design a test account scenario for Entra ID users or guest users.
Source: https://azure.microsoft.com/updates?id=567085


Business Continuity & Disaster Recovery

1 items

GA Generally Available: Support 5x churn in Azure Site Recovery

· Azure Site Recovery now supports up to 5x churn, or 500 MB/s per VM.
· This enhancement makes it possible to protect high-IOPS workloads with Azure Site Recovery more confidently.
· The announcement specifically mentions scenarios such as demanding applications and databases.
· It is an update that relaxes the previous limitation in disaster recovery design that “this workload generates too much change data to replicate effectively.”

What it is: Azure Site Recovery is a service that replicates VM workloads from on-premises or other environments to Azure to build DR (Disaster Recovery). With this announcement, support for a higher changed data rate (churn) per second means that more write-intensive workloads can now be included within the protection scope.

Why it matters: When designing DR, the harder bottleneck is often not CPU or memory, but changed data rate and replication throughput limits. For engineers, this update expands the practical decision boundary for “Which systems can ASR realistically cover?”

Try it: Think of your key production VMs or database server candidates, and reassess Azure Site Recovery applicability based on the current workload’s disk change rate and IOPS characteristics.
Source: https://azure.microsoft.com/updates?id=566966


Retirements at a glance

There are no separate service retirement items in today’s list.

Today's learning mission

  1. Storage security: Map out how Microsoft Entra ID-based access control for Azure Blob Storage SFTP differs from the existing local account model in terms of authentication flow
  2. External collaboration design: Assume an SFTP file exchange scenario using Microsoft Entra External Identities guest users, and design the permission model
  3. File transfer modernization: Based on your organization’s current SFTP use cases, compare the operational benefits and remaining constraints of moving to Azure Blob Storage SFTP
  4. DR architecture: Analyze what kinds of workloads are meaningfully affected by Azure Site Recovery’s churn concept and 500 MB/s per-VM support, using databases and high-IOPS servers as reference points
  5. Operational review: Review the list of protected VMs and classify whether high-change-rate workloads that were previously difficult to protect with Azure Site Recovery should now be reconsidered in light of this update