Microsoft 365 Community Microsoft 365 PnP Weekly, 9 Mar 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Microsoft 365 PnP Weekly – Episode 117

Description

In this installment of the weekly discussion revolving around the latest news and topics on Microsoft 365, hosts – Vesa Juvonen (Microsoft) | @vesajuvonen, Waldek Mastykarz (Microsoft) | @waldekm, are joined by Microsoft Belgium-based Senior Service Engineer - Bert Jansen | @o365bert. This episode’s discussion focuses on why Partners would be interested in Microsoft 365, on site migrations – On-prem to cloud – Classic to modern, and on modern pages - APIs, Microsoft Graph and PnP Core SDK. A blog busting 23 articles and videos were published by Microsoft and Community members in the last week. This session was recorded on Monday, March 8, 2021.

References:
• See the full blog post for this episode at https://aka.ms/M365DevBlog
• Download the podcast for this episode at http://pnpweekly.podbean.com.
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos

A

And action and welcome everybody: this is bmp weekly episode, 117 in the bmp weekly. We talk about the latest in microsoft, 365 platform or in general. My name is cesar ivan I'm a program manager in the one tribe, sharepoint site, well, obviously, expanding on many many of the other technologies in microsoft's, racist, five as well and with me as a co-host, is wild deck who.

B

Are you hi everybody? My name is valik muslic. I am cloud developer advocate for microsoft, 365 and today with us, we have a guest from belgium, berg, johnson, a guest.

C

From belgium yeah so muscle from brussels.

C

Pretty far from brussels, I'm almost close to you.

A

But muscles but.

C

A

C

For sure, but uh yeah, um I'm also at microsoft, um um senior service engineer in a team called the um uh wait.

C

A

Am I doing again.

C

C

And the team does many things, but one of the things that I've particularly focus on is helping isvs and partners, but mainly isvs get the most out of their sharepoint and onedrive experience.

C

So um we work with uh we get like typical questions like nice fee as a particular integration, they want to prove some a scenario with an involved sharepoint or there was a new isv that is uh wants to. That has a connection with box, for example, uh and now uh their customers are asking like: hey, actually can do something similar with sharepoint, because we need that we use sharepoint, and we want you to do something similar. Then we help those isvs. We start talking to them. We give them ids.

C

We code snippets samples, we're not writing that code as such, but we are more coaching them helping them understand what are the best options, how to integrate with sharepoint onedrive and that's like a substantial part of my job and the other part is working with you guys on pnp.

B

Yeah, perfect customers, like do you um engage more with devs, or is it more with the architects bdms cios ctos.

C

It says mixed audience. Sometimes it starts indeed with businesses you make a ctos, but then the actual work mainly is with the dev guys that talk about techno things. Typically, they also have like experienced people. They have. They have an idea what they want. They even have to write things out. They have questions. Do I should use option a? I should use option b and then we so it quite often ends up in a technical discussion around.

C

What's the best approach, how to do this and how to do that and so but yeah, and sometimes you talk to a need, a cto or a architect. It also depends on the size of the company. Obviously like the bigger the company that the the that's actually the smaller the company, the easier you talk to a cto.

A

For sure now, actually, let's truly are on drilling and let's do some trailing on you on this one. So why would an isv or partner be interested in microsoft 365? What is it what's in it for them.

C

I think uh when you see is it that microsoft and sharepoint in general max is more and more evolving towards like an intelligent uh file, storage platform as well like we see many isps uh that use us to to handle files and what more will come in the future, and then we have already a ton of features around handling files in sharepoint, um around compliance, for example, security, scale, co-authoring with office and so on, and that's an incredible valuable asset.

C

If you today are an isv and you work with files and you're, not in a cloud platform. Where do you go? Do you build your own cloud? Do you store your own files yeah? You could do that sure, but they think thinking in the global world. Okay, I built something I put something in a data center somewhere, okay, fine, but then your next customers is across the other side of the world. So you need to have some or you have a multinational company which is across the world.

C

You need to think about multi-geo and, and then you get into particular scooter regulations.

C

You need to implement those, and so on so soon it becomes like a massive, complex endeavor to really handle files in the correct enterprise scale level in the cloud, and why not just give them to the microsoft to micro65, sharepoint onedrive and use that as a backend to handle your files, you can still build a front-end application and then use use that, but we can uh be, I think, uh very well we're actually very well capable platform of handling the backup need for you when it comes to fast.

C

We do obviously way more than that, but that's just something that that kind of recently, uh where a couple of isps in the direction kind of they wanted to uh use us as a file platform, and that's why yep.

A

And and like I said, the compliance and the centralized coordination centralized control. All of that has a massive impact.

B

Backup permissions.

C

Everything so much work to build this yourself. It's like as a much work and you you shouldn't do that. It makes no sense anymore to do that yourself, but it's related.

A

On this one above, I was actually in a discussion on this one for past week, but one thing what's still apparently not. There is, however, that every single end user needs to have a license right, so you cannot actually just take advantage of the platform just by the platform you.

C

