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

For years, SharePoint has carried a reputation for complicated document libraries, outdated intranets, confusing navigation, too many sites, and information that employees simply cannot find. But Microsoft 365 is changing, and Copilot is making SharePoint more important than it has been in a long time.In this episode of the M365 FM Podcast, Mirko Peters talks with Microsoft MVP Marcin Siewnicki about how SharePoint is evolving from a traditional document and intranet platform into a central information and knowledge layer for the modern workplace. Marcin has worked with SharePoint since the SharePoint 2003 era, giving him more than two decades of perspective on how the platform has changed.

WHY SHAREPOINT GOT A BAD REPUTATION
Much of SharePoint’s reputation was created by the way organizations implemented it. Intranets were often designed by IT, heavily customized, difficult to use, and disconnected from what employees actually needed.Instead of continuously gathering feedback and improving the experience, many companies delivered an intranet and expected employees to adapt to it. The result was complex navigation, outdated content, overloaded pages, and systems people avoided whenever possible.

INFORMATION ARCHITECTURE BEFORE TECHNOLOGY
One of the biggest problems is not SharePoint itself but how information is organized inside it. Without a clear information architecture, SharePoint can quickly become a huge shared folder filled with duplicated files, outdated information, unclear ownership, and multiple versions of the same document.Marcin explains why organizations should start with a simple structure, understand their data, remove unnecessary content, and introduce basic metadata. Information architecture does not have to be complicated to make SharePoint significantly easier to use.

BUILDING A MODERN SHAREPOINT WORKPLACE
A modern SharePoint homepage should not become an endless collection of web parts, corporate announcements, applications, and links. It should be simple, personalized, visually clear, and focused on what employees actually need.Communication sites can provide departments and organizations with modern, mobile-friendly publishing experiences without requiring the enormous custom intranet projects that were common in the past. The focus should be on useful information, important applications, relevant documents, straightforward navigation, and strong search capabilities.

SOLVING THE SHAREPOINT NAVIGATION PROBLEM
Navigation remains one of SharePoint’s biggest challenges. Organizations frequently attempt to expose every department, application, resource, and internal page through a single navigation structure.Marcin explains why simpler navigation usually works better. Global navigation should focus on the most important destinations, while detailed navigation can be provided closer to individual departments, sites, and business areas. Otherwise, navigation itself becomes another information problem.

SHAREPOINT AND TEAMS SPRAWL
Microsoft Teams and SharePoint are deeply connected. Every new Team and many Teams channels can introduce additional SharePoint resources, which means uncontrolled Teams creation can quickly become uncontrolled SharePoint growth.Organizations therefore need simple creation processes, templates, basic metadata, lifecycle management, and user education. Employees should understand when they need a Team, when a SharePoint site is sufficient, and what happens behind the scenes when these collaboration environments are created.One useful way of looking at the relationship is to think of Microsoft Teams as the collaboration interface while SharePoint provides much of the document and information layer underneath it.

GOVERNANCE WITHOUT KILLING INNOVATION
Governance does not need to mean preventing employees from using new technology. The goal is to provide enough freedom for people to work effectiv

Hello everybody and welcome back to the Amsti65FAM podcast.

For years SharePoint has had a reputation problem.

Ask many employees what they think about SharePoint and you will hear

familiar answers, complicated document libraries, outdated

intranets, impossible navigation, too many sites and

information nobody can find.

Microsoft 365 is changing and AI could fundamentally change the

role SharePoint plans inside modern workplaces because when co-pilot needs

organization knowledge documents permissions context and business

information, suddenly the way we structure SharePoint becomes extremely

important. My guest today is Martin C. Vesnik,

Microsoft 365 solution architect with more than 20 years experience of

creating an implementing business application based on SharePoint

and Microsoft 365. Massive specialized in building modern workplaces using

SharePoint, Microsoft Teams, Power Platform, Power Automate and

increasingly co-pilot. He is also active in the Microsoft community,

