Welcome to episode 339 of the Microsoft Cloud IT Pro Podcast. Recorded live on June 16th, 2023. This is a show about Microsoft 365 and Azure from the perspective of it pros and end users where we discuss the topic or recent news and how it relates to you. This week, the internet is breaking again, Reddit is on fire. Google Domains is being sold and AWS broke fast food. However, in Microsoft News, Azure ad Graph is still retiring with a modified timeline.
There is a new Microsoft Intune, PowerShell script library in collaborative notes and Microsoft Teams is in public preview. So let's get on with the show. Look at that. We kind of just that easy sort of half know what we're doing every once in a while maybe ish, kind. Of sort of, you know, who doesn't know what they're doing. Am I supposed to be politically corrected or am I supposed to guess or
am I supposed to just pull something out of the top of my head? I. Mean, any of the above would be valid threat ceo, but I would posit . Yeah, Steve Huffman is having a very strange week. The Reddit thing's disappointing to me. Like I'm a big fan of some of the third party apps, especially one of the bigger ones that is announced. It is shutting down on June 30th, which is Apollo, which is an iOS Reddit application that was just
nicely designed. It worked well, never really crashed, had awesome little things for like media controls, like, you know, like scrub your finger across a video or an animated gif and it would just scrub to the location and uh, it, it was just like a really nice application. Had great multi Reddit management sorts of things. Anyway, Reddit has gone down the path where, and, and they've been on this path for a while where they, they want to I P o at some point, they're mainly funded by investors.
They're not a profitable company. So it makes it hard to I p o and go to a public offering. Yep. In the United States if you are not a profitable company. So now it's kind of like profits by any measure. And for Reddit that means starting to charge for access to their a p I, which I don't have any problem with. I don't think any reasonable person out there does have an issue with that.
Right? Like if you're consuming from on top of something, there's gotta be a logical limit to it and there has to be some skin in the game for everybody, right? Right. Like if I'm an infrastructure provider and I'm providing you data as a consumer of said data, if I'm not able to advertise to you or do other things, like I'm gonna have to charge you some money just to keep the lights on, if anything, break even and, and maybe have some margin on top of it.
And you know, Reddit's in the same boat. So they have an a p I that a p I was written in the way back when, hasn't been meaningfully improved from everything I know about it in years now. Like it's had additive things put on top of it, but they kind of haven't fixed the core of it.
And it was made for things like bots on Reddit and, and for the Reddit app itself, like their official app for Android and iOS, it was never necessarily intended for third party consumers, especially at the scale they grew to like the these third party apps and the number of requests they made. So okay, you have a third party app ecosystem, you're not charging for your api. You need to flip to a model where you charge for set api.
Unfortunately the amount of money that Reddit decided to charge for that API and you know, the, the pricing per API request or per bucket of a thousand requests, things like that ended up being astronomically high and kicked a bunch of apps basically off the platform. It made them feel like made the made the developers, those applications. Like Kristen Selig who does, uh, Apollo. Yeah, Apollo, the folks who do Reddit is fun sync is going away there there,
there's a couple other ones that are out there. They all basically said like no, we can't do this and we can't do it on 30 days notice. Which is basically what Reddit gave them. You know, some applications like Apollo make billions of requests a month. I know billions with a B sounds like a big number. It's really not too big a number considering the number of users Reddit has and likely the user base of something like Apollo and the actions you take, right?
Like you think about like loading a new page in a client that has all the comments on a Reddit post, well there's an API to retrieve comments, there's an API to upvote, to downvote, to bookmark, to to do all these things. So those are all individual API calls and and they add up and the way Reddit was thinking about pricing didn't align with the expectations or
what was manageable for those third party providers. So I think Apollo, like the quoted number from the developer was they were gonna go from $0 for Reddit a p I spend to something on the order of 20 million a year. Yeah. Which is nuts .
Yeah, that's huge. And I saw, again, I'm with you charged for the api, it obviously cost them hardware and I think I saw from the creator of Apollo that people have tried to do some rust estimates and figure each a p I call is maybe costing Reddit itself on the magnitude of like 12 cents per call. And they were marking it up to like two 50. It was like a massive increase from what the estimated spend actually was. it's on the order of like, so every user's gonna be different.
Like uh right. You know, I know for like the way I use Reddit, I would be on Reddit in the morning and, and maybe at night you, you know, as I wanted to reduce at the end of the day, things like that, a moderator could be on their way more than I am and they're doing more than reading. Like they're clicking around, they're firing off more a p i actions, things like that.
So it's tough to break it down to like a user or really like a persona, but you know, I guess broadly like per user per day a p i cost or per user per month a p i cost. So the way Reddit was thinking about that was, you know, their app, which is pretty crappy these days. Like they actually bought a third party app years ago and then they ruined it. Kinda like Twitter did , right? Like when, when, when they took over Tweety and, and all that stuff. So it's what corporations do.
Like they take good things and they ruin them and they make them ugly and and they don't make it so people don't want to use them. But uh, even for their own stuff they're calling out these third party apps and saying, well, like these third party apps aren't performant. So I don't think that's the case. Like from all accounts, these third party apps have reached out to Reddit many times and said like, Hey, your a p I isn't good in this way.
Can you improve it or can you tell us how to make this better? Like, we don't wanna be throttled by you. Cuz Reddit had throttling mechanisms and, and other things in place the whole time. So yeah, I, I think some of the third party developers estimated, you know, it's basically like 24 cents less than a dollar per user per month in a, in a p i costs. And then Reddit was kind of coming back with something that really aligned to
about two 50 a month per user. So if you think about having an app like Apollo, which charges a subscription, great, so now you have to charge not just two 50 a month cuz you gotta cover your API costs, right? But you also have to cover your development costs plus any margin or things that
you need to live. So you go all of a sudden from really not even like a, you know, a minimal subscription amount to a month but you've probably gotta overcharge by a bunch cuz you're gonna have that mix of heavy users and lighter users and things like that. Like it probably wasn't too insane to say like, oh you're gonna have to charge $10 a month for this Reddit app and that starts to become unsustainable pretty quickly in like a whole bunch of
dimensions. So those app developers, they just spun out, there's still a bunch of blackouts on Reddit, a bunch of subreddits have locked and aren't allowing comments. Some have unlocked and made themselves readable and they're not aligned comments. Reddit this point is coming back and saying, Hey, if you're a community that's shut down, we are going to potentially flag you as in violation of the terms of service and we'll find new moderators for your subreddits.
Which I think is like a crazy step for them to take. Like, I don't know, they really lost sight that, you know, much like Twitter, like they were providing a a free service. Like they, they they should have like maybe thought about other ways to monetize that or make it leaner. And really what drives Reddit is community and the community does all that stuff for free. There's no such thing as a paid moderator on Reddit.
So if you go into like the funny subreddit, like our funny like the moderators for our funny who put up with all the crap go in there every day, they moderate all the spam, they ban people, they allow people and like all those things like they do that for free and you can't run a forum for that size for free in many places. But Reddit was able to do it right cuz you have users who are passionate about
the community. Yep. And now they're going to lose all of that. Like uh, I saw today some articles on moderators starting to leave and other things. So it will be a shame if Reddit goes away. Much like I was sad when Twitter goes away, but once again I have way more time in my day cuz I'm not spending like 30 minutes to an hour in the morning just browsing Reddit and seeing what I
missed or trying to see what's going on. It. Was interesting, I was watching one uh, the Linus tech tip videos too where they were talking about Reddit and I even think about it from the podcast, right? Like we have stuff on Discord, we've done stuff on Twitter, Mastodon, we've tried stuff on Reddit. Never really gotten anything there. But they even talked about how all of these ups recently like with Twitter, with Reddit, with some of those how stable it's been for a while.
But you think back like and they were bringing up all these different, all the different tech that we used like think high school, college, I remember what was it, Zenga that was like the blogging and you had MySpace and you had all these different online community services that we've gone through cycles like this where you get certain platforms that get really big really fast, stay very relevant for a few years and then just kind of
fade away. And recently, like you look at the Twitter and Facebook and Reddit, some of those have been around for so long that I think people have forgotten kind of the cycle that maybe you and I went through 20 ish years ago when we were in high school and college. And it was just interesting to kind of see how maybe some of this is starting to repeat itself with some of these services.
. Yeah. The thing that probably hurts the most there is even if you are not a consumer of said service, like you might not know what Reddit is or you might not be on it day-to-day. I can almost guarantee you if you've ever gone out and searched for something that's maybe a little more esoteric, right? Like you could be a Jeep owner and you're really into CJ's from the 1970s, there's a forum for those Jeep owners from exactly that year that can tell you like, oh yeah, you need this part.
Or right here's where you can get that thing to be successful. You're a hamma radio operator and you and you need to go swap parts with somebody. Somebody for this dying art like can pretty much guarantee you like there's a forum for that on Reddit. And a lot of their traffic was driven inorganically through things like Google searches.
And now like if you go to Google this week and you start searching for things where you normally would've ended up on Reddit for your answer, you're not really able to end up on Reddit because the SEO rankings have fallen cuz everything's been shut down. Or if you go there, it's probably not gonna be what you thought it was gonna be. Like you could land in a cash Google link and all of a sudden you're in this lockdown Reddit that you can't actually see anything in. Yeah.
So it'll be interesting, we'll keep an eye on it with a podcast like what's kind of next for some of these things. There's a bunch of different things that are trying to spin up. But all of that aside, Scott, I don't think you were gonna say the Reddit CEO didn't know what they were doing when you started off that question like 10 minutes ago. I wasn't.
Gonna go down that path, but it was a good, good one to go down doing so else we should keep going down like stupid companies doing stupid things or I guess companies doing things that's really long. List Scott. We're gonna be here for. A long time. Don't make any sense. our friends at Google, you know there's kind of this trope out there that for every one service, like a will turns on they shut down, you know, like 10 more of them. Yep.
And it, I, I'm really surprised that some things like Gmail haven't shut down over time and, and Google's kept them around. I'm glad they do cause like I'm a a prolific Gmail user, but one of the things that did happen is Google domains, I had no idea, didn't see this one coming is shutting down and they're selling all their
assets over to Squarespace. So I, I think this is interesting for several reasons, one of which is like Google Domains just a few weeks ago, like within the past couple months they announced a bunch of new TLDs that they were gonna allow like zip and things like that and, and some of the kind of ruckus that came up around that. And now they're just like, they're done. They're throwing in the towel.
So if you're a Google apps customer, anything like that, like you had your domain registered through Google through those offerings, like congrats, you are now a Squarespace customer. I think that's interesting. Like I, I typically don't think of Squarespace as a domain registrar but they just picked up a probably what's a pretty decently sized customer base.
Like I know quite a few people personally who have bought domains on Google like, and lots of them did it because of things like those TLDs that they had tho those top level domains that were a little bit more unique and that you could get into. I don't know, it should be interesting to watch and see how Squarespace handles it. Squarespace is an awesome company. Like everybody's, if anybody's ever done like a CMS with something with them or anything like
that, like they're really good at it. But uh, Google too is getting out of a game. Yeah. This one will be interesting. I did find an article here that 10 million, it's not, I don't, I'm trying to think like what would I have expected 10 million customer domains hosted on the service. So not necessarily 10 million customers. I mean personally when I go I own like 30 domains. I'm possibly was gonna say probably.
A little excessive but I mean 10 million customer domains could legitimately only be about a million customers. Maybe 5 million. That doesn't to me with the size of Google, that doesn't seem like a huge number cuz you still are competing against people like GoDaddy, right? GoDaddy is still huge. I think as a network services I've actually flipped all of mine domain registrations.
I buy all of mine and have all of mine now through CloudFlare cuz they're actually pretty cheap and I can't stand GoDaddy but it doesn't, I mean to me again 10 million customer domains does not sound like it was actually that sizeable of a business unit for them. no, sometimes I don't think you wanna be in businesses because they're big. Sometimes you wanna be in businesses because they make sense. So if you think about all the other things that Google does, selling ads,
web hosting, like they do you those kinds of things, right? Like the G suite, Google Workspaces, G Suite, like all those kinds of things, right? Like you want it to be really easy for awe G Suite customer to come in and pick up a new custom domain for their email. And it was unique, right? Like I think about the way Microsoft does it with the GoDaddy relationship. Like that's horrible. Like you can still buy buy domains from Microsoft. Did you know you can buy domains from Microsoft? You.
Can everybody I run into Yeah but it like the path you're let down, like you end up in a weird GoDaddy thing with a, with with a GoDaddy. It's straight through Microsoft. So not Office 365. You can go into Azure and I think oh if you go to domain names in Azure, nope it's not domain names. See this is why it's weird. There is a place in Azure where you can purchase domains in Microsoft. Like you actually buy 'em from Microsoft and they end up on your Microsoft bill. It's not a GoDaddy one.
In Azure. Yes you've got like Azure, dns, things like that. Like yeah like there are registrar services within Azure. I think it's just a weird place, right? Like there's now gonna be friction there for their customers where there wasn't for friction before. Like if they were willing to maintain it, why not do it right and keep the business. Yeah. And have it going. Yeah CloudFlare is really good. Like you said, like you've got some folks in the chat saying CloudFlare is good,
I use name cheap for a bunch of stuff. Hovers good. A lot of it depends sometimes on like the TLDs you want and just how, how, how easy you want some of that stuff to uh, right to be done. I did see one comment from some other people I worked with that said Google's in the business of starting services, not maintaining services and improving services. So they started it and got bored with it and just sell it. Cuz nobody wants to maintain, they wanna come up with something new.
Ver very much right? It's a, i I get it like it's how careers are made. You know, nobody keeps getting promoted over running the domain domain service for 10 years. For for 10. Yeah. You wanna move on and do and do the next thing. I I think that was like my comment earlier like you know for every one thing they spin up there's like 10 things that shut down and at some point like that perception starts to stick, right? Like perception becomes reality. So hopefully they can get better at it. Yes.
But now we've ranted about two things shutting down and all that. We should probably talk about something like. Relevant. Okay so I have no I'm well it's relevant but something else is shutting down just not on the timeline that maybe we had initially thought, Do you feel overwhelmed by trying to manage your Office 365 environment? Are you facing unexpected issues that disrupt your company's productivity?
Intelligent is here to help much like you take your car to the mechanic that has specialized knowledge on how to best keep your car running Intelligent helps you with your Microsoft cloud environment because that's their expertise. Intelligent keeps up with the latest updates in the Microsoft cloud to help keep your business running smoothly and ahead of the curve.
Whether you are a small organization with just a few users up to an organization of several thousand employees they want to partner with you to implement and administer your Microsoft cloud technology, visit them at intelligent.com/podcast. That's I N T E L L I G I N k.com/podcast for more information or to schedule a 30 minute call to get started with them today. Remember intelligent focuses on the Microsoft cloud so you can focus on your
business. So Azure ad graph Scott, we have talked about this, the Azure ad graph, PowerShell Azure ad graph was going to shut down on June 30th, 2023. So like two weeks from now and I think this was just announced yesterday, yeah June 15th. This has now been pushed back. So instead of shutting down on June 30th, 2023, we now have until a couple different timelines, licensing assignments, PowerShell commandlets for ad user licenses, UL user licenses, some of that type of stuff.
All of the migration to the new PowerShell module is September 30 of this year. So we get an extra June, July, September three months out of that. And then the legacy PowerShell modules, MS online, Azure ad, Azure ad preview, we now have until March 30th, 2024. So we got another nine months out of those.
It kinda sounds like there was just not quite, maybe they hadn't quite gotten to the point they wanted to in terms of feature parody and having everything there and getting people moved over so we get a little more time before all these older PowerShell modules. . Go away. It amazes me how painful it is in the cloud to move folks along to the next thing from the outside. As somebody who kept up with the news, I always looked at these timelines and I'm like three years is like forever
should, right? Should customers be able to move faster than that? And now that I'm on the inside , see how it goes, I'm like man, like I get it. Like I understand like why it's three years cuz those three years are a war of attrition the entire time trying to socialize these things with folks here. Like I think I lose sight of it sometimes.
Like for all the things that we go out and we pay attention to, uh, Azure updates, RSS feeds, blah blah blah, like all these different things like nobody else does that like no customers do it. Like even if you tell 'em about it, like the person who heard it might not work at that company like two months later. So the whole thing is lost to tribal knowledge anyway and it's really kind of crazy to watch some of these things go and ultimately like the line in the
sand is like you break customers, right? And nobody wants to do that. So you kind of bend over backwards based on your telemetry, right? And how things are going and you and you try and turn it around. So I'd imagine this is one of those scenarios, right? Like somebody's looking at the usage and saying like, ah crap, we can't actually go. We can't do this yet.
Do you think though part of this is Microsoft has shot themselves in the foot from the standpoint of I feel like this happens with every single deprecation that we're gonna deprecate on this time, but we were just kidding, we're gonna give you longer. So to some extent customers have gotten in the habit of, well Microsoft maybe really doesn't mean the date they said because they always extend it. It's like the whole boy who cried wolf thing of we're gonna deprecate on this
date but not really because you see them do this, right? You see 'em, they announce a date and then it gets close and they push it off and they push it off and sometimes they push it off two or three times and then when it still finally gets to that date, everybody starts screaming about why isn't this getting pushed out? You're actually deprecating it now we need more time .
And it's like they gave you more time three times maybe if they started or maybe I'm just getting tired of my kid's not listening to me in the same way. But like if they actually stuck to their timeline, people are screaming and arguing and complaining no matter what, maybe if they just stick to their timeline, people would start to get that there are no extensions.
So get your act together and get it done at on the timeline that Microsoft said or it's gonna break and we don't need to keep having all these crazy six month or nine months extensions because frankly I'll forget about it now. Like I was actually working with a bunch of clients to get this moved over. Yes I still need to do that but now in my head I'm like I've got another three months or nine months or six months and then it'll still come down to crunch time. I don't know.
Yeah, if you are passionate about it and you think it's something you can drive, I'm pretty sure there's a role Microsoft where you know somebody's ready to get that rocking. I think I've been pretty lucky. Like I, I don't know, I don't, I don't know that I have the right mindset to walk in and kind of understand all the constraints on something like this. Like I've only had to depre uh, deprecate things like SDKs which I think are a little bit easier.
Particularly cuz like most of our SDKs are developed in the open, so they're all on GitHub, you know, we can communicate that in a more open way I think. Yeah. And then customers have the opportunity to carry it forward on their own. Like I had to deprecate our P H P S D K for storage uh, a couple months ago. I think that was something I did like late last year And you know, like it wasn't a fun experience to not delight customers cuz like, oh this thing is going away.
But we were able to give customers a clear signal like, hey, this is going away, it's going away on this timeline. We are definitive in that. Like we're not gonna extend it. It's done. Like here's what you can do today and you know, we've already had portions of our community like pick up what was our P P s dk, go ahead and fork it and start to work on it at a different place and uh, like a relatively rapid manner and that's totally different than something like
this, right? Like shutting down a whole a p I surface and just, you know, effectively turning it off, right? Like, like that a p I endpoint is gonna go away. So it'll be interesting to see where some of that goes. I did see one from the Intune folks. So we're talking about Intune on here quite a bit. Like you tend to bring it up every now and then. Yep. So the Intune folks have gone ahead and spun up some new repositories with some PowerShell examples.
So they're getting away from kind of the A O L thing and moving over to graph as well. So there used to be some GI GitHub repos out there on from the Intune team in the Microsoft org and now there's just kind of this one catchall web uh, webpage. So if you go to aka ms slash Intune scripts that'll take you to webpage. It's got like three simple buttons on it and you can just say like, okay, I'm interested in the graph PowerShell Intune samples.
They actually have bash samples as well, which is nice. So if you're like a Linux Mac customer that's all out there and ready to go. And then the archive, much like the SDK that I was talking about earlier that I deprecated, like it's not going away, it is on GitHub, it'll remain there, it just won't have any new commits to it and you know, it'll get a message that says it's deprecated and there's newer stuff over here kind of thing. Very cool. I will go dig through this.
I'm sure there's some fun scripts in here I can play with. I. Think it's always interesting to see like how the folks who make the service build these things. . Yeah. Oh I 100%. Maybe I'll have to go play with these and we can like do an episode on our favorite Intune PowerShell script samples or I can do an episode on my favorites or just walking through some of what's in here cuz they do have quite a few scripts in here just kind of diving through it.
Application sync, device config stuff, enrollment scripts. Yeah. Interesting. So I have another one. Scott, do we have time for one more news announcement? Yeah. For you. We've got all the time in the world for. Me. Okay. Collaborative notes in Microsoft Teams meetings are now in public preview. This one is interesting. We could maybe do a longer episode as this comes out. But collaborative notes in Microsoft Teams meetings and now
our in public preview. Essentially what this means, and we actually have it nars, is that if you go click on the whole, go into a meeting and click on notes instead of using the old wiki thing in teams that it used to, this now uses a loop component in the Microsoft
teams meetings to do collaborative notes. So you can go add your, you can go add task lists, you can go add notes, you can just start typing bullet lists, comments, dividers, tag people, progress trackers, all that good stuff that you would be able to do in Loop you can now do in these collaborative notes. They had to come up with something because a few months back they announced Wikis and teams were going away, but they were not getting replaced with Loop.
They were getting replaced with OneNote. Mm-hmm . So this puts people in a really weird spot. I personally, I don't like this now my meeting notes for all of my meetings are going to be loop components, but by default now my notes tab in a team where maybe all these said meetings are occurring are gonna be in OneNote. So OneNote's the default, no place for teams yet. Loop is the default stuff for notes related to a meeting. The one saving Grace ish I would say they got with all of this.
And this also interests me for more than just the collaborative notes piece is that coming this fall, the integration of loop components with OneNote will enable you to seamlessly incorporate your collaborative meeting notes into your OneNote notebook. So this means loop components next three to six months are gonna start showing up in OneNote, which I really like.
I have kind of shifted back towards OneNote for a lot of my work notes, but I don't use task lists in OneNote because they sync with nothing. But now if I can go add loop components, not just from meeting notes, but if they allow me to add a task list, loop component, all of that in OneNote, I can do task lists and a OneNote component sync 'em up with to do or planner
and some of that. So while I, in a way I would've liked to see OneNote kind of completely replaced with Loop if it could achieve that, I think this is also a good option of being able to take some of these loop components and put 'em in OneNote. Frankly, I'm surprised it's taking until this fall to do it. I would've expected it a little sooner with how much they integrated components everywhere else. But it is coming and I mean I don't think it's
a half bad solution. It just, or it's kind of the only solution they, I had given the corner they put themselves in with two different note solutions both used within teams. , couple of things to think about on this one. So like you talked about like the disjointed nature of OneNote versus Loop still exists. I think the other thing that's very real is the permission aspect of loop components again strikes here. Yeah.
So I can't be the only person where we have a teams chat in a meeting and then I might try and bring somebody else into that chat later or like, Hey, I need to like share the results of this kind of thing. Still extremely nebulous, extremely hard to do with loop components. And I think OneNote like until they solve this whole permission thing with loop components, OneNote's gonna be a mess too, right?
Like what's gonna happen when you embed a loop component that you and I have access to and then, you know, we've got uh, Joey in the chat with us and we wanna share it with Joey and, and Joey can't get in then like that would be very sad and we, we don't want that to happen. And then the last part is they really didn't talk about like roadmap and what's
next . And I think that's a little weird cuz like, one of the areas I think they, they fell down was they talk about like supported clients and platforms. This doesn't work on iOS or Android, so you cut out all your mobile users right off the bat. And I find myself on like teams on mobile more and more and more these days just as like, I don't wanna be locked into like these same four walls all the time.
Like I know if I have a meeting where, you know, I'm not the scribe or the heavy note taker, like I'm gonna be off on my phone and then when folks are working in those notes, I don't get to see them. . Yes. You know where else this falls apart that frankly I'm surprised also isn't fixed yet is guests, external guest users that you invite to teams and you want to do the whole collaborative meeting notes things loop components or Loop in Loop in general does not work with guest users.
Well I've been in meetings too where like now my meeting notes thing is just completely gone because I'm a guest. Yes. And an external tenant or Yeah, it's like it all just breaks as soon as you introduce those guest users now or external users. All right. So Loop is still broken. We talked about that. Reddit's broken Google Domains is broken. The, the whole internet's just breaking down again and we'll come back in like six months and talk about how it's still burning.
It's because AWS East one went down and that breaks the whole internet. Scott. , uh, it does. I don't know if I can share it in the blog post, but there is this great little picture. I think I sent it to you the other day. Yes. In, in one of the chats we have. I'll, I'll put it in the chat. Over year. We we'll absolutely put, we can put that in the show notes dis I will put that in the show notes if you do not. All right.
. I see how it is. But anyway, yeah, , AWS US East one went down the other day and so many services take a dependency on, uh, AWS is a hyperscaler, uh, especially here in the US that particularly when that region goes down, like bad things happen. . Yes. I, so I won't lie. When that happened, I quick did some Googling to see if it went down for the same reason Azure went down like a few days before, if some nefarious person was trying to increase the amount of traffic to an
endpoint. Although it was not confirmed, it was nefarious. The official stuff I saw from Microsoft was they had an unusual spike in traffic. I think. . Take that as you will, but that is why Yes. I I don't, we've said it before, I don't envy these cloud providers. They all have their bad days and both of them have had bad days in the last couple weeks. Yeah. At least Microsoft was only a portal going down. It wasn't like the underlying like management plane or anything like that.
Right. But, uh, so, so AWS was a little, little worse. My kids couldn't order the McDonald's that day, so they were kinda sad. Oh, was Mick broken still down? Remember that episode to check his screen? Yeah, I I oh man. It's an interesting thing, right? Like, like AWS and, and all these hyperscalers, like they used to be used by I think more like internet first kind of companies cloud native, right? Like Spotify stops working.
It could be because G C P broke and, and something happened over there. But more and more like user facing consumer things in the appification of the world, like the us like McDonald's, taco Bell, burger King, like all that stuff. Like they're all cloud driven and when the cloud goes down, they have a bad day too. Yes, absolutely. But with that, Scott, we should probably wrap up for the day. I don't know, I think I might have another meeting. Do I have another meeting?
I do have another meeting. I have another meeting. Should figure that out. Five minutes. So we should probably wrap up so I can go to my other meeting. You can either go keep working or probably keep working. We will say that I'm gonna keep working. I'm gonna keep working. Okay. Yep. Sounds good. Well, enjoy Scott, thank you for the episode about everything being broken and we will talk to you next week, I think for at least another week or two.
We're back to our normal recording on Fridays until one of us decides to leave on vacation again. Sounds good. All right. It's been And enjoy your Father's Day. You too. All right, I will. And everybody that's listening, I hope you had a good Father's Day cuz this comes out after it. . All right, tight to later Scott. Bye Ben. If you enjoyed the podcast, go leave us a five star rating in iTunes. It helps to get the word out so more it pros can learn about Office 365 and Azure.
If you have any questions you want us to address on the show or feedback about the show, feel free to reach out via our website, Twitter, or Facebook. Thanks again for listening and have a great day.