Need to have a license.

A

Yes, exactly exactly, but at the same time I think one billion. uh What does it say? It's it's a massive number of hundreds of millions of people actually using microsoft, 365 on a monthly basis. I think it's, including the consumer side. I think we're crossing one billion or something it's just mind-blowing. So.

C

The figures suggest out of a mind, blowing out of the roof yeah. It keeps.

A

C

Yeah and okay today we need maybe license, but maybe future things might be different, maybe there's different operating models, but today yeah you need to have license, but most big companies have nowadays license and people are using sharepoint onedrive. So you you're good to go so you can just as nicely this also kind of makes your story easier, because while you already have the back end, you don't have to pay for that as such yeah, so microsoft paid already that the customer already paid for microsoft to host that for them.

C

So you can piggyback on that investment. It makes you all stronger and your investments, especially your kind of return, investment better. I think, because you don't have.

A

C

Host and content yourself.

A

Absolutely absolutely and, and then, if we talk about the scale, is microsoft really able? What if I I upload a terabyte of files to the tenant? uh Is the microsoft really able to scale down.

C

A

C

Actually think about the terabyte file.

D

C

You want to put a terabyte in theory. You could now do that with four files of 250 gigabytes.

A

Just four files good point: yes,.

C

Talking about scale, that's one way to express scales, but so we we scale in file size. We got a really large files nowadays, like 250 gigabyte, max file, size and sizing wire the amount of files, the that's there is not really like an undefined limit anymore, I think yeah. So we just doing our best to scratch all the limbs that we had from the past and there's yeah in the future.

C

I think meaning, there's no point in the cloud in future clouds there will be no limits anymore, just sure, just usage, just use it like electricity, you just use it and you get it. What you need.

A

Infinite elastic cloud right so.

C

It reminds me of my days that I long long time ago today that, like some unix vendor, I think ibm it was you could kind of pay usage of the unix box, and that was like a great idea back then, like you, just paid a bill for what you use from the unix machine from the cpu wow yeah. But that's like 20 years ago now we're back in a situation where you actually have a real pay by use model that that skills and it works.

A

Everything yeah absolutely absolutely or well. That's that's already way back, but at some point we were in on premises and then we needed to figure out. How do we create? How do we plan our deployments in a way that the sql server can scale with the usage and and then we needed to actually buy this certain set of ssd disks and all of that stuff? And that was.

D

B

Nice size right because, like you, had limit pair side per content database, you could particularly true that so you could, like you, had to know all of that up front or at least have a model to it like okay, if we grow, then we will grow that way and not that way, because we need to accommodate to these limits that are on prem scale.

A

Scale results and all of that, so that's wow. That is a good point. Yeah.

C

A

C

Something from the past more or less yeah.

B

In a cloud yeah yeah.

C

Which is good, we can focus on other things.

A

Well, on other things, uh bert you've been also actively part of the bmp initiative from actually from a day one, because you you you and me basically started collecting the samples before anything was uh public um as an internal microsoft effort. um Thank you for being there um because we're pretty far on this journey um related on where we actually started, but on there anything new what you want to talk about, or anything new on the bmp. What you've been focusing on so I but the site score story. Do you want to kind of.

C

A

What that's, what it actually.

C

Means we can talk about cisco, but I think before jumping on that one, I want to kind of just um talk a bit about modernization, which is one of my uh kind of uh clean course things that I've been working on a lot and that I've been I'm passionate about and then and that becomes more relevant because microsoft keeps on shipping new things, good things, viva topics, we've connections, for example.

C

Well I mean great, but if you're still in the classic world, yeah okay, you can look at it, but you can't really use it that much so you get.

B

More benefits yeah. So that's, I think, an interesting thing, because aggression is not just on-prem to the cloud right. It's also from the um classic experience to modern, correct.

C

Yeah yeah absolutely absolutely. I think that that's uh something that that customers are seeing and many customers already working on that good, but there's still also lots of customers still using classic uis in sharepoint or still today, creating classic team sites and doing that because they were used to do that again. Nothing wrong. It's supported it works, but.

B

Just don't do it.

C

I'm not a marketing guy.

C

I could have wrapped that a little bit better, but.

A

C

A

We're not marketing garcia, so it's all good! You.

C

Can't do that just spend more money to undo what you do today. Yes, that's the point, so you can do it and you can kind of push the old potato forward. There's a certain point. You have to deal with it and then you just have to handle more classic content to transform to model again yeah. Now. Luckily, there is some tooling. We have some and pnp. We built uh several modernization, scripts and tools, including page transformation technology that helps you transform the classic pages. The modern pages which you need, for example, fifa connections.

C

If you want to show a page on a mobile device in the viva connections, app well, if it's classic, it won't render sorry so it needs to be modern.

C

We have a scanner to help. You assess what is classic content in your in your tenant and how to kind of take that one forward.

C