co-organized the SharePoint Saturday, Waslove and regulated speaks at community

events. Today we are going to explore how SharePoint and Teams fit

together, why traditional intranets need to evolve and how

co-pilot change information is covering, what organizations need to fix

before introducing AI and what AI power modern workplaces could look like in the

next few years. Martin, welcome to the MC65athon podcast.

Hello everyone, thank you for the great introduction.

Awesome, so you started in the IT 20-5, how did you only get into SharePoint?

Well, that was my very first real IT job and the company simply used SharePoint

where it was SharePoint on-prem version 2003 so it was quite

old one, looking from now. So I started working at SharePoint

as a user, power user, add the mean and customizing in building

solutions based on SharePoint. It was pretty interesting,

no path from the simple user so I had to use documents, upload documents,

create lists, items, records and so on.

And I ended up with a pretty advanced solution on SharePoint on-premises

within a few years. Awesome, and now yeah, I think

when, what will you say with did SharePoint look like when you started

compared to the platform we have today?

Oh, that's interesting question, well it was complex solution

back in the days. You had to know what you want to do,

how you want to do that task and so on, you had to understand the platform

correctly. It was a pretty complex solution because

sometimes simple change could damage entire site, entire library or even

portal. So yeah, it was a complex solution, you had to use additional tools

to create pages, to create complex library views or

list views or add some automation. You had to use additional tools and

know really you had to know what you are doing.

But right now I think it's the best time for SharePoint

because that knowledge level is pretty low. You can start quickly working SharePoint,

you can work with your documents, sites, with your data in general

and you don't need to think how to create library, how to create

least, how to connect the data. It's pretty simple, for some level,

so you can use SharePoint features, functions, pretty quickly and

build what you need. Of course, if you need more, more complex solutions, you need

to understand and know much more but that basic level, that user

level or even power user level is pretty low now and you can

extremely quickly start working with SharePoint and that's amazing,

comparing to 20 years ago or even 10 years ago, it was just, you know, like day and night.

And yeah, the most employees I know from different companies,

they don't like SharePoint very much. It's had these bad

reputation so we also titled it, "Shaport is boring anymore"

but why did you think SharePoint have these bad reputation?

I think that because I saw many, many implementations,

that implementations, so simply organization created complex

intranet solutions with a lot of wet parts, a lot of, you know,

customizations, it was, first of all, usually it was ugly, simply ugly.

It wasn't prepared for employees, it was simply IT solution,

built by IT and employees had to use it, simply.

So it was simply hard to use complex and usually outdated

on the very first date. And I had to use some of those

intranets and it wasn't the best experience to be honest.

So I know why, why still have bad reputation because it's, well, we,

IT guys, IT staff, built that reputation,

and future actually. So is it because I don't know the IT

things, they build something great or build, we build, we

intranets based on what the management things instead of what

employees actually need. So did we have, I don't know, a feedback, feedback

looks or something? Yes, I saw it many times that, that thing

that loop was simply broken, IT gathered requirements,

built something based on those requirements, and that's it.

Simply, so the solution is done, intranet is done,

Ray, you have to, you have to use that portal and live with that.

And what, what did you think, how much of the problem comes from the information

architecture and how much comes from governance?

I think the biggest one is information architecture because usually people don't

know how to use, how to build it, don't know even what it is.

So this is just, no, skipped or nonexisting part of the project.

So just put a lot of data inside into the SharePoint and

use it. So usually SharePoint is a

shared folder for huge bucket for everything. So there's no

information architecture. And then it's hard to find information, hard to find

documents. Usually you have five, ten, twenty versions of the same document

and you don't know which one is correct, which one is

currently used, which one is outdated.

Maybe archived and so on. So it's, I think that information architecture is the

biggest pain point in Manage SharePoint implementation.

And this is also, governance is also important, but

it's from the IT and security perspective.

For users, for everyday work, everyday tasks,

information architecture is the biggest thing I think.

Yeah, but when we forget everything about the

traditional SharePoint internet, what do

