Microsoft 365 Copilot Without the Hype: Adoption, Governance & Getting Your Tenant Ready with Paul Keijzers [MVP]
Key Takeaways
- Microsoft 365 Copilot readiness goes beyond simply buying licenses and requires a deep review of existing data foundations like SharePoint, Teams, and OneDrive.
- Over-sharing is a major risk when deploying Copilot, as the AI will surface any content, including outdated files and sensitive data, that users already have permission to access.
- Effective information architecture, including sensible folder structures and limited metadata fields, remains crucial for ensuring Copilot returns accurate and relevant results.
- Organizations must look beyond basic technology deployment and implement ongoing adoption strategies, regular prompt tips, and agent management to truly save time and improve productivity.
- Tools like Microsoft Purview for sensitivity labeling and Power Automate DLP policies are essential components for protecting sensitive information before rolling out Copilot.
Microsoft 365 Copilot can help people find information and get work done faster, but its answers depend on the content and permissions already in an organization’s Microsoft 365 tenant. In this episode of the M365 FM podcast, Mirko Peters speaks with Microsoft MVP Paul Keijzers, founder of KB Works, about preparing Microsoft 365 for Copilot in a practical, responsible way. They look beyond demos and licensing to the foundations that shape Copilot results: SharePoint, Microsoft Teams, OneDrive, data quality, access controls and governance. Copilot can make existing access issues more visible. Files that have been shared broadly, outdated documents, old versions and content with unclear ownership may all affect what employees can find. Paul explains why organizations should review their sharing settings and understand where sensitive or unnecessary access exists before rolling Copilot out widely. SharePoint oversharing reports can help identify potential issues across SharePoint, Teams and OneDrive, although organizations still need to check whether flagged sharing is appropriate for their business.
GOVERNANCE, LEGACY DATA AND INFORMATION PROTECTION
The conversation explores how to manage years of legacy SharePoint content. Old project files may need to be retained for legal or business reasons, but that does not always mean they should appear in everyday search or Copilot results. Organizations can consider archiving content or restricting access, depending on how often it needs to be used and how the tenant is structured. Paul also highlights the need to plan for Microsoft 365 backup and recovery, including how a company can retrieve its data if it changes backup providers. Microsoft Purview is part of the wider governance picture. Paul recommends reviewing sensitivity labels, checking whether they are applied consistently, and considering automatic labeling where appropriate. Data Loss Prevention policies can help protect personal and sensitive information, while Power Automate DLP policies need attention when Copilot uses connectors to work with services such as Jira. These controls should fit the organization’s actual needs, since a global company and a small business may require different policies.
SHAREPOINT STRUCTURE AND COPILOT ADOPTION
Good information architecture remains important even as AI becomes better at understanding natural language. Paul discusses using metadata and content types to make information easier to organize and retrieve, while keeping SharePoint libraries practical for employees. His guideline is to avoid overly deep folder structures and excessive metadata fields, since people are less likely to maintain a system that is too complicated. Copilot can help suggest or populate information, but organizations still need a clear structure and reliable content. Copilot adoption also requires ongoing support. Rather than delivering a single training session and expecting employees to figure out the rest, organizations can share regular tips, demonstrate useful prompts and agents, and help teams solve real daily frustrations. Paul recommends starting with the work people actually do, then identifying where Copilot could save time or improve an outcome. Adoption plans should be adapted to the size and working practices of each organization instead of copied wholesale from a framework designed for a different environment.
AI VALUE, AGENTS AND A PRACTICAL PATH FORWARD
Mirko and Paul also discuss how organizations can assess the value and cost of AI, how agents may increasingly work alongside employees, and why administrators need ways to discover and manage agents in their environments. Paul shares his Focus Week concept in Portugal, where teams spend dedicated time working on Microsoft 365, SharePoint, governance or Copilot challenges away from their usual workplace interruptions. The central message for IT leaders is that Copilot readiness starts with understanding the Microsoft 365 tenant: who can access what, how information is organized, which content should be retained or surfaced, and how employees will learn to use AI in their work. Review sharing settings, improve information governance and connect adoption to real business needs before treating Copilot as simply another license to deploy.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-a-microsoft-mvp-podcast-by-mirko-peters--6704921/support.
🚀 Want to be part of m365.fm?
Then stop just listening… and start showing up.
👉 Connect with me on LinkedIn and let’s make something happen:
- 🎙️ Be a podcast guest and share your story
- 🎧 Host your own episode (yes, seriously)
- 💡 Pitch topics the community actually wants to hear
- 🌍 Build your personal brand in the Microsoft 365 space
This isn’t just a podcast — it’s a platform for people who take action.
🔥 Most people wait. The best ones don’t.
👉 Connect with me on LinkedIn and send me a message:
"I want in"
Let’s build something awesome 👊
Frequently Asked Questions
What happens when you deploy Microsoft 365 Copilot without checking permissions?
Copilot can inadvertently surface sensitive or outdated information, such as salary data or legacy project files, that was previously hidden in deep SharePoint or Teams structures simply because users technically have access to it.
How can organizations handle years of legacy SharePoint data before using Copilot?
Companies can archive old files that no longer need everyday access or restrict Copilot from accessing specific legacy content so it does not interfere with daily search and AI results.
Why is metadata still important for Microsoft 365 Copilot?
While AI is great at understanding natural language, having a clear SharePoint structure with well-maintained metadata and content types helps organize information and ensures Copilot retrieves accurate data.
What is the best way to drive Microsoft 365 Copilot adoption?
Successful adoption relies on continuous support, sharing regular tips, demonstrating useful prompts and agents, and aligning Copilot use cases with the real daily frustrations and workflows of employees.
00:00:00,000 --> 00:00:06,040
Yeah, welcome back to another episode of the MC65 as a podcast.
2
00:00:06,040 --> 00:00:12,400
Today we are talking about one of the biggest questions facing Microsoft 365 organizations
3
00:00:12,400 --> 00:00:14,640
right now.
4
00:00:14,640 --> 00:00:21,200
Are you actually ready for co-pilot because buying license is easy, but what happens
5
00:00:21,200 --> 00:00:31,840
when co-pilot suddenly has access to years of SharePoint sites, TeamsCon version conversations,
6
00:00:31,840 --> 00:00:36,880
documents, permissions, language, the content and information that perhaps should never
7
00:00:36,880 --> 00:00:39,320
have been shared in the first place.
8
00:00:39,320 --> 00:00:42,280
My guest today is Paul Kiosz.
9
00:00:42,280 --> 00:00:48,360
A time Microsoft MVP and founder of KB Works, Paul has spent more than 20 years in the
10
00:00:48,360 --> 00:00:57,360
Microsoft ecosystem helping global organizations improve the way they use Microsoft 365 from
11
00:00:57,360 --> 00:01:03,560
SharePoint and Teams architecture to security, Microsoft, PUE, View, governance and co-pilot
12
00:01:03,560 --> 00:01:04,560
adoption.
13
00:01:04,560 --> 00:01:10,320
His focus isn't simply on the deploying technology, it's about turning Microsoft 365 and co-pilot
14
00:01:10,320 --> 00:01:14,200
into something organizations can actually measure.
15
00:01:14,200 --> 00:01:17,640
His waste time, better productivity and lower risk.
16
00:01:17,640 --> 00:01:23,800
Paul also runs an intensive focused weeks in Portugal where customers work directly with
17
00:01:23,800 --> 00:01:31,560
him on some of their thoughtless Microsoft 365 and co-pilot challenges.
18
00:01:31,560 --> 00:01:35,800
So today we are going beyond co-pilot demos.
19
00:01:35,800 --> 00:01:42,720
We are talking about what happens before co-pilot arrives by co-pilot fails, where oversharing
20
00:01:42,720 --> 00:01:49,200
becomes dangerous, how PUE View fits into the picture and how organization can prove whatever
21
00:01:49,200 --> 00:01:52,400
it's actually the lower value.
22
00:01:52,400 --> 00:01:56,800
Paul, welcome to the LCC-65FM podcast.
23
00:01:56,800 --> 00:01:58,120
Thank you, thank you.
24
00:01:58,120 --> 00:02:01,000
It was a big introduction.
25
00:02:01,000 --> 00:02:06,480
I'm not used to such a big introduction, yes.
26
00:02:06,480 --> 00:02:08,480
Thank you for inviting me.
27
00:02:08,480 --> 00:02:10,440
Yeah, Paul, it's amazing.
28
00:02:10,440 --> 00:02:15,560
You are working around 20 years in the Microsoft ecosystem.
29
00:02:15,560 --> 00:02:20,520
Where did your journey organically start?
30
00:02:20,520 --> 00:02:25,520
Well, my first start was actually not in IT.
31
00:02:25,520 --> 00:02:30,280
I was 21 when I started and it was in Card Audio.
32
00:02:30,280 --> 00:02:40,360
So you know, those big boom boxes around the road in the early 2000s or even earlier.
33
00:02:40,360 --> 00:02:47,800
Where people had big boxes, that's where I started and I started my own company in that.
34
00:02:47,800 --> 00:02:54,200
But after like three, four years it was hard because the innovation became better for
35
00:02:54,200 --> 00:02:55,280
the cars.
36
00:02:55,280 --> 00:03:04,880
So then I had to move along and then I started at an insurance company where I was just
37
00:03:04,880 --> 00:03:16,160
doing manual work and they saw, hey, you have some, how do you say that, feeling with IT.
38
00:03:16,160 --> 00:03:18,600
So don't you want to work for our department?
39
00:03:18,600 --> 00:03:20,440
Okay, I want to.
40
00:03:20,440 --> 00:03:23,640
And that's where the journey started.
41
00:03:23,640 --> 00:03:30,400
After a while they had to reorganize, so I had to go and then I went to another IT company
42
00:03:30,400 --> 00:03:40,160
and that was in 2001 when I first touched the SharePoint ecosystem.
43
00:03:40,160 --> 00:03:51,600
So I was doing VBA and lots of people with branding and then SharePoint came along and the
44
00:03:51,600 --> 00:03:55,840
first steps were only like versioning.
45
00:03:55,840 --> 00:04:05,120
So just check in, check out, that was it and it was still buggy but it was a good first
46
00:04:05,120 --> 00:04:06,600
step.
47
00:04:06,600 --> 00:04:14,800
And after that I went to several other companies and in 2007 I really picked up again my own
48
00:04:14,800 --> 00:04:23,560
company but different name of course, but really into SharePoint and then I did some migrations
49
00:04:23,560 --> 00:04:33,440
of 2003 to 2007 and that's where I really started to feeling with SharePoint and do some more
50
00:04:33,440 --> 00:04:44,880
coding on that and the web parts and I did some things for big education schools there
51
00:04:44,880 --> 00:04:53,520
and then in 2010 and I 2009 I went to the first or no it was a second.
52
00:04:53,520 --> 00:05:01,320
And then I got to the SharePoint conference in Las Vegas and that's where I met a lot of
53
00:05:01,320 --> 00:05:08,360
people and I even got more hooked to SharePoint and also the community because it's, SharePoint
54
00:05:08,360 --> 00:05:19,320
has a really great community and then later on I went to a big bank also for my own but
55
00:05:19,320 --> 00:05:31,120
I did do a lot of internet parts and at the time SharePoint 2010 and then we got BayPos
56
00:05:31,120 --> 00:05:43,520
around 2011 to 2012 I think which is originally the name of Office 365 so they renamed it, rebranded
57
00:05:43,520 --> 00:05:51,680
well as we know every year there's a rename of products and after that I went more and more
58
00:05:51,680 --> 00:06:03,040
into the clouds and then in 2016 I got the first time MVP awards and at that time I was
59
00:06:03,040 --> 00:06:13,160
working with Wurthel, Microsoft Partner, a very nice company as well but that was a time
60
00:06:13,160 --> 00:06:21,360
that I was working for them not for my own and I fully focused on Microsoft Teams at the
61
00:06:21,360 --> 00:06:31,800
time which was brand new in 2017 so lots of work in there and especially what we see now
62
00:06:31,800 --> 00:06:38,800
and still see is the way they set up for example their storage which is still in the background
63
00:06:38,800 --> 00:06:48,520
SharePoint so that's what I did a long time, a focus on Microsoft Teams especially because they
64
00:06:48,520 --> 00:06:58,080
improved a lot during the years and you see more usage and then actually late when it was
65
00:06:58,080 --> 00:07:06,600
it, well when co-part it came out I directly, I was at the at the different bank working and they
66
00:07:06,600 --> 00:07:16,200
were Early Access Partner so then I had the chance to jump on the wagon and go along with
67
00:07:16,200 --> 00:07:24,680
the co-pilot Early Access so that was really a very good start for me and yeah and at that
68
00:07:24,680 --> 00:07:34,360
time I took all the knowledge I could of co-pilot with me but a lot has changed since then of course
69
00:07:34,360 --> 00:07:41,080
because it was also the first versions and everybody was searching okay how do we implement what do we
70
00:07:41,080 --> 00:07:52,040
need to take care of and yeah basically a lot of companies use it for outlook still because it's
71
00:07:52,040 --> 00:08:00,040
easy to use in outlook but lately we see how do you say that something coming back is SharePoint
72
00:08:00,040 --> 00:08:07,400
and people are using more and more SharePoint although some don't even know that but they are
73
00:08:07,400 --> 00:08:16,280
and lots of Office 365 components are really built on SharePoint and that's something not a lot of
74
00:08:16,280 --> 00:08:24,040
people know. Most people think it's just a server-like environment but a lot is hosted within the
75
00:08:24,040 --> 00:08:33,800
SharePoint environment so it's really important to have your governance up to date there and especially
76
00:08:33,800 --> 00:08:42,600
you already mentioned it in the intro when you take a look at your file storage and there's not
77
00:08:42,600 --> 00:08:51,720
a lot changed to be honest since 2016 when Delph came out because I don't know do you know Delph?
78
00:08:52,680 --> 00:08:56,760
It's not I never really worked with it I only hear this.
79
00:08:56,760 --> 00:09:05,240
Okay maybe I explain a little bit about that because lots of people think it's only the
80
00:09:05,240 --> 00:09:13,080
governance got really important when co-pilot came out but it was already in 2006 actually when
81
00:09:13,080 --> 00:09:21,240
you start a project it's already important but most people didn't care about it but now with co-pilot
82
00:09:21,240 --> 00:09:33,080
it surfaces easier but when Delph came out Delph is made by the craft team and it was made to
83
00:09:33,080 --> 00:09:43,000
let people see what are other colleagues working on so when you would share something with the
84
00:09:43,000 --> 00:09:51,800
organization it would surface up into the to Delph so you would already see it but most people didn't
85
00:09:51,800 --> 00:09:59,880
care of it or they shut down Delph because Delph was if you turned off Delph you would also turn off
86
00:09:59,880 --> 00:10:14,600
graph so problem gone but that was like just an easy thing to do but later on during the years more
87
00:10:14,600 --> 00:10:21,800
and more services were accessible via graph so then you had to make a decision okay do we keep Delph
88
00:10:21,800 --> 00:10:29,720
off or are we going to do Delph and then even in the mid-time there was a switch for a graph
89
00:10:30,200 --> 00:10:39,240
so then you could change a lot of things but with co-pilot now it's really like it's surfacing so
90
00:10:39,240 --> 00:10:45,880
people try to query it and you don't want to turn off co-pilot because that's what the business
91
00:10:45,880 --> 00:10:52,840
wants so now it's not that easy as in within Delph where you just turn off the knob and then it was
92
00:10:52,840 --> 00:11:07,400
gone now you have to be careful and what I see in daily life so to say yeah that's cool
93
00:11:07,400 --> 00:11:16,440
they're directly dive into co-pilot so I think Microsoft co-pilot looks
94
00:11:16,440 --> 00:11:24,360
incredibly simple for from end user perspective you open an application type or prompt get an answer
95
00:11:24,360 --> 00:11:32,440
but behind the simple interface there's enormous amount of Microsoft 365 info structure
96
00:11:32,440 --> 00:11:38,840
what are companies underestimated when they start with their co-pilot journey
97
00:11:41,160 --> 00:11:50,680
well as I already a bit told in the in the earlier stages they forget about permissions they forget
98
00:11:50,680 --> 00:12:04,120
about retention they forget about a DLP they forget about the labeling aspect so when they start off
99
00:12:04,840 --> 00:12:14,840
and some take it seriously so it's not all bad but a lot of companies just take off they buy some licenses
100
00:12:14,840 --> 00:12:24,840
co-pilot they start and they they see that some data is there but they don't care till there's something like
101
00:12:24,840 --> 00:12:33,720
how do you say that salaries that's coming up and people may not know it or something else that comes
102
00:12:33,720 --> 00:12:41,480
up because it was shared with the whole company so basically the first setting I always look at is
103
00:12:41,480 --> 00:12:53,080
the how the sharing is configured so if it's new guests and guests or is it allow everyone which is
104
00:12:53,080 --> 00:13:00,280
mostly used in a new environment or small companies because they just don't know it
105
00:13:01,880 --> 00:13:08,840
so that's that's the start where where I always look and then I have to talk to them and see what
106
00:13:08,840 --> 00:13:17,480
what they really need and if they really want everyone to be part of this sharing experience
107
00:13:17,480 --> 00:13:26,520
so I think that's the the the first start that's going well where there's problems let's
108
00:13:26,520 --> 00:13:34,200
put it that way and they surface once they start with co-pilot and not when they just you share
109
00:13:34,200 --> 00:13:40,360
search it doesn't yeah you can still find it but it's hard let's put it that way
110
00:13:40,360 --> 00:13:50,680
awesome I think we have to talk or we have to look more into the Microsoft 365 tunnel
111
00:13:51,720 --> 00:13:58,520
not only at the co-pilot so what does the co-pilot run in ready tenants actually mean for you
112
00:13:58,520 --> 00:14:12,040
oh a co-pilot is ready 10 means that the at least your data structures and labels
113
00:14:12,040 --> 00:14:21,400
the DLP is in order and even further which is not my expertise area but like in
114
00:14:21,400 --> 00:14:29,000
June defender you all have to set it up because I think when you are going to work with a product like
115
00:14:29,000 --> 00:14:37,000
this you want to have everything correctly in place and of course you can skip the defender
116
00:14:37,000 --> 00:14:45,240
and the in-tune part but still it's I think is very very important especially the bigger the company
117
00:14:45,240 --> 00:14:53,560
the more problems that arise there and that it's not my expertise there so that's why I say this but
118
00:14:53,560 --> 00:15:01,800
I think that there are many people who know a lot about this as well yeah I think what's one of
119
00:15:01,800 --> 00:15:08,840
your topics is SharePoints so and I think many organizations have been running SharePoint for 10 15
120
00:15:08,840 --> 00:15:22,040
or even 20 years what happened when co-pilot meets the all this historical content and how to avoid
121
00:15:22,040 --> 00:15:30,680
the the broad problem with co-pilot from your perspective yeah I see that as well that companies
122
00:15:30,680 --> 00:15:38,760
that are using like from 2013 onwards or even earlier but then migrated to SharePoint on
123
00:15:38,760 --> 00:15:51,720
line that files are old so files that are not archived or the still there are lots of and this is
124
00:15:51,720 --> 00:16:01,320
really important you know there are lots of files that are just migrated from a file several in 2010
125
00:16:01,320 --> 00:16:10,040
I don't know it doesn't matter but it's all data but it's not archived and it's got like version number one
126
00:16:10,040 --> 00:16:18,200
version number two no made the data anything and what co-pilot does it just looks at the data
127
00:16:18,200 --> 00:16:25,400
so when you query something and it finds that file of 2010 version one but you also have a version
128
00:16:25,400 --> 00:16:35,800
13 or 30 it will check both documents or files and then it will surface it if it's correct that's
129
00:16:35,800 --> 00:16:45,960
on to you but this problem is one of the big problems at the moment that companies start to use
130
00:16:45,960 --> 00:16:54,920
the co-pilot they think they only have the correct data but also the data the data may seem correct
131
00:16:54,920 --> 00:17:03,880
but if it's old versions you can still not use it and then it looks like co-pilot is hallucinating
132
00:17:03,880 --> 00:17:14,440
but it's not it's purely on your own data I think in Germany we have yeah we have when we start
133
00:17:14,440 --> 00:17:24,520
the project we all data we have yeah have stay for for the next 10 years so it's for the documentation
134
00:17:24,520 --> 00:17:35,160
it also means we have this to yeah if the the last from close projects for yeah
135
00:17:35,160 --> 00:17:44,920
well that's data from from the last 10 years so what's the best way to to to handle this year
136
00:17:44,920 --> 00:17:53,080
old projects or old data that that must say in in the company
137
00:17:54,200 --> 00:18:02,200
yeah it depends on how how many times this data still needs to be accessed because if it doesn't
138
00:18:02,200 --> 00:18:09,240
need to be accessed anymore it still needs to exist you can archive it within the Office 365
139
00:18:09,240 --> 00:18:17,880
suite and then it doesn't surface in the co-pilot but you could also restrict it from co-pilot to get
140
00:18:17,880 --> 00:18:25,720
access to it so if you restrict it it will not show up in in the co-pilot results so there are
141
00:18:25,720 --> 00:18:34,840
several ways to do this and of course it's depending on how the site structure is because what I also
142
00:18:34,840 --> 00:18:42,200
see is you say okay we have data we have to keep it 10 years but we just go on in the same site we
143
00:18:42,200 --> 00:18:50,600
just build our our complete folder structure and then we call it the different year and that's
144
00:18:50,600 --> 00:18:57,640
that's a harder part because then you really have to check okay we can archive sites but on file
145
00:18:57,640 --> 00:19:04,280
level it's it's a bit different and you have to check okay how are we going to do that and what do
146
00:19:04,280 --> 00:19:13,400
we really want to surface in in co-pilot or search because for me co-pilot is still like search it's
147
00:19:13,400 --> 00:19:23,240
only you give it a normal speech but it's still like search for me yeah that's interesting so
148
00:19:23,240 --> 00:19:31,560
I think a lot of companies say oh storage it's it's cheap let let keep let keep everything here but
149
00:19:32,840 --> 00:19:40,040
what or how do you say or what's the best practice for for content lifecycle management
150
00:19:40,040 --> 00:19:48,520
for co-pilot readiness from your perspective I think it really depends per company because you
151
00:19:48,520 --> 00:19:56,280
cannot say okay this works for this company and this works for this company because for example
152
00:19:56,280 --> 00:20:03,720
you say storage is cheap but I'm not agreeing on that because I think the storage is still
153
00:20:03,720 --> 00:20:11,560
very expensive on SharePoint actually so you would need to check depending of course of the size of
154
00:20:11,560 --> 00:20:21,960
your of your company but I would even look into blob storage for example or use the office 365 backup
155
00:20:21,960 --> 00:20:30,600
or use a third party tool that you that backup your data on a on a blob storage and
156
00:20:30,600 --> 00:20:39,480
talking about backup it's really important that you have a backup partner that backup your data
157
00:20:39,480 --> 00:20:48,280
but also restores it that's one but the other one which all companies forget is what if I want to
158
00:20:48,280 --> 00:20:58,840
leave this third party to another third party what is going to happen to my backup and I was a bit
159
00:20:58,840 --> 00:21:06,840
surprised by some companies that have like really high fees to get your own data back so this is
160
00:21:06,840 --> 00:21:15,720
something you have to look out for I think it's really important to look at that I think a
161
00:21:15,720 --> 00:21:25,160
melatopic a lot of companies talking about it's it's oversharing how how how will you define
162
00:21:25,160 --> 00:21:33,160
oversharing and what did you think is the biggest source of yeah of oversharing is it's a SharePoint
163
00:21:33,160 --> 00:21:41,560
is a team is one drive by so that my across of 365 groups or what did you think it depends I think it's
164
00:21:43,320 --> 00:21:53,320
I think it starts by looking at your settings if if allow everyone is on for example which is the
165
00:21:53,320 --> 00:22:01,480
base one yeah then you you have a big chances of oversharing especially on the SharePoint side
166
00:22:01,480 --> 00:22:10,280
and I think when you look now when you have one copied license you also have this advanced
167
00:22:10,280 --> 00:22:17,320
dashboard in the SharePoint admin center where you can get your oversharing reports and they give you
168
00:22:17,320 --> 00:22:27,480
good insight on how your sites are used and where the oversharing is taking place it sometimes it
169
00:22:27,480 --> 00:22:38,280
may not be correct in in the way it's rational so it sees that it's overshared but sometimes this
170
00:22:38,280 --> 00:22:44,840
can be for example I know some companies that use it for marketing data they just share it with
171
00:22:44,840 --> 00:22:53,720
other companies and then it's shown as oversharing but it's actually not it's it's just the way it's set up
172
00:22:53,720 --> 00:23:01,640
but yes this these reports really give you a good insight on on the sharing and where it's taking
173
00:23:01,640 --> 00:23:10,520
place and this is done across because SharePoint is the base it's done across the the teams the one
174
00:23:10,520 --> 00:23:19,960
drive and SharePoint so there's no no reason not to look into that I think when you when you when
175
00:23:19,960 --> 00:23:27,560
you have a copied license check into that I even sometimes say to companies if you only have one
176
00:23:27,560 --> 00:23:35,960
copied license you already get this extra features so that could be worth it for a whole company
177
00:23:35,960 --> 00:23:46,040
especially if it's a big company yeah I think one of the yeah Microsoft tools that that helps it's
178
00:23:46,040 --> 00:23:56,120
a peer view absolutely yeah peer view it's it's I don't know what's the right thing peer view
179
00:23:56,120 --> 00:24:08,280
modules solutions there are so many there's the information protection the DLP the DSPM the data
180
00:24:08,280 --> 00:24:15,480
lifecycle management you discovery compliance manager and the data governance we fight catalog
181
00:24:15,480 --> 00:24:24,920
what are important for for for co-pilot when well what what did I have as minimum
182
00:24:24,920 --> 00:24:34,200
requirement to look then into QVU well I do some peer view but I don't do all the per view but
183
00:24:35,000 --> 00:24:41,800
I think for copilot it's important to look at the labels so what do the labels say
184
00:24:41,800 --> 00:24:50,120
and have you set up the labels that's the first question of course and if you have set it up if
185
00:24:50,120 --> 00:24:58,200
is it applied do you have auto labeling on or not I think that are the basics on SharePoint side
186
00:24:58,200 --> 00:25:06,280
but on DLP and then we are talking first per view is like personal information like
187
00:25:06,280 --> 00:25:12,760
and that's also depending on which company because if it's an international company you have a lot
188
00:25:12,760 --> 00:25:22,680
of DLP policies but if it's like a ditch company or a German company you know okay no credit cards no
189
00:25:23,640 --> 00:25:30,360
physical numbers that kind of stuff you don't want to share it out that's what DLP can do but there's
190
00:25:30,360 --> 00:25:37,320
one thing that a lot of people again miss and it's not on the per view side it's more in the power
191
00:25:37,320 --> 00:25:45,720
automate side and that's the DLP on the power automate side because when you use copilot and you
192
00:25:45,720 --> 00:25:55,320
want to use connectors for example to Gira or to whatever you have you have to configure them in
193
00:25:55,320 --> 00:26:04,760
in the power automate DLP so and that's a different story it's something I wasn't aware of like two
194
00:26:04,760 --> 00:26:13,080
years ago but and nowadays I see it a lot and I see a lot of things happening in a default environment
195
00:26:13,080 --> 00:26:22,360
but also with advanced connectors and rules that's a whole new world for me but it's a very nice world
196
00:26:22,360 --> 00:26:29,880
very big world with lots of things changing because they see oh we should have done this
197
00:26:29,880 --> 00:26:39,480
so there's a lot of things going on there and then that's because it's also called DLP you can get
198
00:26:39,480 --> 00:26:48,280
mixed up really fast so and from the per view I focus on the labels and the DLP within
199
00:26:48,280 --> 00:26:54,760
per view but of course there's much more in there like the retention etc. Yes.
200
00:26:54,760 --> 00:27:03,400
Did you think copilot change how we should design SharePoint architecture or can we use the
201
00:27:03,400 --> 00:27:10,520
classics like I think for years we talk about information architecture or metadata, content
202
00:27:10,520 --> 00:27:16,520
types, subsides, taxidermy and search. Do these concepts become more important or less important
203
00:27:16,520 --> 00:27:25,640
when I can understand I think your natural language? Well I think they are becoming more important
204
00:27:25,640 --> 00:27:35,240
again instead of less important and there's a little bit of history because when teams came out
205
00:27:35,240 --> 00:27:45,400
you had this general folder in your SharePoint library and I must be honest I did not like it
206
00:27:45,400 --> 00:27:52,680
in there because it fully trolled the structure of how you set up SharePoint it's a total different
207
00:27:52,680 --> 00:28:01,720
way and a lot of people were a bit disappointed to say the least but then with teams we were working
208
00:28:01,720 --> 00:28:12,520
more again to a folder structure because teams was like that but I think when we look now I would say
209
00:28:12,520 --> 00:28:25,240
metadata is really important to have the correct data coming out and that not alone but if you
210
00:28:25,240 --> 00:28:34,280
in my opinion when I look at SharePoint libraries or team libraries doesn't matter I always say
211
00:28:34,280 --> 00:28:44,360
maximum three folders deep and the rest metadata but also like three or four fields maximum
212
00:28:44,360 --> 00:28:52,760
because if you do too much of metadata the people will not fill it in and now with co-pilot it can
213
00:28:52,760 --> 00:29:00,280
even look at your data and make the columns itself and then we also come to a point where we have to
214
00:29:00,280 --> 00:29:08,600
say okay this is a repeating order so then we have to set up content types which are also really
215
00:29:08,600 --> 00:29:15,800
important in the in the co-pilot space but also in the search space because a lot of people
216
00:29:15,800 --> 00:29:29,160
forget that as well. Yeah yeah I think one one thing it's oh we have the IT they have their work
217
00:29:29,800 --> 00:29:35,960
to do to make co-pilot ready but there it's also the employees I think the normal users I say
218
00:29:35,960 --> 00:29:49,800
marketing sales and so on. So I think we have the governance questions I think it's most IT and
219
00:29:50,360 --> 00:30:03,400
the other side I say it's the adoption part. What separates organization that gets strong co-pilot
220
00:30:03,400 --> 00:30:15,080
adoption from those that don't? Well especially the companies I've seen and a few have really good
221
00:30:15,080 --> 00:30:23,800
adoption because what they do they inform their clients how to get work done easier and with
222
00:30:23,800 --> 00:30:32,520
tips every day but also like not only co-pilot but also agents how to use them what are the best
223
00:30:32,520 --> 00:30:41,080
prompts to use and they organize like days in the company where you can check out what
224
00:30:41,080 --> 00:30:53,960
what agents they use or how they prompt it so they are really good and they you see like an adoption
225
00:30:53,960 --> 00:31:03,560
grade of or above 90% but there are also companies that just do like a day and then you get all
226
00:31:03,560 --> 00:31:11,560
information at once like they throw a full bucket of of trash over you and you have to figure out
227
00:31:11,560 --> 00:31:20,040
how it works the day after so they are doing not as well but you have to be careful with it because
228
00:31:22,360 --> 00:31:29,880
if you keep in contact with the business you will have much more of attraction not only from
229
00:31:29,880 --> 00:31:37,640
a IT perspective but also from the business side because once people see that there is a team
230
00:31:37,640 --> 00:31:45,160
constantly involved and helping them to get better it goes around in the company and people get
231
00:31:45,160 --> 00:31:54,760
better instead of one time this is it and a lot of things that in adoption land happens and I
232
00:31:54,760 --> 00:32:05,000
did it as well I haven't turned on to blame anybody but it's like this is this knob is for this this
233
00:32:05,000 --> 00:32:15,240
knob is for that but I think the better adoption practices are why would I use this and what is the
234
00:32:15,240 --> 00:32:24,520
outcome what can I expect and I think it's when you go to a company and you want to improve the
235
00:32:24,520 --> 00:32:31,960
adoption ask them how they work on the daily base what are the first stations that they have on a
236
00:32:31,960 --> 00:32:39,480
daily base and then check if you can create that something with copilot to improve like one hour to
237
00:32:39,480 --> 00:32:50,440
our day or a week because you can really improve your your work with copilot but you need to know exactly
238
00:32:50,440 --> 00:32:57,320
how to use it and that's that's the hardest part and especially because we have like
239
00:32:58,600 --> 00:33:06,200
weekly we have like 25 updates or something like that so it's not only like okay I know now copilot
240
00:33:06,200 --> 00:33:14,120
and I'm done no and next week it looks different and a good example is for example the the work
241
00:33:14,120 --> 00:33:20,920
editor or PowerPoint where you first had like you had the in PowerPoint you could
242
00:33:20,920 --> 00:33:28,520
prompt a copilot chat and it would do only in the side it would generate something now you can
243
00:33:28,520 --> 00:33:38,840
edit it and during the first times prompts for people just before summer you had to choose
244
00:33:38,840 --> 00:33:47,320
in the prompts which brand kit you were going to use if you use it brand kit of course but now you
245
00:33:47,320 --> 00:33:56,200
can already pre-select it from with the plus sign which makes it way much easier and just to prompt
246
00:33:56,200 --> 00:34:04,200
what you want in your PowerPoint and that's all those little skills they are they they make your work
247
00:34:04,200 --> 00:34:17,800
so much easier okay I think what did you think about the yeah I say the copilot champion
248
00:34:17,800 --> 00:34:25,000
program what did you think about it and and what did you think are here the best practice
249
00:34:25,160 --> 00:34:34,440
I think the copilot champion program is already good is a good start let's put it that way but you
250
00:34:34,440 --> 00:34:43,960
always have to check on how your company is working and if it's going as you planned and if it's
251
00:34:43,960 --> 00:34:52,840
the same as the the AI adoption plan for Microsoft because a lot of adoption plans that are made are not
252
00:34:53,480 --> 00:35:03,960
are for really big big companies which some companies with 25 people they won't use it it's
253
00:35:03,960 --> 00:35:11,480
it's too much and I think it's really important to look at that what does my company need does it need
254
00:35:11,480 --> 00:35:21,080
the AI adoption plan for Microsoft which is free by the way so you can just use it but I would rather
255
00:35:21,080 --> 00:35:29,800
make a combination of that like look at the adoption plan and take a little bit of that and create
256
00:35:29,800 --> 00:35:38,920
full plan for your organization and challenge users challenge if they they like it or not and what
257
00:35:38,920 --> 00:35:47,880
they think about this adoption program I think what also interesting is I think at the start the
258
00:35:47,880 --> 00:35:57,080
copilot it was really simple if the CFO came in and asked me yeah make sense to pay for copilot and
259
00:35:57,080 --> 00:36:06,440
then I are simply asked okay how many hours your employee saved and he say six okay then I say okay
260
00:36:06,440 --> 00:36:15,640
you pay 30 dollars it's it's five dollars per hour did you pay your employees more than more than five
261
00:36:15,640 --> 00:36:25,560
dollars than yes if less no so but now we get the the price thing with different tokens and so on
262
00:36:25,560 --> 00:36:34,200
yes yeah what what I heard in a different podcast with different people who do a lot of it AI
263
00:36:34,200 --> 00:36:41,080
really focus on only AI and they do it with different brands so it's a cloud and
264
00:36:41,640 --> 00:36:51,880
chat GBT but they they say that about it should be like two to three percent of the payment of
265
00:36:51,880 --> 00:37:03,560
the salary should be considered to be used on AI so like two to three present if somebody has a
266
00:37:03,560 --> 00:37:13,160
salary then it would be reserved for cost of AI for example co-work for a clot or any other
267
00:37:13,160 --> 00:37:23,880
AI system because people can learn more and more if they have like a budget on on their hand
268
00:37:23,880 --> 00:37:31,320
which they can spend on and this is something that's completely new of course because we are not
269
00:37:31,320 --> 00:37:41,240
used to spend so much on software for employees at least not in this way let's put it that way
270
00:37:41,240 --> 00:37:49,480
so I think that's a good thing if people would do that because you will see that they will adopt
271
00:37:49,480 --> 00:37:55,720
also more and more if they are aware so you have to get them aware of the situation
272
00:37:56,680 --> 00:38:06,200
and I think especially for example the copilot license is about 30 euros and 30 dollars 30 euros
273
00:38:06,200 --> 00:38:16,680
but with co-work you are talking tokens and with Microsoft Scout you are also talking tokens
274
00:38:16,680 --> 00:38:23,960
and the token thing is a whole different story whole different thing to talk about because
275
00:38:24,680 --> 00:38:34,680
if we look at co-work the first time I tried it out the amount of tokens I burned was immense
276
00:38:34,680 --> 00:38:43,480
so I thought okay what's going on here especially because we were in front there which means
277
00:38:43,480 --> 00:38:52,760
you can pre-use it then it was free and then first of July 26 they started to price you
278
00:38:53,960 --> 00:39:05,080
and when I did it then it was like really expensive and I thought okay I leave it for a while
279
00:39:05,080 --> 00:39:13,320
and then I went back like three weeks later and then it was like really cheap cheap and that's not
280
00:39:13,320 --> 00:39:22,840
only because co-work we came cheap but also because you have to be aware if you use co-work and it's on auto
281
00:39:22,840 --> 00:39:29,960
it will choose the model that's most suitable for your prompt but if you
282
00:39:29,960 --> 00:39:43,400
use co-work and you for example use clot opus 4.8 which is less than 5 a faible your cost will drop
283
00:39:43,400 --> 00:39:52,120
their mast dramatically so have a look at that if you want to do it but also there does this
284
00:39:52,120 --> 00:39:57,880
learning curve because if people start and they don't know this they will use faible 5 or
285
00:39:57,880 --> 00:40:08,200
astra from chatchipity to get the results and if they are not aware they will use co-work as co-pilot
286
00:40:08,200 --> 00:40:14,120
because there's also a chat in there so why not use it there and they are not aware of the cost
287
00:40:14,120 --> 00:40:18,360
so then you are getting into trouble let's put it that way
288
00:40:20,360 --> 00:40:29,720
I think what or we have started with co-pilot with prompt engineering doing prompts but now we
289
00:40:29,720 --> 00:40:37,480
yeah we have the the next era and I say it's the agent world and there are agents that say other
290
00:40:37,480 --> 00:40:43,240
agents to do this and that what's your view view on agents
291
00:40:45,240 --> 00:40:55,640
well I think agents can be very powerful and I heard a talk from missiel barman a few weeks back
292
00:40:55,640 --> 00:41:02,280
also in a podcast and he was talking about the Microsoft organization where they have
293
00:41:02,280 --> 00:41:10,840
enabled Microsoft's card for everyone and of course they have a earlier version so they eat their
294
00:41:10,840 --> 00:41:20,120
own dog food so to say but what he was telling me and or telling in the podcast he was telling that
295
00:41:20,120 --> 00:41:28,360
they have several everybody has a Microsoft scout session and those Microsoft scout sessions they
296
00:41:28,360 --> 00:41:36,440
are starting to talk to each other so they are agents talking to each other and they even show up in
297
00:41:36,440 --> 00:41:45,160
their organization profile so when you go into teams you can look at who's where in the organization
298
00:41:45,160 --> 00:41:53,160
and now even Microsoft scout agents show up there and you can talk to them directly so
299
00:41:53,160 --> 00:42:01,560
you can have like a question on one side from for me for example and I want to ask it to missiel
300
00:42:01,560 --> 00:42:09,000
and then missiel's agents pick it up and they say okay we can do that without disturbing missiel
301
00:42:09,000 --> 00:42:18,200
and putting it back to me so I think the future will be more like that but it can also be a danger
302
00:42:18,200 --> 00:42:28,600
because yeah we we are going to do a more AI way of working and once they start talking you still
303
00:42:28,600 --> 00:42:36,280
have to input them but once you stop inputting them and they can do everything you can do
304
00:42:36,280 --> 00:42:46,200
it can be a danger that's pretty that way. I think that's yeah I could be really critical but
305
00:42:46,200 --> 00:42:56,200
what did you think about yeah I think something like an agent center of excellence or AI center
306
00:42:56,200 --> 00:43:06,440
I don't know how we got there there is already one the the agent 365 is already a it is another
307
00:43:06,440 --> 00:43:13,160
license which at the moment I'm getting crazy about all those licenses that they come up with
308
00:43:13,160 --> 00:43:20,760
but within your admin center you also already have a agent 365 where you can view all your agents
309
00:43:20,760 --> 00:43:28,520
that are deployed in your environment even once you don't know because sometimes you don't know them
310
00:43:28,520 --> 00:43:36,840
and you can administrative them from there but also monitor them and even give permission from there
311
00:43:36,840 --> 00:43:45,800
so that's a really nice admin center I must say there are also third parties again
312
00:43:45,800 --> 00:43:53,880
that have similar functionality but cheaper and even sometimes more functionality so I would look
313
00:43:53,880 --> 00:44:02,040
I won't look will tell you not only to look at agent 365 but also look at third parties because
314
00:44:02,040 --> 00:44:11,240
although Microsoft works on it but third parties are most most of the time they are more
315
00:44:11,240 --> 00:44:17,720
innovative so they are more ahead of time and because they do it on the third party they can
316
00:44:17,720 --> 00:44:30,920
deliver it for a cheaper price yeah yeah and they have something that's yeah if you have these these
317
00:44:30,920 --> 00:44:37,160
what I read you from interesting you're you're originally from from from the Netherlands and then
318
00:44:37,160 --> 00:44:45,800
you go to Portugal and you have something you call it the focus week concept can you tell us a little
319
00:44:45,800 --> 00:44:57,960
bit about what is this as something to do with scope pilot or yes well what I we moved in 2023 to
320
00:44:57,960 --> 00:45:07,320
Portugal and at that time I did not know I was going to stay here but after three weeks we decided to
321
00:45:07,320 --> 00:45:15,560
stay here and now we have our own guesthouse as well on the land where we live and what I do in the
322
00:45:15,560 --> 00:45:25,000
focus week is actually you you start with how you want to do copilot or sharepoint and you you
323
00:45:25,000 --> 00:45:33,640
are going to go a week with me focusing only on copilot on sharepoint how to deploy it make
324
00:45:33,640 --> 00:45:42,600
you governance or make your development doesn't matter I'm here to help you then and what we do is in
325
00:45:42,600 --> 00:45:49,000
the morning we do the sessions in the afternoon you can go for a surf or you can go to the beach
326
00:45:49,960 --> 00:46:00,200
depending on what you like or go for a hiking we have great hiking trails so it's the thing is when
327
00:46:00,200 --> 00:46:07,160
you are in a company you are in a company so people come and disturb you all the time but when you
328
00:46:07,160 --> 00:46:13,160
go out of the company and you go somewhere else and you have the focus on it and you don't get
329
00:46:13,160 --> 00:46:21,400
disturbed by your colleagues you make search a lot of progress compared to in company and that's
330
00:46:21,400 --> 00:46:30,440
why I thought okay I have to make this and I like that people then come here as well and we can have
331
00:46:30,440 --> 00:46:38,120
a chat and we can check how we can improve everything of the company so yeah that's that's the thing
332
00:46:38,120 --> 00:46:48,040
what came up with me and I do a lot of surfing as well myself so yeah that's why I say it's a really good
333
00:46:48,040 --> 00:46:55,480
combination and you get back refreshed with the full program or a full list of things you can do
334
00:46:55,480 --> 00:47:04,280
or you are already ready to work on it with with the rest of your team or your company yeah
335
00:47:05,960 --> 00:47:12,040
awesome yeah that's that's that's I think yeah that that makes sense and you have the better
336
00:47:12,040 --> 00:47:21,400
better or more sunny weather than than we in middle Europe yes yes I'm I'm originally from Amsterdam
337
00:47:21,400 --> 00:47:29,080
or at least from the Netherlands I'm not an Amsterdam but from Aintova area but I lived a long time
338
00:47:29,080 --> 00:47:37,000
in Amsterdam so I know exactly the differences and just the weather is most of the time it's great
339
00:47:37,000 --> 00:47:49,720
we have 60 days of rain on a normal year so yeah I can I cannot complain but by the Netherlands
340
00:47:49,720 --> 00:48:02,680
the better you are parties yeah absolutely yeah cool I have yeah I say in every interview
341
00:48:02,680 --> 00:48:10,600
yeah I say rapid fire round I give you a short question and you give a short short answer so
342
00:48:11,560 --> 00:48:24,200
SharePoint or teams I would say teams at the moment okay co-pilot co-pilot studio or AI foundry
343
00:48:24,200 --> 00:48:34,840
co-pilot studio governance before adoption or adoption before governance
344
00:48:36,760 --> 00:48:44,760
all the way around and governance before adoption what what is the most underrated Microsoft 365 feature
345
00:48:44,760 --> 00:48:50,680
oh that's a good one
346
00:48:50,680 --> 00:49:02,520
early a days I would say one now but nowadays I would say much probably loop
347
00:49:04,200 --> 00:49:13,480
because I think loop is great it really works really well yeah it starts so simple and now it's such a
348
00:49:13,480 --> 00:49:21,480
powerful tool it's it's real it's really amazing how old is this evolved and so what's your
349
00:49:21,480 --> 00:49:25,320
five favorite co-pilot use case
350
00:49:28,360 --> 00:49:40,120
well I use it a lot for my own marketing as well so I think is is not early for in-company but also for
351
00:49:40,120 --> 00:49:48,360
your marketing it's a great tool but I also use it to keep me informed about things I still need to do
352
00:49:48,360 --> 00:49:57,640
things I forget that it just reminds me and what I also do is a lot of skills so
353
00:49:58,120 --> 00:50:07,160
we didn't talk about skills but a skill is like something like a standard operating procedure you
354
00:50:07,160 --> 00:50:17,960
every time repeat the same order a skill can do that so I love skills all my short videos that I
355
00:50:17,960 --> 00:50:29,000
post on youtube instagram and tiktok are actually done with AI so I speak normally but the editing is
356
00:50:29,000 --> 00:50:39,720
done by AI I'm not doing anything and it amazed me how much time I say for that so and then
357
00:50:39,720 --> 00:50:50,680
what do we have more yeah I use it also for myself for my CRM everything on that yeah it's hard to say
358
00:50:50,680 --> 00:51:00,440
okay this side of five use cases because there are many use cases to talk about and I think it
359
00:51:00,440 --> 00:51:09,560
also this is like each company has different use cases and some things that sound so logic
360
00:51:09,880 --> 00:51:17,880
they and you think okay yeah this isn't done in copage yet or there's no agent for that okay let's
361
00:51:17,880 --> 00:51:26,360
make a agent for that yeah when satanidalya calls you and say hey Paul you get all the money and
362
00:51:26,360 --> 00:51:36,200
resources to develop your dream feature and copilot what would it be to be honest I wouldn't know now
363
00:51:36,840 --> 00:51:49,720
I really don't know no no I couldn't answer your questions sorry okay okay who should I invite next
364
00:51:49,720 --> 00:52:05,560
and what questions should I ask I think it would be interesting to invite Vincent Clayis is a new
365
00:52:05,560 --> 00:52:14,520
MVP he's a Belgium guy living also in Portugal and he's on the adoption side so I think it would be
366
00:52:14,520 --> 00:52:25,480
really nice to hear his stories on adoption and where people yeah miss their tricks let's put it
367
00:52:25,480 --> 00:52:34,440
that way I also have a podcast with him but he's really nice and I think the main question is it
368
00:52:34,440 --> 00:52:45,240
would be like how do you do adoption in a multi multi country tenancy something like that
369
00:52:45,240 --> 00:52:51,320
because I think it's still lots of people can learn from him
370
00:52:51,320 --> 00:53:00,200
and finally if I tealed I listened to this episode we remember one thing about preparing
371
00:53:00,200 --> 00:53:09,160
Microsoft 365 for copilot what should it be I would start with the sharing settings I think that's
372
00:53:09,160 --> 00:53:18,280
a really important part to start with and to remember yeah then Paul thank you for for joining me today
373
00:53:18,280 --> 00:53:26,040
I think the biggest takeaway from the today session is that copilot readiness isn't really a
374
00:53:26,040 --> 00:53:33,000
copilot project it's Microsoft 365 project it's understand your share point environment
375
00:53:33,000 --> 00:53:38,920
it's understand who can access what it's yeah dealing with oversharing it's yeah building
376
00:53:38,920 --> 00:53:46,360
information protection strategy with technology such Microsoft PueView and yeah sensitivity labels
377
00:53:46,360 --> 00:53:53,640
and yeah then it's making sure people actually have real business problems where copilot can make
378
00:53:53,640 --> 00:54:06,040
a measurable difference so yeah for all the people you find all the links to Paul's podcast and
379
00:54:06,040 --> 00:54:15,800
to Paul's linked it profiles and other things in the show notes from the m65fmp podcast page and yeah
380
00:54:15,800 --> 00:54:22,760
which thank you podcast as Microsoft MEP found out kbworks for for joining us
381
00:54:22,760 --> 00:54:27,720
thank you it's all not to be here
382
00:54:27,720 --> 00:54:30,700
[ENGINE REVVING]
Apple Podcasts
Spotify
Youtube Music
Spreaker
Podchaser
Amazon Music


