June 4, 2024

Episode 323: In the Dynamics Corner Chair: Determining the Product Roadmap and the Power of Copilot

Episode 323: In the Dynamics Corner Chair: Determining the Product Roadmap and the Power of Copilot
Apple Podcasts podcast player icon Spotify podcast player icon Youtube Music podcast player icon RSS Feed podcast player icon Amazon Music podcast player icon Audible podcast player icon YouTube podcast player icon
Apple Podcasts podcast player icon Spotify podcast player icon Youtube Music podcast player icon RSS Feed podcast player icon Amazon Music podcast player icon Audible podcast player icon YouTube podcast player icon
Season 3

In this conversation, Jannik Bausager, Group Product Manager for Microsoft Dynamics 365 Business Central, discusses various product roadmap and strategy topics. He explains how the product roadmap is determined. He also discusses the planning horizon for the roadmap, highlighting the difference between planning and sharing specific details. The conversation covered various topics related to the Business Central application roadmap and growth opportunities. The discussion also highlighted the significance of staying up to date with the release plan and the importance of adequate documentation and communication.

Send us a text

#MSDyn365BC #BusinessCentral #BC #DynamicsCorner

Follow Kris and Brad for more content:
https://matalino.io/bio
https://bprendergast.bio.link/

00:00 - Exploring Microsoft Dynamics Roadmap

11:52 - Product Management Strategy and Roadmaps

19:27 - Community-Driven Feedback and Product Development

32:35 - Product Roadmap Planning and Growth Opportunities

44:06 - Co-Pilot Data Security and Growth

48:32 - Leveraging Business Central and Copilot

01:03:01 - Business Central Podcast Promotion and Information

WEBVTT

00:00:00.240 --> 00:00:09.073
Welcome everyone to another episode of Dynamics Corner, the podcast where we dive deep into all things Microsoft Dynamics and its roadmap.

00:00:09.073 --> 00:00:19.111
Whether you're a seasoned expert or just starting your journey into the world of Dynamics 365, this is your place to gain insights, learn new tricks and hear from industry experts.

00:00:19.111 --> 00:00:20.745
I'm your co-host, chris.

00:00:22.120 --> 00:00:22.902
And this is Brad.

00:00:22.902 --> 00:00:27.591
This episode is recorded on May 21st 2024.

00:00:27.591 --> 00:00:31.082
Chris, chris, chris, you said roadmap.

00:00:32.445 --> 00:00:33.508
We all need a roadmap.

00:00:33.548 --> 00:00:37.274
You said roadmap but it makes me think.

00:00:37.274 --> 00:00:41.267
Do you remember when you were driving, or have you ever driven with a like a paper map?

00:00:41.267 --> 00:00:43.030
Oh my gosh, with a paper map?

00:00:43.030 --> 00:00:43.310
Oh my gosh.

00:00:43.310 --> 00:00:43.771
Yes, A map quest.

00:00:43.771 --> 00:00:45.554
Now everybody has a GPS.

00:00:45.554 --> 00:00:46.115
Remember map quest?

00:00:46.115 --> 00:00:51.508
I talked with my son and others and they grew up with the phone and a map.

00:00:51.508 --> 00:00:58.066
I don't think they understood what it was like to have to print out directions or to use a map book when you're driving down the street.

00:00:58.066 --> 00:01:06.760
It's just amazing how technology has changed and how some of the old technologies have forgotten.

00:01:06.799 --> 00:01:08.819
You couldn't even figure out what the traffic was Like.

00:01:08.819 --> 00:01:12.813
It's just a piece of paper expecting like oh, I'm going to make it this time Exactly.

00:01:12.834 --> 00:01:18.450
and you would just go yes, now it talks to you, now it reroutes you, now it does everything.

00:01:18.469 --> 00:01:18.850
Yes.

00:01:20.439 --> 00:01:21.161
You say roadmap?

00:01:21.161 --> 00:01:22.462
That's what it makes me think of.

00:01:22.462 --> 00:01:50.108
And, speaking of roadmaps, today we had the opportunity to speak with Yannick Balser about what goes into the Business Central application roadmap, what goes into Business Central we talked about so much, and also some amazing growth opportunities and strategies for prospects, customers and partners.

00:01:50.108 --> 00:01:50.908
Good afternoon, how are?

00:01:50.927 --> 00:01:53.349
you doing, I am doing fine, and you guys?

00:01:54.129 --> 00:01:57.712
Not too bad, doing very well, very well, thank you, thank you.

00:01:57.891 --> 00:01:59.153
Good morning to Christopher.

00:01:59.153 --> 00:01:59.873
I guess it is.

00:02:00.132 --> 00:02:14.147
It looks really dark there it is it's morning Six in the morning, oh okay, okay, too bad, and you don't have jet lag, like I have from Asia.

00:02:14.147 --> 00:02:15.520
So you know, no, certainly not, not from you guys.

00:02:15.939 --> 00:02:23.437
No, that must be a big change, although we went to DynamicsCon live last week.

00:02:23.959 --> 00:02:24.080
Okay.

00:02:24.983 --> 00:02:30.004
And for me that was a two hour time difference and that hurts.

00:02:30.004 --> 00:02:35.420
And just talk with me like I know you went to asia, so what's the difference for you with asia?

00:02:36.241 --> 00:02:39.268
asia is five hours, so you know a little more.

00:02:39.268 --> 00:02:43.402
Um, as I say, you know I hate to not hate, but you know I don't like to go.

00:02:43.402 --> 00:02:45.729
You know east, because that's I can't accommodate when I go.

00:02:45.729 --> 00:02:46.973
You know I hate to not hate, but you know I don't like to go.

00:02:46.973 --> 00:02:48.176
You know east, because that's I can't accommodate.

00:02:48.176 --> 00:02:51.348
When I go west, you know to US, I love it, that's where I'm Superman in the morning.

00:02:51.348 --> 00:02:53.989
So you know I actually went home.

00:02:53.989 --> 00:03:13.429
So now I went west, you could say, and that's of course great, because I was up early this morning and thought I was even in the office after my exercise at seven here in the office the morning, and thought I was even in the office after my exercise at seven here in the office the first thing they do.

00:03:13.449 --> 00:03:16.699
They had a fault in the fire alarm, so we all had to walk to the street and I was here ready to work and I ended up on the street this morning.

00:03:16.699 --> 00:03:17.861
So, anyway, yeah, that's what happens.

00:03:17.861 --> 00:03:19.025
That's what happens.

00:03:19.485 --> 00:03:39.012
Yes, no, the time difference affects me because then we went to directions in North America, which was three hours for me, because this year the conferences are towards the West Coast and, like you, I'm Superman in the morning, but when everybody wants to go to eat dinner at seven in the evening or 1900, it's crash.

00:03:39.012 --> 00:03:40.074
It's my bedtime.

00:03:40.860 --> 00:03:42.748
So it's a little it's a little difficult.

00:03:42.829 --> 00:03:44.830
So it's a little difficult, and then I think it takes.

00:03:44.830 --> 00:03:51.472
I try to stay on the schedule, but after a few days you become acclimated to the local time because of the sun.

00:03:51.472 --> 00:03:54.454
So then when you come back that's where the whole jet lag comes in.

00:03:54.454 --> 00:04:00.336
You get a little sleepier, a little off, as you can say how was the conference?

00:04:01.515 --> 00:04:02.757
conference.

00:04:02.757 --> 00:04:04.858
So so I just want to did we start already.

00:04:04.858 --> 00:04:06.397
Is are we live are we?

00:04:06.677 --> 00:04:10.025
yeah, yeah, always okay it's, it's rocking okay I?

00:04:10.044 --> 00:04:13.312
just wanted to know if this was like a small trip into this.

00:04:13.312 --> 00:04:14.152
No, okay.

00:04:14.152 --> 00:04:17.043
So uh, conference was, uh was great.

00:04:17.043 --> 00:04:22.411
I mean, uh, in asia we had 500 partners, a little more than last year.

00:04:22.411 --> 00:04:28.161
So I mean I love, you know I like all the events.

00:04:28.161 --> 00:04:41.625
But Asia is great in the sense that you know it's a smaller audience so you know it's not as busy, you don't run around crazy and have, you know, all kind of sessions on top of each other.

00:04:41.625 --> 00:04:49.588
You know you're a little more in control there and I mean the appetite for a business central is the same as the sessions on top of each other.

00:04:49.588 --> 00:04:56.036
You know you're a little more in control there and I mean the appetite for a business central is the same as the other conferences as well.

00:04:56.036 --> 00:04:58.158
It's just huge and there's, you know, a lot of growth in Asia.

00:04:58.158 --> 00:05:07.160
So it's a matter of you know just us, yeah, getting to both more partners, more capacity out there, and we'll rock like you rock like we do in the rest of the world, so to speak.

00:05:07.701 --> 00:05:24.108
Well, the product is growing, at least from what I can see here in the US, and also now with that wonderful thing they call the Internet, you have to take it for what it's worth, but you get to see visibility into other countries and just from the communications that you have you can see that the product's taking off.

00:05:24.108 --> 00:05:25.906
So you mentioned there's 500 partners.

00:05:25.906 --> 00:05:29.886
How many attendees does that equate to, I know, in directions North America?

00:05:30.139 --> 00:05:32.168
I think we had 1,300.

00:05:32.168 --> 00:05:37.437
No, so when I say 500 partners, I mean like there were 500 attendees there.

00:05:37.437 --> 00:05:38.341
Okay, you know.

00:05:38.341 --> 00:05:39.747
So that's what it is.

00:05:39.747 --> 00:05:44.865
How many partners that would I mean, like you know, unique partners?

00:05:44.865 --> 00:05:45.605
I'm not really sure.

00:05:45.605 --> 00:05:48.668
The number was there on a slide.

00:05:48.668 --> 00:05:55.617
Of course, some said you know more and some just one, but in total we had 500 people there 500 is a good number.

00:06:01.560 --> 00:06:03.372
It's an intimate group because it gives you the opportunity to speak with more people.

00:06:03.372 --> 00:06:03.519
That's as Chris had mentioned.

00:06:03.519 --> 00:06:04.165
You get more time with more people.

00:06:04.165 --> 00:06:05.891
That's as chris had mentioned, you get more time with individuals.

00:06:05.891 --> 00:06:11.576
One thing I a curiosity, just not to spend too much time on the conference is the message the same?