modern SharePoint architecture look like?

Well, the best one, of course, the modern one,

something that has been always in the SharePoint. So metadata

properly implemented or it can be based, basically, metadata implementation,

but it must be created before we start

working with documents. And then we need to understand our own data and

hit it, simple, remove all those duplicates, all those

unnecessary data because it makes just chaos in inside SharePoint.

So if it's simple, if we know what we want to achieve and if we have metadata,

even basic one, actually, that's good enough for most of

implementation, most of companies.

And when we start the homepage of a modern digital workplace,

what should it actuary accomplish? Home page, that's interesting.

Home page, well, the best one is that it's a bit personalized, so it shows

what I need to do, my data, my own information,

and so on. So it should be somehow attached to my own

information. Of course, it should be good looking

home page because we have nice and beautiful pages,

but it should be personalized and it should contain all those information that I

probably need, should use. So my applications, my documents,

pretty simple navigation, not too complex. This is

GQ1, not too complex. And of course, search, right now, copy lots,

it's a bit different, but

that's the thing, not too complex. So pretty simple, I saw many, many

home pages that I don't know, maybe even four pages,

hate, so it's, you know, scroll down, scroll down, and oh, that's the thing that I was

looking for. No, if it's not on that top page, it won't be used to be honest.

And normally say how important are communication sites today?

I think this is the most important part because if we use SharePoint sites,

we need to come, we want to communicate something,

and communication sites are, though, pretty, they are properly implemented,

those out of the box templates are, I think, good enough for most

organizations. And if it's implemented with basic information, it's good enough.

You can easily, I use it as even as your intranet portal,

simply good enough, basic information, basic news, some links,

good looking, mobile, friendly, that's great. And I think,

also about mobile, that this is extremely important right now because usually

I spend a lot of time on my phone and store my SharePoint

sites or my customer sites. And if it's not working on my mobile, I probably

won't use it. Yeah, and we have the other,

I think, how do they fit into the architecture?

Yeah, it's a nice concept, but many organizations don't know how to use it,

because it's simply connection between sites. Right now we don't have,

no, this commonly used back in the days, architecture,

when you have site and multiple subsides, but that pattern is gone

fortunately. But now we can connect different sites together to just know,

to make it simple and consistent navigation between sites consistent,

template, look and feel. So it's nice, nice concept,

pretty simple, pretty simple to continue to use. But my experience,

many organizations simply don't use it. I don't know why, maybe to

complex, maybe to, maybe they don't know. I just simple and

quite powerful. I like it. Yeah, and I think when I talk to,

I don't know, I'm not so deep in the SharePoint topic, it's for me it's more

to organize data, but when I talk to people, the one of the core problems I think they have,

it's the navigation, they don't understand the navigation.

How should organizations think about navigation on SharePoint pages?

Yeah, this is pretty important to, and to be honest, SharePoint still has problems with it,

because it should be simple, but contains all required information, all required links,

and usually you don't have links properly divided into categories or so,

but if you create or gather all links, filter only, or filter out all those

unnecessary, leave only those required and important, usually you have pretty long list,

and it's not so simple to put all those links in modern SharePoint navigation, because

no, you have to create complex, you know, those mega menu with categories, links, sublinks,

and so on, and it's complex in SharePoint still. So what works is that it must be simple,

really, only basic links to the most important part of your organization,

to departments, to their critical applications, and on that target site, you can have no more

detailed navigation, because otherwise it just complex, you know, monster with hundreds of links,

and you usually use those as well, lost in those links, and last, it's, I don't know,

it's still a thing in SharePoint that it's not so easy to create navigation, to modify it,

you need to go and write for a while with this editing tool, so I think this is the thing,

the part of the store point that there are a lot of no space for improvement right now.

And, well, I think what's also make is the little bit problem, it's, we have a lot of SharePoint,

it's, yeah, we have the SharePoint sprawl problem, and it's so much stuff in there, because it's

connected to two teams, and so some companies have connected it to one drive and so on.

