Get a first look at Restricted Content Discoverability for Copilot, the latest SharePoint Premium feature! Join me and Microsoft Principal Product Manager Sanjoyan Mustafi as we show how this tool helps prevent accidental data exposure, keeping sensitive content secure while still allowing users to stay productive. Learn how it works, see a live demo, and get answers to top community questions—all in one video!
Watch my 80+ courses on Pluralsight
Video Summary
- Introduction to RCD: Vlad and Sanjoyan introduce the new SharePoint feature, Restricted Content Discoverability, which helps prevent accidental data oversharing by ensuring sensitive content doesn’t appear in tenant-wide searches or Copilot queries unless recently accessed.
- Implementation and Demo: Vlad demonstrates how to set up RCD using PowerShell, explaining that once enabled, the site’s content is flagged to prevent it from appearing in broad searches. He shows how restricted content can still be accessed directly within the site.
- Behavior and Exceptions: They discuss how RCD works with recent files and direct references. If a user has accessed a file recently (within the last 28 days) or references it directly, it will still appear in searches, ensuring productivity isn’t hindered.
- Comparison with Other Features: The video compares RCD with the existing Restricted SharePoint Search feature, highlighting that RCD is more flexible and suitable for long-term use, while Restricted SharePoint Search is more of a temporary solution for testing and initial deployment.
- Q&A and Future Plans: They address various questions from the community, including licensing requirements, integration with sensitivity labels, and the impact on Copilot agents. Sanjoyan also shares insights into the future development and potential enhancements based on user feedback.
For more information, read the transcript blog below, or watch the video above!
Video Transcript
Hello everyone and welcome to this video, which is a first look at a new SharePoint premium feature called Restricted Content Discoverability for Copilot. This video, well, this feature is really hot off the press, so for this one, I will not do it alone. I am joined by somebody that’s been on the channel quite a few times now, Sanjoyan Mustafi. How are you doing, Sanjoyan?
Hey Vlad and hey everyone. Thanks for inviting me to your channel one more time. I’m doing awesome. Okay, so the reason we are here is because, well, about a month ago, you posted something on LinkedIn which kind of took everybody by surprise. So you did this post here: “As a SharePoint admin, are you concerned about data oversharing within your organization or are you hesitant to deploy Copilot? Basically, check out this new upcoming feature called Restricted Content Discoverability.” Everybody loved it, and you had 299 likes, by the way, so if anybody looks at the video, go on LinkedIn and give us that 300th like so we reach 300.
Also, I want to mention you see I’m number one here with the heart, so I was the first one to like it. But basically, in that video, as you can see, you had 47 comments, so you had a ton of different questions because it’s a brand new feature. It might have a bit of an overlap, and we’ll talk a bit about that with some other existing features. So a lot of people asked some great questions, so let’s try to clarify them for everybody.
But first, before we get into the Q&A, can you share a bit more about it? And I know you gave me a quick video because this feature can take a bit of time to implement. Let me add it here, and as it plays, explain to us what RCD does.
Sure, let us run the video and I’ll take you through. So we start by asking a very innocent question: “Is there any reorg happening recently?” It finds out a confidential document. Now, this is exactly what we don’t want. So as a SharePoint admin, I go and run this new cmdlet, which is set-SPOsite -RestrictedContentOrgWideSearch, and now you can see just after running, when the things go crawling is done, on your left-hand side for the same user, the outcome was you can see their content that was restricted content, and on the right-hand side, you do not see the content for the same user. Do note that the user can still go and access the content if they manually want to browse to the content and be productive.
However, what really we are doing here, Vlad, is we are preventing accidental discoverability. So let’s spend some time, Vlad, during this, you know, our conversation on two things which you mentioned very important. One, we have a whole lot of questions and curiosity against the feature. I can understand that, and again, thank you for inviting me. I will be happy to clarify, go through all your questions and our questions from our community, and answer them.
Well, for everybody, Sanjoyan was nice enough to give me access to the feature in a preview so I can actually go and play with it. And now he gave me the homework of trying to set it up in front of him and not make any mistakes. So we will do a bit of the cooking show in here just because some things take time to implement, but still, let’s try to see how it would work from A to Z. So first of all, what I will do is I will create a brand new site here.
Let’s just go for a very normal team site, standard team, and let’s call it Demo RCD. Let’s add Vlad as the group owner here. Perfect. And then let’s click on next. It will take one second to create, and I can already add Vanessa as a member here. Or let me try and do… I cannot add everyone except external users yet, but I want to have a bit of an over-shared site, you know, one of those sites that maybe not everybody should have access to it, but we’ll try and fix it.
So let me go to the site here, and again, I’ll try to make it super over-permissioned and add the infamous everyone except external user groups. That group is not available by default anymore, right, Sanjoyan? I think by default it is turned off on new tenants. By default, for any new tenants that are getting provisioned in our cloud, we do not surface that. For existing tenants, that is still available. Can I add it, or did you hide it? You probably hid it in my tenant. I was sure I enabled it, but anyway, I will just go… let’s add some more users here. We’ll add Alex as well, and it doesn’t matter. And then let’s go to the document so we have some… so Vlad, can you open the permissions? We have now three users in your site, but I think I added them to the group.
You know what, let me also share the site. Let me see if now does it show if I do everyone… no. So let me add Alex here as well. We’ll give them both permission only to the SharePoint site. So now I see here in addition, so now I know I have those users in here. Now let me go and let’s add some… let’s add some PDF files in here. Okay, so let me go, let me just find a few PDF files to get. Shouldn’t be too hard, or some PowerPoint files because this feature works with both PDF, PowerPoint, everything, right? Any file, Vlad, that’s a good question. Any file that is crawlable by SharePoint today, this feature is going to work on. Awesome. So I have a recent course that I was working on. I have different PowerPoint files. I will add them in here. This way we have everything.
There we go. M1, 2, 3, 4, 5. There, that should be enough. And of course, it will take a few minutes. Let’s see how fast the SharePoint index is now. No, it wasn’t this fast. I have to give it, you know, I tried. It will take a few minutes, but anywhere between five and ten minutes from now, this content will be available in SharePoint search and Copilot. But let’s say that this was now my super secret finance site, and I want to make sure that I cannot find this in Copilot. So what I have to do is, well, first of all, copy the URL, and then I’m connected to the SharePoint Online PowerShell module in here. Go to set-SPOsite -Identity, and then there is a switch called restrict access, restrict… what’s the… what’s the PowerShell? Restricted organization discoverability. If you just do tab, it should auto… oh, there we go. It was hiding from me. Restricted content, restrict content org search.
That’s why it got me, because sometimes some of them are restricted, some of them are restrict. And then I just say that it’s true. Is that it? Okay. Yes, that is that simple. That is it. And after that, I guess we’ll give it a few seconds, and then we can…
So, what is Vlad? I’ll take one moment to explain. Behind the scenes, this is setting up a property or a flag on the site object or the site collection in the true sense. Now, what we are doing is we are putting these flags in a synthetic way across all the files and folders of that site. The next time a user tries to do a search, either in Copilot or in SharePoint homepage or office.com, in any central location if they want to search, they will not see the content show up unless, of course, and this is a subtle point, and we will spend some time on this, unless they have accessed the file recently. We will talk more about what ‘recently’ means.
Awesome, okay, so now that I’ve done it, now it’s the part where we wait. I did my job, I double-checked, so I ran a get SPO site, selected the property, made sure that it’s applied. Good. This is the part where we wait, and this is one of the things I think we’ve both worked on SharePoint on-prem. It was kind of fun because I could always go run a timer job or do an IIS reset and it would apply instantly. Now, this is the part where we wait. But something that, once it takes effect, and of course, just to be able to show it to all of you in a demo, we actually had another site here called RCD demo that we decided to play with. In retrospect, I should have maybe uploaded some documents with a different name, but it’s okay. I’ll show it in the URL that it works.
So now if I go and I’ll just show before you start. Yeah, I’m just going to show the permissions in this site. You see I have Vanessa Lee that has edit permissions and Vlad that uploaded the documents that has full control. Great. Now if I go to just a Microsoft 365 homepage, I’ll search for here for M2. Let’s do show more results here as Vlad. Even if RCD is on that site, I do see the results because it’s one of the documents I recently modified. Well, I’ll have so many questions about what ‘recent’ means in just a few seconds. But if I go to Vanessa here, which Vanessa never opened this document but still, you see Vanessa has access to the library, the Sam 7 RCD.
I’ll search for EMP here, show more results. Vanessa does not see anything inside the tenant-wide search. But something that is really cool is that even if I don’t see anything in the tenant-wide search, I can still go to the site and if I search M2 over here, I find it. So with RCD, one of the cool things that I love, by the way, is that yes, we remove stuff from the tenant-wide search, but it still keeps it inside the site search that you have access to.
Now, the other part, which again, this is one of those things that can take time, and I learned it the hard way because I tried to do it too close to this demo. I should have maybe done my example a few extra days before because it’s not out of Copilot yet. So I’ll still show it because it’s a lesson learned for everybody. Be patient. Are there any files about internet speeds in the Sam 7 site?
Let’s see if Copilot can understand it. Yes, okay, so we did find it. I did not manage to see it in this site yet. It just takes time, but eventually, after the full site gets reindexed, that would not show up anymore. Is that correct? Correct. And something also that I tried to do, and then I was told it doesn’t work that way, you know, because I’m a SharePoint person, I was like, oh, I know how to fix it. Let me go to more library settings, let me go to advanced settings, and then let me go and request a reindex with this button. I thought that’s going to fix everything, but I learned it’s a site-level property, right?
So it’s not even if I reindex a document library, it will not take effect until the full site is indexed. Correct, correct, correct. You just need to give it a little bit of additional time, definitely not during this demo, but the expectation and the outcome, Vlad, that you pointed out is exactly the same, that in the Copilot also for Vanessa user, this document will not surface, but it already started working. So it worked very fast on the index, it just takes a bit more time for Copilot. And eventually, if we go back a bit to the video, the idea is, like you said here, Copilot will never leverage any document or any piece of information from a site that has RCD on, unless it’s a file that we have recently opened. And now I’m sure that’s like a bit, everything else is super clear for me, but I will need help.
All I know about recent documents is when I go here, I see recently opened, and I see files that I recently opened. So I guess are those the only files that will still show up in RCD and search, what into Copilot and search once RCD is on, or are there any other, you know, tips and tricks or things like that? That’s a very good question. Okay, and I would like to take some time to, you know, make this clear to our, you know, audience through your channel.
Permission to the site, like how you were trying to add everyone except it didn’t let me, so I guess that’s good, but I was trying. True, but you could have created a security group with, say, 100 users, and you definitely can add that, correct? Or all the company, like you know, I work for Microsoft, we have several very large groups which have like, you know, 100,000 people in it, okay? Like, you know, employees all across North America as an example. So let’s say you have done that by mistake.
You are the owner of the site. Now, I have nothing to do with the site, and I was just typing a query to do my work. Let’s say I was typing to find out about green energy or something that is a patent-pending work that Microsoft is doing. Because of somebody else’s mistake, it will now show up in my semantic query result by Copilot. So that is what the purpose of restricted content discoverability is, what it is doing. And you asked a question, what is the meaning of recent?
Okay, so say you are working on the file. When you access it in the last 28 days, it will show up in the recent tab. If you open Word, Excel, or PowerPoint, I believe all our viewers are pretty much aware, as you are showing on the screen in the web view also. If you open any document, it gives you a view of what files you’re working with recently and things like that. So we have a way to remember two things: A, you did visit a file, okay, and then B, you visited the file within a given time frame. What it proves to Copilot internally is that this is a file that you are using, and there is nothing accidental about it, okay?
You are using the file regularly, it is in your recent, and hence Copilot decides to show you the content from that, okay, to keep you more productive, which is, in our research, the 90% of the cases that happens. And then this 10% of the cases, people just stumble across content, okay? And they are, in our example, we gave the keyword, is there any reorg happening? What is the salary that should be good for a manager like me? I can ask that question too. So similar things, and then you get, you should not get an answer back from things that you do have access to but you are not supposed to have access to. And that is the distinction between a regular search result versus a Copilot search result. So I’ll stop for your question.
Sure, so one question I have for you. Let’s say I go on here, and then let’s say I just look. So as soon as I open it, I guess it’s there. If ever I see the file in search, so for example, if I go to normal search and I see the, let me go here, doesn’t matter, M2, I show more results. If I see the thumbnail in search or if I see part of it, does it count like a file I recently interacted with, or do I have to open it, or do I just have to know it exists?
“You need to, uh, two things. You asked a good question. It’s a combination of multiple things, Vlad, so it’s not a straight answer. You must need access to the F, so that is given. Assure short cases, if you open the file, it will be in your recent. That’s a very common way to get a file to your recent. The last way is if you are referring to the file directly. Let’s say, summarize content from the file and you give the full URL of the exact file, like from the site folder and then the file name and the exact file name, which means it is as good as you are opening the file and reading and then asking for the summary, which you can do today because you do have access to the file.
So, you know the presence of the file and you are giving a very pointed question, so that we will never suppress because you know where the file is. If I refer to it like this, if I do summarize this file, this will always work. This will even work with RCD on.”
“Oh wow, because you know the presence of the file, as I said. However, if you say, ‘Your M2 file, for example, has some chapter information on tuning the car’s engine,’ as an example. If you say, ‘Tell me more about car tuning,’ it can fetch information from many other documents but not files in this site because it is suppressed. But when you give a pointed question, ‘Tell me about car tuning from this specific document,’ which means you already know that there is a document. You could have pretty much opened the document, right? Because you took the pain of copying the URL, you could have. The idea is really to prevent people from finding files they have no idea they have access to.”
“Exactly, you said the right sentence. However, even with RCD on, let’s, uh, like, so maybe a follow-up question. So RCD will block me, like say I ask, ‘Are there any files about internet speeds?’ What if I only mention in the Sam 7 site? Will it still find it because I mentioned the site, or will it only find it if I pick the file or give it the exact URL?”
“If you give the exact URL, it will find it. But if you just put ‘from the Sam 7 site,’ it will not. That is vague enough, it should not. Because you said if you know you have access to the file, you can get to the file even with RCD on. If I go to this file here and let’s say I have Copilot, Copilot will still work in the document.”
“Exactly, you are 100% correct. So you are productive because you know the presence of the document. You have enough access to open the document, you have opened the document already. And now you could have read the document. Instead, you are asking help from Copilot. ‘Hey Copilot, can you summarize?’ ‘Hey Copilot, can you make this document better?’ RCD only applies in Biz chat, which is the name of the Copilot app, technical name I think is Biz chat, as you name it internally.”
“Correct. By the way, is it back to being Biz chat officially, or is that just an internal name?”
“We lovingly call it Biz chat. Today, I think the official name is M365 M or M365 chat.”
“I want to add one small thing, Vlad, which you said at the end for our viewers. The RCD feature works in any Copilot. The example is like this: in your example, suppose you have a document open. In the document, you are typing in the Copilot that appears inside the document, which is Office Copilot. So in the Copilot, you say, ‘Bring me all the information about green energy and write a paragraph in this document.’ So now Office Copilot is also doing a similar thing. It is going out and doing a semantic search across the knowledge base.
If that document is in another site, not this document, in another site, in another document which you do have access to but is suppressed by RCD or restricted content discoverability, then it will not show up. Because the pipeline or the funnel starts with our backend engine that covers any query coming from anywhere, unless of course you are querying on the given document which is already open, then all bets are off. But otherwise, it will work. It doesn’t matter which Copilot.
So as long as I’m in the document, it’s good. If I’m in the document in question, Copilot works. But if I’m in a brand new file and I say, ‘Create a summary,’ and then I search for M2, like say, ‘Oh, it didn’t find it,’ but if I reference the file directly, then it will work. But if I just say, ‘Create a document you mentioned about cars based on company data,’ and then I had a file about cars that was in an RCD protected site, then it would not work because Biz chat is going to go search the tenant. That site is not meant to show up in Biz chat or the company-wide Copilot. Then that will block me. But if I know the URL, if I’m in that document, so if I know about the file, it works. If I don’t know about the file, it doesn’t. That’s kind of the way to put it.”
“I totally agree with the way you have put it. If you know about the file and you have recently accessed it, if you know about the file, which means you can refer to the file directly or you have accessed the file recently. If you don’t know, then it should not work because you never used it, you don’t know.”
“And how long do you know? I’m sure there is an answer for how long is the recent. Let’s say I access it today and I access 50 other files today. At what point does it get kicked out of the recent files club?”
“I get this question a lot. It’s a complex logic. I would say just to keep it simple for the viewers, consider any number of files that you have accessed in the last 28 days. After that, if it’s one month and a half later, it will not show up in Biz chat unless I reference it directly.”
“Awesome, totally 100%. So I think I have a lot of my questions answered. But like I said, you had 40-something comments on that blog post. So let’s go take some of the community Q&A here. Give me a second and let’s see what are the popular questions that you received. The first one is, why did you build this? What motivated the development of this feature?”
“Fantastic question, and I love and admire people trying to understand what is going on behind the scenes and why we are introducing this kind of feature. The primary idea is Copilot is a per-user license, which means you buy Copilot and then deploy it to individual users. They start seeing the Copilot icon, they start clicking, and they can use Copilot in their daily life across various apps and things like that. When a customer is about to press the button to turn on Copilot for a given user, that admin needs to be confident that after doing that act, the user will not be in a state where they accidentally see data because of the way Copilot works today.
They accidentally see data which he or she is not supposed to see as an end user. The reason behind that is very simple. It’s because of how search works based on keyword match. You might have got a result set that did match but it was not on the first page, maybe it was on the fifth page and you never went to that page. However, because of this very fluid question and answer style, English-like communication that you have with Copilot, the information is now assimilated as knowledge in one piece and presented.
So there is no control, and then you may end up seeing those information light up in front of your eyes. This is the reason people are concerned. Our new feature, restricted content discoverability, gives peace of mind that once you apply that, then any… and we do not recommend applying it to all the sites because that will reduce the value of Copilot. The important point I remind all my customers is please do not apply this indiscriminately because you are buying Copilot to make your users more productive, ask those knowledgeable questions. If you don’t have the data to generate the knowledge, then there is no value in buying an expensive Copilot license. But there are some highly confidential content and documents that you are worried about, and yes, for correct reasons, RCD is meant for that.”
“Awesome. Now the next question is, and you’ve shared a bit of that as I was doing the demo, you shared a bit about how it works in practice. Can you share some of the extra implementation details? From what I understood, and you’ll tell me if I actually listened and did a good job, as soon as I executed the PowerShell commandlet, a trigger or property changes on the site. The next time the full search index runs, it sends a signal to Copilot, indicating not to look at that specific site anymore unless there are exceptions, such as recent files or direct mentions. Correct?”
“Yes, you are 100% correct,” the speaker confirmed. “Thanks for explaining this in a less technical way. I could have made it more complex.”
“Oh, we want the complex stuff, don’t get me wrong. I love to learn the complex stuff, but I know you can talk about it for a day.”
“I admire that. I’ll provide some more details. As you explained, you enter a prompt. First, we analyze the prompt to understand what you’re asking for, convert that into a query, and then perform a search across the index of all files. We fetch a set of files and give them to the large language model to create a summary. Just before we provide these files to the model, we run a filtering logic to check if there are any restrictions on these files from the sites. If we find that a file, like M2, comes from a restricted site, we reduce the set of files accordingly. If we reduce the set too much and there’s nothing left to give to the LLM, we fetch more files until we have a good set to provide a meaningful answer.”
“Wow, that’s a lot more complicated than I thought it would be, but it makes so much sense. Awesome.”
Now, I’m sure the other question that you get a lot is, “Do I need a SharePoint premium license to try out this feature?” Yes, the answer today, as of now, is that you will need a SharePoint premium license. I highly encourage our users, through your channel, to at least get a free trial license. If you are an enterprise, you can always talk to your Microsoft representatives locally and ask for extensions and things like that, but do give it a try and see how it works out for your scenario. More licensing announcements are coming later this year, so do stay tuned.
If you’re an IT Pro like me who just wants to practice it for your clients, you can just go in the billing marketplace, start 28 days, you get 25 licenses to play with it, and after that, even without a CSM or being a big company, you can extend it for another 30 days. So, even if you’re just an IT Pro wanting to try it out for your clients, you can get 60 days of it for free and run demos and things like that, which is kind of cool.
Since you answered the question about licensing, how does this differ from the existing SharePoint restricted or restricted SharePoint search feature? I copied this from LinkedIn, which doesn’t need additional licensing. For those of you who don’t know about restricted SharePoint search, I’ll do a quick summary in 30 seconds. It basically lets you set an allowed list of up to 100 sites in your tenant, and Copilot only lets you query or the Copilot engine will only look at those up to 100 sites for any answer. SharePoint search will also only work on up to those 100 sites, so you’re limiting both search and Copilot to an allowed list of up to 100 sites.
Thanks, Vlad, for that. You explained it quite well. Restricted SharePoint search, or RSS as we call it because it’s a mouthful, is basically a very small allow list where you make your Copilot intelligent on those 100 sites that are in the allow list. Your Copilot is as intelligent as the content in those 100 sites you trust. We have that feature for customers who are very early in their lifecycle of using Copilot. They just want to test the waters, and once they are satisfied enough with the results for Copilot, they want to expand. At that point in time, they can lift the restrictions or remove that allow list and then expand.
On the other side, some of our customers tell us that their knowledge base is spread across many hundreds and thousands of sites. To narrow it down to a hand-counted number of 100 sites is not easy. They ask what they should pick and what they should not pick, and their corporate users will complain that some knowledge base is not coming. It’s difficult to choose. What they can do is mark content that should not be picked up by Copilot for regulatory reasons, compliance reasons, or trade secrets. This leads to the idea of a deny list, which a customer can create. When a customer marks a site with restricted content discoverability, they are creating a kind of deny list. This list can expand to all sites, so there are no restrictions like the former. However, please use it with discretion, as you will kill Copilot or the benefits of it.
Next, does this feature also mean that content excluded from Copilot with RCD is also excluded from the SharePoint search results? We kind of covered it throughout the demos, but let’s still take the question. The short answer is yes, it is excluded because search via Copilot and search via SharePoint or office.com or in Teams, etc., are the same. The backend engine is the same. However, as you already discussed, if you are within that site, you can search in the site but not in SharePoint search. It impacts both Copilot and SharePoint site results unless you are within the site. It impacts tenant-wide stuff, not site-wide stuff.
With the upcoming Copilot agents in SharePoint, can I still create a Copilot agent based on those files if the site is RCD protected? That is a fantastic question. When I see you next time, Vlad, I’ll buy you coffee or beer for asking this question. I’ll take both. Copilot agent is a new feature that Microsoft SharePoint is launching very soon. It captures local intelligence and you can share it with others. However, if a site is marked with RCD, you cannot create a new Copilot agent for that site. If you already had a Copilot agent created on the site prior to configuring this restricted setting, that agent will continue to work. It can fetch content from the site, but if you refer to another site with restricted content discoverability, it will not show up.
Are there any endpoints or applications that do not filter out content with RCD applied? This is a very interesting question. The way Copilot works is by providing personalization. For a regular lexical search, if you and I both have the same access, we will both get the same answers. For Copilot or large language model-based querying, it is different based on your personalized information. Your personalization as an end user comes from your OneDrive, where you have your personal stuff. You cannot apply restricted content discoverability on OneDrives. If there is a file in OneDrive, that file will be considered by Copilot for grounding purposes. The entire OneDrive site cannot be suppressed using restricted content discoverability.
Another aspect is what we call recent documents or working set. This is a virtual set that we maintain per user, which you have accessed in a given tenant in the last 28 or 30 days. Since you did access them, that content will still continue to surface because the model figures that this is something you are using regularly. It will not suppress that. So, no OneDrive for Business and no recent documents.
Does RCD affect site access permissions? This question comes up a lot. It does not impact your end user access at all. If you had access, all your links will work, all your sharing links will continue to work, and all your productivity will continue to work. The only difference your end users will notice is that content from a restricted site will silently go away from their search results. It should not make any customer user impact because if they have access to it, they can still go to it. If you want to change access permissions, that’s where restricted access control, another SharePoint premium feature, comes in. It doesn’t change access permission but acts more like a conditional access policy. If your goal is to suppress visibility in search and Copilot, do RCD. If your goal is to restrict access and suppress content from Copilot, use the new control called restricted access control.
Awesome, okay next up, really interesting question: Can this be configured as part of a container sensitivity label? Who sneaked this question in? Glad, did you do this? Or this is a… I can give you names, like I can give you names. Okay, so this is a very interesting question. As of now, the answer is no, we do not attach this to container sensitivity labels yet. But we will see if there is a demand from several of our customers. We will, you know, add this to our roadmap. We are just launching this feature, Vad, as you are aware. We are going to announce G soon, so we’ll see how the market reacts to that.
Awesome, and this is it for the questions, but I have one more thing here hidden in the slides for you: Copilot vs. Copilot. For how long have you worked with SharePoint, Sanjoyan? Do you remember how many years of SharePoint experience you have? I believe, uh, 8 years now in SharePoint. 8 years now in SharePoint. Well, I can see that you got into the habit of capitalizing the P, because there are some comments on there on LinkedIn. I think you put “Cop” with a capital P on the “Copilot” and I had to show you Laurian, who is always known to call out everybody when they spell SharePoint wrong without the capital P.
Well, this time you did the capital P but at the wrong spot, so there are some funny comments there about “Copilot” with, you know, it’s also Microsoft marketing, you know, SharePoint capital P, Copilot no capital P. So remember that everyone. This is so funny, and I do accept, yes, I did SharePoint with the capital P, but that’s okay. It’s the Copilot that’s no capital P. Microsoft marketing never makes it easy on us when they find the name of the products. They’re like, how do we make it that people are gonna make a mistake and get laughed at on LinkedIn? It’s always like that.
But thank you so much, Sanjoyan. I know this took a lot longer than we initially planned, but there is so much good information there to share, and I really appreciate you taking an hour of your time to share your knowledge with people on everything that is coming up. So, thank you, thank you, thank you so much. And for everybody else, if you enjoyed, make sure you put it in the comments, like the video, subscribe to the channel, and share it with everybody. This way, Sanjoyan comes back on the channel for the next cool feature. So thank you so much, everyone, and talk to you soon. Bye. Bye.
