SharePoint Isn't Boring Anymore: How Copilot Is Reinventing the Modern Workplace with Marcin Siewnicki [MVP]

1
00:00:00,000 --> 00:00:04,480
Hello everybody and welcome back to the Amsti65FAM podcast.

2
00:00:04,480 --> 00:00:09,280
For years SharePoint has had a reputation problem.

3
00:00:09,280 --> 00:00:13,280
Ask many employees what they think about SharePoint and you will hear

4
00:00:13,280 --> 00:00:18,000
familiar answers, complicated document libraries, outdated

5
00:00:18,000 --> 00:00:22,000
intranets, impossible navigation, too many sites and

6
00:00:22,000 --> 00:00:24,880
information nobody can find.

7
00:00:24,880 --> 00:00:28,880
Microsoft 365 is changing and AI could fundamentally change the

8
00:00:28,880 --> 00:00:34,560
role SharePoint plans inside modern workplaces because when co-pilot needs

9
00:00:34,560 --> 00:00:38,160
organization knowledge documents permissions context and business

10
00:00:38,160 --> 00:00:42,160
information, suddenly the way we structure SharePoint becomes extremely

11
00:00:42,160 --> 00:00:46,960
important. My guest today is Martin C. Vesnik,

12
00:00:46,960 --> 00:00:51,200
Microsoft 365 solution architect with more than 20 years experience of

13
00:00:51,200 --> 00:00:54,240
creating an implementing business application based on SharePoint

14
00:00:54,240 --> 00:01:00,000
and Microsoft 365. Massive specialized in building modern workplaces using

15
00:01:00,000 --> 00:01:05,360
SharePoint, Microsoft Teams, Power Platform, Power Automate and

16
00:01:05,360 --> 00:01:09,360
increasingly co-pilot. He is also active in the Microsoft community,

17
00:01:09,360 --> 00:01:15,520
co-organized the SharePoint Saturday, Waslove and regulated speaks at community

18
00:01:15,520 --> 00:01:19,120
events. Today we are going to explore how SharePoint and Teams fit

19
00:01:19,120 --> 00:01:23,520
together, why traditional intranets need to evolve and how

20
00:01:23,520 --> 00:01:27,680
co-pilot change information is covering, what organizations need to fix

21
00:01:27,680 --> 00:01:31,840
before introducing AI and what AI power modern workplaces could look like in the

22
00:01:31,840 --> 00:01:36,800
next few years. Martin, welcome to the MC65athon podcast.

23
00:01:36,800 --> 00:01:42,160
Hello everyone, thank you for the great introduction.

24
00:01:42,160 --> 00:01:53,040
Awesome, so you started in the IT 20-5, how did you only get into SharePoint?

25
00:01:53,040 --> 00:02:02,320
Well, that was my very first real IT job and the company simply used SharePoint

26
00:02:02,320 --> 00:02:11,440
where it was SharePoint on-prem version 2003 so it was quite

27
00:02:11,440 --> 00:02:17,840
old one, looking from now. So I started working at SharePoint

28
00:02:17,840 --> 00:02:26,480
as a user, power user, add the mean and customizing in building

29
00:02:26,480 --> 00:02:30,960
solutions based on SharePoint. It was pretty interesting,

30
00:02:30,960 --> 00:02:39,680
no path from the simple user so I had to use documents, upload documents,

31
00:02:39,680 --> 00:02:44,880
create lists, items, records and so on.

32
00:02:44,880 --> 00:02:53,600
And I ended up with a pretty advanced solution on SharePoint on-premises

33
00:02:53,600 --> 00:03:03,680
within a few years. Awesome, and now yeah, I think

34
00:03:03,680 --> 00:03:11,120
when, what will you say with did SharePoint look like when you started

35
00:03:11,120 --> 00:03:16,000
compared to the platform we have today?

36
00:03:16,000 --> 00:03:24,000
Oh, that's interesting question, well it was complex solution

37
00:03:24,000 --> 00:03:30,160
back in the days. You had to know what you want to do,

38
00:03:30,160 --> 00:03:37,280
how you want to do that task and so on, you had to understand the platform

39
00:03:37,280 --> 00:03:42,640
correctly. It was a pretty complex solution because

40
00:03:42,640 --> 00:03:49,360
sometimes simple change could damage entire site, entire library or even

41
00:03:49,360 --> 00:03:56,960
portal. So yeah, it was a complex solution, you had to use additional tools

42
00:03:56,960 --> 00:04:02,560
to create pages, to create complex library views or

43
00:04:02,560 --> 00:04:08,240
list views or add some automation. You had to use additional tools and

44
00:04:08,240 --> 00:04:12,320
know really you had to know what you are doing.

45
00:04:12,320 --> 00:04:18,160
But right now I think it's the best time for SharePoint

46
00:04:18,160 --> 00:04:25,760
because that knowledge level is pretty low. You can start quickly working SharePoint,

47
00:04:25,760 --> 00:04:31,360
you can work with your documents, sites, with your data in general

48
00:04:31,360 --> 00:04:36,320
and you don't need to think how to create library, how to create

49
00:04:36,320 --> 00:04:44,000
least, how to connect the data. It's pretty simple, for some level,

50
00:04:44,000 --> 00:04:50,320
so you can use SharePoint features, functions, pretty quickly and

51
00:04:50,320 --> 00:04:54,240
build what you need. Of course, if you need more, more complex solutions, you need

52
00:04:54,240 --> 00:05:00,240
to understand and know much more but that basic level, that user

53
00:05:00,240 --> 00:05:04,080
level or even power user level is pretty low now and you can

54
00:05:04,080 --> 00:05:07,840
extremely quickly start working with SharePoint and that's amazing,

55
00:05:07,840 --> 00:05:17,520
comparing to 20 years ago or even 10 years ago, it was just, you know, like day and night.

56
00:05:17,520 --> 00:05:25,360
And yeah, the most employees I know from different companies,

57
00:05:25,360 --> 00:05:29,280
they don't like SharePoint very much. It's had these bad

58
00:05:29,280 --> 00:05:34,240
reputation so we also titled it, "Shaport is boring anymore"

59
00:05:34,240 --> 00:05:39,760
but why did you think SharePoint have these bad reputation?

60
00:05:39,760 --> 00:05:44,720
I think that because I saw many, many implementations,

61
00:05:44,720 --> 00:05:51,360
that implementations, so simply organization created complex

62
00:05:51,360 --> 00:05:54,640
intranet solutions with a lot of wet parts, a lot of, you know,

63
00:05:54,640 --> 00:06:02,080
customizations, it was, first of all, usually it was ugly, simply ugly.

