Word 365 File Authorization Error Causing Loss of Changes

Alessandra Micco 0 Punti di reputazione
2026-06-18T21:27:29.9733333+00:00

Hi,

I am experiencing a persistent issue with Microsoft Word 365 on my Mac.

When I work on a document and save it, Word appears to save successfully. However, when I attempt to close the document, Word prompts me to save again. After clicking Save, I receive the following error message:

"Word cannot complete the save due to a file authorization error."

When I reopen the document, I find that my most recent changes have not been saved and the document has reverted to an older version, resulting in loss of work.

The issue affects all documents, including newly created ones. Initially, even "Save As" failed. My Desktop and Documents folders are synchronized with iCloud, and AutoSave is disabled. I have noticed that saving files to a different location sometimes works, which makes me suspect a permissions or synchronization issue rather than document corruption.

I have already tried the following troubleshooting steps:

  • Signing out of and back into Microsoft 365.
  • Checking macOS file permissions.
  • Disabling AutoSave.
  • Moving files outside synchronized folders.
  • Checking for conflicts between iCloud and OneDrive.
  • Resetting Word preferences and deleting temporary files.

Despite these steps, the issue persists. I am using Microsoft Word 365 on macOS Tahoe.

Could you please advise on additional troubleshooting steps or let me know if this is a known issue?

Thank you for your assistance.

Microsoft 365 e Office | Word | Per il lavoro | MacOS
0 commenti Nessun commento

1 risposta

Ordina per: Più utili
  1. Anonimo
    2026-06-18T22:54:28.5233333+00:00

    I noticed that your post is in English, while your preferred language appears to be Italian. If you would like to continue in a different language, please let me know. 

    Hi Alessandra, 

    Thank you for sharing the detailed information and for confirming the troubleshooting steps you have already tried.  Based on your description, this behavior may be related to how Word is being allowed to access and write to the folder location on macOS, especially because the issue affects multiple documents and saving to another location sometimes works. Please try the additional checks below to further isolate whether the issue is caused by folder permissions, iCloud or OneDrive synchronization, or the current macOS user profile.  Step 1: Grant Word the required macOS permissions 

    • Go to Apple menu > System Settings > Privacy & Security. 
    • Select Full Disk Access, add Microsoft Word, and turn access on.  
    • After that, go back to Privacy & Security > Files and Folders, expand Microsoft Word if it appears, and make sure access is allowed for Desktop, Documents, and any cloud storage folders listed there.  
    • Once this is done, fully quit Word, reopen it, and test saving a new document again. 

    Step 2: Test saving in a local folder outside cloud sync   

    • Please create a new folder directly under your user profile. Make sure this folder is not inside Desktop, Documents, iCloud Drive, OneDrive, or any other synchronized folder.  
    • Then create a brand new Word document and save it to that folder.  
    • If the document saves and closes normally there, the issue is likely connected to the original synchronized folder location or its permissions. 

    Step 3: Test Word in a new macOS user profile  If the issue continues, please test Word from a new temporary macOS user profile.  

    • Go to Apple menu > System Settings > Users & Groups. 
    • Select Add user, sign in to that profile, open Word, sign in with your Microsoft 365 account, and test saving a new document to a local folder.  
    • This helps determine whether the problem is related to the current macOS profile or Word configuration. 

    Step 4: Create a ticket to Microsoft Support  If the same issue still occurs after taking these steps, the next best step is to have your Microsoft 365 administrator open a support ticket from the Microsoft 365 admin center. A technical support engineer can then initiate a remote session, review backend settings, and run diagnostics. If needed, they can escalate the case to specialized engineering teams who are well-equipped to perform advanced troubleshooting and provide targeted solutions.  

    As moderators, our primary goal is to provide helpful guidance and support through general troubleshooting steps. While we don’t have access to internal systems or administrative tools required to resolve account-specific or backend issues, we truly appreciate your understanding of these limitations. We genuinely hope the information we share helps point you in the right direction, and we're always here to assist as much as we can within our scope.  

    For guidance on how to request support in the admin center, please refer to: Get support - Microsoft 365 admin.      

    In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support  

     

    I hope this information is helpful. Please follow the steps above and let me know if it works for you. If not, we can continue working together to resolve the issue.  

    Thank you for your patience and understanding. If you have any questions or need additional assistance, please don’t hesitate to reach out so I can continue to support you. If you found the response useful, please consider marking it as accepted, as this may help other community members who are looking for similar guidance.  

    I look forward to continuing the conversation.  


    If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.     

    La risposta è stata utile?


Risposta

Le risposte possono essere contrassegnate come "Accettata" dall'autore della domanda e "Consigliata" dai moderatori, in modo da consentire agli utenti di sapere che la risposta ha risolto il problema dell'autore.