00:06:11.576 --> 00:06:13.786
So yeah, at each conference?

00:06:13.786 --> 00:06:15.612
Is there how different?

00:06:15.612 --> 00:06:21.685
We had directions north america approximately maybe a month ago, and so now here we are, a month later.

00:06:21.685 --> 00:06:27.894
Is there a cycle for these conferences or is the messaging rather similar now that 2024 wave one was released?

00:06:29.141 --> 00:06:31.269
So that's a super question.

00:06:31.269 --> 00:06:36.653
So I would say, in most cases it's the same message we actually do.

00:06:36.653 --> 00:06:49.807
And the great thing about Asia coming after the North American one is we, you know, in my case, doing, you know, keynote day one and so on is that we, you know, have already rehearsed that or not even rehearsed.

00:06:49.807 --> 00:06:51.701
We've already given that in North America.

00:06:51.701 --> 00:07:06.134
So, going to Asia, I mean, if people go to both, they will, you know, some will be disappointed if they expect a completely different show, because for us, a lot of it is, of course, a replay of what we did in North America.

00:07:06.134 --> 00:07:11.240
Of course, if there is, you know, we're, of course, looking at what's happening in the region.

00:07:11.240 --> 00:07:18.473
So, opening-wise, satya was just, you know, traveling Asia the week before we came there.

00:07:18.473 --> 00:07:24.115
We can't take the you know and say it's due to us, unfortunately not.

00:07:24.115 --> 00:07:26.182
We can't take the you know and say it's due to us, unfortunately not.

00:07:26.182 --> 00:07:27.444
But he was there.

00:07:27.564 --> 00:07:33.875
And there's been a lot of communication in the media about the investment Microsoft is doing in the Asia region.

00:07:33.875 --> 00:07:37.822
So of course we referenced that.

00:07:37.822 --> 00:07:48.728
It doesn't make sense to, you know, go on stage and not just be silent, because there's actually, you know, we're building data centers in most of the countries there we're investing in, you know, skilling of people.

00:07:48.728 --> 00:07:51.144
I mean it's billions and billions of dollars.

00:07:51.144 --> 00:08:02.930
That was basically committed, you know, from Indonesia to Malaysia, to Thailand, singapore, you know, yeah, and I could give Vietnam, you know, just going on with the countries.

00:08:02.930 --> 00:08:12.250
So I'm sorry for not mentioning all of them if there are some international listeners here, but it was just a huge, huge commitment.

00:08:12.250 --> 00:08:14.839
So of course that's changed from an opening perspective.

00:08:14.980 --> 00:08:19.372
And then another thing is in this business, you know, things move so fast.

00:08:19.372 --> 00:08:28.939
So the news we had in North America I mean, there are new, you could say, things and new updates to our release, even, you know, a month later.

00:08:28.939 --> 00:08:46.740
So one of the things we had in Asia and announced there was our new set of Power BI reports that we will be releasing, first in private preview and then we will release it, you know, ga, in October.

00:08:46.740 --> 00:08:53.951
So we had some mock-ups of what that actually is, full embedded experience in Business Central for the power behind.

00:08:53.951 --> 00:09:00.205
So that was not North America, because we first have finalized the plans after coming back.

00:09:00.205 --> 00:09:01.544
That's how fast it is.

00:09:01.544 --> 00:09:03.166
So no show is the same.

00:09:03.166 --> 00:09:09.206
I have to say it's not like going seeing, you know a rock concert and you'll say, oh, it's the same set list you know.

00:09:09.206 --> 00:09:16.537
For that we will always have, you know, a new tune to play, because this world is changing so fast that's true.

00:09:16.557 --> 00:09:18.142
It's only about a month difference.

00:09:18.142 --> 00:09:23.081
Right like that, you have a brand new announcement which we just missed in north america.

00:09:23.081 --> 00:09:24.707
We had to see it through Twitter.

00:09:29.759 --> 00:09:31.947
Yes, yes, thankful for Twitter and the internet, because we were able to see the screenshots of the preview.

00:09:31.947 --> 00:09:37.825
I try to keep up with it, as you had mentioned, and in this space, I feel as if you go to sleep for 24 hours.

00:09:37.825 --> 00:09:39.629
The world would be completely different.

00:09:39.629 --> 00:09:53.807
So you have to sleep in smaller chunks, to sleep in in smaller chunks every time we speak with someone from your office.

00:09:53.828 --> 00:09:56.413
I'm just feel like I have to go visit because I really enjoy the legos.

00:09:56.432 --> 00:09:57.715
Yeah, it was such a nice touch.

00:09:58.642 --> 00:10:26.053
It makes me want to have a set of legos here for me to play with yeah, yeah to get creative and promote thought I was actually thinking when I looked at my background in this meeting room, which is our, you know, yeah, lego creative room, I was just thinking having titanic over my head is probably you know, not maybe the best sign I hope we'll get through this without me saying something that later will be used against me or whatever will be happening here.

00:10:26.053 --> 00:10:30.282
But you know, yeah, we have whatever you could see.

00:10:30.282 --> 00:10:33.710
We even have, like let me see, yeah, the Eiffel.

00:10:33.730 --> 00:10:37.647
Tower is there and, by the way, now for people that haven't been here.

00:10:37.767 --> 00:10:47.504
I can see the lightning is a little bad, but you can see your A3M there and yes, and then, of course, you know all the different kinds of small Lego.

00:10:48.427 --> 00:10:50.724
It's amazing To go to Directions EMEA.

00:10:50.724 --> 00:10:52.610
I want to go to the Microsoft office.

00:10:54.783 --> 00:10:56.509
You should come, Brad and Christopher.

00:10:58.403 --> 00:11:04.048
I will put it on my list, we'd like to thank you for taking the time to speak with us this morning.

00:11:04.048 --> 00:11:11.187
We know that you have a busy schedule and time is extremely valuable, and there's several things that we wanted to talk about.

00:11:11.187 --> 00:11:15.740
You know, as far as the application roadmap, some growth opportunities as well as strategies.

00:11:15.740 --> 00:11:21.831
But before we get into that conversation, would you mind telling everyone who's listening, who may not know, which I don't know who?

00:11:21.831 --> 00:11:24.075
That would be a little bit about yourself.

00:11:25.240 --> 00:11:27.264
Sure, I can definitely do that.

00:11:27.264 --> 00:11:28.808
And no, I do not know.

00:11:28.808 --> 00:11:31.140
Thank you, everybody knows me, but you know.

00:11:31.140 --> 00:11:33.566
So that is always a good start.

00:11:33.566 --> 00:11:35.229
Who are we listening to here?

00:11:35.229 --> 00:11:42.312
So yeah, I mean the name is there, yannick Bowset, and all people always ask me so how do you pronounce that?

00:11:42.312 --> 00:11:45.000
And I would say it depends on where we are in the world.

00:11:45.000 --> 00:11:50.952
So you know, feel free, when you address me, to say it the way you say it in the world, because that's just how it is.

00:11:52.500 --> 00:11:56.886
So, what I've been, it's actually 31 years ago.

00:11:56.886 --> 00:12:02.695
I walked through the doors of what was called Navision actually in the old days.

00:12:02.695 --> 00:12:07.131
I mean that was, you know, we're basically the foundation for Business Central.

00:12:07.131 --> 00:12:16.090
So 31 years ago I started actually, and even you know some people here around they get a shock when I said I was doing development.

00:12:16.090 --> 00:12:18.025
They think did you really touch the code?

00:12:18.025 --> 00:12:18.729
Yes, I did.

00:12:18.729 --> 00:12:43.192
I started as a programmer for localization so had different countries where I did the you know, bat, sales tax, gst and so on, and did that for quite some years of the Windows version actually.

00:12:43.192 --> 00:12:45.933
And, yeah, been through all the time.

00:12:45.933 --> 00:12:49.895
I mean took actually also a job in Asia for some years running.

00:12:49.895 --> 00:12:59.379
The Malaysian office started in the Singapore office, then later set up and part of setting up the sales office there, so doing sales as well.

00:12:59.379 --> 00:13:08.014
And then I transitioned back to Denmark just after Microsoft bought Navision in 2002.

00:13:08.779 --> 00:13:26.894
And so that also means that what is it 22 years in Microsoft by now and what I do now just coming to that was long intro, by the way, but what I do now is I'm responsible for the team that defines what goes into the application.

00:13:26.894 --> 00:13:31.511
So that actually is called in Microsoft a product management team.

00:13:31.511 --> 00:13:36.131
So I am what we title-wise call a group product manager.

00:13:36.131 --> 00:13:39.340
So you know having this group of great product managers.

00:13:39.340 --> 00:13:42.967
So if we look at my team, I have one, you know.

00:13:42.967 --> 00:13:46.033
I have some persons responsible for finance.

00:13:46.033 --> 00:13:50.211
I have some for a supply chain, what we put into the supply chain area.

00:13:50.759 --> 00:13:58.830
Also people looking after what do we do with the, for example, the power platform, what integrations do we need to build?

00:13:58.830 --> 00:14:10.832
I have people also looking into what do we do with the other Dynamics 365 products, also looking into what do we do with the other Dynamics 365 products.

00:14:10.832 --> 00:14:15.398
I have also people looking after what do we do in terms of the localizations that are, you know, delivered by Microsoft.

00:14:15.398 --> 00:14:20.342
We have 21 country localizations, so we need to stay on top of what's actually changing in the world.

00:14:20.342 --> 00:14:26.153
And oh my, there's a lot of you know things changing in the world right now when we talk about requirements and so on.

00:14:26.660 --> 00:14:28.467
We could have a whole chapter on that.

00:14:28.467 --> 00:14:33.471
You should invite my guy that actually runs that, alexander Totowich, at some point.

00:14:33.471 --> 00:14:47.679
He could spend hours on telling you how the world is changing, getting more electronic, how it's being mandated from the different countries, different countries Anyway.

00:14:47.679 --> 00:14:51.230
So you could say, basically setting this strategy for what are we going to invest in product-wise over the coming years?

00:14:51.230 --> 00:14:56.712
And these days you probably guess what it is we are looking at, but that's co-pilot.

00:14:56.712 --> 00:14:59.528
That's where a lot of our investments go.

00:14:59.528 --> 00:15:09.375
So yeah, just finishing off, I've been here, I would say almost on all kinds of roles you could do in this business.