So there is tools for you to to make that happen, and actually I want to quickly plug quests in this case, because quest last week released a new version of contact matrix, which is one of their migration products which migrates on-prem to uh online, and they now integrate pnp page transformation technology as a way for customers to modernize their content while transforming from on-prem to online, which is a really great feature, because it really adds value to the customer for customers like if you're on classic on-prem.

C

Okay, it is what it is because it was classic there. You had my choice, but if you go to the cloud, why continue in a classic world? If you do the work to move over and do all the change management to go from platform on-prem to online? So there's a lot of things going on yeah. Why not consider taking the extra jump to go to modern at the same time, because it adds more value for you when you do like a one-time, big migration versus two smaller ones?

C

And now the quest supports the technology of that approach in their product. um So you can, when you have the latest content metrics, you have an option to download the pdp transmission binaries from yougut.

C

You upload them to the quest uh you give to actually a request tool and then they can uh use it uh in regards that's kind of how it works and.

A

That's just a recap on that one. That's actually really good. If you think about the migration stories and cloud adaption in general, it is a really big change management uh project for end user perspective and so moving from a let's say, classic internet.condozer.com to condole.sharepoint.com and all of the changed behavior, the administrative behavior and the things look a bit different already, even though you would be in a classic. You would need to understand how things work. Why wouldn't you actually do the same at the modernization at the same time, because sooner or.

A

At some point will need to modernize those sites so combining.

B

That, with expansion yeah, I think interesting thing to ask- is how much work is it so, to what extent does the tool everything that needs to be done to move from asset to modern and to what extent there is still work left to be done, it's manual effort and mapping and reven, which is why people might be hesitant to do it.

C

um I personally think it's quite easy, so when you go from classic to modern, if you migrate content over what's content, content is lists and libraries documents and pages. That's it.

C

If you create your target site as a modern site, a modern team site, for example, or communication site okay, you start modeling, you move over lists and libraries yeah for 95 that all ends up in model nowadays, so that should be good right. One thing that doesn't enter the model by default is pages. I have wiki pages in my site. Okay, now page transformation will take wiki pages and will give you like a really good deep by default.

C

Modern page, you don't have to configure anything, you just run it and you'll get like really good modern pages. There's not really much more. You can improve because the things that can be translated from classic to modern are translated. If you have custom web browsers, you can build you share. What about the.

A

Web parts, what about I have a farm solution deployed in my own premises? uh What now? What is the story? Can you recap on that.

C

First thing I would say like you: do you really need it? Ideally, you just throw it away, forget about it yeah, but sure.

A

It's a business, critical thing.

C

A

Every single team side.

C

It is critical, you need it uh great, no problem with that. That makes sense as well. uh You built a model equivalent using sharepoint framework, you deployed a web art and then in in the basic technology. There's like a mapping concept which allows you to say, like this particular old web part or these old web parts, just ship all sharepoint web parts.

C

I map them to this new svx webpart and then the mapping to will handle that and you you will will replace them. Your old web part will be replaced by a new web part and you can even control the configuration you can kind of tie things together there. So that's an option, but for most people they don't have customer parts or they don't want to move over customer apart. So but yeah, it's an option.

C

A

So that even that is being considered, that's actually really right. Yes,.

C

And so is slightly different, but that's uh but it's doable with the puppets for.

A

The products as well publishing.

C

Portals allowed like in classical all the freedom you build a page layout where you define the canvas, so you put this goes to the top right. This goes to the bottom.

C

Whatever you kind of configure that so kind of free format, you have full control using the page right on the master page when you move that publishing page to a communication site, because you can only move it to a modern communication site or modern team site to something model, you have an option by default, the transformation tech will just put everything like one column, all your text, all your web parts.

C

They will be there, but they are not nicely layout, but you can define your own custom layout there again and say, like okay, this piece of text goes to section one column, two. This goes to the first buckle. You swap that as well, so you just define like okay, so in a way.

B

You have exactly the same outcome.

C

Yeah you can build something from structure wise, you can. If you want to modernize your structure, and you said like yeah, I want to use the the right column and.

A

Yeah, but what about, if I have a highly customized base layouts um are those supported in in modern not on modern. So.

B

I can't do a custom basic fine.

A

Well, I know obviously answer on this question, but I'm just teasing on the questions. So so, let's say that a customer has a a customized base layout, where they, for example, expose metadata whenever the page layout is in the edit mode uh kind of a typical, classical way of collecting metadata on base level. Can we do something similar in the motor.

C

You put at the same metadata columns in your site, pages library, and you configure it to your open and just like the web page to show metadata on a page. It will show up always not in edit mode only yeah. There are some differences over here between between the platforms and not exactly the same feature set, but uh you can more or less do whatever you. What you need in modern as well yeah.

D

C

Are not locked, so you you like, if you imagine you had a page layout where you had like a web partner better than the page cloud, so like a fixed web product on all the pages, you couldn't remove it as user.

C

That web part will be translated, so you will end up with a model equivalent web part on the modern page. But this time the section is not blocked, so the user can delete it. So there is, but there's differences in the platform and again the modern page platform is evolving as well. Maybe in the future there will be an option to log sections and then we are just space transformation to take that an account. But today it's it's like it is yep.