64
00:06:02,080 --> 00:06:07,040
It wasn't prepared for employees, it was simply IT solution,

65
00:06:07,040 --> 00:06:12,960
built by IT and employees had to use it, simply.

66
00:06:12,960 --> 00:06:19,120
So it was simply hard to use complex and usually outdated

67
00:06:19,120 --> 00:06:25,680
on the very first date. And I had to use some of those

68
00:06:25,680 --> 00:06:31,680
intranets and it wasn't the best experience to be honest.

69
00:06:31,680 --> 00:06:39,200
So I know why, why still have bad reputation because it's, well, we,

70
00:06:39,200 --> 00:06:45,120
IT guys, IT staff, built that reputation,

71
00:06:45,120 --> 00:06:50,880
and future actually. So is it because I don't know the IT

72
00:06:50,880 --> 00:06:55,600
things, they build something great or build, we build, we

73
00:06:55,600 --> 00:06:59,840
intranets based on what the management things instead of what

74
00:06:59,840 --> 00:07:05,520
employees actually need. So did we have, I don't know, a feedback, feedback

75
00:07:05,520 --> 00:07:11,360
looks or something? Yes, I saw it many times that, that thing

76
00:07:11,360 --> 00:07:17,120
that loop was simply broken, IT gathered requirements,

77
00:07:17,120 --> 00:07:21,440
built something based on those requirements, and that's it.

78
00:07:21,440 --> 00:07:25,520
Simply, so the solution is done, intranet is done,

79
00:07:25,520 --> 00:07:32,480
Ray, you have to, you have to use that portal and live with that.

80
00:07:32,480 --> 00:07:38,480
And what, what did you think, how much of the problem comes from the information

81
00:07:38,480 --> 00:07:42,960
architecture and how much comes from governance?

82
00:07:42,960 --> 00:07:50,400
I think the biggest one is information architecture because usually people don't

83
00:07:50,400 --> 00:07:54,560
know how to use, how to build it, don't know even what it is.

84
00:07:54,560 --> 00:08:02,400
So this is just, no, skipped or nonexisting part of the project.

85
00:08:02,400 --> 00:08:08,160
So just put a lot of data inside into the SharePoint and

86
00:08:08,160 --> 00:08:12,800
use it. So usually SharePoint is a

87
00:08:12,800 --> 00:08:17,760
shared folder for huge bucket for everything. So there's no

88
00:08:17,760 --> 00:08:22,640
information architecture. And then it's hard to find information, hard to find

89
00:08:22,640 --> 00:08:28,160
documents. Usually you have five, ten, twenty versions of the same document

90
00:08:28,160 --> 00:08:33,520
and you don't know which one is correct, which one is

91
00:08:33,520 --> 00:08:37,360
currently used, which one is outdated.

92
00:08:37,360 --> 00:08:42,160
Maybe archived and so on. So it's, I think that information architecture is the

93
00:08:42,160 --> 00:08:48,880
biggest pain point in Manage SharePoint implementation.

94
00:08:48,880 --> 00:08:53,520
And this is also, governance is also important, but

95
00:08:53,520 --> 00:08:57,120
it's from the IT and security perspective.

96
00:08:57,120 --> 00:09:01,360
For users, for everyday work, everyday tasks,

97
00:09:01,360 --> 00:09:06,640
information architecture is the biggest thing I think.

98
00:09:06,640 --> 00:09:10,880
Yeah, but when we forget everything about the

99
00:09:10,880 --> 00:09:14,320
traditional SharePoint internet, what do

100
00:09:14,320 --> 00:09:22,640
modern SharePoint architecture look like?

101
00:09:22,640 --> 00:09:29,920
Well, the best one, of course, the modern one,

102
00:09:29,920 --> 00:09:39,920
something that has been always in the SharePoint. So metadata

103
00:09:39,920 --> 00:09:46,640
properly implemented or it can be based, basically, metadata implementation,

104
00:09:46,640 --> 00:09:51,440
but it must be created before we start

105
00:09:51,440 --> 00:09:57,600
working with documents. And then we need to understand our own data and

106
00:09:57,600 --> 00:10:04,960
hit it, simple, remove all those duplicates, all those

107
00:10:04,960 --> 00:10:10,640
unnecessary data because it makes just chaos in inside SharePoint.

108
00:10:10,640 --> 00:10:16,240
So if it's simple, if we know what we want to achieve and if we have metadata,

109
00:10:16,240 --> 00:10:22,480
even basic one, actually, that's good enough for most of

110
00:10:22,480 --> 00:10:26,240
implementation, most of companies.

111
00:10:26,240 --> 00:10:32,480
And when we start the homepage of a modern digital workplace,

112
00:10:32,480 --> 00:10:42,640
what should it actuary accomplish? Home page, that's interesting.

113
00:10:42,640 --> 00:10:50,240
Home page, well, the best one is that it's a bit personalized, so it shows

114
00:10:50,240 --> 00:10:54,800
what I need to do, my data, my own information,

115
00:10:54,800 --> 00:11:01,360
and so on. So it should be somehow attached to my own

116
00:11:01,360 --> 00:11:07,200
information. Of course, it should be good looking

117
00:11:07,200 --> 00:11:13,120
home page because we have nice and beautiful pages,

118
00:11:13,120 --> 00:11:20,720
but it should be personalized and it should contain all those information that I

119
00:11:20,720 --> 00:11:27,360
probably need, should use. So my applications, my documents,

120
00:11:27,360 --> 00:11:33,680
pretty simple navigation, not too complex. This is

121
00:11:33,680 --> 00:11:41,280
GQ1, not too complex. And of course, search, right now, copy lots,

122
00:11:41,280 --> 00:11:45,360
it's a bit different, but

123
00:11:46,320 --> 00:11:51,680
that's the thing, not too complex. So pretty simple, I saw many, many

124
00:11:51,680 --> 00:11:58,080
home pages that I don't know, maybe even four pages,

125
00:11:58,080 --> 00:12:03,200
hate, so it's, you know, scroll down, scroll down, and oh, that's the thing that I was

126
00:12:03,200 --> 00:12:11,440
looking for. No, if it's not on that top page, it won't be used to be honest.

127
00:12:11,440 --> 00:12:17,920
And normally say how important are communication sites today?

128
00:12:17,920 --> 00:12:24,400
I think this is the most important part because if we use SharePoint sites,

129
00:12:24,400 --> 00:12:28,320
we need to come, we want to communicate something,

130
00:12:28,320 --> 00:12:36,560
and communication sites are, though, pretty, they are properly implemented,

131
00:12:36,560 --> 00:12:40,960
those out of the box templates are, I think, good enough for most

