WEBVTT

1
00:00:03.520 --> 00:00:06.160
- Welcome to episode 435

2
00:00:06.160 --> 00:00:09.439
- of the Microsoft Cloud IT Pro podcast recorded

3
00:00:09.439 --> 00:00:12.179
- live on 08/24/2026.

4
00:00:12.240 --> 00:00:14.054
- This is a show about about Microsoft three

5
00:00:14.054 --> 00:00:16.214
- sixty five and Azure from the perspective of

6
00:00:16.214 --> 00:00:18.535
- IT pros and end users, where we discuss

7
00:00:18.535 --> 00:00:20.614
- a topic or recent news and how it

8
00:00:20.614 --> 00:00:23.494
- relates to you. Today, Ben and Scott take

9
00:00:23.494 --> 00:00:26.079
- a lap around what's new in Power BI,

10
00:00:26.140 --> 00:00:28.620
- starting with the two MCP servers now in

11
00:00:28.620 --> 00:00:31.339
- preview, one local and one remote, that can

12
00:00:31.339 --> 00:00:33.979
- help you clean up your data model, write

13
00:00:33.979 --> 00:00:36.219
- decks for you, and turn a messy pile

14
00:00:36.219 --> 00:00:39.695
- of tables into an actual usable semantic model.

15
00:00:39.755 --> 00:00:41.515
- From there, we dive into how you can

16
00:00:41.515 --> 00:00:43.135
- start using Power BI

17
00:00:43.675 --> 00:00:44.655
- with GitHub,

18
00:00:45.195 --> 00:00:47.135
- DevOps, or other Git repositories

19
00:00:47.594 --> 00:00:50.655
- to help you manage updates, changes, and even

20
00:00:55.899 --> 00:00:56.399
- Another

21
00:00:57.019 --> 00:00:57.519
- sweltering

22
00:00:58.059 --> 00:01:00.519
- 90 degree day in Florida. Before the sun

23
00:01:00.519 --> 00:01:02.379
- even comes up, this is just not

24
00:01:03.015 --> 00:01:05.094
- I don't know why people decided Florida was

25
00:01:05.094 --> 00:01:06.155
- a good place to live.

26
00:01:08.614 --> 00:01:10.614
- Who knows? First place they landed and they

27
00:01:10.614 --> 00:01:12.555
- thought there was a fountain of youth here.

28
00:01:13.015 --> 00:01:14.534
- Yeah. It turns out it was not a

29
00:01:14.534 --> 00:01:16.135
- fountain of youth. It was a fountain of,

30
00:01:16.135 --> 00:01:17.994
- like, mosquito diseases, but

31
00:01:18.670 --> 00:01:20.829
- same difference. Anyways, we're not here to talk

32
00:01:20.829 --> 00:01:22.209
- about heat, humidity,

33
00:01:22.590 --> 00:01:23.090
- weather,

34
00:01:23.390 --> 00:01:25.709
- but all of that ties into data, which

35
00:01:25.709 --> 00:01:27.709
- we are gonna talk about. Well, how was

36
00:01:27.709 --> 00:01:29.629
- that? Yeah. You're getting so much better at

37
00:01:29.629 --> 00:01:31.569
- these. I'm trying, Scott.

38
00:01:32.245 --> 00:01:34.564
- Oh, and a trip down memory lane. Like,

39
00:01:34.564 --> 00:01:36.005
- this is a product that's been out for

40
00:01:36.005 --> 00:01:37.365
- a while, and I don't know that we've

41
00:01:37.365 --> 00:01:40.805
- talked about this recently. We haven't. We've talked

42
00:01:40.805 --> 00:01:42.885
- about well, we're gonna talk about Power BI

43
00:01:42.885 --> 00:01:45.590
- today. So we're gonna talk about some new

44
00:01:45.590 --> 00:01:47.590
- things that have come in Power BI. I

45
00:01:47.590 --> 00:01:49.430
- think you were introducing me to some things,

46
00:01:49.430 --> 00:01:51.450
- and I was introducing you to some things.

47
00:01:51.750 --> 00:01:54.009
- And it was just very interesting how much

48
00:01:54.069 --> 00:01:54.810
- it has

49
00:01:55.189 --> 00:01:55.689
- changed

50
00:01:55.989 --> 00:01:56.810
- over time.

51
00:01:57.224 --> 00:01:58.905
- And I think if you've been stuck in

52
00:01:58.905 --> 00:02:01.484
- your ways of using Power BI

53
00:02:02.105 --> 00:02:04.424
- in, like, one modality, like, there's a whole

54
00:02:04.424 --> 00:02:05.944
- bunch of new things that are out there

55
00:02:05.944 --> 00:02:07.645
- and available to you from

56
00:02:08.104 --> 00:02:08.925
- team collaboration

57
00:02:09.544 --> 00:02:10.685
- to MCP

58
00:02:11.064 --> 00:02:11.564
- servers,

59
00:02:12.189 --> 00:02:12.689
- like,

60
00:02:13.150 --> 00:02:14.370
- plural, that that can

61
00:02:14.669 --> 00:02:15.569
- help you out

62
00:02:15.949 --> 00:02:17.169
- and accelerate

63
00:02:17.550 --> 00:02:18.050
- your

64
00:02:18.430 --> 00:02:19.250
- pretty visualizations

65
00:02:19.550 --> 00:02:21.389
- in Power BI. Well, really, your, like, data

66
00:02:21.389 --> 00:02:24.030
- analysis, right, and and bringing things to bear.

67
00:02:24.030 --> 00:02:25.835
- Yeah. I would say just everything.

68
00:02:26.455 --> 00:02:27.895
- Like, for me, I don't spend a ton

69
00:02:27.895 --> 00:02:29.614
- of time in Power BI. Every once in

70
00:02:29.614 --> 00:02:30.935
- a while, it comes up or I'm working

71
00:02:30.935 --> 00:02:32.794
- on something or I want some reports, and

72
00:02:32.935 --> 00:02:34.534
- this kinda came up because I started playing

73
00:02:34.534 --> 00:02:36.134
- with it for a client that kinda wanted

74
00:02:36.134 --> 00:02:37.574
- a POC, and there are some things that

75
00:02:37.574 --> 00:02:39.655
- have definitely gotten easier. And then some things

76
00:02:39.655 --> 00:02:41.489
- that you were informing me about too that

77
00:02:41.489 --> 00:02:43.489
- I missed. So where should we start with

78
00:02:43.489 --> 00:02:46.949
- Power BI today? Why don't we start with

79
00:02:47.810 --> 00:02:48.389
- the MCP

80
00:02:48.849 --> 00:02:49.349
- servers

81
00:02:49.650 --> 00:02:51.810
- and kinda do a little trip around the

82
00:02:51.810 --> 00:02:53.704
- block there? Because there's some other stuff that

83
00:02:53.704 --> 00:02:54.905
- we wanna talk about later when it comes

84
00:02:54.905 --> 00:02:57.324
- to, like, collaboration and things like that. But

85
00:02:57.465 --> 00:02:59.305
- I think we talk about that later because

86
00:02:59.305 --> 00:03:02.044
- the MCP server, at least one of them,

87
00:03:02.264 --> 00:03:04.924
- can be super helpful for interacting

88
00:03:05.384 --> 00:03:08.364
- with that new mode for Power BI development.

89
00:03:08.960 --> 00:03:10.419
- So let's start with

90
00:03:10.800 --> 00:03:14.340
- the servers. Big overview, high level overview. There's

91
00:03:14.560 --> 00:03:18.340
- two MCP servers for Power BI. There's a

92
00:03:18.560 --> 00:03:21.699
- local and a remote. So you've got

93
00:03:22.805 --> 00:03:25.125
- different modes to think about when you were

94
00:03:25.125 --> 00:03:25.625
- interacting

95
00:03:26.724 --> 00:03:28.664
- with Power BI, the service,

96
00:03:29.444 --> 00:03:29.944
- versus

97
00:03:30.405 --> 00:03:30.905
- developing

98
00:03:31.764 --> 00:03:34.245
- Power BI through the Power BI app, and

99
00:03:34.245 --> 00:03:36.025
- maybe you're working with, like, PBX

100
00:03:36.324 --> 00:03:39.280
- files. You need help creating measures.

101
00:03:39.819 --> 00:03:42.139
- Maybe DAX isn't, like, your strong suit, but

102
00:03:42.139 --> 00:03:44.219
- you've run into it kinda thing if you're

103
00:03:44.219 --> 00:03:46.699
- just getting started with Power BI. So there's

104
00:03:46.699 --> 00:03:49.580
- a bunch of kinda niceties across both of

105
00:03:49.580 --> 00:03:52.544
- those servers. So maybe we'll start with the

106
00:03:52.544 --> 00:03:54.064
- local one, and then we can kinda work

107
00:03:54.064 --> 00:03:56.705
- our way towards the the service one. How's

108
00:03:56.705 --> 00:03:58.564
- that sound? Sounds good to me. And

109
00:03:58.865 --> 00:04:02.465
- the local one is the one that I

110
00:04:02.705 --> 00:04:03.985
- I think it was the local one that

111
00:04:03.985 --> 00:04:05.825
- I spent the most time playing with. Because

112
00:04:05.825 --> 00:04:07.840
- it was, to your point,

113
00:04:08.379 --> 00:04:09.199
- I had

114
00:04:09.979 --> 00:04:10.719
- a client

115
00:04:11.020 --> 00:04:13.259
- that wanted to start building some reports on

116
00:04:13.419 --> 00:04:16.220
- and it was actually QuickBooks data, QuickBooks online.

117
00:04:16.220 --> 00:04:19.275
- And Microsoft used to have this nice QuickBooks

118
00:04:19.495 --> 00:04:22.235
- Online data connector built right into Power BI,

119
00:04:22.694 --> 00:04:23.194
- and

120
00:04:23.895 --> 00:04:25.814
- they got rid of it. So I had

121
00:04:25.814 --> 00:04:28.615
- to go find other options and ended up

122
00:04:28.615 --> 00:04:29.115
- finding

123
00:04:29.574 --> 00:04:32.040
- a third party that I was able to

124
00:04:32.040 --> 00:04:34.379
- connect to the Power BI or the QuickBooks

125
00:04:34.439 --> 00:04:35.419
- online APIs,

126
00:04:36.120 --> 00:04:37.980
- dump content into