A

Absolutely absolutely and it and and for sure, in general, modern pages and more and better updates uh creation of modern pages. Managing them is much more efficient and much easier and from an user perspective, much more intuitive as well, so for sure absolutely now on on other areas. So you we talked about the modern pages and modern pages uh api being part of the modernization tooling, um but that's not precisely the only location where the modern pages ai pages api does exist. Right.

C

Actually, the model pages api does not exist in the modulation tooling. It's exactly part of pnp cars dedicated to apis.

A

There's no api! So let's talk about this one and let's hit those, let's say difficult discussions as well, so there's a pmp uh core sdk, which is the the new term and which is for net five and you can use it in dotnet standard or whatever. You can implement your stuff on. That's.

C

Everywhere the whole.

A

Net everywhere it works everywhere, which is really really cool, and that has the modern pages apis are able to basically create pages. Add sections columns put a web parts there manipulate all of that stuff, but that's still in the pmp core sdk, which is an open source solution. So if I'm a customer, what if I have concerns related on open source? So what's your? Why isn't this part of craft.

C

Yeah, oh yeah, in the ideal world this would be in graph like many other things would be in graph in the ideal world. There's other things as well, but it's not the ideal world we live in. We live in the world right now, aussies and by plans and priorities and so on and then building a modern page api is a fairly complex endeavor. That today does not really exist in draft now. That being said, are you blocked?

C

uh No, because the pnp karzik implementation in the end uses supported apis under covers. We just read the list item and a page is a list item with con so list item with particular columns in this column columns of those fields they contain the page content. So what does the page api do? It will read that content?

C

It will translate it into an object model for you as developer, to make it easy to add a section to add a column, to put something in a section to do to make it multilingual and so on and so on. But in the end we just serialize back the data into the list- item and say: sharepoint system update list item save back the list. So it's reading this.

A

Item, why is it system item system update or is it anyway sorry.

B

Back in when sharepoint was no no, no, no, no, no.

C

That's the item, the sharepoint.

A

Yes, yes, exactly, but so, and and this this node package. Oh sorry, nougat package is open source, uh so is it then supported or what's to support a bit of the story? You mentioned that the apis are.

C

Supported yes, but the the source code from people's key from any open source project as such is not supported. So if you call support and say like yeah using this particular method doesn't work. If you can pinpoint the fact that the example saving of the list item breaks, then okay spock will help you.

C

But if it's uh something else going wrong before then you well, you you have to work with the the open source team, owning the library or you can try to fix it yourself, um that's open source, so this is free, but it's not uh there's no support, sla and yeah and so on. As you all know, but but we we do our best as a team to kind of listen to the incoming feedback and to answer quickly. uh Sometimes that works. Sometimes you need to work wait longer.

C

It kind of depends a bit on the capacity and the people that are at that point in time online. Looking at the content, picking up an issue and helping you, I think, with open source for me, the more detailed you can describe your issue or even recommend a fix, the easier it gets for the folks, owning the library or an open source component to to make the fix. If it's generic, like yeah, it doesn't work. Okay, yeah we yeah.

A

C

Time to figure out, it's really broken. If something is broken. Often it's not something broke, it's more like a user question, but if you can be more precise, it's good, and for that actually there's one thing: we have uh sourcing support in all the pnp.net packages nowadays.

C

So if you just use the pnp.net package in visual studio, your developer, using that it doesn't work, it breaks, you can just press f11 and dive into our source code without having it pull down on your system, and you can give a more tailored kind of messaging and github like yeah. This line is breaking or this particular thing doesn't work, or I get exception at this point.

C

So it helps you to give to better understand why it goes wrong and if it goes wrong, it helps you to also write a more tailored a more to the point issue in github or even make like a pr. That would be even better. If you create a pr with your fix, then it's uh and it's really a problem, then merging that it's like a matter of days typically um but yeah. It's it's.

A

C

A

Of course, it's it's absolutely 100 better that we rather build this one, unified library, together with the community as an open source solution, rather than every single company building their own unique thing which are evolving on different uh section, because also you bert, have a lot of insights related on what happens inside of engineering. So if something happens for the modern pages, we can take that into account in this open source library, with the partner who's building their own couldn't so so that's one of the reasons.

A

Of course, why, by having one unified, open source solution built together with partners, is better than having multiple competing ones for sure absolutely.

C

Absolutely and as partners, you can use those open source components in your products. I mentioned the beginning quest uh integrating base transformation. Now they made they've taken this approach that their customers their end. Customers have to download the latest bits from bnb from nikket, so they have to take a deliberate action to download that and add it to their content, matrix installation, and they also clearly spell like guys. We don't own the source code, so we don't officially support it if it goes wrong, we'll try to help you, but we are not.

C

It's not like our score that we can immediately jump in and fix things so, but they have like a hybrid working model um and the thing that's a good kind of way forward for this thing, where uh they add the value to the customer because their customers were demanding like hey. I want this quest.

C

