How are you dealing with applying information governance and/or retention policies in Office 365? How are you dealing with new applications such as Microsoft Teams where documents are loaded outside of a traditional document management system?
San Diego County Water Authority
I am looking for the same information. We are just readying for Office 365 implementation. Do certain features have to be be activated? What works and has worked for your organizations?
Lorelei Chernyshov, CIP, IGP
Director of Information Governance
Considering how badly, from an IG, IM, Standards, and security perspective (not to mention UX, sustainment, integration, I can go on….) many O365/M365 deployments are done, this is a very, very big topic (IMO, of course) and should (again, IMO) be addressed by engaging a competent, experienced, standards-driven partner (or at least individual resource) to guide you. Assuming your organization doesn’t want to deploy O365/M365 just as badly as many others just to be “part of the club and get the t-shirt”.
But, that’s solely my individual take on it.
Will staff actually migrate business value information from O365 into a traditional document management system? The path of least resistance says…haha.
However, you can apply records retention to Office365 content in the form of labels.
Hi, I agree with @Lorne Rogers on this. It is crucial to have someone that assists you in understanding the document structure within Office 365. Many do not know that Files in Teams are actually within a Team Site (Document Library) in SharePoint. We have been assisting companies that come from files shares, SharePoint On Prem and even SharePoint Online which have not fully understood the connection between documents and files within Teams and other services in Office 365, like Onedrive and SharePoint.
In addition to that, the document management funcationality and permission levels are currently very limited within Teams and for more advanced document management you would always have to implement that within SharePoint. For instance, document approval process and metadata to name few.
In my opinion working with documents within Teams should be on the level of group/team/project collaboration, sharing and working on shared documents that belong to that structure where permissions levels are limited to full/contribute/read permissions only on the whole set of documents.
Again in my opinion, the information governance and architecture should be built around these four information pillars of Office 365
- SharePoint – The backbone for all documents for the organization, teams, projects
- Onedrive for Business – Employee documents, should be limited as possible
- Outlook – Email and other communications, find ways to save important and relevant content to SharePoint
- Teams – For collaboration within teams/groups/projects where permissions are limited to full/contribute/read permissions, is just a view/entry point into team sites in SharePoint
- Other document / information structures if allowed such as dropbox. Google drive (not recommended)
Hope this clearifies and helps in you journey.
Lorne, Sigurjon, and others in multiple threads are all on point.
The topic is very vast and the solutions are very specific to the business.
Someone who knows the area for assistance…someone who can look at your use case in particular and couple it with the tools available…is required. Resources here are good, check them out. But also go to your local AIIM meetings and JOIN! 🙂 SharePoint users groups can be OK, but frankly, well attended with folks that have limited experience.
Wish you very well! Reach out if you like, happy to help!
IQ Business Group, Inc.
Just HAVE to give a shout out for the line “well attended with folks that have limited experience”! That was just awesomely funny, LOL! And subtle! (and TRUE!)
Ha! Ya, I was just typing fast, I am more of an engineer and doing delivery so I would LOVE to respond to more of these…it is overflowing with opportunity to take out day to day frustrations with subtle jabs. 🙂
IQ Business Group, Inc.
I think there are two key points here.
First, Teams loads documents to SharePoint. If you’re inferring that SharePoint isn’t your document management system, I’d consider how to manage a hybrid environment.
Second, I think it’s important to understand the business needs for governance and understand what the features are of the platform. Depending on your needs, classic SharePoint features may be sufficient, or you may find that you need to implement Microsoft’s Office 365 labels approach. If you need to use labels, it’s important to understand what they do — and do not support from the perspective of your goals.
Thor Projects LLC
Thanks for making those two points – There is also a records center in SharePoint that can be used to retain documents labelled as records when the team sites eventually go away, correct?
Peter Rahalski, CIP
Information Solutions Architect
EXCELLUS HEALTH PLANS
Yes, sort of. Records centers can retain records but those are records which are declared as records and sent to the center. There’s an additional records model which holds records in-place. There’s not an automatic migration from one to the other.
If you’re using in-place records management in SharePoint (or SharePoint via Teams) you have to consider what you’re going to do when you want to retire the team to move the records into more permanent storage. There’s not an out of the box way to do this currently.
Thor Projects LLC
- Click to share on Facebook (Opens in new window)
- Click to share on Twitter (Opens in new window)
- Click to share on WhatsApp (Opens in new window)
- Click to share on Skype (Opens in new window)
- Click to print (Opens in new window)
- Click to share on Telegram (Opens in new window)
- Click to email this to a friend (Opens in new window)
- Click to share on Reddit (Opens in new window)
- Click to share on Pocket (Opens in new window)
- Click to share on Pinterest (Opens in new window)
- Click to share on Tumblr (Opens in new window)