127
00:04:38.600 --> 00:04:40.919
- Data Lake, but then it was a lot

128
00:04:40.919 --> 00:04:43.579
- of data. Like and I will say QuickBooks

129
00:04:43.720 --> 00:04:46.514
- online from looking at the data is not

130
00:04:46.675 --> 00:04:47.975
- the most intuitive

131
00:04:48.355 --> 00:04:50.035
- in terms of the databases and how they

132
00:04:50.035 --> 00:04:52.754
- structure some of the data. And I very

133
00:04:52.754 --> 00:04:55.314
- quickly got overwhelmed. Again, I don't do Power

134
00:04:55.314 --> 00:04:57.655
- BI a ton. I don't do QuickBooks

135
00:04:58.194 --> 00:05:00.035
- Online data a ton. And I got to

136
00:05:00.035 --> 00:05:01.560
- this point where I'm like, I have, like,

137
00:05:01.800 --> 00:05:02.540
- 50 tables.

138
00:05:03.240 --> 00:05:03.740
- And

139
00:05:04.360 --> 00:05:06.680
- just a glimpse into it, like, this was

140
00:05:06.680 --> 00:05:09.879
- looking at projects in QuickBooks online. And projects

141
00:05:09.879 --> 00:05:12.779
- in QuickBooks online end up in your customer

142
00:05:12.839 --> 00:05:15.745
- table with, like, a flag that it's a

143
00:05:15.745 --> 00:05:18.225
- project and not actually a customer or a

144
00:05:18.225 --> 00:05:19.605
- project for a customer.

145
00:05:19.985 --> 00:05:22.625
- Like, super weird. And I was like, I

146
00:05:22.625 --> 00:05:24.464
- needed help. I was like, I don't know

147
00:05:24.464 --> 00:05:25.904
- how to sort through all this data. There

148
00:05:25.904 --> 00:05:27.930
- is a ton of data here. How can

149
00:05:27.930 --> 00:05:30.330
- I start digging through it? And I was

150
00:05:30.330 --> 00:05:32.250
- like, oh, I wonder if Power BI has

151
00:05:32.250 --> 00:05:35.370
- an MCP server. And lo and behold, here

152
00:05:35.370 --> 00:05:37.290
- is this local MCP server I could go

153
00:05:37.290 --> 00:05:39.230
- hook up. Yeah. The local one is super

154
00:05:39.735 --> 00:05:42.954
- super nifty. So for for those that haven't

155
00:05:43.014 --> 00:05:45.334
- played with it, you can go ahead and

156
00:05:45.334 --> 00:05:46.634
- wire this up to,

157
00:05:47.095 --> 00:05:48.535
- I I mean, a couple different things. So

158
00:05:48.535 --> 00:05:51.334
- it really just requires any harness that can

159
00:05:51.334 --> 00:05:54.740
- allow you to interact with a local MCP,

160
00:05:54.959 --> 00:05:55.459
- so

161
00:05:55.839 --> 00:05:56.899
- Claude on the desktop.

162
00:05:57.199 --> 00:05:58.800
- If you're I believe you have I believe

163
00:05:58.800 --> 00:06:00.720
- you still have to be licensed for for

164
00:06:00.720 --> 00:06:03.600
- those to come through. But Claude Code, GitHub

165
00:06:03.600 --> 00:06:04.100
- Copilot,

166
00:06:04.959 --> 00:06:05.779
- anti gravity,

167
00:06:06.160 --> 00:06:06.660
- codex,

168
00:06:07.235 --> 00:06:08.134
- things like that.

169
00:06:08.675 --> 00:06:10.774
- So you can just go out. There's instructions

170
00:06:11.235 --> 00:06:13.555
- on GitHub to wire it up. It was

171
00:06:13.555 --> 00:06:14.754
- a little bit of a rough start when

172
00:06:14.754 --> 00:06:16.514
- this first came out, but way easier to

173
00:06:16.514 --> 00:06:19.394
- kinda configure and wire up to everything that's

174
00:06:19.394 --> 00:06:20.935
- out there now. But

175
00:06:21.319 --> 00:06:24.300
- what the local MCP server does is

176
00:06:25.000 --> 00:06:27.420
- kind of cool. So if you're

177
00:06:27.800 --> 00:06:30.699
- sitting there and, say, you're working in

178
00:06:31.160 --> 00:06:33.560
- a PBYX file, so you've actually got Power

179
00:06:33.560 --> 00:06:34.379
- BI open,

180
00:06:34.694 --> 00:06:35.194
- and

181
00:06:35.654 --> 00:06:38.055
- you're sitting and you're working with an active

182
00:06:38.055 --> 00:06:39.995
- file, you can just go into

183
00:06:40.454 --> 00:06:40.954
- your

184
00:06:41.495 --> 00:06:42.634
- your LLM

185
00:06:42.935 --> 00:06:45.495
- interaction harness, whatever it happens to be, and

186
00:06:45.495 --> 00:06:47.814
- you can do things like, hey. Power BI

187
00:06:47.814 --> 00:06:50.479
- MCP server, connect to my local file.

188
00:06:50.779 --> 00:06:53.279
- And it knows that Power BI is open,

189
00:06:53.339 --> 00:06:56.459
- and it's able to go and interact with

190
00:06:56.459 --> 00:06:59.039
- that PBIX file. So you can do things

191
00:06:59.099 --> 00:07:01.039
- like you can say,

192
00:07:01.339 --> 00:07:01.839
- maybe

193
00:07:02.435 --> 00:07:04.435
- look at my schema and tell me anything

194
00:07:04.435 --> 00:07:06.055
- that I should fix with my relationships.

195
00:07:06.514 --> 00:07:08.274
- Like, Power BI can get a little weird

196
00:07:08.274 --> 00:07:09.875
- sometimes, right, when it comes to the whole

197
00:07:09.875 --> 00:07:11.334
- star schema thing and

198
00:07:12.035 --> 00:07:14.274
- one to one. And sometimes it just wants

199
00:07:14.274 --> 00:07:16.210
- to do many to many's, And you're, like,

200
00:07:16.210 --> 00:07:18.050
- sitting there fighting it. Like, what's wrong with

201
00:07:18.050 --> 00:07:20.210
- the model? What what's going on that I

202
00:07:20.210 --> 00:07:22.610
- just can't work with it? So it's super

203
00:07:22.610 --> 00:07:24.370
- good for things like that. Like, it's it

204
00:07:24.370 --> 00:07:24.870
- basically

205
00:07:25.330 --> 00:07:25.830
- has

206
00:07:26.290 --> 00:07:29.830
- inherent knowledge of Power BI modeling best practices

207
00:07:30.514 --> 00:07:33.235
- because it's kinda grounded and built on top

208
00:07:33.235 --> 00:07:34.995
- of all that. The other one that I

209
00:07:34.995 --> 00:07:36.214
- really liked with it

210
00:07:36.754 --> 00:07:38.915
- is I I can figure out Power Query

211
00:07:38.915 --> 00:07:40.595
- all day. Like, I'm used to it from

212
00:07:40.595 --> 00:07:42.835
- Excel and then in into Power BI, things

213
00:07:42.835 --> 00:07:44.355
- like that. I'm not good at all at

214
00:07:44.355 --> 00:07:46.629
- decks. Anytime I have to go look up

215
00:07:46.629 --> 00:07:50.389
- and especially get into, like, authoring, like, DAX,

216
00:07:50.389 --> 00:07:52.389
- I my my brain just doesn't work that

217
00:07:52.389 --> 00:07:54.870
- way. Like, it doesn't work for me. But

218
00:07:54.870 --> 00:07:57.285
- that Power BI MCP server, the local one,

219
00:07:57.365 --> 00:07:58.105
- it lets

220
00:07:58.564 --> 00:07:59.464
- you not only

221
00:07:59.764 --> 00:08:02.725
- validate DAX functions that are out there, but

222
00:08:02.725 --> 00:08:03.865
- it can help you

223
00:08:04.245 --> 00:08:07.365
- write DAX queries against your model. It can

224
00:08:07.365 --> 00:08:09.845
- do things like go write a bunch of

225
00:08:09.845 --> 00:08:12.560
- measures for you. So say say you've never

226
00:08:12.620 --> 00:08:13.599
- worked with measures

227
00:08:14.139 --> 00:08:16.379
- and they're confusing you for the DAX and

228
00:08:16.379 --> 00:08:18.060
- things that comes along, you can do something

229
00:08:18.060 --> 00:08:21.039
- like, hey. Go connect to my local file

230
00:08:21.579 --> 00:08:22.079
- and

231
00:08:22.620 --> 00:08:25.115
- suggest to me suggest what measures I should

232
00:08:25.115 --> 00:08:27.535
- have in this model. Or maybe you know,

233
00:08:27.675 --> 00:08:29.915
- like, kinda popular measures that you should have.

234
00:08:29.915 --> 00:08:31.595
- Maybe it's built, like you said, on, like,

235
00:08:31.595 --> 00:08:33.534
- Intuit data, like sales data,

236
00:08:34.075 --> 00:08:36.779
- invoices, things like that. So you'll know like,

237
00:08:36.779 --> 00:08:39.660
- you might want measures around, like, sales by

238
00:08:39.660 --> 00:08:41.899
- week, sales by month, sales by year kinda

239
00:08:41.899 --> 00:08:44.379
- thing. You just say, hey. Go create these

240
00:08:44.379 --> 00:08:47.820
- measures for me in this table or keep

241
00:08:47.820 --> 00:08:49.580
- the measures in the source tables, however you

242
00:08:49.580 --> 00:08:52.214
- wanna do it. And it will go and

243
00:08:52.914 --> 00:08:55.074
- spin those things up. Let's see what else.

244
00:08:55.074 --> 00:08:56.855
- It will troubleshoot calculations.

245
00:08:57.475 --> 00:08:58.855
- That that is super helpful.

246
00:08:59.235 --> 00:09:01.074
- If you've ever been working with, like, trying

247
00:09:01.074 --> 00:09:03.414
- to, like, round things out, convert,

248
00:09:03.860 --> 00:09:05.960
- say, from, like, a double to a percentage,

249
00:09:06.100 --> 00:09:08.580
- things like that. Super helpful for all that.

250
00:09:08.580 --> 00:09:10.820
- I have a public safety message going off.

251
00:09:10.820 --> 00:09:13.379
- Yep. You're getting on alert. I agree. And