132
00:12:40,960 --> 00:12:47,520
organizations. And if it's implemented with basic information, it's good enough.

133
00:12:47,520 --> 00:12:53,680
You can easily, I use it as even as your intranet portal,

134
00:12:53,680 --> 00:12:59,440
simply good enough, basic information, basic news, some links,

135
00:12:59,440 --> 00:13:06,720
good looking, mobile, friendly, that's great. And I think,

136
00:13:06,720 --> 00:13:13,840
also about mobile, that this is extremely important right now because usually

137
00:13:13,840 --> 00:13:20,160
I spend a lot of time on my phone and store my SharePoint

138
00:13:20,160 --> 00:13:26,320
sites or my customer sites. And if it's not working on my mobile, I probably

139
00:13:26,320 --> 00:13:32,560
won't use it. Yeah, and we have the other,

140
00:13:32,560 --> 00:13:39,920
I think, how do they fit into the architecture?

141
00:13:39,920 --> 00:13:47,840
Yeah, it's a nice concept, but many organizations don't know how to use it,

142
00:13:47,840 --> 00:13:53,440
because it's simply connection between sites. Right now we don't have,

143
00:13:53,440 --> 00:13:58,160
no, this commonly used back in the days, architecture,

144
00:13:58,160 --> 00:14:05,840
when you have site and multiple subsides, but that pattern is gone

145
00:14:05,840 --> 00:14:12,880
fortunately. But now we can connect different sites together to just know,

146
00:14:12,880 --> 00:14:20,160
to make it simple and consistent navigation between sites consistent,

147
00:14:20,160 --> 00:14:24,560
template, look and feel. So it's nice, nice concept,

148
00:14:24,560 --> 00:14:30,400
pretty simple, pretty simple to continue to use. But my experience,

149
00:14:30,400 --> 00:14:34,960
many organizations simply don't use it. I don't know why, maybe to

150
00:14:34,960 --> 00:14:40,880
complex, maybe to, maybe they don't know. I just simple and

151
00:14:40,880 --> 00:14:48,320
quite powerful. I like it. Yeah, and I think when I talk to,

152
00:14:48,320 --> 00:14:52,160
I don't know, I'm not so deep in the SharePoint topic, it's for me it's more

153
00:14:52,160 --> 00:14:58,880
to organize data, but when I talk to people, the one of the core problems I think they have,

154
00:14:58,880 --> 00:15:03,600
it's the navigation, they don't understand the navigation.

155
00:15:03,600 --> 00:15:09,280
How should organizations think about navigation on SharePoint pages?

156
00:15:09,280 --> 00:15:17,760
Yeah, this is pretty important to, and to be honest, SharePoint still has problems with it,

157
00:15:17,760 --> 00:15:24,080
because it should be simple, but contains all required information, all required links,

158
00:15:24,080 --> 00:15:33,200
and usually you don't have links properly divided into categories or so,

159
00:15:33,200 --> 00:15:40,400
but if you create or gather all links, filter only, or filter out all those

160
00:15:40,400 --> 00:15:47,680
unnecessary, leave only those required and important, usually you have pretty long list,

161
00:15:47,680 --> 00:15:52,560
and it's not so simple to put all those links in modern SharePoint navigation, because

162
00:15:52,560 --> 00:16:00,160
no, you have to create complex, you know, those mega menu with categories, links, sublinks,

163
00:16:00,160 --> 00:16:07,600
and so on, and it's complex in SharePoint still. So what works is that it must be simple,

164
00:16:08,880 --> 00:16:17,040
really, only basic links to the most important part of your organization,

165
00:16:17,040 --> 00:16:25,200
to departments, to their critical applications, and on that target site, you can have no more

166
00:16:25,200 --> 00:16:33,200
detailed navigation, because otherwise it just complex, you know, monster with hundreds of links,

167
00:16:33,200 --> 00:16:43,440
and you usually use those as well, lost in those links, and last, it's, I don't know,

168
00:16:43,440 --> 00:16:48,480
it's still a thing in SharePoint that it's not so easy to create navigation, to modify it,

169
00:16:48,480 --> 00:16:57,040
you need to go and write for a while with this editing tool, so I think this is the thing,

170
00:16:57,040 --> 00:17:02,560
the part of the store point that there are a lot of no space for improvement right now.

171
00:17:02,880 --> 00:17:13,520
And, well, I think what's also make is the little bit problem, it's, we have a lot of SharePoint,

172
00:17:13,520 --> 00:17:20,480
it's, yeah, we have the SharePoint sprawl problem, and it's so much stuff in there, because it's

173
00:17:20,480 --> 00:17:28,960
connected to two teams, and so some companies have connected it to one drive and so on.

174
00:17:31,200 --> 00:17:37,920
How can we prevent these sprawl in SharePoint? What's your tips here?

175
00:17:37,920 --> 00:17:46,880
Oh, that's complex one, and I face it to be honest every day. I think every, every,

176
00:17:46,880 --> 00:17:53,440
every single customer, they use it that way, so they create a lot of teams, a lot of SharePoint sites,

177
00:17:53,440 --> 00:18:00,800
in SharePoint, and they are lost, because you have a lot of teams, a lot of

178
00:18:01,280 --> 00:18:06,480
no channels, and every channel can have our SharePoint sites, and then

179
00:18:06,480 --> 00:18:16,000
the dedicated SharePoint sites, so it's pretty complex for managing, for finding information,

180
00:18:16,000 --> 00:18:24,640
and for governance, and for permissions, it can be a really painful one, but

181
00:18:27,920 --> 00:18:34,560
the best, or maybe not the best, but it works pretty good, pretty well, this is

182
00:18:34,560 --> 00:18:46,240
approach that people need to create sites based on some kind of template, and even teams,

183
00:18:46,240 --> 00:18:52,400
so they need to provide information about why they need to create that site, and provide basic

184
00:18:52,400 --> 00:19:00,560
metadata for a site, and the same way for teams, so then you can create a list, manage those sites,

185
00:19:00,560 --> 00:19:10,240
manage those teams, and more or less you will be able to know what is inside each site, or inside

186
00:19:10,240 --> 00:19:20,160
each team, but from the end user perspective, well, it's still a thing to understand

187
00:19:20,160 --> 00:19:24,720
what's the difference between SharePoint and Teams, usually they don't know, so you need to simply

188
00:19:24,720 --> 00:19:31,680
educate them, provide some training, because otherwise they will still use SharePoint as

189
00:19:31,680 --> 00:19:38,240
something, storage, bucket, and teams have a storage bucket in Teams, so they don't know what's

190
00:19:38,240 --> 00:19:42,080
the difference, and they put everything inside, no matter what it is.

