 Good morning, afternoon, or evening to those that are joining us today. My name is Kevin Mulholl, and I'm a technical customer success manager here at TechSoup. I'll be moderating today's virtual office hour, so you all are aware we are recording this session. Those that have registered will receive a link to the recording along with a copy of the slide deck. I'm joined by a very special guest and one of TechSoup's own, Michael Inos, our senior director of community and platform. Hello everyone, it's really great to be here. Thank you for having me, Kevin. Absolutely. Before turning it over to the bulk of the presentation, which Michael will be speaking on, I'd like to address a couple of housekeeping items. Please use the chat function to type in your questions and comments. We will collect the questions and comments during this session and address them during the Q&A portion. In fact, as some of you have already done, some of you may not, we can begin using the chat by saying hello and writing in where you're attending this conversation from. As some of you have already heard, I'm personally dialing in from Westlake, Ohio. For close captioning, please click on the ellipsis and then turn on live captioning. Again, this session is being recorded and will be made available within 72 hours of this presentation to those who have registered to attend. A quick overview of today's topics. First we're going to begin with an intro to SharePoint site types. We'll then be moving to Microsoft lists before going to Governance, Governance Overview and Considerations, then moving on to Compliance and Permissions, Integration with Teams and Site Administration. And with that, I'm going to officially hand it over to Michael to begin breaking down some of the details in the previous bullets. Go ahead, Michael. Great. Well, thanks to everybody for joining and thank you, Kevin. It's a great pleasure to be here. And I wanted to first just introduce myself quickly and why I'm here speaking about this topic. And I've been with TechSoup for about eight years. And prior to working at TechSoup, I worked in the food security sector, working with Food Bank of Silicon Valley and also worked very closely with Food in America, helping organizations, food organizations, pantries and food banks leverage technology, help design supply chain systems and volunteer systems and such to help improve the efficiencies of the food security sector. And I did that work over 10 years. And before I start, I want to tell a quick story because I've been working with SharePoint since shortly after it was launched in 2001. And in about 2004, I was working with a group. We created a group called the Operations Technology Consortium, which comprised of the technology leaders of the 10 largest food banks in the country. And we would have meetings where we would discuss how we can share and optimize our collective technologies so that we weren't each inventing our own systems. Food banking is very unique in terms of the way that you manage inventory. So we had a specialized version of Microsoft Dynamics that we used to help us track that we collectively co-collaborated on the creation of. And we would do that partially through this consortium that we created. And one evening, we're at the first consortium meeting, and we discussed how are we going to collaborate with each other. And so myself and the technology director for the Houston Food Bank, who's so close to my mind, we went back to our hotel rooms and that evening actually brought up the OTC SharePoint site, which remains possibly still in use today. And it was a very effective tool that we used to collaborate amongst ourselves and other food banks. And so at that time, of course, it was an on-premise system. And so when I came to TechSoup, we were still sort of, we still have a lot of, most of our systems were on-premise, at least our Microsoft productivity suite. And so one of the first things I did when I came to TechSoup was move us to Office 365. And we are now, we've now migrated a lot of our, most of our, a lot of our on-premise SharePoint internal stuff that we do at TechSoup to SharePoint online and are just going to be launching in a sort of our official sort of new internet very soon. But currently some of the teams are using it. So, and I'm involved with some of that work, obviously. But so I wanted to basically provide sort of what I've learned over the years. This isn't going to be technical, although I could try to address the technical questions if you have some. But this is going to be more general. But essentially, as most of you know, at its heart, SharePoint is a web-based collaborative, collaboration platform. And it's oftentimes used by organizations for document management and as a storage system. It's really integrated tightly within the Office suite. And it's tremendously configurable. There's so much you can do with it. There's plugins, there's all kinds of, you can change the look and feel of it. You can make it pretty much almost anything you want to. But it has this very, very rich back-end architecture, you know, that you can leverage. You can, you know, it's got these, I'll go into some of the basic concepts. But essentially, these are some of the things that, you know, are the capabilities at a very high level. So, you know, so maybe Kevin, if you can advance to the next slide, I'll get into some of the details. But first, I want to talk about some of the core concepts. Essentially, there's sort of a, you know, when there's sort of this recently, they launched what they call the modern experience in SharePoint, which is, you know, kind of a little bit more like it kind of pre-vills the site for you very easily, which is great because it's sort of, it can jumpstart your entire sort of, you know, you know, if you're creating a new site, it can kind of jumpstart that process and more immediately sort of get you access to the things that you would need for it. There's a concept of a start page in this modern experience. And this is where you could, you know, kind of pull in feeds, where you could have high-level bullets and, you know, as you can see here, the links to direct sort of resources and also, and web content that gets pulled in from other areas. And also, this is where you can very easily sort of just create a new site or create a post. And oftentimes this is sort of integrated within the context of somebody would, you know, normally call a collaboration site, like an intranet. Next slide. One of the fundamental concepts is the idea of links, which are essentially, it's essentially, you can think of as a collection of shareable data, but that data could be anything and it could be in column form, it can be in a blog post form, it could be in a calendar form, it could be as contacts or issued, like issue tracking form surveys, is essentially, you know, and by combining different types of lists, you can pretty much very readily build an entire very rich, you know, portfolio of content and feeds that pull in from dynamic content. So one thing to remember about your point is that it's very dynamic and it's meant to be dynamic, meaning as data changes, the site will update based on that change data. I mean, you can have it for preserved data, you know, for example, like you're in play handbook or things like, you know, recordings of things that don't change like static content, but it's real power is an ability to leverage real time, you know, things that are happening, for example, a feed from your blog post. So your company's news events or press articles that come up, you know, can be triggered and then they can come in automatically into a list or announcements, things that happen. So that, for example, you have a, you know, something every changes, you know, the events for your weekly organization or things that are happening in the community. You can have these sort of automatically feed into it, into it, you know, and generate that, you know, content live for your audience. The next page, please. Important, one of the things I do at TechSoup is I oversee our cyber security and data security. And so one of the things that's very important to have, you know, understanding of is some basic principles of security and governance. And these things will, you know, naturally apply to, you know, anything that you do with technology and your organization. But for something like as powerful as SharePoint, it's especially the case, because if somebody has too many, you know, too high privileges, they can, you know, sort of mistakenly do something or harm a production environment. So one of the things that concepts I try to teach people or let people know about is this concept of the principle of least privilege. And so as an administrator, one of the way this rolls out is that you only want people to have the privileges and the permissions for the work that they need to do in their role. So think of it like role-based permissions. So for example, if somebody has, you know, somebody's in marketing, you know, they should have the ability to do things they need to do for the marketing team, but not necessarily the same thing they would think like what the finance staff do. So, you know, you basically have to, you want to control that so that you don't, nobody except for the main owners or administrators or the IT staff, have sort of access, you know, the trained staff who understand the power of this, you know, have access to the global settings, for example, because they could inadvertently, for example, turn on guest access for, you know, everybody and then, you know, next thing you know, there's all kinds of people crawling on your site that you don't want to. Another, you know, critical practice is understanding, you know, and understanding how your data is, you know, sort of categorized. Sensitive data or confidential information that shouldn't be shared externally should be in its own site unless this, you know, in a site that is, you know, doesn't have the ability for somebody to provide guest access to an external user. And, you know, there's a process for that. So, for example, if, you know, you know, Kevin wants to add somebody to a collaboration site, there's no problem with that, except that what we don't want is maybe for him to have the ability to do it himself, because, but actually have it done by an IT staff who's trained because that way it's documented and when that person does not need that access anymore, we could remove that access. So, these are very important, you know, sort of concepts that we employ and it's part of a larger sort of idea of what we call privileged access management or PAN, which is a fundamental concept in IT security. A very important other thing that Microsoft has some really powerful native security tools that can be used. For example, alerts that happen when people log in from places outside, you know, that they normally would log into. So, for example, if all of a sudden, you know, today I logged in from California or Montana and knows that, but let's say four hours later, Microsoft noticed a login from China, it would flag it and send an email alert to to, you know, the person who's monitoring, you know, the the the global admins saying, look, this is suspicious login. As well as, you know, those sorts of, you know, configured the ability to configure those types of security alerts, there's also a native Microsoft Defender that will help scan documents and thanks for malicious content, malicious files prior to them actually, you know, in the site, calling to the site. So, for example, if somebody was to, you know, get a malicious document and an email and they they just said, oh, I'm going to, I want to share this with my IT team so that they could look at this. I'm going to post it on SharePoint. It will flag that just like it does throughout the entire sort of ecosystem. So, but oftentimes this stuff really needs to be configured. It doesn't natively, it doesn't, if you move on to the next slide, I'll talk a little bit more about some of the things that are, you know, other types of considerations. The SharePoint, fortunately, has very granular access policies and also very granular permissions. So, you could very much sort of refine, you know, what types of things people could do within the site. I think it's one of the more complicated parts of, you know, working with SharePoint, but because it's almost so flexible and with the permission structure, it's kind of like you can kind of get lost and it's like, oh, I don't understand, how does this going to affect my, you know, and so you have to understand the relationship between sort of the hierarchical nature of how things kind of cascade down in the permission structure. So, this is important when thinking about it because, you know, oftentimes permissions are inherited from a parent and so there's, you know, understanding that and spending time learning about the permission structure will go really long ways to understanding how to best configure SharePoint. The other thing is, I mean, it has also these other very fine points like, for example, if you want to block some secret confidential sites from unmanaged devices, meaning devices that aren't, you know, haven't been, aren't being scanned by Intune or haven't been provisioned using Intune or not part of your domain. For example, like, you know, a mobile device or somebody's personal, you know, iPad, you can block those types of devices from being on the network as well as places in geographic regions. So, for example, if you're not going to be doing business anywhere with anybody in, say, Russia, then you can just block the IP ranges in Russia and not worry about that or, and just actually very specifically, even more specifically for other people in California, you can just say, I only want people, you know, and of course there's ways around that and, you know, hackers and people who are, you know, threat actors at that found ways around this sort of geo mapping, but it is, it is a good sort of first start. So, if you can move on to the next slide. So, essentially, in terms of the, one of the things that's really great about SharePoint is it's sort of, is it's integration, it's very, very tight integration with Teams. And it's almost as if SharePoint is, or Teams is part of SharePoint or vice versa. It's almost like they're really interest-wine, but Teams leverages sort of, think you can think of this way, Teams, Teams leverages this sort of backend infrastructure and schema and data storage of SharePoint. So, for example, a SharePoint site, essentially, is, you know, the top two things are, you know, so for example, when you create a team, it's automatically creating a SharePoint site for that team. They could be used independently, but they're also used, you know, by teams for file storage. So you can create a site that doesn't, you know, you're not integrated with Teams, but generally the two are connected. So, for example, and you want that, actually, I'm going to say, because you want that rich collaboration through your web content, you know, collaborate with, if it's a web-based collaboration tool, having Teams integration is great. But you can also do other things. For example, a team can have its own site where it manages collaborative, you know, documents for collaboration, where there's, you know, updates or announcements for that particular team. So you can see this, there's this concept of the parent site, which is this, that's what's created when you create a team. And everybody by default, probably this team has access to that. But then there's also a site that's created on the channel level, too, so that if you're just talking about a particular topic, you can create sub-sites, you know, you think you can have sub-sites for that. So there's just still that part of that sort of hierarchical sort of approach that I was talking about in terms of the way that SharePoint is structured. So maybe we can move on to the next slide. I hope that moving through this too fast, but I want to make sure we have lots of time for questions and answers. So here, as I mentioned before, this very rich sort of hierarchical sort of, you know, way it works. This is sort of an illustration of this. I have, by the way, these are what you see in the slide deck, these sort of things that are underlined. These are hyperlinks to that actual documentation within, in Microsoft. So when you get this deck, you say, oh, I want to go back to what Michael was talking about, about the, you know, hierarchical permission structure, you know, or some of those security governance policies, you can click on that link and you can go there and get that documentation directly from Microsoft. So this is sort of an illustration of it, but you can see that there's this item, a site collection, and then there's a top level, which then cascades down to subsites, which then each of the subsites, then we'll, we'll contain these lists. Like I said, lists, it's a, it's sort of a very generic term, but I mean, that could be any type of dynamic content or even static content. And it's oftentimes in very different forms, you know, like a calendar or a best page or announcement or a survey or form. And in that's why it's kind of said list items, you know. And so those, these are the things, the list, the list is composed of list items. So that would be the example for, you know, would be if the list is a calendar, the items would be the events on the calendar. And the permissions kind of cascade down. So you can see here, there's permissions for the site collection, permissions for the subsites, permissions for lists, and then permissions for list items. So for example, if you wanted just somebody to be able to not add a calendar, you know, but you wanted them to deal with that events to a calendar, you can say this person is, you know, has those sort of permissions to do so. All right, move on. Next slide, please. So there's these are, you know, we often sometimes also can think of this as role based permissions, but there are some default permission levels. And this sort of gives you an idea of the ability to kind of quickly create, you know, you know, sort of, you know, you can create your own role and then, you know, with, with granular permissions, but Microsoft provides the ability for you to sort of have these default permissions, which in this area, you can, you know, it allows you to quickly and easily provide common level of permissions for one of these groups. So, and now we can go ahead and see who's a member of which, you know, who are team site visitors versus team site owners very quickly. And you can actually add people or take them away or move them around in these groups. And then their permissions as a result change. And you can see that the permission levels can be things like just, you know, view only, edit full control, like, and that would be for an owner of a site. And, and then things where as a visitor, you just want them to read because you don't want them making any edits. So that's fine. We can we can move on to the next slide. So this is, you know, this is, you know, we're, we're starting to get near sort of the, you know, the place where this is, this is a little bit more, yes, high level. But, you know, one of the really important things to do is when you're is to think thoughtfully about something, if it's going to be a, you know, I mean, you could use, you know, before we sort of launched, you know, at TechSoup, before we embarked upon, you know, saying, are we going to build this whole internal agency enterprise intranet and TechSoup is very large organizations international. It's really good to, you know, sort of, we spent a lot of time months and months discussing planning with all the other departments and teams within the organization. For example, we wanted to find out the requirements, the needs, the gaps in terms of things, so that when we rolled it out, it would be adopted, and it would be successful. And also people were engaged, if people are engaged in something, during the planning and the process, then they're going to be, you know, super users, they're going to be engaged, they're going to be, there's going to be better adoption. And also just the content won't be static. I think oftentimes, one of the things that can happen with an unsuccessful rollout of SharePoint is that people go through a lot of effort to build something, but they do it sort of in a black box, they launch it, people look at it, and then the content gets stale, it never changes, and over time, and there isn't, because there isn't really rich participation. A SharePoint, a successful SharePoint team, or because it's a collaborative platform, the most important thing is to encourage collaboration. And the way that, you know, the best way to do that is to bring people in, you know, socialize it with the departments, that will foster adoption, engage key team members in the planning and design, and really work with them in the design. If you're the person who's the right owner, it's this is, you know, it's so critical to the success. It's also important to consider, you know, who's going to own these different subsites, right? So when I worked at the food bank, what we did is we sort of had somebody who was, you know, in a relatively senior position in the department, but it was also, it was knowledgeable enough to be able to actually, it's not, you don't need a lot of technical knowledge to do stuff in a SharePoint, it's one of the beauties of it as well, is that you're not really young need to code unless you want to do something really fancy, like create API integrations or, you know, custom, you know, graphical interfaces and such, but you can bring other people in to do that, but then it's pretty much plug and play. And so if you train people who, you know, for example, I mean, you know, there are people in the culture department or on the finance team to, you know, this is, it's how you can update the, you know, our sort of monthly dashboard or KPIs or this is where you can find resources for an employee. As those things change, like as the, you know, take calendar changes each year, they'll have the ability to do that without having to, you know, go to the IT department and say, hey, look, you know, we've got some new content resources for staff, can you publish these for us? It's, you know, you want to give the power to the people and you want them to be engaged. Now, it is important that the people who do that have the responsibility and us to understand this sort of, you know, that they're accountable for what they post. And, you know, in, but most people who are within an organization who are in that sort of more senior role will use good judgment when we're posting content and will not use it for, you know, if they want, you know, for example, a, you know, if you want to share something about, you know, adopting, you know, kittens from your house, you know, if you're, if you want to develop something like this, maybe be a separate site than the site that actually has your resources for your, you know, employee handbook and such. Just, you know, some advice there in terms of making sure that the site, the type of site, the content in the site matches sort of, you know, what the intent of that is. It should be intentional. And I think part of this is, you know, providing access to training resources and support channels. So if somebody does have a problem, you know, who do we go with, you know, maybe because you don't want to get frustrated. If they're trying to develop something in SharePoint or to put something together, they should have access to, you know, either support channels or to documentation and things, you know, the training resources so that they can, you know, get what they need and do what they need to do. So at this point, I'm going to hand it back to Kevin who's going to talk a little bit about, you know, the ways that TechSoup can help and also, you know, how to create, you know, sort of, and what we do ourselves. So thank you. Thanks so much, Michael. Thank you so much. And I've seen that that's come in through the chat feed as well. So to the point here, it's okay to ask for help. There's several options, and we've built this out as part of the discussion flow. We're getting with requesting managed support. We have TechSoup several managed partners with whom which we work. There are a couple of them that immediately come to mind that this is right up their wheelhouse. If this is something that you look at internally and think this is, we need to have this, this needs to be part of our infrastructure, our digital infrastructure. But we don't really want to jump into the deep end on this. That's definitely a situation or scenario where a managed provider would come into play. Whether it's something as simple as a general page setup and even a one-on-one tutorial session, we have a managed partner that specifically has that product within their catalog all the way up to a full integration with containing multiple types of APIs. As Michael had mentioned, all the bells and whistles. We have a partner that also works on scaling those out. Connecting with a contractor or someone who specializes in SharePoint. There are a ton of people that do that. There's don't want a name that may be able to scale a project for you. The access to this catalog typically has a cost. The product that is in our catalog provides it to you for free, along with a 20% discount to your first paid service. That would definitely be something I'd recommend it looking at as an alternative, perhaps, to manage support. And then getting into the last part here, seeking a volunteer. Again, depending on what it is that you are looking to do with SharePoint, even bringing on someone in a voluntary capacity may make sense. When I think of that, I think of resources such as Ketchifier, Volunteer Match and Taproot Foundation are just a couple. I don't think that we necessarily have direct affiliation with those, but I know that in the past there's been some engagement that we've had. So if you are strapped for resources, you don't really know which way to go. And these two that are mentioned are not in your wheelhouse. A volunteer may be an excellent alternative to that. So with that, we're going to open up the floor for Q&A. I'm going to take a quick look at the chat first to see if we have anything that's sitting in there before just allowing individuals to come off of mute and to ask their questions. So it looks like we had a couple that were going on the same thing with an environment that is a little bit smaller, a smaller group of people. And again, that speaks, hopefully we address that, that there are some options to manage providing or even a contract service. What you're looking to do will probably be smaller in scope, document libraries, etc. I think that those would be a great place to start. We'll also be providing contact information at the end that you can get in contact with us and we can discuss your projects a little bit further. I do have a question that's coming in. Jamie, you're welcome to come off of mute if you wanted to ask it live or otherwise I can throw it on out there. Yes, thank you. So my organization, we have about seven terabytes of data and people don't like using the VPN to connect to our file server and management wants to move to the cloud. And they're talking about SharePoint and I never really thought of SharePoint as like a replacement for a file server, but I guess is that possible or does that make sense to do that? You know, it is sort of, I mean, I think that it can serve to that capacity, definitely. It's not, it wouldn't be necessarily, you know, generally when people think of file servers, they have a specific sort of idea in terms of what that is in terms of like, for example, there's sort of this old school sort of approach to sharing where you have each department has its own file store and they manage their departments with it, but then they can open up that drive or it's like a shared drive on their system. There is some capabilities for using OneDrive to that capacity and SharePoint to that capacity. However, depending on the amount of data you have, it sounds like you have a tremendous amount of data, you may have to break that down into different, you would have on the look at the storage. You know, I don't, my knowledge, I don't think, you know, you can get an office license that would allow for, would you say, seven terabytes? Yeah, yeah. So there are other, you know, other platforms that do do that, but I think that you would probably need to, you know, think about archiving or using if all that data is really necessary to access or, you know, put it, you know, what's most readily accessed in, you know, in SharePoint and that's accessible, but then, you know, in department, like, for example, I texted you, you know, on our older SharePoint sign, we're going to be doing, we kind of are doing this in the new one as we're migrating is we had, we were using it for file source. So for example, but it was mostly for things that were collaborative, you know, documents. We use another system at TechSoup Box for things that are more permanent, more, more traditionally like a file server kind of storage. And then we use SharePoint because it's more for the collaboration side for sharing, you know, things that, for example, you want the whole enterprise to see. And so we do use it as a file, as a file server, but it's not, it's not like, you know, sort of a centralized place where everybody, this is the only place where you put all your files, this is it. You know, we sort of separated the two, you know, types of, we said what kind of documents are for sort of, you know, the things that are like contracts, policies, you know, things like that, that or, you know, contracts or, you know, that's a good example, contracts, you know, contracts probably, you know, you don't need to collaborate necessarily on a contract unless you're creating a contract with somebody else, but then once it's a contract is signed and unique, you know, that's not something you would generally put in SharePoint. You could, you could put in one drive and, and you can share it with others, you know, who need access to that. But it might be, you know, you know, so there's, you have to kind of think through with the requirements of the organization. I think it'd be different for a lot, you know, depending on those needs. But yes, you can't, you can't, the simple answer is yes. Okay, thank you. That was in the details though. Yeah, that's exactly what that kind of what I was figuring with the, since I have so much data, I might might need another location for, for more static storage. So thank you. Yeah, exactly. Yeah, I pinked in some links to also, Jamie, hasn't applied for the Azure nonprofit grant as $3,500 yearly to Michael's point about archived or cold storage. It might be a temporary or even permanent solution for hosting some of that in the cloud. Right. We had another question here. Laura, you're welcome to come off of mute if you'd like. Yeah, I'm wondering if we're kind of debating how best to create an internet for our staff. And we sort of wanted to be like, a lot of our staff aren't very tech savvy. So we wanted to look almost like a website where we can have multiple tabs. So we want the front page to kind of be like the latest staff newsletter. And then we have here, you can find policies here, you can find links to commonly visited sites here. Here's an archive of past meeting, meeting notes, that kind of thing, but have it sort of visually look appealing and easy to navigate. This is, this is the perfect tool for that. I mean, this is exactly in some ways what, you know, in the organizations I work for, this is what the main utility was of SharePoint. And, you know, I mean, it does so many other things, but that's sort of like, I think, with a lot of organization. And one of the reasons is because you could really lock down the permissions to just your staff and not have it accessible to the outside world, right? People have to log in and then depending on what they log into the Microsoft account, that's what they see. But if you want to provide, you know, if you need to be like a consultant or somebody to have access to information on a site, you can, you know, but you'd usually create another site and then with its own permissions for that. But for the, for your needs and your requirements, it sounds like this would be the perfect tool. And then is there a place where I can see sort of visual, like ideas or templates of what that could look like so we could sort of build off that? Absolutely. And Kevin, I'm sure you could, you know, send some links. There are definitely lots of demos. There's lots of content and lots of templates actually that are provided by, you know, by Microsoft to this purpose. And, you know, if you, you know, you are going to want to do, you may want to do some custom navigation work or something like that. And all that's doable. But you just do that sort of thing like once and then it's done. And so people don't, you know, maybe you need a grant like a consultant just to first sort of, you know, if you, if you want to have a specific sort of custom navigation that you are or something that's not how the box, which is pretty rare. Okay. That's really helpful. Thank you. Yeah, I just, to that point, I just threw in my team's mailbox as well as my own personal. You're welcome to send an email to me. I actually, in a voluntary capacity have built a couple of SharePoint communication sites, which are simple out of the box and probably check a lot of the items off that you're looking to do. We'll be happy to talk with you more about that. Yeah, thank you. I'll reach out. Right. All right. I got another question that just came in. Brad, did you want to come off of mute? Or if you'd like, I could just read the question. Yes. I've recently learned it's possible to have your SharePoint site files managed through a personal computer's file explorer. And I was wondering, how do we, how do we do that? Yeah, I, I can't say that as far as Windows PC file explorer, I can't say that I have a really strong knowledge of what that is. I'm familiar with file explorer, but Michael, is there any chance that you? Yeah, there is essentially there are, you know, a location in SharePoint is essentially, you know, it's, it's, it's similar to, you know, OneDrive in the sense that if there's a document repository within, within SharePoint, there is, you know, the ability, from my understanding, to be able to create, you know, essentially a, you know, your, you know, file explorer on your computer is basically just a, it's almost like a URL, you know, in a way. So if you're, if you have the right permissions, you should be able to have links directly. So it's just sort of like a link to that sort of, you know, that storage area uniquely for without having to navigate essentially from SharePoint to that location. And that is, we could probably, you know, since, you know, throw some things in this chat or, or, you know, if you reach out, we can, we can sort of send you some links to that. But if you, you should be able to get that in documentation, all this stuff is pretty relatively available on Microsoft, but we're happy to help if you have any issues with that. All right. Oh, there's somebody actually providing some of the things there. Yeah, there's a, yeah. Yeah. So Becca, the chat is closed to guests after a meeting or webinar shuts off, but some of the content that's in here, I can certainly, I can get that to you. Again, I dropped my email address in there. You're welcome to reach out to me. You should have your contact information as well. But if you wanted to also do that, I can get this into a redacted form that you can reference at a later time. And I have a question here from John. Yeah. I'm just going to go ahead and read just for the sake of time here. We currently use Dropbox for file storage and file sharing. I was not sure from Michael's answer on file share, if SharePoint is a good replacement or not. Yeah. And I'm sorry to be sort of vague about that, but it really depends on the specific requirements for, you know, and, but generally, yes, it is a good replacement. I'm just going to say that generally, yes, it is. Unless you have some very specific sort of requirements, I would, you know, not make it a good one, which, you know, some organizations have, and that would be, but for most organizations, it would be a good, it is a good replacement for a file server. And Kevin sent some links about that. So, you know, and how to migrate files from a file server to SharePoint and have it sort of replicate the same functions. But, you know, there's some very specific types of things that other systems use do that, you know, it may not work well for, but that those are very few sort of off use cases. Right. We are another comment or question here from Becca. We're trying to get 365 up and running. So, okay, okay. Nevermind. That's not a question. My apologies. Becca, again, I just pinged in my email address. You're welcome to reach out to me. I can certainly help with that. See if I've got everything in here. Question. You know what, I'm just real fast, though, the one of the things we did when we rolled out Office 365 is we turned off, we didn't want people, so does they have Office 365 didn't go markers on, you know, SharePoint, radius, size and stuff. So, we got to lock down some of that stuff until we had everybody rolled up, everybody in and trained and we had a plan. So, I do think that's the proper order of operations because otherwise you're going to end up with lots of artifacts that you may not want, you know. And actually the two, your on-premise system will step on your cloud system. If you're still using on-premise active directory, for example, things like distributionalness, you know, if you create something in Azure that could then step on something that's an active directory, you can end up, you know, with some problems. So, it's always a good idea to plan and if you roll something out to think through everything before you start opening up the features because they're so vast and by default, everything in Office 365 or Microsoft 365 is sort of open by default. So, you know, before you, you know, start inviting users to it, you're going to go in there and really look at the configuration to lock things down for the things that you don't want people to just play around with, you know, if you don't want to meet, you know, and just go to town with and stuff. Okay, got another question in here. John, what is the best way to train staff on how to use SharePoint? That would be definitely in your purview, Michael. So, you know, I think that the one of the things that we've done is we do brownbacks. And so, one of the things we'll be doing, for example, when we sort of roll out our new intranet to these, you know, departments and people too, we'll be doing sort of brownback, which is essentially a couple and we'll set them up different times of the day for people in different, you know, time zones. And we spend an hour basically providing access to resources, going through screenshots, going through features and capabilities, answering questions, and then also providing, and then identifying people within departments who could be subject to our experts. And if you, if you train one person within a department, they could help support and train the others within the department to a good way to outsource it if you, you know, if your resource can strain. So those are the things we do internally and they've been very successful. There's also training documentation and there's things Microsoft provides and there's actually just go to YouTube and, you know, it's where a lot of people get trained and everything, like on how to build a deck to how to, you know, configure dynamics, you know, for example, and SharePoint. So, you know, there's lots of freely available information out there, but to, if you want people to have more sort of like, this is how we've configured our intranet, this is how we want, you know, these, these are the parts of it. Those are things more appropriate for an in-person training. So you can show them these things and actually have them even have it on the computer and give them access and have them try it out and then answer questions if they run in problems. So you can kind of do these things in real time. You can create a test environment or a practice environment. That's the other thing. That's a nice thing about SharePoint is you can create a site and then throw it away afterwards because it's, you create one up for demo purposes or for training purposes and let people go to town on that. So they're not going to town on your production one. Another resource that kind of sits, I think, buried in the application stack also is Microsoft Streams. Now granted that you can only record up to 15 minutes of video, but I have filmed a lot of internal demonstrations because I'm a visual person to share internally with how to do certain things within the 365 stack. That might be something also worth looking at. At least again, it's a 15 minute max. So are you going to have a long discussion? No, but there's probably things that you could break down into chunks and do it that way. I have another question in here from Sebastian. A nonprofit sister organization has been holding some of our data in their SharePoint, 10 gigabytes plus. Now we have established our own SharePoint and I want to move the data to its new home. Is there an easy way to transfer the data to the new SharePoint other than downloading and reuploading in small segments? I think I might know an answer for this. If it's still available, there's a tool and correct me if I'm wrong, it's called Mover. I think that's supposed to get retired, but I don't know when, but I know it's at least was available as of a couple of weeks ago when I walked somebody through that process migrating something similar from a SharePoint to a SharePoint tenant. Yeah, there are some third party tools as well that serve to that function that can be configured pretty readily to do that. So you don't have to go through that download, upload, sort of process. Yeah, one that comes to mind that's not a partner of ours is a bit Titan, but I know that that's a little bit pricey. So that's something you can consider when you're looking for a tool. Okay, do you have anything else coming in here? All right, you're very welcome. All right. Was there anything else that we wanted to kind of add here, Michael? I think I'm pretty good to go. I know there's a lot to unpack here for folks. Yeah, and I, you know, it's, there is a lot to unpack. And also it's a very broad topic. And so, and there's, we could probably do an entire, you know, presentation on just one feature in, you know, or one thing within share points. This was sort of, we hope you got sort of a large, broad overview. And then it's partial curiosity to do a deep dive into any of these sort of subtopics that we discuss. All right. All right. So to that point, we want you to know that you're not alone in your journey and that we at TechSoup do have resources to help. Some of those items that you can see here in the presentation include the Microsoft Getting Started Guide, the Digital Transformation Forum, as well as Digital Skills Center training courses. Coming up next month, this is still a TBD. So I had to just kind of put that out there as to be determined. But these virtual office hours we do do every month on the topics do vary. I know that there's some other points that we want to hit in the future that spin off of SharePoint as well, such as Power Automate, part of the Power Platform. And we will get to those, but October's being worked on as we speak, when we do have that information, we will be getting that out to you all. We also have some additional resources that are going to be included in the slide deck that you all be receiving. As far as items such as scheduling a consultation with us, again, my email has been added to the chat, so you can feel free to contact me there. We do have a new platform that was built, a tremendous amount of work was put into it, and they did an excellent job, the Microsoft Product Recommendation Tool. So if you're just onboarding 365 or you have 365, you're not really quite sure if you're in the right license type, you can certainly use that. We have information on utilization requirements, so for those of you that are using Business Basic or Business Premium Donated Licenses, there is some information surrounding the Microsoft requirements for that, which will be accessed through the link. We also have another amazing tool which I spent quite a bit of time on to put together, it's a digital assessment tool that goes beyond the scope of Microsoft. That also ties in also to where our team and customer success comes in for technology road mapping, technology auditing, that is just a service that we do. You have, of course, the TechSoup product cloud, our product catalog, as well as a variety of additional blogs to help you along the way. So with that, we thank you for joining us, again, whatever time zone it is early, afternoon, late. This has been absolutely awesome. Huge fan, huge, huge fan of SharePoint, and having you, Michael, that was just icing on the cake. There's a tremendous amount of work that goes into our back end, and I think we might have missed IT Appreciation Month this past month, but you certainly, you and all the team there, have my appreciation. Again, for further follow-up, my team can be reached at customer success at TechSoup.org. And with that, we thank you and have a great day. Thank you, everybody. Thank you. Have a good afternoon. Bye-bye.