Microsoft 365 Community Microsoft 365 PnP Weekly, 27 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Microsoft 365 PnP Weekly – Episode 102

Description

In this weekly discussion of latest news and topics around Microsoft 365, hosts – Vesa Juvonen (Microsoft) | @vesajuvonen, Waldek Mastykarz (Microsoft) | @waldekm, are joined by Cloud Developer Advocate - Tomomi Imura (Microsoft) | @girlie_mac. Discussions focused on efforts to help others learn the Microsoft product line, the importance of conveying what’s possible to help the customer bridge the gap between business need and technology capabilities and on the Microsoft 365 platform opportunity to partners. 21 recently released articles and videos from Microsoft and the PnP Community are highlighted as well. This episode was recorded on Monday, October 26, 2020.

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

Action and welcome everybody: this is bmw weekly. It is episode, 102.

B

A

True good point: I need a meeting as well, so this is pmp weekly where we're talking about uh what has happened within the last week, related on microsoft, uh the m365 platform and all of that stuff, and typically we also have a visitor here. My name is jose: I'm from the onedrive sharepoint engineering site and with me as a co-host is valdick before we go to our visitor.

B

Hi everybody, my name is cloud developer advocate for microsoft, 365 and today we have a guest from san francisco us. My fellow cloud advocate tomomi imura hi to mommy.

C

Hey thank you for having me it's yeah, it's really nice to be here, though yeah should I just intro myself yep, please.

A

Feel free, yeah, absolutely.

C

All right, yes, yeah, like well that just say I'm his co-worker and I'm relatively new too. Actually.

A

C

Joined microsoft like this summer, I thought that was a new one, but then valdec joined, so I'm no longer new, I'm like veteran now so yeah. So I'm doing a m365 developer, advocacy, focusing on teams and yeah. I live in san francisco. Actually, I've been here for over like 16 years. It's been a long time and I've been in the industry for longer, so I've witnessed all that up and down in silicon valley. It's been interesting right here and this time it's definitely interesting time. It's pretty quiet because all the techies have desired the town.

C

So it's no one here.

A

Really so people are moving to different areas, then, from san francisco.

C

Maybe going back to their home because you know the price of living is quite expensive here, although the price is actually going down now because everybody's gone, you know and landers are having a hard time getting new tenants. So I I heard the price is getting lower.

A

C

Yeah but yeah it's because of covet and a lot of companies allow us to work from home. I mean not a lot of us. We have to continuously probably working remotely like microsoft, so everybody's asking me it's like hey tommy. Are you moving out because your company allows you to work from home permanently? I don't know. I'm still here.

A

How's yeah, just out of curiosity, because I was following at some point that you had massive air uh air quality issues in something.

C

Yeah, that's all.

A

Good all good now.

C

So my area, so I live in the city of san francisco and we are the air quality index. I think it's a us index so might not be global, but it's being green means it's good breathable, but the fire itself is not fully contained yet, and this is actually the worst time I have to watch out because november we do have a wildfire pretty much every year, because air is super dry and anything can get ignited and spread.

C

So people can do some dumb stuff, like I don't know, if you're part of one really stupid thing have close to one huge fire. What's a gender revealing party.

B

A

C

So I thought it was hopefully no one does that yeah yeah, it's it's bad. At least breathable is breathable right now.

A

Yeah yeah yeah, like there wouldn't be enough of things in 2020 to worry about right. So.

C

We have a presidential election coming up very soon.

B

That's true, that's right! That would be nice.

C

Being crazy for sure.

A

Yeah yeah yeah. Now, let's, let's get back on the let's say technology and career, so tomomi you well you've been twice as long in microsoft than uh waldeck, which is great so, like you said, you're a senior.

B

Here, it's not like your experience right. Yes,.

A

But what did you do before joining microsoft? So what's your background.

C

Uh-Huh, so I would say I'm not probably like I'm not really your typical developer. I mean to be honest: I never really have used any microsoft technology or even product. You know, because I'm in san francisco and the bay area is not very microsoft, land right, we, like all let's say using mac and emailing on gmail, even for business chatting on slack and stuff like that.

C

So immediately before I joined microsoft, I was actually working for slack almost three years yeah and before that I was in multiple startups and some corporate some startups, some mid-range a lot of different companies and in the typical things about being me in san francisco, is I'm such a job hopper so hop in the job to job like every two years, or so sometimes only seven months yeah. So, but I think it's pretty normal here, there's a plenty of job opportunities, maybe not anymore because of the covet.

C

But it's been like that so and yeah doing developer advocacy for almost 10 years, and before that I was like front end engineer yeah. So.