00:15:09.375 --> 00:15:16.727
I haven't run it yet, but that's all fine, I love what I'm doing.

00:15:16.727 --> 00:15:22.013
I love, you know, basically being part of defining what's going to happen in the future.

00:15:22.259 --> 00:15:24.729
That's my job, my team's job, that's amazing.

00:15:25.640 --> 00:15:29.010
That sounds like a lot and it is extremely important.

00:15:29.010 --> 00:15:38.131
I would say even more so, with it sounding about the responsibility that you have to enjoy what you do because of the time that you invest in it.

00:15:38.131 --> 00:15:53.470
So, as a group product manager that determines what goes into the product I'm assuming it's also defining the product roadmap and you had mentioned you have individual talented members of your team that assist with determining what goes into it.

00:15:53.470 --> 00:15:57.870
How do you determine what goes into the product roadmap?

00:15:57.870 --> 00:16:01.270
We had just spoken about how the world changes so rapidly.

00:16:01.270 --> 00:16:02.519
You mentioned with localizations.

00:16:02.721 --> 00:16:05.080
We were talking about news between conferences.

00:16:05.080 --> 00:16:09.191
I see the product roadmaps that you release at the conferences we're talking.

00:16:09.191 --> 00:16:15.679
You know the investments for right now it's 2024, wave 2, which is six months from now approximately.

00:16:15.679 --> 00:16:27.135
How do you determine what is going to be, what is going to be the focus or work done for the next six months, or the wave, in such a dynamic world?

00:16:28.620 --> 00:16:32.369
You know what I think, what I would love to answer here.

00:16:32.369 --> 00:16:40.774
I will answer it, but what I would love to is give you the link to the book, because it's actually a long answer and it's worth a book.

00:16:40.774 --> 00:16:45.731
So to say how we do that and there's probably plenty of product management books.

00:16:45.731 --> 00:16:49.671
But the reason why I say that is there are so many nuances to it.

00:16:49.671 --> 00:16:59.052
I mean, first of all, it starts with the customers customers already using the product, getting a lot of feedback from them.

00:16:59.052 --> 00:17:04.652
But I can't just say that's all we do, because it will be a really slim book.

00:17:06.280 --> 00:17:08.509
There's many ways how you talk to customers.

00:17:08.509 --> 00:17:18.119
Of course, we have the benefit of as you know, like yourself, you know the great network of partners that you know actually deliver business.

00:17:18.119 --> 00:17:24.188
So we also get a lot of input from the partners that have spoken to many customers, from the partners that have spoken to many customers.

00:17:24.188 --> 00:17:29.154
So that's, you know, you could say, one place of you know, a great source for this.

00:17:29.154 --> 00:17:34.289
But then, of course, there's the market trends.

00:17:34.289 --> 00:17:44.432
I mean no customer asked us or asked us, you know, for Copilot before Copilot was there, you know, or at least no customer asked us for AI before AI was there.

00:17:44.432 --> 00:17:53.750
So it's also about for any product manager, of course, you know, following the industry we talk a lot to also analysts that also look into the future.

00:17:53.750 --> 00:18:07.354
Microsoft internally have a great drive of coming up in different teams with new ideas Our research and department team not only ourselves in terms of R&D, but also in other groups.

00:18:07.354 --> 00:18:19.791
We also, of course, get feedback from there what's the trends, what's going on, what's being invested in, and we go and explore does that fit to an S&P market?

00:18:19.859 --> 00:18:22.229
Because that's, of course, what you have to remember.

00:18:22.229 --> 00:18:37.506
Business Central is focused on the S&P market, so not everything that necessarily happens, you know, day one in a large enterprise is applicable for S&P.

00:18:37.506 --> 00:18:40.531
However, over time we often see what you know enterprises would adopt also has a big influence.

00:18:40.531 --> 00:18:43.637
What's going to happen in the S&P space?

00:18:43.637 --> 00:18:46.884
Let me take one example.

00:18:46.884 --> 00:18:49.151
You know sustainability reporting.

00:18:49.151 --> 00:18:52.801
It's a mandate in many countries right now EU.

00:18:52.801 --> 00:18:54.307
You have to report.

00:18:54.307 --> 00:19:02.412
You know your emissions of, you know of gases and whatever, and those requirements are being put on the large companies.

00:19:02.412 --> 00:19:05.390
But they will ask their suppliers about some of these numbers.

00:19:05.390 --> 00:19:09.010
It's called scope three for those of you listening knowing that.

00:19:09.010 --> 00:19:14.011
And of course, suddenly you know an S&P will ask for those numbers.

00:19:14.011 --> 00:19:15.925
So, again, you know what I'm trying to say.

00:19:15.925 --> 00:19:25.855
Here is also market trends, and this is just an example of how we have to, you know, stay ahead and not just look at what's going on in our space but what's going on outside.

00:19:27.079 --> 00:19:33.172
Then we have, over time, instrumented a lot of great tools for feedback.

00:19:33.172 --> 00:19:44.153
I mean, first of all, everybody listening should remember this short URL, and now I can't, I should have, like you know, right in there, aka MS slash.

00:19:44.153 --> 00:19:46.715
I mean BC Ideas.

00:19:46.715 --> 00:19:55.549
All our short links start with AKA dot MS and then a slash, and this one would then be BC Ideas.

00:19:55.549 --> 00:20:07.766
The BC Ideas place is basically where anybody partners, customers, even prospects, could, you know, register, you know an idea for something we should change in the product?

00:20:07.865 --> 00:20:13.384
And the cool thing is, this is a community driven, so people vote for each other's ideas.

00:20:13.384 --> 00:20:28.526
And again you could say, if that was just it and we didn't have the other components, that will be easy to be a PM, because then we just look at these, you know ideas, and say which one is on the top, and then, and then an look at these, you know ideas, and say which one is on the top, and then an easy job done.

00:20:28.526 --> 00:20:35.252
You know here it is, but then you would miss out on what's the market trend, what other things should we invest in?

00:20:35.252 --> 00:20:43.515
But we take it seriously and we have reviews, always of the ones that come in and also the ones on the top.

00:20:43.515 --> 00:20:52.512
We don't go through those with many votes and basically have, you know, discussions about when is the right time to you know implement it in the product.

00:20:54.040 --> 00:20:55.203
And as I said, this is a book.

00:20:55.203 --> 00:20:57.411
You asked me, so this is a long answer.

00:20:57.411 --> 00:21:02.351
Then, another thing that also drives you know, what are we investing in?

00:21:02.351 --> 00:21:12.271
One thing is something being a top idea, but it's also about what we decided to, you know, open the hood on, so to say.

00:21:12.271 --> 00:21:28.750
Because when you have a product like Business Central that takes care of so many business processes and so on, we've seen that efficiency from a development perspective sometimes comes from when we open and look at a certain area, it tries to focus.

00:21:28.990 --> 00:21:35.180
Let's say, over the last couple of releases in finance, we focused on multi-company investments.

00:21:35.180 --> 00:21:54.092
So that means the engineering team are thinking about that, looking at what can we do to run, you know, in several countries and so on, and therefore we of course review, you know, ideas related to that versus you know, checking, maybe something for service order management.

00:21:54.092 --> 00:21:59.189
In the middle of it have to close down what we're doing, go and change gear and then do that.

00:21:59.189 --> 00:22:06.508
So what we invest in also depends on what we've said, you know, over X number of years.

00:22:06.868 --> 00:22:22.027
When is it we open the hood on, let's say, manufacturing those of you listening out here and saying I'm in the manufacturing industry that's something we have on the roadmap, on a future roadmap, right now, making sure it's great what we have.

00:22:22.027 --> 00:22:29.209
You know, if there's any bugs, whatever, we fix all that but an investment in could we do something a little bit better there?

00:22:29.209 --> 00:22:45.448
That's down the road, because right now in the top supply chain a lot of the focus is in the service and sales area and, again, copilot, of course, driving a lot of these investments and now I can take a breath a lot of these investments and now I can take a breath.

00:22:45.448 --> 00:22:55.655
That was a high-level answer to how we do that and I probably forgot some that's in the back of the book which, by the way, we're not writing a book but I'm thinking we should.

00:22:56.297 --> 00:23:09.153
That's incredible I understand Well it is a big challenge and I appreciate you saying that it's not long-winded at all, because I'm here to listen and learn from you and what you have to say about the product.

00:23:09.153 --> 00:23:10.944
I've been working with it for a long time.

00:23:10.944 --> 00:23:20.729
It's dear to me, and to be able to learn more about what happens behind the scenes versus on the front what I call user or partner facing is important.

00:23:20.729 --> 00:23:45.794
I do appreciate that strategy for your engineering team of focusing on an area, letting them get deeply involved in it and work on that functionality all at once while they're focused on it, because then they understand it, and to me it affords the opportunity for an engineer to submerge themselves in it and live it and understand it and not really have to remember.

00:23:46.000 --> 00:23:47.605
You know, like you said, the pick up and put down.

00:23:47.605 --> 00:23:51.403
Sometimes you forget where you left off and it could leave a gap in the product.

00:23:51.403 --> 00:23:53.346
So there are a number of ways.

00:23:53.346 --> 00:24:00.553
So it is not an easy task because the BC ideas is one avenue where someone can suggest topics.

00:24:00.553 --> 00:24:14.928
Then you also have the market trends that have to be analyzed, and then the user and partner feedback, which also have to be collected and analyzed, and then you sort of mix them up and mush them together on top of your internal initiatives.

00:24:14.928 --> 00:24:16.652
I don't envy you on that.

00:24:16.652 --> 00:24:23.663
I like the little graphics that you do with the roadmap, but having to do all the work to get there is significant, I see.

00:24:24.424 --> 00:24:27.731
Yeah, and maybe I say, you know, thinking about the chapter missing.

00:24:27.731 --> 00:24:36.227
There's, of course, also the things that we don't know, but it's still important in the sense of prospects Because, again, you know, here we are, we develop product.

00:24:36.227 --> 00:24:37.590
You develop the greatest product.

00:24:37.590 --> 00:24:42.233
But if a prospect walks up to it and wants to, you know, maybe try it.

00:24:42.233 --> 00:24:44.340
You know, test it.

00:24:44.340 --> 00:24:44.762
Whatever.

00:24:44.762 --> 00:24:46.669
As you know, we have the trials available.

