Power Platform Boost Podcast

Rubber Ducks

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

Share episode
Nick:

sometimes he would just call me in a team's meeting and like Nick Nick, I need you to look at something Like okay, donovan, sure, and we'd hop on a team's call. I'm doing this code, I'm doing this, I'm doing this, okay, I need to move this. Like, oh man, that's not working Okay. And then boom, oh, it's working. Thanks so much, and I'm like Don, you're a perfect rubber duck.

Ulrikke:

And of course, it goes back to coding about talking your problems or talking through yourself when you're actually talking to a rubber duck. 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 Akerbeck.

Nick:

Good morning.

Ulrikke:

Good morning. Good morning for both of us.

Nick:

Yeah.

Ulrikke:

Yeah, because you're here or not here, here, but they're here.

Nick:

Yes, I'm in the same time zone. I'm actually in Oslo today, yeah. After a week of vacation and then before that, dynamics Minds. So yeah, a week week of vacation and then before that, dynamics mind. So yeah, it's uh. Well, you wake up some mornings and you're like where, where am I again?

Ulrikke:

so we've been in the same time zone for like a month already, or something about three weeks probably, more or less yeah, that's really cool.

Ulrikke:

And then this week I'm gonna see you a little bit and then we're going off to Vienna next week. So I'm going to see a lot the next few weeks. I'm so excited about that. Very good. So tell us about a little bit, about Dynamics Minds and your trip, because Dynamics Minds is like for those of you who don't know, I've never been and everyone's like, oh, it's the event, right, you just I can't believe you have it. If you want to prioritize anything, you have to go to dynamics mind. So tell me why. What is so special about it?

Nick:

yeah, it's, it's strange, right, because it's like I went for the first time last year and I went again this year and again, nothing against the other user groups and community conferences and everything else. They're great. There's just something about this one and if I was, actually, if I had to pick and it'd be a very hard choice, but I would actually if I had to pick just one to go to, this would be the one I would go to, and I think it's because there's a couple reasons which makes it special. First off, it's in terms of a carpet. It's bigger than your typical Saturday user group but it's not massive like a like a power platform community conference in Vegas where there's like 10,000 people. I think they have 1000 to 1200 people, if I were to guess, in terms of attendees, of course, a lot of speakers there. So of course, the content is great. I think, as much as the content is very similar to what you see, they also try to put a special spin on it. There is a whole theme around it, kind of a Tim Burton-ish kind of wizard theme around that as well. The keynote, which is usually they open a conference at a keynote. They do the keynote at the end of the opening day and it was really interesting. It's more than just your average Microsoft VP coming out and telling everybody here drink the Kool-Aid. It's awesome.

Nick:

They had this whole little dramatic play thing. It's hard to describe, uh, I'll call it a, a theater piece of sorts. And last year it was. It was all about co-pilots, right. So they had one uh actor come up.

Nick:

She was the co-pilot and she gathered her other co-pilot friends and they were a musician group and they kind of did a band and they kind of themed around that this year she's not a co-pilot, she was an agent and they talked about the. They kind of did a band and they kind of themed around that this year she's not a co-pilot, she was an agent and they talked about the um kind of factory or warehouse of the future. And of course it had all these uh people sort of dressed up in kind of worker factory clothes, but they were agents and they were doing different themes and different little like numbers like that and of course, and then, um, it was donna sarkar and Chris Huntingford. They were kind of the, the, the main people at the keynote. So they, they talked to theirs, they kind of worked their way around through this whole scene. I really can't do it justice to explain it, so I'm just telling you you have to go and see these things.

Ulrikke:

Yeah, it's one of those things that you had to be there, kind of experiences, right.

Nick:

Absolutely so. In terms of keynote, it's definitely there's nothing like it. So, in terms of the conference itself, a couple of things, I think you have going for it. The social events is it's all your first off, you're in a hotel in Porto Ros in Slovenia which you can't just fly into, and 20 minutes later you're there at the venue. You have to fly into some surrounding cities and it's about a two-hour shuttle ride to get to the actual venue. So it's hard a little bit there's. I would say it's hard, it's not. It's not hard to get there, it's just you have to plan to get there and you have to plan to go home.

Nick:

Around that, and the organizers, in terms of the speakers, are really good at organizing the shuttles and if, if you're an attendee, they have a lot of great information how to get in, how to get out, and then, of course, you're in the hotel. There's two or three big hotels sort of attached to each other, so everybody's there on site and then they have the big social events down by the beach. They have these every night, with lots of food, lots of entertainment, and it gives you an opportunity to interact and chat with everybody and just sort of get to know everybody a lot better. One of Donna's sort of you know, donna gives homework all the time in the conferences. She sort of said, okay, make new friends this week and definitely I definitely made brand new friends and strengthened some other friendships as well. So in that respect it was really good. And and then, yeah, just overall, it has more of a festival feel to it than maybe like a corporate conference or some of these other conferences.

Nick:

Um, and then at the end of the day, of course, everybody as opposed to everybody scattering doing their own thing everybody instead gathers, uh at these, at sort of these beach parties and sort of kind of you know, reflects on the day of course, celebrates and related that where. So I think that really helps as well. And then, yeah, just in terms of the venue, all the rooms are, all the breakout rooms, more or less, are close to each other, with a couple of exceptions, of course. Those are just venue things. But yeah, I absolutely, truly enjoyed myself.

Nick:

Definitely I'm going to go back again next year. It doesn't conflict with any power lifting things, although it's happening before the, the, the next year's bench press championship, like the week before, so that might make things a little bit more interesting. We'll see, let's. Let's revisit that in a year to see where I'm at. But anyways, yeah, I would highly recommend, if you have the opportunity, to go to Dynamic Spine. It's definitely worth the money. Like I said, not taking away from any of the other events that we go to, but this one to me is there's something special about it.

Ulrikke:

So did you check out the gym this year so that you know that you'll be able to go before the next? They have a good gym.

Nick:

Oh no, they don't. Oh, okay, we didn't, yeah, so we'll have to. We'll have to figure out a few things around there. So, like again, that's a, that's a whole lot of it. Lots can happen between now and then. But they did but they did announce that they were having it again. They did announce the dates, which I don't have in front of me, but it's roughly about the same time next year, I think, around May 26th, 27th week. So definitely put that on your calendars and come check that out.

Ulrikke:

I'm actually going to check because I asked a few friends who were there to send me. If they announce the dates, send it to me so that I can put it in my calendar right away. And they said May 25th to 27th the 2026.

Ulrikke:

And that's of course, the day after my birthday. So that's going to be um same thing as as this year. I'm going to go, I put it in my calendar already and I'm going to make sure not to miss it. And I think also, if you talk to Mira, she may, she's able to fix absolutely anything. So if you ask her to kind of ramp up the gym facilities, I'm sure she can handle that.

Ulrikke:

But I recognize the same thing, as you said, because you know, acdc is one of those events where there is really no place to go right. So everyone's at the same place, at the same hotel for a few days in a row and it's so far away from the Oslo city center that no one really goes to the city. Everyone stays at the same place. And I think that's one of the key things that has made that event so popular is that it creates a very intimate feeling because you know that everyone's going to be at the same place for for a consecutive number of days. It creates a special vibe that I think you don't get anywhere else. So it's going to be very interesting to see if that kind of creates, if it's kind of the same mechanisms at play, and I'm really looking forward to going next year.

Ulrikke:

So that's, uh, yeah, definitely cool, all right. So, uh, you had a refreshing week and then, because you had a few sessions, um, and then you went on holiday and now we're ready for a week of work and then a week of EPBC. So that's going to be fun. Yep, you want to dive into the news? The first news item here is you, and a good friend of ours has repurposed old content in new ways.

Nick:

Yeah, but it's interesting because Steve was at Dynam, at dynamics mind, so he had a chance to chat with him a little bit here and there. Um, steve's steve's a good like, he's one of my favorite people just in terms of his attitude and it's sort of like just it's really refreshing, like it's brutally honest, um, but in a good way. And him and mark smith and george Dubinsky and Yuka Njernan did a panel and it was four bold guys talking shit and I was in a front row seat you actually had to be because you just didn't know what was going to come up and it was interesting them talking and agreeing and disagreeing those types of things. And Steve did mention that. He said oh, he says I have have a followup blog post to my mountain of shitty little apps that he did last year. He said a mountain of shitty little agents. And, um, basically talking about, uh, again, where everybody's building apps last year and, of course, how many were used, and talk about the citizen developer. Well now, the citizen developer? Well, now we're saying you know, the pitch from Microsoft is anybody can build an agent, so people are going through building all of these agents. Now, if you build an app and you don't use it or you use it for yourself and it screws up a few things. That's one thing. But then, all of a sudden, now, if you have everybody building agents going out, automating, doing things, what kind of chaos is this going to cause? So, I think, in terms of this new era of AI and agentification and everything, governance is going to be such an important aspect to this in the guardrails, and this is what a lot of people are working through.

Nick:

But basically, steve is very pro-AI. He actually is developing code, believe it or not. He's vibe coding. He says he's not necessarily building enterprise apps, but he's still building apps for himself, but also recognizes that we do need some professional. Again, this is business software. It does need some guardrails and things like that. So, read through his post. He talks about the different things and, of course, as Steve can do it, he's been posting a lot in terms of different things around ai, a lot of stirring the pot. That's what steve does, but I think also he does a very good job at creating conversations that we all should be having as we go through this. This, this whole ai process um, that I've been you and I have been talking about, I've been talking about with other people as well, how we're trying to figure, figure all of this stuff out. So it's good to keep these these types of conversations going, yeah.

Ulrikke:

And I think he's poking at something that is not talked about enough is that when everyone creates their own little cause, we're taught. This is what we're taught in the the future you're going to be surrounded by your colleagues is going to be agents. They're all going to be autonomous and then um, and then you're going to have the orchestrator kind of that is your interface in into the workforce of agents. But how does that then work with my set of agents? Work with your set of agents? Are they the same? Do we have the same job? Did they kind of stumble into each other saying how many overlapping agents do we have with the same knowledge? How many? How do you? There's so many questions here and you know how do you do environment and solution strategy around this. What is production really? And there are so many questions now that we haven't really kind of gotten our heads wrapped around yet. So I think the traditional sense of all this is production and this is our pipeline and these I don't know.

Ulrikke:

It seems to me like it's going to be more of an organic environment where you have your environment and, of course, you have to draw on the same data, but because these agents are autonomous and they can connect to anything, it doesn't really matter where the production data is. So maybe we're in a solution where we have production environment in terms of data, or we have different production instances of data scattered around and then all the agents simply have access to those production environments, data sources and pull into my environment and for you to your environment. But then, looking at so I mean, I think we have to rethink what that looks like in terms of our linear production line type thinking won't, probably won't work in the future. So who then has the insight and the kind of the, of the, the privilege or the you know, permissions enough to see all of this holistically right?

Nick:

yeah, well, yeah, that's interesting because this is where we start talking about mcp servers like agents talking to others, things like that. Now, one analogy that I sort of I came up with and I talked about and I don't think I talked about it in the last episode, but I know I talked to a few people at Dynamics Minds about this concept Um, and if you've I don't know if you've ever read the book the seven habits of highly effective people by Stephen Covey, one of the habits is, um, begin with the end in mind. So when we were transitioning servers on-prem servers to the cloud 10 years ago roughly, we knew what the end in mind was. The end in mind was basically that we're going to be using software but we're going to access it through the internet on our computers. We're not going to have servers anymore, the server will be in the cloud. It's almost like the same thing, but it's just sort of. This was our end in mind. We got it, we totally understood that was our end goal, end in mind.

Nick:

And then, when we talk about the citizen developer, powerapps, low code solutions, again we knew what the end in mind was. We figured, and maybe we didn't quite get there in terms of the whole concept. But Bob off the street, who does Excel very well, should be able to go in and create his own business app and deploy that, whether to himself or to his team, and then that was our end in mind. With citizen developers, yes, they can build apps, or they can build apps to a certain point. Did we get to that point? Not really. Are we using low-code tools? Absolutely, we use those every day. So, in terms of that end in mind of being able, we, as makers and developers, even low-code or or pro code or even just developers in general using that, we knew what the end in mind was. We were creating software, we knew what it was going to look like, we knew what was going to get there.

Nick:

Now we're in the term of AI and AI agents. What does it mean to be building AI agents? What does that mean To me? I have ideas, I use agents for certain things, but it's still a little fuzzy and it's still a little unclear from where we are today in terms of interacting with software to where we'll be with agents.

Nick:

