[Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP
What the source says
Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens security with Entra ID authentication, MFA, and Conditional Access. Accelerates onboarding and enables secure external collaboration with partners and vendors via Entra External Identities (B2B). Key capabilities Single Sign-On and Multi-Factor Authentication using existing corporate credentials. Conditional Access policies based on user location, device compliance, sign-in risk, and other signals. Unified identity lifecycle — SFTP access is automatically updated or revoked through your existing identity governance processes. Native Azure RBAC, ABAC, and ACL integration — SFTP honors the same authorization model as the REST API, Azure CLI, and other data-plane access methods. New in GA ABAC + Storage Blob Data Owner: resolved an inconsistency that could cause timeouts when combining ABAC conditions with the Storage Blob Data Owner role. ABAC sub-operations: added support for sub-operations, enabling finer-grained conditional access.
Who is affected: The audience described by the Microsoft update is represented by: [Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens secu
Why it matters: The change matters because the official source describes: [Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens secu
Urgency: Monitor
Next action: Review affected accounts with the customer using the official announcement.
Commercial opportunities
Use the verified change to open a scoped customer conversation.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The effective date is unknown and must be confirmed before scheduling action.
Reading for it_manager_dsi
Who is affected: The audience described by the Microsoft update is represented by: [Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens secu
Why it matters: The change matters because the official source describes: [Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens secu
Urgency: Monitor
Next action: Assess technical dependencies and ownership against the official update.
Commercial opportunities
Offer a scoped technical-readiness assessment if the customer confirms impact.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The effective date is unknown and must be confirmed before scheduling action.
Reading for partner_channel
Who is affected: The audience described by the Microsoft update is represented by: [Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens secu
Why it matters: The change matters because the official source describes: [Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens secu
Urgency: Monitor
Next action: Prepare a source-backed customer conversation and confirm the affected estate.
Commercial opportunities
Qualify a partner-led assessment only after customer scope is confirmed.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The effective date is unknown and must be confirmed before scheduling action.
Reading for sales_manager
Who is affected: The audience described by the Microsoft update is represented by: [Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens secu
Why it matters: The change matters because the official source describes: [Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens secu
Urgency: Monitor
Next action: Review portfolio exposure with account owners using the official source.
Commercial opportunities
Prioritize accounts that confirm affected products or workloads.
Technical actions
Assess whether the documented change intersects the customer's current stack.
Questions to ask the customer
Does this documented change affect a product or workload in scope?
Risks and objections
The official source does not establish facts beyond the quoted material.
Points to confirm
The effective date is unknown and must be confirmed before scheduling action.
Evidence and traceability
Each excerpt is linked to the primary source. Current raw version: 454.
Raw capture : 2026-08-26T14:18:57.653130+00:00 — hash 890882556e30dd51…
Event
[Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens security with Entra ID authentication, MFA, and Conditional Access. Accelerates onboarding and enables secure external collaboration with partners and vendors via Entra External Identities (B2B). Key capabilities Single Sign-On and Multi-Factor Authentication using existing corporate credentials. Conditional Access policies based on user location, device compliance, sign-in risk, and other signals. Unified identity lifecycle — SFTP access is automatically updated or revoked through your existing identity governance processes. Native Azure RBAC, ABAC, and ACL integration — SFTP honors the same authorization model as the REST API, Azure CLI, and other data-plane access methods. New in GA ABAC + Storage Blob Data Owner: resolved an inconsistency that could cause timeouts when combining ABAC conditions with the Storage Blob Data Owner role. ABAC sub-operations: added support for sub-operations, enabling finer-grained conditional access.
[Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens security with Entra ID authentication, MFA, and Conditional Access. Accelerates onboarding and enables secure external collaboration with partners and vendors via Entra External Identities (B2B). Key capabilities Single Sign-On and Multi-Factor Authentication using existing corporate credentials. Conditional Access policies based on user location, device compliance, sign-in risk, and other signals. Unified identity lifecycle — SFTP access is automatically updated or revoked through your existing identity governance processes. Native Azure RBAC, ABAC, and ACL integration — SFTP honors the same authorization model as the REST API, Azure CLI, and other data-plane access methods. New in GA ABAC + Storage Blob Data Owner: resolved an inconsistency that could cause timeouts when combining ABAC conditions with the Storage Blob Data Owner role. ABAC sub-operations: added support for sub-operations, enabling finer-grained conditional access.
[Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens security with Entra ID authentication, MFA, and Conditional Access. Accelerates onboarding and enables secure external collaboration with partners and vendors via Entra External Identities (B2B). Key capabilities Single Sign-On and Multi-Factor Authentication using existing corporate credentials. Conditional Access policies based on user location, device compliance, sign-in risk, and other signals. Unified identity lifecycle — SFTP access is automatically updated or revoked through your existing identity governance processes. Native Azure RBAC, ABAC, and ACL integration — SFTP honors the same authorization model as the REST API, Azure CLI, and other data-plane access methods. New in GA ABAC + St
[Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens security with Entra ID authentication, MFA, and Conditional Access. Accelerates onboarding and enables secure external collaboration with partners and vendors via Entra External Identities (B2B). Key capabilities Single Sign-On and Multi-Factor Authentication using existing corporate credentials. Conditional Access policies based on user location, device compliance, sign-in risk, and other signals. Unified identity lifecycle — SFTP access is automatically updated or revoked through your existing identity governance processes. Native Azure RBAC, ABAC, and ACL integration — SFTP honors the same authorization model as the REST API, Azure CLI, and other data-plane access methods. New in GA ABAC + St
[Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens security with Entra ID authentication, MFA, and Conditional Access. Accelerates onboarding and enables secure external collaboration with partners and vendors via Entra External Identities (B2B). Key capabilities Single Sign-On and Multi-Factor Authentication using existing corporate credentials. Conditional Access policies based on user location, device compliance, sign-in risk, and other signals. Unified identity lifecycle — SFTP access is automatically updated or revoked through your existing identity governance processes. Native Azure RBAC, ABAC, and ACL integration — SFTP honors the same authorization model as the REST API, Azure CLI, and other data-plane access methods. New in GA ABAC + St
[Launched] Generally Available: Microsoft Entra ID-based access for Azure Blob Storage SFTP Microsoft Entra ID-based access for Azure Blob Storage SFTP is now generally available in all regions. You can now use Entra ID identities including guest users via Entra External Identities to securely connect to Azure Blob Storage over SFTP, without provisioning or managing local SFTP users. Why it matters Eliminates the operational overhead of managing local SFTP users and credentials. Strengthens security with Entra ID authentication, MFA, and Conditional Access. Accelerates onboarding and enables secure external collaboration with partners and vendors via Entra External Identities (B2B). Key capabilities Single Sign-On and Multi-Factor Authentication using existing corporate credentials. Conditional Access policies based on user location, device compliance, sign-in risk, and other signals. Unified identity lifecycle — SFTP access is automatically updated or revoked through your existing identity governance processes. Native Azure RBAC, ABAC, and ACL integration — SFTP honors the same authorization model as the REST API, Azure CLI, and other data-plane access methods. New in GA ABAC + St