191
00:19:45,200 --> 00:19:51,920
Yeah, that's interesting, I think these, yeah, because SharePoint and Teams are

192
00:19:51,920 --> 00:19:58,880
closely connected technically, but yeah, you say many users don't understand that

193
00:19:58,880 --> 00:20:01,520
relationship, how do you explain it?

194
00:20:01,520 --> 00:20:14,400
Basic, one, maybe, to pay one teacher, simply one, very basic documents with all those information,

195
00:20:15,360 --> 00:20:21,440
and use cases, so when you need to use SharePoint, when you need to use Teams, what's good for

196
00:20:21,440 --> 00:20:29,040
this specific use cases for this specific scenario, so users can simply know, check, oh, I need to

197
00:20:29,040 --> 00:20:36,080
communicate a lot, so I should create a team, a team inside Teams, or maybe I need just documents

198
00:20:36,080 --> 00:20:42,640
and share them with my external parties, partners, vendors, whatever, so I don't need Teams,

199
00:20:44,160 --> 00:20:50,800
I can stay with SharePoint, so I create a SharePoint site, it will be no good enough, so I don't

200
00:20:50,800 --> 00:20:59,600
need to create all those additional layers of communication, and it must be tailored to the

201
00:20:59,600 --> 00:21:06,240
specific organization, because usually wherever organization is different, so it should be,

202
00:21:06,240 --> 00:21:13,760
a dose scenario should be, should match specific organization, then users will be, no, they will

203
00:21:13,760 --> 00:21:17,120
more, they will understand it better simply.

204
00:21:17,120 --> 00:21:27,280
Can we say Teams should be considered the user interface while SharePoint becomes the information

205
00:21:27,280 --> 00:21:39,440
layout, then is it? Yeah, that's, yeah, we can say that. And what I see is also when we talk about

206
00:21:39,440 --> 00:21:46,640
SharePoints Pro, we also have to talk about Teams Pro, so a lot of organizations create, so-so-so-them,

207
00:21:46,640 --> 00:21:57,200
many Teams, Locals, Birthday Party, and Project Final 7, and so on, how should we

208
00:21:57,680 --> 00:22:09,440
take care or of it? Yeah, this is the governance part, and the best way is to start with

209
00:22:09,440 --> 00:22:20,160
governance before we let users create a lot of Teams, but usually right now everyone has Teams,

210
00:22:20,160 --> 00:22:29,440
so it's a lot of Teams inside Teams, but implementing proper governance I think is the

211
00:22:29,440 --> 00:22:35,600
critical part, because then we can, or admins can understand what's going on in their own tenant,

212
00:22:35,600 --> 00:22:45,760
how many Teams are used, outdated, orphaned, and so on, so proper governance, it can be

213
00:22:45,760 --> 00:22:52,560
even simple, simple SharePoint or maybe Microsoft Forms, Form with basic information that

214
00:22:52,560 --> 00:23:00,960
users should provide, and basic SharePoint list with approval and so on, so nothing, nothing

215
00:23:00,960 --> 00:23:11,520
fancy, just simple, simple stuff, and then, and to be honest, even in large, I have one customer,

216
00:23:12,240 --> 00:23:22,160
50, more than 50,000 users, so it's not the simple, not the small one, basic Microsoft Form,

217
00:23:22,160 --> 00:23:27,920
basic SharePoint list, it's good enough, and it is working, really, really good, really well,

218
00:23:27,920 --> 00:23:37,520
and class, there are many, many sort of features, yeah, features, many features inside SharePoint,

219
00:23:37,520 --> 00:23:43,280
admin center right now, that you can use to simply add some governance layer, so admins can

220
00:23:43,280 --> 00:23:49,360
send dedicated messages to SharePoint site owners, so in fact, Teams as well,

221
00:23:49,360 --> 00:23:55,600
to check if there's still need that site, need that team, if not that

222
00:23:55,600 --> 00:24:02,320
site can be archived automatically, or put to, or simply removed if you need it,

223
00:24:03,040 --> 00:24:11,200
you don't need those data anymore, so Microsoft implemented a few really, really needed features

224
00:24:11,200 --> 00:24:20,320
in that, in that governance area. I think when people are going and they often

225
00:24:20,320 --> 00:24:27,840
figure, for they often sounds like the opposite of innovation, how do you balance these two

226
00:24:27,840 --> 00:24:41,360
yeah, sites? Yeah, innovations, of course it's nice to have the best to create everything,

227
00:24:41,360 --> 00:24:51,840
not to be governed, but usually there must be some kind of governor, some, someone

228
00:24:53,600 --> 00:25:00,720
should check what we are doing, what users are doing, otherwise there will be mess chaos,

229
00:25:00,720 --> 00:25:10,480
ants, data will be no leaking everywhere, so there must be a balance between

230
00:25:10,480 --> 00:25:17,440
you know, those innovations extremely useful, many times features,

231
00:25:20,080 --> 00:25:26,880
and of course, governor security, so admins always need to keep an eye on the data,

232
00:25:26,880 --> 00:25:33,760
on the security part, ad-keyf, or maybe configure it properly, then users can use what's

233
00:25:33,760 --> 00:25:42,320
new, what's, you know, best for the work, but still keep their own data secured and

234
00:25:42,320 --> 00:25:51,040
properly governed, that's always tricky one, because you find that balance between what's new,

235
00:25:51,040 --> 00:25:57,040
what's, you know, innovations, you've users everything, but still keep everything secured.

236
00:25:57,040 --> 00:26:04,320
And when we think about, especially when we talk about security, but is it,

237
00:26:05,600 --> 00:26:13,200
did you think governance is an IT topic and should it be governed centrally or is it?

238
00:26:13,200 --> 00:26:21,760
It is IT topic for sure, but there must be a consistent governance model for everything, not only for

239
00:26:21,760 --> 00:26:28,640
Sherpo, because Sherpo is one part, but we have sensitivity labels, of course for documents,

240
00:26:28,640 --> 00:26:35,360
for information, for teams, for sites, for third-party applications, not from Microsoft,

241
00:26:35,360 --> 00:26:45,040
so it must be created or managed centrally, but IT is the critical part, but together with

242
00:26:45,040 --> 00:26:52,400
management and with key business users, because they will use that system anyway, and if you create

243
00:26:52,400 --> 00:26:59,520
these two complex, they will, as usual, find a workout and don't use it, or maybe for example,

244
00:26:59,520 --> 00:27:11,600
skip a sensitivity labels or safe data on, on devices, not on the SharePoints, so it's, I think

245
00:27:11,600 --> 00:27:19,280
that everything must be involved in the governance process, otherwise it's just, no, people will