00:24:47.259 --> 00:24:48.625
We have to think about that as well.

00:24:48.625 --> 00:24:51.968
How you know, how easy it is to approach.

00:24:51.968 --> 00:24:57.871
You know, I can make a feature and I can say, you guys, go out there, you know, tell it 10 times and then they will learn it.

00:24:57.871 --> 00:24:59.907
That doesn't really work in the SMB space.

00:24:59.907 --> 00:25:03.423
We have to try to at least make it, you know, as intuitive as possible.

00:25:03.423 --> 00:25:05.046
We have to try to at least make it as intuitive as possible.

00:25:05.125 --> 00:25:23.711
I'm sure you guys can tell me a few places where we didn't, but we're always trying to, again, listen and learn, but we try so that also, when prospects go to it, I mean one of the things right now which I, you know, let's say you could say that's not really for customers but our demonstration data, demo data as we call it.

00:25:23.711 --> 00:25:40.385
You know we invested heavily over the last couple of releases, but I'm still not satisfied with our level of, you know, transactional data there, because how do you demonstrate these new reports we just talked about if I don't have transactional data with dimensions, with locations, with other things?

00:25:40.385 --> 00:25:44.366
I want to look here you have you can see by location, and then there's one in the demo data.

00:25:44.366 --> 00:25:45.461
It doesn't work.

00:25:45.461 --> 00:25:49.009
But think about that investment here I am, you know, do I want to?

00:25:49.009 --> 00:26:00.125
You know, I need to show great new innovations, which we have, which we are doing, but at the same time, I have to think about also, you know, it can actually showcase all that great stuff.

00:26:00.125 --> 00:26:03.991
So, yeah, that's also what comes to mind.

00:26:04.393 --> 00:26:05.634
That is a key point.

00:26:05.634 --> 00:26:18.192
And one thing that I thought of before is we now have the open contribution pilot for Business Central, which Jesper is managing, which is wonderful.

00:26:18.192 --> 00:26:27.397
But you hit that is a wonderful avenue for the community, as I'll call it, to contribute to make the product better for us all.

00:26:27.397 --> 00:26:33.991
Rise and tides raise all ships, so if the product's doing well, all of us that work with it, including the customers and prospects, get the benefit of that.

00:26:33.991 --> 00:26:38.182
You hit on a key point with the transactional data and the demonstration data.

00:26:38.809 --> 00:26:44.663
Demonstrating or using the product can be a bit difficult because of that data.

00:26:44.663 --> 00:26:51.022
Oftentimes customers or prospects, partners, will tailor the demonstration with products that are similar to theirs.

00:26:51.022 --> 00:27:04.502
Has anyone considered doing a contribution pilot for data building, meaning if you could do like an open source Git where the community members can contribute?

00:27:04.502 --> 00:27:14.461
This is data that would be for a typical manufacturer, this would be for a service manager, this would be for a multi-company supply chain.

00:27:14.461 --> 00:27:31.520
That way we could all contribute, then pick the demo data that would execute, because obviously there's so many options and configurations, it's tough to throw everything in there, right, but if you start bringing in lot, number tracking, serial number tracking, putaways, picks, you talk about all that.

00:27:31.520 --> 00:27:39.315
So maybe there's a way we could, maybe using Copilot, set up a demonstration system with an open source contribution of data.

00:27:39.395 --> 00:27:57.395
That is how I struggle with because I do a lot of demo and so you know, trying to prepare all that and imagine if you have to do that multiple times different industries and unique scenarios and trying to put as much information in there just to get through like an hour's worth of data.

00:27:57.395 --> 00:28:08.570
But it would be really nice to be able to go oh, this is the prospect and they're in this industry, click on that and it'll just populate all the things I need to do a demo.

00:28:09.992 --> 00:28:11.997
Oh man, yes, A great idea.

00:28:11.997 --> 00:28:13.740
By the way, I would love.

00:28:13.740 --> 00:28:20.372
You know, this is exactly what we all would love, right, and what I'm saying here, it is a gap and how we get there.

00:28:20.372 --> 00:28:24.423
I do love, brad, also the idea of contribution.

00:28:24.423 --> 00:28:31.901
I am not sure we explored that enough and you know we can go now and talk to Jesper after this call.

00:28:32.510 --> 00:28:50.419
I think one of the things we want to, you know, always when we do things like this, we at least want to be able to describe foundational what we want, because you know again, data is great, but I also want, for example, you know, I want a company that at least shows some growth.

00:28:50.419 --> 00:28:55.336
I mean data that shows a company in distress and losing money.

00:28:55.336 --> 00:29:03.951
I mean you could say here I am, you know I got all this data, but when we then look at it, it's all you know, no profit and whatever, and that's.

00:29:03.951 --> 00:29:10.710
You could say that's, of course, a given, but that's not always a given, from what I've seen, you know in the past of some of these situations.

00:29:10.710 --> 00:29:15.521
And then you zoom in on a location and then it's just all messed up.

00:29:15.521 --> 00:29:18.690
Then you zoom in on a location and then it's just all messed up.

00:29:18.690 --> 00:29:29.425
So there are some rules and whatever we need to at least set the scene for so that I guess if you do manufacturing, it's not completely off from that service business, but not necessarily.

00:29:29.425 --> 00:29:30.329
You know, I'll think about that.

00:29:30.871 --> 00:29:47.278
I am not sure how much time we spent on, you know, really thinking about the contribution part here, and maybe for listeners, brad, because you brought it up that doesn't really know about this Maybe it's worth to say one minute what this whole GitHub contribution is.

00:29:47.278 --> 00:30:03.838
But I just want to say, and maybe that's also a part I would say, not forgot, but it almost feels like forgot again for the book, because that's in itself, you know, also a way to build the product and have a roadmap and we are seeing great contributions.

00:30:03.838 --> 00:30:19.823
So it's basically, as you know, the capability I'm talking not to you but to your listeners now but the capability for the community to say I want to fix this as the broker, we have open sourced our base code, but we haven't, you know, open gated it.

00:30:19.823 --> 00:30:37.065
I want to stress that every time we talk about open source, that you know there are some customer listening and saying, wow, everybody can just change the code and no, not everybody, and it is always gated by the same PM that would have told you know, development organization to actually develop it.

00:30:37.710 --> 00:30:44.104
And the community itself also reviews together and, you know, discuss whether a feature function makes sense.

00:30:44.104 --> 00:30:52.759
But end of the day, it's somebody here looking through it and say, approve, but, and in collaboration with those that are contributing.

00:30:52.759 --> 00:30:58.242
But we are seeing, you know, of course, you course, actually quite a lot coming in these days.

00:30:58.242 --> 00:31:04.781
I'm so thankful for those of you listening that actually do these contributions.

00:31:04.781 --> 00:31:11.621
We already got the crystals produced for the next event, so to hand out and saying contribution heroes.

00:31:11.621 --> 00:31:15.056
So those of you listening out there doing that, make sure to get one of those.

00:31:19.071 --> 00:31:21.775
That is again to take away from some of the topics I want to speak with you.

00:31:21.775 --> 00:31:33.075
It is a great way to contribute and help improve the product, because it may be easy to wish or say it doesn't do this or I wish it did this, but to have the opportunity to contribute to make it a better product is great.

00:31:33.075 --> 00:31:35.199
To contribute to make it a better product is great.

00:31:35.199 --> 00:31:44.082
And you did hit on a key point and that's where I'm happy that it's called the contribution pilot, because it's not open source, where it's controlled by the community.

00:31:44.082 --> 00:31:44.603
Everybody does it.

00:31:44.849 --> 00:31:55.250
It's members of the community have the application, has the transparency to see how it's written and what it's done, and it doesn't mean that I can go in and just change anything.

00:31:55.250 --> 00:32:06.903
It is still controlled from the Microsoft engineering team where they review properly the code that somebody contributes to see where it fits within the application, as well as the roadmap.

00:32:06.903 --> 00:32:13.622
So it's not an open source product which some may look at and I've seen some literature on where it's almost a negative.

00:32:13.622 --> 00:32:14.932
To me it's the opposite.

00:32:14.932 --> 00:32:24.155
In this case it's an extreme positive because there is a voice to be able to add improvements to the product versus somebody sitting, as they say, in the ivory tower.

00:32:24.155 --> 00:32:31.623
You will work with what we give you, which does make to me a better product, a much better product, and consistency is the key there.

00:32:33.834 --> 00:32:35.218
Yeah, it definitely does.

00:32:35.218 --> 00:32:46.903
One of the ones I remember we got I think about 100 in the last release, and one of them is this currency on employee ledgers.

00:32:46.903 --> 00:32:51.440
We didn't have the capability of actually supporting currencies and we got that as a contribution.

00:32:51.440 --> 00:33:06.186
And it's one of these things that just makes so much sense and that somebody is saying you know, we have a lot of customers that work across borders and they need the expenses and whatever on the employees registered in different currencies.

00:33:06.186 --> 00:33:09.799
So now, that was a contribution, it was reviewed, makes sense.

00:33:09.799 --> 00:33:13.118
You know, it's something a lot of users are asking for.

00:33:13.118 --> 00:33:21.160
It's in there, so I can't remember who it was, but anyway, I want to say thank you to the partner, the person that did this.

00:33:22.653 --> 00:33:23.910
There's some great contributions.

00:33:23.910 --> 00:33:30.538
I watch them and see what goes in there because it gives me some insight to what's going on with the application as well.

00:33:30.538 --> 00:33:37.289
Just to step back for a moment on the application roadmap how far out do you plan the roadmap?

00:33:37.289 --> 00:33:52.474
I know that right now, within Directions Asia I saw the screenshot that was shared on Twitter and also by attending Directions North America, I saw the roadmap for 2024, wave 2, where the emphasis is how far out do you plan?

00:33:53.770 --> 00:34:01.000
Yeah, and I'll be careful, because when I say a certain year and so on, then the next question I'll get for somebody, can you share that with me?

00:34:01.000 --> 00:34:13.201
There's a difference between, let me just say that, from planning and then having something that we believe is the right thing to land and share in the community.

00:34:13.201 --> 00:34:15.938
And yeah, of course I could question on that.

00:34:15.938 --> 00:34:21.117
But the thing is we normally sit and plan what is it like?

00:34:21.117 --> 00:34:22.719
Five releases out.