A

Is it for the web stack development, then so.

C

Yeah so yeah it's mostly web, so I have been involved in web standards too. So I was actually working with w3c for a while.

B

C

Set the standards for mobile cool.

B

That's actually.

C

A funny story, because that time I worked in nokia, so I think yeah you familiar just feel like the company, so yeah.

A

C

I hope yeah fortunately,.

A

C

There in the winter, but.

A

C

Working for windows form.

A

I I have to say a funny funny story related on that. I still remember. I was doing a long, long, multi-month project with with one of the global companies in finland when I was still a consultant- and there was two italian consultants who started working in finland, I think in mid october, and I think it was like january when they were like when when does the sun come up? This is crazy.

C

I heard all the stories. Oh my gosh, I heard all the artificial lights in office.

A

Yeah then, but then they said that one of them or both of them actually stayed for the summer time, and then they said. Okay, now I get it so now. I absolutely get why finland is an awesome place to live in the summertime, because it's still.

C

Six months, beautiful yeah.

B

A

B

Anyway, you don't have have night right like like half year.

A

Long, it's like 24 7,.

B

A

Yeah and now it's dark all the time, but hey no can do um so. Let's not go back on the on the time of nokia, but.

C

My cat is shaking my desk, sorry.

A

Yes, priorities, family or whatever and cats. Okay,.

C

A

Now now considering that you're from the valley area and obviously we want, as a microsoft, we're gonna target that those kind of developers as well and we're moving away from this super microsoft oriented world and to an open source and communities and and uh web stack development and all the certain standard. So what actually made you or is it exactly for that reason? Why did you decided to move to microsoft? So what what's the I.

B

Want to test what else.

A

Is he doing the same sorry.

B

C

So, of course you know I've been in developer advocacy for a long time, so I do. I do know a lot of people from microsoft already and I was talking to some people and they actually have contacted me for the opportunity. So why not I mean my priority is always working with great people. It's not like when I'm leaving a company, I'm leaving a company or product or whatsoever, it's more like a people. You know.

C

Well, it's not like I'm saying I'm living for the people who I don't like, but it's more like you know, joining a company is great people because I really think you know, especially for our job, like advocacy jobs, all about people right, we say it's develop advocate, but the developers not about us, it's more like developers out there in a community. So it's all about. We invest on people. So, of course, I always like to work with great people and I knew microsoft's a lot of great people.

A

Yeah yeah, it has really changed and uh well I may I miss I've been too long in microsoft already, but but the time has really changed in the past. When I started it was completely different company because they they would not allow these kind of phones to be used, which is super weird.

A

Your friends know me yeah, that's true, but it's actually great to see that we're transitioned away from that and now we're embracing, then the the open source and openness and then trying to be as transparent, but how any any kind of uh your first feelings moving to microsoft, anything what you've been super surprised or anything, that's like whoa! I didn't know that they do that.

C

It is difficult to say, though, because I joined during the pandemic, so I never really met anybody in person, yet I'm always working from home right here, while my silly cats are bothering me, so it's really hard to feel you know, because I've been always in working from office, you know always office, always with people and now I'm home and each you know meeting its own teams.

C

I mean it's still great so that it's diff yeah, it's really difficult to say, but the thing is like again technology stacks because I'm completely from a different world, almost like a bizarro world for microsoft developers right, I use a mac and I even demand it for mac. When I join it's like a map, give me man give me my equinox.

A

I don't think there's any problems with that anymore right, so you can easily.

C

Get them no yeah. It got me max because I didn't want to spend too much time for setup and stuff and long that's gonna delay my start, so I just wanted to work on something familiar with and that kind of stuff, but still you know I to be honest.

C

I never really put my code on azure because I was always using competing products and I think only well beside the time at the nokia when I was working for windows phone other things, I'm familiar with only like vs code and github, so then yeah when I just joined. I was like in more like in shock because, first of all, I didn't even know what m365 really meant, and then I had to learn that I'm like.

C

Oh, my gosh, I don't know any of those, so the inspired technology stack is something that I'm not familiar with. So I feel like this is really not just the new job or new role. It's like new everything, yeah! It's it's tough! It's a huge challenge. For me to be honest, but at the same time I guess I can level it for not knowing anything about it. It's actually a strength yeah, because that's how you know we begin this uh onboarding developer project yeah, so we just reworked on teams, documentation and we improved the whole.

C

You know develop onboarding experience, especially for new developers. Yeah. Like me, you know exactly.

A

That's actually a really good point, because you're then the the awesome candidate of testing through the things.

C

A

That, okay, we're missing gaps here and here so yeah.

B

