 Sarah asks, are there any considerations with using numbers and special characters in team names, SharePoint site names, and associated connected notebook names? Any gotchas? Yes. Some are reserved characters? I think a lot of people don't think about their naming conventions, and it's really important that you think about the naming conventions. You know, using underscores or dashes, fine. But when you start to get into special characters, it's so much harder to find things. And then people will recreate a team or ship on because I can't find some things. Then you end up with some duplication going on, keeping it really simple. And in terms of characters, it's going to be really important. Plus less than 30 character length. You know, when it comes to a team name and channels, we want to try and limit it down. So when those naming conventions, it's always easier if you go, this is a project type channel or it's an organizational. My ORG underscore. So people can run down and they really only see the first 11 characters as well, 11 to 12 characters in a team. So you need to be really succinct so people can find it as they're running their eye down. And I know that we can use emojis and get those, you know, iconography in there. I wouldn't do it personally on a team. A channel? Great. Because it really will help you on a channel. We have a 76% better recall if we've got a picture and it will help people with reading, especially those with accessibility issues and dyslexia. So having a picture at the front of a channel, great. You can just do your windows period or full stop key, whatever you prefer to call it, and bring those characters emojis up to do those naming. But I wouldn't do it with SharePoint science. I wouldn't do it with creating a team. All those things come into play. Heather, thoughts? Oh, yes, I've got lots of thoughts. Let's discuss it. We figured some stuff out in the last several months that, let's say that your team name is like two, zero, period, zero, zero. And then two, zero, period, zero, zero. There's also a name in there. No, there's a name in there. So there might be like strategy or something like that. There's a name for each of these functional teams, right? Whatever it might be. What we found, though, is that works fine for the team. That works fine for the associated SharePoint site name, but for the one note notebook. Oh, yes. When you're looking at it in like the recent, so if you're on the Microsoft 365 homepage and you're looking at your recent files, if one of those notebooks is listed there, that notebook name would just be 20, because that period ends up being like a hard stop and it doesn't read the rest of it. So then if you have a lot of these teams like that, then you end up with notebooks that are 20, 21, 22, and that doesn't contextually tell you what it is. Then what you have to do is you have to go into the SharePoint site, into the site assets where that notebook lives and change that to something like an underscore and then the full name will come through. So that was one of the challenges. The other challenge we found with the one note notebooks was if you kept the period or periods in the name and you needed to change that name later on, it wouldn't let you use the period anymore. If you tried to go in and change it in SharePoint. Only in that new. Only in that new, somehow. Yeah. Yeah, so some... Yeah, because it doesn't like it in its naming convention because what it's doing is it's treating it like it's the file path name and trying to change it from a one note package. Yeah, it's a reserved character. Yeah, yeah, yeah, rather than... And you can't use ampersands instead of the word amp. No, you can't. It'll tell you right out of the gate. Can't use that kind of a character. So yeah, there was definitely some interesting things. And Planner didn't seem to have a problem with it as much. I think earlier on there was something that we noticed with that too. But yeah, definitely some things to consider before you go down that road too far. So something... So when you're keeping it simple and thinking about, I think in this example too, of your naming conventions to make sure that you can do it in one application, but not in another, you want them to be consistent so they can be used anywhere. Yeah. Something that I like is case sensitivity in your naming because in like some coding standards, some people do it, you know, every new word is the first letter, letters capitalized, everything else, other letters are lowercase, so that you can have less space, tighten it, but you can easily read the naming because, you know, each word has the first letter capitalized. So that's just, you could have more complex naming, but following that method, rather than have it all lowercase, all caps while it's just infuriating to try and read that stuff. So... When? What I was going to say, what I'm hoping is that at some point we will have a way to sort our teams and that when you're using these types of things, if you're using numbers or you're starting it like you said, Kirstie, like ORG, that there would be a way for us to not have to drag and drop to get them in the order that we want that you could say like put these in ascending or descending order or some sort of an order. I've seen those requests sound on the feedback portal, but nothing yet, unless you guys know something. One of the things you have to us to consider is that the applications are cross-platform. So Linux has different rules around filename means and even inside the Office apps, there are restrictions on what you can call name documents and things like that. Mac is the same way because Mac is basically Darwin, which is Linux. So it's a matter of, you know, they have to try and find a happy medium you know, illegal characters in Linux are different than illegal characters in Windows. Linux doesn't have a 256 character limitation like Windows, you know, there's a bunch of differences and Linux is case sensitive. So anything you do from a case standpoint when it comes across over to the other operating systems, you have to be very specific about it. Yeah. Yeah. Go ahead, Kirstie. I was going to say, the use of spaces as well, it can be an important component for readability when they're all kind of joined together or at least having underscores or something, but you have a space that's going to give you a percentage sign in SharePoint and all these things can get a little confusing sometimes with people. Now we're going to get into the global argument of spaces versus tabs. Yeah. I know, right? What I found from a consistency perspective back to when we were creating these teams was working with team templates. So by using those, we had consistency with the names and the spaces for the teams and the channels. The only thing that had to be added in were those numbers that were coming in at the beginning when using those templates. So I really found those useful. I don't know if any of you have used those team templates that you can create in the Admin Center. I don't like teams that much, sorry. You're more of a humor guy, I know. Telephony all the way. Let's go. Yeah, I'm going to do another one of those.