How can we prevent these sprawl in SharePoint? What's your tips here?

Oh, that's complex one, and I face it to be honest every day. I think every, every,

every single customer, they use it that way, so they create a lot of teams, a lot of SharePoint sites,

in SharePoint, and they are lost, because you have a lot of teams, a lot of

no channels, and every channel can have our SharePoint sites, and then

the dedicated SharePoint sites, so it's pretty complex for managing, for finding information,

and for governance, and for permissions, it can be a really painful one, but

the best, or maybe not the best, but it works pretty good, pretty well, this is

approach that people need to create sites based on some kind of template, and even teams,

so they need to provide information about why they need to create that site, and provide basic

metadata for a site, and the same way for teams, so then you can create a list, manage those sites,

manage those teams, and more or less you will be able to know what is inside each site, or inside

each team, but from the end user perspective, well, it's still a thing to understand

what's the difference between SharePoint and Teams, usually they don't know, so you need to simply

educate them, provide some training, because otherwise they will still use SharePoint as

something, storage, bucket, and teams have a storage bucket in Teams, so they don't know what's

the difference, and they put everything inside, no matter what it is.

Yeah, that's interesting, I think these, yeah, because SharePoint and Teams are

closely connected technically, but yeah, you say many users don't understand that

relationship, how do you explain it?

Basic, one, maybe, to pay one teacher, simply one, very basic documents with all those information,

and use cases, so when you need to use SharePoint, when you need to use Teams, what's good for

this specific use cases for this specific scenario, so users can simply know, check, oh, I need to

communicate a lot, so I should create a team, a team inside Teams, or maybe I need just documents

and share them with my external parties, partners, vendors, whatever, so I don't need Teams,

I can stay with SharePoint, so I create a SharePoint site, it will be no good enough, so I don't

need to create all those additional layers of communication, and it must be tailored to the

specific organization, because usually wherever organization is different, so it should be,

a dose scenario should be, should match specific organization, then users will be, no, they will

more, they will understand it better simply.

Can we say Teams should be considered the user interface while SharePoint becomes the information

layout, then is it? Yeah, that's, yeah, we can say that. And what I see is also when we talk about

SharePoints Pro, we also have to talk about Teams Pro, so a lot of organizations create, so-so-so-them,

many Teams, Locals, Birthday Party, and Project Final 7, and so on, how should we

take care or of it? Yeah, this is the governance part, and the best way is to start with

governance before we let users create a lot of Teams, but usually right now everyone has Teams,

so it's a lot of Teams inside Teams, but implementing proper governance I think is the

critical part, because then we can, or admins can understand what's going on in their own tenant,

how many Teams are used, outdated, orphaned, and so on, so proper governance, it can be

even simple, simple SharePoint or maybe Microsoft Forms, Form with basic information that

users should provide, and basic SharePoint list with approval and so on, so nothing, nothing

fancy, just simple, simple stuff, and then, and to be honest, even in large, I have one customer,

50, more than 50,000 users, so it's not the simple, not the small one, basic Microsoft Form,

basic SharePoint list, it's good enough, and it is working, really, really good, really well,

and class, there are many, many sort of features, yeah, features, many features inside SharePoint,

admin center right now, that you can use to simply add some governance layer, so admins can

send dedicated messages to SharePoint site owners, so in fact, Teams as well,

to check if there's still need that site, need that team, if not that

site can be archived automatically, or put to, or simply removed if you need it,

you don't need those data anymore, so Microsoft implemented a few really, really needed features

in that, in that governance area. I think when people are going and they often

figure, for they often sounds like the opposite of innovation, how do you balance these two

yeah, sites? Yeah, innovations, of course it's nice to have the best to create everything,

not to be governed, but usually there must be some kind of governor, some, someone

should check what we are doing, what users are doing, otherwise there will be mess chaos,

ants, data will be no leaking everywhere, so there must be a balance between

you know, those innovations extremely useful, many times features,