246
00:27:19,280 --> 00:27:26,720
always find a workout, if not, no, say the best, the best workout is if you do not provide a proper

247
00:27:28,240 --> 00:27:35,280
governance for AI, for example, and proper tools for users, they will use own devices, create

248
00:27:35,280 --> 00:27:43,440
screenshots and send it to own charge PT, so anyway, data will be lost, but people will do what they want.

249
00:27:43,440 --> 00:27:53,200
Yeah, awesome. I think a little bit about when companies start with governance, you say they

250
00:27:53,200 --> 00:27:59,200
should start with governance at the first time, so what are the main governance policies you

251
00:27:59,200 --> 00:28:09,520
should establish for SharePoint and Teams? So the very first one is that SharePoint or SiteWare

252
00:28:09,520 --> 00:28:16,800
Teams is still in use, so check every, no, periodically, for example, every six months, if that specific

253
00:28:16,800 --> 00:28:24,320
site or team is still in use, if not, maybe we should archive it, maybe we should remove it, maybe

254
00:28:24,320 --> 00:28:30,480
is accessible, so some kind of test, test one, there are plenty of test sites, test teams, we can

255
00:28:30,480 --> 00:28:38,880
simply remove it from our tenant. The next one is, no, check permissions, it's obligatory to have

256
00:28:38,880 --> 00:28:49,760
that policy to check periodically every few months, at least once a year, so push site owner or site

257
00:28:49,760 --> 00:29:00,320
owners, team owners to check their own permissions, because usually users, they would have many

258
00:29:00,320 --> 00:29:09,760
colleagues, so that's site or Teams. External practice, external users, usually after some time,

259
00:29:09,760 --> 00:29:18,880
you have nice, beautiful SharePoint site with hundreds or even thousands, external links,

260
00:29:18,880 --> 00:29:25,840
and you are not able to check who has access to that specific file, and simply you can create it,

261
00:29:25,840 --> 00:29:32,880
well, you create that and over sharing problem, so you can't control data, you can't control

262
00:29:32,880 --> 00:29:38,640
permissions, and you can even share your own data outside of your organization, and this is critical.

263
00:29:38,640 --> 00:29:45,920
Fortunately, Microsoft is implementing right now these hero links, so instead of

264
00:29:45,920 --> 00:29:51,200
having multiple links to one file, we will have one single link,

265
00:29:52,480 --> 00:29:58,240
to a file or to a folder, and you can simply add more permissions to that link, remove some permissions,

266
00:29:58,240 --> 00:30:06,240
so only one specific link, so it will be much, much easier to manage, but still, this is critical

267
00:30:06,240 --> 00:30:12,640
policy to check every few months permissions, if it's correct, if they are correct, not correct,

268
00:30:12,640 --> 00:30:22,320
maybe you should remove. Many, many obsolete permissions, you know, those links with permissions,

269
00:30:22,320 --> 00:30:30,080
this is critical, and of course, I think the basic one is to, of course, it depends on the organization,

270
00:30:30,080 --> 00:30:38,640
but a form or a simple process that users should use to create size or teams, at some level,

271
00:30:38,640 --> 00:30:47,600
it is critical, so you should somehow create that process, it can be very basic, and to be honest,

272
00:30:47,600 --> 00:30:54,800
it should be basic, even in large enterprise, huge enterprises, it must be simple one, so simple

273
00:30:54,800 --> 00:31:04,400
information, but then people think twice before they create a site or a team, so provide business

274
00:31:04,400 --> 00:31:10,720
justification, why you need that site, is it so important to create another test site, or test

275
00:31:11,360 --> 00:31:18,080
birthday party, or whatever, or maybe you can use your own one drive to put those files inside it,

276
00:31:18,080 --> 00:31:27,040
so this will greatly minimize those no theft, test sites, test teams, and provide some

277
00:31:27,040 --> 00:31:31,120
no basic metadata for your content, this is important.

278
00:31:31,120 --> 00:31:39,040
I think one of the topics, especially in governance, is automation, so

279
00:31:40,000 --> 00:31:46,080
what did you think, should companies, world-based, power, share, graph, ARP, or use tools like,

280
00:31:46,080 --> 00:31:52,560
I don't know, RENCORE, BCC, script runner, what's your view here?

281
00:31:52,560 --> 00:31:54,400
Be honest,

282
00:31:54,400 --> 00:32:04,320
there are plenty of tools, of course, power share or power upgrade and graph,

283
00:32:05,040 --> 00:32:11,760
this is the minimum, I think, must have for every admin, if you think about governance,

284
00:32:11,760 --> 00:32:18,080
because they can provide you with the data, they provide everything you need, access to sites,

285
00:32:18,080 --> 00:32:23,920
manage sites, other permissions, and so on, so power share and graph, I think, is the basic.

286
00:32:23,920 --> 00:32:30,720
Of course, if you have complex environments, you can add some additional

287
00:32:30,720 --> 00:32:38,080
fair-party tools, why not RENCORE, share gate, whatever you need, but of course, they take cost more,

288
00:32:38,080 --> 00:32:45,680
but you don't deal with automation, and those scripts, that's great, but usually, I think,

289
00:32:45,680 --> 00:32:51,440
power share may be power-alchemy with graph, it's good enough for most cases,

290
00:32:51,440 --> 00:32:59,360
and usually I use power-alchemy with graph, or maybe, as your logic apps for,

291
00:32:59,840 --> 00:33:04,000
for more demanding tasks, but graph is great.

292
00:33:04,000 --> 00:33:14,640
I think, when we go back to what is SharePoint, I think,

293
00:33:14,640 --> 00:33:23,040
what do people think about SharePoint is still heavily associated with documents?

294
00:33:24,080 --> 00:33:29,440
What do the good document management look like today, especially in SharePoint?

295
00:33:29,440 --> 00:33:36,880
Yeah, documents, we use documents every day, so that's why we need to think about SharePoint as a

296
00:33:36,880 --> 00:33:45,520
document storage, in general, it's a storage for documents for data. So, first of all, of course,

297
00:33:45,520 --> 00:33:53,040
well, the best one is to understand your data, so you need to provide some kind of metadata

298
00:33:53,040 --> 00:34:00,400
management, model, maybe, and it's something that will help users' tag documents at some categories,

299
00:34:00,400 --> 00:34:09,280
maybe, and give them some help with naming convention, because usually, you know, name files,

300
00:34:09,280 --> 00:34:16,400
something, something, and version 1, version 2, final version, something, test version,

301
00:34:16,400 --> 00:34:22,560
whatever, draft, second draft, so naming convention is important, some basic metadata is also

302
00:34:22,560 --> 00:34:30,080
important, so they simply can be discovered easily. And a few things about configuration also is

