Why AutoSave is Disabled for SharePoint Server Documents
Question details
Users find that the AutoSave feature in Microsoft 365 Apps is disabled when working on files stored on an on-premises SharePoint Server.

- Product
- Microsoft 365 Apps
- Device & OS
- not provided
- Scenario
- Attempting to use the AutoSave feature to automatically sync document changes while working on files hosted on a local SharePoint Server.
- Observed behavior
- The AutoSave toggle is disabled or grayed out in the Office application, and automatic syncing does not occur, even if the feature is turned on in the global Office settings.
Verify whether your organization uses an on-premises SharePoint Server or cloud-based SharePoint Online, as the AutoSave feature relies exclusively on Microsoft's cloud infrastructure.
Move Documents to Supported Cloud Storage
To utilize Microsoft 365's AutoSave feature, you must migrate and store your files in a supported cloud environment such as SharePoint Online or OneDrive.
AutoSave is deeply integrated with Microsoft's cloud synchronization technology. It is fully supported for files stored on OneDrive, OneDrive for Business, and SharePoint Online, but intentionally restricted for on-premises servers.
Launch the Microsoft Word, Excel, or PowerPoint document currently stored on your on-premises SharePoint Server.
Click on 'File' in the top-left corner of the application ribbon, then select 'Save As' from the left-hand menu.
Choose 'OneDrive - [Your Company]' or a 'Sites - [Your Company]' SharePoint Online location as your new save destination.
Click 'Save'. Once the file is successfully uploaded to the cloud location, the AutoSave toggle in the top-left corner of your application will automatically switch to the 'On' position.

Utilize Manual Saving and SharePoint Versioning
If organizational policies require keeping documents on an on-premises SharePoint Server, you must rely on manual saving combined with SharePoint's check-in/check-out version history.
Implement a Third-Party Auto-Backup Utility
For users who require automated backups while working on on-premises servers, IT-approved third-party software can automatically save local backup copies.
Experience Seamless Document Management with WPS Office
Avoid frustrating saving limitations and expensive subscriptions. WPS Office provides a complete suite with reliable local auto-backup features and extensive format compatibility, serving as the perfect free alternative to Microsoft Office.
- 1. Download the installer: Visit the official WPS website to download the free WPS Office suite for your preferred operating system.
- 2. Install and launch: Run the quick installation file and open WPS Office in seconds thanks to its highly optimized, lightweight design.
- 3. Open your files: Drag and drop your existing Microsoft Office documents into WPS Office to continue working seamlessly without any formatting issues.

Frequently Asked Questions
Why is the AutoSave button grayed out in Word or Excel?
The AutoSave button is disabled if your file is saved locally, on a standard network drive, or on an on-premises SharePoint Server. It only activates for files stored in Microsoft cloud environments like OneDrive, OneDrive for Business, or SharePoint Online.
Can I force AutoSave to work on an on-premises SharePoint Server?
No. AutoSave relies on specific synchronization protocols built into Microsoft's modern cloud services. On-premises servers lack this specific integration, so traditional manual saving is strictly required.
Will I lose my work if AutoSave is disabled on SharePoint Server?
Not necessarily, provided you manually save your document frequently using Ctrl+S or the Save icon. Additionally, your SharePoint Server likely has versioning enabled by your administrator, which keeps a history of your manual check-ins and saves.
How do I know if my SharePoint is on-premises or online?
You can usually tell by the web address. SharePoint Online URLs typically contain 'sharepoint.com' (e.g., yourcompany.sharepoint.com). If the URL is just an internal server name (e.g., http://intranet), you are likely using an on-premises SharePoint Server.