I mean, I have an app, a power app, that used to be on-prem and I moved it to the cloud just to track my weekly time as a consultant. It's still an app and I'm trying to figure how would this be an agent? Am I going to have a chat bot asking me what projects I worked on this week and me just giving it some details and it going and compiling that information and creating my invoicing? Or is it just still going to? But to me, the app just works better than that experience. So, yeah, maybe there's agents in the background. Maybe there's an agent that's doing the currency conversion, like a blog post I did a few weeks ago, or how I'm going to interact with it.

Nick:

To me, I'm still typing in numbers and pressing buttons because it's easy. Maybe I'll talk to it, maybe that'll be a user interface and maybe that's where we're going. So I don't know. That's what I think is part of it. This is a phase where we don't know what the end in mind really is. Everybody has different ideas. There is no clear vision. This is what an agent will be, this is how it will look, this is what it will do, and maybe it might mean a hundred different things, and maybe that's part of the issue as well.

Ulrikke:

I don't know just my mind can kind of fire it off in 10 different directions just by that one little comment. I just five of the things I'm going to talk about in the show notes relate to what you just said, and I have my own little kind of comment on how this works. But I just want to say we're going to go into so many of the the kind of the strings that you pulled up just there, but for me it's also one of those things where I think we need to just embrace the fact that we don. So in terms of your app, if it's easy for you to type that in, then keep typing it in. I think, if anything, let's you know. Next blog post on the list Louise Freeze. Can we just get off the hype already?

Nick:

If it's a flow.

Ulrikke:

It's a flow. If it's an app, it's an app. If it works, if you're comfortable with it, it doesn't have to be an agent. Can we just kind of just take a step back and just go? Oh okay, well, off the hype, stop thinking to Kool-Aid and actually look at what it is and what it can be used for in a more sensible way, because I think we're all just riding the wave and, like she talks about LinkedIn and how it's just a big rah-rah kind of echo chamber at the moment, and I absolutely subscribe to that.

Ulrikke:

Now, also, one of the things that I saw this week was um, then I can, I can kind of just plug that in right here. It's from um. Oh, where is it? It's from, uh, from reza, uh, dorani, where he shows uh, no, sorry, another one.

Ulrikke:

Yeah, andrew, hess shows voice to text with Power Apps using ChatGPT, whisperer, which is exactly what you said. So you have a Canvas app, but you won't be able to talk to it and you send what. You use the microphone component and then you control and then Power Automate will transcribe it using Whisperer and then it will give it back to the Power App and that may be a way for you to enable voice on your Power App. Powermate will transcribe it using Whisper and then it'll give it back to the PowerApp and that may be a way for you to enable voice on your PowerApp and actually being able to. If you also then have an agent that goes and monitors your Outlook and then you're a bit more diligent in what you put into Outlook, maybe it's able to kind of scrape your calendar and give you kind of a rough draft of this is what your week looks like, and then you can maybe adjust it and maybe you can talk to it and get it to give you some insights.

Ulrikke:

But probably doesn't have to be more complicated than that. But back to my point. If it works for you, louis, that it is today, you're going to just spin your wheels trying to add smack AI on top of it, and I think a lot of us do that right now. So let's talk about Louise Fries' blog post, because it's perfect to where we're at now. It's your entry.

Nick:

Yeah, I saw this yesterday. I think she posted a few days ago, but the title of the blog post is Tired of the AI Hype Machine, where she kind of talks about like all we're sort of talking about now, about how people are. Basically, people are just sort of making these bold statements about AI will reinvent your entire industry. The companies that don't adapt will die. And here's how I use AI 10 times my thinking. And then you also see, you know the comments of people just replying AI comments back and then basically, it's just sort of like people are just sort of arguing and you see these AI experts, you know they'll kind of take it on. And she has one statement there that just jumped out at me the AI theater is exhausting, and I totally agree.

Nick:

And I think this is what's stressing people out too. It's like, okay, I should be using this thing. Um, yes, I have my time tracking app. I should be using AI, because everybody's telling me to use AI and I'm like, but how is AI going to make this better? Yeah, I can talk to it.

Nick:

Okay, that might be a little bit of an improvement, but I know, if I start talking to my phone just sort of randomly about different things. I don't know people look at me weird, or or my family kind of says what are you? Who are you talking to my phone, just sort of randomly about different things. I don't know People look at me weird, or or my family kind of says what are you? Who are you talking to? What did you want? Like no, no, I'm talking to my, I'm talking to my phone, I'm talking to my, not talking to you. So you know, this causes all these things. So I, I and again, she's into AI as well. Right, like this is, she's very much a proponent, but she even said something like stop solving imaginary problems.

Nick:

And again, this is, I think, what we're into now. It's like, okay, I need to use it, but what can I use it for? And always, apps have always been driven by I need to do this. So how could I I'm going to write an app to do this as opposed to I need something for my app to do. And I think this is where we and there are definitely things like you know, yeah To getting an email and having it. You know, update my exchange rates. That's something that makes sense to me and that was something I used AI builder for. But it's so like but you know, again, we're still yeah. Anyways, I could go on. But, great post, I love it, read it and, yeah, help. I think everybody, if we could work to tone down the AI feeder, tell the, celebrate our wins, I think, definitely share what we're building, but just sort of this other kind of hype about you're going to lose your job and this and that let's take the panic out of this. That's my partially takeaway from this too.

Ulrikke:

Yeah, yeah, no, I 100% agree, and I think apps also was one of those. Well, we need apps over data, right. So it was access to data to see it, structure it, handle it, fiddle with it. Right. To see it structure it, handle it, fiddle with it right Now. Ai if you slap AI onto stuff that it's not meant to solve, then you have a. You know it doesn't add value, but what I do see adding value is something like Project Sophia, for instance. Right.

Ulrikke:

So I've had two customer presentations last week where I talked about Project Sophia and it blows their minds. It's one of those products and I've talked about it before, and then it kind of went away for a little while and now it's really coming back up. So, if you need or if you're looking for something new to dive into, project Sophia is really hot right now, and so what it is? It's in an application where you upload your data set. It could be Dataverse, it could be SharePoint, it could be uploading an Excel file and then Project Sophia will go in and it will look through your data set and it will give you an interface based on the data that it sees. So if you update your data set, it will be different every time and they'll visualize your data for you and give you kind of an abstract or a summary, a narrative around it, and then you can also use the ai cursor to to dive more into the specific um kind of visualizations that it gives you um. So there was a linkedin post by um, by anna, who kind of just went through because she's now using Project Sophia all over the place and it was kind of a little video about how she's using it and it was really good and it kind of put it back on my radar.