00:34:22.719 --> 00:34:28.626
And now you say, wow, that's a lot, five releases in this, because in this world of agile you don't plan for.

00:34:28.626 --> 00:34:38.192
You know five releases out, but what the planning is, it's really, when you look at the last, it's the helicopter planning, meaning like really high level.

00:34:38.192 --> 00:34:46.496
So again, as we just talked about what the room of the you could say of the product are we going to invest in?

00:34:46.496 --> 00:34:48.280
You know this release, this release.

00:34:48.320 --> 00:35:00.092
So when I say planning and when I say five releases out, it is taking the different areas and see when do we believe this is the right time to invest in this or that area.

00:35:00.092 --> 00:35:04.621
It gets more and more blurry as we go up, but we put up.

00:35:04.621 --> 00:35:11.161
Let me say one thing that's also for sure when we do that, it changes and it changes Again.

00:35:11.161 --> 00:35:14.976
As I said, we had an announcement a month ago and now we have a different keynote.

00:35:14.976 --> 00:35:20.059
It's the same thing with the roadmap we do adjust to what's happening in the market.

00:35:20.059 --> 00:35:30.623
So it's like with Copilot there are areas that we thought we would do a little later on that we're now bringing up because we have high usage.

00:35:30.829 --> 00:35:37.384
Let's say, for example, in the you could say sales area documents and how you create those, how you create lines.

00:35:37.384 --> 00:35:58.181
You've seen some of the first investments we've done here with sales line creation and so on with Copilot, and of course that means that we're focusing on that area and the sales, how you actually go from, you know, create a product to get paid eventually, and that changes a little bit on our planning there.

00:35:58.181 --> 00:36:06.418
But we sit down, all the PMs, and discuss if we wanted to have a focus, you know, from a high-level point of view.

00:36:06.418 --> 00:36:15.610
And when I say two and a half, it's yeah, releases out, that means it's two and a half year, sorry, no.

00:36:15.610 --> 00:36:15.990
What am I saying?

00:36:15.990 --> 00:36:17.954
I say two and a half year, sorry, no.

00:36:17.954 --> 00:36:18.875
What am I saying?

00:36:18.875 --> 00:36:25.844
I say two and a half releases out, that's one and a half year, yes, because we have six months of release cycle.

00:36:25.985 --> 00:36:30.978
Yes, yes, those changes come sometimes, yes, and I don't get it myself.

00:36:30.978 --> 00:36:31.119
Yeah.

00:36:32.590 --> 00:36:47.181
Because when we just have these keynotes and I have to tell everybody that we always say let's focus, let's do this, you know, let's really, you know, narrow in on this release, and I think we do, and I think we do a great job on it.

00:36:47.181 --> 00:36:54.623
But then, of course, you could say is it focused then to release about 60 new features, you know, in a release?

00:36:54.623 --> 00:36:58.621
But again, do remember, there are so many areas.

00:36:58.621 --> 00:37:14.262
There's something for finance, there's something for service, there's something for the you know our platform, there's something for the developers, there's something for the reporting strategy, and when you add that all up, then it becomes a lot, because we want to move on all these.

00:37:14.630 --> 00:37:16.199
We don't want to stand still with reporting and analytics.

00:37:16.199 --> 00:37:17.929
We don't want to stand still with report and analytics.

00:37:17.929 --> 00:37:21.018
We don't want to stand still in the finance area.

00:37:21.018 --> 00:37:37.237
So that's why you see these you could say also roadmaps with a lot of things on, but I think we're pretty controlled on that and good discussions and have a great process on this internally as well.

00:37:37.237 --> 00:37:39.802
For it, that's impressive, it's excellent.

00:37:40.932 --> 00:37:48.778
I think the products evolving well allows many businesses the opportunity for growth within the application as well.

00:37:48.778 --> 00:37:56.559
So as their business dynamic changes, a lot of that functionality within the application can grow with them.

00:37:56.559 --> 00:38:01.992
And, as you mentioned, the co-pilot I don't talk about co-pilot because everybody else talks about, I'm just kidding.

00:38:01.992 --> 00:38:04.623
It's uh, it's amazing thing.

00:38:04.623 --> 00:38:05.144
It's amazing.

00:38:05.144 --> 00:38:24.661
I had conversations this morning about just github co-pilot and how beneficial it is to the development life cycle of the extension, which is important, which which leads us to something else that we were talking about is also some growth opportunities as far as there is with business central.

00:38:24.661 --> 00:38:30.396
Could we dive into that a little bit, pick up where we talked before?

00:38:31.010 --> 00:38:32.454
Yes, for sure, I mean it's.

00:38:32.454 --> 00:38:37.570
It's a very interesting, you know, like questions and so what are the growth opportunities?

00:38:37.570 --> 00:38:41.931
And you're right, I could, you know I could default and roll to begin with.

00:38:41.931 --> 00:38:45.338
You know go pilot, you know lead with that, you know land that match.

00:38:45.338 --> 00:38:53.731
And, as I'm saying, you know it's a growth opportunity in the sense of reeling in the customer or the prospect as well.

00:38:53.731 --> 00:38:57.963
And I think you know you in the customer or the prospect as well.

00:38:57.963 --> 00:39:00.449
And I think you know you saw our keynotes.

00:39:00.710 --> 00:39:07.916
But you will notice there, compared to the past where the keynotes we just did, it was a lot of, you know, business, central business central focus, maybe a little bit on the products we integrate with.

00:39:07.916 --> 00:39:18.012
But if you notice this time, well, we were leading a lot with the M365 products because Co-Pilot is a little different, you know, this time than it's been.

00:39:18.012 --> 00:39:23.657
You know when M365 products has released something you actually need to buy the access to.

00:39:23.657 --> 00:39:25.824
You know to see and explore.

00:39:25.824 --> 00:39:29.438
You know this co-pilot and whether it's Word and Excel and so on.

00:39:29.438 --> 00:39:32.480
So we wanted to land the message of how important it is.

00:39:32.480 --> 00:39:41.639
Also partners use that every day because if partners use that, they're also able to, you know, talk to the prospects about the importance of this.

00:39:41.639 --> 00:39:55.101
And if you just start with the M365, maybe with Business Central data, as you may be seeing, we showed one of these presentations where we had 100,000 rows from Business Central into Excel.

00:39:55.101 --> 00:40:06.030
So now we're not, you know, we're using the capabilities where you work seamlessly with Excel, but now, using Copilot, I could easily find outliers in these 100,000 rows.

00:40:06.530 --> 00:40:11.222
So the opportunity here that we have to think about is really opening the door.

00:40:11.222 --> 00:40:42.782
Opening the door there are still, you know some I'm not saying but some people that will have experienced, you know, gpt as you know something where you ask a funny question and get a funny answer and haven't really seen the benefit necessarily of using it inside a company on the company data and do remember when you're doing that on the company data that's not shared outside the organization but Copilot is then learning on the you could say, the common knowledge in the business.

00:40:42.782 --> 00:40:48.802
So that's a huge opportunity in itself just to land that message, get people to talk about.

00:40:48.802 --> 00:40:59.485
You know, understand, you know if you choose the Microsoft stack that not only in M36, you get the benefit but later you also get it in Business Central.

00:40:59.485 --> 00:41:04.934
So I think that opportunity is really, you could say, the existing market you are going after.

00:41:04.934 --> 00:41:12.782
You can now have a, I would say, a faster door opener, hopefully also faster sales closer.

00:41:12.782 --> 00:41:17.907
You know when you talk about Goal About it, but of course it's not only about that.

00:41:17.907 --> 00:41:30.597
It's also maybe looking at some of the other things that we have, you know, released recently and one of the you know the opportunities that I do believe that is out there and still a little bit untapped.

00:41:30.597 --> 00:41:42.920
But it also requires you as a partner to maybe go into a new territory and that's really the Shopify integration we did some releases ago and we keep improving.

00:41:44.150 --> 00:41:48.382
And from the numbers, we know that there is about 2.8 million.

00:41:48.382 --> 00:41:50.538
Let's take the US market, for example.

00:41:50.538 --> 00:41:53.798
There's 2.8 million shops running Shopify.

00:41:53.798 --> 00:41:54.762
They're actually active.

00:41:54.762 --> 00:41:57.298
We're not talking about people that bought it and don't use it.

00:41:57.298 --> 00:42:01.420
Of course you can start to say, okay, there's many, small, there's many.

00:42:01.420 --> 00:42:05.251
The funny thing is a lot of these has grown In the US.

00:42:05.251 --> 00:42:09.902
We know Shopify takes care of about 10% of all commerce transactions there.

00:42:11.369 --> 00:42:31.278
So that opportunity you know going to first I would actually a business central partner start by going to the Shopify customers already using Shopify, because one of their, you could say problems as they have grown is really having a tight integration to the back office, and that's what business central offers with Shopify.

00:42:31.278 --> 00:42:33.271
So I heard from some partners that have been doing this.

00:42:33.271 --> 00:42:35.052
So I heard from some partners that have been doing this.

00:42:35.052 --> 00:42:42.617
They say that the number one value prop is actually the setup of having Shopify integrate to Business Central.

00:42:42.617 --> 00:42:53.523
It's a funny value prop in itself because often it's about, you know, I wouldn't, of course, forget the control of your finances, control of your inventory or regulatory reporting.

00:42:53.523 --> 00:42:57.846
That's what you, of course, you course, have to mention as the door opener.

00:42:57.846 --> 00:43:14.782
But then when you then talk to them about did you know that I can link these two products together in like five minutes, then they are all just surprised by that, and that's often actually what gets to the next conversation.

00:43:15.329 --> 00:43:28.188
We've had partners that did some call-downs like this, took the list, found out who was using Shopify and did in four months, 55 customers, new customers.

00:43:28.188 --> 00:43:43.498
So going after that opportunity that is out there, it's a world we don't see because we are in the business central world and we know our industry, we know our customers, but there's also a world out there of a lot of Shopify's that I would actually say it this way.

00:43:43.498 --> 00:43:46.559
We need to do them a favor.

00:43:46.559 --> 00:43:48.835
They need to be integrated to business central.

00:43:48.835 --> 00:43:50.815
That's how I see it.

00:43:50.815 --> 00:43:56.119
Because they are growing, they need to be in control of these things I just mentioned.

00:43:56.119 --> 00:43:58.835
So they are growing, they need to be in control of of these things I just mentioned.

