Power Platform Boost Podcast

Hack the (AI) Planet! (#58)

• Ulrikke Akerbæk and Nick Doelman • Season 1 • Episode 58

Share episode
Ulrikke:

Can I talk about one thing please?

Nick:

It's half your show. You talk about whatever you want.

Ulrikke:

So you know the thing we talked about from the release wave.

Nick:

I want to let everybody know. Before we started recording, Ulrikke said she had a monster and something else, but I know what you're talking about, not something else, but it's now live and I tried it out and it's just.

Ulrikke:

I almost cried when I saw it. It was so beautiful. You just go in through this interface and it's, it's the Hello. Everyone, and welcome to the Power Platform Boost podcast, your timely source of Power Platform news and updates, with your hosts Nick Doelman and Ulrikke Akerbæk.

Nick:

Fair enough. So all of this AI stuff that we've been talking about, that I've been talking to you about that, I'm talking to my wife about that, I've been talking to friends about that aren't even in this space. There's been an overwhelming amount of information. There's people in businesses trying to apply it to their businesses. I've heard, I see I've heard of people that say I don't want to do anything about AI, I'm not going to worry about it, you can't make me do it, you fire me before you make me use it.

Nick:

To other people that seem to be all in yes, ai is great, and then you kind of try to zero in on what it is they're doing. And so much information, so many things. I think we're all. I don't think we're struggling. I just think that we're at a buffet right now and you go to a restaurant and you see all the food in the buffet and you're like where do I even start with all this? And then you just load up your plate and then, all of a sudden, your plate's almost overflowing. This is where we're at right now, I think, in the stage of all this ai information and things like that. Um, so, yeah, so where, where is your head at?

Ulrikke:

this week in terms of ai. Yeah, because, um, yeah, this come, yeah it's. It comes from a place where we look at the show notes and we recognize that over half of the things that are in there are related to ai co-pilot. And then we go what do we do? Do we keep this a very much a power platform specific podcast, because the co-pilot includes um is included in the platform, so or do we kind of try to manage it?

Ulrikke:

And I think we're both at a place where there's so many important things that are happening around co-pilot studio and that, as a, as a product that we have to touch on in order to and to spread the word to people out there that maybe not have time in their daily work to keep on top of these things.

Ulrikke:

And I still want to do that, even though maybe we don't touch on the other products of the platform as much, because right now, the news and the updates and the announcements that we see it's full on around open AI, about Copilot Studio and about agents, and so I think what you're going to see is that we follow where the news and the updates and the new capabilities are, and that's what you're going to see is that we follow where the news and the updates and the new capabilities are, and that's what we're going to talk about and be preoccupied with Now. When Fabric came along, that was very much on our radar. You know, we've talked a lot about Foundry and there's so many things that come in that are new that we talk about, so I think this is just natural for us to right and and, and we're looking for feedback too from the listeners, like you want to just hear.

Nick:

I mean, I know some of you just want to hear the news and updates and you probably skip over the the banter that we have about you know the weekends and the weather and all that, and I know that I've also heard from a lot of you basically saying, yeah, just hearing you two talk about it makes me feel better in my position, where I'm at trying to figure this out as well. So, but definitely provide this feedback. And you know, and again, we always say, this podcast is really just to give us an excuse to chat with each other, but really, at the end of the day, it's really sharing with the community and engaging this community. You know, making sure we all as a community work together and, um, rising tide to make all boats float up or some bad, bad thing of that saying Um yeah, yeah, no.

Ulrikke:

So so how about this? Um, for the future episodes, what we'll do is we'll share with you the kind of links that we send to each other anyways, because our WhatsApp chat is full of links back and forth and it's a crazy hot mess of everything. So we'll keep it to the tech related things, but I mean the things that preoccupied us, the things that make us want to share with one another. That's what we're going to share with our listeners going forward. So that's you and that's what we're going to share with our listeners going forward. So that's you and that's what we're going to do. That's a promise we make and that's kind of where we draw the line, I think.

Nick:

Yeah, that sounds awesome. So I think, just to kick this off in terms of things like that, there was a post by our friend, yuka Nirenin. Of course everybody knows Yuka and to me I don't know what it was, but maybe it was the mood I was in or the when I read it, but to me it was just sort of like yes, yes, this, this to me kind of hit. Now I'm not going to, we'll share the link to the post, but specifically, I'm just going to basically just bring up the what he said, like oh, just I'm going to take a line out of what he said, so you'll see the whole post. But basically he said because AI as we know it today is not about products or solutions. It is not going to magically allow you to increase productivity or replace employees by signing up for service X from vendor Y. It's not a top-down digital transformation initiative, it's a bottom-up revolution, just like low-code was is only this time nothing is sacred or safe. The whole post itself kind of gave me chills.

Ulrikke:

Yeah, and it's funny because this is LinkedIn, right? So you see that in one post and you read it and you go into grumpy Finn mode with Yuka. And then you scroll down and then suddenly you hit global enterprise, american marketing, with from Steve Mardu, when what he's posting is exactly what Yuka says. This is not about, because he's now got a new suite of services and products all aligned from AI out on all the things Yuka says you cannot, or you, you know this is not what it's about.

Ulrikke:

So I and I think that that is my LinkedIn feed at the moment you just have two sides of the spectrum going ding, ding, ding, ding and my brain is following this as a ping pong ball all over the place. And I read yuka's post and I go, yes, ah, yes, you got it, I'm, I'm on board. And I read what steve's doing and I'm like, yeah, oh no, that's what we should do. Why are we doing this? And then I read to the next one and I look at what fem is doing and I'm going, what I would? I should do that. And then, yeah, anyone else you know, raise a hand, because I think this is what our feed is like these days and it's. I don't think the point is to settle. The time is not to settle. I think that's the point. The time is not to settle. I think that's the point. The time now is to embrace both what you're saying and what Steve is is talking about and producing.

Nick:

Yeah, because at the end of the day, whether like I think the bottom line is whether we like it or not AI is going to change our jobs. Is it going to come for our jobs? I don't think so, but our job is going to change. And this brings up to and like again what I liked about yuka's thing. It gave a very much of the kind of that movie hackers feel like hack the planet. That was something I actually posted on it. It's about, you know, using this stuff. And he talks about vibe coding and I know there's our feed is full of what vibe coding is and what it isn't. There's the naysaysayers like going, well, vibe coding can't do this, and the other is going, this is going to change everything. And I think I even posted on one of Steve's things. It's like okay, programmers, pro coders, ai is not going to come for your job. Steve is Now we've been saying that for years with low code solutions and things like that. So I think, at the end of the day, everybody's safe.

Nick:

But for me doing when I'm doing development tasks, my visual studio code desktop right now, full pilot, a github co-pilot is open and I'm experimenting with different models and things like that and I am actually really impressed of I'm both. It comes up with some absolute garbage sometimes, but it also comes up some really good points and it goes through and highlights the changes. So not only am I able to dive into things, I'm learning new things like well, I didn't know I could do that. That's really cool. I can apply that to other places, I mean because I'm coming from a place of understanding code. If I didn't know what I was doing at all, then I would have to really break it down into smaller and smaller chunks in order to be successful, which there's going to be a line of diminishing returns in terms of being able to develop code, understanding code and get it to all work together. And, of course, this is going to get smarter and smarter. And, of course, hopefully, these AI agents are also going to incorporate things like security and governance, like all those other important side pieces that I think sometimes we tend to forget a little bit, pieces that I think sometimes we tend to forget a little bit. So, anyways, it's really I don't know where I'm going with all of this, but in terms of the tools we're using every day, I'm trying to, I'm using, I got into a mindset. Okay, I need to use this every day. So a couple quick wins for me.

Nick:

This week we were working on you and I were both working on something with trying to wrap our heads around some multi-factor authentication changes that are coming through and how that's going to affect all of us. I went through and applied into a reasoning model of doing some research. Here's my problem, here's what I need, here's your role, here's this and it did. It broke it down into a chart format, breaking down what it is that we needed to do, why we needed to do it, the impact of all of this, and then even allowed it to ask some questions and things like that. To me, that was really powerful. I shared that with the team, and so that was something we kind of worked and collaborated with a little bit together and try to kind of sort all of these things out.

Ulrikke:

And can I just say something before you continue? Because what I loved about that was that actually, it also looked into the future. It said today this is the limitation, this is what you need to do, but please make sure that you keep a close eye on the release notes or the release plan, because this is changing and Microsoft will soon enable this and this and that, and also, by the way, make sure you don't check this checkbox. So it was kind of, yeah, it was a business oriented, it was a solution oriented, it was detail oriented and it was kind of future proofing its own solution. I loved it, it was brilliant.

Ulrikke:

When you put that in the chat, I thought, oh, you just saved my ass because that was what I was just going to do. Right, cause you just beat me to it and I and I love it and the fact that we just share it across, because I think there's a certain degree of prompt gatekeeping going on as well in companies today. Right, you want to be the smartest kid on the block. You want to be the guy that's most the the best kind of prepared for a meeting. You want to do your own research with chat deputy or ai service you use. You want to go into the setting and be the star. So it's. I feel like more and more people are kind of gatekeeping and not sharing, because I don't see what you did as often as I should at this point, so I'm not sure if that, you know, strikes a chord with anyone. Maybe we could have a conversation in the chat kind of how often do you share your stuff with other people, or maybe kind of holding your cards close to your chest. I don't know.

Nick:

This is, this is what I've been starting to do is like it's even um, even in one of my presentations I was putting together I'm going to dynamics con this week and I thought, oh, and this is on our platform pipelines which I'm presenting a hundred like. But anyways, I thought, oh, it'd be great if I did a slide comparing all the different types of ways to deploy solutions in Power Platform. And I know we have there's people, blog posts and different things. And I thought you know what? No, I'm going to ask ChatGPT and I kind of gave it the parameters here's what I'm doing, here's what I want to compare. And it came back and asked me questions Do you want to stick just to Microsoft solutions or you want to incorporate third-party solutions and how detailed do you want to go?

Nick:

And I put it all together and it presented me with a table that I basically cut and paste and put on the slide and then I also put here's the prompt I use to generate the slide to share with the people. So it's not like it's making me look smart, it's basically going hey, you guys are empowered with this information. You can go forward as well and I don't think there's anything wrong with. I think we're we're beginning to. We'll see that a lot where, um, it's kind of show your work, show your prompt, because with these sharing these prompts, then people can take that and apply it to their own scenarios and learn from that as well. So to to me, this is you know, look like I would say look at us using AI on a day-to-day basis, you know so.

Ulrikke:

Yeah, yeah, yeah, no, and and I and I recognize that and also the frameworks, right, so you have some just kind of I know you were going to share all the fancy things. You uh, you can go back to that Also keeping an eye on time and on the stuff we want to share, because this really ties into the next link that we have here, which is yours and this is something you shared with me a video on YouTube, because I also have a bit of a thing with that. Do you want to share what that's all about?

Nick:

Yeah, absolutely so. Basically it was a podcast called Learn it All. It's on YouTube, it's not on Spotify, but it's on some of the other ones, but we'll put the link to the YouTube link, for sure, and it's basically an interview with someone called Jeff Woods. You may or may not have heard of Jeff Woods. He's written a book about AI which I'm actually reading or I'm audiobooking right now Not right right now, but you know what I mean.

Ulrikke:

But it's basically that's multitasking on the next level. You're too much of a man to do that. I did not expect you to listen to that at the same time. No, no, no.

Nick:

But it talks about what leaders need to know about ai in 2025 and he had a couple really interesting points. Basically, are you going to be the next net? Are you the blockbuster? Are you the next netflix? And this is how even the book starts. Talk about blockbuster, multi-billion dollar successful company and you know. And then now like I can't you can't go and rent videos at a store anymore. It's just that's way in the past. And about the shift to Netflix and the streaming services and things like that, just showing how this technology changes. But the other thing is a couple of things that he said in the podcast is a job is nothing more than the skills you apply in the process you follow is nothing more than the skills you apply in the process you follow. And basically I think a lot of it is a part of our jobs is applying the ai as a tool to to our jobs, um, and making that a lot, a lot faster. And then also the other thing is that ai is a tool, not an end destination. I know a lot of people okay, we need to be an ai company, we need to to do this. Well, what does that mean? And to me it's like if you're a company.

Nick:

And here's an analogy I heard yesterday and this is actually good credit to my wife, she came up with this 100 years ago you milked a cow to get. If you needed milk, what did you do? Someone milked a cow by hand in a bucket. And then you get your milk by hand in a bucket, and then you get your milk. And then what happened? We had these automatic milking machines. So still, someone had to put on the milking machines.

Nick:

I grew up on a farm. I did this every day for my for like 15 years of my life. Um, and then the milking machine would go and you would do that. And then you're now to a point where we're getting robotic milkers. So, but at the end of you know, and the robotic, the cows go in the stall, the robots hook it up. It's really cool if you ever get a chance to see it, you should.

Nick:

But at the end of the day, what are we doing? I want a glass of milk and it still comes from a cow. It's all of this process and this is part of our job, and ai is accelerating how the jobs are getting done. It's changing the context, but at the end of the day, your job is still the job, so that's's not changing. It's AI being applied to it. So AI is not going to take your job. It's going to change your job, but again, it's all about the skills you're applying and the process you follow. The process is changing and maybe some of the skills as well. So that again, ai is the tool, not the destination.

Ulrikke:

Yeah, and you share that. I'm sorry.

Nick:

Go ahead. Yeah, and you share that. I'm sorry, go ahead.

Ulrikke:

No, no, you talk now I've been flabbergasted real predicaments where they're facing bankruptcy, they have a lock situation in a culture they don't know, in a situation they can't handle, and they're looking at closing their business down. And they reach out to him or in some way they talk to Jeff and he says, oh, have you asked AI? And then with a very clever and very thoughtful and very thorough prompt, they're actually able to navigate some of these business challenges just by that prompt. And it blows my mind now how little I've done in the past. Now I've said this multiple times If you're not ashamed of the code you wrote a year ago, you haven't had any progress. That very much applies to AI and the time span is a week. I can't believe I tried to solve the things I solved last week with my head.

Ulrikke:

Now that I'm in, I'm now, like you, have a Copilot no, sorry, github Copilot up and running. You know, I have chat tippity and I have a bazillion chats going and we have so many things on the go Business strategy, prepping for meetings, making my own visual brand. There's so many things on the go. Business strategy, prepping for meetings, um, making my own visual brand. There's so many things going on and I can't believe I didn't understand this way of using it before, because what I learned from this is his approach to using ai to enhance your own mind, right. So he has a framework and it calls it crit, context, role, interview, task. So you the you build the prompt this way. You give it a context. So I'm a powerful consultant, I work with power pages. That's my expertise. I'm an mvp travel the world, blah, blah, blah. Role. Your role as a, as a attendee at these events. Yeah, you want to learn from me.

Ulrikke:

Now. Give me three to five interview questions to enable me to solve the task of forming my content in a way that you can adapt to. Or I have a meeting. This and this is the context. Ask me questions to make me smarter. I want to be able to think more strategically when I'm in meetings. I can't ask chat TPT to give me the solutions to questions I get in meetings. I have to be able to think that and I want to be better at it. I'm using it as a tool to help me expand and grow my mind. That is what I've unlocked the last few weeks. I've been just it's how. It's fantastic.

Nick:

I'm blown away by it yeah, and basically it comes down to his whole, his whole thing. Uh, jeff wood's thing is use ai as a thought partner, um, and and that's what I've been doing with like it's as opposed to yeah, like exactly what you said yeah, or as a yeah, you're the thought leader and it's your thought partner.

Nick:

It's, it's the person you bounce ideas off. I mean, I still encourage people to do that, like I do that all the time uh, bounce ideas off real people. But this is also. It adds another context, gives you another avenue and, yeah, it just even produces information of like trying to solve I forget the context. I was trying to solve another problem and it came back with a solution for me that I didn't even really think of and I'm like huh, wow, so yeah, but don't you want to, because that's when I stop, because I don't want that.

Ulrikke:

And I stop because I don't want that and I've explicitly told it not to do that. I want it to teach me to evolve my brain to the point where I can think of the other thing. Right, because if you constantly ask it to give you the answers, what are you going to do? You're going to become lazy and your brain is going to shut off. Because that's what the brain does, because it will optimize for the easiest path of least resistance. So what I'm? And it's hard.

Ulrikke:

It is now very taxing for me to use chat, gpt, because suddenly there's an added layer of always accumulating knowledge. I'm pushing myself, I'm stretching my brain. It's become a friction, full experience for me. So I'm now kind of conscious when I have the mental capacity to go in and work with it, because suddenly it takes more, because it just gives you the answers. Well, it's nothing right. So, but what I do recognize is that when I can ask, that I don't ask you as much, because before I would ask you or I would ask a friend or ask someone else.

Ulrikke:

I'm looking into this problem. Am I seeing the full picture? Can you see what's wrong with this. I mean experience. This is really weird. Or I'm going into this meeting. Do you want to have a bit of a call before so we can kind of just give each other a little boost and a little context here? No, now I find myself doing that on my own with Chat to PT, and I really don't want anyone to interfere with that process, because now we have a thing going. Does that make me more isolated?

Nick:

Hmm, that's a good question. And I just wanted to go to your first point about giving the answer. And I totally agree. It's like, oh, there's the answer, why? There's the why didn't I think at that moment? But then there's also hey, I think it's more.

Nick:

The benefit is did you think about this? And I'm like, hmm, I did think about that. But now that you say it that way, this triggers my, this triggers a thought in my brain. Oh, but maybe I'm not good at that way, but maybe I can take a little bit of that idea, formulate it with my own ideas and come up with something new. This, to me, is the huge benefit.

Nick:

But yeah, in terms of isolation, you're right. You look at social media, right, you know, we're just, you know, going on the different social medias and like, oh, I don't need to ask somebody, I can go and find some of this information on my own. I mean, that's part of the community as well, but that's definitely food for thought. Is this going to? Are we going to have a closer relationship with ChatGPT or Copilot than we actually are with other people? And this is what I think I encourage. We still need to have those conversations, but maybe we're better prepared with these conversations as well, saying, hey, I did this thing with ChatGPT, it came up with these ideas. You're a real human. What do you think of this plan kind of thing. I mean not for every case, but this could be part of the. If we can, I think we need to include our own humans in our loops to make this really effective.

Ulrikke:

Yeah, yeah, 100%. And also I mean I saw so just to kind of keep track of the things, because we're going to go way over this time. So, cause we should have done, we need actually we have enough content to go once a week or more often, so we're trying to squeeze it in so you'll get long episodes. That's just a benefit for you. Cause I saw Femke Cornelius and she posts all the time on LinkedIn prompt, I'm sorry. And this time she was publishing a prompt sheet yes, Cheat sheet that she came up with just a one pager. It was really good, really helpful. But the funny part is, now that I'm so that I'm using chat to be all the time.

Ulrikke:

Actually, I just finished my own and I asked that kind of because I was all into the crit. Because I was all into the crit, there's so many prompt frameworks. I said give me the five most popular frameworks that I need to kind of get the broadest picture and, from what you know about me, the five prompt techniques that I should be using more. Give it to me in a framework that I can easily remember and put it up as a desktop. I can put it on my laptop desktop. And it went oh okay, and then it just created one back and as a desktop icon I can put it on my laptop desktop. And it went, oh, okay, and then it just created one back and forth a little bit and now I have it as a desktop screen. So I mean, this is very much so fun to see things that pop up that you know, you give it like, oh yeah, I just did that.

Ulrikke:

All right, I kind of feel like, yeah, I'm on the same level as Femke Conill is in now. Oh, look at me. But then, and then I look at her next post and I go, no, I'm way off, way behind. But I think also that's one thing you know I ranted to you earlier this week that I'm like, I feel like I'm just, I'm so behind, I'm not doing it right. Everyone's just ahead of me. It's look my right, Everyone's just ahead of me. It's look my LinkedIn, Everyone's just getting it and I'm not feeling it. And you went, yeah, and 99% of the world barely even touched it. It's just in our bubble. It's just we're the 1% of people that get this and because we are surrounded by other people in our little echo chamber, it feels like we're falling behind. But, of course, talk to friends and family. You realize that. No, actually it's just our little bubble, yeah, yeah.

Nick:

And you talk about that and maybe I'm kind of jumping around, but you talked about, like you know, using the co-pilot and I think this ties in. But my wife sent me this prompt that she did and this she has a I think a lot of people have the full Microsoft the co-pilot studio where she put this in, and her prompt was based on previous chats please summarize my personality and it came back. It just sort of blew us away of how that kind of nailed it, but it was very positive. So she followed it up with wow, that sounds very positive, but can you give me some critical feedback? Things I need to work on? And, holy crap, it nailed it. It chopped back with things that you know you're a little this and a little bit too much.

Ulrikke:

so maybe this is something that you might not want to do if you want to hear the illicit truth yeah, nope, because and I've seen variations of this and I think that was a very simple prompt, but I've also seen the internet is full of these where you know you have this really deep, um and really thought and crafted prompt that will give you the things that you don't know about yourself. So tell me the five biggest lies that I'm telling myself and why I'm telling myself these lies, and what would happen if I dare to face reality. And there's always kind of a bit of a caveat going. Make sure you're ready and only put this in if you are actually really ready for the result and that you have time by yourself to process what it comes back with, because this will give you the truth and it's um, it's a bit done and I'm not done it because I know myself well enough to know I'm not ready for it yeah, because and the thing is, because that's the thing ai doesn't care.

Nick:

It doesn't care about your feelings. Yeah, maybe, that's. Maybe that's the episode title ai doesn't care about your feelings yeah, exactly, it's an internet bully.

Ulrikke:

No, no all right, let's yeah let's try to keep track of things here, okay, so, um, so all of this is very um. I think it's valuable, not just for us but for other people, I hope, uh. But there are also news and updates in terms of the technologies. So, for instance, you have what's new in Call Palette Studio, the April version we're now in the middle of May, so maybe a bit behind, but actually for April, the computer use for Call Palette Studio agents, now new limited research preview, and Charles Amana says if a person can use an app, the agent can too. So I mean, this is, like you said last time, rpa for agents and co-pilots and yeah, so it's very interesting to see the two worlds merge together I've signed up for it.

Nick:

I haven't got a response if I'm in or not. You need a us based tenant, which I have set up the the us-based preview tenant. So I'm curious the fact I'm able to set up that tenant in my environment, but I'm not. Well, we'll see.

Ulrikke:

We'll see and I'll hopefully report back yeah and uh, there's a new graph connectors and you have advanced approvals for agent flows. This is very interesting, jesus. When they unlock that, the advanced approvals wow, and you have the reasoning and you have the transparency to see what it does. Yes, cobalt Studio, support for customer managed keys We've talked about that before and a few other things. So make sure to check what came out of April in terms of news and updates for Cobalt Studio, what came out of April in terms of news and updates for Cobbley Studio. And also we had Bail, which used to be called. What did we use to shorten it for BizApps?

Nick:

BizApps.

Ulrikke:

Launch Event, I know so, microsoft Business Applications Launch Event. That's what it stands for, bail, but we used to shorten it for something else. I can't remember what it was, and I saw a really cool demo from Kendra which blew my mind. It has to do with enhanced testing capabilities in Copilot Studio. Okay, so what she shows is and this is just, I get so excited about this, I get excited about everything, but this is just. This is really cool.

Ulrikke:

So she creates an agent and then she configures it, and that's one part of her demo. And then she configures it. That's one part of our demo. And then she goes in and she says all right, so let's start testing it. And then, of course, you can test it in the interface by chatting with it. But it's an agent. It should be able to go off and do things on its own. So what you can actually do now is you can say, oh, so we need some testing. Can you create tests for you? And then it does. And then not only that, but you can say, oh, nice test, I love it. Can you now produce test data so that I can test you using your test data that you created, on the test you created to test that you work. Yeah, sure, it does that too, and I'm like I'm blown away. It's just an inception thing. And Kend, way, it's just an inception thing. And then kendra is also just a freaking great presenter and so it's just. It just blew my, blew my mind.

Ulrikke:

So test and debugging, agent, actions in copilot, studio people, automatic testing and also that brings me to vibe coding, because something you said we talked about vibe coding. This is a few weeks back. You said said well, with vibe coding comes the throwaway app mentality right, so you can create an app in a week because people go oh, how are you going to maintain it? Because it's a crap app maintenance. You're going to edit one thing and it ruins the whole thing.

Ulrikke:

Well, why would you need to maintain it if you could just create one new one just as easily? And not only that, but then all the new will bring in all the new frameworks and all the updated versions of everything, as long as you have the testing, so that you're able to test thoroughly that it works the same way as the other one, that it handles data the same way, it's just as secure, just as accessible. If all of those tests in place, why wouldn't you just create a new app? Those tests in place? Why wouldn't you just create a new app? And I think testing, just by thinking through that scenario, testing is going to be so important going forward. So if you're a techie and you wonder where you're going to put your money and what you're going to do next, automated testing is just yeah, that's.

Nick:

I would put my money on that yeah, oh for sure, and and like not only just the data and the usability, but security, pen testing. I see if you, if you have a security, if you're in it and security right now, I mean you know start, start looking for mansions and yachts, because I think this is going to be such a, such a I wish I understand, I wish I understand security, I wish I know, security.

Ulrikke:

I would be so rich.

Nick:

Yeah, yeah, but I can. I can also see it being a pretty uh high stress job as well, Um so, saying I don't handle stress, I don't know.

Ulrikke:

I'm just kidding, all right. So, um, trying to jump a little bit around here to see so that we both have things in here, but I think we can just talk to all of us both of us. So I looked at a few AI things that inspired me this month by Charles Numana. Every month now he comes out with a new article about things he is inspired by, and this time it was very much about A2A framework from Google that allows you agent to agent interaction. Yeah, did you read anything about this?

Nick:

I didn't. I didn't go too too deep into that, but I've heard a few things. It's sort of, but it, I mean it makes sense right, like industry standards, like USB-C, I think, is the analogy they're using a lot with MCP. I mean, at our house we're primarily in terms of our phones. We are an Apple house and I know there's this whole Android versus Apple. But now we're in the transition of some of us in our house are still using the lightning cables. We got new iPads that use usbc. I know we're merging to usbc, but it's just sort of like you have all these different cables and connectors on just your mobile devices. But now but that's what I like to see with these agents and the um, the whole these frameworks is yeah, now we can actually connect things together a lot more easier and use use the right, right tool for the right job. If Google's got something that works better than Microsoft, well, why don't we use the Google piece? But we can still use our other Microsoft pieces as well.

Ulrikke:

Right, and so this is much larger than just different partners partnering up. So what Google has launched is an A2a agent to agent framework that everyone can use, and I think this is also talking to just what you said. You know, the um, uh, dvd, uh or the. You know it wouldn't be so many places where you had to choose what to do, angler, react right, and then someone wins at the end. But actually this is really quick because google was on the ball and they said well, we got this framework, everyone subscribed to it overnight. It seems Everyone's embracing it.

Ulrikke:

And now, with MCP servers. So just to kind of explain to people how this scenario enables us to do is that now, from Copilot Studio, you can create an agent with an MCP server that can connect to anything. So it's a connection hub that allows you to connect to anything you want, to anything. So it's a connection hub that allows you to connect to anything you want. You can then have an agent to agent connection that allows you to connect your agent to other agents on other services or providers. And now look at MasterCard is now also released an agent API which allows you to perform credit card transactions. So actually now you can potentially create the agent that in you says you know what I want to go on, all expenses paid a weekend or week somewhere. Just give me this travel, just book everything for me travel. And it can actually go through and do it, because up until this point we haven't been able to do the transactions yet. But now, with mcp and a to a framework, we can amazing scary.

Ulrikke:

Yeah, I'm not sure would you do it?

Nick:

no, I would not hand over my credit card to ai. I say that this week, maybe next week would be different um, because I do. I do do a lot of my own travel planning and everything like that and I'll um, I mean, maybe this is a talk about the travel and I'm not this. This goes away from the a to a framework of the mcp stuff. But just for for quick, I did actually co-pilot said go through my emails, find my hotel reservations, my flight, and give me a travel sheet. I always do a travel sheet to stick on the fridge so my family knows where to find me. And it went out and did it almost perfectly and it just blew me. It took me five seconds as opposed to the 20 minutes that normally takes me.

Ulrikke:

So yeah, and I think also this is from when I say, oh, do you want to just have a simple prompt and have it pay for you? Of course it wouldn't, but I'm planning an interrail trip down through Europe with my kids this summer. Right, and I've given it so many instructions and we had a very good conversation where it's still not. You know me and Chatipiti, this is still not finished with the planning, but I've told it. I want to go see cities that are, um, that are friendly towards tourism but not tourist destinations. I would like to sleep at hotels with three stars, not above this rate. Once we have that in place, I honestly I don't think I would have any reservation. Saying this is my hotelscom credentials Feel free to make bookings fully refundable on my behalf and send me back the full travel artillery. Give me the plane, the train ticket I would need for me and my kids to go from oslo to whatever destinations we planned and show me what that price is and book me a full, refundable ticket that I would actually be comfortable with.

Nick:

Strangely, right, yes, because you've given it the framework and the guardrails, the government, you've given it the governance around that. So, yeah, I'd be on board with that for sure.

Ulrikke:

Yeah yeah, and that's what we need to do with everything you know.

Nick:

I mean yeah, yeah, well, it's, it's very important but it's the same as handing your credit card over. If you have a, an executive assistant kind of thing, right, book be my flights, or I used to let, I mean. But what scares me is because maybe it's a little bit I had a project once. I had to fly to Winnipeg from Ottawa. For those of you who live in Canada, winnipeg to Ottawa would probably be like a two hour direct flight basically. But my customer just said, oh, we'll book your flights for you. Yeah, sure, just let me know. And to save money, they put me on a milk run. I went from Ottawa to Toronto, to Thunder Bay, to Sault Ste Marie, to Winnipeg. It took me all day to do a two hour flight. So after that I'm like, no, no, I'm going to, I book my own, my own travel. Um, so, yeah, if an AI, if an AI agent did that to me and, like you know, all over the place, then I'd have trust issues, which I still do. But if I give it the parameters and this is what you said, I kind of did a similar thing gave it parameters, I want direct flights, I want this, give me like, actually give me the links of what's available, and then, yeah, it's amazing and you can feed it different and it even sees. If you watch the reasoning in ChatGPT on one of the models, you can see it thinking it said okay, checking kayakcom, checking Expedia, checking this site, it's going through. It's basically doing what I would do, but it's doing it. So yeah, but, yeah, looking forward. So we'll hear an episode after the summer how your adventure went, when you end up with your kids somewhere in a country in south in africa we never heard of before, but you know you had a good time yeah, maybe, maybe I'll discover a new continent, who knows?

Nick:

yeah, um copilot sure does.

Ulrikke:

But have you seen, because I love it when it kind of talks about our conversation in third person. When you go use the one of the reasoning models and then you ask it something, it has to go out and think and then send it a little box up here when it says so she asked you to, so you now have to do, and it has a conversation with itself about our conversation in third person, and then that disappears and then suddenly it gives me my answer back and I go um, who are you talking to? Who are you? Yeah, who are you?

Ulrikke:

But of course that's orchestration, right. That's when you see the transparency into the agent to agent capabilities, because you have one agent or one set of one model which is really good at this and you have another model where it's really good at this and it's using the different models and it has to have an interaction between them into the chat experience that I'm having. So it's kind of keeping track of what it's doing on our behalf and then it's coming back with something. So I just love seeing that and I love how much more transparency there is now, yes, compared to what it used to be and I think that calm us, gives us like, alleviate some of those trust issues.

Nick:

So it's like, okay, it is doing, it is following the same path I would, or oh, I didn't realize that this site existed and it's doing it. But yeah, it is kind of weird seeing that thing talk to itself as it's figuring something out, but again, it's watching a genius at work, I suppose.

Ulrikke:

Yeah, yeah, you're not wrong. So just to close this A2A protocol and MCP stuff off, this week Carlson and Mona actually announced that Coppola Studio and AI Foundry will now support A2A, building on the MCP support we announced earlier this spring. So if you have a requirement regarding that, please check that out. We'll put links in the show notes. And to close off the whole AI co-pilot 40 minutes rants you've had so far, we have a post on LinkedIn from Thomas Vander Ward. Is it Ward or Ward?

Nick:

I would say, thomas van der Waals.

Ulrikke:

Ward yeah, okay, fast. Yeah, sorry my mistake. Should Coppola Studio replace Power Art Mate or stay in its own lane?

Nick:

It depends.

Ulrikke:

Ah, chicken, chicken. Oh, you don't want. Bark, bark, bark, bark, bark, bark. Oh, you don't want to go there, do you? It's a really weird post. Have you seen it? Because it's just putting. It's very long, there's few words, like a poem. Yeah, it's like a poem, but it's also. It resonated with me because I think that's what my mind does when I think about these things. It's like cause, you go from one thing to another and then you go back and then you move forward, and then you go to the left and then to the right, and then suddenly you go oh, I landed where I started. Yeah, so it's, it's fun. I love seeing posts like this. It kind of makes you think should it, should it not? And I can't say either way at this point, can't.

Nick:

No, but I think it kind of goes back to a little bit what we talked about last week with Anna's post and her flowchart of. You know, do you use an agent, an automation, or you just keep doing things manually, and then I mean I find those are really helpful. And I mean I find those are really helpful, but again, with all these other tools and stuff, I think it's going to blend together where like even I did a post on it was basically power automate but I used AI builder processes. It wasn't calling an agent per se, it was using AI, but that might be part of it. We're building power automate but we might be calling agents as part of that, or the agents are calling uh, power automate flow. So that's still part of our structured processing, but we still can incorporate other agentic you know uh ideas into this. So my answer would be it's going to be both. I think it's going to merge into one thing down the road, but who's who knows.

Ulrikke:

I think you're right, because I think there is specificity needed in some processes where you can't allow the LLM to go free. The generative AI cannot just work on probability, which which it is doing, so you need to be specific enough. And it has has to do with security, has to do with I don't know GDPR, sensitive things. Right, you need to make sure that it's doing it correctly, so that's when you're going to need it, and then for other things, you can allow it to just roam free, right, so you want to move on to the rest of the things, because there are other things happening in the tech realm around Power platform that does not necessarily touch on AI. Right, you want to go with one of yours first.

Nick:

Do I have anything? Oh yeah, I do.

Ulrikke:

Yeah, this was a quick?

Nick:

Yeah, yeah, I do. Actually. This was a quick little one that actually it stood out because I was working with. For those of you who do PowerPages or do other development, you probably played with FetchXML before and FetchXML is the querying tool that's part of Dataverse. It's been part of CRM forever. We all talked about how I was there at this. You know the invention of the internet and all that other fun stuff but it was interesting because I was using FetchXML Builder from our tool from Jonas Rapp, which of course we all should have installed and we use every day. But then there was a whole bunch of new.

Ulrikke:

You can pay for it.

Nick:

Yes, please donate, um. But then there was a whole bunch of new pay for yes, please donate, uh, buy, buy, yonas a beer or more, um so, but it was interesting. There was a whole bunch of new link options which I know were added to fetch xml, but I didn't really pay much attention to these. But then it came into a case of okay, I do need to do some inner and outer loops, but it has these other functions like there's any, there's not any, not all exists. Match first row using cross supply. I'm like, what are these? I've never knew what these were before. And then, thankfully, there was a post on LinkedIn, um, by, uh, someone I've not heard of before, but hopefully again, uh, more contents coming from Pranjal Tiwari and Pranjal.

Nick:

Thank you for this post. It was really well written. Basically, he gave a table of the different link type options in FetchXML and then basically broke it down and gave Kind of applied it to a little bit of how SQL works, which is something way in my background. So it was really interesting. So it's a great post. If you're trying to wrap your head around these new FetchXML or new, they might have been there for months, I just never really noticed it before. But if you're learning fetch xml and you need to make fetch xml dance a little bit, because sometimes you do run into, you do run into boundaries or some edge cases when you're, especially when you're linking other entities, this could probably really get you out of a jam. So so, yeah, thanks, pranjal, for this post.

Ulrikke:

And I don't think, I don't think even months cut it. I think this is years and all time old, because I've had to, the way that I've approached this, as if I'm, in fact, xml builder and I don't get the results that I need. I just play with that, I just go through the list until it gives me what I was expecting to give. And then I was like, oh, so, this is an inner Okay, but enter in there and so, and then it works. I have no idea why. And so this was just so insightful. I'm like, oh, oh, of course, oh, yeah, now I get, oh right, light bulb moments. Still have those. And in another light bulb moment, actually, because I saw something, um, that was really weird, so, or not really weird, okay, so in the red cross project, we have something where you have an activity board and then, uh, you, there's a, a set set of roles that you can, um, fill, right, so I'm putting on an activity, I need three activity leaders, I need four volunteers, I need da-da-da-da, and then, as a volunteer, you can go in and you can grab one of those jobs or roles. Now, in PowerPages, imagine, and of course, a flow kicks off and then there's a web API and we do some and we kind of just put that volunteer on that spot and then that's filled. But imagine two people doing it at exactly the same time. And we've had that, of course, up and we've talked to our PO about it and he said, well, actually this is not enough of a real thing for us. It's not that high usage of these, so we're going to leave it for now. We're going to revisit it later. And then I talked to a friend of mine, scott Durow, a friend of ours, and we talked about Now, we're going to revisit it later. And then I talked to a friend of mine, scott Durow, a friend of ours, and we talked about transactions, and transactions is because I'm not a pro developer. I'm like, yeah, this doesn't. And then we left it.

Ulrikke:

And then suddenly there's a video where Scott goes through the principles and the theory behind it. It's a bit you know, videos from Scott usually kind of snappy and you have the, but this is a bit more low key, it's slower music, a little bit of low key. It actually kind of affords you to learn deep learning. It talks about acid tests, so atomicity. If one thing fails, then everything rolls back Consistency, consistency, isolation and durability, so that a transaction can put a lock on something so that the second one has to wait.

Ulrikke:

And it goes through everything from kind of the theory how it works in practice, how you do this with dataverse, and also from the power pages perspective of how that would work so that you wouldn't have two people booking the same ticket at the same time, kind of scenario, and it was really insightful. So very good video. And then also the day after I went through that video, I saw a broad post from Kalash Ramchandran which was handling transaction errors in dataverse plugins. So, having that video and that theory from Scott, when I read this blog post, I would not have understood a single thing about this if I didn't have that knowledge fresh in the back of my head of how you can now use transactions In plugins. You have that ability to handle transactions and how you manage errors, to kind of alert. If you have two things going on at the same time and one fails, then you roll the whole thing back.

Nick:

So it has examples of good bad practices and good best practices for how to do that in a plugin, um, which is really really cool and insightful now that I understand more of it, um, so yeah two very good resources for you guys to check out yeah, this problem came up to me a few years ago because this was before the invention of auto number, like the auto number field in in tables and dataverse, because we used to there's things we always used to, you know, want to auto number things and there was a time where the only auto numbers that were available out of the box were for like invoices, quotes and orders Everything else. You had to build your own auto number. So you think, oh, no problem, I'll just create a classic workflow that just increments the number and pulls from a table. But then you realize you have multiple people that are putting in like let's say, event registrations, for example, registration 001, 02. You have multiple people doing that. Or, even worse, from a PowerPages site where multiple people are registering, you end up with duplicates out the yin yang that are using the exact same number, and it's crazy.

Nick:

So I remember we developed a plugin to try to get around this and even then it wasn't a hundred percent bulletproof, because at that time the idea of transactions really wasn't built into plugins, so it was just sort of like okay, how do we get around this? And of course you start dealing with people that have an sql background in sql. This was something that's been there since day one, like going back into the 90s of doing locks on tables and things like that. So you talk to developer, we'll just use a sequel lock. Well, we yeah exactly.

Nick:

We can't because we don't have we can't, we can't do that, we don't have that ability. So so, now that this is, you know, 10 years too late, but at least it's there, now going forward, um, because, yeah, yeah sorry yeah, so but. But basically, yeah, like. But to me when I, as soon as I saw that, I'm like oh, we can finally solve that auto number problem from 10 years ago, which is no longer a problem because we have auto number fields now.

Ulrikke:

But also you have to recognize the opposite, because what Dataverse is actually really good at is doing multiple things at once. That means it scales and it's performant and it can handle so many work load at the same time. So it's one of those things where sure you had that in SQL 10 years ago. But then look at what you know Dataverse is really good at. So it's always a trade-off and I think that's going back to what you said earlier. It depends. It depends on your use case, it depends on what you're building, it depends on what is the most critical thing for you and also the skill set and the ecosystem and everything you have to put. Take everything into account, um to find the right solution right?

Nick:

Yes, yes.

Ulrikke:

All right, so we're closing it on the hour now, um, but we have a few other things we want to discuss, so, um, let's just um talk about. Can I talk about one thing please?

Nick:

It's half your show. You talk about whatever you want.

Ulrikke:

So you know the thing we talked about from the release wave, where you can trace one flow from start to finish and you can see all the child flows and all the other things that are related to it.

Nick:

I want to let everybody know before we started recording, odrika said she had a monster and something else, so, but I know what you're talking.

Ulrikke:

The thing is not something else, but it's now live and I tried it out and it's just, I just, I just wanna. I almost cried when I saw it. It was so beautiful. You just go in through this interface and it's the generate process maps for multi-flow automations. You go in through the interface, you choose a starting flow and AI goes through and it maps out all the things that this flow is related to. It tells you the child flows, it tells you other flows that are updating the same thing and it gives you a visual map where you can follow from one end to the other. I mean, come on, it's so beautiful and I shared them to the whole team and they went crazy. It was, it's so good, it's funny because I love it.

Nick:

It was popping up in my teams, which I know was well out of your regular working hours, and then you were just sort of like look at this, look at this, look at this. So I was like okay. And then I looked and like okay, that is cool.

Ulrikke:

That is so cool and it's so helpful. Imagine the documentation, just having that visual where you can see things from end to end. Oh, I know, as a note in your documentation. I mean, it's just a lifesaver. And then it includes a whole whack of other things you can see at the same time. And also I dove into the uh, the um automation center, which allows you to see across your, in your environment, all the flows that fail and what kind of capacity and all this, all these things. You get an automation center now, which is is just beautiful. I love it. I just had to talk about that.

Nick:

Yep, cool, all right, going through, okay. So there's a Trying to think. What else is there? Oh yeah, another interesting small little thing, our friend Michael Roth from Germany. Hey, mike, how's it going? Roth, from Germany? Hey Mike, how's it going?

Nick:

We'll talk about turning managed to unmanaged in terms of environments. And it's interesting because, as I was putting my presentation together for DynamicsCon about Power Platform Pipelines, you need managed environments and I thought I should put a slide of what that means and I never considered turning it on. Do you really want to turn it off? Because of course, it gives you a lot more features and functionality. The caveat to that is all the users that are part of that environment need to have the premium licenses which I think in a lot of our cases. In enterprise projects, that's not a problem because they have those premium licenses, but from other projects, where they don't, they're using the per app license or a lower level of licensing. Then you don't have access to those managed features and you might not need them. That's fine.

Nick:

But then how do you flip an environment from managed to unmanaged? And if someone just asked me, I would have just assumed oh, just go in and unclick the button you did to turn it on. But that's not the case. I didn't know that. And Michael goes through how to use PowerShell to go through and flip your managed environment back to unmanaged. It was a question he got. He did the research, he shared with the community. This again is another example of sharing, saving keystrokes. If one person has that question, probably 100 other people have that question and by answering it once in a blog post like this, you've answered it. Everybody else and um, and we learned something I didn't know. So thanks, michael, for that post yeah, 100.

Ulrikke:

I love this so easy and so, uh, something you didn't know, you didn't know yeah very cool. So do you want to close this off with one of the last ones here? Do you want to go directly to the events?

Nick:

um, yeah, uh, yeah. This is um, yeah. So I did a, I did a podcast. So there's about three things I really want to touch on here briefly. I did a podcast with griffin lichfeldt, um which you have the link.

Nick:

There was, uh, definitely a lot more personal to me than a lot of the other talks I am leading into a talk at Dynamics Minds in two, three weeks, two weeks, two and a half weeks about burnout and powerlifting and mental health. So I did talk quite a bit about a burnout that I had in the past. We did see a link from one of our friends and I did ask for permission if we could share this. This is from Rebecca Albers, who's a great friend of both of ours, a really great lady. But she just basically kind of laid out the line, said I've taken on too much, I need to scale back.

Nick:

So it goes to show it's if you're feeling overwhelmed or you're feeling burnt out in the community. You're not the only one. I think all of us at some point will have felt different levels of that. So there's no reason to not feel bad about it or feel ashamed about that or anything. It's something we all go through and, again, this is where we as a community can definitely help each other out as well, and sometimes it's just sharing your stories and just knowing you're not the only one. And what are some of your coping mechanisms to work through this, and it's sometimes the best medicine is just to take a step back.

Nick:

You don't need to go to every event, you don't need to post a video every day or do a blog post every week, um, and it is a lot of work. There's certain things like, like I said, what I do for me is is just being in the gym, um, working out. For me, it's my mental release and mental help. It just keeps my mind settled, allows me to focus. So, with that session, with what Rebecca posted and with the talk with Griffin Lickfield as well, these things all kind of came together, sort of sharing a bit of my story if you're interested. But again, if you do want to talk about this, whatever, reach out to friends or, yeah, come talk to me at some of the events. Speaking of overdoing it, I am going to a whole crap load of events in the next four and five weeks, but my dad always say do what I say, not what I do.

Ulrikke:

Yeah, exactly, but yeah because we don't lead the way on this one.

Nick:

Definitely not so. But anyways, yeah, I didn't, I didn't want to kind of close out on that. Despite all of this stuff, the, the you know, all this tsunami of AI information, trying to figure out our way, everything like that, we do, we do have a support, we do have a support community around us.

Ulrikke:

So definitely there's take advantage of it yeah, and if anyone ever needs to talk about anything, we're here and we're not that different in private that we are, because we're very much what we're like here. So, uh, just reach out if you need to chat. And also we recognize especially new mvps. There are some groups in our community that we pay extra attention to and young mvps is one of them where we know that the first year is usually when people find it the hardest and people crash. So we do really recognize that as well.

Ulrikke:

Talks about how to survive a conference as an introvert, because I think that actually fits very well into one to the to this, where she talks about what it's like to be an introvert at events like this and actually a lot of good ways you can. You know actual things you can apply to manage it, if that applies to you. So, so things like it's not just pick your social moments, divide and conquer, plan your energy, not just your sessions, and also it's okay to say that you need space. Don't apologize for that. You're not the only one, and we know a lot of people in our community that are introverts as well as extroverts. I mean, I think it's kind of half and half and you have someone who's both in the middle. So I mean, if you don't feel like social settings fill you with energy but it costs you more energy than it gives. Maybe you're an introvert and that's okay, as long as you're aware of it and you know how to handle it, so that you have a great experience and everyone else has a great experience.

Nick:

Yeah, absolutely yeah, and yeah, and thanks for bringing that link back up, cause that was at the top there, but it is. That's the thing you go in and you don't have to go to every single session. That's fine, like, go to the ones you want to do, or like, you know what we do and we're at it, we're at events together, we, we, we actually divide and we kind of we bring it together. Sometimes we do a podcast on that. We hope to do that again, uh, soon.

Nick:

But again it's like and a lot of these, uh, here's a here's a secret a lot of these sessions will actually be repeated at other events. So if you miss, you know, uh, someone's session at a particular event and you know they're going to be at another one, chances are they're going to be doing very similar or the same session again. So you don't, you know. So there's a lot there. But just yeah, conferences can be overwhelming by day three. Of course, your head is buzzing with new ideas, but you could also be okay, I'm done with people for a few days. I know I get like that, yeah, so yeah.

Ulrikke:

Yeah, and also usually conferences will share the side decks for all the sessions afterwards. So as an attendee, even though you didn't see the session, you probably get access to the side deck. So that's also a way to spread your knowledge. And a little other secret that we can share is that you don't see it, but all of us sneak out and all of us take time. I know so many people in the community I know more people that do that than people that don't. Usually you won't see every one of us the whole day, just don't because everyone's at sessions. You don't realize who takes time to go at the expo hall for a bit of peace and quiet during sessions, for instance a very good way to or stay in a very good conversation. Just skip a session, stay in that conversation and have that good connection instead. It's so important. Um, and yeah, just do what you need to do to get it.

Nick:

We have a whole list of events, but I mean, we, we do that and these are all available. But we do want to call out for the European Power Platform Conference, um, to use boost as a discount code. So if you've not got your ticket yet, um, Ella reached out to ask us to kind of say hey, there's a, we have a, we have a discount code for you guys. I forget what it was, Um, I don't know. Maybe I don't know, I had it somewhere, Sorry.

Ulrikke:

Um, I thought we put it in the show notes. Let's put it like that Perfect.

Nick:

Yeah.

Ulrikke:

And also, our next episode is going to be May 28th, and yeah, isn't that right?

Nick:

Yikes Already. The end of May, yes, and that is going to be. I'm going to be at Dynamics Mines that day. So again sneaking yeah, people sneak out to take a break. I'm going to sneak out dynamics mines that day. So again sneaky yeah, people sneak out to take a break. I'm going to sneak out and record a podcast episode. I'm not presenting that day, so it works out good. So, yeah, I'll be able to kind of report from the field, so to speak.

Ulrikke:

Sounds awesome.

Nick:

Cool, all right. So I think everybody's brain is melted by this point, or hope. Your commute was good, your drive was good, your gym session was good, your walk was good. Thank you for allowing us to, uh, be part of the conversation, um, and some of the conversations you're probably having with your colleagues and friends all about this wonderful world of technology and AI that we live in.

Ulrikke:

Thank you so much for listening and we'll talk to you next time.

Nick:

Thank you for listening. If you liked this episode, please make sure you share it with your friends and colleagues in the community and be sure to leave a rating or a review on your favorite streaming service. That makes it easier for others to find us. Follow us on social platforms and make sure you don't miss a single episode. Thank you for listening to the Power Platform Boost podcast with your hosts, Luric Akebek and Nick Dolman. See you next time for your timely boost of Power Platform news and updates. Hey.

People on this episode

Head Shot

Nick Doelman

Host
Head Shot

Ulrikke Akerbæk

Host