That's actually really really.

A

B

Yeah, and also so all the things like, if you are, if you are doing the same thing like over and over again, like you, no longer see the halls and the things that are assumed of you to know which, on the other hand like if you are new well, you don't know like like there's this example like in docs, we often say get a token from what it's like 20 steps, because you need to have app. You need to have destinations.

A

B

And and there's like this, one line get a token like from where, where.

C

Yeah, I don't know here.

C

Because I don't have any of the muscle memory right.

A

C

I have no idea about those 20 steps, so as a new person new developer, I had to figure it out yeah. So I thought it was quite.

B

Down and we realized like how how often these new devs are stuck and maybe.

A

B

I am stuck stuck, I'm hitting the wall. I will leave it because, like it's too hard right.

C

Yeah, when we can't help them to leave right, you have to just somehow hold them and that that's tough, because I really find out that development like team, especially teams development, has such a steep learning card.

B

C

Gotta do something to just maybe I wouldn't say flatten the car, but it's still, I think it is hard, but I try to make the experience easier with documentation and the tutorials too so yeah.

A

B

And I- and I think like like with everything else, because it's so much right- I mean, if you try to take it all at once and say: okay, develop things for teams. Well, there are tabs. There are boss messaging extension there, our web, we're like no! No, no. Let's just try to do this one thing and even within bots, maybe you don't want to do auth immediately.

B

A

Just like something.

B

Simple and then like when you uh grasp that, then only you add this off and build it out as opposed to trying to squeeze it yeah. It's like this big pile of like how do I even see the top of that right.

C

Even before they actually, I didn't even know their different features like bots, tabs and messaging extensions and all those. So that was a problem so to even get to the point that you know finding out what to do. It's a long like yeah, I had to just read everything and click click or not. This and I started googling something else for third parties. No, this is not the right path. Then, when I was googling, it's like oh shoot. The seo might not be great. That's another issue right.

B

C

Finding a lot of issues, so I think one of the first things uh we're talking with the documentations and product team was like just making sure like you know, just presenting the feature like it, what kind of not just api and stuff just more like a feature that you can create in a first page, with like more graphical way, right, some yeah, screenshots or graphics and diagrams all those.

C

So at least you know that could be a good starting point yeah, but the funny thing is, I didn't want to be a bad person telling everybody especially adjusting the company. No one knows me: they won't have to see me I'm not in seattle, I'm like how I am tomorrow. I'm a new person, and I hate your dog and.

B

You can't this is what's wrong with your dogs,.

C

I did something cunning. Bringing a third party like somebody outside of the company, like actual developers, then help them to run, and we all listen to. They want.

B

I'm okay with that, but they're, saying.

C

Oh yeah, it's complaining about this, but the serious lecture, not just that worked it was I well yeah. I really appreciate everybody who have joined us telling us about their struggles and all their stories and that actually helped a lot to improve. You know the current docs and- and you know, gave me ideas right, tutorials and stuff too.

A

And that's that's the number one thing which we're always asking from the community is that it's it's fine to rent and it's fine to complain, but please make sure that microsoft hears them so that we actually get the feedback so don't go and run in the corner.

B

A

Else because that's not useful, let's try to work together and and make things better. um So because that's everything what we do in microsoft is any way targeted for the developers and end users to take advantage. So something is wrong. We need to know about it so that we can fix it. So exactly.

C

A

Look like you're about to ask something.

B

B

Maybe one more thing to add to that like when you, you complain, it's fine as long as you do it in constructive ways like saying like this sucks, because it sounds cool that doesn't help anybody, but you say like this sucks, because I'm stuck here here, you're here here you say about getting token. But how do.

C

I do it all the reasons.

A

C

A

And like saying, the community calls also super super important pieces if somebody is providing. If there's somebody is there's few things, it's okay, to provide positive feedback as well, because those things do matter as well. So it's not just about friending, but then, when.

C

A

That something is cool so about sending a message.

B

And saying that.

A

And providing positive feedback, because then that really resonates well for those people, who've been spending their time on fixing things so but hey it's it's a journey and wants a better time.

A

Good and now uh tomomi, uh considering you've been in the slack in the past, and and obviously you can't talk about too much on on too many things. But what how would you kind of characterize the differences between slack and, for example, the microsoft teams, or or or let's say.

C

Microsoft, so they are really quite different products and, of course, you know as a consumer product perspective like it when we're talking about just the product, everybody think about their competing products right. So to be honest, when I joined microsoft, it was a huge shock to my friends and everybody's asking me: it's like. Oh my gosh. How dare you type of you know reaction, but yeah, that's a long story anyways.

