WEBVTT
00:00:00.239 --> 00:00:02.799
Yo, I tell you what I wanna wanna really really want.
00:00:02.879 --> 00:00:04.799
Just tell me what you want what you really really want.
00:00:04.879 --> 00:00:06.799
I tell you what I wanna wanna really really wanna.
00:00:06.959 --> 00:00:24.879
Just tell me what you want I wanna really really wanna wanna I wanna I wanna I wanna I wanna really really really wanna zig a zig morning.
00:00:25.120 --> 00:00:26.960
I don't know, I just had that song in my head this morning.
00:00:27.039 --> 00:00:27.519
I don't know why.
00:00:28.079 --> 00:00:30.879
Um you should see a doctor, maybe.
00:00:31.120 --> 00:00:32.000
I don't know.
00:00:32.240 --> 00:00:36.479
I I unfortunately I had a young sister growing up who listened to that stuff all the time.
00:00:36.640 --> 00:00:41.119
So actually, most of the Spice Girl songs are permanently ingrained in my memory.
00:00:41.200 --> 00:00:44.079
So you know that's my party trick, should we say?
00:00:45.039 --> 00:00:46.000
I see, I see.
00:00:46.159 --> 00:00:53.359
What a great, great party trick to start off a new episode of the Unresolved Dependencies Podcast.
00:00:53.520 --> 00:00:54.960
Episode 16.
00:00:55.520 --> 00:01:00.719
That's 13 more episodes than I thought we were gonna do, but we are keeping going.
00:01:01.359 --> 00:01:04.000
We're in a good rhythm, like we're able to do stuff.
00:01:04.079 --> 00:01:07.280
We we've all we've kind of got our roles and responsibilities.
00:01:07.359 --> 00:01:10.159
Um, everyone we both kind of know what we're doing.
00:01:10.319 --> 00:01:13.120
You don't have to like um chase me as often anymore.
00:01:13.200 --> 00:01:15.120
I just kind of get my shit together.
00:01:15.200 --> 00:01:18.959
So yeah, I think we're finally we've got a good groove going on, it feels like.
00:01:19.439 --> 00:01:24.400
All you want to say is that you're coming in prepared now, and you also have topics, right?
00:01:24.640 --> 00:01:25.200
I too.
00:01:25.359 --> 00:01:26.319
I do have topics today.
00:01:27.200 --> 00:01:29.519
I actually literally wrote them down and sent them to you as well.
00:01:29.599 --> 00:01:31.439
So I mean that's my amp.
00:01:31.840 --> 00:01:32.959
That's the crazy part.
00:01:33.840 --> 00:01:35.120
That is the crazy part.
00:01:35.200 --> 00:01:39.519
Um, but you know what's crazy is what's what the craziest thing in the world is Joe's travels.
00:01:40.079 --> 00:01:47.280
So the mileage consumption is very close to my AI token consumption, but let's not talk about that.
00:01:47.519 --> 00:01:49.280
Talk about your travels.
00:01:49.760 --> 00:01:51.599
Yes, where have you been?
00:01:51.680 --> 00:01:52.239
Where are you?
00:01:52.319 --> 00:01:53.599
Where are you next?
00:01:53.840 --> 00:01:55.760
So let me give you the answer from the previous clue.
00:01:55.840 --> 00:01:59.200
So, again, the inbox was absolutely smashed full of responses.
00:01:59.359 --> 00:02:01.439
Uh, clearly the most popular feature in the world.
00:02:01.519 --> 00:02:03.439
So, so much love for this feature.
00:02:03.599 --> 00:02:07.200
Um, so the answer for the clue for last time was Barcelona.
00:02:07.359 --> 00:02:11.919
I was in Barcelona for the European fabric and sequel con.
00:02:12.319 --> 00:02:16.400
I had a very nice time there as well, even though it was a condensed a little bit too short.
00:02:16.560 --> 00:02:22.639
So, yes, Barcelona, lovely city, great food, great tapas, great sangria, definitely would recommend you sort of go in there.
00:02:22.719 --> 00:02:25.039
So the sangria made you go.
00:02:25.120 --> 00:02:25.840
Yeah, okay.
00:02:26.080 --> 00:02:27.199
No, no, it was learning.
00:02:27.280 --> 00:02:28.319
I want to learn about fabric.
00:02:28.560 --> 00:02:29.120
Fabric.
00:02:29.199 --> 00:02:34.400
What's and I'm and I may have been converted, I may have been converted over to the fabric side.
00:02:34.479 --> 00:02:35.840
Um, let's just see.
00:02:36.000 --> 00:02:39.599
Um, but anyway, let's not get into that whole uh rabbit hole there.
00:02:39.680 --> 00:02:41.199
So uh so that was the answer last time.
00:02:41.280 --> 00:02:52.159
So if you did want to play along and you want to and you want to sort of get involved, you can drop us an email, hello at unresolved dependencies.com, or alternatively just drop us an answer on the socials when you see those funny reels come up.
00:02:52.240 --> 00:02:53.199
We'd be happy to hear from you.
00:02:53.280 --> 00:02:56.080
So, my next clue where is Joe traveling next?
00:02:56.240 --> 00:03:10.639
I am travelling to the first capital city in the northern American United States that that fell to Union forces during the American Civil War, and which is famous for its riveting music scene.
00:03:10.960 --> 00:03:12.879
Where am I going to next?
00:03:13.039 --> 00:03:13.840
Let us know in the email.
00:03:14.960 --> 00:03:18.000
Music scene, that's maybe a big hint, Darryl.
00:03:18.159 --> 00:03:23.439
Because of, I mean, of course, all of our listeners would have gasted with like um the first hint.
00:03:23.520 --> 00:03:36.560
Um, that is very much obvious if you're our core our core listeners are just a bunch of uh history nerds, you know, living in their basements, or that's obsessed with these obscure military facts, uh, particularly relating to the uh the American Civil War.
00:03:36.639 --> 00:03:39.120
So, yeah, clearly I'm also giving it away too easily with that one.
00:03:39.199 --> 00:03:43.280
But if not, then I'll give you a nice easy clue to sort of give you uh to help you along there.
00:03:44.560 --> 00:03:45.599
Nice, nice.
00:03:45.840 --> 00:03:47.680
Yeah, so a lot of travel again.
00:03:47.759 --> 00:03:49.280
Um, I'm also traveling.
00:03:49.439 --> 00:03:54.319
Um you're going to quite an interesting place, aren't you?
00:03:54.800 --> 00:03:57.919
I'm going to Singapore actually, um, over the weekend.
00:03:58.080 --> 00:04:10.560
Um actually, I'm going there for the Microsoft AI tour that happens um basically on the day you are listening to this podcast.
00:04:10.800 --> 00:04:13.120
Um, so I'm traveling all the weekend to Singapore.
00:04:13.759 --> 00:04:17.360
But this also falls into the same week with my vacation.
00:04:17.439 --> 00:04:32.480
So I'm only going there um doing my session there with uh colleague of us, um, meeting with the fabulous Daniel Laskowitz because he will be there as well, and then going back home because then I want to enjoy some days off.
00:04:33.680 --> 00:04:34.720
That's the plan.
00:04:35.120 --> 00:04:37.120
Or Dan be going to Vegas.
00:04:37.439 --> 00:04:43.279
So then you need to get a photo with Daniel and you need to get him to say something nice about the podcast, and then yeah, that's your mission.
00:04:43.680 --> 00:04:48.480
Let's start with the photo, um, and then let's see what happens from there.
00:04:49.040 --> 00:04:55.120
Um yeah, but basically we we saw Daniel uh a few days ago.
00:04:55.279 --> 00:04:56.480
So at the Scottish Summit.
00:04:57.120 --> 00:05:02.800
Scottish Summit, yeah, where we did have some uh maybe this this could be Sebastian's uh eats for this week.
00:05:02.879 --> 00:05:04.560
We did have some quite nice food there, didn't we?
00:05:04.639 --> 00:05:06.720
Like street-related kind of food.
00:05:06.879 --> 00:05:07.680
I quite liked it.
00:05:08.000 --> 00:05:43.839
Yeah, this was it was quite well, but it was not the the Sebastian's food of the week because um I was not only at Scottish Summit um the last days, I was also at the AI Paloozer in uh Stuttgart, which is a German event, and there we went out um for dinner because we were as well um exhibited there, so we were had a little booth, and I was there with some colleagues, and then we said, Hey, in the evening, let's go out for some nice dinner, because one of them was well happy birthday, and I was like, Come on, let's go.
00:05:44.240 --> 00:05:46.079
Um, got some nice food in.
00:05:46.240 --> 00:05:52.959
She wanted to have an Italian um uh dish, and so we can uh so we went for burgers.
00:05:53.600 --> 00:05:56.959
Just kidding, the Italian place was closed.
00:05:57.439 --> 00:06:00.480
So it was not right.
00:06:00.800 --> 00:06:03.120
So so so ignore what you want, it's your birthday.
00:06:03.279 --> 00:06:06.560
We tried your first choice, so we're going for burgers, and you like it all.
00:06:07.120 --> 00:06:09.120
Oh by by the way, happy birthday.
00:06:10.240 --> 00:06:11.600
Yeah, exactly like that.
00:06:11.759 --> 00:06:12.800
No, no, no.
00:06:13.759 --> 00:06:28.879
No, um actually we went to the Italian place, but it was already quite late because the event, I think it was pretty interesting because the event started like at 10, and then the first session or so was at 12, and um then it all goes on the first day to like 7 p.m.
00:06:28.959 --> 00:06:35.279
or so, and then you go back to the hotel, get refreshed, and then um till you then make it to the restaurant.
00:06:35.360 --> 00:06:40.240
Then the restaurant was like, uh guys, we don't have the kitchen's closed.
00:06:40.480 --> 00:06:54.879
So then we went to a burger place, and I really had a very nice um bowl which uh made with bulgur, tomatoes, um cottage cheese, some bread, chicken on top, salad.
00:06:54.959 --> 00:06:59.439
So it's a pretty nice, a lot of nuts, and on the side some fries.
00:06:59.600 --> 00:07:01.360
And do you know what is the best?
00:07:02.240 --> 00:07:09.759
I took a picture, so you can upload that later on to the to the socials, which I then um if I will share it with you.
00:07:09.839 --> 00:07:15.519
Sorry, but yeah, I I took a picture and then um we can grab that.
00:07:15.759 --> 00:07:20.399
Yeah, so it's kind of like a deconstructed burger almost.
00:07:20.959 --> 00:07:25.040
Yes, yes, but but with less spread actually, um, but it was really nice.
00:07:25.120 --> 00:07:29.680
So it was a it was a huge potion, so it was literally like a bald bowl thing.
00:07:29.920 --> 00:07:35.120
Um but it was it was uh very very nice and good, yeah.
00:07:35.360 --> 00:07:36.399
Very delicious.
00:07:36.639 --> 00:07:38.720
Fantastic, fantastic.
00:07:39.360 --> 00:07:39.839
Thank you.
00:07:40.000 --> 00:07:44.240
So yeah, speaking of Scottish Summit, it was uh yeah, it was I had a lot of fun.
00:07:44.319 --> 00:07:47.839
We were both in Edinburgh, we were sharing an Airbnb together.
00:07:48.000 --> 00:07:51.920
Um you left without saying goodbye, but we won't we won't dwell on that, obviously.
00:07:52.160 --> 00:07:58.480
Um well you were still in bed, I think, so I didn't want to wake you up after the heavy party night we had.
00:07:58.560 --> 00:08:01.439
So um I decided uh it's eight o'clock in the morning.
00:08:01.600 --> 00:08:10.560
I'm struggling a bit to um make my way to the airport, so let's leave, let's let Joe sleep and not make any mess.
00:08:10.639 --> 00:08:17.199
And therefore, just just just just just remember, I may or may not have pictures of you in a pink cowboy hat.
00:08:17.279 --> 00:08:20.000
So you know, just think on, always think on.
00:08:20.240 --> 00:08:23.279
Yeah, it's the the 100 episode special, maybe.
00:08:23.439 --> 00:08:24.720
Um, but I traded this.
00:08:24.879 --> 00:08:28.000
I traded the the pink cowboy heat later, actually.
00:08:28.160 --> 00:08:34.240
Um with a guy on the street to to a cat, which to get home, yeah, yeah.
00:08:34.720 --> 00:08:40.080
Yeah, please, please not like not like a cap, so not an Uber cab, but like a hat.
00:08:40.240 --> 00:08:42.960
So um, so yeah.
00:08:44.480 --> 00:08:45.120
It was fun.
00:08:45.200 --> 00:08:46.240
Yeah, fun night.
00:08:46.320 --> 00:08:50.879
Um, but as as people say, what happens in Edinburgh stays in Edinburgh.
00:08:51.759 --> 00:08:53.840
Yeah, but it was a very interesting event.
00:08:53.919 --> 00:09:00.320
We both had sessions, uh Asian 365 session with AJ, which I think was very well received.
00:09:00.480 --> 00:09:11.120
Um, some of the feedbacks, feedback was quite good, some of it was a bit concerning in terms of you know, very, shall we say, um, amorous comments directed towards me and AJ.
00:09:11.360 --> 00:09:14.159
Um, so I mean, I'll I'll take it where I can get it, obviously.
00:09:14.399 --> 00:09:16.960
But uh, yeah, just uh maybe just calm down a bit in the future.
00:09:17.039 --> 00:09:18.080
So that was a good session.
00:09:18.159 --> 00:09:20.879
Uh and then I gate crashed your session, didn't I?
00:09:21.039 --> 00:09:22.480
Um yes, you did.
00:09:22.559 --> 00:09:24.879
There was even like a comment going in this direction.
00:09:25.039 --> 00:09:28.399
So overall, so we talked about um yeah, yeah.
00:09:28.480 --> 00:09:31.039
Who who is this guy and why is he ruining the session?
00:09:31.360 --> 00:09:31.840
Lovely session.
00:09:32.000 --> 00:09:32.480
Something like this.
00:09:33.519 --> 00:09:35.759
Um I I just don't know.
00:09:35.919 --> 00:09:39.440
Um sorry, that's firstly start with the session itself.
00:09:39.600 --> 00:10:18.000
So the session was on Agent Builder versus Copala Studio, which um at the point when I submitted the session, um and as well when we did it, or when I did it with Andrew Bibby in uh Color Cloud earlier this year, the the line in between was was made uh tougher and it was may more fixed um than it is meanwhile, because meanwhile we as well have skills there, we do have plenty um of of reasons why we should build something on Agent Builder over um using Coparty Studio for certain use cases.
00:10:18.240 --> 00:10:21.840
Back in the days, this was much more limited and much more clear.
00:10:22.000 --> 00:10:40.960
Um, so it was a bit more blurry, but this is this is my most seen issue lately with session submission submissions that at the moment you submit something, you're pretty sure that you need to rework half of the idea literally till the event happens.
00:10:41.120 --> 00:10:54.480
So that's a bit weird, but nevertheless, um, because Andrew was not there at Scotter Summit, I then asked you and you volunteered to jump on me, uh jump jump on me, jump with me on the stage.
00:10:55.600 --> 00:10:56.879
Yeah, jump on me literally.
00:10:56.960 --> 00:11:42.080
But there was so overall the feedback was very, very positive, and people liked the awkwardness, and uh it's a bit more funny and loose, but there was like one concerning comment which was like say, like only twos and threes in terms of the um uh reason like ratings, and that was like, yeah, there were so one of the guys clearly knew what he was talking about, while the other one was constantly like challenging him and um disturbing him, which would look like very unprofessional, and and no professional okay, and so no, we don't we know we have one clearly because because we interrupted ourselves the whole time because this was part of the little like fight between agent building and cowboy studio.
00:11:42.320 --> 00:11:46.240
So I I'm not sure who was who in the story.
00:11:46.480 --> 00:11:50.559
So even you have to sit your i have it, I have a suspicion.
00:11:50.639 --> 00:11:54.000
So if the person is listening to this, then yeah, I I do apologize.
00:11:54.240 --> 00:12:04.639
We were trying to keep the session fairly fairly light, and the whole objective was okay, we're trying to show um each person is trying to basically show that their technology is the better.
00:12:04.720 --> 00:12:09.600
So it was kind of all meant in good sort of um ribbing, should we say?
00:12:09.840 --> 00:12:25.200
Yeah, it was the idea of of the session to to have those little fights on stage, basically, yeah, to challenge the other person as well with with weird questions or um telling how the products or the other technology is better than the other.
00:12:25.519 --> 00:12:26.480
Yeah, but yeah, for sure.
00:12:26.639 --> 00:12:29.440
Overall, Scottish summit cabaret, you won a price.
00:12:29.519 --> 00:12:30.639
The podcast didn't.
00:12:30.879 --> 00:12:40.480
So how how do you feel now after a few days and it has settled down that you are an UK community award winner again?
00:12:40.960 --> 00:12:44.720
Yeah, so I was actually texting Urika about this, actually.
00:12:44.799 --> 00:12:57.279
So, yeah, obviously, very well, very well done to M365 to still for winning that award, but but clearly, you know, um podcasts involving alcohol, you know, it just tells tells the story in terms of where people's interest in this community lie.
00:12:57.440 --> 00:13:00.240
That I'm just putting it out there in terms of you know, in terms of that.
00:13:00.320 --> 00:13:01.600
But no, very well done to them.
00:13:01.679 --> 00:13:15.279
So we uh and then as well, uh I yes I was on stage because the Manchester Evening edition of the Dynamics 365 uh and power platform UK user group, and I think I probably got that order wrong.
00:13:15.440 --> 00:13:15.919
We won an award.
00:13:16.240 --> 00:13:17.279
Yeah, it's it's it's great.
00:13:17.360 --> 00:13:19.600
You don't know what you won the prize for, what do you do?
00:13:20.080 --> 00:13:25.519
Yeah, I've been in a user group, I've been in a user group that I've not even that I've not even actually attended in person all year.
00:13:25.679 --> 00:13:27.200
Yeah, yeah, I just claimed the award at the end.
00:13:27.279 --> 00:13:29.039
I'm just like, yeah, yeah, it's my user group.
00:13:29.120 --> 00:13:30.159
I I won this award.
00:13:30.320 --> 00:13:36.639
Um, so I need to do give a huge thank you to all of the people who are on the committee who run the event who are actually there on the ground doing it.
00:13:36.720 --> 00:13:47.519
So that includes Adrian, Danielle, uh Damien, and Tom, particularly to Adrian as well, because I understand that he did do quite a good whip round of votes during our event last week when we were there.
00:13:47.600 --> 00:13:54.720
And yeah, he also has been a huge asset in terms of giving us uh a really lovely venue uh right in the centre of Manchester to manage all of this.
00:13:54.799 --> 00:13:56.080
So it is a team effort.
00:13:56.159 --> 00:14:05.360
We will I'll be making sure the award gets to uh the team uh at some point, probably when I'm next in Manchester or when I can next attend my user group, which again is looking unlikely.
00:14:05.679 --> 00:14:13.200
Um but it's a it's a big accolade not only for the uh uh Manchester edition user group but the entire user group as well because we've got these events running all across the UK.
00:14:13.279 --> 00:14:15.279
So I'll I'll put the uh links in the chat.
00:14:15.440 --> 00:14:24.879
We would love to see you at a future meeting, or indeed if you want to get involved as a speaker next year, um then Bell means please reach out to me, contact me.
00:14:24.960 --> 00:14:32.799
We're already starting to get the uh the programme put together for next year, and we'd love to have um you know new speakers come and present to our community in Manchester.
00:14:33.120 --> 00:14:37.120
So you've not been there all year for the event.
00:14:38.639 --> 00:14:40.399
You still won the prize.
00:14:40.799 --> 00:14:44.000
And I've still won't want to claim it, and I'm putting it all over social media.
00:14:44.080 --> 00:14:45.759
Yeah, my user group I've won it, yeah.
00:14:45.840 --> 00:14:49.120
So do you think do you think I'm a bit of a do you think I'm a bit of a narcissistic arsehole?
00:14:49.279 --> 00:14:49.679
Do you think?
00:14:49.759 --> 00:14:52.240
Or that's by that's by side.
00:14:52.399 --> 00:14:54.159
That's that's not even what I want to question.
00:14:54.320 --> 00:14:56.639
What I want to question is like that's obvious.
00:14:56.799 --> 00:14:57.759
That is obvious, okay.
00:14:57.840 --> 00:14:58.000
Right.
00:14:58.960 --> 00:14:59.200
That's fine.
00:14:59.279 --> 00:15:00.399
Okay, we've established that.
00:15:00.480 --> 00:15:00.639
Okay.
00:15:11.919 --> 00:15:18.720
Which is in Manchester, which is my my my second favorite football club in the world.
00:15:18.879 --> 00:15:21.679
Um, and I've never been invited to you.
00:15:23.039 --> 00:15:27.279
Okay, would you that's let's take this offline.
00:15:27.440 --> 00:15:28.399
Let's take this offline.
00:15:28.480 --> 00:15:30.480
Um let's circle back on that.
00:15:30.720 --> 00:15:32.559
Let's circle back on that later on.
00:15:32.639 --> 00:15:34.080
Uh, we'd love to have you, Sebastian.
00:15:34.159 --> 00:15:35.840
We'd love absolutely love to have you.
00:15:36.240 --> 00:15:39.519
Okay, let's let's see how it is sounds offline.
00:15:40.159 --> 00:15:41.120
This is still true.
00:15:41.919 --> 00:15:47.279
And I still need to and I still need to work on getting tickets for buying Munich and United when it's there at all Trafford.
00:15:47.440 --> 00:15:48.720
So that is still my to-do list.
00:15:49.039 --> 00:15:49.759
Yeah, yeah.
00:15:50.000 --> 00:15:54.480
All right, but what is also an order to-do list to learn more about security these days.
00:15:54.799 --> 00:16:05.279
So I heard there is a pretty nice new feature where the people have been secretly waiting for years basically to have those in Dataverse, and now it's finally here.
00:16:05.600 --> 00:16:07.360
Yeah, I saw this on LinkedIn yesterday.
00:16:07.440 --> 00:16:09.759
So kind of uh hit me by kind of surprise.
00:16:09.840 --> 00:16:16.720
I wasn't too involved in, I think, some of the stuff leading up to it, but now we've got something known as filter-based security.
00:16:16.879 --> 00:16:31.200
So, what's interesting about this is that okay, for a long time in Dataverse, the great thing about it is we've got role-based access control, we can control access to records at all different levels of the business unit, of the environment, whatever it may be, including as well things like column level security.
00:16:31.440 --> 00:16:42.240
Now we can grant access to data based on specific filter criteria that we sort of apply on that, uh, with support there for being able to do filters using things like fetch XML.
00:16:42.320 --> 00:16:44.639
So I can then say, okay, here are some records.
00:16:44.720 --> 00:16:50.080
Maybe that's okay, for example, all of my high priority cases where case priority equals one.
00:16:50.480 --> 00:16:54.720
That can then be something that I then can uh give out from an access point of view.
00:16:54.960 --> 00:17:01.120
From what I understand from the announcement as well, is then something that I can also then assign security roles to as a kind of privilege.
00:17:01.200 --> 00:17:11.039
It creates a privilege behind the scenes, so it means that I can then give some very specific, highly specific access out to certain records, you know, to basically to anyone across the organization.
00:17:11.519 --> 00:17:38.880
Um so this is quite a nice uh thing because yeah, we do sometimes are faced with some quite unusual access requirements, not always, you know, in the in the past we've had to do some crazy things involving things like uh access teams and owner teams and you know, having to create and the thing with um access teams in particular is that it creates uh records for every single kind of share that you do in behind the scenes, so your data storage just kind of bloats up over time, which isn't good.
00:17:39.039 --> 00:17:41.920
Uh so this one here I think is going to be quite sort of nice and quite sort of good.
00:17:42.000 --> 00:17:44.000
So it's currently out in preview.
00:17:44.240 --> 00:17:47.279
Uh there's some configuration that you need to do to get started with it.
00:17:47.359 --> 00:17:52.559
I'll put the notes in the uh in the chat as well as also the announcement from Paul at Microsoft.
00:17:52.640 --> 00:17:56.400
He's the uh I think the um uh the owner of this from a product standpoint.
00:17:56.559 --> 00:17:59.200
But yeah, I think this is quite a nice, nice surprise.
00:17:59.359 --> 00:18:09.759
We don't really get these just we occasionally get these nice little things that kind of seep through the cracks, you know, stuff that isn't the flashy sort of like you know AI sort of stuff, but just some good, solid, yeah, security.
00:18:09.839 --> 00:18:11.519
Yeah, I just want some security stuff.
00:18:11.599 --> 00:18:12.160
Yeah, yeah.
00:18:12.400 --> 00:18:12.799
Just like, yeah.
00:18:15.759 --> 00:18:18.640
Yeah, these days um is interesting.
00:18:18.720 --> 00:18:26.000
That I I have the feeling that right now there is more of this core features landing.
00:18:26.079 --> 00:18:30.480
Same on Canvas apps, there are some updates, there's an update, some order of maps here and there.
00:18:30.640 --> 00:18:38.079
So it is like small quality of life features slowly making it into the product which you wished you had like years ago.
00:18:38.319 --> 00:18:46.720
Same with like this um new new access by security that uh or like filter-based security, which we had a client like many years ago.
00:18:46.880 --> 00:19:04.640
Um, this was like before project operations, um, but they also had like our custom uh project solution in place, and because their security was there strict, um, people couldn't have access to all of the projects, uh just like because if you just have read access, you have read access.
00:19:04.720 --> 00:19:13.039
It's there is no that may um no difference if the record is um owned by person A or person B.
00:19:13.279 --> 00:19:17.039
If person C has read access, the person C has read access.
00:19:17.119 --> 00:19:21.839
So it anyways sees the record, otherwise you play with shares and stuff like that.
00:19:22.000 --> 00:19:42.400
And we have that that we had a full project structure and then shared this to like the project team only, that only they can see that project, and indeed that like bulked up the whole database storage because all of all of these access teams and as all of that um shares that have been created in the background.
00:19:42.720 --> 00:19:52.720
It was the best solution at the time based on the requirement, but I was wishing for a such a feature back in the days, which we don't see today.
00:19:52.960 --> 00:19:55.920
Yeah, I've seen some wild, wild shit.
00:19:56.319 --> 00:20:09.599
Another way to describe it, like literally plugins where people are plugins are firing on either retrieve, retrieve multiple, and in there you're doing all sorts of crazy filtering, removing records and collections, and adding all of that blur sort of overhead into there.
00:20:09.759 --> 00:20:11.200
So, yeah, I think it's good.
00:20:11.279 --> 00:20:24.160
I say it's good to see investments in the core product, in you know, little quality of life sort of things, stuff that isn't flashy, that isn't kind of you know buzzwordy or anything like that, but just good solid features.
00:20:24.240 --> 00:20:26.960
This you know, this is I could eat this all day, basically.
00:20:27.119 --> 00:20:36.559
Yeah, so talking about flashy announcements, I also have some to um I have some of them basically because in all tradition you're gonna ruin it now, then basically.
00:20:36.960 --> 00:20:38.880
Yes, I wouldn't ruin it for everyone.
00:20:39.039 --> 00:20:43.759
So if you're listening, listening, this is now roughly at the 20-minute mark.
00:20:43.839 --> 00:20:45.039
You can just leave it.
00:20:46.400 --> 00:20:48.559
Skip at the end, skip, skip to the end.
00:20:48.640 --> 00:20:50.160
Uh see you in two weeks.
00:20:50.319 --> 00:20:52.559
Um, have a good day, bye-bye.
00:20:52.799 --> 00:20:57.359
Um, but so up to flashy announcements, all of the AI and copilot stuff.
00:20:57.440 --> 00:21:08.559
So basically, um, in old tradition, Microsoft decided to announce new stuff right on the day when we recorded the past episode.
00:21:08.640 --> 00:21:10.640
So you may have seen it already.
00:21:10.880 --> 00:21:17.119
So Microsoft is announcing new copilot with home, code and autopilot.
00:21:17.279 --> 00:21:18.880
Um, what does this mean?
00:21:19.039 --> 00:21:24.480
Basically, home um combines co-work and the chat feature.
00:21:24.640 --> 00:21:42.640
Um, code brings in some more GitHub co-pilot-based capabilities so you can directly in copilot um create new solutions or or work in GitHub repos or on local files with code features.
00:21:42.799 --> 00:21:59.759
And autopilot is potentially the one which is a bit more interesting for me personally, as this is um whatever was previously called Scout, which is like something your digital um assistant or teammate, which is funny enough because.
00:22:00.160 --> 00:22:05.680
I think around the same time, Meta um has released their personal assistant.
00:22:06.319 --> 00:22:13.279
There is a um OpenAI, I think, around dot, which is also going into this direction.
00:22:13.440 --> 00:22:25.039
So all of like these um big flashy players going into that personal assistant um or personal teammate direction, which is um definitely interesting to see at the same time.
00:22:25.359 --> 00:22:28.640
So why would I use this code thing rather than GitHub Copilot?
00:22:28.720 --> 00:22:30.160
What's the advantage, would you say?
00:22:30.480 --> 00:22:33.839
I don't think that there is a in particular advantage.
00:22:34.079 --> 00:22:49.759
Um, I do think it's um what Microsoft wants to build, it's just like you need to have one app, you want to have like one interface you can work with, and you can seamlessly going from summarizing your latest email to um to a card-based project.
00:22:49.920 --> 00:22:59.519
Um I I would expect that it is a little bit less functionality or integration around GitHub Copilot.
00:22:59.680 --> 00:23:04.400
So I think for core developers, they still want to use GitHub Copilot, but we need to try it.
00:23:04.559 --> 00:23:09.440
Um the biggest benefit, I think, is the um integrated Microsoft IQ.
00:23:09.839 --> 00:23:25.839
So there is a lot of IQ lately from Microsoft, including SL work IQ and um all of the fabric IQ, which you know be have been an expert since you have been to Barcelona and the Fabric on there.
00:23:26.000 --> 00:24:01.039
Um, but all of that business context um makes maybe the creation of the application or the the code that needs to be written inside the the code panel um better in the first version, and you don't need to um explain so much around your rules internally, or if you um have a certain requirement, you can directly attach it seamlessly without like downloading it or referencing it in GitHub Copilot.
00:24:01.119 --> 00:24:05.599
So if you have your code style guide stored in SharePoint somewhere can access it there.
00:24:05.920 --> 00:24:10.160
Yes, that's yeah, that's definitely something to to explore.
00:24:10.240 --> 00:24:12.000
Like where does it get the data from?
00:24:12.079 --> 00:24:14.880
Is it I think it's still somewhat connected to GitHub.
00:24:15.039 --> 00:24:25.920
Um, so I hope I hope as well this goes um seamlessly with within the license, so it just uses the same license, very similar to the GitHub Copilot app, maybe.
00:24:26.079 --> 00:24:45.680
Um that you can just see that kind of app inside Copilot, and then everything is basically managed by the GitHub organization, which would be ideal, so you don't need to have something stored in SharePoint lists or something to make sure your code works as you expect.
00:24:45.839 --> 00:24:50.720
So, yeah, um from that perspective, pretty interesting.
00:24:50.960 --> 00:24:59.279
Also, um, which is maybe not so obvious, um, the whole product basically got a small rebranding.
00:24:59.440 --> 00:25:02.720
Microsoft is no longer talking about M365 copilots.
00:25:03.039 --> 00:25:04.480
Microsoft rebranding things, really?
00:25:04.640 --> 00:25:07.279
Yeah, they're just renaming so that's such a shock, yeah.
00:25:07.359 --> 00:25:07.920
Yeah, yeah.
00:25:08.319 --> 00:25:12.400
So Excel is like Excel since 1997 or something, so definitely a shock.
00:25:12.480 --> 00:25:14.319
Windows is that's brand power.
00:25:14.400 --> 00:25:17.440
If you can stick around for that long, then you know your brand is strong here.
00:25:17.680 --> 00:25:24.480
Yeah, but in in terms of co-pilot, it's no longer M365 co-pilot now, it's just copilot.
00:25:24.880 --> 00:25:34.960
So I think um the idea is really to create one co-pilot platform which then brings in all of the different co-pilot capabilities um in one space, right?
00:25:35.039 --> 00:25:40.000
Yeah, because we got co we got copilot and the traditional copilot, uh emphasis by copilot, that's what I always call it.
00:25:40.079 --> 00:25:46.480
You've got copilot in dynamics, you've got copilot in Azure, you've got copilot in um power platform, you know.
00:25:46.640 --> 00:25:49.359
So it's um it's a lot.
00:25:50.079 --> 00:25:54.559
We are basically one step before we have copilot on our toaster or fridge.
00:25:54.720 --> 00:26:16.079
So um in this case, um, we just have one copilot app which then just serves everything or should serve everything in the future, which I like as an approach because then you just have like one thing to maintain and um you have the same underlying SDK perhaps, which comes to the next fancy announcement, which is managed runtime.
00:26:16.319 --> 00:26:24.160
So managed runtime or Microsoft Copilot Managed Runtime is uh going into public preview.
00:26:24.240 --> 00:26:34.880
I think when you listen to that, it is already in public preview, but it's basically the platform to run code within the Microsoft 365 tenant.
00:26:35.119 --> 00:27:19.519
So you get all of the great governance features of the uh of your Microsoft tenant, including Intra and the Microsoft Admin Center, and also all of the um connectors from the Power Platform, you get um the um different DLP uh DLP policies, you get um the graph integration, you get work IQ, everything in there, and then basically um you can just bring your app, you can develop it with the new app scale in coverg, or you can have your custom-built app, or you can, for example, as well directly integrate this with um third-party tools such as Lovable.
00:27:19.680 --> 00:27:31.279
I think Lovable in this case is the premium um example, as they have a direct connector to Microsoft Managed Runtime.
00:27:31.680 --> 00:27:46.079
Um, so you can create your app in Lovable and then directly with like one click to deploy it into Microsoft ecosystem, um, which comes with um the business and enterprise license.
00:27:46.240 --> 00:27:50.960
So if you just have the Pro license or free plan, it is not included there.
00:27:51.119 --> 00:27:56.720
But as soon as you do have the business or enterprise license, it is included in there.
00:27:56.960 --> 00:28:12.240
So pretty interesting because then the idea is that the um Microsoft platform works as a platform and it works as a centralized um governance tool that you can with agent 365.
00:28:12.480 --> 00:28:14.960
I mean, you have been talking about this with AJ.
00:28:15.359 --> 00:28:43.200
Um you can like organize and and govern your um apps and agents and all of that stuff, and um handle all of your standards and rules and have everything in one place, but the user just have their own experience, um, whatever they would like to work with across teams or within smaller teams, um, which is then making their lives easier, and you don't need to rely on the UI of a model driven app anymore.
00:28:43.759 --> 00:28:45.279
Happy users, happy life.
00:28:45.440 --> 00:28:47.759
So yes, absolutely.
00:28:48.000 --> 00:28:50.720
Um, I have one more fancy one.
00:28:50.960 --> 00:28:51.279
Wow.
00:28:51.759 --> 00:28:53.599
Very quick, very quick, very demo.
00:28:54.000 --> 00:28:55.119
Um, work IQ.
00:28:55.200 --> 00:28:59.039
I already mentioned work IQ now like 15 times in the last 10 minutes.
00:28:59.279 --> 00:29:06.960
Um so far, work IQ was working across the Microsoft 365 apps, so all of your print work IQ works, yeah.
00:29:07.039 --> 00:29:07.519
It works, yeah.
00:29:07.920 --> 00:29:09.359
It works, yes, it works for you.
00:29:09.519 --> 00:29:16.319
Yeah, so work IQ basically is a layer on top of graph so far.
00:29:16.640 --> 00:29:21.759
Because if you if we look at graph, have you ever worked with the graph API?
00:29:22.720 --> 00:29:29.200
I have the graph is there's lots of really nice, lovely endpoints there for all sorts of information about it.
00:29:29.359 --> 00:29:37.680
Yes, it it has like all of this Teams information, SharePoint, Outlook, calendar information, everything you need.
00:29:38.240 --> 00:29:39.440
Everything about you.
00:29:40.160 --> 00:29:40.799
Exactly.
00:29:40.960 --> 00:29:46.480
Um, it knows everything that I have done at work, which is a bit terrifying, but also very helpful.
00:29:46.720 --> 00:29:53.440
Um but working with this API is maybe not ideal for a large language model.
00:29:53.839 --> 00:29:56.480
So what Microsoft built is work IQ.
00:29:56.640 --> 00:30:08.400
It's just an intelligence layer between that, um, between Graph and any custom agent, copilot, copilot studio, github copilot, whatever there is.
00:30:08.720 --> 00:30:14.000
And so far, as mentioned, this was focused on the my M365 suite.
00:30:14.720 --> 00:30:27.039
Now with the new public preview, which has been started on the 30th of September, you also get um Dynamics 365 and Power Platform apps into that work IQ context.
00:30:27.279 --> 00:30:36.559
So your Dynamics 365 sales or your Dynamics 365 perturbations data is available in work IQ if you want to.
00:30:36.640 --> 00:30:46.960
It's an opt-in feature, but you can directly then set this in connection, and also the work IQ MCP is able to update this data directly in the system.
00:30:47.119 --> 00:30:53.839
So it works with um first-party apps, it works with um finance, it works as well with Dataverse.
00:30:53.920 --> 00:31:19.200
So you can just bring um all of your custom tables into it, and you can just access this very seamlessly from from Copolitic and Cowork, for example, um, build in in custom agents, and um set the meeting you do have, or the Teams chat information you do have directly in association with that opportunity project task or whatever there is.
00:31:19.440 --> 00:31:25.039
So that opens up many, many different new um features and approaches.
00:31:25.279 --> 00:31:40.799
Also, I would say kills a lot of custom agents you may have built of the past weeks and months, because this is exactly what a lot of custom agents are doing, bringing in different data sources and then writing this to potentially your CRM system.
00:31:41.119 --> 00:31:49.440
And if you're like all on the Microsoft platform, you may have something like that created for your own uh purposes, but maybe that kills it off.
00:31:49.839 --> 00:31:52.720
Um something to I was talking, we were talking about this.
00:31:52.960 --> 00:31:53.440
Was it with you?
00:31:53.519 --> 00:31:55.119
I might have been with Emma Claire Shaw.
00:31:55.200 --> 00:31:58.079
So I think it's it's great to see these work IQ investments.
00:31:58.160 --> 00:32:12.319
I guess the challenge is that yeah, from a configuration standpoint, I'm guessing you need to be highly privileged on the in tenant level to be able to go and set up the connection between work IQ and between sort of Dataverse to do that.
00:32:12.559 --> 00:32:12.880
Yeah, yeah.
00:32:12.960 --> 00:32:25.519
So the initial the initial setup, um, I think there is still um global tenant involved and also need to be administrator on the um Dataverse environment um to opt in for that, yeah.
00:32:25.839 --> 00:32:44.480
Yeah, because often the challenge that we find with our enterprise customers is okay, we we we we we find ourselves often very lucky that okay, yeah, they've got power platform administrator, that means we can get most of the things done, but then trying to do anything affecting the M365 environments or even indeed at a global level, it just involves different teams and slows things down.
00:32:44.640 --> 00:33:03.839
So I think the concept's great, they just need to make it a bit easier to kind of uh set up the initial kind of configuration without these highly privileged roles, because otherwise I think people are just gonna fall back to using connectors, MCPs, you know, stuff that is possible for you to do, provided that you've got access at the database level rather than you know at the tenant level.
00:33:04.160 --> 00:33:20.799
Yeah, um, that's also what what I have seen because I had just struggles as well doing some previews that there is certain because it ever it now happens everything in M365, um, you very easily need a tenant or global admin, basically.
00:33:20.960 --> 00:33:24.559
Um, there is a new role which is the II administrator.
00:33:24.720 --> 00:33:40.960
Um, potentially it makes sense to as well introduce here maybe um something in between the II administrator and the um global admin, or to have maybe something um sort of sorted out privileges for these new features in particular.
00:33:41.200 --> 00:33:44.160
Um, I trust Microsoft that they're working on it.
00:33:44.319 --> 00:33:51.039
Um, if not they will hear this feedback as well um at the Power Platform Community Conference in Las Vegas.
00:33:51.119 --> 00:33:52.240
So I will then direct you too.
00:33:56.960 --> 00:33:59.359
I'm gonna rage about this, you know, literally.
00:33:59.599 --> 00:34:02.400
And I was like, Yeah, thank you for feedback, that's very helpful.
00:34:03.680 --> 00:34:04.960
Okay, thanks.
00:34:05.599 --> 00:34:07.519
Let's have an in-and-out burger, man.
00:34:08.480 --> 00:34:16.159
No, no, no, you know, you you have in and out burger with them first, so you so you invite them under false, tasty pretenses.
00:34:16.400 --> 00:34:25.280
They think they're going for a double-double chocolate shake and a fries, but in the end, they walk away feeling, oh, I've just been I've been like catfished.
00:34:25.760 --> 00:34:26.159
Molested.
00:34:26.559 --> 00:34:27.440
I've been catfished.
00:34:27.679 --> 00:34:29.679
This was supposed to be an ice in an outdate.
00:34:29.760 --> 00:34:36.719
Instead, I've now got 10 additional items for my backlog, uh, and a very unhappy German who has expressed his opinions towards me.
00:34:37.360 --> 00:34:38.400
Maybe that happens.
00:34:38.480 --> 00:34:39.519
Um, I hope not.
00:34:39.679 --> 00:34:44.400
But yeah, I I try to be very neutral with my feedback and try to help, of course.
00:34:44.880 --> 00:34:49.679
You you are you are you are you are very polite and you are also very well known.
00:34:49.840 --> 00:34:56.239
Um, yeah, so just pro tip for people listening, you know, Seb is the guy, he can he can connect you.
00:34:56.320 --> 00:35:00.320
He's he's he's a he's just bringing bringing bringing people together.
00:35:00.480 --> 00:35:05.440
He's very, very good, he's very, very charming and very, very well connected individual.
00:35:05.760 --> 00:35:09.840
What do you want from me that you're saying so nice things about me?
00:35:10.400 --> 00:35:12.719
You'll find out, you'll find out in due course.
00:35:13.039 --> 00:35:14.960
I am very concerned.
00:35:15.199 --> 00:35:23.119
Um what you also should be concerned about if you're attending the Power Platform Community Conference in two weeks.
00:35:23.360 --> 00:35:24.320
It is literally two weeks.
00:35:24.480 --> 00:35:24.880
It's three weeks.
00:35:25.119 --> 00:35:26.480
It's three weeks, yeah.
00:35:26.719 --> 00:35:28.079
Yeah, you know, it's two weeks now.
00:35:28.159 --> 00:35:34.800
So when this when this episode releases, it's two weeks, literally, because then um next week, next week AI tour.
00:35:34.880 --> 00:35:45.360
So okay, when this comes out this week, AI tour in Singapore, the week after AI tour in Cologne, or or local German or European listeners, I will be there as well.
00:35:45.599 --> 00:35:49.519
Um nice, nice, cool.
00:35:49.760 --> 00:35:55.760
Um, and then the week after that is um power platform community conference.
00:35:56.000 --> 00:36:01.679
And what you should be concerned about is we're doing, I think it's a live podcast recording there.
00:36:02.000 --> 00:36:14.000
So I think you can join, uh, put on some headphones and listen to this live in the making, just to make sure that there are no cuts, there is no script, there is just us wiping.
00:36:14.159 --> 00:36:17.440
And um, I don't know exactly where it will be.
00:36:17.599 --> 00:36:22.400
I've not checked that yet, but it will be on Wednesday, on the Wednesday, I think, early afternoon.
00:36:22.480 --> 00:36:25.760
I think something like see us live recording.
00:36:25.840 --> 00:36:27.599
I mean, like, live recording, yes.
00:36:27.679 --> 00:36:29.519
So it will be a very special episode.
00:36:29.760 --> 00:36:35.360
So huge thank you and shout out to um Vendana at Microsoft for reaching out to us there and uh getting that organized.
00:36:35.519 --> 00:36:36.800
That's really, really nice.
00:36:37.039 --> 00:36:38.239
Yes, absolutely.
00:36:38.400 --> 00:36:38.960
I agree.
00:36:39.119 --> 00:36:40.719
So, yeah, that was so nice.
00:36:40.960 --> 00:36:46.559
Um, therefore, I think for all of these news, updates, stuff like that.
00:36:46.800 --> 00:36:50.159
Um we've covered your actually, it's been meaty.
00:36:50.559 --> 00:36:52.880
There's lots of good content.
00:36:53.199 --> 00:36:56.000
This this is starting to become almost like a semi-professional thing.
00:36:56.079 --> 00:36:59.920
It's as if it's as if M365 distilled won the award, you know.
00:37:00.000 --> 00:37:07.119
We were so despondent at that, and then now we're we're kind of like trying to right, let's let's just get this podcast better, you know.
00:37:07.199 --> 00:37:09.039
We're just gonna put it for the content, you know.
00:37:09.119 --> 00:37:11.199
It's it's acts as like a catalyst for growth.
00:37:11.280 --> 00:37:11.679
I like it.
00:37:11.840 --> 00:37:19.119
So, do you think that the um nomination has done something positive?
00:37:19.599 --> 00:37:21.679
I well, uh well, maybe let's see.
00:37:21.760 --> 00:37:31.360
The the time time will tell, but I'm sure that yeah, we we we now have I mean, having that albatross around our neck in terms of having an award would have been quite scary.
00:37:31.440 --> 00:37:40.239
But now that we can sort of say that we're finalists, we're we're we're a uh UK Community Award finalist podcast, it's just rolls off the tone, doesn't it?
00:37:40.320 --> 00:37:41.119
Yeah, yeah, yeah.
00:37:41.360 --> 00:37:43.599
I I it it totally sticks with me.
00:37:43.760 --> 00:37:50.639
I I think I will put this as a banner right here next to this light here, just really let it shine.
00:37:50.960 --> 00:37:57.519
Yeah, it's clearly the one accolade that you need to just basically tell everyone about and never let them forget it because it's just so important.
00:37:57.760 --> 00:37:59.119
Absolutely, absolutely.
00:37:59.280 --> 00:38:06.239
Right, before we close, um, one very last shootout to Emma and Crack, which do you have on your um podcast?
00:38:06.400 --> 00:38:08.400
The Power Platform Panic Room.
00:38:08.639 --> 00:38:14.400
I think um Power Platform Panic Room.
00:38:14.800 --> 00:38:15.360
Penigroom.
00:38:15.440 --> 00:38:16.320
I thought we said Pentagon.
00:38:16.480 --> 00:38:21.199
Panic Room Penic Room Panic Room Panic Room, okay.
00:38:21.280 --> 00:38:21.760
Panic room.
00:38:21.840 --> 00:38:28.400
I thought you said they were doing some I thought they were doing some like satanic ritual or something, maybe.
00:38:28.880 --> 00:38:29.599
That would be also cool.
00:38:29.679 --> 00:38:32.000
Maybe maybe to just to make that average work at some point.
00:38:32.079 --> 00:38:33.119
Sub summoning demons.
00:38:33.199 --> 00:38:34.079
Yeah, that'd be quite cool.
00:38:34.159 --> 00:38:36.239
Anyway, but yeah, please tell us more about this podcast.
00:38:36.559 --> 00:38:42.239
Yes, so uh Emma Claire Shaw and Craig White are doing this um podcast together.
00:38:42.400 --> 00:38:43.840
It has a few episodes on now.
00:38:44.079 --> 00:38:50.320
I I just was not aware until their session on um uh the CEO star kit, rest in peace.
00:38:50.559 --> 00:38:56.800
And um therefore, um uh it was very pleasant to to listen on to a few episodes so far.
00:38:57.119 --> 00:39:05.199
So yeah, if you if you're searching for more um professional podcasts, yeah, for a better more professional podcast, yeah, yeah.
00:39:07.440 --> 00:39:07.920
There you go.
00:39:08.079 --> 00:39:12.000
Yeah, just this one that's literally just turned up and it's just doing things correct for the day one.
00:39:12.079 --> 00:39:14.000
Just yeah, they they're they're very funny.
00:39:14.079 --> 00:39:17.199
So very very nice lats, if you want to say that like this.
00:39:17.360 --> 00:39:19.920
So um, yeah, definitely give it a shout.
00:39:20.159 --> 00:39:24.000
Um I think it's more professional than yeah, it's more professional.
00:39:24.960 --> 00:39:25.679
It definitely is.
00:39:25.760 --> 00:39:28.320
I can tell you right now it is more professional than this.
00:39:28.880 --> 00:39:30.079
Oh, listening to you a second, yes.
00:39:30.239 --> 00:39:35.840
If I listen to a single second, I can tell you right now, I would probably I'd bet my life savings on it.
00:39:36.960 --> 00:39:44.320
Awesome, with that on that bomb shell right away.
00:39:44.480 --> 00:39:45.360
We don't care.
00:39:45.599 --> 00:39:49.440
Uh please stick with us.
00:39:51.519 --> 00:39:54.320
This is this this is the only thing that's keeping him going, Sebastian.
00:39:54.400 --> 00:39:55.599
So yeah, don't don't disappoint him.
00:39:56.000 --> 00:39:56.800
Do you set his face now?
00:39:57.199 --> 00:39:58.480
Do you set his face now on camera?
00:39:58.559 --> 00:40:00.480
So people this is this is the this will be a good wheel.
00:40:00.639 --> 00:40:05.920
So Sebastian, just look into the camera and just be like, sad eyes, please listen to my podcast, please.
00:40:06.079 --> 00:40:09.920
Oh can you can you please listen to my podcast, please?
00:40:11.760 --> 00:40:12.400
I'm not good at us.
00:40:12.639 --> 00:40:14.000
Sorry, all right, all right.
00:40:14.159 --> 00:40:15.199
See you in two weeks.
00:40:15.440 --> 00:40:19.440
See you in Singapore, Cologne, or Las Vegas.
00:40:19.599 --> 00:40:21.599
We'll be very happy to see you in person.
00:40:21.840 --> 00:40:22.400
Bye bye.
00:40:22.719 --> 00:40:24.719
See you, Joe, in Cologne, which is weird.
00:40:24.960 --> 00:40:25.519
See you, okay.
00:40:25.840 --> 00:40:26.079
Hello.
00:40:27.119 --> 00:40:27.679
Whatever.
00:40:27.840 --> 00:40:29.039
Bye bye, take care.
00:00:00.239 --> 00:00:02.799
Yo, I tell you what I wanna wanna really really want.
00:00:02.879 --> 00:00:04.799
Just tell me what you want what you really really want.
00:00:04.879 --> 00:00:06.799
I tell you what I wanna wanna really really wanna.
00:00:06.959 --> 00:00:24.879
Just tell me what you want I wanna really really wanna wanna I wanna I wanna I wanna I wanna really really really wanna zig a zig morning.
00:00:25.120 --> 00:00:26.960
I don't know, I just had that song in my head this morning.
00:00:27.039 --> 00:00:27.519
I don't know why.
00:00:28.079 --> 00:00:30.879
Um you should see a doctor, maybe.
00:00:31.120 --> 00:00:32.000
I don't know.
00:00:32.240 --> 00:00:36.479
I I unfortunately I had a young sister growing up who listened to that stuff all the time.
00:00:36.640 --> 00:00:41.119
So actually, most of the Spice Girl songs are permanently ingrained in my memory.
00:00:41.200 --> 00:00:44.079
So you know that's my party trick, should we say?
00:00:45.039 --> 00:00:46.000
I see, I see.
00:00:46.159 --> 00:00:53.359
What a great, great party trick to start off a new episode of the Unresolved Dependencies Podcast.
00:00:53.520 --> 00:00:54.960
Episode 16.
00:00:55.520 --> 00:01:00.719
That's 13 more episodes than I thought we were gonna do, but we are keeping going.
00:01:01.359 --> 00:01:04.000
We're in a good rhythm, like we're able to do stuff.
00:01:04.079 --> 00:01:07.280
We we've all we've kind of got our roles and responsibilities.
00:01:07.359 --> 00:01:10.159
Um, everyone we both kind of know what we're doing.
00:01:10.319 --> 00:01:13.120
You don't have to like um chase me as often anymore.
00:01:13.200 --> 00:01:15.120
I just kind of get my shit together.
00:01:15.200 --> 00:01:18.959
So yeah, I think we're finally we've got a good groove going on, it feels like.
00:01:19.439 --> 00:01:24.400
All you want to say is that you're coming in prepared now, and you also have topics, right?
00:01:24.640 --> 00:01:25.200
I too.
00:01:25.359 --> 00:01:26.319
I do have topics today.
00:01:27.200 --> 00:01:29.519
I actually literally wrote them down and sent them to you as well.
00:01:29.599 --> 00:01:31.439
So I mean that's my amp.
00:01:31.840 --> 00:01:32.959
That's the crazy part.
00:01:33.840 --> 00:01:35.120
That is the crazy part.
00:01:35.200 --> 00:01:39.519
Um, but you know what's crazy is what's what the craziest thing in the world is Joe's travels.
00:01:40.079 --> 00:01:47.280
So the mileage consumption is very close to my AI token consumption, but let's not talk about that.
00:01:47.519 --> 00:01:49.280
Talk about your travels.
00:01:49.760 --> 00:01:51.599
Yes, where have you been?
00:01:51.680 --> 00:01:52.239
Where are you?
00:01:52.319 --> 00:01:53.599
Where are you next?
00:01:53.840 --> 00:01:55.760
So let me give you the answer from the previous clue.
00:01:55.840 --> 00:01:59.200
So, again, the inbox was absolutely smashed full of responses.
00:01:59.359 --> 00:02:01.439
Uh, clearly the most popular feature in the world.
00:02:01.519 --> 00:02:03.439
So, so much love for this feature.
00:02:03.599 --> 00:02:07.200
Um, so the answer for the clue for last time was Barcelona.
00:02:07.359 --> 00:02:11.919
I was in Barcelona for the European fabric and sequel con.
00:02:12.319 --> 00:02:16.400
I had a very nice time there as well, even though it was a condensed a little bit too short.
00:02:16.560 --> 00:02:22.639
So, yes, Barcelona, lovely city, great food, great tapas, great sangria, definitely would recommend you sort of go in there.
00:02:22.719 --> 00:02:25.039
So the sangria made you go.
00:02:25.120 --> 00:02:25.840
Yeah, okay.
00:02:26.080 --> 00:02:27.199
No, no, it was learning.
00:02:27.280 --> 00:02:28.319
I want to learn about fabric.
00:02:28.560 --> 00:02:29.120
Fabric.
00:02:29.199 --> 00:02:34.400
What's and I'm and I may have been converted, I may have been converted over to the fabric side.
00:02:34.479 --> 00:02:35.840
Um, let's just see.
00:02:36.000 --> 00:02:39.599
Um, but anyway, let's not get into that whole uh rabbit hole there.
00:02:39.680 --> 00:02:41.199
So uh so that was the answer last time.
00:02:41.280 --> 00:02:52.159
So if you did want to play along and you want to and you want to sort of get involved, you can drop us an email, hello at unresolved dependencies.com, or alternatively just drop us an answer on the socials when you see those funny reels come up.
00:02:52.240 --> 00:02:53.199
We'd be happy to hear from you.
00:02:53.280 --> 00:02:56.080
So, my next clue where is Joe traveling next?
00:02:56.240 --> 00:03:10.639
I am travelling to the first capital city in the northern American United States that that fell to Union forces during the American Civil War, and which is famous for its riveting music scene.
00:03:10.960 --> 00:03:12.879
Where am I going to next?
00:03:13.039 --> 00:03:13.840
Let us know in the email.
00:03:14.960 --> 00:03:18.000
Music scene, that's maybe a big hint, Darryl.
00:03:18.159 --> 00:03:23.439
Because of, I mean, of course, all of our listeners would have gasted with like um the first hint.
00:03:23.520 --> 00:03:36.560
Um, that is very much obvious if you're our core our core listeners are just a bunch of uh history nerds, you know, living in their basements, or that's obsessed with these obscure military facts, uh, particularly relating to the uh the American Civil War.
00:03:36.639 --> 00:03:39.120
So, yeah, clearly I'm also giving it away too easily with that one.
00:03:39.199 --> 00:03:43.280
But if not, then I'll give you a nice easy clue to sort of give you uh to help you along there.
00:03:44.560 --> 00:03:45.599
Nice, nice.
00:03:45.840 --> 00:03:47.680
Yeah, so a lot of travel again.
00:03:47.759 --> 00:03:49.280
Um, I'm also traveling.
00:03:49.439 --> 00:03:54.319
Um you're going to quite an interesting place, aren't you?
00:03:54.800 --> 00:03:57.919
I'm going to Singapore actually, um, over the weekend.
00:03:58.080 --> 00:04:10.560
Um actually, I'm going there for the Microsoft AI tour that happens um basically on the day you are listening to this podcast.
00:04:10.800 --> 00:04:13.120
Um, so I'm traveling all the weekend to Singapore.
00:04:13.759 --> 00:04:17.360
But this also falls into the same week with my vacation.
00:04:17.439 --> 00:04:32.480
So I'm only going there um doing my session there with uh colleague of us, um, meeting with the fabulous Daniel Laskowitz because he will be there as well, and then going back home because then I want to enjoy some days off.
00:04:33.680 --> 00:04:34.720
That's the plan.
00:04:35.120 --> 00:04:37.120
Or Dan be going to Vegas.
00:04:37.439 --> 00:04:43.279
So then you need to get a photo with Daniel and you need to get him to say something nice about the podcast, and then yeah, that's your mission.
00:04:43.680 --> 00:04:48.480
Let's start with the photo, um, and then let's see what happens from there.
00:04:49.040 --> 00:04:55.120
Um yeah, but basically we we saw Daniel uh a few days ago.
00:04:55.279 --> 00:04:56.480
So at the Scottish Summit.
00:04:57.120 --> 00:05:02.800
Scottish Summit, yeah, where we did have some uh maybe this this could be Sebastian's uh eats for this week.
00:05:02.879 --> 00:05:04.560
We did have some quite nice food there, didn't we?
00:05:04.639 --> 00:05:06.720
Like street-related kind of food.
00:05:06.879 --> 00:05:07.680
I quite liked it.
00:05:08.000 --> 00:05:43.839
Yeah, this was it was quite well, but it was not the the Sebastian's food of the week because um I was not only at Scottish Summit um the last days, I was also at the AI Paloozer in uh Stuttgart, which is a German event, and there we went out um for dinner because we were as well um exhibited there, so we were had a little booth, and I was there with some colleagues, and then we said, Hey, in the evening, let's go out for some nice dinner, because one of them was well happy birthday, and I was like, Come on, let's go.
00:05:44.240 --> 00:05:46.079
Um, got some nice food in.
00:05:46.240 --> 00:05:52.959
She wanted to have an Italian um uh dish, and so we can uh so we went for burgers.
00:05:53.600 --> 00:05:56.959
Just kidding, the Italian place was closed.
00:05:57.439 --> 00:06:00.480
So it was not right.
00:06:00.800 --> 00:06:03.120
So so so ignore what you want, it's your birthday.
00:06:03.279 --> 00:06:06.560
We tried your first choice, so we're going for burgers, and you like it all.
00:06:07.120 --> 00:06:09.120
Oh by by the way, happy birthday.
00:06:10.240 --> 00:06:11.600
Yeah, exactly like that.
00:06:11.759 --> 00:06:12.800
No, no, no.
00:06:13.759 --> 00:06:28.879
No, um actually we went to the Italian place, but it was already quite late because the event, I think it was pretty interesting because the event started like at 10, and then the first session or so was at 12, and um then it all goes on the first day to like 7 p.m.
00:06:28.959 --> 00:06:35.279
or so, and then you go back to the hotel, get refreshed, and then um till you then make it to the restaurant.
00:06:35.360 --> 00:06:40.240
Then the restaurant was like, uh guys, we don't have the kitchen's closed.
00:06:40.480 --> 00:06:54.879
So then we went to a burger place, and I really had a very nice um bowl which uh made with bulgur, tomatoes, um cottage cheese, some bread, chicken on top, salad.
00:06:54.959 --> 00:06:59.439
So it's a pretty nice, a lot of nuts, and on the side some fries.
00:06:59.600 --> 00:07:01.360
And do you know what is the best?
00:07:02.240 --> 00:07:09.759
I took a picture, so you can upload that later on to the to the socials, which I then um if I will share it with you.
00:07:09.839 --> 00:07:15.519
Sorry, but yeah, I I took a picture and then um we can grab that.
00:07:15.759 --> 00:07:20.399
Yeah, so it's kind of like a deconstructed burger almost.
00:07:20.959 --> 00:07:25.040
Yes, yes, but but with less spread actually, um, but it was really nice.
00:07:25.120 --> 00:07:29.680
So it was a it was a huge potion, so it was literally like a bald bowl thing.
00:07:29.920 --> 00:07:35.120
Um but it was it was uh very very nice and good, yeah.
00:07:35.360 --> 00:07:36.399
Very delicious.
00:07:36.639 --> 00:07:38.720
Fantastic, fantastic.
00:07:39.360 --> 00:07:39.839
Thank you.
00:07:40.000 --> 00:07:44.240
So yeah, speaking of Scottish Summit, it was uh yeah, it was I had a lot of fun.
00:07:44.319 --> 00:07:47.839
We were both in Edinburgh, we were sharing an Airbnb together.
00:07:48.000 --> 00:07:51.920
Um you left without saying goodbye, but we won't we won't dwell on that, obviously.
00:07:52.160 --> 00:07:58.480
Um well you were still in bed, I think, so I didn't want to wake you up after the heavy party night we had.
00:07:58.560 --> 00:08:01.439
So um I decided uh it's eight o'clock in the morning.
00:08:01.600 --> 00:08:10.560
I'm struggling a bit to um make my way to the airport, so let's leave, let's let Joe sleep and not make any mess.
00:08:10.639 --> 00:08:17.199
And therefore, just just just just just remember, I may or may not have pictures of you in a pink cowboy hat.
00:08:17.279 --> 00:08:20.000
So you know, just think on, always think on.
00:08:20.240 --> 00:08:23.279
Yeah, it's the the 100 episode special, maybe.
00:08:23.439 --> 00:08:24.720
Um, but I traded this.
00:08:24.879 --> 00:08:28.000
I traded the the pink cowboy heat later, actually.
00:08:28.160 --> 00:08:34.240
Um with a guy on the street to to a cat, which to get home, yeah, yeah.
00:08:34.720 --> 00:08:40.080
Yeah, please, please not like not like a cap, so not an Uber cab, but like a hat.
00:08:40.240 --> 00:08:42.960
So um, so yeah.
00:08:44.480 --> 00:08:45.120
It was fun.
00:08:45.200 --> 00:08:46.240
Yeah, fun night.
00:08:46.320 --> 00:08:50.879
Um, but as as people say, what happens in Edinburgh stays in Edinburgh.
00:08:51.759 --> 00:08:53.840
Yeah, but it was a very interesting event.
00:08:53.919 --> 00:09:00.320
We both had sessions, uh Asian 365 session with AJ, which I think was very well received.
00:09:00.480 --> 00:09:11.120
Um, some of the feedbacks, feedback was quite good, some of it was a bit concerning in terms of you know, very, shall we say, um, amorous comments directed towards me and AJ.
00:09:11.360 --> 00:09:14.159
Um, so I mean, I'll I'll take it where I can get it, obviously.
00:09:14.399 --> 00:09:16.960
But uh, yeah, just uh maybe just calm down a bit in the future.
00:09:17.039 --> 00:09:18.080
So that was a good session.
00:09:18.159 --> 00:09:20.879
Uh and then I gate crashed your session, didn't I?
00:09:21.039 --> 00:09:22.480
Um yes, you did.
00:09:22.559 --> 00:09:24.879
There was even like a comment going in this direction.
00:09:25.039 --> 00:09:28.399
So overall, so we talked about um yeah, yeah.
00:09:28.480 --> 00:09:31.039
Who who is this guy and why is he ruining the session?
00:09:31.360 --> 00:09:31.840
Lovely session.
00:09:32.000 --> 00:09:32.480
Something like this.
00:09:33.519 --> 00:09:35.759
Um I I just don't know.
00:09:35.919 --> 00:09:39.440
Um sorry, that's firstly start with the session itself.
00:09:39.600 --> 00:10:18.000
So the session was on Agent Builder versus Copala Studio, which um at the point when I submitted the session, um and as well when we did it, or when I did it with Andrew Bibby in uh Color Cloud earlier this year, the the line in between was was made uh tougher and it was may more fixed um than it is meanwhile, because meanwhile we as well have skills there, we do have plenty um of of reasons why we should build something on Agent Builder over um using Coparty Studio for certain use cases.
00:10:18.240 --> 00:10:21.840
Back in the days, this was much more limited and much more clear.
00:10:22.000 --> 00:10:40.960
Um, so it was a bit more blurry, but this is this is my most seen issue lately with session submission submissions that at the moment you submit something, you're pretty sure that you need to rework half of the idea literally till the event happens.
00:10:41.120 --> 00:10:54.480
So that's a bit weird, but nevertheless, um, because Andrew was not there at Scotter Summit, I then asked you and you volunteered to jump on me, uh jump jump on me, jump with me on the stage.
00:10:55.600 --> 00:10:56.879
Yeah, jump on me literally.
00:10:56.960 --> 00:11:42.080
But there was so overall the feedback was very, very positive, and people liked the awkwardness, and uh it's a bit more funny and loose, but there was like one concerning comment which was like say, like only twos and threes in terms of the um uh reason like ratings, and that was like, yeah, there were so one of the guys clearly knew what he was talking about, while the other one was constantly like challenging him and um disturbing him, which would look like very unprofessional, and and no professional okay, and so no, we don't we know we have one clearly because because we interrupted ourselves the whole time because this was part of the little like fight between agent building and cowboy studio.
00:11:42.320 --> 00:11:46.240
So I I'm not sure who was who in the story.
00:11:46.480 --> 00:11:50.559
So even you have to sit your i have it, I have a suspicion.
00:11:50.639 --> 00:11:54.000
So if the person is listening to this, then yeah, I I do apologize.
00:11:54.240 --> 00:12:04.639
We were trying to keep the session fairly fairly light, and the whole objective was okay, we're trying to show um each person is trying to basically show that their technology is the better.
00:12:04.720 --> 00:12:09.600
So it was kind of all meant in good sort of um ribbing, should we say?
00:12:09.840 --> 00:12:25.200
Yeah, it was the idea of of the session to to have those little fights on stage, basically, yeah, to challenge the other person as well with with weird questions or um telling how the products or the other technology is better than the other.
00:12:25.519 --> 00:12:26.480
Yeah, but yeah, for sure.
00:12:26.639 --> 00:12:29.440
Overall, Scottish summit cabaret, you won a price.
00:12:29.519 --> 00:12:30.639
The podcast didn't.
00:12:30.879 --> 00:12:40.480
So how how do you feel now after a few days and it has settled down that you are an UK community award winner again?
00:12:40.960 --> 00:12:44.720
Yeah, so I was actually texting Urika about this, actually.
00:12:44.799 --> 00:12:57.279
So, yeah, obviously, very well, very well done to M365 to still for winning that award, but but clearly, you know, um podcasts involving alcohol, you know, it just tells tells the story in terms of where people's interest in this community lie.
00:12:57.440 --> 00:13:00.240
That I'm just putting it out there in terms of you know, in terms of that.
00:13:00.320 --> 00:13:01.600
But no, very well done to them.
00:13:01.679 --> 00:13:15.279
So we uh and then as well, uh I yes I was on stage because the Manchester Evening edition of the Dynamics 365 uh and power platform UK user group, and I think I probably got that order wrong.
00:13:15.440 --> 00:13:15.919
We won an award.
00:13:16.240 --> 00:13:17.279
Yeah, it's it's it's great.
00:13:17.360 --> 00:13:19.600
You don't know what you won the prize for, what do you do?
00:13:20.080 --> 00:13:25.519
Yeah, I've been in a user group, I've been in a user group that I've not even that I've not even actually attended in person all year.
00:13:25.679 --> 00:13:27.200
Yeah, yeah, I just claimed the award at the end.
00:13:27.279 --> 00:13:29.039
I'm just like, yeah, yeah, it's my user group.
00:13:29.120 --> 00:13:30.159
I I won this award.
00:13:30.320 --> 00:13:36.639
Um, so I need to do give a huge thank you to all of the people who are on the committee who run the event who are actually there on the ground doing it.
00:13:36.720 --> 00:13:47.519
So that includes Adrian, Danielle, uh Damien, and Tom, particularly to Adrian as well, because I understand that he did do quite a good whip round of votes during our event last week when we were there.
00:13:47.600 --> 00:13:54.720
And yeah, he also has been a huge asset in terms of giving us uh a really lovely venue uh right in the centre of Manchester to manage all of this.
00:13:54.799 --> 00:13:56.080
So it is a team effort.
00:13:56.159 --> 00:14:05.360
We will I'll be making sure the award gets to uh the team uh at some point, probably when I'm next in Manchester or when I can next attend my user group, which again is looking unlikely.
00:14:05.679 --> 00:14:13.200
Um but it's a it's a big accolade not only for the uh uh Manchester edition user group but the entire user group as well because we've got these events running all across the UK.
00:14:13.279 --> 00:14:15.279
So I'll I'll put the uh links in the chat.
00:14:15.440 --> 00:14:24.879
We would love to see you at a future meeting, or indeed if you want to get involved as a speaker next year, um then Bell means please reach out to me, contact me.
00:14:24.960 --> 00:14:32.799
We're already starting to get the uh the programme put together for next year, and we'd love to have um you know new speakers come and present to our community in Manchester.
00:14:33.120 --> 00:14:37.120
So you've not been there all year for the event.
00:14:38.639 --> 00:14:40.399
You still won the prize.
00:14:40.799 --> 00:14:44.000
And I've still won't want to claim it, and I'm putting it all over social media.
00:14:44.080 --> 00:14:45.759
Yeah, my user group I've won it, yeah.
00:14:45.840 --> 00:14:49.120
So do you think do you think I'm a bit of a do you think I'm a bit of a narcissistic arsehole?
00:14:49.279 --> 00:14:49.679
Do you think?
00:14:49.759 --> 00:14:52.240
Or that's by that's by side.
00:14:52.399 --> 00:14:54.159
That's that's not even what I want to question.
00:14:54.320 --> 00:14:56.639
What I want to question is like that's obvious.
00:14:56.799 --> 00:14:57.759
That is obvious, okay.
00:14:57.840 --> 00:14:58.000
Right.
00:14:58.960 --> 00:14:59.200
That's fine.
00:14:59.279 --> 00:15:00.399
Okay, we've established that.
00:15:00.480 --> 00:15:00.639
Okay.
00:15:11.919 --> 00:15:18.720
Which is in Manchester, which is my my my second favorite football club in the world.
00:15:18.879 --> 00:15:21.679
Um, and I've never been invited to you.
00:15:23.039 --> 00:15:27.279
Okay, would you that's let's take this offline.
00:15:27.440 --> 00:15:28.399
Let's take this offline.
00:15:28.480 --> 00:15:30.480
Um let's circle back on that.
00:15:30.720 --> 00:15:32.559
Let's circle back on that later on.
00:15:32.639 --> 00:15:34.080
Uh, we'd love to have you, Sebastian.
00:15:34.159 --> 00:15:35.840
We'd love absolutely love to have you.
00:15:36.240 --> 00:15:39.519
Okay, let's let's see how it is sounds offline.
00:15:40.159 --> 00:15:41.120
This is still true.
00:15:41.919 --> 00:15:47.279
And I still need to and I still need to work on getting tickets for buying Munich and United when it's there at all Trafford.
00:15:47.440 --> 00:15:48.720
So that is still my to-do list.
00:15:49.039 --> 00:15:49.759
Yeah, yeah.
00:15:50.000 --> 00:15:54.480
All right, but what is also an order to-do list to learn more about security these days.
00:15:54.799 --> 00:16:05.279
So I heard there is a pretty nice new feature where the people have been secretly waiting for years basically to have those in Dataverse, and now it's finally here.
00:16:05.600 --> 00:16:07.360
Yeah, I saw this on LinkedIn yesterday.
00:16:07.440 --> 00:16:09.759
So kind of uh hit me by kind of surprise.
00:16:09.840 --> 00:16:16.720
I wasn't too involved in, I think, some of the stuff leading up to it, but now we've got something known as filter-based security.
00:16:16.879 --> 00:16:31.200
So, what's interesting about this is that okay, for a long time in Dataverse, the great thing about it is we've got role-based access control, we can control access to records at all different levels of the business unit, of the environment, whatever it may be, including as well things like column level security.
00:16:31.440 --> 00:16:42.240
Now we can grant access to data based on specific filter criteria that we sort of apply on that, uh, with support there for being able to do filters using things like fetch XML.
00:16:42.320 --> 00:16:44.639
So I can then say, okay, here are some records.
00:16:44.720 --> 00:16:50.080
Maybe that's okay, for example, all of my high priority cases where case priority equals one.
00:16:50.480 --> 00:16:54.720
That can then be something that I then can uh give out from an access point of view.
00:16:54.960 --> 00:17:01.120
From what I understand from the announcement as well, is then something that I can also then assign security roles to as a kind of privilege.
00:17:01.200 --> 00:17:11.039
It creates a privilege behind the scenes, so it means that I can then give some very specific, highly specific access out to certain records, you know, to basically to anyone across the organization.
00:17:11.519 --> 00:17:38.880
Um so this is quite a nice uh thing because yeah, we do sometimes are faced with some quite unusual access requirements, not always, you know, in the in the past we've had to do some crazy things involving things like uh access teams and owner teams and you know, having to create and the thing with um access teams in particular is that it creates uh records for every single kind of share that you do in behind the scenes, so your data storage just kind of bloats up over time, which isn't good.
00:17:39.039 --> 00:17:41.920
Uh so this one here I think is going to be quite sort of nice and quite sort of good.
00:17:42.000 --> 00:17:44.000
So it's currently out in preview.
00:17:44.240 --> 00:17:47.279
Uh there's some configuration that you need to do to get started with it.
00:17:47.359 --> 00:17:52.559
I'll put the notes in the uh in the chat as well as also the announcement from Paul at Microsoft.
00:17:52.640 --> 00:17:56.400
He's the uh I think the um uh the owner of this from a product standpoint.
00:17:56.559 --> 00:17:59.200
But yeah, I think this is quite a nice, nice surprise.
00:17:59.359 --> 00:18:09.759
We don't really get these just we occasionally get these nice little things that kind of seep through the cracks, you know, stuff that isn't the flashy sort of like you know AI sort of stuff, but just some good, solid, yeah, security.
00:18:09.839 --> 00:18:11.519
Yeah, I just want some security stuff.
00:18:11.599 --> 00:18:12.160
Yeah, yeah.
00:18:12.400 --> 00:18:12.799
Just like, yeah.
00:18:15.759 --> 00:18:18.640
Yeah, these days um is interesting.
00:18:18.720 --> 00:18:26.000
That I I have the feeling that right now there is more of this core features landing.
00:18:26.079 --> 00:18:30.480
Same on Canvas apps, there are some updates, there's an update, some order of maps here and there.
00:18:30.640 --> 00:18:38.079
So it is like small quality of life features slowly making it into the product which you wished you had like years ago.
00:18:38.319 --> 00:18:46.720
Same with like this um new new access by security that uh or like filter-based security, which we had a client like many years ago.
00:18:46.880 --> 00:19:04.640
Um, this was like before project operations, um, but they also had like our custom uh project solution in place, and because their security was there strict, um, people couldn't have access to all of the projects, uh just like because if you just have read access, you have read access.
00:19:04.720 --> 00:19:13.039
It's there is no that may um no difference if the record is um owned by person A or person B.
00:19:13.279 --> 00:19:17.039
If person C has read access, the person C has read access.
00:19:17.119 --> 00:19:21.839
So it anyways sees the record, otherwise you play with shares and stuff like that.
00:19:22.000 --> 00:19:42.400
And we have that that we had a full project structure and then shared this to like the project team only, that only they can see that project, and indeed that like bulked up the whole database storage because all of all of these access teams and as all of that um shares that have been created in the background.
00:19:42.720 --> 00:19:52.720
It was the best solution at the time based on the requirement, but I was wishing for a such a feature back in the days, which we don't see today.
00:19:52.960 --> 00:19:55.920
Yeah, I've seen some wild, wild shit.
00:19:56.319 --> 00:20:09.599
Another way to describe it, like literally plugins where people are plugins are firing on either retrieve, retrieve multiple, and in there you're doing all sorts of crazy filtering, removing records and collections, and adding all of that blur sort of overhead into there.
00:20:09.759 --> 00:20:11.200
So, yeah, I think it's good.
00:20:11.279 --> 00:20:24.160
I say it's good to see investments in the core product, in you know, little quality of life sort of things, stuff that isn't flashy, that isn't kind of you know buzzwordy or anything like that, but just good solid features.
00:20:24.240 --> 00:20:26.960
This you know, this is I could eat this all day, basically.
00:20:27.119 --> 00:20:36.559
Yeah, so talking about flashy announcements, I also have some to um I have some of them basically because in all tradition you're gonna ruin it now, then basically.
00:20:36.960 --> 00:20:38.880
Yes, I wouldn't ruin it for everyone.
00:20:39.039 --> 00:20:43.759
So if you're listening, listening, this is now roughly at the 20-minute mark.
00:20:43.839 --> 00:20:45.039
You can just leave it.
00:20:46.400 --> 00:20:48.559
Skip at the end, skip, skip to the end.
00:20:48.640 --> 00:20:50.160
Uh see you in two weeks.
00:20:50.319 --> 00:20:52.559
Um, have a good day, bye-bye.
00:20:52.799 --> 00:20:57.359
Um, but so up to flashy announcements, all of the AI and copilot stuff.
00:20:57.440 --> 00:21:08.559
So basically, um, in old tradition, Microsoft decided to announce new stuff right on the day when we recorded the past episode.
00:21:08.640 --> 00:21:10.640
So you may have seen it already.
00:21:10.880 --> 00:21:17.119
So Microsoft is announcing new copilot with home, code and autopilot.
00:21:17.279 --> 00:21:18.880
Um, what does this mean?
00:21:19.039 --> 00:21:24.480
Basically, home um combines co-work and the chat feature.
00:21:24.640 --> 00:21:42.640
Um, code brings in some more GitHub co-pilot-based capabilities so you can directly in copilot um create new solutions or or work in GitHub repos or on local files with code features.
00:21:42.799 --> 00:21:59.759
And autopilot is potentially the one which is a bit more interesting for me personally, as this is um whatever was previously called Scout, which is like something your digital um assistant or teammate, which is funny enough because.
00:22:00.160 --> 00:22:05.680
I think around the same time, Meta um has released their personal assistant.
00:22:06.319 --> 00:22:13.279
There is a um OpenAI, I think, around dot, which is also going into this direction.
00:22:13.440 --> 00:22:25.039
So all of like these um big flashy players going into that personal assistant um or personal teammate direction, which is um definitely interesting to see at the same time.
00:22:25.359 --> 00:22:28.640
So why would I use this code thing rather than GitHub Copilot?
00:22:28.720 --> 00:22:30.160
What's the advantage, would you say?
00:22:30.480 --> 00:22:33.839
I don't think that there is a in particular advantage.
00:22:34.079 --> 00:22:49.759
Um, I do think it's um what Microsoft wants to build, it's just like you need to have one app, you want to have like one interface you can work with, and you can seamlessly going from summarizing your latest email to um to a card-based project.
00:22:49.920 --> 00:22:59.519
Um I I would expect that it is a little bit less functionality or integration around GitHub Copilot.
00:22:59.680 --> 00:23:04.400
So I think for core developers, they still want to use GitHub Copilot, but we need to try it.
00:23:04.559 --> 00:23:09.440
Um the biggest benefit, I think, is the um integrated Microsoft IQ.
00:23:09.839 --> 00:23:25.839
So there is a lot of IQ lately from Microsoft, including SL work IQ and um all of the fabric IQ, which you know be have been an expert since you have been to Barcelona and the Fabric on there.
00:23:26.000 --> 00:24:01.039
Um, but all of that business context um makes maybe the creation of the application or the the code that needs to be written inside the the code panel um better in the first version, and you don't need to um explain so much around your rules internally, or if you um have a certain requirement, you can directly attach it seamlessly without like downloading it or referencing it in GitHub Copilot.
00:24:01.119 --> 00:24:05.599
So if you have your code style guide stored in SharePoint somewhere can access it there.
00:24:05.920 --> 00:24:10.160
Yes, that's yeah, that's definitely something to to explore.
00:24:10.240 --> 00:24:12.000
Like where does it get the data from?
00:24:12.079 --> 00:24:14.880
Is it I think it's still somewhat connected to GitHub.
00:24:15.039 --> 00:24:25.920
Um, so I hope I hope as well this goes um seamlessly with within the license, so it just uses the same license, very similar to the GitHub Copilot app, maybe.
00:24:26.079 --> 00:24:45.680
Um that you can just see that kind of app inside Copilot, and then everything is basically managed by the GitHub organization, which would be ideal, so you don't need to have something stored in SharePoint lists or something to make sure your code works as you expect.
00:24:45.839 --> 00:24:50.720
So, yeah, um from that perspective, pretty interesting.
00:24:50.960 --> 00:24:59.279
Also, um, which is maybe not so obvious, um, the whole product basically got a small rebranding.
00:24:59.440 --> 00:25:02.720
Microsoft is no longer talking about M365 copilots.
00:25:03.039 --> 00:25:04.480
Microsoft rebranding things, really?
00:25:04.640 --> 00:25:07.279
Yeah, they're just renaming so that's such a shock, yeah.
00:25:07.359 --> 00:25:07.920
Yeah, yeah.
00:25:08.319 --> 00:25:12.400
So Excel is like Excel since 1997 or something, so definitely a shock.
00:25:12.480 --> 00:25:14.319
Windows is that's brand power.
00:25:14.400 --> 00:25:17.440
If you can stick around for that long, then you know your brand is strong here.
00:25:17.680 --> 00:25:24.480
Yeah, but in in terms of co-pilot, it's no longer M365 co-pilot now, it's just copilot.
00:25:24.880 --> 00:25:34.960
So I think um the idea is really to create one co-pilot platform which then brings in all of the different co-pilot capabilities um in one space, right?
00:25:35.039 --> 00:25:40.000
Yeah, because we got co we got copilot and the traditional copilot, uh emphasis by copilot, that's what I always call it.
00:25:40.079 --> 00:25:46.480
You've got copilot in dynamics, you've got copilot in Azure, you've got copilot in um power platform, you know.
00:25:46.640 --> 00:25:49.359
So it's um it's a lot.
00:25:50.079 --> 00:25:54.559
We are basically one step before we have copilot on our toaster or fridge.
00:25:54.720 --> 00:26:16.079
So um in this case, um, we just have one copilot app which then just serves everything or should serve everything in the future, which I like as an approach because then you just have like one thing to maintain and um you have the same underlying SDK perhaps, which comes to the next fancy announcement, which is managed runtime.
00:26:16.319 --> 00:26:24.160
So managed runtime or Microsoft Copilot Managed Runtime is uh going into public preview.
00:26:24.240 --> 00:26:34.880
I think when you listen to that, it is already in public preview, but it's basically the platform to run code within the Microsoft 365 tenant.
00:26:35.119 --> 00:27:19.519
So you get all of the great governance features of the uh of your Microsoft tenant, including Intra and the Microsoft Admin Center, and also all of the um connectors from the Power Platform, you get um the um different DLP uh DLP policies, you get um the graph integration, you get work IQ, everything in there, and then basically um you can just bring your app, you can develop it with the new app scale in coverg, or you can have your custom-built app, or you can, for example, as well directly integrate this with um third-party tools such as Lovable.
00:27:19.680 --> 00:27:31.279
I think Lovable in this case is the premium um example, as they have a direct connector to Microsoft Managed Runtime.
00:27:31.680 --> 00:27:46.079
Um, so you can create your app in Lovable and then directly with like one click to deploy it into Microsoft ecosystem, um, which comes with um the business and enterprise license.
00:27:46.240 --> 00:27:50.960
So if you just have the Pro license or free plan, it is not included there.
00:27:51.119 --> 00:27:56.720
But as soon as you do have the business or enterprise license, it is included in there.
00:27:56.960 --> 00:28:12.240
So pretty interesting because then the idea is that the um Microsoft platform works as a platform and it works as a centralized um governance tool that you can with agent 365.
00:28:12.480 --> 00:28:14.960
I mean, you have been talking about this with AJ.
00:28:15.359 --> 00:28:43.200
Um you can like organize and and govern your um apps and agents and all of that stuff, and um handle all of your standards and rules and have everything in one place, but the user just have their own experience, um, whatever they would like to work with across teams or within smaller teams, um, which is then making their lives easier, and you don't need to rely on the UI of a model driven app anymore.
00:28:43.759 --> 00:28:45.279
Happy users, happy life.
00:28:45.440 --> 00:28:47.759
So yes, absolutely.
00:28:48.000 --> 00:28:50.720
Um, I have one more fancy one.
00:28:50.960 --> 00:28:51.279
Wow.
00:28:51.759 --> 00:28:53.599
Very quick, very quick, very demo.
00:28:54.000 --> 00:28:55.119
Um, work IQ.
00:28:55.200 --> 00:28:59.039
I already mentioned work IQ now like 15 times in the last 10 minutes.
00:28:59.279 --> 00:29:06.960
Um so far, work IQ was working across the Microsoft 365 apps, so all of your print work IQ works, yeah.
00:29:07.039 --> 00:29:07.519
It works, yeah.
00:29:07.920 --> 00:29:09.359
It works, yes, it works for you.
00:29:09.519 --> 00:29:16.319
Yeah, so work IQ basically is a layer on top of graph so far.
00:29:16.640 --> 00:29:21.759
Because if you if we look at graph, have you ever worked with the graph API?
00:29:22.720 --> 00:29:29.200
I have the graph is there's lots of really nice, lovely endpoints there for all sorts of information about it.
00:29:29.359 --> 00:29:37.680
Yes, it it has like all of this Teams information, SharePoint, Outlook, calendar information, everything you need.
00:29:38.240 --> 00:29:39.440
Everything about you.
00:29:40.160 --> 00:29:40.799
Exactly.
00:29:40.960 --> 00:29:46.480
Um, it knows everything that I have done at work, which is a bit terrifying, but also very helpful.
00:29:46.720 --> 00:29:53.440
Um but working with this API is maybe not ideal for a large language model.
00:29:53.839 --> 00:29:56.480
So what Microsoft built is work IQ.
00:29:56.640 --> 00:30:08.400
It's just an intelligence layer between that, um, between Graph and any custom agent, copilot, copilot studio, github copilot, whatever there is.
00:30:08.720 --> 00:30:14.000
And so far, as mentioned, this was focused on the my M365 suite.
00:30:14.720 --> 00:30:27.039
Now with the new public preview, which has been started on the 30th of September, you also get um Dynamics 365 and Power Platform apps into that work IQ context.
00:30:27.279 --> 00:30:36.559
So your Dynamics 365 sales or your Dynamics 365 perturbations data is available in work IQ if you want to.
00:30:36.640 --> 00:30:46.960
It's an opt-in feature, but you can directly then set this in connection, and also the work IQ MCP is able to update this data directly in the system.
00:30:47.119 --> 00:30:53.839
So it works with um first-party apps, it works with um finance, it works as well with Dataverse.
00:30:53.920 --> 00:31:19.200
So you can just bring um all of your custom tables into it, and you can just access this very seamlessly from from Copolitic and Cowork, for example, um, build in in custom agents, and um set the meeting you do have, or the Teams chat information you do have directly in association with that opportunity project task or whatever there is.
00:31:19.440 --> 00:31:25.039
So that opens up many, many different new um features and approaches.
00:31:25.279 --> 00:31:40.799
Also, I would say kills a lot of custom agents you may have built of the past weeks and months, because this is exactly what a lot of custom agents are doing, bringing in different data sources and then writing this to potentially your CRM system.
00:31:41.119 --> 00:31:49.440
And if you're like all on the Microsoft platform, you may have something like that created for your own uh purposes, but maybe that kills it off.
00:31:49.839 --> 00:31:52.720
Um something to I was talking, we were talking about this.
00:31:52.960 --> 00:31:53.440
Was it with you?
00:31:53.519 --> 00:31:55.119
I might have been with Emma Claire Shaw.
00:31:55.200 --> 00:31:58.079
So I think it's it's great to see these work IQ investments.
00:31:58.160 --> 00:32:12.319
I guess the challenge is that yeah, from a configuration standpoint, I'm guessing you need to be highly privileged on the in tenant level to be able to go and set up the connection between work IQ and between sort of Dataverse to do that.
00:32:12.559 --> 00:32:12.880
Yeah, yeah.
00:32:12.960 --> 00:32:25.519
So the initial the initial setup, um, I think there is still um global tenant involved and also need to be administrator on the um Dataverse environment um to opt in for that, yeah.
00:32:25.839 --> 00:32:44.480
Yeah, because often the challenge that we find with our enterprise customers is okay, we we we we we find ourselves often very lucky that okay, yeah, they've got power platform administrator, that means we can get most of the things done, but then trying to do anything affecting the M365 environments or even indeed at a global level, it just involves different teams and slows things down.
00:32:44.640 --> 00:33:03.839
So I think the concept's great, they just need to make it a bit easier to kind of uh set up the initial kind of configuration without these highly privileged roles, because otherwise I think people are just gonna fall back to using connectors, MCPs, you know, stuff that is possible for you to do, provided that you've got access at the database level rather than you know at the tenant level.
00:33:04.160 --> 00:33:20.799
Yeah, um, that's also what what I have seen because I had just struggles as well doing some previews that there is certain because it ever it now happens everything in M365, um, you very easily need a tenant or global admin, basically.
00:33:20.960 --> 00:33:24.559
Um, there is a new role which is the II administrator.
00:33:24.720 --> 00:33:40.960
Um, potentially it makes sense to as well introduce here maybe um something in between the II administrator and the um global admin, or to have maybe something um sort of sorted out privileges for these new features in particular.
00:33:41.200 --> 00:33:44.160
Um, I trust Microsoft that they're working on it.
00:33:44.319 --> 00:33:51.039
Um, if not they will hear this feedback as well um at the Power Platform Community Conference in Las Vegas.
00:33:51.119 --> 00:33:52.240
So I will then direct you too.
00:33:56.960 --> 00:33:59.359
I'm gonna rage about this, you know, literally.
00:33:59.599 --> 00:34:02.400
And I was like, Yeah, thank you for feedback, that's very helpful.
00:34:03.680 --> 00:34:04.960
Okay, thanks.
00:34:05.599 --> 00:34:07.519
Let's have an in-and-out burger, man.
00:34:08.480 --> 00:34:16.159
No, no, no, you know, you you have in and out burger with them first, so you so you invite them under false, tasty pretenses.
00:34:16.400 --> 00:34:25.280
They think they're going for a double-double chocolate shake and a fries, but in the end, they walk away feeling, oh, I've just been I've been like catfished.
00:34:25.760 --> 00:34:26.159
Molested.
00:34:26.559 --> 00:34:27.440
I've been catfished.
00:34:27.679 --> 00:34:29.679
This was supposed to be an ice in an outdate.
00:34:29.760 --> 00:34:36.719
Instead, I've now got 10 additional items for my backlog, uh, and a very unhappy German who has expressed his opinions towards me.
00:34:37.360 --> 00:34:38.400
Maybe that happens.
00:34:38.480 --> 00:34:39.519
Um, I hope not.
00:34:39.679 --> 00:34:44.400
But yeah, I I try to be very neutral with my feedback and try to help, of course.
00:34:44.880 --> 00:34:49.679
You you are you are you are you are very polite and you are also very well known.
00:34:49.840 --> 00:34:56.239
Um, yeah, so just pro tip for people listening, you know, Seb is the guy, he can he can connect you.
00:34:56.320 --> 00:35:00.320
He's he's he's a he's just bringing bringing bringing people together.
00:35:00.480 --> 00:35:05.440
He's very, very good, he's very, very charming and very, very well connected individual.
00:35:05.760 --> 00:35:09.840
What do you want from me that you're saying so nice things about me?
00:35:10.400 --> 00:35:12.719
You'll find out, you'll find out in due course.
00:35:13.039 --> 00:35:14.960
I am very concerned.
00:35:15.199 --> 00:35:23.119
Um what you also should be concerned about if you're attending the Power Platform Community Conference in two weeks.
00:35:23.360 --> 00:35:24.320
It is literally two weeks.
00:35:24.480 --> 00:35:24.880
It's three weeks.
00:35:25.119 --> 00:35:26.480
It's three weeks, yeah.
00:35:26.719 --> 00:35:28.079
Yeah, you know, it's two weeks now.
00:35:28.159 --> 00:35:34.800
So when this when this episode releases, it's two weeks, literally, because then um next week, next week AI tour.
00:35:34.880 --> 00:35:45.360
So okay, when this comes out this week, AI tour in Singapore, the week after AI tour in Cologne, or or local German or European listeners, I will be there as well.
00:35:45.599 --> 00:35:49.519
Um nice, nice, cool.
00:35:49.760 --> 00:35:55.760
Um, and then the week after that is um power platform community conference.
00:35:56.000 --> 00:36:01.679
And what you should be concerned about is we're doing, I think it's a live podcast recording there.
00:36:02.000 --> 00:36:14.000
So I think you can join, uh, put on some headphones and listen to this live in the making, just to make sure that there are no cuts, there is no script, there is just us wiping.
00:36:14.159 --> 00:36:17.440
And um, I don't know exactly where it will be.
00:36:17.599 --> 00:36:22.400
I've not checked that yet, but it will be on Wednesday, on the Wednesday, I think, early afternoon.
00:36:22.480 --> 00:36:25.760
I think something like see us live recording.
00:36:25.840 --> 00:36:27.599
I mean, like, live recording, yes.
00:36:27.679 --> 00:36:29.519
So it will be a very special episode.
00:36:29.760 --> 00:36:35.360
So huge thank you and shout out to um Vendana at Microsoft for reaching out to us there and uh getting that organized.
00:36:35.519 --> 00:36:36.800
That's really, really nice.
00:36:37.039 --> 00:36:38.239
Yes, absolutely.
00:36:38.400 --> 00:36:38.960
I agree.
00:36:39.119 --> 00:36:40.719
So, yeah, that was so nice.
00:36:40.960 --> 00:36:46.559
Um, therefore, I think for all of these news, updates, stuff like that.
00:36:46.800 --> 00:36:50.159
Um we've covered your actually, it's been meaty.
00:36:50.559 --> 00:36:52.880
There's lots of good content.
00:36:53.199 --> 00:36:56.000
This this is starting to become almost like a semi-professional thing.
00:36:56.079 --> 00:36:59.920
It's as if it's as if M365 distilled won the award, you know.
00:37:00.000 --> 00:37:07.119
We were so despondent at that, and then now we're we're kind of like trying to right, let's let's just get this podcast better, you know.
00:37:07.199 --> 00:37:09.039
We're just gonna put it for the content, you know.
00:37:09.119 --> 00:37:11.199
It's it's acts as like a catalyst for growth.
00:37:11.280 --> 00:37:11.679
I like it.
00:37:11.840 --> 00:37:19.119
So, do you think that the um nomination has done something positive?
00:37:19.599 --> 00:37:21.679
I well, uh well, maybe let's see.
00:37:21.760 --> 00:37:31.360
The the time time will tell, but I'm sure that yeah, we we we now have I mean, having that albatross around our neck in terms of having an award would have been quite scary.
00:37:31.440 --> 00:37:40.239
But now that we can sort of say that we're finalists, we're we're we're a uh UK Community Award finalist podcast, it's just rolls off the tone, doesn't it?
00:37:40.320 --> 00:37:41.119
Yeah, yeah, yeah.
00:37:41.360 --> 00:37:43.599
I I it it totally sticks with me.
00:37:43.760 --> 00:37:50.639
I I think I will put this as a banner right here next to this light here, just really let it shine.
00:37:50.960 --> 00:37:57.519
Yeah, it's clearly the one accolade that you need to just basically tell everyone about and never let them forget it because it's just so important.
00:37:57.760 --> 00:37:59.119
Absolutely, absolutely.
00:37:59.280 --> 00:38:06.239
Right, before we close, um, one very last shootout to Emma and Crack, which do you have on your um podcast?
00:38:06.400 --> 00:38:08.400
The Power Platform Panic Room.
00:38:08.639 --> 00:38:14.400
I think um Power Platform Panic Room.
00:38:14.800 --> 00:38:15.360
Penigroom.
00:38:15.440 --> 00:38:16.320
I thought we said Pentagon.
00:38:16.480 --> 00:38:21.199
Panic Room Penic Room Panic Room Panic Room, okay.
00:38:21.280 --> 00:38:21.760
Panic room.
00:38:21.840 --> 00:38:28.400
I thought you said they were doing some I thought they were doing some like satanic ritual or something, maybe.
00:38:28.880 --> 00:38:29.599
That would be also cool.
00:38:29.679 --> 00:38:32.000
Maybe maybe to just to make that average work at some point.
00:38:32.079 --> 00:38:33.119
Sub summoning demons.
00:38:33.199 --> 00:38:34.079
Yeah, that'd be quite cool.
00:38:34.159 --> 00:38:36.239
Anyway, but yeah, please tell us more about this podcast.
00:38:36.559 --> 00:38:42.239
Yes, so uh Emma Claire Shaw and Craig White are doing this um podcast together.
00:38:42.400 --> 00:38:43.840
It has a few episodes on now.
00:38:44.079 --> 00:38:50.320
I I just was not aware until their session on um uh the CEO star kit, rest in peace.
00:38:50.559 --> 00:38:56.800
And um therefore, um uh it was very pleasant to to listen on to a few episodes so far.
00:38:57.119 --> 00:39:05.199
So yeah, if you if you're searching for more um professional podcasts, yeah, for a better more professional podcast, yeah, yeah.
00:39:07.440 --> 00:39:07.920
There you go.
00:39:08.079 --> 00:39:12.000
Yeah, just this one that's literally just turned up and it's just doing things correct for the day one.
00:39:12.079 --> 00:39:14.000
Just yeah, they they're they're very funny.
00:39:14.079 --> 00:39:17.199
So very very nice lats, if you want to say that like this.
00:39:17.360 --> 00:39:19.920
So um, yeah, definitely give it a shout.
00:39:20.159 --> 00:39:24.000
Um I think it's more professional than yeah, it's more professional.
00:39:24.960 --> 00:39:25.679
It definitely is.
00:39:25.760 --> 00:39:28.320
I can tell you right now it is more professional than this.
00:39:28.880 --> 00:39:30.079
Oh, listening to you a second, yes.
00:39:30.239 --> 00:39:35.840
If I listen to a single second, I can tell you right now, I would probably I'd bet my life savings on it.
00:39:36.960 --> 00:39:44.320
Awesome, with that on that bomb shell right away.
00:39:44.480 --> 00:39:45.360
We don't care.
00:39:45.599 --> 00:39:49.440
Uh please stick with us.
00:39:51.519 --> 00:39:54.320
This is this this is the only thing that's keeping him going, Sebastian.
00:39:54.400 --> 00:39:55.599
So yeah, don't don't disappoint him.
00:39:56.000 --> 00:39:56.800
Do you set his face now?
00:39:57.199 --> 00:39:58.480
Do you set his face now on camera?
00:39:58.559 --> 00:40:00.480
So people this is this is the this will be a good wheel.
00:40:00.639 --> 00:40:05.920
So Sebastian, just look into the camera and just be like, sad eyes, please listen to my podcast, please.
00:40:06.079 --> 00:40:09.920
Oh can you can you please listen to my podcast, please?
00:40:11.760 --> 00:40:12.400
I'm not good at us.
00:40:12.639 --> 00:40:14.000
Sorry, all right, all right.
00:40:14.159 --> 00:40:15.199
See you in two weeks.
00:40:15.440 --> 00:40:19.440
See you in Singapore, Cologne, or Las Vegas.
00:40:19.599 --> 00:40:21.599
We'll be very happy to see you in person.
00:40:21.840 --> 00:40:22.400
Bye bye.
00:40:22.719 --> 00:40:24.719
See you, Joe, in Cologne, which is weird.
00:40:24.960 --> 00:40:25.519
See you, okay.
00:40:25.840 --> 00:40:26.079
Hello.
00:40:27.119 --> 00:40:27.679
Whatever.
00:40:27.840 --> 00:40:29.039
Bye bye, take care.