303
00:34:30,080 --> 00:34:37,920
important from IT perspective, so the very basic, very important, very critical one is, of course,

304
00:34:37,920 --> 00:34:48,080
version, so how many versions you will keep, and this is critical because it costs storage,

305
00:34:48,080 --> 00:34:56,080
so each version of your document is additional megabytes of your storage, and it costs a lot

306
00:34:56,080 --> 00:35:04,320
of problems in large organization, because one PowerPoint, one version of PowerPoint with

307
00:35:04,320 --> 00:35:10,720
a few slides, videos inside can cost you one gigabyte, so imagine that you have 50 versions of

308
00:35:10,720 --> 00:35:19,840
that file, so it will cost you 50 gigabytes, and usually organizations and with, you know,

309
00:35:19,840 --> 00:35:28,400
storages gone, and they need to buy additional storage, because they don't control versions,

310
00:35:28,400 --> 00:35:38,240
I'm envisioning is great for users, because I don't need to think about backup, I can go and

311
00:35:39,920 --> 00:35:45,520
check by the very first version of my document, and so on, but usually it doesn't need

312
00:35:45,520 --> 00:35:55,280
500 versions of a file, and this is very helpful from IT perspective to configure it before

313
00:35:55,280 --> 00:36:03,440
we start heavily using SharePoint, otherwise they will have to deal with it later, and fix,

314
00:36:03,440 --> 00:36:08,480
remove all those unnecessary versions, create communication with users, and so on,

315
00:36:08,480 --> 00:36:14,720
so I would add versioning, cache, and configuration part, critical about those, start with metadata,

316
00:36:14,720 --> 00:36:26,800
naming, conversion, and of course this versioning stuff, plus for security to provide additional

317
00:36:26,800 --> 00:36:34,720
security layer sensitivity, libraries from Microsoft PURV, this is also important, because it

318
00:36:34,720 --> 00:36:41,440
will add additional layer of security, so you can tag document if it's secured, not secured,

319
00:36:41,440 --> 00:36:47,200
maybe highly confidential, so add some additional encryption, add some additional header,

320
00:36:47,200 --> 00:36:52,480
footer information to those documents, this is also important, but add some additional layer of

321
00:36:52,480 --> 00:37:04,000
security. That's very useful, PURV, yes, I think what also often

322
00:37:04,000 --> 00:37:13,120
discussed is there are two, two red religions I think living when it's when document handles

323
00:37:13,120 --> 00:37:21,440
there, the one side is the religion of the four of us, and the other is the religion of the

324
00:37:21,440 --> 00:37:27,440
metadata, is these four or versus metadata debates still relevant actually?

325
00:37:32,320 --> 00:37:40,640
I think, well it depends, but the data are important, because it's critical, but it's so hard to

326
00:37:40,640 --> 00:37:48,640
implement and requires no proper training, so usually we end up with list columns with some

327
00:37:48,640 --> 00:37:59,760
lazy information or naming or some tags inside the document, but I'm from the metadata part,

328
00:37:59,760 --> 00:38:09,520
so I always encourage people to build or implement even basic metadata, policy metadata model,

329
00:38:09,520 --> 00:38:18,560
because it will help them later, and metadata are supported by copilot, so it's always also a good

330
00:38:18,560 --> 00:38:29,280
thing to, that's why you should use metadata. Then I think for a lot of people,

331
00:38:29,280 --> 00:38:37,280
as a normal user, they hear metadata and I think, oh I have to handle this,

332
00:38:37,280 --> 00:38:51,120
how many, how should they do it, or can I automate it to reduce this burden, or how did it

333
00:38:51,120 --> 00:39:03,040
show people handle their metadata? This is a good question, metadata model should be really

334
00:39:03,040 --> 00:39:09,440
simple, so users don't need to think about, you don't need to spend much time on finding proper

335
00:39:09,440 --> 00:39:17,120
tag for a document, so it must be simple, very basic, and tailored to data needs, class,

336
00:39:17,920 --> 00:39:22,960
right now we have a lot of automation tools, even from Microsoft, if you have copilot license,

337
00:39:22,960 --> 00:39:28,160
you can create a autofill columns in SharePoint in document libraries,

338
00:39:28,160 --> 00:39:36,720
so SharePoint will handle those no metadata extraction for you, so a SharePoint will

339
00:39:36,720 --> 00:39:43,040
or copilot will analyze the document and extract metadata and put inside columns,

340
00:39:45,440 --> 00:39:50,080
this is great stuff because you can upload documents, of course you should prepare those metadata

341
00:39:50,080 --> 00:39:57,280
beforehand, but if you have them, just upload documents, say that or type as a prompt,

342
00:39:57,280 --> 00:40:04,960
and extract all those information from your documents, and put inside metadata columns,

343
00:40:04,960 --> 00:40:10,320
so later on users can use those metadata to find documents, to use copilot, to find documents,

344
00:40:11,200 --> 00:40:18,560
to create some tables and so on, so right now if you have copilot license, you can use it and you can

345
00:40:18,560 --> 00:40:25,920
even configure it for your sites or user can upload documents and they will get those metadata

346
00:40:25,920 --> 00:40:35,040
just for free, of course generated by AI, but still it's much, much better than nothing.

347
00:40:35,680 --> 00:40:45,840
Yeah, yeah, it's cool that we know in the copilot part, so what have fundamentally changed

348
00:40:45,840 --> 00:40:48,320
when copilot enter the SharePoint environment?

349
00:40:48,320 --> 00:40:59,680
Oh, a lot, of course, but I think the biggest one is that now that knowledge level

350
00:41:03,680 --> 00:41:11,840
is much, much lower, so you need less knowledge to start working proper use SharePoint,

351
00:41:11,840 --> 00:41:19,360
so you don't need to understand all those, you know, fancy things, like content,

352
00:41:19,360 --> 00:41:24,240
type and so on, of course they are important, but for you you can start quickly

353
00:41:24,240 --> 00:41:31,600
creating your sites, managing your data, and treating your content, this is important,

354
00:41:31,600 --> 00:41:39,440
so that means all power users can create your templates or, you know, that basic configuration,

355
00:41:39,440 --> 00:41:46,080
but then users can quickly start working data without thinking about creating proper columns,

356
00:41:46,080 --> 00:41:53,680
extracting data, creating nice sites, nice pages from content, just they can do that like that,

357
00:41:53,680 --> 00:42:01,520
just five minutes pages ready to go, good looking, with proper information, you can just check it

358
00:42:01,520 --> 00:42:07,600
if it's correct, not correct, add something, so all those boring things