and of course, governor security, so admins always need to keep an eye on the data,

on the security part, ad-keyf, or maybe configure it properly, then users can use what's

new, what's, you know, best for the work, but still keep their own data secured and

properly governed, that's always tricky one, because you find that balance between what's new,

what's, you know, innovations, you've users everything, but still keep everything secured.

And when we think about, especially when we talk about security, but is it,

did you think governance is an IT topic and should it be governed centrally or is it?

It is IT topic for sure, but there must be a consistent governance model for everything, not only for

Sherpo, because Sherpo is one part, but we have sensitivity labels, of course for documents,

for information, for teams, for sites, for third-party applications, not from Microsoft,

so it must be created or managed centrally, but IT is the critical part, but together with

management and with key business users, because they will use that system anyway, and if you create

these two complex, they will, as usual, find a workout and don't use it, or maybe for example,

skip a sensitivity labels or safe data on, on devices, not on the SharePoints, so it's, I think

that everything must be involved in the governance process, otherwise it's just, no, people will

always find a workout, if not, no, say the best, the best workout is if you do not provide a proper

governance for AI, for example, and proper tools for users, they will use own devices, create

screenshots and send it to own charge PT, so anyway, data will be lost, but people will do what they want.

Yeah, awesome. I think a little bit about when companies start with governance, you say they

should start with governance at the first time, so what are the main governance policies you

should establish for SharePoint and Teams? So the very first one is that SharePoint or SiteWare

Teams is still in use, so check every, no, periodically, for example, every six months, if that specific

site or team is still in use, if not, maybe we should archive it, maybe we should remove it, maybe

is accessible, so some kind of test, test one, there are plenty of test sites, test teams, we can

simply remove it from our tenant. The next one is, no, check permissions, it's obligatory to have

that policy to check periodically every few months, at least once a year, so push site owner or site

owners, team owners to check their own permissions, because usually users, they would have many

colleagues, so that's site or Teams. External practice, external users, usually after some time,

you have nice, beautiful SharePoint site with hundreds or even thousands, external links,

and you are not able to check who has access to that specific file, and simply you can create it,

well, you create that and over sharing problem, so you can't control data, you can't control

permissions, and you can even share your own data outside of your organization, and this is critical.

Fortunately, Microsoft is implementing right now these hero links, so instead of

having multiple links to one file, we will have one single link,

to a file or to a folder, and you can simply add more permissions to that link, remove some permissions,

so only one specific link, so it will be much, much easier to manage, but still, this is critical

policy to check every few months permissions, if it's correct, if they are correct, not correct,

maybe you should remove. Many, many obsolete permissions, you know, those links with permissions,

this is critical, and of course, I think the basic one is to, of course, it depends on the organization,

but a form or a simple process that users should use to create size or teams, at some level,

it is critical, so you should somehow create that process, it can be very basic, and to be honest,

it should be basic, even in large enterprise, huge enterprises, it must be simple one, so simple

information, but then people think twice before they create a site or a team, so provide business

justification, why you need that site, is it so important to create another test site, or test

birthday party, or whatever, or maybe you can use your own one drive to put those files inside it,

so this will greatly minimize those no theft, test sites, test teams, and provide some

no basic metadata for your content, this is important.

I think one of the topics, especially in governance, is automation, so

what did you think, should companies, world-based, power, share, graph, ARP, or use tools like,

I don't know, RENCORE, BCC, script runner, what's your view here?

Be honest,

there are plenty of tools, of course, power share or power upgrade and graph,

this is the minimum, I think, must have for every admin, if you think about governance,

because they can provide you with the data, they provide everything you need, access to sites,

manage sites, other permissions, and so on, so power share and graph, I think, is the basic.

Of course, if you have complex environments, you can add some additional

fair-party tools, why not RENCORE, share gate, whatever you need, but of course, they take cost more,

but you don't deal with automation, and those scripts, that's great, but usually, I think,

power share may be power-alchemy with graph, it's good enough for most cases,