00:43:58.835 --> 00:44:04.496
So that's one opportunity I would, you know, yeah, suggest for some people at least not everybody, but some people to look into that's a good way.

00:44:04.516 --> 00:44:06.163
There are a lot of opportunities.

00:44:06.163 --> 00:44:12.275
The co-pilot that you had mentioned and I'm happy that you had mentioned it that's in conversation.

00:44:12.275 --> 00:44:20.152
Co-pilot is everywhere and I think a lot may not fully understand what it is, how it works, it's.

00:44:20.152 --> 00:44:26.978
It's almost like it's a buzzword of the day and you could almost say co-pilot and it will show up and people will stand in line to talk with you.

00:44:26.978 --> 00:44:40.416
But with co-pilot and data and I'm happy that you had mentioned that the co-pilot is only analyzing your data- your tenant it's not taking your data and your tenant it's not taking your data and your tenant it's not taking your data and sharing it.

00:44:41.590 --> 00:44:55.375
Another question or conversation that I've had, which, again now that it's becoming more popular, users and partners, prospects and customers are having the same types of conversations or there's more conversation about it.

00:44:55.375 --> 00:45:06.117
So we just identified that it's tenant-only data, which is wonderful, because you don't want your information potentially shared or have somebody get into it.

00:45:06.117 --> 00:45:09.577
What about within the application?

00:45:09.577 --> 00:45:18.911
Not to talk about the growth strategies, but it's just a question and it comes from a conversation I had last week what about user permission with that data?

00:45:18.911 --> 00:45:23.440
Does co-pilot honor the user's permission at this point or is that?

00:45:23.440 --> 00:45:29.530
And if it's out of the scope of this conversation, we can continue with the growth strategies, but it's something that came up, uh.

00:45:29.530 --> 00:45:30.291
So often.

00:45:30.711 --> 00:45:33.713
No, that's a super valid, you know question.

00:45:33.713 --> 00:45:36.934
I think you know what you.

00:45:36.934 --> 00:45:40.677
Often, when we do this, you know the demonstration and we show the product.

00:45:40.677 --> 00:46:02.523
What people do not see is all the effort and time we spent which we rightfully spent actually making sure you know it is secure, that privacy is respected, that you know permissions are expected, that no user can you know see data, that they should not have access to that no user I mean so it respects.

00:46:02.523 --> 00:46:09.291
You know that's the fundament of, fundamentally, you know the requirement for anything we ship.

00:46:09.291 --> 00:46:17.929
You know, and I would actually say we spend more time on that than you know you could say the business process part of it and optimizing that on that than you know you could say the the business process part of it and optimizing that.

00:46:18.291 --> 00:46:22.849
Because, as you know, microsoft, as we say is, is built on trust.

00:46:22.849 --> 00:46:24.271
People have to trust microsoft.

00:46:24.271 --> 00:46:41.862
We cannot, we cannot have any crack in this and we don't because there are so many processes and checkpoints and I you know that we do to make sure that we deliver something that is just respecting security, privacy and any risk out there.

00:46:41.862 --> 00:46:55.981
So, yeah, that's a super valid question and I think that's part of the adoption here, as you're saying and I do get why people are asking that question People are, of course, afraid of whether your data is shared.

00:46:55.981 --> 00:47:00.639
I mean, what if you're writing a secret project name and the competitor could do that?

00:47:00.639 --> 00:47:01.811
That's not going to happen.

00:47:01.811 --> 00:47:11.813
It is so important that you can trust you know your company co-pilot to only use that data and that's, yeah what we spend.

00:47:12.976 --> 00:47:26.663
I'm happy to hear the official answer that it respects the individual, not only your tenant boundaries, but also the user's boundaries and what they have access to in the system.

00:47:26.663 --> 00:47:33.878
It's important for the adoption of it to understand that which is great, and then also the growth strategies or the growth opportunities.

00:47:33.909 --> 00:47:39.893
I think there are many opportunities with the application and you had mentioned also looking at.

00:47:39.893 --> 00:47:55.543
I like the strategy of looking at and you had mentioned Shopify or even other customers work with people who have an existing need and then they can get the Shopify integration in the Business Central ERP SMB software as part of that whole process.

00:47:56.351 --> 00:48:10.481
It's a good way to adopt and then, with that, also the integration to the whole M365 stack with Teams, integration with the ability to use Power Platform, power Automate.

00:48:10.481 --> 00:48:16.250
See, this is where I'm happy that I'm getting to the end of my life, because there's just so much where I'm happy that I'm getting to the end of my life, because there is just so much.

00:48:17.092 --> 00:48:30.996
No, you and sometimes we have these, you know, missed opportunities because you could say we spent a couple of releases communicating it and then it's buried under you know whatever material and nothing.

00:48:30.996 --> 00:48:32.019
But you mentioned Teams.

00:48:32.019 --> 00:48:43.813
We're the only product where you can actually if again respecting user permissions and everything you can read data in Business Central for free for a user that is licensed for Teams.

00:48:43.813 --> 00:48:54.494
If the user is licensed for Teams and in the same environment as Business Central is installed, then they can read data, again respecting permission sets and everything.

00:48:54.494 --> 00:48:58.641
But often you would have to pay for that.

00:48:58.641 --> 00:49:10.268
Not often you have to pay for that in other ERP products there is no free, and not only that, there are a few actions you can also perform through that free access.

00:49:10.268 --> 00:49:18.318
There you can get a business central client open from if you are within Teams and do not have a business central license.

00:49:18.318 --> 00:49:21.311
If you have the permission, you get that Again.

00:49:21.690 --> 00:49:27.202
What a great opportunity to talk to people about when you sometimes get into licensing and licensing thing.

00:49:27.202 --> 00:49:38.597
Talk about the things that we can offer that nobody else offers out there, because maybe the company has a lot of users that could benefit at least from you know, discussing the data.

00:49:38.597 --> 00:49:41.045
Not working with the data, but discussing it.

00:49:41.045 --> 00:49:44.458
See an item card in the full size and the information there.

00:49:44.458 --> 00:49:45.713
That's so.

00:49:45.713 --> 00:49:48.530
Yeah, you know there's so many and you said M360.

00:49:48.530 --> 00:49:54.041
There's, of course, also the recent D365 field service opportunity.

00:49:54.041 --> 00:49:57.563
Now you know, as you know, we announced that in this release.

00:49:58.105 --> 00:50:04.222
Yeah, integration so yeah, and the opportunity there is really about.

00:50:04.222 --> 00:50:16.139
You know a whole, you could say, market out there of frontline workers that needs to be digitalized because a lot of frontline workers out there may be doing the service checking something off.

00:50:16.139 --> 00:50:22.943
They've been used to do that on pen and paper or you know some app that wasn't really integrated and so on.

00:50:22.943 --> 00:50:31.492
That's what we have now with the field service integration, because they deliver that great frontline experience, even also with Copilot, you can speak to the phone, you can get a summary with Copilot of the work order.

00:50:31.492 --> 00:50:35.679
Speak to the phone, you can get a summary with Copa Live Pilot of the work order.

00:50:35.679 --> 00:50:41.226
And then, by integrating to Business Central, field service has the you know, inventory on stock.

00:50:41.226 --> 00:50:44.940
It has, you know, direct invoice control and so on.

00:50:44.940 --> 00:50:47.650
So again, another great opportunity there.

00:50:48.231 --> 00:50:50.956
Just to go back on that, m365 and Teams.

00:50:50.956 --> 00:51:07.885
You know I did a session in Dynamics User Group regarding working together with Business Central teams and Outlook and sometimes when you do those presentations or sessions, I have to tell myself that not everyone knows it.

00:51:07.885 --> 00:51:13.983
So I did a quick survey during the session and I asked you know, do everyone use Teams here?

00:51:13.983 --> 00:51:21.760
Everyone raised their hands right by 99.99% and I made an assumption that people are already doing it.

00:51:21.760 --> 00:51:28.440
You know BC and Teams and when I asked the question and they all said no, I didn't know you could do that.

00:51:28.440 --> 00:51:43.925
So I went through my whole session and it was very surprising that there's still a lot of customers that don't even realize that's capable of how you can work all together in a single application, minimizing, app switching.

00:51:43.965 --> 00:51:44.184
Yeah.

00:51:44.385 --> 00:51:44.885
It's amazing.

00:51:45.827 --> 00:51:47.894
Yes, that is a challenge.

00:51:47.894 --> 00:51:50.175
I think it's a challenge.

00:51:50.175 --> 00:52:08.083
I don't want to go down the whole documentation road because I think we'll just step into a black box the documentation and partner and customer awareness, partner, customer prospect awareness in the documentation.

00:52:08.083 --> 00:52:12.309
We could have several volumes of books to talk about that.

00:52:12.309 --> 00:52:12.889
Yeah, to talk about that.

00:52:14.172 --> 00:52:22.278
Yeah, I think there, you know, I see a little bit of light in the end of the tunnel and I don't think it's a train coming towards me.

00:52:22.278 --> 00:52:24.418
But you know, real revelation there.

00:52:24.418 --> 00:52:27.954
And one of the things again, and, believe it or not, I'm going to say Copilot.

00:52:27.954 --> 00:52:31.329
But you know, when I see some of the results.

00:52:31.329 --> 00:52:33.711
Now we have, with you know on a tooltip.

00:52:33.711 --> 00:52:35.195
Now, now we have with you know on a tooltip.

00:52:35.195 --> 00:52:43.704
Now it's called Ask Copilot, it's not called Learn More, which was actually, you know, the same as Confuse Me More, because that was what you got.

00:52:43.744 --> 00:52:49.478
As I said, I got confused every time I clicked Learn More and there was actually a technical reason for it.

00:52:49.478 --> 00:53:00.016
The reason was that we did, in most cases, send people to page help and not to field help, because we didn't have necessarily that specific field explained.

00:53:00.016 --> 00:53:03.188
Or if we did, we still sent them to page help.

00:53:03.188 --> 00:53:14.422
But if you're sitting with a field and you want to learn more, then it doesn't make sense that if it's learn more on customer credit limit, and then you land on a page saying this is how you create a customer.

00:53:14.422 --> 00:53:30.798
That has changed now with Ask Copilot, because it goes through and finds that specific area If you want to learn about costing method, we have a fantastic article that, even with graphics, show what's the difference between FIFO and LIFO.

