Users may have been unable to fetch Shared Access Signatures (SAS) keys during mailbox file import in Microsoft Purview

Title: Users may have been unable to fetch Shared Access Signatures (SAS) keys during mailbox file import in Microsoft Purview User impact: Users may have been unable to fetch SAS keys during mailbox file import in Microsoft Purview Data Lifecycle Management. More info: This issue specifically affected tenants requiring new storage-account provisioning for Personal Storage Table (PST) imports, and tenants that already have storage accounts provisioned were unaffected. Users impacted by this event encountered the following error during SAS key generation: "(500) Internal Server Error." Final status: We've confirmed that impact is remediated following an extended period of monitoring service-side telemetry. Scope of impact: This issue may have affected any user for tenants provisioning new storage accounts in the following regions: Australia East, Brazil South, Canada Central, Central India, East US 2, France Central, Germany West Central, Indonesia Central, Israel Central, Italy North, Japan East, Korea Central, New Zealand North, North Europe, Norway East, Poland Central, South Africa North, Southeast Asia, Spain Central, Sweden Central, Switzerland North, Taiwan North, UAE North, and UK West. Start time: Wednesday, September 23, 2026, at 10:12 AM UTC End time: Wednesday, September 30, 2026, at 12:30 PM UTC Root cause: Data Lifecyle Management calls to create new accounts in Azure during PST import SAS key generations were failing for tenants requiring new storage accounts in certain regions. Next steps: We're reviewing performance data and trends on the affected systems to help prevent similar impact from happening again. This is the final update for the event.

Title: Some users may be unable to fetch Shared Access Signatures (SAS) keys during mailbox file import in Microsoft Purview User impact: Users may be unable to fetch SAS keys during mailbox file import in Microsoft Purview Data Lifecycle Management. More info: This issue specifically affects tenants requiring new storage-account provisioning for Personal Storage Table (PST) imports, and tenants that already have storage accounts provisioned are unaffected. Users impacted by this event encounter the following error during SAS key generation: "(500) Internal Server Error." Current status: We've completed a fix to correct the import of SAS key generation. Users may need to complete a fresh login and retry twice if the first attempt fails. We're continuing to monitor our service-side telemetry to ensure the stability and effectiveness of the fix. Scope of impact: This issue may affect any user for tenants provisioning new storage accounts in the following regions: Australia East, Brazil South, Canada Central, Central India, East US 2, France Central, Germany West Central, Indonesia Central, Israel Central, Italy North, Japan East, Korea Central, New Zealand North, North Europe, Norway East, Poland Central, South Africa North, Southeast Asia, Spain Central, Sweden Central, Switzerland North, Taiwan North, UAE North, and UK West. Root cause: Data Lifecyle Management calls to create new accounts in Azure during PST import SAS key generations are failing for tenants requiring new storage accounts in certain regions. Next update by: Thursday, October 1, 2026, at 10:30 AM UTC

Title: Some users may be unable to fetch Shared Access Signatures (SAS) keys during mailbox file import in Microsoft Purview User impact: Users may be unable to fetch SAS keys during mailbox file import in Microsoft Purview Data Lifecycle Management. More info: This issue specifically affects tenants requiring new storage-account provisioning for Personal Storage Table (PST) imports, and tenants that already have storage accounts provisioned are unaffected. Users impacted by this event encounter the following error during SAS key generation: "(500) Internal Server Error." Current status: We've identified that the Data Lifecyle Management calls to create new accounts in Azure during PST import SAS key generations are failing for tenants requiring new storage accounts in certain regions. We're in the process of developing and testing a solution to unblock the calls. Scope of impact: This issue may affect any user for tenants provisioning new storage accounts in the following regions: Australia East, Brazil South, Canada Central, Central India, East US 2, France Central, Germany West Central, Indonesia Central, Israel Central, Italy North, Japan East, Korea Central, New Zealand North, North Europe, Norway East, Poland Central, South Africa North, Southeast Asia, Spain Central, Sweden Central, Switzerland North, Taiwan North, UAE North, and UK West. Root cause: Data Lifecyle Management calls to create new accounts in Azure during PST import SAS key generations are failing for tenants requiring new storage accounts in certain regions. Next update by: Thursday, October 1, 2026, at 10:30 AM UTC