359
00:42:07,600 --> 00:42:12,320
are done by copilot, and this is great.

360
00:42:12,320 --> 00:42:24,880
When, will you say, do scopilot effectively turn SharePoint into an enterprise knowledge layer?

361
00:42:24,880 --> 00:42:32,800
No, or yes, it's going into that way, because now if you have a lot of information inside

362
00:42:32,800 --> 00:42:43,280
your SharePoint, you can use copilot to find it easier, to get to extract all those information from

363
00:42:43,280 --> 00:42:50,880
your documents, even right now from your SharePoint lists, properly tag them and use and build

364
00:42:50,880 --> 00:42:58,960
something based on those data, this is fantastic, so because if you have 5,000 documents in your site,

365
00:42:58,960 --> 00:43:05,840
you need to find the document, exor data manually, and do something with it, right now you can ask

366
00:43:05,840 --> 00:43:13,440
copilot, and copilot will find that document or relate documents, extract information, and even

367
00:43:13,440 --> 00:43:22,720
can build for your presentation, or HTML5, dynamic file with some dashboard related connected to your data,

368
00:43:22,720 --> 00:43:27,760
and this is fantastic, so those you can just focus on your work, on the data quality,

369
00:43:27,760 --> 00:43:35,280
not on those boring stuff, finding information and digging what's inside, and moving parts in PowerPoint,

370
00:43:35,280 --> 00:43:40,320
which is always quite thank you.

371
00:43:41,440 --> 00:43:52,560
So we can say it's copilot moving the SharePoint from finding the documents to give the answers,

372
00:43:52,560 --> 00:44:01,520
and when it do it, what kind of content can copilot understand from SharePoint content?

373
00:44:01,520 --> 00:44:08,640
Of course, Microsoft documents, this is the basic source of documents,

374
00:44:10,880 --> 00:44:19,040
back, all those text files, HTML files, markdown files, that's standard right now,

375
00:44:19,040 --> 00:44:26,640
back even, and this is great thing, even if you have videos in your SharePoint,

376
00:44:26,640 --> 00:44:33,600
copilot can understand it, copilot can, of course, you have to create all those no transcripts

377
00:44:33,600 --> 00:44:41,520
from your videos, but this is out of the box SharePoint, so then copilot can use those transcripts and

378
00:44:41,520 --> 00:44:49,120
give you information from your videos, from your training videos, from your meetings, and so on,

379
00:44:49,120 --> 00:44:57,520
so you have so many information right now in SharePoints, so you can use copilot to understand

380
00:44:57,520 --> 00:45:04,000
everything inside SharePoint, to be honest, and this, I mean, I love that, got it, can understand

381
00:45:04,000 --> 00:45:09,040
transcripts from my videos, this is, I have a lot of videos on my side, so

382
00:45:09,040 --> 00:45:19,920
and we think a lot about how can SharePoint help me to use SharePoint,

383
00:45:20,800 --> 00:45:26,960
can copilot also develop SharePoint, I don't know, web paths or something?

384
00:45:26,960 --> 00:45:35,120
At very basic level, right now yes, of course you can create HTML files,

385
00:45:35,120 --> 00:45:44,080
and this is very basic level of developing new content, but Microsoft will implement

386
00:45:46,720 --> 00:45:53,760
support for HTML files, so if you create an HTML file with some task board report, whatever,

387
00:45:53,760 --> 00:46:02,400
you will be able to insert into your asset library or pages library,

388
00:46:02,400 --> 00:46:09,120
and then it will be rendered inside SharePoint as a native SharePoint page, so in fact,

389
00:46:09,120 --> 00:46:17,600
every copilot user will be able to create some kind of application in HTML, using of course

390
00:46:17,600 --> 00:46:23,840
copilot out of the box, just like that, and it will be automatically displayed in SharePoint,

391
00:46:23,840 --> 00:46:28,800
it should be available, I think September or October, something like that,

392
00:46:28,800 --> 00:46:38,560
and this is the data, this basic level for power users, I would say that,

393
00:46:39,520 --> 00:46:47,600
but for if you need to create your own web paths, then copilot can be helpful, but it's not

394
00:46:47,600 --> 00:46:55,200
application designed for creating code, so you should skip, well you should move to

395
00:46:55,200 --> 00:47:00,880
a GitHub copilot, to create such web paths or something like that.

396
00:47:02,880 --> 00:47:09,120
And I think another topic, a lot of people actually discussed especially in SharePoint,

397
00:47:09,120 --> 00:47:15,760
but we talk a lot about copilot, and we talk about copilot, we talk about now at agents,

398
00:47:15,760 --> 00:47:19,760
and there are SharePoint agents, what are these SharePoint agents,

399
00:47:19,760 --> 00:47:24,320
what use case is there?

400
00:47:24,320 --> 00:47:31,040
Well, I think this feature, so SharePoint agents,

401
00:47:31,360 --> 00:47:38,880
where Microsoft released it last year, released that feature,

402
00:47:38,880 --> 00:47:46,240
so it was simply an dedicated agent grounded on your specific SharePoint site,

403
00:47:46,240 --> 00:47:52,880
dedicated document library, so that agent understands your content and gives you answers,

404
00:47:52,880 --> 00:47:58,560
so like that, so specific agent grounded on your selected data sources,

405
00:48:00,400 --> 00:48:08,320
so it simply can ask a given information about specific, for example, knowledge base,

406
00:48:08,320 --> 00:48:15,920
only your, all your HR data. Nice feature, but to be honest, it's kind of forgotten, because

407
00:48:15,920 --> 00:48:24,000
it's not so simple to find your agents right now, with the newest user interface,

408
00:48:25,920 --> 00:48:34,640
and well, it was a thing, right now it's kind of a abandoned feature, but the people don't use it so often.

409
00:48:34,640 --> 00:48:46,560
Well, I don't think that we lose something without agents, that's just, you can,

410
00:48:46,560 --> 00:48:53,360
anyway, you can use those agents, anyway, using copilot in SharePoint, so you can ask a question,

411
00:48:53,360 --> 00:48:59,680
and you will get answers, if there is an dedicated agent or not, so it's up to you, how you can,

412
00:48:59,680 --> 00:49:04,160
how you will configure it, just an additional thing.

413
00:49:04,160 --> 00:49:15,600
So, a lot of people say, SharePoint becomes the, yeah, the knowledge base of copilot,

414
00:49:15,600 --> 00:49:23,200
did you also see it, or is it more marketing story?

415
00:49:23,200 --> 00:49:30,960
Well, it is marketing, of course, but because we store documents in SharePoint,

416
00:49:30,960 --> 00:49:34,480
well, in fact, it is a data source for copilot, there's not a way.