00:53:30.798 --> 00:53:37.043
And all that Funny thing is people didn't find it with Learn More because they landed on inventory page.

00:53:37.043 --> 00:53:38.635
Now they actually get it.

00:53:38.635 --> 00:53:49.322
If you try this out, go to costing methods, ask how valid Comes up with a nice description of what the field is, and you can click a direct link and get this beautiful documentation on this.

00:53:49.322 --> 00:54:12.659
So I see you know actually a lot of yeah, you could say improvements in that area going forward and hopefully you know that is the way that you know documentation will consume, because, yes, it is difficult to come up with a genius way of structuring this, finding the right way to searching it, finding the right result.

00:54:12.949 --> 00:54:16.956
But that's where Copilot kicks in, and I'm really you know now.

00:54:16.956 --> 00:54:27.851
I even said to one of my PMs this day I would have loved to see what's actually the attraction of new users and ask Copilot versus, you know, learn more.

00:54:27.851 --> 00:54:36.114
In the past I would have expected if you tried to learn more twice, you'd never use it again because you were so confused that you'd never go back twice.

00:54:36.114 --> 00:54:37.878
You never use it again because you are so confused that you never go back.

00:54:37.878 --> 00:54:48.512
So I think now with new users we would see that monthly active tenants of that and I can tell you right now the number is.

00:54:48.512 --> 00:54:53.802
We cannot share numbers, but it's really surprising how much is used these days because people found out finally I can get help to my problems.

00:54:54.931 --> 00:54:57.436
You can put me in that bucket of using.

00:54:57.496 --> 00:54:59.601
Learn more twice and never going back.

00:55:00.003 --> 00:55:00.202
Yes.

00:55:01.590 --> 00:55:08.760
Because not to make a joke or to be cool, but I called it the learn less button because I was more confused.

00:55:09.541 --> 00:55:14.001
Yes, it was learn less because I was more confused after I was there.

00:55:14.730 --> 00:55:16.253
I almost sometimes forgot One time I forgot, I think, what I was looking for.

00:55:16.253 --> 00:55:16.614
But I do, I almost sometimes forgot.

00:55:16.614 --> 00:55:17.711
One time I forgot, I think, what I was looking for.

00:55:17.711 --> 00:55:20.074
But I do like the ask co-pilot.

00:55:20.074 --> 00:55:21.719
Um, I see I could go.

00:55:22.289 --> 00:55:24.092
I try not to go too far down these holes.

00:55:24.092 --> 00:55:27.882
But ask co-pilot, is it on the roadmap?

00:55:27.882 --> 00:55:31.706
See, now I'm going to put you there so that you could put your own information in there.

00:55:31.706 --> 00:55:38.349
So now we have the Ask Copilot, which Microsoft Learn is another area that the community can contribute to.

00:55:38.349 --> 00:56:02.688
I know there's a big push with Kenny and another group of individuals to continually add information, to learn as well, as the community members have been adding information, even correcting small things, which is again another way that it makes it better, and it's my understanding please correct me if I'm wrong that Ask Copilot uses Learn as a primary data source to come up with the information.

00:56:02.688 --> 00:56:08.807
Now, within an organization, there's a lot of options, a lot of ways to set things up.

00:56:08.807 --> 00:56:22.375
What is the plan, if there is a plan, for me to be able to put my own information in so that if my employees or co-workers are looking for assistance on how to enter a sales order.

00:56:22.375 --> 00:56:26.565
I can give them specific information how I want it done within my organization.

00:56:27.146 --> 00:56:29.775
Yeah, so let's start again.

00:56:29.775 --> 00:56:35.860
As you also know, again, I can't even, didn't it say now, I should remind you, you saw the roadmap as well.

00:56:35.860 --> 00:56:38.701
I can't remember if we put, but, but let's just start with the.

00:56:38.701 --> 00:56:44.405
You know the, the fundamental, you know you could say strategy of of business central.

00:56:44.405 --> 00:56:50.867
As you know, we, we, we, we have a great product because we have great partners, we have great ISVs.

00:56:50.867 --> 00:57:06.927
I mean, yes, we do develop a great product, but fundamentally we make sure that whatever we do in Business Central, you can extend that, Sure, there's an area here or there or whatever, but we're always looking into how can partners add their IP on top.

00:57:07.315 --> 00:57:22.489
It doesn't make sense if we didn't do that, because we will never be able to deliver that fish farm solution or winery solution or car manufacturer retail solution.

00:57:22.489 --> 00:57:23.615
I mean we would not.

00:57:23.615 --> 00:57:27.021
That's just so many industries, so many verticals.

00:57:27.021 --> 00:57:48.887
So if we now have Copilot that has to help and tell how to do things, again it doesn't make sense for us if we only say no, it can only be done on top of our documentation Because, as you know, our documentation is the foundation for all these solutions and verticals people build on top.

00:57:48.887 --> 00:57:54.985
So of course we are looking into this and, yeah, I can't even remember if we said it.

00:57:54.985 --> 00:57:59.266
I'm almost about to open the roadmap to just I have the roadmap.

00:57:59.715 --> 00:58:00.800
I did open the roadmap.

00:58:00.800 --> 00:58:02.201
I don't want you to say anything.

00:58:02.201 --> 00:58:04.382
I don't want to put you in a position to say anything.

00:58:05.579 --> 00:58:06.563
So you knew it was there.

00:58:06.563 --> 00:58:09.682
Great, no, no, no, I just pulled it up as we spoke.

00:58:12.295 --> 00:58:12.856
And from the generative AI.

00:58:12.876 --> 00:58:15.101
This is from the slide that was presented at Directions Asia that I'm reading.

00:58:15.101 --> 00:58:32.710
Generative AI is to create orders from chat page summarization, payment reconciliation, e-document, more matching, drag and drop on prompt dialogue, late payment prediction new model that was out before Third party knowledge basis there you go More languages.

00:58:32.710 --> 00:58:40.789
So, again so this is the slide from Directions Asia that was shared for 2024 release wave.

00:58:40.789 --> 00:58:49.925
Two investment areas, so I'm assuming third party knowledge basis would be where I could have the opportunity to put my own information.

00:58:50.054 --> 00:58:56.405
See right there now, now this whole conversation yeah, I, I should have just remembered again.

00:58:56.425 --> 00:59:00.402
There's so much information, I forgot I should as well, because I was part of making that column.

00:59:00.402 --> 00:59:06.438
So you know it's like and I and of course know that we can discuss in ups and downs and whatever, but it's always.

00:59:06.438 --> 00:59:10.280
The subtleness here is in what did we communicate externally?

00:59:10.280 --> 00:59:22.972
And the roadmap we show at these events are actually just hitting the street some months before we actually do the you could say the official finalized release plan.

00:59:22.972 --> 00:59:24.541
So things can change a little bit.

00:59:24.541 --> 00:59:28.206
And also, even with the release plan, that's of course, always the disclaimer.

00:59:28.206 --> 00:59:32.663
So that's why you know there's more concrete around it.

00:59:32.663 --> 00:59:35.449
When we get to, is it june or july?

00:59:35.449 --> 00:59:40.965
I think you know the, the next wave roadmap gets out on the street.

00:59:41.025 --> 00:59:41.947
Yeah, I'm excited.

00:59:41.947 --> 00:59:44.275
It seems like there is really full steam behind this.

00:59:44.275 --> 00:59:45.336
Co-pilot I'm.

00:59:45.336 --> 00:59:48.121
I say this every episode and with every conversation.

00:59:48.121 --> 00:59:57.795
I'm waiting that I can open up business central for a new customer and say, set up a base system for a manufacturer of light bulbs, and it will fill up.

00:59:57.795 --> 01:00:02.074
All the number, series will fill, a chart of accounts will fill up, you know customer templates.

01:00:02.235 --> 01:00:03.016
It will fill up a number.

01:00:03.016 --> 01:00:10.766
It's a long way from there, but even if you did it with a number of sections, you know, and I've previewed some partners creating some tools such as this.

01:00:10.766 --> 01:00:20.146
Where it's, it's nice to just say you know, create something, yeah, and it will go ahead and fill in all the information for you, as well as the opportunity to analyze data.

01:00:20.146 --> 01:00:23.260
Now, I'm excited that.

01:00:23.280 --> 01:00:26.028
Yeah, yeah, like that, something's so small.

01:00:26.028 --> 01:00:28.356
Yeah, yes, just one line there.

01:00:28.356 --> 01:00:36.070
I would like that in ideas and then it it's the top, then I have to deliver, that's amazing Makes sense.

01:00:37.237 --> 01:00:37.878
No, I'm excited.

01:00:37.878 --> 01:00:38.721
There's a lot of features.

01:00:38.721 --> 01:00:40.786
Now you have me down the rabbit hole of the roadmap.

01:00:41.735 --> 01:00:43.858
Maybe you will contribute it after this call.

01:00:43.858 --> 01:00:46.481
That will be all great, we'll look at it.

01:00:46.481 --> 01:00:47.744
I have done.

01:00:48.324 --> 01:00:53.130
I have made a few or a couple of small contributions to the pilot.

01:00:53.130 --> 01:00:55.764
I will do more.

01:00:55.764 --> 01:01:01.126
Unfortunately, this first quarter of the year many of us will call, you know, conference season or other types.

01:01:01.126 --> 01:01:06.047
It just gets difficult with time, with life and work.

01:01:06.047 --> 01:01:08.543
But I want to get back into it now that things are leveling out.

01:01:08.543 --> 01:01:12.465
For now, because I enjoy adding it For now.

01:01:12.465 --> 01:01:19.025
It seems like every day I think it levels out, and then those hills come back for us, which is good.

01:01:20.277 --> 01:01:21.643
It's in a positive manner.

01:01:21.643 --> 01:01:28.143
So, Noah, we appreciate your discussion on the application roadmap, as well as some growth opportunities.

01:01:28.143 --> 01:01:43.222
Are there any other strategies that you share that come to mind that you would like to relate to either partners, customers or prospects, as far as product adoption, product use and how to ensure you get the most out of the product?

01:01:48.242 --> 01:01:51.389
Yeah, so I could start again going off in different directions.

01:01:51.389 --> 01:01:55.706
I mentioned one of these AKAs before, bc Ideas.

