Share via

When I try to upload pst file, I receive error 500 when try to generate SAS URL.

Anonymous
2025-02-20T17:04:10+00:00

Hello,

When I try to upload a pst file to import it in Exchange Online, I receive Error 500 when I create import task and try to get SAS URL.

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2025-04-30T14:16:20+00:00

    Hello,

    Any news on this topic ? I have the same issue for one of our customer.

    Regards,

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-02-20T20:51:46+00:00

    Dear Lirex Lirex,

    Good day! Thank you for posting to Microsoft Community.

    Based on the issue you have shared, the issue with importing PST file in Microsoft purview seems there is a service degradation posted in Microsoft service health dashboard with the tracking number MP1011050. You can refer to the incident detail below:

    Title: Some admins receive a 500 error when attempting to generate Shared Access Signature (SAS) URLs during PST imports

    User impact: Admins receive a 500 error when attempting to generate SAS URLs during Personal Storage Table (PST) imports.

    More info: Admins receive the following error message: "The remote server returned an error: (500) Internal Server Error."

    Current status: We've further identified that a security code update inadvertently introduced a regression that's causing a permissions issue with a section of storage infrastructure, resulting in a 500 error when users attempt to generate SAS URLs during PST imports. We're developing and testing a fix to repair the permissions issue, and once the fix has been validated, we'll start a deployment to affected users.

    Scope of impact: Your organization is affected by this event, and some admins can't generate SAS URLs during PST imports.

    Root cause: A security code update inadvertently introduced a regression that's causing a permissions issue with a section of storage infrastructure, resulting in a 500 error when users attempt to generate SAS URLs during PST imports.

    Next update by: Friday, February 21, 2025, at 6:30 AM UTC

    For affected customers to easily identify the information here, you may subscribe to this thread for updated information. I will post back here once the issue is resolved. Thanks in advance for your understanding! Your patience and cooperation will be highly appreciated.

    Thank you for your patience and understanding. We apologize for any disruption this service degradation may cause to your operations.

    Have a good day!

    Sincerely,

    Libeamlak | Microsoft Community Moderator

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-06-04T06:32:36+00:00

    Hi,

    the support of my country distributor made me add the user account nominatively in the roles mandatory to do mail import/export, even if the user was a global admin and the global admin group has already the right roles, I was sceptical but it worked.

    I don't know if they've done anything else from their side (I think not), but at least give it a try and give us a feedback.

    Regards,

    Geoffroy

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-06-03T15:29:02+00:00

    Hello,

    Same issue with all my customers tenants in France.

    I'm working on many migration from Exchange On Prem to 365 Online and all is blocked.

    It's an aleatory issue but recurring since 2019.

    We need a real solution !

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-05-13T18:41:13+00:00

    Any update on this, its now May and i am still seeing the same issue

    Was this answer helpful?

    0 comments No comments