and usually I use power-alchemy with graph, or maybe, as your logic apps for,

for more demanding tasks, but graph is great.

I think, when we go back to what is SharePoint, I think,

what do people think about SharePoint is still heavily associated with documents?

What do the good document management look like today, especially in SharePoint?

Yeah, documents, we use documents every day, so that's why we need to think about SharePoint as a

document storage, in general, it's a storage for documents for data. So, first of all, of course,

well, the best one is to understand your data, so you need to provide some kind of metadata

management, model, maybe, and it's something that will help users' tag documents at some categories,

maybe, and give them some help with naming convention, because usually, you know, name files,

something, something, and version 1, version 2, final version, something, test version,

whatever, draft, second draft, so naming convention is important, some basic metadata is also

important, so they simply can be discovered easily. And a few things about configuration also is

important from IT perspective, so the very basic, very important, very critical one is, of course,

version, so how many versions you will keep, and this is critical because it costs storage,

so each version of your document is additional megabytes of your storage, and it costs a lot

of problems in large organization, because one PowerPoint, one version of PowerPoint with

a few slides, videos inside can cost you one gigabyte, so imagine that you have 50 versions of

that file, so it will cost you 50 gigabytes, and usually organizations and with, you know,

storages gone, and they need to buy additional storage, because they don't control versions,

I'm envisioning is great for users, because I don't need to think about backup, I can go and

check by the very first version of my document, and so on, but usually it doesn't need

500 versions of a file, and this is very helpful from IT perspective to configure it before

we start heavily using SharePoint, otherwise they will have to deal with it later, and fix,

remove all those unnecessary versions, create communication with users, and so on,

so I would add versioning, cache, and configuration part, critical about those, start with metadata,

naming, conversion, and of course this versioning stuff, plus for security to provide additional

security layer sensitivity, libraries from Microsoft PURV, this is also important, because it

will add additional layer of security, so you can tag document if it's secured, not secured,

maybe highly confidential, so add some additional encryption, add some additional header,

footer information to those documents, this is also important, but add some additional layer of

security. That's very useful, PURV, yes, I think what also often

discussed is there are two, two red religions I think living when it's when document handles

there, the one side is the religion of the four of us, and the other is the religion of the

metadata, is these four or versus metadata debates still relevant actually?

I think, well it depends, but the data are important, because it's critical, but it's so hard to

implement and requires no proper training, so usually we end up with list columns with some

lazy information or naming or some tags inside the document, but I'm from the metadata part,

so I always encourage people to build or implement even basic metadata, policy metadata model,

because it will help them later, and metadata are supported by copilot, so it's always also a good

thing to, that's why you should use metadata. Then I think for a lot of people,

as a normal user, they hear metadata and I think, oh I have to handle this,

how many, how should they do it, or can I automate it to reduce this burden, or how did it

show people handle their metadata? This is a good question, metadata model should be really

simple, so users don't need to think about, you don't need to spend much time on finding proper

tag for a document, so it must be simple, very basic, and tailored to data needs, class,

right now we have a lot of automation tools, even from Microsoft, if you have copilot license,

you can create a autofill columns in SharePoint in document libraries,

so SharePoint will handle those no metadata extraction for you, so a SharePoint will

or copilot will analyze the document and extract metadata and put inside columns,

this is great stuff because you can upload documents, of course you should prepare those metadata

beforehand, but if you have them, just upload documents, say that or type as a prompt,

and extract all those information from your documents, and put inside metadata columns,

so later on users can use those metadata to find documents, to use copilot, to find documents,

to create some tables and so on, so right now if you have copilot license, you can use it and you can

even configure it for your sites or user can upload documents and they will get those metadata

just for free, of course generated by AI, but still it's much, much better than nothing.

Yeah, yeah, it's cool that we know in the copilot part, so what have fundamentally changed

when copilot enter the SharePoint environment?

Oh, a lot, of course, but I think the biggest one is that now that knowledge level

is much, much lower, so you need less knowledge to start working proper use SharePoint,