417
00:49:34,480 --> 00:49:40,720
So, it is, if it's, you know, properly configured, properly governed,

418
00:49:42,400 --> 00:49:50,080
it's great, you will get great results, if not, you will get, no, well, sometimes even bad results,

419
00:49:50,080 --> 00:49:59,600
but bad information from copilot. So, this is, that's why you should think about SharePoint as

420
00:49:59,600 --> 00:50:04,000
your main data source in your organization, SharePoint and Teams in general.

421
00:50:06,000 --> 00:50:12,240
At SharePoint, this is the main knowledge source for everything in site copilot.

422
00:50:12,240 --> 00:50:21,280
Maze, even transcripts, one write, yes, but no SharePoint is the biggest one, the most critical one,

423
00:50:21,280 --> 00:50:24,240
so yeah, that's, of course, a lot of marketing, but for sure,

424
00:50:24,240 --> 00:50:32,160
because of the architecture, so it is the main source of your data, and copilot will use it,

425
00:50:32,160 --> 00:50:39,680
if you want, if you like it or not, simply. I think you are also, since years,

426
00:50:39,680 --> 00:50:48,400
passionable with automation, where do you power automate fit into modern world places,

427
00:50:48,400 --> 00:50:57,840
slash SharePoint? Yes, I do love power automate, because it gives me a lot of freedom,

428
00:50:57,840 --> 00:51:03,840
so I can automate my everyday tasks, I can move documents between libraries, I can know

429
00:51:03,840 --> 00:51:11,440
transfer data between data sources, I can create content inside SharePoint or do something,

430
00:51:11,440 --> 00:51:18,480
for example, if I get an email from specific customer, I can put it, save it in my SharePoint

431
00:51:18,480 --> 00:51:25,200
folder, in my SharePoint library, dedicated site, and maybe send additional notification to my team,

432
00:51:25,200 --> 00:51:30,320
to my colleagues, and so on, so it's great, it can automate a lot of stuff,

433
00:51:30,320 --> 00:51:37,520
even of course, you can automate SharePoint itself, so create sites, create libraries,

434
00:51:37,520 --> 00:51:44,080
add additional permissions to your site based on something, based on, for example, new employees,

435
00:51:44,080 --> 00:51:51,440
so it's great, and now with copilot, you can even create your own

436
00:51:52,880 --> 00:51:58,640
power automate flows, or ask copilot to help you with power automate, so it's so simple that it's

437
00:51:58,640 --> 00:52:10,000
a thing to not to use it really. Okay, I think is there when or why show what

438
00:52:10,000 --> 00:52:20,320
place has power automate now, because we can do all sorts of code pilot, when we

439
00:52:21,280 --> 00:52:26,160
show it shows power automate instead of a copilot or an AI.

440
00:52:26,160 --> 00:52:34,880
Right now still copilot is not able to know, to fully automate a lot of tasks,

441
00:52:34,880 --> 00:52:41,040
while it can give you answers, it can give you information about your content,

442
00:52:41,040 --> 00:52:46,640
and it can do something right now, even in SharePoint, for example, create documents,

443
00:52:46,640 --> 00:52:55,600
yeah, so HTML files in the future, so it's great, but if you, but it's still AI, it's

444
00:52:55,600 --> 00:53:04,240
generally it can behave a bit different each time, so your results can be different from time to time,

445
00:53:04,240 --> 00:53:10,960
today it can create a document that way, but next month it can be a bit different, or even tomorrow,

446
00:53:11,680 --> 00:53:19,920
but with power automate you are sure that each outcome, each output will be the same, because you can

447
00:53:19,920 --> 00:53:25,920
clearly define it, you can use copilot inside power automate as well, but still you define it from

448
00:53:25,920 --> 00:53:31,360
the very first step to the very last step, so you have full control over what's going on your

449
00:53:31,360 --> 00:53:41,360
automation, so copilot yes can do a lot, but more from information perspective, our automates more

450
00:53:41,360 --> 00:53:52,080
from no automation from first step, last step, so if you need that, if you must be sure,

451
00:53:52,080 --> 00:54:03,360
so you will use power automate. Yeah, awesome, I have every round, a rapid fire round, so I give

452
00:54:03,360 --> 00:54:12,480
short questions and you give a short, short answer, so yeah, power mate or AI agent,

453
00:54:12,480 --> 00:54:23,280
power automate, search for our copilot, copilot I think, most underrated SharePoint feature,

454
00:54:25,200 --> 00:54:37,280
oh, underrated, oh well I think search, okay, what should I take to eat when I come to Warsaw?

455
00:54:37,280 --> 00:54:46,960
I would bet, I think Polish dumplings, pierogi, oh yeah they are really good,

456
00:54:50,640 --> 00:55:01,760
Cheap Chat or channel? Well I'm channel the guy, channel, when sat yandere calls today and say you

457
00:55:01,760 --> 00:55:07,280
get all the money and resources you need to build your dream feature for SharePoint, what will it be?

458
00:55:07,280 --> 00:55:13,840
Oh, oh, that's that's tricky one, I don't know, I don't have so many of them,

459
00:55:17,440 --> 00:55:24,560
well I will simplify permissions inside SharePoint, managing permissions,

460
00:55:24,560 --> 00:55:30,960
what is the biggest SharePoint mistake? Oh,

461
00:55:30,960 --> 00:55:36,000
last mistake,

462
00:55:41,600 --> 00:55:50,240
item tall, when, who should I invite next and what question should I ask?

463
00:55:50,240 --> 00:56:02,320
Who I think from my perspective, the most positive because he's a great guy and he knows a lot about

464
00:56:02,320 --> 00:56:18,560
bar or homemade? Awesome, okay, yeah then, yeah then my, I can say thank you for for for for

465
00:56:18,560 --> 00:56:26,960
this round, this was really cool and yeah I think yeah we have learned a lot with the what mistakes

466
00:56:26,960 --> 00:56:36,720
people do or organizations and I think yeah for for the most people I can say give SharePoint another chance

467
00:56:36,720 --> 00:56:44,720
for sure definitely, when you handle it great it's a great great tool especially in the age of AI

468
00:56:44,720 --> 00:56:52,640
and yeah I think they are it's I don't know 25 years or so as SharePoint also I think that

469
00:56:52,640 --> 00:56:58,720
even the next 25 years brings and for all the listeners you find the vaccines,

470
00:56:58,720 --> 00:57:07,360
information all in the show notes on the M65M page and yeah thank you so many for for the time

471
00:57:07,360 --> 00:57:14,880
you have spent here with me and give give your insights. Thank you very much.

472
00:57:14,880 --> 00:57:17,840
(wind blowing)