I need this particular feature and now they ship it and they enable their customers with a trade-off that if there is something with page transformation that goes wrong as such, that they will, with their customers, bring it back to the community where we try as green tea, try to fix it and get them unblocked.

A

Yeah, what about what happens when, whenever the so sooner or later, will luckily have a native modern betas api in a craft? What happens then? Do you need to re-implement um your whole functionality?

A

So is it worthwhile to maybe well, it will certainly not happen within the six months, but uh is it something like do you want to wait for the craft to have that or do you use this and do I need to re-implement the whole thing whenever the craft will have the native modern pages api.

C

Yeah, first of all, waiting for the graph to have this waiting for something to ship a particular feature.

C

I wouldn't recommend doing that unless you're really sure that the team is shipping, the new feature that you need like in next two, three months great then you have, if you have committed timeline sure, but if there's like a if it's still open waiting, but I see nothing so in this case uh for pages api, you would why why? Wouldn't you use pnp chorus decay, because then you get the value right away now, if later on graph ships uh page api- and that applies also to other areas.

C

But let's take page api's example, then, because the case written in a way that we can undercover change the api implementation, while you as developers, use users of the library are not impacted.

C

So the pin because k under covers uses graph uses a sharepoint rest and even some csum, but what you get back from api is a set of objects that are not connected to any api anymore. Yeah, like a system works, get a system object back. You can only use it with system.

C

This time we have a clear disconnect you get back uh bike or sdk objects and how we populate those objects. How we populate the web object or the list object or the item object, is up to the sdk to do that, for you, based on what you ask and if apis need to change because microsoft evolves, then we make those changes under the covers and you should not see any impact for your application. Let's think.

A

About the big thing.

C

With forza games.

A

So then, oversimplifying things the the core sdk gives us the capability of using features already today, as in addressing the gap whatever is there and without then, and- and if I commit on that my so, I don't need to actually re-implement my stuff, because it's the abstraction layer between the under underlying apis- that's actually a really cool thing so well implemented. Whoever came up with this model so.

C

I don't know, I don't know.

B

A

Well, I think that's the the one of the things if we think about the bmp sa um the larger program and initiative, there's just multiple kind of efforts where the b b is running and a lot of those efforts have originally started. Based on addressing a gap.

A

I still love the the story related on 365 cli, because waldek was an mvp employed by me as a vendor to write developer documentation for spfx, and then we created the developer documentation related on how to enable cdn within your tenant, and you needed to use a powershell for it and the powershell doesn't work in mac. So we needed to address the gap and then poof and then there's the cli for microsoft, 365. So.

C

You should introduce our original name back.

A

Which one are the gaps? Yes,.

C

The really first, first year of the initiative, it was internal only so not just for because we were president in iowa, both the consulting services working with clients across the world and then we're.

A

Actually, building real world customer cases.

C

Real world stuff yeah.

A

C

uh But then yeah we uh euro code, they built great apps, which was, if you kind of put it together with gaps. It was like the.

D

Hidden message was like.

C

Yeah, actually, there's so many gaps, so we have to build something just to be able to build great apps. We have to fix the gaps kind of plus the story around.

D

C

That wasn't really a marketing ready.

B

But I guess in a way you could like, I think that can be said of any dev, tooling or or an sdk right like like it's meant to make things easier and whether that's a gap or like you can you you can argue about anything, that's that it's a gap that it should be a part of the product. Well sure ever like thinking that way everything belongs in there. But on the other hand, maybe there is something specific. Maybe some people use it that way, but not everyone right.

B

So, like there's like you, you draw the line at some point right and also like like there's. As you say, resources like we at microsoft cannot physically do like. We don't scale to do everything for everyone yeah right, so if you think about it at the end of the day like like, who is the best at doing what and who? Who is the only party who can do things like if you think about like who is the only one who can implement things in in the cloud?

B

Well, obviously us, like customers cannot build things in our cloud like they cannot. They cannot change code on servers like that is just a not an option, but they can build an sdk that has scenarios implemented specifically for them. Well, then, they should do that and then we'll focus on building apis, providing them with services, intelligence and insights, as the only thing that we can do right. Yep, absolutely.

A

Absolutely cool: let's actually jump into articles and and talk about those and we'll come back on on uh talking about the next steps in a second, I will start sharing my screen wherever the team shows me, the screen.

B

Nine eight seven six.

D

Five, four: three, two really one: no, not.

A

D

Okay, here we go here, we go now.

A

I know the screen sharing. I can select the screen number, two one. What? Yes, I clicked it already. So it's in the progress so, uh okay, there we go.

B

Yes, it's through.

A

Ignition excellent ignition still and last week, obviously a lot of lot of a lot of a lot of a lot of a lot of announcements related on ignite and we're going to do recaps of these in community calls and all of that stuff and what it does actually mean as part of this journey it, and these big announcements are always about marketing more, like awesome, okay, what does it read? Really means? That's the day-to-day community engage and what we need to actually explain so awesome now uh related on microsoft, viva.

A