so you don't need to understand all those, you know, fancy things, like content,

type and so on, of course they are important, but for you you can start quickly

creating your sites, managing your data, and treating your content, this is important,

so that means all power users can create your templates or, you know, that basic configuration,

but then users can quickly start working data without thinking about creating proper columns,

extracting data, creating nice sites, nice pages from content, just they can do that like that,

just five minutes pages ready to go, good looking, with proper information, you can just check it

if it's correct, not correct, add something, so all those boring things

are done by copilot, and this is great.

When, will you say, do scopilot effectively turn SharePoint into an enterprise knowledge layer?

No, or yes, it's going into that way, because now if you have a lot of information inside

your SharePoint, you can use copilot to find it easier, to get to extract all those information from

your documents, even right now from your SharePoint lists, properly tag them and use and build

something based on those data, this is fantastic, so because if you have 5,000 documents in your site,

you need to find the document, exor data manually, and do something with it, right now you can ask

copilot, and copilot will find that document or relate documents, extract information, and even

can build for your presentation, or HTML5, dynamic file with some dashboard related connected to your data,

and this is fantastic, so those you can just focus on your work, on the data quality,

not on those boring stuff, finding information and digging what's inside, and moving parts in PowerPoint,

which is always quite thank you.

So we can say it's copilot moving the SharePoint from finding the documents to give the answers,

and when it do it, what kind of content can copilot understand from SharePoint content?

Of course, Microsoft documents, this is the basic source of documents,

back, all those text files, HTML files, markdown files, that's standard right now,

back even, and this is great thing, even if you have videos in your SharePoint,

copilot can understand it, copilot can, of course, you have to create all those no transcripts

from your videos, but this is out of the box SharePoint, so then copilot can use those transcripts and

give you information from your videos, from your training videos, from your meetings, and so on,

so you have so many information right now in SharePoints, so you can use copilot to understand

everything inside SharePoint, to be honest, and this, I mean, I love that, got it, can understand

transcripts from my videos, this is, I have a lot of videos on my side, so

and we think a lot about how can SharePoint help me to use SharePoint,

can copilot also develop SharePoint, I don't know, web paths or something?

At very basic level, right now yes, of course you can create HTML files,

and this is very basic level of developing new content, but Microsoft will implement

support for HTML files, so if you create an HTML file with some task board report, whatever,

you will be able to insert into your asset library or pages library,

and then it will be rendered inside SharePoint as a native SharePoint page, so in fact,

every copilot user will be able to create some kind of application in HTML, using of course

copilot out of the box, just like that, and it will be automatically displayed in SharePoint,

it should be available, I think September or October, something like that,

and this is the data, this basic level for power users, I would say that,

but for if you need to create your own web paths, then copilot can be helpful, but it's not

application designed for creating code, so you should skip, well you should move to

a GitHub copilot, to create such web paths or something like that.

And I think another topic, a lot of people actually discussed especially in SharePoint,

but we talk a lot about copilot, and we talk about copilot, we talk about now at agents,

and there are SharePoint agents, what are these SharePoint agents,

what use case is there?

Well, I think this feature, so SharePoint agents,

where Microsoft released it last year, released that feature,

so it was simply an dedicated agent grounded on your specific SharePoint site,

dedicated document library, so that agent understands your content and gives you answers,

so like that, so specific agent grounded on your selected data sources,

so it simply can ask a given information about specific, for example, knowledge base,

only your, all your HR data. Nice feature, but to be honest, it's kind of forgotten, because

it's not so simple to find your agents right now, with the newest user interface,

and well, it was a thing, right now it's kind of a abandoned feature, but the people don't use it so often.

Well, I don't think that we lose something without agents, that's just, you can,

anyway, you can use those agents, anyway, using copilot in SharePoint, so you can ask a question,

and you will get answers, if there is an dedicated agent or not, so it's up to you, how you can,

how you will configure it, just an additional thing.

