Multiple account issues - Office documents in Teams/SharePoint

Question

Multiple account issues - Office documents in Teams/SharePoint

Heather 40

I am facing multiple issues in Microsoft office products from my Teams for education account.

1 - Unable to turn on auto-save word documents within the application. It does work within the browser for documents stored in Teams/Sharepoint. However, it works for word documents outside of Teams/Sharepoint.

2 - Unable to checkout and edit documents within a certain folder in Teams/Sharepoint although I am the owner of the Team. As an owner, I have permissions to edit documents in all folders within that team.

What steps can I take to troubleshoot? It seems like an account issue and not a local issue.

0 comments

1 answer

Your answer

Answer 1

Hi Heather,

Sorry you're going through this. I appreciate you sharing the details of what happened.

As this is a user-to-user community forum, I do not have the ability to directly access or modify your account or service. However, I can provide guidance, recommend next steps, share applicable resources, and direct you to the appropriate support channels so the issue can be investigated further.

Based on what you described, this does not appear to be a purely local Word application issue. Since AutoSave works in the browser and also works for documents outside of Teams/SharePoint, the issue is more likely related to the SharePoint document library, folder-level permissions, checkout settings, file lock status, or the way the Office desktop app is authenticating to your education account.

A key point is that files in Microsoft Teams are stored in SharePoint behind the scenes. Even if you are the owner of the Team, a specific folder or file can still have different permissions if inheritance was broken, if checkout is required, or if a policy is applied at the library, folder, or file level.

Here are some steps you can try:

1/ Open the affected folder directly in SharePoint

Go to the affected Team and channel.
Open the Files tab.
Select Open in SharePoint.
Test the file from SharePoint directly rather than from the Teams interface.

2/ Check whether the file is checked out

In SharePoint, select the affected file.
Open the Details pane or select the More options (...) menu.
Check whether the file is currently checked out to you or another user.
If it is checked out, try checking it back in.
If it is checked out by another user, that user may need to check it in, or a SharePoint owner/admin may need to discard the checkout if appropriate.

3/ Review the library checkout setting

In the SharePoint document library, go to Settings > Library settings > More library settings > Versioning settings.
Check whether Require documents to be checked out before they can be edited is enabled.
If this is set to Yes, it can affect both editing behavior and AutoSave in the Word desktop app.
If your organization’s policy allows it, try setting this to No and then test AutoSave again.

4/ Check folder-level permissions

Since the issue only happens in a certain folder, please check whether that folder has unique permissions.
In SharePoint, open the folder.
Select Manage access or go to Advanced permissions.
Confirm whether the folder is inheriting permissions from the parent library.
If inheritance is broken, please confirm that your account has Edit or Full Control permissions on that folder specifically.

5/ Test with a new document

Create a new Word document in the affected folder.
Open it in Word desktop and test AutoSave.
Then create another test document in a different folder in the same Team.
If the issue only occurs in the affected folder, that strongly points to folder-level permissions or library settings.

6/ Check your Office desktop sign-in state

Open Word desktop.
Go to File > Account.
Confirm that you are signed in with the correct Teams for Education account.
If there are multiple Microsoft accounts signed in, sign out of the unrelated accounts, close all Office apps, then sign back in with the education account.
After that, reopen the file from SharePoint and test again.

If the issue continues after these checks, please share any relevant details, such as the affected folder path, screenshots of the error, and whether other users are experiencing the same behavior, so I can help investigate further. Also make sure to redact any personal or sensitive information before sharing the screenshots or file path.

Please understand that my initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution.

I hope this information is helpful. Should you have any further questions or need additional assistance, please feel free to share them in the comment below. I'm very happy to help.

I'm looking forward to hearing your thoughts.

If the answer is helpful, please click 'Yes' and kindly upvote it.

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

Heather 40 Reputation points

2026-08-05T13:29:54.17+00:00

Thanks for your help. It seems like the issue is related to check-out required settings. I turned it off and then turned it back on. I now have access to edit the documents at least. However, I still am unable to use auto-save. Is it potentially a setting on the back end configured by my administrator? It seems likely because auto save is on until I edit the document and it saves once. Once it has saved, auto-save turns itself off and I am no longer able to turn it back on again.
Chris-D 565 Reputation points Independent Advisor

2026-08-05T15:39:04.7933333+00:00

Hi Heather,

Thank you for the update. It does sound like the issue is tied to the SharePoint Require Check Out setting.

If Require Check Out is enabled on the SharePoint document library, Word desktop may disable AutoSave once the document enters a checked-out or exclusive-editing state. AutoSave is designed to continuously save changes to OneDrive/SharePoint, while check-out is designed to lock the document for one user until it is checked back in. Because these two behaviors conflict, AutoSave may turn itself off in the desktop app after the file is edited or saved.

This would also explain why AutoSave works in Word for the web but not consistently in the Word desktop app.

If your goal is to use AutoSave and co-authoring in Word desktop, the recommended approach would be to keep Require Check Out set to No and rely on Version History instead. If your organization requires check-out for document control, then AutoSave may not be available in the desktop app for that library, and users would need to manually save changes and check documents back in.

It may still be worth checking with your Microsoft 365 or SharePoint administrator to confirm whether Require Check Out is intentionally enforced for that library, or whether any retention, sensitivity, or document management policies are applied.

For your reference: Check out, check in, or discard changes to files in a SharePoint library | Microsoft Support

I hope this information helps. Please contact if you need anything else.
Heather 40 Reputation points

2026-08-05T16:13:02.6966667+00:00

I believe this worked in the past by auto-saving locally. Do you know if something changed recently with Microsoft? Also, I'm able to use auto-save in excel still, but not Word.
Chris-D 565 Reputation points Independent Advisor

2026-08-05T20:51:12.66+00:00

Hi Heather,

Thank you for the additional details.

I’m not aware of a confirmed recent Microsoft change that specifically changed AutoSave behavior for Word with SharePoint check-out. However, Microsoft’s current guidance is that AutoSave is designed for files stored in OneDrive, OneDrive for work or school, or SharePoint in Microsoft 365. It is not the same as saving directly to a local-only file.

If it seemed to auto-save locally in the past, it may have been one of the following:

AutoRecover, which saves temporary recovery information and helps recover a file if Word closes unexpectedly.

A locally synced OneDrive/SharePoint file, where the file appears local in File Explorer but is still connected to the cloud.

The Office document cache or sync process handling the file in the background.

Since this may also depend on your school’s Microsoft 365, SharePoint, or Office policy configuration, I would recommend reaching out to your school’s IT administrator to confirm whether any recent changes were made to the SharePoint library settings, check-out requirements, retention policies, sensitivity labels, or Office update policies.

If needed, your IT administrator may also open a support ticket with Microsoft Support through the Microsoft 365 Admin center so they can review the tenant-side configuration and investigate this further.

I hope this helps clarify the behavior. If you have any further questions, feel free to reach out.