252
00:09:13.379 --> 00:09:15.300
- part of what I was too was, like,

253
00:09:15.300 --> 00:09:17.139
- I needed to create a semantic model, and

254
00:09:17.139 --> 00:09:19.399
- I had to narrow down these 44 tables,

255
00:09:19.725 --> 00:09:22.204
- And that's where I started using it. I

256
00:09:22.204 --> 00:09:22.704
- had

257
00:09:23.084 --> 00:09:23.584
- a

258
00:09:24.125 --> 00:09:26.125
- I had a report, and it was interesting.

259
00:09:26.125 --> 00:09:28.044
- Like, I had a report in Power BI

260
00:09:28.044 --> 00:09:30.144
- that I wanted to replicate, and

261
00:09:30.605 --> 00:09:32.125
- I had all my data. So I was

262
00:09:32.125 --> 00:09:34.080
- like, no. I have all the data. I

263
00:09:34.080 --> 00:09:35.200
- have a report of what I want it

264
00:09:35.200 --> 00:09:36.879
- to look like, and I was able to

265
00:09:36.879 --> 00:09:38.259
- go feed it into

266
00:09:38.960 --> 00:09:41.519
- Claude, say, I have this report. Here's the

267
00:09:41.519 --> 00:09:44.980
- data. I need to essentially recreate this report.

268
00:09:45.360 --> 00:09:47.120
- Help walk me through it, and it was

269
00:09:47.120 --> 00:09:49.059
- able to go in and

270
00:09:50.075 --> 00:09:51.215
- help me generate

271
00:09:51.754 --> 00:09:54.955
- a semantic model and pull in the different

272
00:09:54.955 --> 00:09:56.095
- tables from

273
00:09:56.715 --> 00:09:57.215
- my

274
00:09:57.995 --> 00:09:59.754
- data lake and my lake house and all

275
00:09:59.754 --> 00:10:01.115
- of that and really narrow it down. So

276
00:10:01.115 --> 00:10:01.995
- at the end of the day, I had

277
00:10:01.995 --> 00:10:03.929
- to net 44 tables. It built

278
00:10:04.250 --> 00:10:06.589
- the, like, six I needed with the relationships

279
00:10:06.730 --> 00:10:08.730
- between all of them, and then it was

280
00:10:08.730 --> 00:10:10.730
- able to go in and here's the

281
00:10:11.289 --> 00:10:13.129
- and I actually told that I wanted to

282
00:10:13.129 --> 00:10:14.730
- understand it more. So I was like, just

283
00:10:14.730 --> 00:10:16.490
- give me the instructions. How do I take

284
00:10:16.490 --> 00:10:19.304
- this data and build my PBIX file? So

285
00:10:19.384 --> 00:10:21.065
- I didn't have it build the whole table

286
00:10:21.065 --> 00:10:23.384
- for or the whole report for me. I

287
00:10:23.384 --> 00:10:25.225
- just had it walk me step by step

288
00:10:25.225 --> 00:10:27.245
- of what did you what's in each table,

289
00:10:27.464 --> 00:10:29.784
- what table goes in which chart, what charts

290
00:10:29.784 --> 00:10:31.945
- should I use, how do I structure my

291
00:10:31.945 --> 00:10:32.445
- filters,

292
00:10:32.919 --> 00:10:35.960
- and actually almost had it teach me how

293
00:10:35.960 --> 00:10:37.500
- I wanted to take the

294
00:10:37.960 --> 00:10:40.139
- data and the models it had built and

295
00:10:40.200 --> 00:10:43.000
- build my PBIX report or the PBIX file,

296
00:10:43.000 --> 00:10:44.919
- build the report in Power BI so I

297
00:10:44.919 --> 00:10:47.160
- could understand it all. And then even some

298
00:10:47.160 --> 00:10:50.115
- notebooks that I needed running behind the scenes

299
00:10:50.175 --> 00:10:51.715
- to do some things from

300
00:10:52.175 --> 00:10:53.774
- data lake to lake houses and all of

301
00:10:53.774 --> 00:10:56.975
- that. So that's where I really found a

302
00:10:56.975 --> 00:11:00.274
- lot of benefit from that MCP server is,

303
00:11:01.309 --> 00:11:02.669
- hey, Scott. I love your puppy in the

304
00:11:02.669 --> 00:11:05.389
- background. Yeah. If everybody's here in squeakers, that

305
00:11:05.389 --> 00:11:08.190
- that that's it. He's No. Really going through

306
00:11:08.190 --> 00:11:09.330
- and helping me

307
00:11:09.710 --> 00:11:12.509
- go from all of that extra data that

308
00:11:12.509 --> 00:11:14.534
- I didn't necessarily need to just narrow it

309
00:11:14.534 --> 00:11:15.894
- down to the data I need and how

310
00:11:15.894 --> 00:11:17.654
- I wanna build the report and what notebooks

311
00:11:17.654 --> 00:11:18.855
- I need and all of that. Yeah. I

312
00:11:18.855 --> 00:11:20.855
- think it's a good way to go about

313
00:11:20.855 --> 00:11:21.595
- those things.

314
00:11:22.534 --> 00:11:23.514
- So you can use

315
00:11:23.975 --> 00:11:26.394
- I think there's two ways that you can

316
00:11:26.934 --> 00:11:27.434
- generally

317
00:11:28.134 --> 00:11:30.629
- use a AI and then certainly, like, these

318
00:11:30.629 --> 00:11:32.710
- MCP servers, things like that. So you can

319
00:11:32.710 --> 00:11:34.070
- either have them do the work for you,

320
00:11:34.070 --> 00:11:35.269
- or you can learn how to do the

321
00:11:35.269 --> 00:11:37.589
- work yourself and have this be kind of

322
00:11:37.589 --> 00:11:41.269
- an an aid or an accelerator for you.

323
00:11:41.269 --> 00:11:43.375
- And once you've made a decision, go in

324
00:11:43.375 --> 00:11:44.235
- a certain direction.

325
00:11:45.254 --> 00:11:45.754
- Sir,

326
00:11:46.615 --> 00:11:48.214
- so I think it is super helpful for

327
00:11:48.214 --> 00:11:49.754
- that iterative process

328
00:11:50.134 --> 00:11:53.014
- of coming through. And like I said, the

329
00:11:53.014 --> 00:11:55.674
- the MCP server is grounded in

330
00:11:56.279 --> 00:11:59.480
- things like the public docs. It understands best

331
00:11:59.480 --> 00:11:59.980
- practices.

332
00:12:00.600 --> 00:12:03.419
- It it knows what to do or ish

333
00:12:03.639 --> 00:12:05.159
- what to do. You might have to teach

334
00:12:05.159 --> 00:12:06.759
- it a little bit about your model. I've

335
00:12:06.759 --> 00:12:08.440
- been kind of impressed at what it's been

336
00:12:08.440 --> 00:12:10.519
- able to infer just by throwing some raw

337
00:12:10.519 --> 00:12:13.054
- tables and things at it. And Power BI

338
00:12:13.054 --> 00:12:14.815
- is generally pretty good about that anyway. If

339
00:12:14.815 --> 00:12:15.554
- I've got

340
00:12:16.095 --> 00:12:18.595
- sale date in this table and the field

341
00:12:18.894 --> 00:12:20.815
- date of sale in this table, sometimes it

342
00:12:20.815 --> 00:12:22.815
- can figure out that, hey. These two things

343
00:12:22.815 --> 00:12:24.654
- are in fact dates for the same tail.

344
00:12:24.654 --> 00:12:25.315
- May may

345
00:12:25.649 --> 00:12:26.929
- for the same sail. Maybe it was more

346
00:12:26.929 --> 00:12:28.309
- like a fact and a dimension,

347
00:12:28.850 --> 00:12:31.009
- things like that. So it can do definitely

348
00:12:31.009 --> 00:12:32.149
- do it and

349
00:12:32.769 --> 00:12:34.389
- and and get you there. So

350
00:12:34.690 --> 00:12:36.209
- so that's all good. So so you've got

351
00:12:36.209 --> 00:12:39.589
- a local MCP server. Author your files locally.

352
00:12:39.649 --> 00:12:40.789
- Work with them locally.

353
00:12:41.465 --> 00:12:42.904
- You get to be kinda human in the

354
00:12:42.904 --> 00:12:45.625
- loop and and go back and forth with

355
00:12:45.625 --> 00:12:47.165
- them. And then there's also

356
00:12:48.424 --> 00:12:51.245
- a remote MCP server. So

357
00:12:51.625 --> 00:12:53.565
- you can use that for

358
00:12:54.345 --> 00:12:54.845
- working

359
00:12:55.225 --> 00:12:56.445
- with your

360
00:12:56.909 --> 00:13:00.049
- semantic models that are already loaded up into

361
00:13:00.350 --> 00:13:03.329
- the Power BI service, things like that. So

362
00:13:03.389 --> 00:13:05.950
- if you're working, say, with, like I said,

363
00:13:05.950 --> 00:13:08.029
- like, a semantic model, it's already up there,

364
00:13:08.029 --> 00:13:10.304
- maybe you've got access to it, You wanna

365
00:13:10.304 --> 00:13:11.445
- go and maybe

366
00:13:11.825 --> 00:13:15.425
- create a new Power BI report dashboard, something

367
00:13:15.425 --> 00:13:18.065
- like that based on an existing semantic model.

368
00:13:18.065 --> 00:13:19.904
- It can go up there and do very

369
00:13:19.904 --> 00:13:22.545
- similar things. It can help you generate, execute

370
00:13:22.545 --> 00:13:23.445
- DAX queries,

371
00:13:24.759 --> 00:13:26.059
- natural language conversations,

372
00:13:26.919 --> 00:13:28.679
- all all that kind of stuff. The other

373
00:13:28.679 --> 00:13:30.919
- one where I think the remote MCP server

374
00:13:30.919 --> 00:13:31.899
- could help is

375
00:13:32.279 --> 00:13:34.299
- one of the things I've found

376
00:13:34.840 --> 00:13:37.285
- AI to be generally good at, I would

377
00:13:37.285 --> 00:13:40.404
- say doesn't tend to hallucinate nearly as much,

378
00:13:40.404 --> 00:13:43.445
- is just analyzing data. Looking over data and

379
00:13:43.445 --> 00:13:46.165
- saying, here's all my data. Like, help me