So, a lot of people say, SharePoint becomes the, yeah, the knowledge base of copilot,

did you also see it, or is it more marketing story?

Well, it is marketing, of course, but because we store documents in SharePoint,

well, in fact, it is a data source for copilot, there's not a way.

So, it is, if it's, you know, properly configured, properly governed,

it's great, you will get great results, if not, you will get, no, well, sometimes even bad results,

but bad information from copilot. So, this is, that's why you should think about SharePoint as

your main data source in your organization, SharePoint and Teams in general.

At SharePoint, this is the main knowledge source for everything in site copilot.

Maze, even transcripts, one write, yes, but no SharePoint is the biggest one, the most critical one,

so yeah, that's, of course, a lot of marketing, but for sure,

because of the architecture, so it is the main source of your data, and copilot will use it,

if you want, if you like it or not, simply. I think you are also, since years,

passionable with automation, where do you power automate fit into modern world places,

slash SharePoint? Yes, I do love power automate, because it gives me a lot of freedom,

so I can automate my everyday tasks, I can move documents between libraries, I can know

transfer data between data sources, I can create content inside SharePoint or do something,

for example, if I get an email from specific customer, I can put it, save it in my SharePoint

folder, in my SharePoint library, dedicated site, and maybe send additional notification to my team,

to my colleagues, and so on, so it's great, it can automate a lot of stuff,

even of course, you can automate SharePoint itself, so create sites, create libraries,

add additional permissions to your site based on something, based on, for example, new employees,

so it's great, and now with copilot, you can even create your own

power automate flows, or ask copilot to help you with power automate, so it's so simple that it's

a thing to not to use it really. Okay, I think is there when or why show what

place has power automate now, because we can do all sorts of code pilot, when we

show it shows power automate instead of a copilot or an AI.

Right now still copilot is not able to know, to fully automate a lot of tasks,

while it can give you answers, it can give you information about your content,

and it can do something right now, even in SharePoint, for example, create documents,

yeah, so HTML files in the future, so it's great, but if you, but it's still AI, it's

generally it can behave a bit different each time, so your results can be different from time to time,

today it can create a document that way, but next month it can be a bit different, or even tomorrow,

but with power automate you are sure that each outcome, each output will be the same, because you can

clearly define it, you can use copilot inside power automate as well, but still you define it from

the very first step to the very last step, so you have full control over what's going on your

automation, so copilot yes can do a lot, but more from information perspective, our automates more

from no automation from first step, last step, so if you need that, if you must be sure,

so you will use power automate. Yeah, awesome, I have every round, a rapid fire round, so I give

short questions and you give a short, short answer, so yeah, power mate or AI agent,

power automate, search for our copilot, copilot I think, most underrated SharePoint feature,

oh, underrated, oh well I think search, okay, what should I take to eat when I come to Warsaw?

I would bet, I think Polish dumplings, pierogi, oh yeah they are really good,

Cheap Chat or channel? Well I'm channel the guy, channel, when sat yandere calls today and say you

get all the money and resources you need to build your dream feature for SharePoint, what will it be?

Oh, oh, that's that's tricky one, I don't know, I don't have so many of them,

well I will simplify permissions inside SharePoint, managing permissions,

what is the biggest SharePoint mistake? Oh,

last mistake,

item tall, when, who should I invite next and what question should I ask?

Who I think from my perspective, the most positive because he's a great guy and he knows a lot about

bar or homemade? Awesome, okay, yeah then, yeah then my, I can say thank you for for for for

this round, this was really cool and yeah I think yeah we have learned a lot with the what mistakes

people do or organizations and I think yeah for for the most people I can say give SharePoint another chance

for sure definitely, when you handle it great it's a great great tool especially in the age of AI

and yeah I think they are it's I don't know 25 years or so as SharePoint also I think that

even the next 25 years brings and for all the listeners you find the vaccines,

information all in the show notes on the M65M page and yeah thank you so many for for the time

you have spent here with me and give give your insights. Thank you very much.

(wind blowing)