C

But for me for, like a cloud advocacy person for like a developer perspective, those two are not competing at all because well many times your employer decide what which to use. So it's not developers too it's first of all and the second of all, of course, it's kind of like ios and android so many times app developers wants to develop for both platform right, but.

B

C

Same issue, those two when you're developing for ios and android, those experience are quite different and you don't want to. Of course people try to, but you don't want to just build one app and expect work for both nicely with same level of user experience that just usually until I mean unless it's a simple super, simple app. It just doesn't work that way. You have to still write from scratch. Then, of course it sounds like such a pain.

C

You know working on two or three different platforms, but still that's really the way it is, and I always have to tell people that those two products are quite different, comes with totally different features, and uh you know uh technology stacks and everything. So just don't think or don't even try to compare. You know right. If you try to compete, I try to even create a comparison chart and I'm like uh maybe not a good idea. It's like a product or a feature to feature comparison, but they don't align really.

C

You know, because slack is just that one product, it doesn't even come with apis for, like let's say, meeting because they rely on what actually slack does have meeting, but usually people rely on the third party like soon. So, if you want to create something for video type of a meeting, you have to use the zoom apis and things things like that. But still api is the same like one api. As far as teams are so many different, like teams tabs has different api or more like technology stuck like sdk teams.

C

Sdk bot has a bot framework which is even larger products, so it's not only for teams, but you can create all kind of chat, bots and stuff boots, but that kind of you know relationships and graph, of course, there's so many different technologies and bits and pieces, and that might be a huge confusion for people who are new to teams, but like again, it's like apple, no oranges or whatever. It's just it's hard to compare yeah I can go on and on and on two different.

C

You know products yeah, maybe competing, but not really for us. Yeah.

B

Yeah, but but this, but it is in an interesting point that one especially, I think that we don't often spend time uh thinking about like that, as you say, like four devs, like one oftentimes, somebody else says, companyx uses this or that it's not devs that say: hey we're, gonna, use this and then two.

B

If you are isv and you build a product like I don't know, let's call adobe or it's like you want to have your app everywhere, because you want to reach as many people as you can as opposed to you know, we will only build for this or that right so so, like, as you said, exactly like from our point of view, we cater like it's not a compete like we cater yeah.

A

B

Can just like they're interested in just as much in our stuff as they are interested in anything else and there's no way around it. That's actually.

A

A good perspective, absolutely that's a good point, and then eventually it's well coming back on on what tommy has already said, related on the documentation as an example. It's it's it's not about the apis, it's all about explaining the scenarios and what you can do within the within the product. So, and I think it was russia's well pretty high on the on the food chain who said that it's all about educating customers and partners on the art of possible.

C

A

So that people understand that okay, I can actually include my lob application line of business application. I can integrate the relevant pieces directly in microsoft teams the relevant pieces- that's all of it necessarily, and I can surface some of the kpis and whatever values there and then and then I can actually ask my developers to do that, or a system integrator to do that or whatever. Whatever is the the use case. So it's really around making sure that those people who have the authority of assigning the developers to work.

B

A

Things to educate them on the art of possible yeah.

A

Yeah so let's see we're doing a lot of stuff actually there for microsoft teams and for the m365 area, which will be live later this year, but we can't talk about all of that stuff, yet just yet working on it working on it. Yes, absolutely now. What else do we want to talk about uh articles should.

B

We talk to the articles. Yes, let's do a bunch.

A

And then we'll come back on a closer uh in here, so let me share my screen. Let's talk about articles and samples and all of that stuff as well- and I just realized that I'm missing one thing here- it's fine!

A

I will show it when we are on the same page anyway from the team's block, uh introducing soho notebook for microsoft themes, so bringing your thoughts and teams together, basically a partner showcase on on how things can work, and I think these are super valuable as well for other partners to understand what's possible and what can be actually done within the team's platform as an example. So.

B

A personal tab, I think, right, if I'm not mistaken,.

A

Seems to be they're actually hiding the left menu, which is slightly weird, um that it's cut away, but um it seems to be a personal tab, yeah and then you can actually access the information there. So embedding that- and this one is for microsoft partners with salesforce to deliver microsoft, dnc integration for sales and service, which is actually pretty interesting.

A

I haven't really analyzed an and had a super detailed look on this one, but it's really around in the creations on the sales.

B

A

And on the tabs and all of that stuff, this actually makes a lot of sense uh so having a true integration with salesforce leads and all of that stuff directly within the product so makes a lot of sense. Good example. By the way again on what the art of possible, then we have the intro zone, which is one of the broadcast series from mark cashman right point with customer. We are in a partner week.