380
00:13:46.165 --> 00:13:48.565
- sort through it, sift through it, find certain

381
00:13:48.565 --> 00:13:50.490
- trends in it, that type of stuff. And

382
00:13:50.570 --> 00:13:52.269
- And I think that's where this remote MCP

383
00:13:52.330 --> 00:13:54.649
- server can could be nice too because like

384
00:13:54.649 --> 00:13:56.409
- you said, it can go connect to those

385
00:13:56.409 --> 00:13:58.809
- semantic models. So even if you're just trying

386
00:13:58.809 --> 00:14:01.470
- to understand your data a little bit more,

387
00:14:01.610 --> 00:14:03.529
- just using it to go query that data,

388
00:14:03.529 --> 00:14:06.684
- ask questions about your data, I found, not

389
00:14:06.684 --> 00:14:08.605
- to knock on Microsoft, but it's totally a

390
00:14:08.605 --> 00:14:11.245
- knock on Microsoft, is the Copilot stuff in

391
00:14:11.245 --> 00:14:14.304
- Power BI, I did try that first, and

392
00:14:14.445 --> 00:14:17.245
- it was trash. I could not get it

393
00:14:17.245 --> 00:14:19.049
- to work and do what I wanted to.

394
00:14:19.129 --> 00:14:21.129
- And when I switched to these MCP servers

395
00:14:21.129 --> 00:14:23.629
- for query tools and hooked it up to

396
00:14:24.009 --> 00:14:26.169
- Claude, I had a lot more success with

397
00:14:26.169 --> 00:14:28.350
- it. So if you've used

398
00:14:28.889 --> 00:14:31.209
- Copilot and Power BI and you're frustrated, I

399
00:14:31.209 --> 00:14:34.029
- would say go give this a try because

400
00:14:34.745 --> 00:14:36.745
- I definitely had a lot letter better luck

401
00:14:36.745 --> 00:14:39.084
- with this. And, again, the remote MCP server,

402
00:14:39.304 --> 00:14:41.325
- great for going in and looking through data.

403
00:14:41.464 --> 00:14:43.065
- I do wanna say too, Scott, both of

404
00:14:43.065 --> 00:14:44.664
- these are still in preview, so we need

405
00:14:44.664 --> 00:14:46.904
- to put our normal preview disclaimer on it.

406
00:14:46.904 --> 00:14:48.044
- These are both preview.

407
00:14:48.509 --> 00:14:50.910
- There's a comparison too between the road remote

408
00:14:50.910 --> 00:14:52.990
- MCP and local MCP that we'll link to

409
00:14:52.990 --> 00:14:54.670
- in the show notes. Right? Because there are

410
00:14:54.670 --> 00:14:56.990
- a few differences there in terms of, like,

411
00:14:56.990 --> 00:14:58.370
- what you can use for authentication.

412
00:14:59.070 --> 00:15:01.414
- It talks about the different tools that are

413
00:15:01.414 --> 00:15:03.335
- available, a few things there. If you are

414
00:15:03.335 --> 00:15:04.855
- trying to figure out, well, do I need

415
00:15:04.855 --> 00:15:06.774
- the local? Do I need the remote? Or

416
00:15:06.774 --> 00:15:08.934
- if one thing doesn't work in one of

417
00:15:08.934 --> 00:15:11.115
- them, what does the other one do, etcetera.

418
00:15:11.174 --> 00:15:13.495
- There are some additional steps along the way

419
00:15:13.495 --> 00:15:14.794
- as well. So

420
00:15:15.610 --> 00:15:16.889
- I I didn't run into some of this

421
00:15:16.889 --> 00:15:18.970
- until I read the documentation because you you

422
00:15:18.970 --> 00:15:20.570
- don't always, like, click all the buttons in

423
00:15:20.570 --> 00:15:22.330
- the ribbon and things like that in Power

424
00:15:22.330 --> 00:15:24.669
- BI. So there's this kinda

425
00:15:25.450 --> 00:15:28.429
- front matter or front loaded step preparation step

426
00:15:28.490 --> 00:15:31.230
- to go and prepare your data for AI.

427
00:15:31.664 --> 00:15:34.384
- So if you're working both with the local

428
00:15:34.384 --> 00:15:37.345
- MCP server or the remote one, Power BI

429
00:15:37.345 --> 00:15:38.945
- local at least has a button go and

430
00:15:38.945 --> 00:15:40.725
- prepare your data for AI,

431
00:15:41.184 --> 00:15:43.764
- and you can go and have it generate,

432
00:15:43.825 --> 00:15:46.225
- like, a AI ready schemas. So you have

433
00:15:46.225 --> 00:15:49.090
- to have Power BI q and a enabled

434
00:15:49.149 --> 00:15:51.170
- to be able to go and do this,

435
00:15:51.549 --> 00:15:53.629
- but you can just run through this set

436
00:15:53.629 --> 00:15:54.929
- of steps to kinda,

437
00:15:56.029 --> 00:15:57.470
- prepare your data for AI. It's what the

438
00:15:57.470 --> 00:16:00.210
- button says. It's what everything guides you into,

439
00:16:00.805 --> 00:16:03.865
- and it'll help you kinda optimize your schema

440
00:16:04.004 --> 00:16:07.465
- and optimize your semantic model for Copilot

441
00:16:07.845 --> 00:16:09.865
- or more broadly for LLMs

442
00:16:10.245 --> 00:16:12.985
- to be able to come in and understand

443
00:16:13.709 --> 00:16:15.490
- all of this stuff. Yeah.

444
00:16:16.350 --> 00:16:17.470
- Yeah. So I don't know if you've run

445
00:16:17.470 --> 00:16:19.230
- through that step yet. I don't think I

446
00:16:19.230 --> 00:16:20.990
- did run through that step. I'm gonna have

447
00:16:20.990 --> 00:16:22.269
- to go back and look at that. It

448
00:16:22.269 --> 00:16:24.029
- will do things like remember I was talking

449
00:16:24.029 --> 00:16:25.870
- about, like, help you with your schema, maybe

450
00:16:25.870 --> 00:16:27.230
- get it back to, like, a a real,

451
00:16:27.230 --> 00:16:29.065
- like, star schema kind of thing. So it

452
00:16:29.065 --> 00:16:31.404
- can help you simplify your schema.

453
00:16:31.865 --> 00:16:35.165
- It can remove redundant fields, redundant measures,

454
00:16:35.785 --> 00:16:38.024
- think things like that. And then part of

455
00:16:38.024 --> 00:16:39.785
- it is you're kinda, like, grounding it and

456
00:16:39.785 --> 00:16:41.545
- asking it along the or it's asking you

457
00:16:41.545 --> 00:16:42.904
- along the way, like, hey. I did this

458
00:16:42.904 --> 00:16:44.585
- summarization. Does this look right to you? And

459
00:16:44.585 --> 00:16:46.399
- you could say yes or no and and

460
00:16:46.399 --> 00:16:48.799
- go back and pivot. So it's another way

461
00:16:48.799 --> 00:16:50.720
- also to kinda not only clean up your

462
00:16:50.720 --> 00:16:54.100
- schema, but verify things like measure logic

463
00:16:54.480 --> 00:16:55.220
- and DAX,

464
00:16:55.679 --> 00:16:57.200
- and all of that is ready. And then

465
00:16:57.200 --> 00:16:58.480
- as part of that, you're gonna go through

466
00:16:58.480 --> 00:17:00.340
- and you're gonna mark things as

467
00:17:01.225 --> 00:17:03.785
- verified answers so that if somebody else is

468
00:17:03.785 --> 00:17:06.205
- using your model, they can also come in.

469
00:17:06.345 --> 00:17:08.265
- And you'll know that, like, consumers of your

470
00:17:08.265 --> 00:17:10.265
- model who are maybe using, like, Power BI,

471
00:17:10.265 --> 00:17:12.825
- q and a, or just Copilot, things like

472
00:17:12.825 --> 00:17:14.585
- that through through Versus Code, maybe they're using

473
00:17:14.585 --> 00:17:16.960
- the MCP server and hooking up, that they're

474
00:17:16.960 --> 00:17:17.460
- getting

475
00:17:18.400 --> 00:17:19.059
- the right

476
00:17:19.360 --> 00:17:21.840
- the right answer all along the way. I'm

477
00:17:21.840 --> 00:17:24.320
- glad to see these MCPs too. I think

478
00:17:24.320 --> 00:17:26.580
- I've talked about it before. I I

479
00:17:27.120 --> 00:17:29.059
- more and more as people create MCPs,

480
00:17:29.680 --> 00:17:30.900
- I think that's

481
00:17:31.605 --> 00:17:32.984
- you get so much flexibility

482
00:17:33.285 --> 00:17:35.045
- out of MCPs in terms of what you

483
00:17:35.045 --> 00:17:36.884
- wanna do with data. I would much rather

484
00:17:36.884 --> 00:17:38.005
- see a whole bunch of people build a

485
00:17:38.005 --> 00:17:38.984
- whole bunch of MCPs

486
00:17:39.365 --> 00:17:42.025
- than everybody build all their own AI stuff

487
00:17:42.164 --> 00:17:44.044
- and just let me get my data wherever

488
00:17:44.044 --> 00:17:46.029
- I want to. Let me choose my own

489
00:17:46.029 --> 00:17:48.589
- harness, choose my own AI platform, and give

490
00:17:48.589 --> 00:17:50.829
- me an MCP rather than, like, making me

491
00:17:50.829 --> 00:17:52.849
- stay in your tool or

492
00:17:53.150 --> 00:17:56.109
- your own specialized AI thing. I also get

493
00:17:56.109 --> 00:17:58.190
- it from a marketing perspective. Everybody wants your

494
00:17:58.190 --> 00:18:00.765
- eyes and their product, so they want you

495
00:18:00.765 --> 00:18:02.684
- to stay in theirs for their AI. The

496
00:18:02.684 --> 00:18:04.144
- more and more I can find MCPs,

497
00:18:04.525 --> 00:18:05.725
- it makes me happy. We could have a

498
00:18:05.725 --> 00:18:07.164
- whole another talk on We could have a

499
00:18:07.164 --> 00:18:08.785
- whole another talk on that. MCPs

500
00:18:09.164 --> 00:18:11.085
- and death of SaaS and things like that.

