Event banner
Microsoft Loop AMA
Event Ended
Tuesday, Jan 17, 2023, 09:00 AM PSTEvent details
We are excited to announce a Microsoft Loop AMA on Tuesday, January 17th at 9:00 AM Pacific time!
Join us as our experts discuss how teams can think, plan, and create together with Microsoft Lo...
Meenah_Khosraw
Updated Jan 17, 2023
Stefan1
Jan 17, 2023Brass Contributor
Hi, Why is every Loop component saved on a users OneDrive? It should be changed to save it on a SharePoint site of a Teams teams so it does not get lost, when a user leaves the company.
- Shane ChismJan 17, 2023Brass ContributorThanks Stefan! It's a great point and definitely one we've talked to a lot of customers about. There's some benefit to having Loop components stored in a user's OneDrive in certain cases (for example, many admins will want to put data controls to ensure multiple employee owners of content stored in SharePoint, and that doesn't lend itself well to "me" stuff that you create for yourself). That said, in collaborative scenarios, it does make sense to follow a more SharePoint-style sharing and permissions model, which is why for the new Microsoft Loop pages we are following a model where all Loop pages created in a Loop workspace are created in a more SharePoint-style container. This will allow admins to put data retention policies in place that map a group or team model vs. a more classic user model (where things can be deleted after an employee leaves the company).
- BenSteginkJan 17, 2023Iron ContributorYes! Was just chatting about this the other day...with all the embedded loop components in Word, Outlook, and Teams...having these components dependent on individuals OneDrive accounts staying licensed and active could cause all sorts of issues...
- darrellaasJan 17, 2023MVPI think it’s right to store Loops in OneDrive when the collaboration begins in a private chat or an email with a few recipients. But components will eventually be supported in SharePoint and that will make it easier to share with the team, and move OneDrive based components into a team site for sharing.