Ulrikke:

And we now have two customers asking us to help them set this up and kind of also have kind of an exploratory workshop. Because now the question says, okay, you can upload a dataset, but then you have to add a prompt to it. What is it you're actually looking for? And this is a very good use case for ai, I think, because you upload a humongous data set and then you have questions. Okay, so you have a factory line. What is my weak spot? Where do we see problems where? Where do you see this going? Can you predict something? You have to have questions towards your data. It's one of those exploratory workshops where you're just looking at what kind of questions we have and also what the data set is, project Sophia is really worth looking into. And then I see we have something called New Interface for Microsoft 365 Copilot. So this is the Microsoft 365 one.

Nick:

Yeah, so this is something Lisa Lisa Crosby in her video that we mentioned, I think, on our last episode. This is sort of the build announcements and actually I basically loaded up Microsoft 365 Copilot and it had everything, all the apps moved over to the left-hand side and it kind of looks like and this is sort of what Microsoft does. It kind of looks a lot more like chat GPT now, but it has interesting things. We have now the analyst agent, which is pretty cool. I actually went through and made it so with the analyst agent. It can go through and kind of interpret data. So actually I used one of the sample prompts just to play with it about creating a table with the volume of planets and add a column to show volume and multiple of Earths. Then you know again, nothing I'm really a need to present or show to anybody. I just really wanted to see what it could do and it actually created the table. That did Python code of how it extracted the data and it showed all of this information in organized format. So if you actually again talking about, you can actually have it, look at your own files and look at different things. I don't think this is you know, kind of on the same lines of Project Sophia, but probably a little bit more ad hoc to your data to analyze.

Nick:

This Researcher was pretty cool. Researcher I'm actually. I have a business idea that I've been working with and I'm actually been using chat GPT to work on this particular project. I actually took my initial prompt, dumped it in a researcher and it asked me a bunch of questions because that was part of my prompt, to kind of interview me a little bit. But it created this actually full business plan around my idea, because it even asked me questions that I didn't think of like, oh, you know, that's kind of good, like we talked about before, it being sort of a thought partner. Um, yeah, did it do it perfectly? Would I present this business plan to a bank? Probably not. I would go through and fine-tune it a little bit more, but it did open up a lot of new, new things.

Nick:

And then, of course, there's visual creator as well, which has sort of been around before in terms of creating images. It does have the ability to create videos. Now, I haven't tried that out yet. Like I said, it just showed up the last day or two, so everything is constantly evolving. For anybody creating content, it's almost like yeah, you can't because it keeps changing all the time. But anyways, if you do have a license to the Microsoft 365 Copilot, next time you fire it up, don't be surprised.

Nick:

The interface has changed. I find the interface is a lot more usable to me. It has this concept called notebooks, which I'll probably dive into, because, because you and I were big fans of one note, I've been using one note for years. Um, I don't think this is. I don't know, is this going to replace my one note? I'm not 100 sure, uh, but it is something you know. It is sort of to work better with copilot and sort of keep track of my information. So we'll see how that evolves as well. So, yeah, take a look at that. And and maybe now people are going to get more value out of that license, which is pretty, still pretty pricey. It's about $30 per user per month, so again, it's. But yeah, maybe now I think the licensing might've changed as well. So, yeah, check, check out those new changes that they announced that build, and you gotta be able to try these for yourself yeah, 100% it's.

Ulrikke:

It's evolving so fast and I've heard people that have had private preview access to this being so blown away by the researcher, especially. That has been kind of a game changer in terms of, yeah, especially that has been kind of a game changer in terms of, uh, yeah, Prepping for meetings or kind of getting more knowledge into something. Um, it's really interesting. So, um, moving on to um, yeah, so this is the um content from Reza Durrani that I, uh that I mentioned.

Ulrikke:

He made a video about agent flows in corporate studio and how agent flows and agents kind of people are a bit confused about the differences. So what he shows is a really good use case of how to use it, how to set it up and also what the differences are. So if you think about agent being autonomous and non-deterministic meaning you give it a task, you give it resources and you give it a goal and how it kind of goes about finding out what to do is up to the agent. Agent flows is more like our item flows for you. It's deterministic, right, so it's. You do this in this in a certain sequence and you can fire off prompts if you want. You can fire off other services, but you know the order of which it will perform its tasks, so it's a very good video, I think, and you know very, very well-structured Reza. There's a new video every week and his tutorials is also really easy to follow, so a very good video, for sure.

Nick:

Yeah, I'll probably dive into that just to. I keep liking these little tutorials and stuff to, kind of sometimes yeah, yeah, it's something material I've already covered but to go back because things have changed, then you always pick up a new little tidbits. So just because you've completed a tour tutorial six months ago, sometimes it's worth your time to to take a step back. It's kind of a two-step forward, one step back approach, kind of like we're talking, we're learning, we're trying to figure all of this stuff out. I've been beginning to refer to myself as an AI pilgrim on a spiritual quest to get enlightenment. So on this pilgrimage, kind of going back and checking out new things like that, yeah, and also yeah, things just kind of sink in a little bit as well.

Ulrikke:

I think, when all of this stuff is happening so fast and there's so many new things every week, just when some kind of letting things just kind of sink in a little bit and then revisiting something, I find then I understand it better, then it gives me another context, maybe have a new few, a few hooks that they put things on. Then I understand it better. So, yeah, that's really valuable for me, I think.

Nick:

Yeah, and I know I don't have it on the list here, but we're talking about tutorials and stuff. I did go through Daniel Lakovic's MCP tutorial, dataverse tutorial, for the most part. There is a portion where you connect basically dataverse to cloud, cloud AI. I didn't do that because I needed to long story. I needed to use it, have an SMS code to activate my cloud account and I'm I have a data plan that doesn't allow us to Smith's on traveling, so I skipped over that part but got it working with visual studio code and, wow, like again, it was just one of these things that, yeah, it's a little clunky right now because you need a preview environment, everything, but I was just sort of like, wait a minute, if I can do this. This means this, this and this in terms of we talked about last time in terms of power pages, development, where we're, you know, ask it to create a fetch xml statement and we have to know the, the table values. Well, now the mcp server will actually it knows that because you can actually ask it what are the schema names for this table from a development standpoint. But also, you can like what we were talking about with using playwright in terms of data. We can get an mcp server to create test data, um, which is pretty interesting.