501
00:18:11.085 --> 00:18:13.164
- Should we move on from MCPs to something

502
00:18:13.164 --> 00:18:14.970
- else you told me about that I had

503
00:18:14.970 --> 00:18:17.049
- kinda completely missed when it came to Power

504
00:18:17.049 --> 00:18:18.410
- BI? Like I said, once you have these

505
00:18:18.410 --> 00:18:18.910
- MCPs

506
00:18:19.450 --> 00:18:22.029
- in place, now you've got kind of a

507
00:18:22.730 --> 00:18:24.589
- a a little bit of a collaboration

508
00:18:24.890 --> 00:18:26.809
- scenario going on, whether it's you as human

509
00:18:26.809 --> 00:18:28.565
- in the loop, just you and kind of

510
00:18:28.565 --> 00:18:30.265
- model and the Power BI service

511
00:18:30.805 --> 00:18:33.365
- going back and forth, things like that. But

512
00:18:33.365 --> 00:18:37.144
- there's also the world where maybe you collaborate

513
00:18:38.404 --> 00:18:40.345
- with with other users,

514
00:18:40.869 --> 00:18:42.789
- maybe other agents, things that are out there.

515
00:18:42.789 --> 00:18:44.630
- Right? You said talk kinda talking through, like,

516
00:18:44.630 --> 00:18:46.549
- hey. You enjoy being able to work with

517
00:18:46.549 --> 00:18:49.429
- kind of, like, model and harness of your

518
00:18:49.429 --> 00:18:52.390
- choice kind of thing. So so that's definitely

519
00:18:52.390 --> 00:18:55.845
- another consideration is now that you've got

520
00:18:56.164 --> 00:18:57.924
- these things out there, like, how can you

521
00:18:57.924 --> 00:18:58.744
- use them

522
00:18:59.204 --> 00:19:01.224
- with your existing harnesses,

523
00:19:01.525 --> 00:19:03.544
- existing agents, things like that?

524
00:19:03.924 --> 00:19:06.484
- So I forget when they added this. I

525
00:19:06.484 --> 00:19:09.059
- turned it on as soon as they did,

526
00:19:09.059 --> 00:19:11.559
- but there's an ability now in

527
00:19:11.859 --> 00:19:12.679
- Power BI

528
00:19:13.379 --> 00:19:13.879
- to

529
00:19:14.579 --> 00:19:15.480
- work on

530
00:19:15.779 --> 00:19:16.839
- collaborative files.

531
00:19:17.140 --> 00:19:20.279
- So if everybody's familiar with a p b

532
00:19:20.660 --> 00:19:21.160
- PBIX

533
00:19:21.815 --> 00:19:25.835
- file, the kinda just raw file that encapsulates

534
00:19:26.214 --> 00:19:28.694
- your Power BI report locally that you work

535
00:19:28.694 --> 00:19:30.535
- with before you go and publish it to

536
00:19:30.535 --> 00:19:32.295
- the service, or maybe you just hang with

537
00:19:32.295 --> 00:19:34.134
- it locally and you never publish it to

538
00:19:34.134 --> 00:19:37.130
- the service kinda thing, There there's this new

539
00:19:37.130 --> 00:19:39.710
- file format for Power BI,

540
00:19:40.250 --> 00:19:41.069
- which is

541
00:19:41.690 --> 00:19:41.769
- a,

542
00:19:42.970 --> 00:19:43.869
- it it basically

543
00:19:44.170 --> 00:19:44.490
- allows

544
00:19:45.130 --> 00:19:46.730
- it'll it allows you to collaborate on these

545
00:19:46.730 --> 00:19:48.730
- things, and it breaks down a what is

546
00:19:48.730 --> 00:19:50.829
- a single PVAX file

547
00:19:51.164 --> 00:19:51.664
- into

548
00:19:52.765 --> 00:19:53.744
- multiple files

549
00:19:54.205 --> 00:19:55.664
- that all end up in this

550
00:19:56.125 --> 00:19:56.625
- PBIP

551
00:19:58.125 --> 00:20:00.684
- file. I I do wonder what, like, like,

552
00:20:00.684 --> 00:20:02.845
- what they were thinking with the the the

553
00:20:02.845 --> 00:20:05.109
- acronyms on the end there. But, basically, what

554
00:20:05.109 --> 00:20:07.769
- a p b I b PBIP

555
00:20:08.789 --> 00:20:10.970
- fi IP file is

556
00:20:11.669 --> 00:20:13.849
- is it makes your,

557
00:20:15.349 --> 00:20:16.089
- it it makes

558
00:20:16.630 --> 00:20:17.690
- the Power BI

559
00:20:18.710 --> 00:20:19.029
- file

560
00:20:19.534 --> 00:20:20.034
- files,

561
00:20:20.335 --> 00:20:20.835
- basically,

562
00:20:21.375 --> 00:20:23.934
- human readable. So that now you can do

563
00:20:23.934 --> 00:20:26.095
- things like you can store this, say, in,

564
00:20:26.095 --> 00:20:28.335
- like, GitHub and collaborate back and forth with

565
00:20:28.335 --> 00:20:31.134
- people. So, like, rather than me writing a

566
00:20:31.134 --> 00:20:33.279
- PBX, and then I gotta shut down Power

567
00:20:33.279 --> 00:20:34.799
- BI and then maybe share you a link

568
00:20:34.799 --> 00:20:35.920
- to it, and then you go work in

569
00:20:35.920 --> 00:20:37.200
- it. And then the next time I open

570
00:20:37.200 --> 00:20:38.740
- Power BI, it's probably broken,

571
00:20:39.119 --> 00:20:40.559
- or we both open it at the same

572
00:20:40.559 --> 00:20:42.500
- time and we really screw each other up

573
00:20:42.559 --> 00:20:44.740
- kinda thing, now you can actually get into

574
00:20:44.960 --> 00:20:46.259
- a collaborative

575
00:20:47.105 --> 00:20:47.605
- workflow

576
00:20:48.065 --> 00:20:50.384
- across these things. There's no, like, there's no

577
00:20:50.384 --> 00:20:53.265
- more having to email these things around, storm

578
00:20:53.265 --> 00:20:54.484
- in a SharePoint site,

579
00:20:54.865 --> 00:20:57.105
- any anything like that. And because they're just

580
00:20:57.105 --> 00:20:59.285
- raw files, I said, you can storming in

581
00:20:59.345 --> 00:21:00.164
- a Git repository.

582
00:21:00.829 --> 00:21:03.470
- So now you get things like safe safe

583
00:21:03.470 --> 00:21:06.369
- rollback. You get actual, like, versioning versioning,

584
00:21:06.910 --> 00:21:08.750
- across things that are out there. But the

585
00:21:08.750 --> 00:21:11.309
- really kinda maybe, like, next level thing you

586
00:21:11.309 --> 00:21:13.275
- can do now is because you have these

587
00:21:13.275 --> 00:21:16.335
- MCP servers also understand that new file format.

588
00:21:16.475 --> 00:21:18.634
- So now you can have, like, agents that

589
00:21:18.634 --> 00:21:19.934
- sit alongside you.

590
00:21:20.315 --> 00:21:22.075
- So you could be, like, authoring one of

591
00:21:22.075 --> 00:21:23.595
- these things, and you could have an agent

592
00:21:23.595 --> 00:21:25.215
- say that, like, runs daily

593
00:21:25.599 --> 00:21:27.519
- and does, like, sanity checks on your DAX

594
00:21:27.519 --> 00:21:30.179
- queries or things like that for you. Yeah.

595
00:21:31.679 --> 00:21:34.659
- If you're managing file storage today, you've probably

596
00:21:34.799 --> 00:21:37.440
- felt the pressure. Refresh cycles are harder to

597
00:21:37.440 --> 00:21:40.904
- plan, costs and complexity are increasing, especially as

598
00:21:40.904 --> 00:21:43.005
- file workloads scale across regions.

599
00:21:43.384 --> 00:21:46.664
- That's why Microsoft customers trust Nasuni. As an

600
00:21:46.664 --> 00:21:48.204
- Azure certified software,

601
00:21:48.585 --> 00:21:51.544
- Nasuni provides a global file system designed for

602
00:21:51.544 --> 00:21:52.924
- enterprise scale environments,

603
00:21:53.339 --> 00:21:56.859
- keeping file data secure, governed, and accessible across

604
00:21:56.859 --> 00:21:59.919
- Azure environments without added infrastructure complexity.

605
00:22:00.299 --> 00:22:03.419
- It's the foundation to keep your unstructured data

606
00:22:03.419 --> 00:22:05.359
- stable even as your infrastructure

607
00:22:05.660 --> 00:22:08.005
- evolves. To see how much you could save

608
00:22:08.005 --> 00:22:10.424
- while keeping your initiatives on track, visit

609
00:22:10.725 --> 00:22:14.325
- nasuni.com/tco.

610
00:22:14.325 --> 00:22:18.984
- That's nasuni.com/tco.

611
00:22:20.164 --> 00:22:22.059
- This is cool, and I did look up

612
00:22:22.059 --> 00:22:24.379
- some dates, Scott. So this was

613
00:22:24.779 --> 00:22:26.940
- this has been a long time coming. It

614
00:22:26.940 --> 00:22:28.629
- was announced in May

615
00:22:28.629 --> 00:22:29.440
- 2023.

616
00:22:29.579 --> 00:22:32.700
- It hit public preview in June 2023, and

617
00:22:32.700 --> 00:22:35.179
- it has been in public preview for the

618
00:22:35.179 --> 00:22:38.674
- last three years. And it's still technically labeled

619
00:22:38.815 --> 00:22:39.315
- preview,

620
00:22:39.775 --> 00:22:40.275
- although

621
00:22:40.654 --> 00:22:42.994
- we do have for Microsoft that general availability

622
00:22:43.055 --> 00:22:45.375
- is planned. So while it's still preview, this

623
00:22:45.375 --> 00:22:47.154
- one is probably relatively

624
00:22:47.775 --> 00:22:49.634
- safe to start using.

625
00:22:49.960 --> 00:22:51.240
- Every once in a while, I had one

626
00:22:51.240 --> 00:22:53.160
- of these recently, Scott, a preview feature that

627
00:22:53.160 --> 00:22:55.340
- got deprecated and never made it to GA.

628
00:22:55.559 --> 00:22:57.100
- It does happen. It does.

