How to view and restore Microsoft Loop version history

If you need to view or roll back a previous state of a Microsoft Loop page or a single Loop component, the definitive history lives with the file in OneDrive or SharePoint; the Loop app and embedded views in Teams/Outlook point to that file. Open the Loop page or component, then use the page menu to jump to `Version history` or `Open in OneDrive/SharePoint` to see saved versions. Below are exact, step-by-step actions to view, copy or restore versions, plus required prerequisites, retention and permission limits, component vs page behavior, and troubleshooting tips.

I need to see or restore an older Loop page or component right now

Prerequisites

• A Microsoft account with access to the Loop page or the host file.
• Edit permission on the OneDrive file or SharePoint library that stores the Loop file when you need to restore or save changes.
• If you use Teams or Outlook embeds, the message or channel must still contain the component and you must have access to the hosting mailbox or team.

Steps — Loop page (inside Loop app)

1. Open the Loop app and open the page you want to inspect.
2. Click the page menu (three dots) near the page title.
3. Choose Version history or Open in OneDrive/SharePoint.

A list of previous versions or a link to the file in OneDrive/SharePoint.

4. If you see a version list, select the version you want.
5. If the host shows Restore, click it to replace the current file state; otherwise open the prior version and copy what you need.

Restoring a previous version at the file level overwrites the file state.

Steps — Loop component embedded in Teams or Outlook

1. Open the chat, channel message, or email that contains the Loop component.
2. Click the component to expand it and click the ellipsis menu (three dots) or choose Open in Loop / Open in browser if shown.
3. When the component opens in Loop or the browser, use the page menu → Version history or follow the link to OneDrive/SharePoint.

You arrive at the version history for the file that holds the component or open the full page containing the component.

Steps — If you land in OneDrive/SharePoint version history

1. From the version list, either restore the whole file or open a previous version.
2. If you only need a component, open the prior version and copy the component content into the current page or component instead of restoring the whole file.

Restoring a version from OneDrive/SharePoint replaces the current file. If you only need a single component, copy content from the older version into the live page to avoid overwriting other recent edits.

Completion — how you know it worked

• If you restored a version, the file content should match the selected version and OneDrive/SharePoint will add a new version entry for the restore.
• If you copied component content from an old version, the current page or component will display the pasted content after you save or the host syncs.

How Loop version history differs by location — Loop app, Teams/Outlook, and SharePoint/OneDrive

Point first: OneDrive or SharePoint is the canonical store for Loop files and their versions. The app and embeds are views that either show history inline or link to the file.

• Loop app: Presents pages and components and often links to the underlying file. When inline page-level history is available, you can use it; when it’s not, the app sends you to OneDrive/SharePoint for full history.
• Teams/Outlook embeds: An embedded Loop component in a message is a live view of the component. The embedded view itself does not always show a full history; use Open in Loop or Open in browser to reach the stored file and its version history.
• OneDrive/SharePoint: These hosts keep the definitive version history according to tenant settings and library configuration.

Practical effect: To restore a whole-page state, use OneDrive/SharePoint. To restore only one component, open a prior file version there and copy the component content into the current page or component.

Why I can’t see older versions or the restore option is greyed out

Common permission and retention reasons

• You don’t have Edit permission on the file; view-only users often can’t restore or sometimes can’t see the full version list.
• Versioning is disabled for the SharePoint library or the OneDrive account where the Loop file lives.
• Tenant retention or governance policies have purged older versions beyond the retention window.
• The file is stored in a location or under settings that restrict guest or external user access to history.

What to ask your admin or change in settings

• Confirm the file’s storage location and whether versioning is enabled for that library or OneDrive account.
• Request Edit permission on the file or the site if you need to restore versions.
• Ask whether a retention policy removed older versions and whether backups or compliance vaults can recover them.

Exact retention time spans depend on your tenant’s OneDrive/SharePoint settings; contact your admin for specific limits.

Component-level history versus whole-page history — what actually gets tracked

What is tracked

• Loop stores edits at the file level in OneDrive/SharePoint. Page-level structural changes, component edits and saved states become part of the file’s version history when the host creates a saved version.

What may not be tracked

• Edits that never reached the server (local unsynced edits) won’t appear in version history until they sync.
• Short-lived views inside a message may not create a persistent version unless the host saved a new file version.

Restoring a single component without reverting the whole page

1. Open the file’s version history in OneDrive/SharePoint and open the prior version you need.
2. In that preview, find the component content and copy it.
3. Return to the current Loop page and paste the copied content into the existing component or create a new component.

This preserves other recent changes while restoring the single component content you need.

Quick fixes when versions are missing or changes don’t appear

Checks to do first

• Verify you’re looking at the correct file: identical pages or components can exist in different workspaces or messages.
• Confirm you have Edit permission on the file or the site.
• Ensure your client has finished syncing: refresh the Loop page, close and reopen the component, or refresh the browser.

Steps to try

1. Close the page or component and reopen it to force a client sync.
2. If you opened the component from Teams, choose Open in browser or Open in Loop to reach the storage host directly.

OneDrive or SharePoint site > Library > (select file) > More actions > Version history

3. Check the OneDrive/SharePoint recycle bin if you think the file or a version was deleted.
4. If versions still appear missing, ask your admin to check tenant retention, backups and audit logs in the compliance center.

How you know a fix worked

• Restoring a version should make the file match the selected version; the version list will show a new entry for the restore or subsequent save.
• Copying content from an older version into the live page will show the old content in the component once saved or synced.

Troubleshooting notes

• If Restore is greyed out, confirm you have Edit permission and that versioning is enabled for the library.
• If recent edits don’t appear in history, wait for the client to sync and then check OneDrive/SharePoint again.
• If versions are missing entirely, tenant retention policies or library settings are the likely cause; involve your admin.

Conclusion

Go to the file host (OneDrive or SharePoint) for the authoritative version history. Use the Loop app or an embedded view in Teams/Outlook only to navigate to that file. If you need only one component, open a prior file version and copy the component content into the current page instead of restoring the entire file. If history is missing or controls are disabled, check permissions, library versioning and tenant retention policies and ask your admin to review backups and audit logs.

Frequently Asked Questions

How long are Loop versions kept?

There is no single retention period for all Loop versions. Version retention depends on the OneDrive/SharePoint versioning and retention settings configured by your tenant. Ask your IT admin or check the site settings where the Loop file is stored for specific limits.

Can an admin restore a version for me?

Yes. An admin with access to the SharePoint site or OneDrive can restore versions and search backups or compliance archives. Provide the file path and an approximate time range to help them locate the version.

How can I see who changed a Loop component?

Open the file’s version history in OneDrive/SharePoint to see who saved each version. For more detailed auditing, ask IT or compliance to check audit logs in the Microsoft 365 compliance center.