uh So a few updates on different microsoft, people learning uh it's gonna, be a public preview in april 2021, microsoft, viva connections and starting to go ga in uh in march. This is mainly for viva connections desktop so this month. So it's going to go to ea, it's it there's this multiple features with go, comes and will be lighting up slightly later, but especially the desktop version will be coming out in march, which is this month, which is really really cool.

A

uh Viva insight is now in public preview and then the viva topics is the one which is currently available um related. Actually, one thing maybe to mention also is that we also mentioned it. Does it say that no, it doesn't say it in here?

A

Vivo connections will be free as part of the licensing for sharepoint online, so nobody has to be any extra related on having the the portal then embedded directly in teams, so the mobile experiences and all of that, so it's really cool uh and then a lot of these ignite announcements, so we're gonna actually collect all of this and in the blog post article as a lot of other stuff, so people can easily access things. I think the new layouts options really really awesome, um absolutely brilliant stuff.

A

uh The live reactions, and this are really really cool as well um and and who said it, somebody said it actually. Last week we had the community call on thursday and and whenever somebody actually clicked that that there was a massive reaction, but people are realizing. Oh, I can actually do these reactions, so I can we can actually kind of. Oh, this is actually cool. I can see them live so, but they actually do have a lot of value for sure and getting the meetings more interactive. It's a really good thing.

A

One thousand person interactive webinars with the moderation control wow, all the scale of things so.

C

They're really cool here.

A

A lot of lot of great uh improvements and the great uh enhancements in microsoft, team sites for sure and devices devices teams panels. We talked about this one last week as well that maybe the team's banners are cool, but you're gonna put them in office. What is an office? Well, the thing where we will go whenever this thingy will go away so.

C

I should put that panel outside of my my door.

B

We go taken now. Yes, I'm in there.

D

A

But a lot of a lot of them awesome uh enhancements and obviously there will be a lot of lot of additional details, one step at a time when things are getting more uh available. Also for microsoft lists. There was a lot of new improvements in here. Here's a cool video from microsoft, mechanics where we have omar shaheen, rcvp related on one hour, sharepoint and lists um as an example, and to talk about the improvements in here. So how what are the things where we are investing and what? What are the really cool things?

A

What you can actually do with the stuff as well, so we're really cool- and there was a lot of improvements and last week was on security and compliance collaboration, microsoft teams, so announcement multi-geo support safety controls uh targeting disabling attendee video during meetings, actually pretty important thing if needed, to have control related on, what's actually happening on the other side. um Technically, having all of this community goals and everything else, I always say: potential risks for us when we're doing the videos, together with anybody else.

A

uh New inclusive features in microsoft theme some more ignite, 2021 edition, uh so really cool uh options related on making things easier, layout, control, uh slides in high contrast, if needed. So you can actually automatically adjust all of that stuff and a lot of a lot of improvements in here as well, so really really cool.

A

uh Then we had a new template coming out for the microsoft lookbook, so help employees transition to hybrid work using sharepoint site template. This is a site template, that's a technical term. It is a site template because you're creating a template site based on a template. Now what is the technology? That's debatable, but really cool a new workplace transformation site with an example content inside of it. So you can actually apply this to any tenant in the world by using the sharepoint lookbook, which is really really cool.

A

So a lot of a lot of good usage on that. um Then there was some cheshire money and what's the new security compliancy on microsoft, ignite 2021 a lot of lot of improvements here as well. So a lot of this stuff is across the microsoft resistive, not just about and the onedrive or sharepoint so more and more. We when we implement the features it's across the the board rather than isolated products, which is really good as well.

A

uh What else uh sharepoint roadmap came out the february 2021 edition last monday as well? We just missed it for the last recording. So what are the latest improvements in here and there's a uh good good um recording and interview with naomi manipeni who's gonna? Actually do a community monthly community call demo tomorrow, tuesday, depending on when you're watching this video?

A

uh Is it on tuesday or not, uh and so a lot of improvements on sharepoint site related on many many many many functionalities, and what else uh we have they might do what's new in the microsoft 365 teams platform, so it updates on that one. So, a lot of cool stuff as well.

A

We have what's new in excel add-ins developers, 2021 everybody is hitting new articles and new new things to talk about in ignite week and then on the bmp blog posts. So we do have now this new microsoft 365 bmp. uh What is it it's a hub in the tech community, yes, uh and in here we have uh five or six new articles uh so quickly running through them as well.

A

So elio had a really cool article related on how to to write a code code comments or not and really think kind of evaluating those different options. What does it actually mean? It's a really cool stuff as well. uh Paul pollock has a modernization lives in pmp framework. This relates on the discussion what we had with bert. So how do we actually?

A

What are the? What are the the modernization tooling? What's where and how does it actually work? What is the old github repo? What is the new, because there were some recent changes related on that layout as well, some really cool stuff uh lewis, freeze saturday, should we use sharepoint tourism, microsoft graph in power automate? Have you read this world deck, putting you on the spot? Yes, I have. What is the conclusion?

A

It depends yes, surprise.

B