629
00:22:57.480 --> 00:22:59.720
- And three three three years is a long

630
00:22:59.720 --> 00:23:02.279
- time to be in public preview. But, yeah,

631
00:23:02.279 --> 00:23:03.914
- I think I probably saw this, like, two

632
00:23:03.914 --> 00:23:05.994
- years ago or so maybe Okay. And started

633
00:23:05.994 --> 00:23:07.674
- playing around with it then. It I don't

634
00:23:07.755 --> 00:23:08.414
- I mean,

635
00:23:08.715 --> 00:23:10.715
- granted, I'm probably using it a way, like,

636
00:23:10.715 --> 00:23:12.715
- a high level, but it seems to work.

637
00:23:12.715 --> 00:23:14.394
- Like, it does what it says. It does

638
00:23:14.394 --> 00:23:16.475
- what it's supposed to do. Yeah. Yeah. It's

639
00:23:16.475 --> 00:23:18.130
- kinda cool. I almost like, like, when you

640
00:23:18.130 --> 00:23:19.569
- were starting to tell me about this, because

641
00:23:19.569 --> 00:23:21.509
- I haven't used it partly because

642
00:23:21.890 --> 00:23:24.210
- being in the position I am with consulting

643
00:23:24.210 --> 00:23:26.049
- and stuff, I don't tend to have a

644
00:23:26.049 --> 00:23:29.269
- ton of collaboration around Power BI stuff. But

645
00:23:29.329 --> 00:23:31.169
- it almost feels like when we made the

646
00:23:31.169 --> 00:23:33.464
- move from the doc files to the docx

647
00:23:33.464 --> 00:23:35.464
- files, where the doc files are kind of

648
00:23:35.464 --> 00:23:36.684
- all self encapsulated,

649
00:23:37.224 --> 00:23:39.464
- docx is I mean, really just a zip

650
00:23:39.464 --> 00:23:40.825
- file with a bunch of other files in

651
00:23:40.825 --> 00:23:42.285
- it so that you can do the coauthoring

652
00:23:42.424 --> 00:23:44.904
- and stuff in Word and all of that.

653
00:23:44.904 --> 00:23:46.984
- This feels very similar where it was like

654
00:23:46.984 --> 00:23:47.484
- PBIX

655
00:23:49.039 --> 00:23:51.859
- was that self contained PBIP, which is Power

656
00:23:51.919 --> 00:23:54.640
- BI project, Scott. That's where it comes from.

657
00:23:54.640 --> 00:23:56.019
- I also saw that.

658
00:23:56.799 --> 00:23:58.880
- It's the way you were describing it, it's

659
00:23:58.880 --> 00:24:00.480
- very similar to that where now it's almost

660
00:24:00.559 --> 00:24:02.240
- it's just a container with a bunch of

661
00:24:02.240 --> 00:24:03.585
- little files in it so that as you

662
00:24:03.585 --> 00:24:04.804
- are doing that coauthoring,

663
00:24:05.345 --> 00:24:06.724
- you're putting these in

664
00:24:07.025 --> 00:24:07.765
- source control.

665
00:24:08.144 --> 00:24:10.304
- It's able to go in and edit, like,

666
00:24:10.304 --> 00:24:12.544
- individual files and do diffs a little bit

667
00:24:12.544 --> 00:24:14.804
- better and all of that with that collaboration.

668
00:24:15.359 --> 00:24:17.119
- So that was kind of the analogy that

669
00:24:17.119 --> 00:24:18.480
- jumped out in my head. I'm like, okay.

670
00:24:18.480 --> 00:24:20.900
- Now it makes sense what those Power BI

671
00:24:21.039 --> 00:24:21.539
- PBIP

672
00:24:22.000 --> 00:24:24.480
- Power BI project files are. There's still some

673
00:24:24.480 --> 00:24:26.400
- proprietary stuff in there. So if you start

674
00:24:26.400 --> 00:24:29.619
- digging into the folders and things like that,

675
00:24:29.934 --> 00:24:32.974
- there there's definitely parts that are kinda just

676
00:24:32.974 --> 00:24:36.414
- custom binary format and not meant for you

677
00:24:36.414 --> 00:24:37.394
- to use, but

678
00:24:37.695 --> 00:24:39.795
- you yeah. But you you can definitely

679
00:24:40.174 --> 00:24:41.875
- get in there and start playing with these.

680
00:24:42.095 --> 00:24:44.734
- Super easy to get going with. They do

681
00:24:44.734 --> 00:24:45.234
- recommend,

682
00:24:46.150 --> 00:24:47.269
- and I don't know, I haven't used it

683
00:24:47.269 --> 00:24:49.349
- with anything else other than, like, GitHub, but

684
00:24:49.349 --> 00:24:51.029
- just Git repos. But you could do this

685
00:24:51.029 --> 00:24:52.950
- with, like, a Git style repo in Azure

686
00:24:52.950 --> 00:24:53.450
- DevOps,

687
00:24:54.390 --> 00:24:56.710
- anything like that along the way. So now

688
00:24:56.710 --> 00:24:59.029
- if you think, like, back to, like, say,

689
00:24:59.029 --> 00:25:00.329
- like, the agents thing.

690
00:25:00.644 --> 00:25:02.424
- So you have one of these

691
00:25:03.445 --> 00:25:03.945
- PBIP

692
00:25:04.565 --> 00:25:05.065
- projects.

693
00:25:05.765 --> 00:25:07.365
- You spin that up. When you do your

694
00:25:07.365 --> 00:25:10.025
- check-in let's say you are using Azure DevOps.

695
00:25:10.164 --> 00:25:11.684
- So you do your check-in. You can have

696
00:25:11.684 --> 00:25:14.664
- a pipeline run that goes and kinda validates

697
00:25:14.805 --> 00:25:16.930
- things for you. And you could potentially have

698
00:25:16.930 --> 00:25:17.670
- that pipeline

699
00:25:17.970 --> 00:25:20.610
- run and invoke something like an MCP to

700
00:25:20.610 --> 00:25:23.570
- go validate your schema, validate your DAX. Like,

701
00:25:23.570 --> 00:25:25.430
- you actually get a little bit more

702
00:25:25.890 --> 00:25:27.570
- a little bit more kinda, like, rigor and

703
00:25:27.570 --> 00:25:30.230
- governance, I guess, around release of these things

704
00:25:30.855 --> 00:25:33.275
- as they as they come out, which is

705
00:25:33.414 --> 00:25:35.095
- super nice to see. Right? It kinda makes

706
00:25:35.095 --> 00:25:36.775
- it a little bit more, I think, a

707
00:25:36.775 --> 00:25:38.875
- little bit more, like, enterprise developer

708
00:25:39.174 --> 00:25:42.055
- versus, like, enterprise power user kinda thing. I

709
00:25:42.055 --> 00:25:43.275
- agree. Power BI,

710
00:25:43.700 --> 00:25:45.859
- it did seem to be very end user

711
00:25:45.859 --> 00:25:46.359
- focused

712
00:25:46.819 --> 00:25:48.500
- originally where it was go install it on

713
00:25:48.500 --> 00:25:50.339
- my desktop, create it there, I publish it

714
00:25:50.339 --> 00:25:52.359
- up, I share it out to people. This

715
00:25:52.579 --> 00:25:55.779
- is very much that collaborative development. Like, you

716
00:25:55.779 --> 00:25:57.434
- were talking about, I could even think if

717
00:25:57.434 --> 00:25:58.335
- you had, like, scheduled agents

718
00:25:58.795 --> 00:26:01.035
- that were running your scheduled tasks in your

719
00:26:01.035 --> 00:26:02.634
- LLM that had to go in and do

720
00:26:02.634 --> 00:26:05.995
- certain things in your Power BI report, publish

721
00:26:05.995 --> 00:26:06.975
- it through a pipeline.

722
00:26:07.515 --> 00:26:10.909
- I feel like it this just greatly expands

723
00:26:11.130 --> 00:26:12.029
- the flexibility

724
00:26:12.409 --> 00:26:13.549
- and the flexibility

725
00:26:14.089 --> 00:26:14.589
- ability

726
00:26:15.289 --> 00:26:18.009
- aspects of what you can now start doing

727
00:26:18.009 --> 00:26:20.409
- with some of these Power BI reports, especially

728
00:26:20.409 --> 00:26:21.849
- because people always like them to be up

729
00:26:21.849 --> 00:26:23.875
- to date. And let's face it, when people

730
00:26:23.875 --> 00:26:26.035
- build reports on data like this, they kinda

731
00:26:26.035 --> 00:26:27.714
- want them to be accurate. So if you

732
00:26:27.714 --> 00:26:29.894
- can use some of these tools as well,

733
00:26:29.954 --> 00:26:32.115
- to your point, help ensure the accuracy, help

734
00:26:32.115 --> 00:26:34.934
- ensure the make sure everything is

735
00:26:35.549 --> 00:26:37.730
- working properly, working the way it should,

736
00:26:38.509 --> 00:26:40.430
- I think there's a lot of lot of

737
00:26:40.430 --> 00:26:42.509
- options here that you start getting. Or just

738
00:26:42.509 --> 00:26:43.630
- the fact that now you can work on

739
00:26:43.630 --> 00:26:45.470
- a report with your best friend, Scott. You

740
00:26:45.470 --> 00:26:47.470
- and I can go work on reports together.

741
00:26:47.470 --> 00:26:50.055
- Best friend, your best AI agent, all all

742
00:26:50.055 --> 00:26:51.734
- those things. Yeah. All the things. I will

743
00:26:51.734 --> 00:26:53.355
- say one of the I guess

744
00:26:54.615 --> 00:26:57.015
- and I I wonder for being in preview

745
00:26:57.015 --> 00:26:58.775
- for three years now, like, why this gap

746
00:26:58.775 --> 00:27:00.714
- hasn't been filled more by Microsoft.

747
00:27:01.414 --> 00:27:02.934
- So if you go and you read the

748
00:27:02.934 --> 00:27:05.130
- documentation for this, it kinda

749
00:27:05.589 --> 00:27:06.089
- stops

750
00:27:06.549 --> 00:27:09.750
- at initialize a Git repo. So it tells

751
00:27:09.750 --> 00:27:12.390
- you how to enable this. It tells you

752
00:27:12.390 --> 00:27:13.049
- how to

753
00:27:13.829 --> 00:27:17.130
- create the new folder structure format thing