A

Apparently every single news is their own partners, but this is really around at the right point and then having a discussion what they build and how they build that and the power platform and using that in the microsoft 365 suit. So good stories related on, what's possible again on educating people now. This one is really interesting around the microsoft teams, apis, so importing third-party platform messages to microsoft. Teams is now available in beta, and I think we we had an interesting discussion related to this one before we started recording.

A

But this is something what tomomi you said that people are asking about this one right.

C

Yeah a lot of people well, so the thing is, a lot of companies has been migrating from one platform to teams right and, of course, you know, people don't want to have the old conversation left in all the platforms, so one at all migrate. Everything. So that's great that we finally have that in beta.

A

Absolutely absolutely, and that there's the super critical thing which I was thinking uh is that you can actually create messages with a back in time. Timestamp.

B

Keep general messages yeah.

A

Yeah, absolutely, you can actually then truly fulfill for the time when it actually was happening in the external system. So that's really really cool. So that is simple.

A

Now this one: um it's not around microsoft, 365 explicitly, but the technology is so it's it's actually. Microsoft forms is now available for personal use and that's actually pretty cool, so I think it's completely free and you can actually use that within your microsoft account um so, which is really really cool as part of the same setup as the outlook.

A

Sorry, the outlook and onedrive and all of that stuff, so yeah and and this one microsoft, 365, developer, podcast came alive today as well, and this is really around the azure communication services which we announced in ignite. So that's a few weeks back uh really concentrating on that one.

A

So paul had a discussion with john henry on that one, and then, if you're wondering what is a azure communication services, it's actually something really really really really cool, which says pretty much over there, which is basically it's the platform which microsoft teams is using for all of the communication channels and that's really cool.

B

So, in our words, like teams without teams, client, imagine that that you can embed a video call in your own app yeah or other things like chat or text or whatever.

A

Yeah, that's really really cool so, and this one is tomomi from you. You can actually yeah that looks familiar.

C

B

C

So this is a second of this beginner series of uh the team's development tutorial like I was saying earlier, you know as a person like new person, new developer to microsoft and, of course, teams and everything. So you know I obviously know we wanted to target a lot of people.

C

Just like me, you know the new developers, um people who have been you know developing on other platforms like teams and zooming or whatever you know there are a lot of people who are not familiar with any of the microsoft technological system, so I'm definitely targeting those kind of people to tell them like easiest possible way to show how to create. I think this tutorial is particularly for conversational bots and the previous one was tabs, so I'm planning to write on another one, for I believe it's a message and extensions or something yeah.

A

C

A

Makes perfect sense then, and for those who are not aware, uh please sign up for the microsoft really 65 developer program. You will get a free free free subscription and it will be automatically renewed as long as you use it for developer usage. So we have a telemetry and ins in place, which is basically detecting that, oh, if you're using it for developer usage, it's going to renew automatically it's really cool now and this one. We wanted to actually talk about this one.

A

This is where actually, I forgot about adding a one tap, which is akms teams, samples and that's basically, a microsoft teams, development samples, plenty of samples already available and- and you can actually look into these samples from multiple different angles. So you can have a look on the client language perspective or you can have a bot framework if it's support related or server language if it has a back end as well as uh but youtube mummy had here, an http status, cad.

C

Oh yeah, that's something I made yeah! So that's really, basically a http status called lookup, so you can use either this uh message composing window. What is the real name for this?

C

So you can look it up from the two different places on the team's client and, of course you know each because it's http status cat, so each status comes with cat picture, and this is something I originally created, like http status cat, so originally created by myself like nine years ago, and that time he really gave me a 15 minutes of fame on all internet.

C

This time I finally created one for teams. Now this is actually available for slack and discord as well. I didn't make one for this called my uh former former colleague from slack have created one for discord.

A

And pretty recently actually had a video demo on this one as well. So this one was last week uh from the microsoft team's monthly computer called um where you actually demo the solution and the box toucher. So.

C

Yeah I gave in eight o'clock in the morning so 404.

B

A

A

Cool, let's, let's go through some other articles, so jarpa's forest from bolo internet had a microsoft graph api to create teams. It's now ga and supports new permission level. So, basically there's a new set of permissions and the more specific permission levels uh available as well, which is really cool, and so you can actually just you don't have to have a massive level of permission. Granted only team create to be able to make things happen um also from an application perspective. It's really really cool.

A

um This one was from alex torrential from sharepoint list outlook on sharepoint events, time zones and display. So it's really.

B

The hardest topic ever seriously: it's not only time zones display days like you just pack, all of these the hardest things ever into one.

C

Especially now you know some.