Of course, I think tldr is like yes, you want to do graph, but in order to call graph like you need to do an http call, which requires a license in empower automate right. So like it comes like yes, you can do more things with graph across 365, but in order to be able to do that, you you need a license so like it comes with additional cost in a way yeah.

A

And we still have the option of using sharepoint rest and the kind of a classic option. You can fall back on that. Obviously we do recommend highly on using microsoft graph apis, where possible, so for sure um how to create a folks table in adaptive cars with power automate, so basically how to create this kind of a table. um And how do we post that one to the teams uh or to the discussion so really cool article as well?

A

uh It was posting to teams. Yes, it was post, adapter, guardian and chat or channel yes uh avoid unnecessary looping apply to each empower automate good article from leon, armstrong related on that one. It's cool to see more and more power automate being used slightly, which is understandable for sure, because it's super powerful to to get access on things and and it's pretty.

B

Easy for automated it's.

A

A

Really cool article from leon on that one as well, and then we had eth now on how to start your spfx web part first with microsoft, craft toolkit and react. So basically, if I'm creating a new uh project and spf projects, how how do I actually integrate with microsoft, craft toolkit? How do I take advantage of that?

A

How do I create the sharepoint provider, which will then take care of the access tokens and all of that stuff for the crap toolkit controls so relatively simple, but really kind of a pinpointing on the exact things to get started, which is really really cool, uh and then we move into the video section so and adam hermitz had a really great video from last week related on introduction, microsoft, viva connections. I think this actually touches really big gives a great overview. What is the viva connections? What does it mean? There's no license in the implication.

A

It will be free. How do we extend that? What does it mean for end user and then also the fact that okay, so is this just repackaged to the company app which we announced the nikknite and all of those questions are being addressed on this video? So it's actually really cool. um So it's not just about marketing, but also about hey.

A

So is this just repositioning what we have or is there's new stuff and he's addressing all of those, so great video uh we uh so dan walling had a really great video related on azure communication services. This one was released to ga or preview as part of the ignite announcements uh right about there. No on that one. Yes, so uh azure communication services, um so basically in preview in preview.

A

Okay, the basic idea of this one is that you can actually build a solution or your custom solution can take advantage of chat, sms and audio and video, rather than just starting a teams as such. So you can actually integrate video calling directly within your custom application and that's actually really really cool. So yeah super cool stuff, uh paulo, had a new article uh episode, 1244, creating teams, link, unfurling extension for your teams and what is link unfurling, because I saw this title first, I'm like what is blank unfurling?

A

What does it actually mean, but basically it's enriching of links in the conversation, and I think somewhere uh in here we're actually seeing that it's more more, let's say advanced, linking not just the link, rather just adding additional content based on the link as well.

C

If, if you paste the link, it will just show some preview and some behavior around the link makes gives you more context about what you paste exactly.

A

Exactly yeah really cool stuff and, of course, he's pasting in vs tech bytes on his demos. So that's good, uh then there's a a new weekly series. This is really really cool as well, uh so a new weekly series for spfx um uh sharepoint framework for beginners episode, one and introduction- and I think later today, as we're recording this on monday. I think robert is going to release this.

A

The episode number two, because this was intended intended to be a weekly uh series, so really cool to get recap on on how to get started on spfx. uh What are the things to consider? How how do we implement stuff and all of that stuff and in general, in the in the proper div, talk, there's actually a good set of videos on on multiple other things, as well, so really great channel.

A

um Will holland from tribal had a a really nice summary related on a nicole herzowicz announcements on what are the latest around the microsoft uh teams, platform and options, and all of that so kind of a summary on on on this one? So this blog post kind of warrants, through the main feature announcements within that within that video. Yes, that's the right way of saying that, yes, it is, it is.

A

I think it is whatever um this one uh also actually really really cool from michael mallett init api permissions for your spf projects without deploying them okay. So how do I grant api permissions to the spfx projects when I'm doing testing and debugging without deployment of the speak at file to the app catalog? And this basically, is that there's a explicit azure ad application where we can go and configure the needed permissions, and that then enables you to do debugging directly in the hosted local workbench so makes sense.

A

But it's good to have a reminder how it works as well, and then chris o'brien had a relatively long article related on sharepoint, syntax, artificial intelligence tips for choosing between document understanding and form processing models. If you are more into the sharepoint syntax, I think, and this will be explaining the different options and how does it actually work.

C

On that one on sharepoint syntax, one thing to mention there is as well as that bp rdk will have syntax support very soon yeah.

C

So we enable you to take syntax models which is going to understanding model, and then you can take that model and deploy that to libraries to so that the library when you upload documents to that library, the model list is processed, and your document, for example, is read and the metadata is extracted and put into the method of the columns. It could be a scenario that you that we support for syntax here so, but we enable you with pnp to uh grammatically.

C

Do that work uh yeah same as running existing content through the models and so on. So the first step is having apis in pp rck once they.

A

Are export and import the configurations? Yes,.

C

Once they're done, that will be in people or shell as well to have like a give it admins. It pros a way to configure and roll out sharepoint syntax in their tenant.