754
00:27:17.595 --> 00:27:19.595
- and get you spun up and kinda how

755
00:27:19.595 --> 00:27:20.255
- to do

756
00:27:20.634 --> 00:27:23.115
- an initial load into a Git repo. But

757
00:27:23.115 --> 00:27:23.934
- it leaves

758
00:27:25.035 --> 00:27:26.474
- all the follow on stuff, and I think

759
00:27:26.474 --> 00:27:28.335
- the power of it, the the versioning,

760
00:27:28.634 --> 00:27:29.134
- CICD

761
00:27:30.154 --> 00:27:33.690
- capabilities, things like that, just as an exercise

762
00:27:33.990 --> 00:27:36.149
- to the reader. So you will have to

763
00:27:36.149 --> 00:27:38.569
- go out and Google Bing, DuckDuckGo,

764
00:27:39.349 --> 00:27:41.690
- Kage, whatever your search engine of choice is.

765
00:27:41.990 --> 00:27:45.029
- If you're looking for, like, specific guidance on

766
00:27:45.029 --> 00:27:47.095
- how to configure, say, like, a CICD

767
00:27:47.555 --> 00:27:48.055
- pipeline

768
00:27:48.914 --> 00:27:51.154
- or some GitHub actions and wire them up

769
00:27:51.154 --> 00:27:53.234
- around this, you're gonna have to go, like,

770
00:27:53.234 --> 00:27:55.075
- find that stuff and hope somebody blogged about

771
00:27:55.075 --> 00:27:56.595
- it or figure it out and blog about

772
00:27:56.595 --> 00:27:59.715
- it yourself because that guidance doesn't exist from

773
00:27:59.715 --> 00:28:02.690
- Microsoft. Yeah. I was looking through this, and

774
00:28:02.690 --> 00:28:04.609
- it is. Like, that ends up with, here

775
00:28:04.609 --> 00:28:06.609
- you go. Initialize your git repo. And then

776
00:28:06.609 --> 00:28:08.609
- I was looking at one of the other

777
00:28:08.609 --> 00:28:11.730
- ones, editing Power BI files externally, and it

778
00:28:11.730 --> 00:28:13.089
- talks about how you can open them in

779
00:28:13.089 --> 00:28:15.265
- Visual Studio Code. And it says, here's the

780
00:28:15.265 --> 00:28:16.704
- button. Just go open it in Visual Studio

781
00:28:16.704 --> 00:28:18.944
- Code. It doesn't really give you, like okay.

782
00:28:18.944 --> 00:28:21.605
- So once it's open in Visual Studio Code,

783
00:28:22.065 --> 00:28:23.204
- what am I supposed

784
00:28:23.744 --> 00:28:26.065
- to do with it? I now get access

785
00:28:26.065 --> 00:28:28.464
- to the report and semantic model definition files,

786
00:28:28.464 --> 00:28:30.319
- but what do I do from there? We'll

787
00:28:30.319 --> 00:28:32.000
- say it also does call out to your

788
00:28:32.000 --> 00:28:34.259
- earlier point, Scott, under some of the limitations

789
00:28:34.480 --> 00:28:34.980
- is

790
00:28:35.359 --> 00:28:37.440
- not all of those project files that you

791
00:28:37.440 --> 00:28:40.160
- may see open up in Visual Studio Code

792
00:28:40.160 --> 00:28:41.299
- or within this file

793
00:28:41.680 --> 00:28:42.180
- support

794
00:28:42.765 --> 00:28:45.724
- editing. It's not saying the blocks editing. Like,

795
00:28:45.724 --> 00:28:47.984
- there's some JSON files in there, a report,

796
00:28:48.045 --> 00:28:49.184
- a mobile state,

797
00:28:50.205 --> 00:28:51.984
- semantic model diagram layout

798
00:28:52.285 --> 00:28:54.445
- where it's JSON. You could edit it in

799
00:28:54.445 --> 00:28:55.424
- any text editor,

800
00:28:55.980 --> 00:28:58.380
- but you might break it here because that's

801
00:28:58.380 --> 00:29:01.180
- not supported in this. So there are other

802
00:29:01.180 --> 00:29:02.240
- areas of the documentation

803
00:29:03.740 --> 00:29:05.819
- too that I would go read before you

804
00:29:05.819 --> 00:29:08.384
- just start editing some of those text based

805
00:29:08.384 --> 00:29:09.825
- files in there. I think if you're actually

806
00:29:09.825 --> 00:29:11.585
- gonna do it, like, in a collaborative way

807
00:29:11.585 --> 00:29:13.345
- too, like, say, you and I were kinda

808
00:29:13.345 --> 00:29:15.345
- going back and forth on something, you do

809
00:29:15.345 --> 00:29:17.205
- need to decide upfront

810
00:29:17.825 --> 00:29:18.325
- about

811
00:29:19.184 --> 00:29:21.125
- kinda how you're gonna approach

812
00:29:22.000 --> 00:29:25.059
- isolation for, like, your changes versus my changes,

813
00:29:25.119 --> 00:29:27.119
- things like that. And, again, this is an

814
00:29:27.119 --> 00:29:30.240
- area that, like, Microsoft doesn't have, like, discrete

815
00:29:30.240 --> 00:29:32.000
- guidance for you or prescriptive guidance, but I

816
00:29:32.000 --> 00:29:33.839
- think there's plenty out there in the community.

817
00:29:33.839 --> 00:29:36.315
- So you can do things like

818
00:29:36.774 --> 00:29:38.634
- you and I could be working

819
00:29:39.335 --> 00:29:41.835
- in the same same report, same dashboard,

820
00:29:42.375 --> 00:29:43.914
- but we could have isolated

821
00:29:44.615 --> 00:29:45.115
- workspaces,

822
00:29:45.734 --> 00:29:48.214
- effectively, like, a dev workspace for you, a

823
00:29:48.214 --> 00:29:50.619
- dev workspace for me. Like, if we were

824
00:29:50.619 --> 00:29:52.859
- working in, say, like, a a a Git

825
00:29:52.859 --> 00:29:53.359
- repo,

826
00:29:53.740 --> 00:29:56.059
- we'd wanna do things, like, probably, like, a

827
00:29:56.059 --> 00:29:58.539
- feature branch per workspace. So, like, I'm gonna

828
00:29:58.539 --> 00:30:00.460
- go spin up like, I'm gonna go work

829
00:30:00.460 --> 00:30:01.200
- on the

830
00:30:01.500 --> 00:30:03.464
- new DAX measures for for blah blah blah.

831
00:30:03.464 --> 00:30:05.005
- You're gonna go work on the visualizations

832
00:30:05.305 --> 00:30:06.444
- for report page

833
00:30:06.825 --> 00:30:09.944
- a, b, c kinda thing. So you you

834
00:30:09.944 --> 00:30:12.664
- do end up into, I think, more, like,

835
00:30:12.664 --> 00:30:14.285
- the geeky, like, Git semantics

836
00:30:14.839 --> 00:30:16.039
- that are out there. And, again, that's where

837
00:30:16.039 --> 00:30:18.759
- I'm more, like, enterprise developer than enterprise power

838
00:30:18.759 --> 00:30:19.259
- user

839
00:30:19.799 --> 00:30:22.119
- if you do go down this path. But

840
00:30:22.119 --> 00:30:24.680
- there's definitely, like, some nicety there, I think,

841
00:30:24.680 --> 00:30:26.440
- even if you're just, like, a solo person.

842
00:30:26.440 --> 00:30:27.880
- Right? You wanna go and have kind of

843
00:30:27.880 --> 00:30:31.744
- that, like, go forward, go back, replay logic

844
00:30:31.744 --> 00:30:34.224
- that you get with things like a with,

845
00:30:34.224 --> 00:30:35.205
- like, a Git repo.

846
00:30:35.585 --> 00:30:37.664
- Could be worth learning even for, like, the

847
00:30:37.664 --> 00:30:40.404
- solo Power BI developer out there. Yeah. Because

848
00:30:40.465 --> 00:30:42.884
- even though this is collaborative, I'm assuming

849
00:30:43.345 --> 00:30:46.619
- because it is Git, you're still doing commits

850
00:30:46.619 --> 00:30:48.859
- and branches and all of that. And you

851
00:30:48.859 --> 00:30:49.599
- could still

852
00:30:49.980 --> 00:30:51.980
- very much end up with a conflict if

853
00:30:51.980 --> 00:30:53.740
- you and I both decide to go edit

854
00:30:53.740 --> 00:30:55.339
- the same thing and change the same thing

855
00:30:55.339 --> 00:30:57.200
- in the same file at the same time

856
00:30:57.259 --> 00:30:59.474
- where then you have to decide which change

857
00:30:59.474 --> 00:31:01.914
- is better, my change or Scott's change? Yours

858
00:31:01.914 --> 00:31:03.054
- is always gonna be better.

859
00:31:03.515 --> 00:31:06.154
- It's definitely something worth looking at if you're

860
00:31:06.154 --> 00:31:08.234
- in Power BI a lot. If you and

861
00:31:08.234 --> 00:31:10.554
- coworkers are working on Power BI reports and

862
00:31:10.554 --> 00:31:12.029
- you wanna take some

863
00:31:12.730 --> 00:31:14.109
- or use some of that functionality,

864
00:31:14.410 --> 00:31:16.890
- this is something I will probably do as

865
00:31:16.890 --> 00:31:19.690
- well just from a I lose Power BI

866
00:31:19.769 --> 00:31:21.930
- the PBI. I keep saying Power BI. I

867
00:31:21.930 --> 00:31:25.049
- lose PBIX files, Scott, all the time. I'm

868
00:31:25.049 --> 00:31:27.565
- like, where did I create it? Which desktop

869
00:31:27.865 --> 00:31:29.884
- documents folder did I put it in?

870
00:31:30.505 --> 00:31:33.545
- I for whatever reason, because you have to

871
00:31:33.545 --> 00:31:35.625
- save them locally and then publish Milan, I'm

872
00:31:35.625 --> 00:31:37.305
- always losing them. I'm like, you know what?

873
00:31:37.305 --> 00:31:39.160
- If I just started doing this and had

874
00:31:39.160 --> 00:31:41.079
- a git repo with all my Power BI

875
00:31:41.079 --> 00:31:43.640
- files or a git repo per client where