Nick:

And again I'm thinking integration scenarios. I'm thinking of tying Dataverse now to other systems. Again, it's going to depend on how the licensing is going to pan out, how much resources it's going to take, or is this again okay? Yeah, that's great, but we could use a data flow or something for that. But anyways, it is again one of these. If you're into some of these, the new stuff, and need to understand how MCP servers work and working with Dataverse, that actually is a really good tutorial. Just to go through those steps and get a good taste, get to a hello world situation with MCP tutorial or the MCP servers for Dataverse.

Ulrikke:

So yeah, yeah Right, very good. And then we have moving on on to some alm stuff. Actually, uh, there's a blog post of um by how dang on service accounts versus service principles and how dang do we know about, I think, the last two, two years? This has been a crazy ride for us. So this is a good blog post or a linkedin post, or kind of summarizes the differences, the similarities, when to use what yeah, yeah, and this, this isn't a new thing, this is, this is, this has been around.

Nick:

But I like, I like houdini, who goes and he keeps, he keeps giving these reminders of these things like, oh yeah, we need to know. Or because our you know, new people coming into the power platform are asking these questions like what's the difference between a service account and a service principal? And you have to think about, okay, which is which is which? Again, and why would you use one versus another? And again he talks about, yeah, using service principle as much. As what he doesn't talk about so much about the service account, but it kind of leads into this is the Outlook connector, which also I saw a post and I don't have the link here, but it looks like the Outlook connector got a bunch of new features, but what it doesn't have yet is the ability to use a service principle with the Outlook connector, which is a royal pain in the butt, especially when you start factoring MFA and all of this other fun stuff.

Nick:

So, um, but again, who didn't? I love these posts Actually. Uh, I, I have a plan to chat with who didn't a little bit later this week. Um, so I'm always looking forward to that piece. It's great to have a conversation with uh so great posts and keep these. Keep these reminders and this stuff coming along. It's a great resource for people both starting out and for people that have been around the block and keep forgetting certain things. It's good.

Ulrikke:

Yeah, and also I mean in terms of the service. So the service account thing has been very top of mind for us this week because we have now Microsoft now enforcing MFA on service users as well. So a couple of new customers has come back to saying, okay, we need to enable MFA for these, because usually when we're in development phase all the stuff is on secured environments anyway, so we haven't had MFA while we've been multiple people working on something. Now MFA is enforced and then they're like okay, so who's going to connect it? And I'm like well, you can connect one service service accounts mfa to different developer phones, because we now have the authenticator app and that seems to be something that not a lot of people know about. So you can have I don't know how many, but I know you can have. You know, I think we have three or five now connected to one account so that you know both you and me can have our phones and our authenticator app connected through mfa to the same service account, meaning that you can still have mfa enabled on those, because usually I think a lot of them don't, just because so many people use them right. So that's kind of just one little tip from from our side that it's um. Especially if you use um, the microsoft enter id, that's um.

Ulrikke:

Yeah, and also just a little plug, I uh had a little chat with how done a couple of weeks ago. Um and uh on his podcast, which where he goes in and interviews people in the platform space. Uh, that was really good conversation, really like um up with Houdang. He was also in my workshop at ColorCloud, so I'm really loving getting to know him better, and that episode is released this week, I think. So if we can get our hands on that link, we'll put it in the show notes for sure and check out all the other conversations on his podcast as well. He's so calm and easy to talk to, creates a really safe space. I really love the way that he kind of goes about his interviews and is so knowledgeable about the people that he interviews and there's really good conversations.

Nick:

I really like that yeah, I'm looking forward to my chat with him as well, um to be for the podcast, which probably will be a few weeks, because I know he batches these things as a way to do it. Yep.

Ulrikke:

But there are other news in terms of ALM, not just the service account and the service principal stuff. There is a new announcement, or the new default pipeline rules are now out of preview. So what does this mean?

Nick:

Well, did I post this? I'm not sure, because I have a.

Ulrikke:

So there's the one. There's the two things, right? So there's one link in here that is an announcement blog post by Microsoft, which is scale ALM org-wide with deployment hub, ga and the new default pipeline rule. And then also Matt Cullen-Jones published a blog post about the same default pipeline rules.

Ulrikke:

So what it means is that you can now, as an admin, go in and set default pipeline rules for environment groups, meaning, if you're a developer and you're in one of the environment, an environment group, you will have a pipeline set up by default. That is not the one that comes out of the box, which is not a private one, but is a default one that someone set up. So it will be a pipeline. And what colin, what matt, says is that, um, he wishes you could actually set an um, uh, kind of a host, not just a pipeline. That's another thing. So this is just the beginning. This is probably going to evolve, but this is a way for you, as an admin or yeah, to kind of set some rules and and create some defaults for people. Uh, so you'll have kind of specific rules that that kind of applies to all the environments in that group and it was also really automatic.

Ulrikke:

So what he really liked that he points out is that I only gave it access to one of my environments and it set everything up for me so you don't have to go in and kind of manually set everything up like you have to in the custom pipelines or custom suddenly the regular pipelines, pipelines, but yeah, so a bit more automatic. It's nice to have these rules so if you have new developer environments coming in, for instance, they will automatically be assigned to a group and that group will automatically have those pipeline rules. That makes it a little bit easier to manage and govern.

Nick:

Yeah, yeah, and it's just sort of also in terms of the deployment. The deployment hub is, you know, you're trying to find what did a particular pipeline run, when did it run from? You know, see the run history and those types of things, and that's that's also a pretty cool feature, as opposed to trying to dive in and find the, the model driven app that it's sort of. Again, it's a separate, you know, it is sort of an admin thing, uh to do deployments. So again, it's just kind of consolidating everything that the new power platform admin center.

Nick:

I, every time I go into the new power platform admin center I'm discovering new little things. Uh, I'm absolutely really enjoying. I think they've done a great job. Um, I really I probably should go and do proper reading up on it to find out everything. But it is kind of neat that they're going through and giving you recommendations and actions and, of course, managing that. And and this is one of those things where a lot of times, if a new interface comes out, you're constantly flipping the switch to go back to a particular, the classic version, this one, I haven't really, I've turned it on and in most cases I haven't had to go back to the old one. I've been able to find either the same feature or something better within the new power platform of mid center. Again, other people might have different experiences, definitely share those with us, but overall definitely liking it. And again that ties in, like the deployments, for example, we can actually monitor the deployments and see what's failed and what's passed and what's going on.