B

C

Of yeah the standout time daylight same. What? What do you call summertime.

A

B

C

Saving time so yeah.

B

C

Still in daylight, saving now here in the summertime started in southern hemisphere, so it's so confusing.

B

Because, like like first like two weeks back, it was in australia, uh I think brisbane or melbourne moved brisbane did not now it's us, then, in a few weeks time it will be you in the u.s yeah. It's like the whole world is just like in this state of like we're moving.

A

Crazy, luckily, luckily, outlook works nowadays. So that's it so.

C

Yeah I've seen a google.

A

C

Have prep yeah the broken, sometimes too, I think.

A

C

The global issue for anybody in any companies yeah.

A

Good, um that's a good summary on how things work, how to look at things, and this is from louis fries. So microsoft, 365, developer bootcamp happened last week and this is a summary from her related on uh participating there and having a participating on the training and she's always telling that she's not a developer. She was a visitor in our show as well, but she's getting the beer developer. I I think it's unfair to say that she's not.

B

More developer than she, she is willing to admit.

C

B

The whole thing like a champ: she had everything ready like. I think she was even one of the first folks who went through all of it like, and you don't quite call yourself. There.

C

B

She's, even holding that there with the nails, the foils on her on her hair, like.

C

B

C

A

Is yes, excellent, excellent stuff and a really great summary related on the on the experience and and how to get started, and this is referencing also the the tutorials and samples and all of that stuff, so really great blog post.

A

Now the moment you, oh sorry, this is not tomorrow with dysrubia.

A

Hosting my first ever developer, bootcamp so related on the luis's message. This is actually robia who hosted that and then explaining her experience related on that and how do we? How what what was built and how was that, how the things were set up so really cool as well. So.

A

Yeah so, and really good good stories on learnings and what works and what doesn't and what are the assets on those things here, we have from shandani spfx cascading drop down in property pain, so basically how to build a pro cascading drop down in the property pane of spfx when you're configuring, a web part or a tab of microsoft themes, because any single web part actually works. Microsoft teams tab.

A

So how do we implement that and how to do a cascading thing and experience over there? So good summary, blog post from her on that? Then we have four different videos, so this one is from giuliano de luca microsoft teams how to create your personal space. For me, experience in microsoft themes while deck, I think you're pretty familiar with this setup.

B

Yeah, so I think, two weeks back or so, we launched a new article in docs about the um the idea of building a me experience in teams. Right like, as we know, teams is all about collaboration and us as a team. But then why not include this me experience that that you can use to easily get um overview of your upcoming meetings, recent files and so forth, and so on.

B

So so, in order to have everything in single place, as opposed to having your team collaboration things in teams, but then for personal stuff, like you need to go elsewhere right- and uh this is a video basically explaining the concept and lyanna also includes a link to a repo in which he has a manifest of a working app. So he takes it to the next step. Yeah.

A

So and really cool setup, so basically he's he's combining the also the sharepoint online pages, which then have dynamic web parts from chip and starter kit and then we're surfacing that as an individual experience inside of the microsoft teams, so pretty complex setup, but absolutely quite quite simple way in the end. Actually making things happen, because this doesn't require necessarily any code. All of these samples we've already.

B

Built right, so yes, that's true.

A

Yes, that is true cool, uh and this one is from our uh italian friend, paula who's, releasing his uh weekly videos- and this is really around the white at the bmp core sdk, so the microsoft craft, first library, which is always hitting the craft and then fall backing on the non-aircraft apis. Only if those, if the api is not available in microsoft, graph, so pretty cool setup as well, breaching the gap between the classic classic development style and then the microsoft graph.

A

This one uh is from marcus miller uh also from the same teams called where mommy and tommy uh were uh showing the the sample uh or demo, but this is around building a microsoft theme, messaging extension with authentication and access to microsoft, craft, so nice 10-minute demo, on on how that works and the sample is available in the same github repo by the way and because we absolutely want to have a centralized location where people can find microsoft team samples so that we want to make it. That's super super easy for people to find them.

A

Well, it doesn't mean that they all have to be in one repo, but still surfaced on one location and then this one, uh a really really cool setup, was also watching.

A

This live so microsoft themes apps for meeting from righteous uh who's, the I think he's actually the bm of this feature, uh some marks from microsoft team site and it's really around building those experiences so pre-meeting, and during meeting and post meeting experiences related on showing uh functionalities like on the on the site, tab or doing a dialogues and pop-ups during the meeting so really kind of making the meeting experience to a new level.

A

So you can actually ask input and surveys and all of that stuff and then the last one was from christoph a temporary message on top of your sharepoint page, not necessarily the recommended way of doing things because he's actually doing a http.