01:01:55.706 --> 01:02:00.981
There's the other one that when you forget them all there's always and we should actually have that.

01:02:00.981 --> 01:02:07.721
I should even have that on my back here, you know, like backstrop and say have somebody make a Lego of it?

01:02:08.182 --> 01:02:17.527
Yes, Actually, yes, you do that, but that is, of course, the BC All page akams.

01:02:17.527 --> 01:02:49.202
That's where we try and I have to say there is so much information, but we try to always put there the top links to, you know, the both opportunities, but also what's hot off the press, uh, in terms of where you could go and learn more and it could be, um, you know now I don't want to compete with your, your podcast here, but there's, of course, also our youtube channel, you know, like you know, but again, what is, how do I find that?

01:02:49.202 --> 01:03:00.063
And whatever bc all will then have a link to that, they will be in the top right now on that page, because that's hot off the press, that we finally got to youtube no, that's great and we don't look at.

01:03:00.123 --> 01:03:01.545
You can talk about that.

01:03:01.545 --> 01:03:04.820
We did speak with vincent about uh, you know, bc under the hood.

01:03:04.820 --> 01:03:09.699
Yeah, I also promote the the business central launch event where there's a lot of good information.

01:03:09.699 --> 01:03:12.146
We do this for the community.

01:03:12.146 --> 01:03:27.663
We want to share information, get to know members of the community, so anything that can help a prospect, customer, partner or anyone I guess that covers everybody customer, prospect, partner or Microsoft employee get more out of the application.

01:03:27.663 --> 01:03:32.920
We want to share that information because that's why we do what we do with this podcast.

01:03:33.541 --> 01:03:48.456
Good, good, and that's where you mentioned, I mean, because if you go to the YouTube channel, as you say, there you will have the launch event as well in these nights bits of you know the different areas and I think that's a great way to, of course, consume in some videos there.

01:03:48.456 --> 01:03:55.724
We of course, course, discussing could we make them even smaller, even shorter, even more focused, because there is a lot of content.

01:03:55.724 --> 01:04:25.862
I think if you, if anything, now going to bc, all again, there's a lot of information, but of course, the release plans, I mean bc release plan, uh, that's that's where we always, we always change that akamsbcreleaseplan to the latest and even going to these events, I do get quite a few questions about features we have released and where it very specifically says in the release plan that we've done it and I'm like, I totally respect.

01:04:25.862 --> 01:04:27.795
I also don't read all kind of documentation comes out from all the products.

01:04:27.795 --> 01:04:36.021
But I think working with Business Central read all kind of documentation comes out from all the products, but I think, you know, working with Business Central, it's a good investment.

01:04:36.021 --> 01:04:44.907
Just, you know, sit down and then read about what's really, you know, coming in this release and what's the story, what's the screenshot.

01:04:44.907 --> 01:04:51.012
You won't need everything, but it will prep you, as oh, didn't I read about this?

01:04:51.012 --> 01:04:54.422
And then you know you can always go back.

01:04:54.422 --> 01:05:02.123
So I think that's where it starts and then, yeah, that's my recommendation Always be on top of the release plan.

01:05:02.355 --> 01:05:13.844
Like you know, I got a question and I do think because we have so much there was this partner asking do you actually now allow, if you have a premium user to log into an Essentials environment?

01:05:13.844 --> 01:05:18.306
Because we had this rule about if you have them in the same environment, you could do that.

01:05:18.306 --> 01:05:30.030
There was one line on our keynote somewhere, but it is in the release plan very well explained that you now can do that if you have, within the same environment, license both premium and Essentials users.

01:05:30.030 --> 01:05:32.842
So that's explained.

01:05:32.842 --> 01:05:41.083
We we didn't do that in the past due to some risk of you know, doing something with premium that essentials couldn't do, but it is explained in.

01:05:41.083 --> 01:05:52.528
These subtle things are important because else we would have a partner that hadn't seen that say no, you cannot, we have to have to do this completely in a different way.

01:05:52.528 --> 01:05:56.224
So just sell premium users to all of them.

01:05:57.135 --> 01:06:07.481
It is important to stay up to date as a partner with all that information, because the information is available for everybody, so you want to make sure that you're relaying truthful information.

01:06:07.481 --> 01:06:15.684
If somebody were to search themselves for it, you were laying truthful information if somebody were to search themselves for it.

01:06:15.684 --> 01:06:26.130
Yeah, I do need to find who does the licensing, because I think we could have a 4 000 hour podcast on microsoft licensing and, you know, a deep dive under the hood of which license do you sell for?

01:06:26.693 --> 01:06:32.686
scenario can you just ask co-pilot, I'm sure hopefully one day we will be easier.

01:06:33.248 --> 01:06:41.442
I have a customer that wants to use power automate to do this, and then they have to use, you know, an e-commerce site that goes to the api but they're only reading data.

01:06:41.442 --> 01:06:42.746
Which license do they need?

01:06:42.746 --> 01:06:44.759
But now, if they want to write data, what do they do?

01:06:44.759 --> 01:06:46.322
See, this is what we know.

01:06:46.322 --> 01:06:48.226
It's, it's, it's going on.

01:06:48.226 --> 01:06:50.976
No, it's it's important to keep up with the information.

01:06:51.418 --> 01:06:52.358
Yes, it is.

01:06:52.358 --> 01:06:53.840
And now you say that.

01:06:53.840 --> 01:07:09.382
I just want to say that now I didn't bring my power to this meeting, but I got 28 minutes left here and I guess we are almost to the end, but I don't want to just cut off, so just, so you know, no, it's okay, it's okay.

01:07:09.443 --> 01:07:12.588
We do appreciate you taking the time to speak with us.

01:07:12.588 --> 01:07:17.115
Again, time is valuable.

01:07:17.115 --> 01:07:17.797
Time is the currency of life.

01:07:17.797 --> 01:07:18.940
Once you spend it, you can't get it back.

01:07:18.940 --> 01:07:23.028
So anyone who takes the opportunity to speak with us, we are more appreciative than we can relay.

01:07:23.028 --> 01:07:37.121
And again we would like to thank you for all that you do for the Business Central community, all of the information you put out and we see more with these conversations the true passion and transparency from everybody in the Business Central team.

01:07:37.121 --> 01:07:57.757
On the Business Central team, whether it's the project managers right down to the engineers, are really doing their best to make it a better product for everybody and have transparency so that we all know what is coming with the product, what's happening with the product positive and if there are any issues, which is helpful With that.

01:07:57.757 --> 01:08:06.166
If anybody would like to have additional conversations or questions for you, how would someone get in contact with you?

01:08:07.355 --> 01:08:07.936
So this is.

01:08:07.936 --> 01:08:17.109
You know, I'm always open about also email address and other things, because every time I share it I think, oh, now I'm going to be flooded.

01:08:17.109 --> 01:08:19.621
But I'm actually, you know, open to anybody.

01:08:19.621 --> 01:08:21.506
Of course there's ideas, you can always go there.

01:08:21.506 --> 01:08:39.462
But if there is a specific thing that somebody you know listened to this and I said something that is completely opposite of where they think it should be done, or whatever, then you know, write to my email address and I assume that you know in the recording you can see my name there, I mean J-A-N-N-I-K.

01:08:39.462 --> 01:08:40.556
It's you know.

01:08:40.556 --> 01:08:45.743
And then just with a, b and then at Microsoftcom, so YannickB at Microsoftcom.

01:08:45.743 --> 01:08:47.360
That's where people can write.

01:08:47.734 --> 01:08:53.087
You know, I always like to make friends with partners, with whoever.

01:08:53.087 --> 01:08:58.599
If there is a customer out there that would listen to it, you know, feel free to write.

01:08:58.599 --> 01:09:03.925
If there's something we could do differently, if there's something we should improve, whatever.

01:09:03.925 --> 01:09:10.444
And I also just want to say thank you to you guys, brian and Christopher here, for actually inviting me.

01:09:10.444 --> 01:09:13.461
Thank you to you guys, brian and Christopher here, for actually inviting me.

01:09:13.461 --> 01:09:19.243
I love to have these chats and we all talk to each other offline, but do let me know if you want other guests here.

01:09:19.243 --> 01:09:28.310
You know I can help you again, also with my team, because you know this is a nice you know, conversation and casual, and I like that.

01:09:28.310 --> 01:09:34.559
And great questions, by the way, conversation and casual, and I like that.

01:09:34.559 --> 01:09:37.532
And great christians, by the way, um, uh, so let's see if my inbox is now flooded because there's something I shouldn't have said.

01:09:37.551 --> 01:09:37.893
You never know.

01:09:37.893 --> 01:09:38.255
You never know.

01:09:38.255 --> 01:09:52.115
I don't think you said anything that you shouldn't have said and, um, I will speak with you after about another initiative I have as far as talking with individuals of the team that I have to follow up with some members there.

01:09:52.435 --> 01:09:53.539
But again, thank you for your time.

01:09:53.980 --> 01:09:56.475
We appreciate it and I hope you enjoy the rest of your day.

01:09:56.475 --> 01:09:56.997
Ciao, ciao.

01:09:57.720 --> 01:09:58.381
The same to you.

01:09:58.381 --> 01:09:59.244
Thank you very much.

01:10:00.108 --> 01:10:07.188
Thank you, chris, for your time for another episode of In the Dynamics Corner Chair, and thank you to our guests for participating.

01:10:07.515 --> 01:10:09.019
Thank you, brad, for your time.

01:10:09.019 --> 01:10:12.466
It is a wonderful episode of Dynamics Corner Chair.

01:10:12.466 --> 01:10:15.961
I would also like to thank our guests for joining us.

01:10:15.961 --> 01:10:18.975
Thank you for all of our listeners tuning in as well.

01:10:18.975 --> 01:10:33.625
You can find Brad at developerlifecom, that is D-V-L-P-R-L-I-F-E dot com, and you can interact with them via Twitter, dprlife.

01:10:33.625 --> 01:10:46.948
You can also find me at matalinoio, m-a-t-a-l-i-n-o dot i-o, and my Twitter handle is matalino16.

01:10:46.948 --> 01:10:50.579
And see, you can see those links down below in their show notes.

01:10:50.579 --> 01:10:51.925
Again, thank you everyone.

01:10:51.925 --> 01:10:53.501
Thank you and take care.
Jannik Bausager Profile Photo

Jannik Bausager

Principal Group Program Manager