Ulrikke:

Yeah, yeah, very good insights. And I'm with you that new Power Platform Admin Center is just so. It's awesome in every way. But I'm also one of those people who, as soon as there's a new interface, toggle, I'm on it. You feel it's crap? I, I just use the old one. I'm like dude, come on, if you're working with our automate these days and you're not using the new interface, you're losing out and your productivity, even though it's buggy, is probably lacking, so just get on the new one come on to.

Nick:

To be fair, I'm more of the. I will try, as soon as something's new I'll turn it on and then probably in about two minutes, like where who moved my cheese back to the old one. But for the power automate one, I do find that I am trying to. Actually I'm using the new one, the new one, the new, the new one. It's definitely improved quite a bit over the last few months and it's definitely improved quite a bit over the last few months and it's actually, um, I'm kind of into that camp now, but I do find that a lot of places, when you're trying to do the entry points, it still will show the old interface.

Nick:

So you find yourself in that old interface if you kind of navigate through solution, through the power app solutions. So you got to remind yourself okay, I need to actually go to the power automate environment to order to get the new interface. So, just out of habit, because I spend most of my time in the Power Apps environment, I'll end up in the classic interface. So that would be something in terms of an improvement to give me at least the toggle, the switch, that I can always default to the new interface because it does have new features and things that actually are very helpful for the most part over the old one. I think it's still a few little things which will, everything in the fullness of time, oh, just get better.

Ulrikke:

Yeah, 100%. And also it's a reminder to use the right tool for the right job and go through the right interface for the right things. If you're working with power apps, use power apps. If you're working with power, automate things. If you're working with Power Apps, use Power Apps. If you're working with Power Automate, I suggest you use the beepin' Power Automate interface. What?

Nick:

if you create tables for Power Pages, what interface do you go through for that?

Ulrikke:

Oh, tables, that's Power Apps Done. It doesn't have anything to do with Power Pages whatsoever. So use Power Apps for any data modeling Done, done. Oh Jesus, don't push my buttons Right, okay, moving on to something that is going to push your buttons, because it's fucking time zones, lynn, which we love. Hi, lynn Created two or, first of all, something that caught my eye and that was Power Automate convert time zones using an expression.

Ulrikke:

This is power FX land, the coding, the mystery of time zone names and through the blog posts, in true Lynn style. And this is funny because Lynn's blog post is one of those notes to self blogs where he simply just create blog posts just so that he remembers the next time. So, and he's written it like he's written it to himself. It's just a completely. It's one of those things you get to see inside someone else's mind worlds and it's magnificent.

Ulrikke:

So when he dived into this cause, he was kind of struggling with time zones, as we all are, and he thought you know what? I'm just going to double down, I'm going to figure this out for good. And what he discovered is that the names of time zones is completely bunkers. For instance, you have two time zones for Australia, which is in it's. It is the same time zone but one adheres to daylight savings and one does not Mind blown, why do you have to make it so hard? And so he figured it out.

Ulrikke:

And then he lost me halfway because it's Flynn. But if you struggle with time zones and time zone names and trying to understand how it works, then he has a solution for you. So there you go. And also, when I scrolled down to the end of that and looked at the conclusion and everything, there you go. And also, when I scroll down to the end of that and looked at the conclusion and everything, he has three other blog posts, related kind of things. And then I saw Base64 and binary file content types in Power Automate blog posts, which saved my ass, because I'm working with a customer right now where I have to convert images to PDFs through HTML pages and then Base64 enc code them for them to show up and the preview thing at another system, and it's like and so, and I saw that and I was like, oh, that's why I haven't been able to get it to work. And then it figured it out. So then save my ass.

Nick:

Yeah, and that was a and that's a five-year-old blog post as well. So it goes. It goes to show that the older stuff is still relevant. I still get comments on stuff I've written like in 2020 or before, right. So yeah, just because the content's old doesn't mean it's wrong. Some of the stuff is timeless.

Ulrikke:

Uh-huh, uh-huh. It's an old platform, so, yeah, 100%. And talking about old technology, um, power pages has had a few announcements this week. Uh, it's now in my head, bar pages as is. He's kind of completely legacy and I don't think I'll ever put another list component on the page. What do you think?

Nick:

uh, yeah, for for, for demos or for understanding, for stuff like this. But uh, this, this new announcement for me. When I looked at it first it was like part of me was, couldn't we always do this? And then I read deeper into it and I'm like, oh yeah, no, not the way that they're describing. So this opens up a lot of new possibilities in terms of building custom user interfaces. And again it really goes to show power pages is is becoming, is what I like about power pages versus power apps or some of these other things. It is very developer friendly. It really opens up rips, because you're you know, when someone talks about power apps like, oh, now you can see the source code in power apps, like we can see the source code in Power Apps. Like we could see the source code and not the source code, but the code behind the pages in Power Pages for a long time now. This opens up a whole new thing in terms of being able to create.

Ulrikke:

Yeah we need to slow down and talk what it actually is, yeah.

Nick:

We forgot to say what that?

Ulrikke:

yeah, so the announcement is you can now create and deploy a single page application in PowerPages. It's now in preview and what it actually means is that you use PowerPages more as a scaffolding, as the blob thing, and you just put your React code inside it and it works like a one-page application. Now backtrack what? 10 years now or something. When I first met you, you did this. So this was when we talked about power pages the first time.

Ulrikke:

I remember you saying actually, for for most project that we do, we use all the benefits of the authentication, the security, the governance, everything that's good in power pages, but what? What you actually interact with on the page is usually custom code, because we just use it as a placeholder and we kind of inject our companion React or Angular app that is hosted in Azure somewhere into the PowerPages site to do what we wanted to do. So actually, when I saw this, I was like wait Inception, because I was just suddenly back there and I thought, yeah, now that we can vibe code and we can use vision studio code and we can get a co-pilot, this is probably the way to go forward with power pages. And then we had an internal discussion between us in the group where we went just ah, what should I learn? React, oh, should I not. And what do we do? And is this good or is it bad?

Nick:

What's your take? You know it's funny because it does go back to the days of the old ADX, the classic ADX Studio product, where it was deployed on IIS. And, yeah, we did use the list and form components where it made sense. But in more times the client had particular requirements where we needed to create custom ASPX pages that interface with Dataverse. Sometimes, I know the question sometimes came up well, why bother using Power or, at that time, adx2 portals at all? Why don't we just build straight up NET web applications? Well, the reason why you wouldn't do that time MediaX Studio portals at all, why don't we just build straight up NET web applications? Well, the reason why you wouldn't do that is because and it's the same argument today of well, why not just build a single page application and deploy it to an Azure website? Well, what we're getting is, for instance, authentication, so we can actually use the regular PowerPages authentication for our single page web app. That saves days of configuration time in terms of building a single page application, in terms of the security, because you can use the PowerPages web API, so you don't have to worry about all of those the token passing. Everything else it's all taking care of you, taking care for you so you can interact with dataverse through your spa as well, using the power pages web api. So this does it definitely opens up a lot of new possibilities. It does provide that good yeah, that framework. Um, I still think there's still a, there's still um, there's still a mode or market for building the pages and using those components for very functional web applications and things like that, if you don't have those specific user requirements. But if you're in a case where the user interface is important, how things interact with the user interface is very important. This is going to open up a lot of new doors and also allow more of Fusion, allow to increase better that fusion team development of the react developers and the power pages features and stuff that we all know.

Nick:

In terms of, yeah, the vibe coding and stuff too, it's like again, yes, we'll be able to. We, I think still what I'm kind of been in my experiences with vibe coding lately, um, it's you still need to have some of that foundational knowledge in order to make sure things work right. But again, the vibe coding to me, you can start vibe coding knowing nothing. But even if you're vibe coding true, they say true, vibe coding you shouldn't even need to look at the code. I'm saying, yes, vibe coding. Look at the code. I'm saying, yes, vibe coding. Look at the code. Learn from the code. See what it's generating, see why it's generating it. Ask it questions Is this secure, is this efficient?

Nick:

You, as a developer, are just going to become better because you're actually now working with, I would say, like someone who's tutoring you through this process, even though it's still your own ideas and business processes. So the next time you want to go create code, first off, you know what prompts to run, but you also can understand a little bit better what's happening. So, again, this opens up. So should we learn React? I think it's not the fact that we're going to sit down and learn React. I think we're going to learn some of the whether it's React or some of these other techniques or frameworks that's just going to come to us, because we're going to be in a situation where we're going to ask GitHub, copilot, I need to do this, and it's going to generate code and we're going to look at it. We're going to go, yes, that makes sense to me or no, but I accidentally learned it along the way.

Ulrikke:

Yeah, but I have a problem with that, and that is when I tried to learn something that complex. I'm not very good at it. So I recognize even now when I look at the React developers that are on my team and how efficient and how well they do things, and I look at my code and I'm like, okay, this is completely new, because it is that foundational development mentality and that you understand how this works and how to create efficient code and all the different mechanisms you learn as a professional developer. I don't think that vibe coding is going to get to that. Also, I don't think I can understand what the code is when I don't think that Vibe Coding is going to get to that. Also, I don't think I can understand what the code is when I don't have that foundation. So when you have that discussion, I'm at the other end. I go.

Ulrikke:

How many professional React developers are there in the world? Quite a lot. How many people know PowerPages and Power Platform as well as we do? Not a lot of people. If you know power pages today and you're looking at what direction to go go in, don't go down the react route. Keep on your lane and just dive in and know the and get to know the platform even better, understand the mechanisms around and on the back and the things surrounding power pages, dive into the security part, dive into the authentication part, dive into copilot studio and learn that as best as you can, because you can always get a react developer to come in and help you with the code stuff. That's not where you're gonna, kind of you, just find your niche, find your little thing that you're really good at. That sets you apart, and nourish that part.

Ulrikke:

So it's interesting that we come at this from different angles and I love that. We can kind of just talk openly about it and we kind of disagree and it's completely fine and then you just do what you want to do. But for sure it is very interesting because I see these pop up so a lot of places and if you look at the conversations I've had with people this last week about AI, the underlying worry and anxiety comes in from a place where where do I fit into all of this? What am I going to do? What is my work going to look like the next five years? What do I need to learn? What is the skill that I need to develop in order to survive and to have a job in the next five years, and I think that is probably the underlying anxiety in this conversation, as well as PowerPages people, now that PowerPages suddenly is a placeholder for React code.

Ulrikke:

If you look at it from the extreme, what do I do with my skills? And I'll always come at it from the perspective of what are you passionate about? What is the thing that sets you apart? What is it that you know that not a lot of other people know? And if that's something that you are passionate about, that's the direction you go in, and don't be scared about kind of, because you always need people with that kind of key knowledge. Um, so yeah, yeah and it.

Nick:

I like that. It's funny because we've talked about this before in terms of career paths and what to learn. Um you like, I know for myself. I didn't choose portals. I didn't sit down one day going. I want to learn.

Nick:

I want to learn how power pages works. I want to learn how PowerPages works, or I want to learn how ADX Studio Portals work. It was more of a case of no. You need to learn this because this is a project, this is where you need to go, and I think this is some of the AI things too. It's sort of like, okay, well, I need to learn this, but I need a project to focus on and to learn that. And finally, a few of these things are popping up, forcing me to go down different roads with that.

Nick:

So, um, yeah, so it's a. It's like the harry potter thing right, the wizard doesn't choose the wand, the wand chooses the wizard. So we're going to see this. So, again, but also, be open, be curious, be, um, be open for the wand to choose you. Whatever that technology stack will be, and I think we, because of our whatever that technology stack will be, and I think we because of our experience and things like that, we're still going to be able to provide a lot of value. But I will agree, it is going to be. We're going to have this conversation in two or three years. Our jobs are going to be radically different and, I think I hope in a really good way. But cause? But the thing is also, when we talk about this thing, about the single page applications, one thing it doesn't do, which both you and I are good at, is liquid. And it brings us to the segue, to the next post that you put from Callum Harrison. You want to chat about that?

Ulrikke:

Sure, no, it's actually just how to learn liquid for power pages, kind of document thing on LinkedIn that he created because he was diving into it and learning it. So it's a really good resource. But I also think that it's kind of becoming a bit obsolete now that we have web API read access and stuff. I'm looking into some of the old things, for instance, how we used to use the AJAX method to read data from Dataverse and then put it into custom dropdowns, for instance.