A

Sorry, a css hack here, but kind of a really really simple way of adding uh something on the on the page. So if you want to have a halloween themed pages, you can really easily do that cool. But in general you should not uh have a dependency on css, hacks or dome structure. So that's not a good thing in sharepoint.

A

A

Why? Why? Because we might change the dome structure. So basically, that's a good huge point and we had pretty two weeks ago we had a change on the modern pages, dom structure in the sharepoint and that caused some of the the headache for some of the sharepoint isvs and partners, because they had a dependency on the dom html dom structure, because they thought that microsoft will not change that now. Nobody from engineering, all everybody in engineering was thinking that everybody knows that you should not have a dependency on the dome structure, but it.

B

Turns out people don't yeah yeah mix and repeat rinse and repeat.

A

But you should not do that. So just a reminder on that, but I think that's all the articles this time. So, let's get in here, we still have a few minutes time. So what's happening this week, it's monday anything cool anything.

B

A

Yeah happening this week, what are you planning to do this week? Anything which we're going to hop on.

C

Oh, you know what tomorrow is my birthday. I just realized. Congratulations.

A

C

Candles, oh my gosh. It's today 26 cake yeah. I put the halloween header there too. Yeah.

B

A

B

C

Yes, this week here, oh wow, it's end of october. Already time flies.

A

It is so you're planning to do blocking, obviously more stuff material, anything anything special.

A

Interesting, okay, what about you? While they get anything interesting this week,.

B

A lot well, I am a little all over the place, I'm trying to see thank you so organized actually, so it's so organized in chaos. um So what for one thing, I'm looking into the ability to for us to be able to update the starter kit to use uh the microsoft graph toolkit, where applicable, because, like we've built it way back when and back then took it, wasn't there. So we built everything ourselves, which means that we added heaps of code that we can avoid now.

B

So I think with that. It might be a great case for us to show maybe even include migration path like we've built that code ourselves, like you, would in real life by yourself and now like like what what are the different steps, if you want to move that to the toolkit right, so that is one two.

B

I also realized that we have tons of samples built in spfx of web parts and extensions and again use graph, but don't use toolkit so yeah is there maybe a way for us to upgrade some of them and show like hey? If you want to build that kind of web part or extension, here's how you can do.

A

B

Or a microsoft team, you would expose it eventually, yes exactly well, so maybe there are even samples that are built as web bars but are not exposed in teams.

B

Another thing for us to look at like how can you build it once and expose it both in sharepoint on pages, as well as in teams? um I'm just doing the latest fixes to get published a new, getting started tutorial with uh microsoft, graph toolkit and react. So there's like almost done like one of two things needs to be fixed and then it's it's live uh and again like the one thing that needs to be fixed is what off yeah.

A

That's always too hard hard thing.

B

Everything yeah, so it's there and the way we want to go about it is that, like the off part, it's it's exactly the same, whether you build an app in react in angular or in in something else. So the way we want to do it is that they want to extract that part and and have it as a reusable block that we can just stab into every walkthrough, because otherwise what you have a walkthrough there's the link.

B

So we have to open this tab and do something in there and then go back like this experience is really poor. So so, instead, we're gonna have it embedded in the walk stream. You said like one article but then not having to maintain the same bits and piece like three times or four times yeah um anything else I mean um other than that. We keep working on cli for our m365.

B

We have heaps of new prs that we need to go through contributors with school exactly so that is also there um anything else. uh That would be pro, probably it. I think that by itself already, that's like a lot of problems. That's a lot of.

C

A

Well, I'm focusing this week on on finalizing the plans and designs for our upcoming m365 scoped sample gallery, which is really cool and then we're working on an extensibility lookbook, which is actually incredible.

B

I have a thing to do in that too right.

A

I think you do, I think you might anyway so, but that's progressing and we're trying to get uh first versions out relatively actually fast, so really showcasing what you can do in the m365 from a extensibility perspective, again, really focusing on that art of possible with fancy pictures like tomomi was saying that we need to explain what's possible rather than just the api and technology.

B

The one the one thing we didn't talk about are doodles to mommy.

C

Oh gosh yeah, so.

B

C

Yeah yeah I do and the especially technology doodle, I would say.

B

One of my expertise is really.

C

Yeah converting like really hard to explain technology into easy to digest doodle, so I'm actually working on a bunch of noodles for not for our own team, because I participate in a bunch of other v team project, so I'm actually working on this uh web dev 101. So this is another beginners tutorial and walkthrough like workshop for, um especially for like teachers who wants to teach students but like for, could be anybody so as like what is programming, languages or whatever javascript, and then what is variables or how to use github, and things like that.