A

Absolutely absolutely really really cool and it's good to see more and more focus and investments on the sharepoint, syntax and the project codex outcomes, so to say, because project codex was basically do things, it was sharepoint syntax and then the viva topics and note that the viva topics and sharepoint syntax are now out and also getting evolved as an individual features and capabilities as well and getting more support for them makes a lot of sense.

A

Now, ignite is done. Dev kitchen is done for vivo contact, aviva connections, we've done that one what's happening this week. I know what I need to do at least sleep this week. Yeah.

C

I have a day.

D

C

A

Really, I should have a tail day off as well.

C

Know it this week, uh I think actually it can be it's a big week for us, because we everything goes well. We plan to uh release both dk v1 as a next official release from pp, farewell powershell.

A

C

Everything goes well by the end of the week, we'll have all of them released, which took us a while, like there's been like a almost a year of journey, to get to this point with being, of course, decay.

A

C

It's a step-by-step approach, but it enables us to gradually replace things and prove things without impacting people the community using our components. So that's why it takes a bit of time, but the other end yeah.

B

I mean more seamlessly, and I guess also another thing is like it's just a scale right: it's not not like you start with a new sdk. That does only allows you to retrieve an update title of a web like it does many things already, so it's big and then in parallel you maintain the other thing that was already available too. So you kind of for all these times split yourself into like trying to support everything you can in the old stuff, but then also bring up this new stuff to par right.

B

So I think it only like. It only makes it clear to folks like how much effort there goes into that, like once you get involved into something at scale. It's like huh it's.

A

Not just like you know, you don't want to.

B

Change it, let's fix it,.

A

You can't break your existing customers, you need to do backward compatibility on it and then the classic story related well, not a problem. You get 10 people of volunteering on on helping you, which is like yeah, but that actually makes situation kind of worse for momentarily, which is an interesting.

D

Challenge as well, yeah, of course, in a long time, but.

A

Managing things coordination, everything else, the overhead, it's it's a really interesting challenge for sure.

C

Maybe in the beginning, but now I think yeah like already mentioned, I think we we.

D

C

Now, at the point where we can definitely use more contributors, we've written how to extend people across decay. It's we've learned from the mistakes on the past, so the bp side score was organically grown over six seven years.

C

Documentation was uh you search on the internet and you might find a blog article and there's many of them, but yeah you have to hunt for documentation our people across the gate. It's well coded well documented, well tested and we put just a way higher quality bar for any submission as well, but I think that's really good, because we want to build something which is stable and can evolve for the next 10 years. um So it's like a big kind of uplift of what we had to uh be ready for the for the future. Again.

A

Yeah, absolutely absolutely so. That's that's the big news for burke for this week. Hopefully crossing fingers and everything goes fine. What about you? While there can be interesting happening on your side,.

B

um Last week I spent a whole week trying to figure out like how do you build a bot with bot other, which is a kind of interesting tool like so I've, never built built a bot in the past so that that is like a low code.

B

But it's not the power platformy way of building bot, it's more advanced, so it's kind of in the middle and it allows you like to basically set the first step to build a ball basically to experience like what a bot is, how it works and then kind of um inspire you to do more right. So I spent a whole week on that. I learned tons of stuff. So now it's kind of okay. There are things that I learned that needs to go back to product groups.

B

There are things that needs to be changed in the docs. There are things that kind of don't fit like in either both so like. Maybe there will be a blog post or video or something so I'm trying to like sort out all of that from the uh past week and then other than that. It's going back to work and um picking up work on learn modules that work on a photograph.

C

A

C

Quite busy, then.

B

Here absolutely every week.

A

Every single week uh we're on our.

D

A

Yeah we're we're looking into releasing sharepoint framework 1.12 this week, uh so um unless there's any last-minute thing is and then we need well, we need to get it out. uh We we have 1.13 coming really soon after this one as well. There's a dependencies related on previews for viva connections and we need to get 1.30 now, then all of that stuff.

A

So this is a release cycle and release management is really really hard, but we'll we'll get there, because, obviously we don't want to actually release 112 and then release 1, 12 1 immediately right after because that doesn't make any sense. So.

B

And you also don't want to ship 113 and 112 uh after that yeah yeah.

A

Well, that dude.

C

Yeah exactly, of course not, let's shift one point. Fourteen then just to see.

A

Yeah exactly yeah, oh yeah, so skipping the 13.. I I think we are planning to release the 13.. So but again I live in a house number 13, so I yeah. So that's.

B

I used to play volleyball everything right.

C

Yeah I I used to always play volleyball with number 13. It was my number so yeah.

D

Never going to I.

C

Never broke anything, I never got really hurt. So yeah, that's happened so.

D

A

Yeah anyway, I think that's it for the for this week's recording. So thank you, everybody for watching we'll be back with the latest on the news uh bmp weekly new week. So all right thanks.

C

D

A

Thanks thanks for joining us, bert awesome to have a chat with you. Thank you we'll be in touch.

D