Ulrikke:

I'm implementing something similar now for a customer and then suddenly I found I think it was Oliver Rigger's blog post where he uses the web API to do the fetching and I'm like, ah, that saves me two web templates one page template and one web page. That's fantastic and I don't have to use Liquid that much. So it's I don't know, um, I'm looking at this and going it's probably yesterday's news and looking forward. Maybe we don't have to use it as much, but it's uh, but it's still. If you're going to work in traditional power pages site implementations, liquid is absolutely valuable to learn. So check out Callum's post.

Nick:

Yeah, and I feel I still think liquid is very elegant for certain situations as well. Much and much more less overhead, like in some cases yes, like the description you just said about dropdowns, for sure, but in other cases it is you could basically write a lot less liquid code, do a lot less setup to get what you want, versus doing the read in the web api. So the right tool for the right job and also the load on on.

Ulrikke:

I mean just to fetch something or to use liquid to get entity, to get data from related entities. It's a lot less load on the system than to go to grab it before and then. Yeah, in terms of that, if you know how to use it, it's really good. In the interest of time, let's wrap it up with the EPBC, the conference that we're doing next week, you and me, and Victor Dantas, has a workshop on Monday about PowerPages. Top Gun is coming back, so you're going to have to get into that little suit of yours and the Top Gun Ray-Bans are coming on for that workshop. Boost your site development skills and become a pro pilot with PowerPages. And then you and me are doing PowerPages Top Tips and Tricks, which we are now reinventing as we speak, because, oh my Lord, there's been some advancements since we did that session last time. And also you have a PowerPages Crash Course Co-Pilot Edition session.

Ulrikke:

And then I'm also on a panel. Andrew Beebe asked me to be on a panel with Joe Griffin, sarah Largus, scott juro and me. Um, I think that was it, so that's going to be interesting. Um, and yeah, then. And if you don't have your ticket yet, which I hope everyone has. You can use nick 10 for 10 off off your ticket and if you go we have some absolutely amazing swag for you. So your wife Bridge brought a very interesting little package to when she came to see you and go on holiday last week. I'm imagining people at the airport scanning those luggages went look, can we look at that again? Did I see what I think I saw? And just zoop, zoop, yes, it is 100 rubber ducks.

Nick:

Oh, you gave it away.

Ulrikke:

Do you want to show people what it is?

Nick:

You have one nearby, I do actually.

Ulrikke:

So if you see us at EPPC, make sure to come by, give us a hug. You'll get a sticker and maybe we'll give you one of those little rubber duckies. They're so cute. You correct me if I love it, right? So do you want to talk about why you ordered a bazillion rubber ducks?

Nick:

Sure.

Ulrikke:

So what happened? Happened what we talk about? So when you're doing coding I'll see what happened by accident, like yeah, so what happened was what happened?

Nick:

no, no, no, yeah. So I mean, we um like, so you do development. There's always this concept of rubber ducking, right where you actually talk to something, and I've had this, uh, when I was at microsoft. This, uh, donovan, good, who, donovan? It's big shout out to donovan. Uh, sometimes he would just call me in a team's meeting and like I need you to look at something, like, okay, donovan, sure we hop on a team's call. I'm doing this code, I'm doing this and did you put you did it? Okay, I need to move this. Like, oh, man, that's not working, okay. And then, boom, you go, oh, it's working, thanks so much.

Nick:

And I'm like donovan, I didn't say two words. He goes, no, no, no, you're a perfect rubber duck. And of course it goes back to coding about talking your problems or talking you're through yourself when you're actually talking to like a rubber duck. So I thought, hey, we should create rubber ducks. I wanted to see, can we to a rubber duck? So I thought, hey, we should create rubber ducks. I wanted to see, can we get a rubber duck with the Boost logo on it? And sure enough, you can.

Ulrikke:

Yes, it turns out. You can, and of course we do this all the time and every single week. Of course we're on the same project together. It makes sense, but also for other things. We have rubber ducks. That's kind of what we do. I just need your eyes and head. Can I borrow your head? That's what I'll say, and I'll use that as my rubber duck. So does this mean I can't use you as my rubber duck?

Nick:

Because, as much as fun as a rubber duck is, I kind of want the in-person experience. Yeah, oh, yeah, no, I'll still be rubber duckable.

Ulrikke:

Okay, rubber duckable, I love it, okay. So what are you going to do now is you're going to use AI and you're going to have it, look at our videos, and then you're going to turn us into rubber ducks.

Nick:

So this whole episode is going to be you and me as rubber ducks doing the episode, right, yeah, yeah, sure, I'll get right on that. I love it Like we don't have a thousand other things to do before next week, but sure.

Ulrikke:

Yeah, yeah, yeah, no worries, yeah, cause we say for everything, we have so much time on our hands, right?

Nick:

Yeah, absolutely.

Ulrikke:

I wonder when that is going to kick in. I'm looking forward to it. You know when, when, when I'm going to get all that extra time that I'm going to get when I use AI and agents and stuff, because they keep telling me that it's going to give me so much time back.

Nick:

Yeah, I haven't seen that yet either.

Ulrikke:

Yeah, no, okay, let me know if you see it, because it's not, yeah, I can't really say that I've, if anything, I have more to do, yeah.

Nick:

I'm in the same boat, all right.

Ulrikke:

So anyone listening to this if you have found where we can go get that extra time, that, they're talking about, then let us know, sounds good. Sounds perfect. All right, have a wonderful rest of your day. It's sunny and calm and a bank holiday here in Norway, so I know that you're going to have going to walk around, probably, and see some stuff and have a wonderful day.

Nick:

Probably trying to get caught up in work. I've done a lot of walking around seeing stuff in the last week, so now it's time to get back to work.

Ulrikke:

Okay, sounds good. I'm going to celebrate my birthday with my brother at my mom's space today, so I'm going to go bake some brownies and some rhubarb tarts and we have the best ice cream, and it's going to be a lovely day with the kids. So I'm looking forward to that and I'll catch you this week Later.

Nick:

Right, all right, catch you later.

Ulrikke:

Sounds perfect, bye, bye, bye, perfect Bye-bye.

Nick:

Bye. 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.

People on this episode

Head Shot

Nick Doelman

Host
Head Shot

Ulrikke Akerbæk

Host