C

So that's all yeah describing my doodle, so yeah I've been working on that, along with my own main project too.

B

There you go, I mean I'd love to see one for like how would you um picture journey like where do you start with m365 dev and what are different routes you can take and what are different things like doodle dad.

C

Yes do that, but I have to understand everything.

B

Right so I'm still learning.

C

B

C

Seen 360., why me? What did I say right number I almost I anyways 300 600, it doesn't matter and whatever it has a massive amount of you know myriads of products and technology, and I have to understand it first. So again, I'm still learning so I'm gonna bug you a lot both of you.

A

Yeah, that's that's all good! Now now, that's actually good! Before we close, that's the one thing. What I want to tell you both um because your cloud advocates- I don't need to answer on this, but um so putting on yes, no, no! No, but I'm thinking around to mommy. You were saying really well that the m3 survivor is one of the it's it's a massive platform and we're having this challenge of explaining the opportunities of that for departments.

A

How would you define what is the opportunity on and why partners would be, should be interested on microsoft 365.? What is the you can you can absolutely have a open discussion on this, but what would be your way of kind of clarifying a let's say, a partner who's, not aware of the opportunity? Why would they need to be interested.

C

You came in hard questions.

B

All right, so with that, let me take one I will give you a moment to think like like you to your time.

C

I think it's just great to have all the bits and pieces connected all together. You know and that's like related to the earlier questions about difference between two platform-like teams and slack.

C

I think the massive like biggest difference I didn't mention, was probably that you know teams can connect with all other products out there in one place without you know letting anyone leave the platform, so that's really the one huge strength and that a lot of new developers like myself aren't aware of and the more you look at and the more you find you know so that can be super confusing.

C

So many things to learn and overwhelming, like I am but the same time you can level it so many different areas within a products not about just the user, but other products, calendars and notes and everything. So that's pretty cool yeah.

B

I don't have much to add to that. I mean I mean like few things you could at that are more like. If you would think about the market side right so enter through twice is big, like there are 250 million users who you who work with that every day. So if you are ise or you build an app, that's a massive market, you can reach right. So that is one two microsoft is: um has resources that help you land these apps right?

B

So there are whole teams that are all about helping you to understand, go to market, giving your resources helping you from the business side, tech side, whatever you actually need right, and there are whole teams for partners to use to benefit. Is there anything else like? Another thing is which is interesting, and I think we didn't talk about that that in the past like if you build an app like that app needs to live somewhere.

B

What you can do is, like sure, you're you can host it whatever you like, but the benefit you get, if you would put it on azure, is that it's the same microsoft cloud? So there will be less cost because your app will go like date within the data source connections. So there'll be less cost for you to run that because the data will not go out. The data sources go back right, yeah.

C

Sorry I lost the connection.

B

Yeah no worries, uh we talked about azure and money right so so, and that is that and two like. If there is enterprise who is 365 like oftentimes, they have requirements for compliance, data, sovereignty and so forth, and so on. If your app lives in azure by default, you get the same benefits for your app as customers get for 365..

B

So it's way easier for you as a vendor to answer any kind of form that they might have as a requirement for your app than if you would host it like under your desk.

A

Yeah yeah absolutely and then there's this. Obviously, if it's an usher, it's a bit bad tools and a different kind of set of tools which you still need to implement. But then m365 is really around the actual services which you're combining not just tools and the data which you're combining so, and so it's almost like an abstraction layer on top of well, it is an abstraction on top of.

B

A

So and then it's all about combining things and then still taking advantage structure so.

B

In the end, to also like graph right, it's just like one api that that allows you to tap into this myriad of products. Right, I mean there's email, there's calendar, there's meeting, there's notes and you don't need to learn as a dev, 20 million ways to talk to each one of them. You have just like one api that you can get. For example, a meeting from meeting you can get attendees from attendees. You can get managers for each one. You can get file for a file. You can get something else.

B

It's like you go from one server to another using the same api. Yes, that is nothing you. You will see anywhere else.

A

Yep, absolutely absolutely cool, I think that's pretty much it uh for this one. So thank you to mommy for joining us. Thank you and and thank you for a good discussion. It's always good, interesting to have a different perspective and, and you come from a different world, so to say so it's actually good. You can.

B

Say what are you saying.

A

But it's good to hear the different perspective and I'm sure that the listeners or watchers. I agree on that. One as well, and thank you waldec once again and we'll be back with a new pmp weekly in a.

B

Week, a month.

A

So, thank you, everybody bye-bye, thank you. Versa. Bye.