Episode 379 – Azure Verified Modules

July 04, 2024

Episode Transcript

Welcome to Episode 379 of the Microsoft Cloud IT Pro Podcast. In this episode, Ben and Scott take a look at Azure Verified Modules, a new initiative from Microsoft to consolidate and set the standards for what a good Bicep and/or Terraform module looks like.

Like what you hear and want to support the show? Check out our membership options.

Show Notes

Ember Temperature Control Smart Mug 2, 14 Oz, App-Controlled Heated Coffee Mug with 80 Min Battery Life and Improved Design, Black
Azure Verified Modules
- What, Why, How
- Module Indexes
- Module Support
- Terraform Modules
- Community Calls
- John Savill – Azure Verified Modules Overview

About the sponsors

Would you like to become the irreplaceable Microsoft 365 resource for your organization? Let us know!

See full episode transcriptTranscript is autogenerated by AI

1 00:00:03,540 --> 00:00:06,087 Welcome to episode 379 2 00:00:06,087 --> 00:00:09,324 of the Microsoft Cloud It pro podcast recorded 3 00:00:09,602 --> 00:00:11,588 on 07/01/2024. 4 00:00:12,065 --> 00:00:14,447 This is a show about Microsoft 3 65 5 00:00:14,447 --> 00:00:16,989 in Azure from the perspective of It pros 6 00:00:16,989 --> 00:00:18,949 and end users where we discuss the top 7 00:00:19,229 --> 00:00:21,143 or recent news and how it relates to 8 00:00:21,143 --> 00:00:23,774 you. We're back after vacation with a new 9 00:00:23,934 --> 00:00:26,725 Azure topic to discuss in this week's episode. 10 00:00:27,363 --> 00:00:29,295 Today, Ben and Scott take a look at 11 00:00:29,454 --> 00:00:32,975 Azure verified modules, a new initiative for Microsoft 12 00:00:32,975 --> 00:00:35,695 to consolidate and set the standards for when 13 00:00:35,695 --> 00:00:38,890 a good by and or terra module looks 14 00:00:38,890 --> 00:00:39,208 like. 15 00:00:41,273 --> 00:00:43,674 My wife broke my Michigan coffee mug. I 16 00:00:43,674 --> 00:00:45,115 had to get a new Michigan coffee, Michael 17 00:00:45,115 --> 00:00:47,215 while I was up there on vacation. Mh 18 00:00:47,274 --> 00:00:49,034 it's a little bit of a pas. Did 19 00:00:49,034 --> 00:00:50,715 you replace... You probably can't get, like, an 20 00:00:50,875 --> 00:00:51,854 Em branded 21 00:00:52,249 --> 00:00:53,765 mug. I'm still in love with my amber 22 00:00:53,765 --> 00:00:55,143 mug. Your. I 23 00:00:55,840 --> 00:00:57,117 do not have a number. I just have 24 00:00:57,117 --> 00:00:59,272 a great big, so I have realized... I 25 00:00:59,272 --> 00:01:01,201 have a great big mug. My mug is 26 00:01:01,201 --> 00:01:03,352 like a 16 ounce or 20 ounce mug. 27 00:01:03,830 --> 00:01:06,856 My coffee does not stay hot, but I 28 00:01:06,856 --> 00:01:08,529 don't run out of coffee as quickly. 29 00:01:09,899 --> 00:01:11,333 Like, my wife broke, and I switched to 30 00:01:11,333 --> 00:01:12,848 a little coffee mug, and I'm like, I 31 00:01:12,848 --> 00:01:14,363 ran out of coffee way too fast. This 32 00:01:14,363 --> 00:01:16,138 is way too many trips 33 00:01:16,515 --> 00:01:18,602 back down to the coffee pot. On a 34 00:01:18,602 --> 00:01:20,753 daily basis. I need my big coffee mug 35 00:01:20,753 --> 00:01:23,619 back. Yeah. Amber does make some big bugs. 36 00:01:23,858 --> 00:01:26,008 I have, like, big travel mugs now and 37 00:01:26,008 --> 00:01:27,700 all sorts of things. I'm scared to get 38 00:01:27,700 --> 00:01:29,620 the travel mug though because I am 1 39 00:01:29,620 --> 00:01:31,319 of those people who 40 00:01:32,420 --> 00:01:32,920 absolutely 41 00:01:34,099 --> 00:01:34,599 loses 42 00:01:35,074 --> 00:01:37,472 my water bottle, like anytime. Have in my 43 00:01:37,472 --> 00:01:40,189 backpack and I travel anywhere. Yep. Then. So 44 00:01:40,349 --> 00:01:43,326 I don't want to have... What's already an 45 00:01:43,625 --> 00:01:44,125 overpriced 46 00:01:44,677 --> 00:01:45,177 funky 47 00:01:45,869 --> 00:01:48,013 toy, which is absolutely delightful. Like, don't get 48 00:01:48,013 --> 00:01:50,475 me wrong. Having always hot coffee at your 49 00:01:50,475 --> 00:01:53,096 desk is absolutely the way that 1 should 50 00:01:53,096 --> 00:01:54,779 lift their life. But, yeah. 51 00:01:55,652 --> 00:01:57,160 It's like, I don't wanna buy a hundred 52 00:01:57,160 --> 00:01:59,463 and 50 dollar tumble and then just have 53 00:01:59,463 --> 00:02:02,480 it, you know, not actually do the things 54 00:02:02,480 --> 00:02:04,803 that it needs too. So... Yes. Like make 55 00:02:04,803 --> 00:02:06,475 it home from a trip. Like, like, make 56 00:02:06,475 --> 00:02:08,069 it home from a trip. Yes. The the 57 00:02:08,069 --> 00:02:10,799 number of water bottles that I have donated 58 00:02:11,096 --> 00:02:12,392 to the 59 00:02:12,704 --> 00:02:14,796 shuttle bus at the airport is 60 00:02:15,330 --> 00:02:17,320 untold. And those, like, most of the ones 61 00:02:17,479 --> 00:02:18,911 I I kinda gave up. I doing la 62 00:02:18,911 --> 00:02:20,105 water bottles. I don't know if you ever 63 00:02:20,105 --> 00:02:21,219 seen those. They're the ones that have, like, 64 00:02:21,299 --> 00:02:22,987 the little Uv light built into the top. 65 00:02:23,306 --> 00:02:24,583 So I was doing those for a while. 66 00:02:24,822 --> 00:02:26,258 Okay. But then I was losing those, and 67 00:02:26,258 --> 00:02:28,971 those are, like, also cost money or water 68 00:02:28,971 --> 00:02:30,731 bottles like, not like, oh, this was a 69 00:02:30,731 --> 00:02:32,317 5 dollar water bottle at Target It's more 70 00:02:32,317 --> 00:02:33,664 like oh. This is a hundred dollar water 71 00:02:33,664 --> 00:02:36,121 bottle in Amazon. So after losing 2 of 72 00:02:36,121 --> 00:02:36,438 those. 73 00:02:37,088 --> 00:02:38,680 I'm done. I just... I'd have to be 74 00:02:38,680 --> 00:02:41,387 that person who buys a 20 dollar bottle 75 00:02:41,387 --> 00:02:42,900 bottled of water at the airport once I'm 76 00:02:42,900 --> 00:02:44,833 inside it now. How how 77 00:02:45,304 --> 00:02:46,900 Do you like, set them down next to 78 00:02:46,900 --> 00:02:48,497 your bag instead of putting it back in 79 00:02:48,497 --> 00:02:50,014 your bag or they fall on at your 80 00:02:50,014 --> 00:02:52,829 bag? My bag doesn't have, like, the 81 00:02:53,367 --> 00:02:54,898 they just fall off the side. Like, they're 82 00:02:54,898 --> 00:02:55,936 just in the little thing on the side 83 00:02:55,936 --> 00:02:57,453 because I put them in my bag. Right? 84 00:02:57,613 --> 00:02:59,608 They're they're attached to my bag and, like, 85 00:02:59,768 --> 00:03:01,066 in in the in the little 86 00:03:02,323 --> 00:03:03,280 little pocket on the side. 87 00:03:04,013 --> 00:03:06,166 So what you really need is instead of 88 00:03:06,166 --> 00:03:08,398 cheap water bottles, you need a bag that 89 00:03:08,398 --> 00:03:10,412 has a deeper, larger, 90 00:03:10,948 --> 00:03:11,448 better 91 00:03:12,399 --> 00:03:14,235 water bottle holder on the side of your 92 00:03:14,235 --> 00:03:16,150 bag so that they don't fall. My gosh. 93 00:03:16,310 --> 00:03:18,625 Oh, my gosh. Yes. So that's the fix 94 00:03:18,625 --> 00:03:20,700 is rather than hundreds of dollars of water 95 00:03:20,700 --> 00:03:21,155 bottles 96 00:03:21,513 --> 00:03:25,093 I need a new multi hundred dollar backpack 97 00:03:25,093 --> 00:03:27,002 because I just I have enough of those. 98 00:03:27,241 --> 00:03:29,245 I mean, you've already out. You've already spent 99 00:03:29,245 --> 00:03:31,791 200 dollars on water bottles, Like, at this 100 00:03:31,791 --> 00:03:33,803 point in time, a already. 101 00:03:34,179 --> 00:03:35,554 You've sort saved you 102 00:03:36,104 --> 00:03:37,544 Well, you still would have the water bottle. 103 00:03:37,865 --> 00:03:40,025 I don't know. Yeah. Right. I've I've I've 104 00:03:40,025 --> 00:03:42,264 already got a really really fancy 10 bucks 105 00:03:42,264 --> 00:03:43,280 2 backpack. So 106 00:03:43,717 --> 00:03:46,101 Anyway, neither here, nor there. Why don't we 107 00:03:46,101 --> 00:03:47,396 go ahead and 108 00:03:47,850 --> 00:03:49,360 get into our topic. So you've been on 109 00:03:49,360 --> 00:03:51,983 vacation for a while, I was a poor 110 00:03:51,983 --> 00:03:53,829 c and was not able to, 111 00:03:54,705 --> 00:03:57,594 secure any interviews in the intervening times. So 112 00:03:57,811 --> 00:03:59,881 we missed an episodes. So we'll have to 113 00:03:59,881 --> 00:04:01,235 backfill at some point and make that up. 114 00:04:01,648 --> 00:04:03,718 But anyway, let's get back into things today. 115 00:04:03,956 --> 00:04:05,787 We got more Azure stuff to talk about. 116 00:04:06,026 --> 00:04:07,856 Yes. And I won't say you were a 117 00:04:07,856 --> 00:04:09,846 puerto cohort c because you did... We did 118 00:04:09,846 --> 00:04:12,490 hit Microsoft to year end my vacation, Microsoft 119 00:04:12,490 --> 00:04:14,267 year end, all collided 120 00:04:14,884 --> 00:04:17,857 to create the missed episode. So 121 00:04:18,567 --> 00:04:20,235 It's funny. How much is an employee, the 122 00:04:20,235 --> 00:04:22,856 fiscal year affects me? It's also and I 123 00:04:22,856 --> 00:04:24,547 just distinctly remember this from my 124 00:04:24,921 --> 00:04:26,906 consulting day is working with partners. How much 125 00:04:27,303 --> 00:04:28,614 Microsoft is go close 126 00:04:29,151 --> 00:04:31,865 in bags partners as well. Oh, like, yes. 127 00:04:32,264 --> 00:04:34,180 I have some projects right now that it's 128 00:04:34,180 --> 00:04:36,709 like, is anybody out there and 129 00:04:37,704 --> 00:04:37,942 anyways. 130 00:04:38,738 --> 00:04:40,727 Funny thing is, your projects must be done 131 00:04:40,727 --> 00:04:41,602 to get invoice. 132 00:04:42,874 --> 00:04:44,642 But it does help when the folks on 133 00:04:44,642 --> 00:04:46,636 the other side aren't third in invoice. Right. 134 00:04:46,875 --> 00:04:50,065 Well, in when you're dependent on, like, feedback 135 00:04:50,065 --> 00:04:52,378 to finish the project in order to invoice. 136 00:04:54,388 --> 00:04:56,384 Oh, interesting scenarios. 137 00:04:56,943 --> 00:04:59,897 But... Yeah. That's my there. Our interesting topic 138 00:04:59,897 --> 00:05:02,052 for today. This is something you introduced me 139 00:05:02,052 --> 00:05:04,063 to since I was on vacation. Let you 140 00:05:04,063 --> 00:05:05,421 pick a topic, and I will come up 141 00:05:05,421 --> 00:05:06,858 with something for the next 1, 142 00:05:07,576 --> 00:05:08,635 But you 143 00:05:09,332 --> 00:05:10,471 brought up Azure 144 00:05:11,248 --> 00:05:11,748 verified 145 00:05:12,366 --> 00:05:12,866 modules. 146 00:05:13,339 --> 00:05:15,491 As a topic for today. This was interesting. 147 00:05:15,810 --> 00:05:17,426 There is a whole 148 00:05:18,201 --> 00:05:20,672 page that we put. On as your verified 149 00:05:20,672 --> 00:05:21,071 modules, 150 00:05:21,564 --> 00:05:23,240 With a Youtube video this as, what are 151 00:05:23,240 --> 00:05:25,155 they? How can I get involved? Where can 152 00:05:25,235 --> 00:05:27,150 I learn more? What value do they offer? 153 00:05:27,868 --> 00:05:29,717 How do I use them? I have a 154 00:05:29,956 --> 00:05:31,704 Youtube logo in the way. No. Where do 155 00:05:31,784 --> 00:05:33,691 I use? Where do I use them? And 156 00:05:33,691 --> 00:05:34,963 what problems do they solve? 157 00:05:35,599 --> 00:05:37,904 So instead of going and watching this Youtube 158 00:05:37,904 --> 00:05:38,222 video? 159 00:05:38,954 --> 00:05:41,510 Scott is going to tell us the answer 160 00:05:41,510 --> 00:05:44,087 to all 6 of those questions in today's 161 00:05:44,147 --> 00:05:44,306 episode. 162 00:05:49,759 --> 00:05:51,840 Do you feel overwhelmed by trying to manage 163 00:05:51,840 --> 00:05:54,673 your office 3 65 environment are you facing 164 00:05:54,890 --> 00:05:57,383 unexpected issues that disrupt your company's productivity, 165 00:05:57,840 --> 00:05:59,673 intelligent is here to help much like you 166 00:05:59,673 --> 00:06:01,666 take your car to the mechanic that has 167 00:06:01,666 --> 00:06:03,750 specialized knowledge on how to best keep your 168 00:06:03,750 --> 00:06:06,693 car running, intelligent helps you with your Microsoft 169 00:06:06,693 --> 00:06:08,920 cloud environment because that's their expertise. 170 00:06:09,572 --> 00:06:11,640 Intelligent keeps up with the latest updates in 171 00:06:11,640 --> 00:06:13,788 the Microsoft cloud to help keep your business 172 00:06:13,788 --> 00:06:16,096 running smoothly and ahead of the curve. Whether 173 00:06:16,096 --> 00:06:18,347 you a small organization with just a few 174 00:06:18,347 --> 00:06:21,084 users up to an organization of several thousand 175 00:06:21,224 --> 00:06:23,621 employees. They want to partner with you to 176 00:06:23,621 --> 00:06:26,606 implement and administer your Microsoft cloud technology. 177 00:06:27,298 --> 00:06:30,819 Visit them at intelligent dot com slash podcast 178 00:06:31,113 --> 00:06:36,065 that's INTELLIGINK 179 00:06:36,065 --> 00:06:37,923 dot com slash podcast 180 00:06:38,301 --> 00:06:40,377 for more information or to schedule a 30 181 00:06:40,377 --> 00:06:42,293 minute call to get started with them today. 182 00:06:42,852 --> 00:06:46,137 Remember intelligent focuses on the Microsoft cloud, so 183 00:06:46,137 --> 00:06:47,732 you can focus on your business. 184 00:06:50,124 --> 00:06:52,037 First of all, what are Azure verified module, 185 00:06:52,276 --> 00:06:53,986 Scott? What our Azure 186 00:06:54,440 --> 00:06:56,611 verified modules. So Azure 187 00:06:56,986 --> 00:06:57,883 verified modules 188 00:06:58,576 --> 00:06:59,076 are 189 00:06:59,610 --> 00:07:01,281 a new ish initiative. 190 00:07:01,774 --> 00:07:02,274 From 191 00:07:02,814 --> 00:07:04,834 Microsoft to offer 192 00:07:05,134 --> 00:07:05,634 customers 193 00:07:06,334 --> 00:07:06,834 basically 194 00:07:07,454 --> 00:07:10,095 vetted ways to work with infrastructure as code. 195 00:07:10,748 --> 00:07:11,248 That 196 00:07:11,786 --> 00:07:13,004 align to 197 00:07:13,621 --> 00:07:14,441 best practices 198 00:07:15,217 --> 00:07:19,539 from Microsoft for things like Azure. Hence Azure 199 00:07:19,539 --> 00:07:21,950 verified modules. So if you think about being 200 00:07:22,007 --> 00:07:25,431 a customer who does infrastructure code, maybe you're 201 00:07:25,431 --> 00:07:28,720 doing terra form, and you've been using existing 202 00:07:28,720 --> 00:07:31,620 modules from Hash corp. Maybe you're using bi, 203 00:07:31,919 --> 00:07:34,419 things like that. And you're finding that 204 00:07:35,039 --> 00:07:35,539 the 205 00:07:35,934 --> 00:07:39,950 kind community modules that exist today around things 206 00:07:40,169 --> 00:07:43,045 in Azure, saying, like, just, like, from Mah 207 00:07:43,045 --> 00:07:45,695 hash Corp, in the terra form module registry. 208 00:07:46,015 --> 00:07:47,931 And don't always lie the best practices and 209 00:07:47,931 --> 00:07:49,527 and you need to do some additional work 210 00:07:49,527 --> 00:07:51,283 to make them get where they need to 211 00:07:51,283 --> 00:07:53,794 land. This is an attempt to 212 00:07:54,966 --> 00:07:55,466 kinda 213 00:07:55,842 --> 00:07:58,731 provide the community a set of modules 214 00:07:59,267 --> 00:08:01,815 that are aligned to those best practices. 215 00:08:02,308 --> 00:08:05,573 They are built by Microsoft out in the 216 00:08:05,573 --> 00:08:07,883 open. Right? These are all Os. You can 217 00:08:07,883 --> 00:08:09,714 continue to find these on Github, like you 218 00:08:09,714 --> 00:08:12,350 find many of your favorite kind of bi 219 00:08:12,350 --> 00:08:15,126 examples and and terra form modules today. But 220 00:08:15,126 --> 00:08:19,027 they specifically align to guidance from things like 221 00:08:19,027 --> 00:08:21,175 the well architect framework. 222 00:08:21,652 --> 00:08:23,880 So, like, if you think about you're a 223 00:08:23,880 --> 00:08:25,175 customer who 224 00:08:25,804 --> 00:08:27,958 does a bunch with virtual machines. So maybe 225 00:08:27,958 --> 00:08:30,053 you're using the existing 226 00:08:30,749 --> 00:08:33,323 compute modules from Hash Corp 227 00:08:33,700 --> 00:08:34,200 around 228 00:08:34,578 --> 00:08:35,296 virtual machines. 229 00:08:35,868 --> 00:08:38,495 Well, over on the other side here, you 230 00:08:38,495 --> 00:08:41,839 could also kinda take a run at using 231 00:08:41,839 --> 00:08:42,339 these 232 00:08:42,873 --> 00:08:43,430 verified modules. 233 00:08:44,003 --> 00:08:48,309 And leveraging them in your day today. So 234 00:08:48,309 --> 00:08:50,064 they'll do all the same things so that 235 00:08:50,064 --> 00:08:51,281 the existing 236 00:08:51,659 --> 00:08:54,069 community modules do. So, you know, if you're 237 00:08:54,069 --> 00:08:56,789 talking about, like, a virtual machine, that's, hey, 238 00:08:57,110 --> 00:08:59,110 I need to be able to create a 239 00:08:59,110 --> 00:09:00,629 windows or a Linux Vm, 240 00:09:01,364 --> 00:09:03,542 along with whatever common 241 00:09:04,001 --> 00:09:07,117 associated resources are there, things like knicks and 242 00:09:07,117 --> 00:09:09,688 disks and Ips and all that kind of 243 00:09:09,688 --> 00:09:11,285 stuff. So so that would be in these 244 00:09:11,285 --> 00:09:13,440 modules as well. And you kinda look at 245 00:09:13,440 --> 00:09:15,116 it and you go, like, alright. Great. So 246 00:09:15,116 --> 00:09:16,814 there's a module for 247 00:09:17,352 --> 00:09:21,033 virtual machines. Like, I've got Azure Rm virtual 248 00:09:21,033 --> 00:09:23,820 machine, maybe in the existing registry today. Why 249 00:09:23,820 --> 00:09:25,276 would I use Av 250 00:09:25,891 --> 00:09:27,006 compute virtual machine. 251 00:09:27,657 --> 00:09:27,974 Well, 252 00:09:28,530 --> 00:09:31,626 compute virtual machine, like the Azure verified module, 253 00:09:31,865 --> 00:09:34,802 it will offer you the same, if not 254 00:09:34,802 --> 00:09:35,937 more functionality. 255 00:09:36,724 --> 00:09:37,224 And 256 00:09:37,681 --> 00:09:40,015 again, it aligns to kind of best practices 257 00:09:40,631 --> 00:09:42,705 from things like the well architect and framework. 258 00:09:43,183 --> 00:09:46,149 And as these continue to mature, because they 259 00:09:46,149 --> 00:09:48,327 are built and designed by 260 00:09:49,186 --> 00:09:52,083 Microsoft and by folks who work directly with 261 00:09:52,143 --> 00:09:54,780 tooling, like virtual machines, storage, 262 00:09:55,433 --> 00:09:56,230 app services, 263 00:09:56,629 --> 00:09:58,143 functions, all these things day in day out. 264 00:09:58,542 --> 00:10:00,556 You also have a path to 265 00:10:01,172 --> 00:10:03,897 support ability potentially in the future. So my 266 00:10:03,897 --> 00:10:05,572 understanding is, like, the intention of this project 267 00:10:05,572 --> 00:10:09,162 is over time, these become things you can 268 00:10:09,162 --> 00:10:09,662 actually 269 00:10:10,039 --> 00:10:11,257 reach out to 270 00:10:12,033 --> 00:10:13,011 Microsoft for 271 00:10:13,723 --> 00:10:15,557 support. So if you go to a aka 272 00:10:15,557 --> 00:10:17,472 a dot ms forward slash av, 273 00:10:18,190 --> 00:10:20,604 that will take you to the Azure 274 00:10:20,981 --> 00:10:22,736 verified modules page. 275 00:10:23,389 --> 00:10:26,590 Is ultimately just github pages. So it's Azure 276 00:10:26,590 --> 00:10:28,509 dot github dot io o forward slash azure 277 00:10:28,509 --> 00:10:31,230 dash verified dash modules, and it can kinda 278 00:10:31,230 --> 00:10:33,403 walk you through all these things. So what 279 00:10:33,403 --> 00:10:35,557 are the existing terra form modules, what are 280 00:10:35,557 --> 00:10:39,088 the existing bi modules that exist out there 281 00:10:39,226 --> 00:10:42,177 for each of those subsets. So for bi 282 00:10:42,177 --> 00:10:44,924 and terra form, things are broken into 283 00:10:45,460 --> 00:10:46,177 resource modules. 284 00:10:46,735 --> 00:10:47,474 They're broken 285 00:10:48,009 --> 00:10:51,154 into pattern modules, and then there's also 286 00:10:52,003 --> 00:10:55,178 utility modules as well. So the the intent 287 00:10:55,178 --> 00:10:57,162 over time is, like, yes, you would have, 288 00:10:57,400 --> 00:10:59,876 say for, like, compute for virtual machines. You 289 00:10:59,876 --> 00:11:02,655 will have that compute module, and that would 290 00:11:02,655 --> 00:11:05,355 be a resource module. Like, that's something that's 291 00:11:05,355 --> 00:11:08,825 actually in, like, the Microsoft dot compute resource 292 00:11:09,184 --> 00:11:12,779 provider, and then you would have pattern modules. 293 00:11:13,338 --> 00:11:15,915 So a pattern thing might be 294 00:11:16,229 --> 00:11:18,322 to give you an example, like, a policy 295 00:11:18,459 --> 00:11:20,371 assignment, a role assignment, 296 00:11:20,929 --> 00:11:23,956 maybe you're instant shooting, landing zones, things like 297 00:11:23,956 --> 00:11:26,678 that. Things that are actually, like, patterns for 298 00:11:26,678 --> 00:11:27,576 deployment versus 299 00:11:28,270 --> 00:11:31,295 individual resource deployments and things like that. And 300 00:11:31,295 --> 00:11:32,988 then you'll have utilities 301 00:11:33,458 --> 00:11:35,208 as well. Yeah I don't know where the 302 00:11:35,208 --> 00:11:37,298 utilities are gonna bake out. There's actually none 303 00:11:37,355 --> 00:11:37,855 published 304 00:11:38,707 --> 00:11:39,207 today 305 00:11:39,661 --> 00:11:42,464 for either buy or terra form. I imagine 306 00:11:42,464 --> 00:11:44,941 utilities could be, like, quick helpers in the 307 00:11:44,941 --> 00:11:45,760 future. So, 308 00:11:46,139 --> 00:11:48,376 you know, maybe things to adhere to you 309 00:11:48,376 --> 00:11:49,655 say, like, naming standards. 310 00:11:50,624 --> 00:11:53,323 Across the board or adhere to tagging standards, 311 00:11:53,879 --> 00:11:55,173 things like that could 312 00:11:55,784 --> 00:11:58,363 potentially be available there. Tl, 313 00:11:58,734 --> 00:11:59,630 these are, 314 00:12:00,160 --> 00:12:00,319 again, 315 00:12:01,032 --> 00:12:01,507 official 316 00:12:01,983 --> 00:12:03,275 Microsoft driven 317 00:12:04,201 --> 00:12:04,701 modules 318 00:12:05,009 --> 00:12:07,663 for buy up and terra form that customers 319 00:12:07,801 --> 00:12:10,513 can come and kind of pick up today. 320 00:12:10,672 --> 00:12:11,869 And and when I say pickup up today, 321 00:12:12,108 --> 00:12:13,863 it's it's probably pick up today and more, 322 00:12:14,022 --> 00:12:16,054 like a Poc see sense, than 323 00:12:16,592 --> 00:12:18,430 production sense, and there's probably somebody out there 324 00:12:18,430 --> 00:12:20,108 on the Av side who's screaming at me 325 00:12:20,108 --> 00:12:22,025 right now. But the reason I say that 326 00:12:22,025 --> 00:12:24,530 is Lots of these things are relatively 327 00:12:25,065 --> 00:12:27,372 early. Like, like, don't get me wrong. They 328 00:12:27,372 --> 00:12:29,122 they absolutely do work and things like that. 329 00:12:29,853 --> 00:12:31,524 But, like, for example, if I look at 330 00:12:31,524 --> 00:12:34,548 the service bus module for terra form, it's 331 00:12:34,548 --> 00:12:37,491 currently at version 0 dot 1, like, most 332 00:12:37,491 --> 00:12:39,494 of these things are, like, 0 dot one's, 333 00:12:39,653 --> 00:12:41,243 0 dot twos, 0 dot 3, 334 00:12:41,958 --> 00:12:44,444 things like that. And some are kinda rapidly 335 00:12:44,818 --> 00:12:47,300 maturing. So I saw, like, Av was all 336 00:12:47,300 --> 00:12:48,358 the way up to 337 00:12:48,815 --> 00:12:50,011 0 dot 7 already. 338 00:12:50,808 --> 00:12:53,119 Virtual machines iterating rapidly. They're up to, like, 339 00:12:53,199 --> 00:12:53,996 0 dot 15. 340 00:12:54,965 --> 00:12:56,790 Eventually, these things make it to, you know, 341 00:12:56,949 --> 00:12:59,250 1 and they're out the door out the 342 00:12:59,250 --> 00:13:00,860 door and really 343 00:13:01,233 --> 00:13:04,211 ready to go. Got it. And I'm assuming 344 00:13:04,268 --> 00:13:05,325 that prior... 345 00:13:06,020 --> 00:13:08,590 I guess kind prior to this or 346 00:13:09,045 --> 00:13:10,160 up till now, maybe 347 00:13:10,797 --> 00:13:14,082 Microsoft has been contributing more to the community 348 00:13:14,082 --> 00:13:14,582 modules 349 00:13:15,199 --> 00:13:15,699 through 350 00:13:16,077 --> 00:13:18,764 terra form. And I'm assuming they've kinda pivoted 351 00:13:18,964 --> 00:13:20,958 they're not gonna... If they were doing community 352 00:13:20,958 --> 00:13:22,713 modules before. This is kinda now 353 00:13:23,351 --> 00:13:27,578 Microsoft's focus for Azure or for Terra form 354 00:13:27,578 --> 00:13:28,535 for Buy up is that, 355 00:13:29,186 --> 00:13:30,320 these are the modules 356 00:13:30,693 --> 00:13:31,169 that 357 00:13:31,565 --> 00:13:33,548 Microsoft will focus on that Microsoft will update. 358 00:13:33,786 --> 00:13:34,976 Kinda like you said, these are gonna be 359 00:13:34,976 --> 00:13:36,825 the ones that are always going to be 360 00:13:37,215 --> 00:13:38,735 up to date. They're gonna have the new 361 00:13:38,735 --> 00:13:39,235 functionality 362 00:13:40,095 --> 00:13:40,595 probably 363 00:13:40,894 --> 00:13:43,774 first unless somebody else beats them to it 364 00:13:43,774 --> 00:13:46,029 out on the community modules. But then you're 365 00:13:46,029 --> 00:13:47,627 gonna be running in a little bit more 366 00:13:47,627 --> 00:13:48,447 of an 367 00:13:48,826 --> 00:13:49,326 unsupported 368 00:13:49,785 --> 00:13:51,324 module, not really knowing 369 00:13:51,783 --> 00:13:54,500 how that particular community member updated that module. 370 00:13:54,740 --> 00:13:57,392 Yeah. Supports... Always always a weird kind of 371 00:13:57,392 --> 00:13:59,550 funky term. Right? Like, some folks in click 372 00:13:59,550 --> 00:14:01,308 support, like, oh, great. I can just, you 373 00:14:01,308 --> 00:14:03,226 know, call my Microsoft rep on the phone. 374 00:14:03,386 --> 00:14:04,285 Like, if I'm 375 00:14:04,599 --> 00:14:05,978 that kind of customer. So 376 00:14:06,597 --> 00:14:09,234 support ability here really does kind of follow 377 00:14:09,234 --> 00:14:12,670 the same flow as existing community modules. 378 00:14:13,482 --> 00:14:15,231 Most of these things are built in the 379 00:14:15,231 --> 00:14:16,742 open. Like, when I say most of these 380 00:14:16,742 --> 00:14:18,832 things like, existing terra form modules 381 00:14:19,446 --> 00:14:20,956 that are outside of Av. 382 00:14:21,448 --> 00:14:22,559 So they're built in the open. They're on 383 00:14:22,639 --> 00:14:24,940 Github, you can go open an issue. So 384 00:14:24,940 --> 00:14:28,035 let me take, like, again, I'll compute as 385 00:14:28,035 --> 00:14:30,360 an example. Oh, so the difference would be, 386 00:14:30,679 --> 00:14:32,753 you know, you run into an issue with 387 00:14:32,753 --> 00:14:35,783 your deployment with the compute module. And you're 388 00:14:35,783 --> 00:14:38,495 using the existing Hash court module. 389 00:14:38,909 --> 00:14:40,181 Well, you go out and you're running do 390 00:14:40,181 --> 00:14:41,772 an issue with that. You're gonna go out 391 00:14:41,772 --> 00:14:44,316 to github. You're gonna open an issue, and 392 00:14:44,316 --> 00:14:46,145 that is going to be triage by a 393 00:14:46,145 --> 00:14:47,754 whole ton of folks. Right It could be 394 00:14:47,754 --> 00:14:49,432 folks from Hash Corp. It could be folks 395 00:14:49,432 --> 00:14:52,628 from Microsoft, could be community support, just like, 396 00:14:52,788 --> 00:14:55,205 you know, via other contributors to 397 00:14:55,678 --> 00:14:57,745 that module or that re... That repo on 398 00:14:57,825 --> 00:15:00,608 Github things like that. So there's really no, 399 00:15:00,847 --> 00:15:03,391 like, Sla there when it comes to portability. 400 00:15:03,550 --> 00:15:05,141 It's also not clear like, 401 00:15:05,874 --> 00:15:08,272 you know, where the issue goes. Like, say 402 00:15:08,272 --> 00:15:09,950 you open up an issue for the compute 403 00:15:09,950 --> 00:15:10,269 module, 404 00:15:10,829 --> 00:15:12,907 and it turns out, like, oh, that's a 405 00:15:12,907 --> 00:15:14,686 thing in a 406 00:15:15,479 --> 00:15:18,585 core Sdk on the Microsoft side. Like, maybe 407 00:15:18,585 --> 00:15:19,859 it's something that needs to be fixed and, 408 00:15:19,939 --> 00:15:21,611 like, 1 of like the resource manager Sd 409 00:15:21,611 --> 00:15:23,761 sdk for compute to actually get it going. 410 00:15:24,414 --> 00:15:26,086 So if you're in Hash Corp world, well, 411 00:15:26,166 --> 00:15:28,077 that means somebody at Hash corp needs to 412 00:15:28,077 --> 00:15:29,511 know how to reach out to the folks 413 00:15:29,511 --> 00:15:31,205 at Microsoft or 414 00:15:31,661 --> 00:15:33,750 that customer then needs to go and open 415 00:15:33,750 --> 00:15:35,990 a support request. With Microsoft Microsoft goes. Oh, 416 00:15:36,149 --> 00:15:38,309 great. It's a community module from Hash Corp. 417 00:15:38,550 --> 00:15:39,990 We can't help you, but we'll see if 418 00:15:39,990 --> 00:15:41,750 we can connect you the right folks. All 419 00:15:41,750 --> 00:15:42,470 those kinds of things. 420 00:15:43,123 --> 00:15:45,740 So from that perspective, like, yeah. You've got 421 00:15:45,740 --> 00:15:47,960 community support with the Hash corp stuff and 422 00:15:47,960 --> 00:15:49,784 and with a bunch of the community modules 423 00:15:49,784 --> 00:15:50,339 that are out there. 424 00:15:51,068 --> 00:15:53,614 But who is supporting that and having an 425 00:15:53,773 --> 00:15:56,796 Sla behind that really is a fuzzy kind 426 00:15:56,796 --> 00:15:57,193 of thing. 427 00:15:58,004 --> 00:16:01,062 So in E land, the intent is, 428 00:16:01,760 --> 00:16:03,678 you know, that, at least in the early 429 00:16:03,678 --> 00:16:03,918 days, 430 00:16:04,557 --> 00:16:06,076 you know, go ahead and open an issue 431 00:16:06,076 --> 00:16:07,924 on Github. So you're in this same flow. 432 00:16:08,083 --> 00:16:09,908 You're you're you're gonna get Hub repo. You're 433 00:16:09,908 --> 00:16:11,970 opening an issue there. There's a little bit 434 00:16:11,970 --> 00:16:14,112 more of an expertise around Sla there, though. 435 00:16:14,604 --> 00:16:16,676 And this is all published out on the 436 00:16:16,836 --> 00:16:19,784 Av side if folks wanna go and take 437 00:16:19,784 --> 00:16:21,379 a look there. Yeah. If you go into 438 00:16:21,379 --> 00:16:24,260 the Lion and how, where where the Sla 439 00:16:24,260 --> 00:16:26,034 stuff. Got it. Yep. And 440 00:16:26,649 --> 00:16:27,308 go down 441 00:16:27,763 --> 00:16:28,263 below 442 00:16:28,639 --> 00:16:30,724 definition. So there's a link in there. At 443 00:16:30,724 --> 00:16:33,832 the very first bullet under verify definition, scroll 444 00:16:33,832 --> 00:16:35,666 it. Oh, I want to our radio for 445 00:16:35,666 --> 00:16:38,296 folks. Yep. There's module support there. 446 00:16:38,948 --> 00:16:40,700 So this will kind of spell out what 447 00:16:40,700 --> 00:16:41,200 module 448 00:16:41,575 --> 00:16:42,769 support is. So you're still gonna go to 449 00:16:42,769 --> 00:16:44,361 github. You're still gonna open an issue on 450 00:16:44,520 --> 00:16:44,759 Github, 451 00:16:45,475 --> 00:16:45,975 and 452 00:16:46,430 --> 00:16:46,930 the 453 00:16:47,306 --> 00:16:50,054 module contributors because it's gonna be in kinda 454 00:16:50,115 --> 00:16:53,154 individual contributors, these smaller, like, feature cruise, v 455 00:16:53,154 --> 00:16:55,475 teams that are responsible for these things. They're 456 00:16:55,475 --> 00:16:56,995 responsible for Triage. 457 00:16:57,649 --> 00:16:58,549 But then 458 00:16:58,929 --> 00:17:01,809 there's also a backing team kinda, like, to 459 00:17:01,809 --> 00:17:03,169 get about it as maybe, like, a governance 460 00:17:03,169 --> 00:17:05,089 board or something like that that sits behind 461 00:17:05,089 --> 00:17:05,170 this. 462 00:17:05,903 --> 00:17:07,176 That steps in with another set of rules. 463 00:17:07,335 --> 00:17:08,768 Like, if you open an issue and you 464 00:17:08,768 --> 00:17:10,836 don't get a response in 3 days, that 465 00:17:10,836 --> 00:17:12,825 core team is gonna step in, and they're 466 00:17:12,825 --> 00:17:14,678 gonna come in and start to kind of 467 00:17:15,069 --> 00:17:17,859 move those things along They're looking for bugs 468 00:17:17,859 --> 00:17:20,751 versus security issues, which potentially have 469 00:17:21,208 --> 00:17:24,252 different triage points along the way. And then 470 00:17:24,252 --> 00:17:24,752 theoretically, 471 00:17:25,289 --> 00:17:25,688 like, 472 00:17:26,406 --> 00:17:28,799 most of these module maintain, if not all 473 00:17:28,799 --> 00:17:29,538 of them 474 00:17:29,915 --> 00:17:33,207 should have direct hooks back into 475 00:17:33,758 --> 00:17:35,905 the right folks internally at Microsoft to go 476 00:17:35,905 --> 00:17:37,971 talk to. So, like, the way I learned 477 00:17:37,971 --> 00:17:38,607 about Av. 478 00:17:39,085 --> 00:17:42,197 I'm a Pm in object storage. And we 479 00:17:42,197 --> 00:17:45,313 actually had the community that's building these modules 480 00:17:45,447 --> 00:17:47,825 approach us and say, hey, we're thinking about 481 00:17:47,825 --> 00:17:49,668 doing this. What's the right way to do 482 00:17:49,668 --> 00:17:51,504 it. What are the things that you find 483 00:17:51,504 --> 00:17:53,579 or maybe gaps in the existing terra 4 484 00:17:53,579 --> 00:17:55,335 modules. So I'm like, well, this is awesome. 485 00:17:55,655 --> 00:17:57,092 I I get a new scale unit for 486 00:17:57,092 --> 00:17:57,730 my customers? 487 00:17:58,303 --> 00:18:00,369 They potentially get a better experience. And then 488 00:18:00,369 --> 00:18:02,196 if there are bugs or things that are 489 00:18:02,196 --> 00:18:03,229 in here that are surfaced, 490 00:18:03,786 --> 00:18:06,029 the folks who build these modules like, in 491 00:18:06,029 --> 00:18:08,110 my case, the, you know, they have a 492 00:18:08,110 --> 00:18:11,009 direct line back to me to ask questions 493 00:18:11,150 --> 00:18:14,118 or help get triage. Like, So saying storage 494 00:18:14,118 --> 00:18:16,190 land, there was an issue in the underlying, 495 00:18:16,269 --> 00:18:18,898 like, resource management Sd sdk for storage, 496 00:18:19,536 --> 00:18:22,095 that's something that I own is in my 497 00:18:22,095 --> 00:18:22,913 wheelhouse. So 498 00:18:23,287 --> 00:18:25,036 potentially, I can help move that along as 499 00:18:25,036 --> 00:18:25,536 well 500 00:18:25,910 --> 00:18:27,443 from my side. So 501 00:18:27,753 --> 00:18:29,424 When we talk about things, like, hey, like, 502 00:18:29,584 --> 00:18:30,402 this is a 503 00:18:30,857 --> 00:18:34,756 official Microsoft driven initiative, it's Microsoft up and 504 00:18:34,756 --> 00:18:37,394 down from the publishing on way to the 505 00:18:37,394 --> 00:18:40,564 back end and and support ability and kind 506 00:18:40,564 --> 00:18:42,465 of re reach out and res sourcing and 507 00:18:42,465 --> 00:18:44,075 all those kinds of things. So 508 00:18:44,543 --> 00:18:46,295 that's what excites me about it. Because in 509 00:18:46,295 --> 00:18:48,844 my world, I'll speak just from the storage 510 00:18:48,844 --> 00:18:49,003 side. 511 00:18:49,720 --> 00:18:52,189 I don't have anybody on, like, my developer 512 00:18:52,189 --> 00:18:55,237 experience team that's doing these things and building 513 00:18:55,237 --> 00:18:56,117 terra modules, 514 00:18:56,596 --> 00:18:59,073 but infrastructure is code is clearly important to 515 00:18:59,073 --> 00:19:00,912 my customers. Like, I get a lot of 516 00:19:00,912 --> 00:19:02,350 questions about it for my customers. 517 00:19:02,923 --> 00:19:05,065 So now I've got another team at Microsoft 518 00:19:05,065 --> 00:19:07,468 who's actually stepping in. They're building these 519 00:19:08,158 --> 00:19:10,458 official, you know, Microsoft Driven modules. 520 00:19:11,108 --> 00:19:12,697 I have line of sight to work they're 521 00:19:12,697 --> 00:19:14,921 doing. They have line of sight back back 522 00:19:14,921 --> 00:19:17,066 to me. Should they need any help blown 523 00:19:17,066 --> 00:19:18,893 the way or guidance or things like that. 524 00:19:19,625 --> 00:19:21,945 I think it's a really cool initiative. 525 00:19:22,585 --> 00:19:24,744 It's definitely early days. Like I said, like, 526 00:19:24,904 --> 00:19:26,505 lots of these modules are in there, like, 527 00:19:26,917 --> 00:19:28,347 you know, 0.1 528 00:19:28,347 --> 00:19:31,230 0.2 0.3 kind of thing, but they're rapidly 529 00:19:31,525 --> 00:19:33,749 maturing. And I think you'll see a lot 530 00:19:33,749 --> 00:19:34,702 of investment here. 531 00:19:35,592 --> 00:19:36,867 You know, as we just talked about, like, 532 00:19:36,946 --> 00:19:39,176 the new fiscal year coming up as the 533 00:19:39,176 --> 00:19:42,442 new fiscal spins up, Like... It's it's gonna 534 00:19:42,442 --> 00:19:45,506 be something that folks lean into, you'll rapidly 535 00:19:45,643 --> 00:19:48,189 see new modules come out across all these 536 00:19:48,189 --> 00:19:50,975 dimensions of, like, resource modules, pattern modules, utility 537 00:19:50,975 --> 00:19:53,442 modules, things like that. It's all moving fast 538 00:19:53,442 --> 00:19:55,765 and it's kind of an an exciting thing 539 00:19:55,765 --> 00:19:57,516 to watch from the outside. Yeah. And if 540 00:19:57,516 --> 00:19:59,505 you go in and look, like, I was 541 00:19:59,505 --> 00:20:02,131 looking at terra form. It looks like they 542 00:20:02,131 --> 00:20:02,927 have lots of plans. 543 00:20:03,578 --> 00:20:06,520 Forum them because it also gives you when 544 00:20:06,520 --> 00:20:09,326 you go into, like, the terra 4 modules 545 00:20:09,621 --> 00:20:11,529 or the buy up modules, you talked about 546 00:20:11,529 --> 00:20:12,722 resource pattern utility, 547 00:20:13,294 --> 00:20:15,606 how many are available. So for, like terra 548 00:20:15,606 --> 00:20:17,621 form, there are 39 549 00:20:17,759 --> 00:20:20,231 resource modules that are already out there, A 550 00:20:20,231 --> 00:20:22,119 0 that are orphan, which 551 00:20:22,478 --> 00:20:24,869 within that support article, we just referenced it 552 00:20:24,869 --> 00:20:25,848 talked about 553 00:20:26,225 --> 00:20:28,478 orphan modules essentially being 554 00:20:28,935 --> 00:20:31,019 modules where the owners, 555 00:20:31,415 --> 00:20:34,267 contributors just stop responding to it, and a 556 00:20:34,267 --> 00:20:37,065 module it could get orphan because nobody's managing 557 00:20:37,278 --> 00:20:39,359 anymore, and then they also have proposed. So 558 00:20:39,359 --> 00:20:39,859 there's 559 00:20:40,234 --> 00:20:41,450 93 560 00:20:41,984 --> 00:20:45,108 proposed resource modules. If you get 17 proposed 561 00:20:45,164 --> 00:20:45,562 pattern, 562 00:20:46,294 --> 00:20:47,968 1 proposed utility module. 563 00:20:48,526 --> 00:20:50,599 So it does give you kind of a 564 00:20:50,599 --> 00:20:52,592 look to both in terra form and I'm 565 00:20:52,592 --> 00:20:54,665 assuming they have the same thing for bi. 566 00:20:54,919 --> 00:20:58,174 Where they have, what's available orphan proposed. I 567 00:20:58,174 --> 00:20:59,365 will say there's a lot more buy something 568 00:20:59,365 --> 00:21:00,952 than terra form, but it it does give 569 00:21:00,952 --> 00:21:02,699 you a little bit of that map in 570 00:21:02,699 --> 00:21:03,596 terms of 571 00:21:04,144 --> 00:21:05,283 kinda what are they 572 00:21:05,662 --> 00:21:08,639 hoping to have out there what's coming 573 00:21:09,018 --> 00:21:10,935 or at least what would they like to 574 00:21:10,935 --> 00:21:14,063 see built. I don't know can anybody go 575 00:21:14,063 --> 00:21:16,856 out there and propose a new module or 576 00:21:16,856 --> 00:21:19,091 those things that are essentially open be an 577 00:21:19,091 --> 00:21:21,345 issue of we need a module for this, 578 00:21:21,664 --> 00:21:24,625 and Microsoft is reviewing those and saying, 579 00:21:25,105 --> 00:21:27,424 that's a good idea. It's been proposed. Now 580 00:21:27,424 --> 00:21:29,160 we just need somebody to go in and 581 00:21:29,359 --> 00:21:31,596 build it. Do you know how you propose 582 00:21:31,596 --> 00:21:32,416 a new module 583 00:21:32,955 --> 00:21:35,432 out here? How do you propose? I was 584 00:21:35,432 --> 00:21:38,479 just looking... Like here's a So So there's 585 00:21:38,479 --> 00:21:40,707 some governance things that go on here that 586 00:21:40,866 --> 00:21:42,855 I'm aware of. So 1 is... And I 587 00:21:42,855 --> 00:21:44,527 kinda... It was it was in that support 588 00:21:44,527 --> 00:21:47,244 that is modules have to have an owner. 589 00:21:47,959 --> 00:21:50,764 So there has to be somebody who is 590 00:21:51,058 --> 00:21:51,558 accountable, 591 00:21:52,091 --> 00:21:52,591 responsible 592 00:21:53,045 --> 00:21:53,545 for 593 00:21:54,173 --> 00:21:55,626 that module development 594 00:21:56,079 --> 00:21:56,579 and 595 00:21:57,271 --> 00:22:00,472 maintenance. Right? In that world, only 596 00:22:01,084 --> 00:22:02,140 Microsoft F t's 597 00:22:02,689 --> 00:22:03,667 full time employees 598 00:22:04,045 --> 00:22:07,235 can be module owners. Okay. So you can't 599 00:22:07,235 --> 00:22:08,910 have somebody from the community come in and 600 00:22:08,910 --> 00:22:09,707 and say, 601 00:22:10,425 --> 00:22:11,621 I wanna spend a new 1 of these 602 00:22:11,621 --> 00:22:14,026 up. It has to be an F t. 603 00:22:14,265 --> 00:22:16,119 And the reason behind that is 604 00:22:16,814 --> 00:22:17,314 this 605 00:22:17,769 --> 00:22:19,840 needs to have that measure of, like, Sla 606 00:22:19,840 --> 00:22:22,322 and sport ability behind it, So there's an 607 00:22:22,322 --> 00:22:24,707 enforcement mechanism. You need to have the enforcement 608 00:22:24,707 --> 00:22:26,854 mechanism and be able to provide that long 609 00:22:26,854 --> 00:22:29,214 term support that's required by this whole 610 00:22:29,893 --> 00:22:30,951 initiative of 611 00:22:31,328 --> 00:22:34,519 error As verified modules. So you can absolutely, 612 00:22:34,678 --> 00:22:36,592 like, contribute to these things without being a 613 00:22:36,592 --> 00:22:38,108 module owner, but as far as like, being 614 00:22:38,108 --> 00:22:38,746 a module owner, 615 00:22:39,478 --> 00:22:40,614 that has to 616 00:22:40,990 --> 00:22:42,024 be an f t. 617 00:22:42,740 --> 00:22:44,593 So you could make 618 00:22:45,206 --> 00:22:47,593 proposals. I believe it's just on, like, the 619 00:22:47,593 --> 00:22:48,093 main 620 00:22:48,483 --> 00:22:51,577 E github home. I they have, contributing. Yeah. 621 00:22:51,895 --> 00:22:53,482 Sorry. I figured since I had it up 622 00:22:53,482 --> 00:22:55,599 here. I just interrupt. So if you go 623 00:22:56,117 --> 00:22:58,903 into contributing they have a process overview, and 624 00:22:58,903 --> 00:23:01,450 there's a module proposal issue that you can 625 00:23:01,450 --> 00:23:03,837 create. So if you go to Github and 626 00:23:03,837 --> 00:23:06,083 go create a module proposal, Then it gets 627 00:23:06,083 --> 00:23:07,439 created and it has to be approved by 628 00:23:07,439 --> 00:23:09,615 the Av team and it has the whole 629 00:23:09,753 --> 00:23:12,466 flow chart here of someone who has an 630 00:23:12,466 --> 00:23:12,785 idea, 631 00:23:13,279 --> 00:23:16,570 check the module indexes, does it already exist 632 00:23:16,868 --> 00:23:17,368 orphan, 633 00:23:18,065 --> 00:23:20,138 what have you then it gets reviewed, 634 00:23:20,696 --> 00:23:22,553 and based on that review process, 635 00:23:23,264 --> 00:23:25,585 the Av core team will triage it and 636 00:23:25,585 --> 00:23:27,924 then go through and either approve it for 637 00:23:28,065 --> 00:23:30,625 creation or reject it. And then there's the 638 00:23:30,625 --> 00:23:32,839 whole process it goes through if it's been 639 00:23:33,038 --> 00:23:35,105 created for approval. So I did find it. 640 00:23:35,264 --> 00:23:36,933 Well you were starting to talk there that 641 00:23:36,933 --> 00:23:38,148 they have the whole 642 00:23:38,840 --> 00:23:39,340 process 643 00:23:39,794 --> 00:23:40,612 flow chartered 644 00:23:40,986 --> 00:23:41,486 diagram 645 00:23:42,273 --> 00:23:44,178 if you do have an idea for a 646 00:23:44,178 --> 00:23:46,719 new module and what that process looks like. 647 00:23:46,877 --> 00:23:48,942 It is... I will say this is quite 648 00:23:48,942 --> 00:23:49,497 a process. 649 00:23:49,989 --> 00:23:51,903 To get to even that 1 650 00:23:51,903 --> 00:23:55,094 release to your point about not just anybody 651 00:23:55,094 --> 00:23:57,008 can go out and do this, not anybody 652 00:23:57,008 --> 00:23:59,662 can go, just create them and manage them 653 00:24:00,134 --> 00:24:01,728 Microsoft has a well defined process for how 654 00:24:01,728 --> 00:24:04,119 this works. Yeah. It's actually, like, really well 655 00:24:04,119 --> 00:24:05,634 thought out. Like, if you go to this 656 00:24:05,634 --> 00:24:08,048 website and looks through it. Like, there are 657 00:24:08,920 --> 00:24:12,200 design specs. And so there's, like, specifications that 658 00:24:12,200 --> 00:24:14,039 need to be followed for building of new 659 00:24:14,039 --> 00:24:16,533 modules, so that could be things like, for, 660 00:24:16,613 --> 00:24:18,706 like, a terra module, consistency 661 00:24:19,321 --> 00:24:22,052 in cross referencing, other modules, 662 00:24:22,747 --> 00:24:25,866 you know, there's code style guidelines that need 663 00:24:25,866 --> 00:24:26,684 to be followed, 664 00:24:27,059 --> 00:24:29,548 like, how do you do, like, tertiary tertiary 665 00:24:29,605 --> 00:24:31,674 operators, checking for k, like, all those kinds 666 00:24:31,674 --> 00:24:31,992 of things. 667 00:24:32,643 --> 00:24:34,574 So it is all very well 668 00:24:35,107 --> 00:24:37,912 spelled out. It's thought out. There's kinda 669 00:24:38,366 --> 00:24:38,866 clear 670 00:24:39,240 --> 00:24:39,740 guidelines 671 00:24:40,353 --> 00:24:44,113 around these portability thing, who's responsible for what, 672 00:24:44,353 --> 00:24:46,268 who does what? Even all the way down 673 00:24:46,268 --> 00:24:49,002 to, like, Ro charts for 674 00:24:49,474 --> 00:24:52,103 you know, how these things compose and, like, 675 00:24:52,262 --> 00:24:54,334 what are the various teams? So, like, what's 676 00:24:54,334 --> 00:24:57,680 the difference between, like, the module owner and 677 00:24:57,680 --> 00:24:58,716 a module contributor? 678 00:24:59,369 --> 00:25:02,162 How do you product groups like folks like 679 00:25:02,162 --> 00:25:04,636 myself, fit into you that world? 680 00:25:05,195 --> 00:25:06,791 It's all there. It's pretty well. 681 00:25:07,603 --> 00:25:09,510 Pretty well thought out. So, you know, whether 682 00:25:09,510 --> 00:25:12,211 you are a buy up or a terra 683 00:25:12,211 --> 00:25:15,008 form customer or you're doing both that you're 684 00:25:15,008 --> 00:25:17,880 just interested in infrastructure code Azure and how 685 00:25:17,880 --> 00:25:20,671 it compose and and how it's looking. I 686 00:25:20,671 --> 00:25:22,506 think this is an interesting 1 to go 687 00:25:22,506 --> 00:25:24,361 look at. Yeah. And if you are 688 00:25:24,832 --> 00:25:26,126 interested to in getting 689 00:25:26,737 --> 00:25:29,514 involved. I did see on the homepage that 690 00:25:29,514 --> 00:25:32,466 the Av team had its first external community 691 00:25:32,466 --> 00:25:34,215 calls. So I'm assuming this is very similar 692 00:25:34,215 --> 00:25:36,361 to Lake cow, some of the P p 693 00:25:36,361 --> 00:25:38,030 stuff works. I know P p, they have 694 00:25:38,030 --> 00:25:39,382 regular community calls. 695 00:25:39,874 --> 00:25:42,432 So they just had their first community call 696 00:25:42,432 --> 00:25:44,669 back at the end of May of 20 697 00:25:44,669 --> 00:25:45,489 24 698 00:25:45,549 --> 00:25:47,706 on the 20 first, and then they do 699 00:25:47,706 --> 00:25:49,065 have a dedicated page. 700 00:25:49,638 --> 00:25:51,786 To these community calls that we can put 701 00:25:51,786 --> 00:25:53,479 in the show notes. So 702 00:25:54,093 --> 00:25:55,786 they'll go in and 703 00:25:56,733 --> 00:26:00,150 They occur quarterly so that people can get 704 00:26:00,150 --> 00:26:00,809 a chance 705 00:26:01,262 --> 00:26:02,557 to participate, 706 00:26:03,328 --> 00:26:05,728 they switch between time zones each quarter. To 707 00:26:05,728 --> 00:26:08,275 kinda spam those time zones. So open the 708 00:26:08,275 --> 00:26:10,583 floor to attendees to bring up questions, 709 00:26:11,060 --> 00:26:12,174 ideas, stories, 710 00:26:12,731 --> 00:26:13,209 ingenious, 711 00:26:13,766 --> 00:26:14,266 suggestions, 712 00:26:15,134 --> 00:26:17,285 or just your cheerful presence Scott. 713 00:26:18,719 --> 00:26:20,255 So they do all regular 714 00:26:20,631 --> 00:26:21,688 regular calls 715 00:26:22,479 --> 00:26:25,533 starting what May. So if they're quarterly, 716 00:26:26,071 --> 00:26:28,328 there should be another 1 coming sometime 717 00:26:28,786 --> 00:26:29,983 June July, August, 718 00:26:30,382 --> 00:26:32,890 ish I would assume? And these 719 00:26:33,263 --> 00:26:36,044 also have been showing up. So it was 720 00:26:36,044 --> 00:26:37,473 interesting. When we were planning this, I saw 721 00:26:37,473 --> 00:26:40,095 a monthly update from January 20 24 on 722 00:26:40,095 --> 00:26:42,419 the Azure tools blog, And I don't know 723 00:26:42,419 --> 00:26:44,976 that I saw many, like February March, but 724 00:26:44,976 --> 00:26:47,852 they just had another monthly update in May, 725 00:26:48,092 --> 00:26:50,111 where they talked about community calls 726 00:26:50,743 --> 00:26:51,481 there was 727 00:26:52,488 --> 00:26:56,057 some updates on module summaries in terms of 728 00:26:56,057 --> 00:26:58,144 where they are and building modules 729 00:26:58,929 --> 00:27:01,242 which ones are still in development, some more 730 00:27:01,242 --> 00:27:04,753 resources around it for bi, bi, all the 731 00:27:04,753 --> 00:27:07,485 terra forms stuff, So there are blog posts 732 00:27:07,485 --> 00:27:10,125 also starting to show up about the Azure 733 00:27:10,125 --> 00:27:13,965 verified modules on the Azure tools blog under 734 00:27:13,965 --> 00:27:16,159 the tech community site. So 735 00:27:16,538 --> 00:27:17,976 we can post a link to a couple 736 00:27:17,976 --> 00:27:19,355 of those blog posts 737 00:27:19,734 --> 00:27:22,370 as well. If you're interested in finding out 738 00:27:22,370 --> 00:27:25,252 more about community calls getting involved. There's some 739 00:27:25,411 --> 00:27:28,299 Youtube videos out there as well that Microsoft 740 00:27:28,356 --> 00:27:28,856 and 741 00:27:29,391 --> 00:27:32,507 John Sa have published around Azure verified modules 742 00:27:32,507 --> 00:27:33,937 as well that we can link to. Yeah. 743 00:27:34,334 --> 00:27:36,423 It's actually very, like, thoroughly 744 00:27:37,750 --> 00:27:39,234 thoroughly documented. So 745 00:27:39,755 --> 00:27:41,434 I would recommend most folks, like they start 746 00:27:41,434 --> 00:27:44,154 at a k dot mask forward slash av. 747 00:27:44,714 --> 00:27:45,934 That takes you to 748 00:27:46,554 --> 00:27:49,369 that github pages site and from there, you 749 00:27:49,369 --> 00:27:52,190 can spider her out and find all the 750 00:27:52,250 --> 00:27:53,630 information that you could 751 00:27:54,009 --> 00:27:57,212 possibly need. I think. Hopefully it it. And 752 00:27:57,212 --> 00:27:59,116 if you don't find it, just send Scott 753 00:27:59,116 --> 00:28:01,576 an email. Send... Scott don't don't send Scott 754 00:28:01,576 --> 00:28:02,766 email. Scott. Send back email. 755 00:28:03,419 --> 00:28:06,455 Ignore all his emails dot com. No replies, 756 00:28:06,695 --> 00:28:10,451 Scott at no some domains dot com. Yeah. 757 00:28:11,010 --> 00:28:11,250 Anyways, 758 00:28:13,577 --> 00:28:15,728 anyways. Yeah. So so that's kind of a 759 00:28:15,728 --> 00:28:19,550 a quick rapid fire overview of Av or 760 00:28:19,630 --> 00:28:20,665 Azure verified modules. 761 00:28:21,239 --> 00:28:24,195 As we sink further into acronym suit. Not 762 00:28:24,195 --> 00:28:26,273 to be confused with an Azure virtual machine. 763 00:28:27,151 --> 00:28:29,082 Correct. Yeah. Those are reduced V. Those are 764 00:28:29,082 --> 00:28:31,626 just Vms, not Av. Yeah. Go by. And 765 00:28:31,626 --> 00:28:33,772 can they compete Av because you got Av 766 00:28:33,772 --> 00:28:35,919 and Av and yeah, all sorts it's other 767 00:28:35,998 --> 00:28:37,667 Av already. Yes. All, 768 00:28:38,239 --> 00:28:38,874 the acronyms. 769 00:28:39,431 --> 00:28:41,361 Alright. Well, thanks, Scott. Very 770 00:28:41,735 --> 00:28:42,132 interesting, 771 00:28:42,609 --> 00:28:44,277 excited to look at this. 772 00:28:44,913 --> 00:28:47,709 This is 1 area. I have not Del 773 00:28:47,709 --> 00:28:50,411 dove dived. Much into. I've done a little 774 00:28:50,411 --> 00:28:52,159 terra form. I've done a little buy. I 775 00:28:52,159 --> 00:28:53,590 have not done a ton of it. It's 776 00:28:53,590 --> 00:28:55,100 been on my never ending list for a 777 00:28:55,100 --> 00:28:58,137 long time. Because it is interesting. I am 778 00:28:58,137 --> 00:28:58,637 always 779 00:28:59,171 --> 00:29:01,501 like, I'm always blown away by 780 00:29:02,036 --> 00:29:03,649 kinda how popular 781 00:29:04,025 --> 00:29:06,113 terra form is. I think it's easy to 782 00:29:06,113 --> 00:29:07,232 be in the micro... But to be in 783 00:29:07,232 --> 00:29:09,949 the Microsoft ecosystem and think, like, oh, this 784 00:29:09,949 --> 00:29:12,107 is just another thing out there, like, why 785 00:29:12,107 --> 00:29:14,205 aren't you doing arm templates 786 00:29:14,598 --> 00:29:17,304 or bi or whatever it is. The reality 787 00:29:17,304 --> 00:29:19,554 is that there's kind of like this just 788 00:29:19,690 --> 00:29:22,332 gravity to terra form. I mean, it's it's 789 00:29:22,332 --> 00:29:23,549 a massive 790 00:29:24,164 --> 00:29:24,562 ecosystem. 791 00:29:25,359 --> 00:29:27,213 It extends well beyond 792 00:29:27,669 --> 00:29:29,422 Azure. So if you're a multi cloud customer, 793 00:29:29,581 --> 00:29:30,616 like, I totally get it. 794 00:29:31,348 --> 00:29:31,848 And 795 00:29:32,224 --> 00:29:34,533 it's a thing that I think everybody would 796 00:29:34,533 --> 00:29:35,033 be 797 00:29:35,489 --> 00:29:37,400 well served to not be an expert in, 798 00:29:37,559 --> 00:29:38,674 Like, you don't need to an expert in 799 00:29:38,674 --> 00:29:40,765 it, but you do need to know enough 800 00:29:40,765 --> 00:29:41,325 to be dangerous. 801 00:29:41,884 --> 00:29:43,744 If you are on the 802 00:29:44,684 --> 00:29:47,164 infrastructure side of the house or you're doing 803 00:29:47,164 --> 00:29:49,648 devops, doing infrastructure as code, like, all these 804 00:29:49,648 --> 00:29:52,114 kinds of things. Like, if you're doing resource 805 00:29:52,114 --> 00:29:52,614 deployments 806 00:29:52,989 --> 00:29:55,709 through these through this model, terra form is 807 00:29:55,709 --> 00:29:58,891 definitely definitely something that is worth knowing. Like, 808 00:29:59,050 --> 00:30:00,641 it's a massive ecosystem, 809 00:30:01,119 --> 00:30:03,187 there's tons and tons of stuff going on 810 00:30:03,187 --> 00:30:03,267 there. 811 00:30:04,000 --> 00:30:06,480 And you won't be the only person doing 812 00:30:06,480 --> 00:30:08,240 it. Right? Which kinda makes it, like an 813 00:30:08,240 --> 00:30:11,220 easy decision to make. Click. You're not forging 814 00:30:11,440 --> 00:30:13,528 into some new world they're going on a 815 00:30:13,528 --> 00:30:15,352 crazy adventure by saying, like, hey, I think 816 00:30:15,352 --> 00:30:17,255 we should use terra form for this instead 817 00:30:17,255 --> 00:30:17,755 of 818 00:30:18,365 --> 00:30:20,030 instead of an a a straight arm template 819 00:30:20,030 --> 00:30:22,058 or a bi template or 820 00:30:22,596 --> 00:30:23,974 en illumination and 821 00:30:24,352 --> 00:30:26,667 a shell script or something like that. Like, 822 00:30:26,906 --> 00:30:29,301 it's a big ecosystem. Yeah. It also works 823 00:30:29,301 --> 00:30:29,780 really well. 824 00:30:30,591 --> 00:30:32,579 1 thing... Yeah. And 1 thing that caught 825 00:30:32,579 --> 00:30:34,964 my I too on this recently, I must 826 00:30:34,964 --> 00:30:37,055 not have been an Azure verified module 827 00:30:37,429 --> 00:30:37,929 module. 828 00:30:38,637 --> 00:30:41,023 But someone did come out with a terra 829 00:30:41,023 --> 00:30:43,569 4 module for Enter recently too. It must 830 00:30:43,569 --> 00:30:44,921 be 1 of the community modules. 831 00:30:45,414 --> 00:30:47,009 And Yeah. Again I I don't know how 832 00:30:47,009 --> 00:30:49,002 it's gonna go at bought brought my car 833 00:30:49,002 --> 00:30:51,554 Microsoft. Yeah. Yeah. It's it's m 3 65 834 00:30:51,554 --> 00:30:54,048 versus Azure. Like, I would say, like, this 835 00:30:54,186 --> 00:30:55,737 initiative is definitely 836 00:30:56,193 --> 00:31:00,175 Azure verified modules. It's not Microsoft verified modules 837 00:31:00,175 --> 00:31:03,042 or Microsoft cloud verified modules. It's it's Azure. 838 00:31:03,933 --> 00:31:04,433 So 839 00:31:04,810 --> 00:31:07,281 ent continues to sit in that weird space. 840 00:31:07,441 --> 00:31:09,774 Right? It's kind of a a gap bridge 841 00:31:10,071 --> 00:31:10,571 between 842 00:31:11,107 --> 00:31:11,586 Microsoft cloud. 843 00:31:12,159 --> 00:31:15,186 And then Azure specifics. So I imagine over 844 00:31:15,186 --> 00:31:17,758 time, like, even if there's not an official 845 00:31:17,975 --> 00:31:19,330 inter module over here, like I said, like 846 00:31:19,330 --> 00:31:21,162 back to, like, the patterns and utility modules, 847 00:31:21,321 --> 00:31:23,413 things like that. Yeah. I I bet there 848 00:31:23,413 --> 00:31:26,130 are helper, helper things that come out. And 849 00:31:26,130 --> 00:31:27,968 some of those helpers already exist for buy. 850 00:31:28,207 --> 00:31:30,445 So for, like, buy, there's pattern modules today. 851 00:31:31,018 --> 00:31:33,963 For dealing with things like policy assignments, role 852 00:31:33,963 --> 00:31:36,749 assignments. So, like, being able to affect policy 853 00:31:36,749 --> 00:31:38,022 changes on your resources, 854 00:31:38,674 --> 00:31:40,588 being able to affect, like, our back assignments, 855 00:31:40,748 --> 00:31:42,742 things like that, Though those do exist. Yeah. 856 00:31:42,902 --> 00:31:43,561 Here's an 857 00:31:43,938 --> 00:31:46,650 authorization role assignment in terra form. So there's 858 00:31:46,650 --> 00:31:48,245 some of those very interesting. 859 00:31:48,739 --> 00:31:50,972 Stuff to play with. More stuff. Add it 860 00:31:50,972 --> 00:31:52,726 to the list more stuff stuff. You never 861 00:31:52,726 --> 00:31:54,002 had enough. Never. 862 00:31:54,879 --> 00:31:56,235 I knew I knew you were looking for 863 00:31:56,235 --> 00:31:58,955 more. Alright. Well, thanks. Thanks for adding more 864 00:31:58,955 --> 00:32:01,416 to my list. And with that, we should 865 00:32:01,416 --> 00:32:03,003 probably wrap up because I just got back 866 00:32:03,003 --> 00:32:05,359 from Vacation, and I also have a list 867 00:32:05,479 --> 00:32:08,373 from coming back from vacation. Separate from my 868 00:32:08,512 --> 00:32:10,028 list of stuff to play with from Scott. 869 00:32:10,507 --> 00:32:12,023 Alright. Well, well, once you get back to 870 00:32:12,023 --> 00:32:13,401 your other list, and then 871 00:32:13,713 --> 00:32:15,805 we'll get back to our regularly scheduled programming 872 00:32:15,862 --> 00:32:18,091 here. And now that vacations and things are 873 00:32:18,091 --> 00:32:20,399 starting to wrap up from June, July. Just 874 00:32:20,399 --> 00:32:21,846 in time for 1 of to probably go 875 00:32:21,846 --> 00:32:24,233 on vacation again. Probably you. I'm done with 876 00:32:24,233 --> 00:32:24,892 the vacation. 877 00:32:25,506 --> 00:32:25,904 That was... 878 00:32:26,540 --> 00:32:28,211 I got all my vacations done in June. 879 00:32:28,450 --> 00:32:30,929 So alright. We'll enjoy Scott. Enjoy the rest 880 00:32:30,929 --> 00:32:32,833 of you today, and we will talk to 881 00:32:32,833 --> 00:32:34,657 you again soon. Sounds good. Thanks, Ben. 882 00:32:37,037 --> 00:32:38,385 If you enjoyed the podcast, 883 00:32:38,798 --> 00:32:40,546 Go leave us a 5 star rating in 884 00:32:40,546 --> 00:32:42,453 itunes. It helps to get the word out 885 00:32:42,453 --> 00:32:44,598 so more It pros can learn about Office 886 00:32:44,598 --> 00:32:45,711 3 65 in Azure. 887 00:32:46,679 --> 00:32:48,186 If you have any questions you want us 888 00:32:48,186 --> 00:32:50,409 to address on the show or feedback about 889 00:32:50,409 --> 00:32:52,711 the show, feel free to reach out via 890 00:32:52,711 --> 00:32:54,960 our website Twitter, or Facebook. 891 00:32:55,359 --> 00:32:57,200 Thanks again for listening and have a great 892 00:32:57,200 --> 00:32:57,359 day.

Digital Dispatch Podcast Podcast Artwork Image

Microsoft Cloud IT Pro Podcast

Ben Stegink, Scott Hoag

On the MS Cloud IT Pro Podcast, Scott and Ben discuss the Microsoft Cloud with a focus on IT Pros. They'll discuss the latest in Microsoft 365 and Office 365 News, Azure news and talk about their experiences with managing the Microsoft Cloud as well as interview industry experts on various cloud technology. They'll cover things such as SharePoint, Exchange, Microsoft Teams, PowerShell, Azure, Azure AD, Security, Networking, Storage, and the many other technologies and products that have made their way into the Microsoft 365 suite and Azure. To stay up-to-date on the latest in Microsoft Cloud news and gain some valuable knowledge as you deploy it within your own organization, make sure to tune in every week! Find out more at msclouditpropodcast.com.

Contact Show