876
00:31:43.640 --> 00:31:45.740
- I'm creating these PBIP files,

877
00:31:46.200 --> 00:31:48.920
- it would just greatly help even to your

878
00:31:48.920 --> 00:31:51.099
- point as a solo person with

879
00:31:51.644 --> 00:31:54.684
- keeping track of my different Power BI reports

880
00:31:54.684 --> 00:31:56.625
- and where kind of that source

881
00:31:57.244 --> 00:31:59.805
- report source file is. Move them all into

882
00:31:59.805 --> 00:32:00.945
- PBIP and GitHub.

883
00:32:01.484 --> 00:32:04.144
- I never even tried to convert one. Like,

884
00:32:05.079 --> 00:32:07.000
- can you convert them? I think you can.

885
00:32:07.000 --> 00:32:09.159
- I think I saw the documentation in there.

886
00:32:09.159 --> 00:32:10.619
- I always just start in,

887
00:32:11.159 --> 00:32:13.159
- start in a modality and go from there.

888
00:32:13.159 --> 00:32:15.720
- PbIP enable PB. Save as a project. If

889
00:32:15.720 --> 00:32:17.639
- you're working on a new project or you

890
00:32:17.639 --> 00:32:18.700
- opened an existing

891
00:32:19.024 --> 00:32:21.904
- Power BI Desktop PBIX file, you can save

892
00:32:21.904 --> 00:32:24.144
- your work as a Power BI project file.

893
00:32:24.144 --> 00:32:26.224
- So you just do, like, the file save

894
00:32:26.224 --> 00:32:28.384
- as, and then in the drop down for

895
00:32:28.384 --> 00:32:30.544
- the save as type, you can switch it

896
00:32:30.544 --> 00:32:33.150
- to PBIP. That's an interesting so so, like,

897
00:32:33.710 --> 00:32:35.230
- like, these tools are so all over the

898
00:32:35.230 --> 00:32:37.150
- place. Like, I don't think I ever use

899
00:32:37.150 --> 00:32:38.849
- the save as dialogue

900
00:32:39.150 --> 00:32:41.470
- in Power BI once I initially create a

901
00:32:41.470 --> 00:32:43.309
- a a project and I go and publish

902
00:32:43.309 --> 00:32:45.164
- it. Once you publish it, it just asks

903
00:32:45.244 --> 00:32:46.924
- you to save again. Like, do you wanna

904
00:32:46.924 --> 00:32:48.845
- save this before you publish it to the

905
00:32:48.845 --> 00:32:51.164
- service? Yeah. I wanna save it. So I

906
00:32:51.164 --> 00:32:53.505
- would never see the save as dialogue.

907
00:32:54.045 --> 00:32:55.984
- Now you can go use the save as.

908
00:32:56.045 --> 00:32:58.380
- Because I did see I think somewhere in

909
00:32:58.380 --> 00:32:59.119
- this documentation,

910
00:32:59.980 --> 00:33:03.039
- it does say that PBIP is going to

911
00:33:03.259 --> 00:33:05.820
- I'm assuming once it hits GA, turn into

912
00:33:05.820 --> 00:33:08.059
- the default file type. I would imagine. Right?

913
00:33:08.059 --> 00:33:09.580
- Like, that that would be kinda like the

914
00:33:09.580 --> 00:33:12.220
- happy path for these things to go on

915
00:33:12.220 --> 00:33:12.720
- is

916
00:33:13.144 --> 00:33:14.984
- let it just be the default state. And

917
00:33:14.984 --> 00:33:16.105
- it really doesn't matter at the end of

918
00:33:16.105 --> 00:33:17.224
- the day. Like, it's gonna be a set

919
00:33:17.224 --> 00:33:19.304
- of files and folders locally, or it's gonna

920
00:33:19.304 --> 00:33:20.924
- be a monolithic thing.

921
00:33:21.224 --> 00:33:22.744
- Arguably better, just have it be the files

922
00:33:22.744 --> 00:33:24.424
- and folders locally, and then if you wanna

923
00:33:24.424 --> 00:33:25.704
- push to Git and be done with it.

924
00:33:25.704 --> 00:33:27.784
- Exactly. Just like we did with I'm gonna

925
00:33:27.784 --> 00:33:29.759
- go back to my office analogy. Just like

926
00:33:29.759 --> 00:33:32.820
- we did where doc and XLS and PPT

927
00:33:32.880 --> 00:33:35.759
- and the other ones all switched. They just

928
00:33:35.759 --> 00:33:38.080
- added an x there. Not to confuse you

929
00:33:38.080 --> 00:33:40.240
- because in Power BI, it had an x

930
00:33:40.240 --> 00:33:42.019
- and then it went to a p.

931
00:33:42.984 --> 00:33:45.144
- Naming, even when it comes to file types,

932
00:33:45.144 --> 00:33:47.704
- can be hard. Such is life. Yep. Alright,

933
00:33:47.704 --> 00:33:49.784
- Scott. With that, we are coming up on

934
00:33:49.784 --> 00:33:51.944
- our We got some new MCP servers, new

935
00:33:51.944 --> 00:33:54.345
- stuff for folks to go play within Power

936
00:33:54.345 --> 00:33:56.184
- BI. And we have meetings coming up that

937
00:33:56.184 --> 00:33:58.410
- we should probably go to keep people happy.

938
00:33:58.470 --> 00:34:00.070
- I do. I don't know if you do.

939
00:34:00.070 --> 00:34:01.589
- I have a meeting coming up. I do.

940
00:34:01.589 --> 00:34:03.269
- I'm gonna roll from this one just into

941
00:34:03.269 --> 00:34:04.170
- my next, and

942
00:34:04.549 --> 00:34:06.150
- and then let's go. We'll have to come

943
00:34:06.150 --> 00:34:08.630
- back sometime and revisit the whole LLM Wiki

944
00:34:08.630 --> 00:34:10.789
- thing because, like, I went down your path

945
00:34:10.789 --> 00:34:12.824
- and built, like, a whole dashboard for mine,

946
00:34:12.905 --> 00:34:14.264
- and I went up, like, a little I

947
00:34:14.264 --> 00:34:16.184
- went a little wild on the side. But

948
00:34:16.344 --> 00:34:18.344
- Do you have any tokens left? Yes. I

949
00:34:18.344 --> 00:34:20.905
- have tokens left. Yeah. We will because I

950
00:34:20.905 --> 00:34:23.804
- keep expanding. I keep trying to

951
00:34:24.264 --> 00:34:26.264
- like, I need to actually get work done

952
00:34:26.264 --> 00:34:28.319
- instead of playing with what can I build

953
00:34:28.380 --> 00:34:30.380
- with AI and my LLM Wiki and all

954
00:34:30.380 --> 00:34:31.900
- this other stuff? I tend to get a

955
00:34:31.900 --> 00:34:34.059
- little distracted with that. So we will come

956
00:34:34.059 --> 00:34:36.539
- back to that. But for those of you

957
00:34:36.539 --> 00:34:37.920
- listening, if you do

958
00:34:39.019 --> 00:34:42.664
- play with these, have any other thoughts, or

959
00:34:43.125 --> 00:34:46.085
- anything about Power BI and MCP servers and

960
00:34:46.085 --> 00:34:47.304
- Power BI or PBIP.

961
00:34:47.765 --> 00:34:48.505
- Would love

962
00:34:48.965 --> 00:34:50.664
- to hear from you. LinkedIn

963
00:34:51.125 --> 00:34:53.844
- or Reddit? We've had some more conversations lately

964
00:34:53.844 --> 00:34:56.405
- on Reddit as well. So I would say

965
00:34:56.405 --> 00:34:57.809
- those are probably the

966
00:34:59.090 --> 00:35:00.550
- two social media

967
00:35:01.090 --> 00:35:03.590
- platforms you and I are both the most

968
00:35:03.650 --> 00:35:05.969
- active on is either LinkedIn or Certainly for

969
00:35:05.969 --> 00:35:08.130
- the podcast. That's a great place to find

970
00:35:08.130 --> 00:35:10.065
- us. Yep. Join us over there. And it's

971
00:35:10.065 --> 00:35:11.824
- been really good to have the feedback over

972
00:35:11.824 --> 00:35:14.144
- on Reddit. So folks should keep that coming.

973
00:35:14.144 --> 00:35:15.585
- For sure. And if you are gonna be

974
00:35:15.585 --> 00:35:17.744
- at TechCon three sixty five in Seattle this

975
00:35:17.744 --> 00:35:19.984
- week, this will come out Thursday morning. I

976
00:35:19.984 --> 00:35:21.664
- will be there Thursday and Friday. So if

977
00:35:21.664 --> 00:35:23.505
- you're there and you wanna say hi, come

978
00:35:23.505 --> 00:35:25.670
- say hi to me. Scott won't be there.

979
00:35:25.730 --> 00:35:27.670
- Sad face. I will not be at TechCon.

980
00:35:27.809 --> 00:35:28.309
- Yeah.

981
00:35:28.769 --> 00:35:31.170
- Outside my wheelhouse these days. Yeah. Not so

982
00:35:31.170 --> 00:35:34.289
- much Azure storage blob stuff there. But for

983
00:35:34.289 --> 00:35:36.289
- now, go enjoy your Monday, Scott. Get some

984
00:35:36.289 --> 00:35:38.769
- work done. Enjoy the puppy, and we will

985
00:35:38.769 --> 00:35:40.304
- talk to you again soon. Thanks, Ben.

986
00:35:42.304 --> 00:35:44.545
- If you enjoyed the podcast, go leave us

987
00:35:44.545 --> 00:35:46.784
- a five star rating in iTunes. It helps

988
00:35:46.784 --> 00:35:48.464
- to get the word out so more IT

989
00:35:48.464 --> 00:35:50.625
- pros can learn about Office three sixty five

990
00:35:50.625 --> 00:35:51.284
- and Azure.

991
00:35:51.824 --> 00:35:53.505
- If you have any questions you want us

992
00:35:53.505 --> 00:35:55.664
- to address on the show or feedback about

993
00:35:55.664 --> 00:35:58.039
- the show, feel free to reach out via

994
00:35:58.039 --> 00:36:00.219
- our website, Twitter, or Facebook.

995
00:36:00.519 --> 00:36:02.360
- Thanks again for listening, and have a great

996
00:36:02.360 --> 00:36:02.860
- day.