 Alright, so good afternoon everyone. My name is Justin Klein. I'm the project lead for Microsoft Teams and the rollout for the Air Force. So as most of you have seen from some of the other conferences or some of the other breakout sessions you've gone to, we've talked about a lot of things that are coming down the road. The good news here is Teams is very close to being out and a lot of your cases is already out. So the things you're seeing here, you'll be able to go back onto the Air Force Network and use. Hi everybody. Sorry for the wait. My name is Rima Reyes and I work for Microsoft, as you can see by this insanely large linear. I work for the Teams product group. So essentially I work for the part of Microsoft that helps and builds to develop and create teams. So I work directly with our headquarters engineers and developers that actually build teams for DoD. I've been taking a really close eye on US Air Force because you guys are really ahead of the game. And so we want to ensure that everything is great with the product. So that's why we've got a really close relationship between essentially the government folks and the military folks and myself. So I want to say really quick, I've had a long history in the Intel community as well. So I'm really familiar with this space even prior to joining the product group. So government is what I love and I'm really passionate about it. So it's also why I'm here. Okay, so what is Microsoft Teams? So Justin, let me ask you this. How do you envision Microsoft Teams? Like what does that mean to you? All right, so today we have all of these cloud services that we run on our time. SharePoint Online, you have OneDrive, you have Do Now. And you go into a different application to use all of these things including Skype. You're one of one conversation. So what Teams gives you and the main value for you is that this is a one application window into all of those services. In addition to that, to bring some new things that you may have never seen before and used and you go into those things. Yeah, so that's a perfect explanation. And I swear I did not tell him to say that's his own volition. So yeah, so Microsoft Teams, in the engineering team, in the product group, we say that Microsoft Teams is actually the presentation layer to everything else in Office 365. So a lot of times we have various applications that usually are all over our desktop or we have a lot of different files. Teams really brings all of that together into a single pane of glass. Kind of like Outlook. Like Outlook is like your one productivity hub two for email. Microsoft Teams is a little bit different because it's really for chat for things that are a little bit more quicker for collaboration. Like if you want to quickly share a file instead of emailing it, it's a lot faster to do it in Teams. So we call it the hub for teamwork and DoD. We have three main pillars. Communicate, collaborate, and working with confidence, really security, right? In the first pillar, communicate, we have persistent chat. Does everybody know what persistent chat is? What is persistent chat? Exactly, perfect. And that's very different than Skype. Who's familiar with Skype? Okay, I'll talk a little bit about Skype later on. So persistent chat means that you have that entire chat history, right? It doesn't go away when you close the window. It's still there when you reopen the application, which is really important. You also have group chat. Group chat essentially means you can have more, anytime you have more than two people. So essentially like three people or more in a chat conversation. That's called group chat and you have persistent chat with that as well. So really important. Let me go over an example for that. The one thing that we have found by using it in the Air Force was amongst our beta test group. So you've got a group of people and you're all chatting back and forth. And let's say you've worked through some project details. Now you want to add a new person to the group. Well, the nice part about the team's application and services, when you add them, they have the entire history of all the chats that you've done. So they can see what decisions you've made, why you've made them. Any kind of communication you want to provide them is given already. That's a really good point. That's really important. When I worked at the National Security Council, I worked at the White House for six and a half years prior to joining Microsoft. And everything was really fast in terms of document collaboration. I mean, if the president needed content, he needed it five minutes ago. And also having a history or understanding of how that decision was made was really important. So if we had teams back then, who would have been revolutionary? Teams also has meetings too. And these are just peer-to-peer online meetings. Do you want to talk a little bit about meetings? Most of us today use the telecom services through DISA or through maybe other parties. And one of the big problems I experience as an end user is I meet with 100 people on the telecom. Somebody goes on mute and you guys know the story. You have the music playing in the background. You tell somebody, please stop. You know, no one stops. And then you try to talk over them and it becomes a mass chaos. Well, with a team service and a meeting, you can hold, again, this is all using a microphone attached to your computer, but you can hold a meeting with a group of people and you can see exactly who's talking at any given time. And you have to go and go in, now they're muted. So there's a lot of other features that come with that. You can all take meeting notes together while you're in a meeting. You can record meeting notes and push them back in your team. There's a lot of other features, but to me, that is the primary annoyance I have. Dennis in the back and talk to that. We've had many meetings where we're shouting at people to please don't use, don't put us in the hall. So how does that scale? Well, I mean, I don't know if you've ever dialed in the cybersecurity forums, but they're always a nightmare. There's tons of that. But there are hundreds of people trying to dial in and kind of support that kind of volume. Yeah, so peer-to-peer meetings right now can support up to 250 people. Eventually, that's what's on the roadmap is to have something called live events. It's not in DOD yet. It's going to be further down the road. And that will have the ability to hold up to 10,000 people. But it's not here today, so just... Okay, so the second pillar, collaborate, which is the core, the meat and potatoes of this thing, right? I know Microsoft Teams is a really generic name, right? I'm sure people are like, what does that mean? But really, the crux of all of this is this app right here, this Teams thing right there, that icon. Because essentially, you can create a team, and a team is a workspace where your work team, like your colleagues, and you can work together on content. You can chat together. You can pin certain things that you want within your workspace, and it's all in just one place, right? Before in the past, sometimes I work with my colleagues, and I have to send an email, and then I have to go visit a different website because I had my favorites there or my files were here. Everything is just jointed, right? Teams really brings all of that together into a seamless workspace. It's really easy to understand. Do you want to talk about Teams, yeah? I have a question for everyone who here loves SharePoint. Loves it. It's crazy about it. I'm a former SharePoint person. I'm also the SharePoint program manager. I'm sorry. There we go. Teams gives you an overlay to SharePoint. So you don't have to worry about all of the billion other Features that SharePoint gives you. As an end user, you just put your file in there and you collaborate on it with your team. That's it. It's as easy as that. It connects in your OneDrive. So your OneDrive account, you can take the file shared with your team members. You can all collaborate on it at the same time. You can see who's typing what at the same time. Simple as that. You don't have to go into all of the complexities of SharePoint and worry about people messing up all the permissions, messing up things in your SharePoint site. You're not doing that anymore. So it's a huge value for us just in that proposition. All right. And so working with confidence. So Teams for DOD is accredited for just the IL-5 information. So you can have solace in the fact that everything that you're putting in Teams is okay. And it's okay by just that. So we've already done the hard work for you. The accreditation, please. And I'll add to that. The IL-5 means that the files are double encrypted. They're encrypted at the database level. They're encrypted in transit using the latest standards, the ST56, and it's FedRAMP approved. So this environment was built for the DOD's information. Oh, and it's HIPAA as well, too. A lot of people don't even know that. It's also HIPAA approved as well. And on permissions, the other nice part about the team function is when you create a team, by default they are private. So that means any information that you're sharing across the team is only searchable by your team members and no one else. That's a good point. So Microsoft Teams was actually built from kind of the ground up through a web-based interface. So we really kind of focused on, okay, how can we make it into a product that is easily portable to any sort of device? Because we know all over the world, people have various devices. Now in DOD, and especially specifically in US Air Force, we've got the desktop application available and the browser version available. I know, like, mobile. So Teams Engineering is going to have teams available on like an iPad or an iPhone soon. But we know that there's extra processes that US Air Force has to take in order to enable that piece as well. So on the roadmap for the Air Force, today, as I said, we've turned on the license for almost every user for the web client. So you can go in through Chrome, Edge, and Firefox to access this application. We have a link for you at the end to tell you how to get to that. Additionally, the web, the desktop client, we're pushing out slowly. We're still working with the EffectModel program office to see if we can push that out. But our target is the end of September to get, to offer that up to everyone. And if it's not available through a push, then we're going to offer it up through other methods, either probably through SCCM, so you can go out and get it if you want it. There we go. Well, one other thing. The mobile portion is coming, but we still have a couple things that we need to work out with this on what connections we need to enable to allow that. But that is very much the Air Force's goal to open up teams and all of the chess services to mobile devices. Oh, yes. And obviously, it's a pretty good Air Force network and it can hold more system information, which is great for a slot to be in the SBA. That's what you owe. And you're bringing it to mobile devices, but what's going to be my incentive to use teams versus Slack? Is it going to be available to commercial phones to download? And somehow, do you authenticate users to be able to use this instead? Okay, so there's a couple portions to that question. First, I'd like to address the bring your own device perspective of this. Right now, that is on a road map. That is also a place that we want to get to. But we need to solve the mobile on GFE first. Once we get there, we're looking at solutions that will allow us to do it on a bring your own device. I don't know, Dennis, if you wanted to add anything to that. So, yeah. So, I'm Dennis Plansky. I'm a mobile fan. I also work with Chas Kremel and partnering with Justin on teams. So, working with the mobile drives and some other things. So, our goal is that we make the Airman mobile, right? So, it is to get it on that device. It is to get the native container, not, you know, right now we use Blackberry UEM, but how can we get it natively? We're working through those things with Justin, and then, I guess, Mr. Koninsky was up here earlier from SAF. Working on the BYOD, there's a proof of concept that went on. And working through the results of that, I don't know, struck back there from SAF, working through the different policies. Now, when you talk to Mr. Greenwell at DOD, the security guy, Slack is in an IL too, maybe even if it's an IL. Why, you know, you can drop FOU out there, and it's out in the wild, wild west. Probably hosted in other nations. Those are some of the adversaries that we have today. So, the goal is that you would use Teams, and it is on the mobile device. Slack, you can just pop in and out of there. But by policy is really, I think, enforcement, having worked at DISA, they really like to cut the connection to Slack because of the information that's being spilled out there today. Does that answer it? It does. I was just curious if it is going to go through commercial vocal just because, obviously... So, our goal is that, and so, our other goal is that we want to use it, not have to use it because of policy. Exactly. So, we've got to get that end user experience there, but we're not there yet, so we're working towards that. Yeah, something just really quick to note about Slack, because I have purviewed to about like 14 million end users with Gov using Teams. And what's interesting is that we've had a lot of interesting scenarios where we've had customers use WhatsApp or Slack. And unfortunately, when you have the free version of either one of those, Slack owns your data. And if you are part of a team, and let's say you get fired from work or you were forced to leave, you still have access to the information if you're on Slack or WhatsApp, which can be a huge security risk. With Teams, it's a centralized admin, right? So, your identity follows how you are in the workplace. So, essentially, if you get let go, if you move to another company, that data, that essentially entry point to that data gets cut off. So, no longer can you access it once you leave. So, that's really the big, I think, kind of like selling point with Teams is really security here for the most part. So. And I would add in the integration with the other services, many of which you guys haven't seen yet, but they're on the road map to be delivered as part of Chess as well. Forms and flow, workflows that pass through all of the Services will go through Teams also. So, it kind of enhances that, and it gives more incentive to use it. And also, our slogan is W-U-S-D, but with Slack there. So, we don't want to. Did not know that. Good to know. So, I went a little nutty with the Air Force images on the Air Force website. So, excuse my excitement here. So, the reality of the modern workplace. So, we have a lot of studies done in the product group. And so, 20% of our average workday is spent tracking down information. Who feels kind of that pain? People are like, yeah. Right. 28% of an average workday is spent managing email. I feel like mine is 50, but I don't know what you guys are. Right. And then, 59% of leaders say that they're missing important information daily due to information overload. I mean, even if you're not a leader, right? There is information overload, right? So, Teams helps kind of focus you on where you need to be and what information you need to actually read or get to. So, why Teams? So, I know we've sprinkled a little bit about the why, but Justin, why do you think the Air Force should be using Teams? I've already mentioned a couple of those reasons earlier, but you mentioned email. So, I get several hundred emails a day, sometimes more than that. I can't sort through all that. Whereas the teams that I've been using in conversations, I never have to go back to an email. You see this greatly reducing the amount of email traffic we do as an Air Force. Now, that's not going to prevent information overload. You're always going to have that. But Teams has built-in filing system for that information. And the search capability is far more robust than what you get in trying to find an email in a haystack. All of our communications are filtered in. We'll go through the channels and the demonstration, but they're all filtered into which groups are used in a team and which channel is talking about what. So, you kind of know where to go to find things. Yeah, absolutely. I mean, that's a great point. You know what's interesting? When I first started living and experiencing Teams, now I know I work for Microsoft, which is a commercial company, totally different environment, right? Apples and oranges. But I will say this. There was an interesting change in behavior that I experienced. And behavior and end user experience is really important to me. I was actually a psychology major in college. So I care about what people think and how they actually perceive technology. It's one of my passions. What was interesting is that I started using email a little bit less, and I was more conscientious about who I sent emails to. So I had more email etiquette, because I knew email took time to read through. And it was more, it felt that it's a bad thing. It was just it took a little bit more time. I had to be more focused and detailed on email. And then internally in my company, so if I ever wanted to communicate, for example, with Amanda, who's sitting in the back, with Microsoft, I just wanted to send her a quick note. I would use Teams. And I realized the response and reply time was much faster than having to go through email. But email's still a really important part of my day. I'm adorably, for the most part, use email to communicate with external entities. So anybody outside of Microsoft. So that was just an interesting shift that I experienced. Not saying that you guys are going to have the same experience, but outside the company, email inside Teams. So just to kind of support what Justin just said too, there's been a study done, a Forrester study, that four hours a week at minimum were saved using Teams. And then essentially for a 5,000 user organization, which you guys are about 600,000, maybe more. I'm sorry, 700,000. That'll probably be a higher cost savings for you guys. So I expect that check. We'll ask Forrester, like, hey, Ramison. So we can deep dive into a little bit more. I'm going to kind of set up a little bit the details of the communicate, collaborate, collaborate, and working with confidence. And then Justin, while I'm running maybe through the first two slides, can we try to see... Well, I guess I can't really do that with your machine, but I'd like to try to test out your machine to see if that'll work for the demo. That's okay, so afterwards. Okay, so we talked about communicate. So we talked a little bit about threaded and persistent channel discussions. Channels are essentially a subtopic in a team. We'll go through that. You can stay in sync with private chats. We talked a little bit about that before. Justin, I think you have a good story regarding communicate across geographies. Yeah, so our organization is geographically separated. Most of my home office is at Hanscom, and it's been a pain, just a real pain. I'm sure those of you in the same situation understand. Trying to communicate and stay on top of things is nearly impossible through email. You get so much email anyway, you can't read it. But using this service, I'm able to just dial in members of my home office at Hanscom, have a quick call, or I'm able to set up a chat, and just helps the collaboration greatly. And I know once you'll use it, you'll see what I'm talking about, but just being able to scroll through and go through all of those communications so that I'm up to speed with what's going on at the home office is hugely beneficial for me. So I see this helping out those organizations across the airport immensely. Yeah, and something to add to this too. A lot of times our communication can seem really formal, and sometimes that can give people some anxiety because they're like, am I writing the right words? I reread emails that I write sometimes several times just to make sure that I'm not saying something colloquially. Anyways, Teams takes down some of that kind of rigor a little bit, and you can actually use stickers and emojis and memes in your team's conversation, so you can do smiley faces, or face problems is my favorite one. Finally, we can communicate with your members. Sometimes a meme does more justice than a meme. It's like an understanding without some words. All right. So I know this is like a really like, whoops, there we go. We've got a couple of pictures here, and I know this isn't necessarily Air Force pictures. I don't replicate this with Air Force pictures, but this is an example of what a meeting looks like. Who uses an iPhone and has like FaceTime? Yeah, does this look a little familiar to FaceTime if you have like multiple people when you chat with them? Or I think even Google has their group meeting solutions very similar to this too. Now, when you're sitting at your desk, Dustin, do you have a webcam? It's been the same. It's totally fine. Do you need a webcam to talk? As a matter of fact, for us, the webcam really doesn't add a lot, but the key is the audio conferencing. That's where, as I mentioned earlier, that's where we get a lot of value, particularly with the large telecoms that we hold. Yeah, and the call quality, in general, like we take pride in the platform to say that the call quality is really, really supreme. I'm sure Dustin, you would agree with that too, but I've noticed even a difference from moving off of Skype and into Teams. The call quality is way different. So is this... Can we use Teams to say to the contractors, meaning I have a telecom, I have a telecom, I got military members that are going to be in it, I have this contract that you see that I'm doing business with, will it be able to use in that sense, as far as holding hold of it? So this service is only right now built for members that have CAPCOM and an athletic company. So as long as they have that, then yes, you can use it with them. Yes, you have something out on that. So a couple things. One, if you have users who are external sitting at their corporation, if they have access to the CAP card, the work mode of solution, that would allow them to be able to use Teams. The other portion of this is, coming down the line, there is a separate solution that would allow different tenants to federate so that you could share with a company's IO for a tenant and have that communication, that is in the roadmap. It's a combination of the flow of free and business. That's actually a good point. So you mentioned telecom. Today it's not telecom. It's audio calls. So there is this distinct difference that is another feature that's on the roadmap that you'd be able to purchase with telecom. But it's the audio. And that's what I meant. No, I get it. Some people, they hear different things. That's the audio portion. So another thing is the other services, the Navy, Marines, DLA, they're moving into Office 365. Very near term, we're going to federate between the other services so you'll be able to collaborate with all of the joint services. All right. Question? Not today, but that is coming in the future. So, yeah, another asterisk coming soon. There is an Office 365 service called Stream that will be like YouTube for the Air Force. That will let you record your meetings, help through this, and then play them back and even transcribe them. Yeah, in the paper, yeah. Any other questions? So collaborate. This is, again, the meat and potatoes I was talking about before. So this is where the actual team, the employees, and start collaborating on information. You can share and co-author Office documents within the team's app and Justin knows the answers to what is actually helping you enable to do that. So this user's SharePoint is the background in which we mentioned, but it's hidden to the end user. So all those people that don't like SharePoint, if you're using it, you just don't realize. Love it. Great. That's the right answer. Thank you. You also get built in apps, SharePoint and SharePoint, and there's a few more coming down the pike too, so you'll be able to integrate all those apps within your team. You can also search across people and files. Justin was talking about that earlier. It's pretty amazing. I actually used to use SharePoint Search a lot, and now I actually just use Team Search because it searches through SharePoint as well, which is really cool. So one thing I don't think we're going to show any of the files button on the left actually goes through here. So if you've touched anything recently, it'll let you know you don't have to go find it. Here it is. Just click on it. Go access it. Question? Can you share a problem with PIA? I don't know. So right now you can. Now there are some policy things that we're going through with SAP on do you need PIAs to be able to do that? So maybe that changes in the future. But right now the policy is you can. Everything needs to be made private, so it's not searchable. But you can do that. Yeah, and to add to that search piece, which I think you touched on it earlier, everything is security trim. So if I search for something in Teams, I'm only finding results of things I have access to. I'm not going to be able to find things that I don't have access to. So it's really important, is the security trimming on that piece. Question? So if you're sharing files on the backside of it, when you save those files, do they go into just like, say for instance I'm coming out of Teams and go into SharePoint? Will I see those same files that I've shared in Teams? Yes, so what this does is when you create a team, it creates a new SharePoint site. So you can access it by going to the SharePoint site if you want it. If you love SharePoint like me, then do it that way. Or interface, a much easier to use interface for that type of collaboration. Any more questions? Okay, so working with confidence, again we touched on this earlier a little bit too. The biggest thing here, and I mentioned this with Slack, is the single admin experience. Is that a good question? I'm just trying to put it all together. I'm an ISSM for one of the jobs that I do. So that's a job that you don't have all the information. So we've linked up on Skype to it's been a lifeline to help each other. So this way we can do it, but our conversations don't disappear and we can have files to help each other out is what you're saying. So I'll give an example. When I switched roles in Microsoft, I joined a different team. I had no idea who was who or even the context of what was happening. But they started adding me to some of the teams and I was able to actually go back in time and see a lot of content, what decisions were made. I had context as to what was going on with my role today. And it actually helped me get up to speed much, much faster if I didn't have that information. So it's really the beauty of persistent chat within teams here. The direct correlation is when I worked with my ISSM and ISSOs to put together an eMass package, we handled all that through a channel. All of the cyber security plan, all of those things were done through a channel in our team. All right, so let's see if we can do a demo. Do you want to try to see if your computer would work? So give us like two minutes while we switch over. If you guys have more questions, feel free to ask them. So with the conversations... Question? Oh, sorry. Being after certain teams, so let's say you're in a team of five people you know, but someone that says, I don't want to be added. Okay, anyone remove someone from the team or just a person that created the team initiative? Great question. So a team has a structure to it. An old structure. The person who created the team is the owner and they have control of who else gets added. You can give other people owner privileges if you'd like, but by default when you add other people they're just members. So that's part of the etiquette of using teams. So if you put together any guide that would be out in a public team that you could find when you get access to the service, it'll explain those types of things. Can you come here and log in? Don't mind. The conversations like in Skype, and I think you said something about as different than Skype or Skype for business or whatever, but with Skype the conversations are saved in Outlook. It is tied to Outlook in any kind of way. It is. Actually your conversations are stored in Outlook in your mail profile. You just don't have access to see them and the reason is is that all your conversations are saved in the team's client anyway. So you don't have to go to Outlook to go search it. So it's literally like single pane of glass. You just go to teams to search, find anything you need. You don't have to switch. For the meeting part, can you move full screen chair? Yeah, absolutely. Yeah. Okay. Great. Okay. So this is what teams look like and this is Air Force teams. So this is real. This is real to you guys. I want to make sure that we did like a real demo. So on the top left here and I'll use this. So on the top left right here, this is called the app bar. You've got activity, chat, teams, meetings and files. Right here is the left rail. This is where all your teams are. And over here is the main arena. You basically push a button here and then push a button here. That influences what happens here. So essentially it's a cascading effect, right? So Justin, do you want to show us? Yeah, one of the teams. So just showing us our 0365 teams soft launch. And this was a team to play in teams. I know that sounds crazy. And as you can see, we've got some windows 10 emojis here. Right into the channel names and a channel essentially is a subtopic of the team. So you're right now. Can you click on like one of the channels? So perfect. So Justin just clicked on a channel and as you can see this window changed and we've got three main tabs up here. We've got conversations, files and wiki. Conversations is where your persistent chat goes through. So Justin, do you mind like scrolling up and just so it goes all the way for it, right? And you can see there's files embedded in here, right? So there's context to the files that you're sharing. You're not just dropping an email and being like, hey, good luck. Go have fun with it. You're providing context to the files that you're sharing which is really important because we have information coming from everywhere. So a lot of times we really need that context. Can you scroll all the way back down? So do you guys see this purple line right here? I know it's tiny. Should we zoom it in? Can you guys see it? That last red line is basically telling Justin, hey, you've read everything before that but you haven't read everything below that. So this is what you need to focus on because you haven't read that part. Do you see that in Outlook? No, right? And that's, I mean, for me, I love Outlook but for me, that's what takes time because I have to go through the whole entire reply history. Right? Can you show the files tab? So Justin just clicked on the files tab and the secret trick is that SharePoint is actually behind the scenes here. So SharePoint is storing your files for you. So nothing's changed in that perspective. You can still create folders. You can still upload files. And can you click on Open in SharePoint? And if you really love SharePoint because I love SharePoint because I came from the SharePoint world so I love it, you can actually go directly to the SharePoint site if you want. So long as you are a member of the team you can access the site, right? And there it is. Regular SharePoint site. You can do all the same things you can with SharePoint. Yeah, question in the back. So with the files thing, I noticed that you can have multiple messages maybe with the same file attached so is it just putting a single copy here in the file area? And if there's a duplicate I'll ask if you'd like to overwrite the previous. Yeah, so single source of truth. How many people have done a V.3 of a document? Oh, I have to merge the changes. It's so difficult, right? You don't have to do that with teams in SharePoint. Okay, and then I don't know if you have anything on the wiki on that. Yeah, so this is a wiki right here in a wiki's part of the tab. So essentially a wiki is like you can just preform text and Justin uses it to manage kind of his tasks and everybody else's tasks. So as he's running this team you're like, hey Rima, you have a task and he'll put it in there. So again, single pane of single pane of glass, single source of source of truth. It's one place to go to find what you need in a very kind of easy and you know, inherent way. It does look like one note and one note is coming. We had to wait for one note to get approval. They're a fed ring up cycle. So if you click on the plus sign that's where one note will be. So there's a plus sign where you can add these tabs into teams. Eventually this will grow and you'll have more. So as they go through the accreditation process and get approved we'll get more tabs in there. Do you have stream? Yeah, that's new. That is absolutely true. Yes. So you guys have a workaround for this which is pretty genius. You see key links. You can use a wiki for a number of things. I like to have it as like a read me. If I'm added to a team, where would I go first? So all of your key links, all of your key information you can have immediately accessible to the user. Did you want to just show what the upload process looks like? Sure. Just for like a file? Like to a conversation? Yeah, the attached function or something. Or you can try. Whatever you want to do. So Justin's going to upload a few things here. So you hit the paper clip icon, right? Similar to Outlook? Yeah. The Wi-Fi is a little spotty in here. That's what I was going to ask. So the speed of it is going to be depending on the speed of the network, right? Yes and no. We've done a lot of performance improvements in general just to make sure we're using as little bandwidth as possible. But yeah, obviously, if you have really, really slow Wi-Fi it's going to take a little bit longer to upload. For example, it usually doesn't take this long. But everybody's on the conference Wi-Fi. So it's fighting. Sometimes we're down on the network as far as SharePoint Outlook, all that stuff. Yeah, if you don't have internet, correct, if you don't have internet then you might need to go take a coffee break. But, um, yeah, sorry. I don't know what to tell you there. Dennis, do you want to talk about how it's helped you? Sure. So as I mentioned, you talk about what's down with Outlook and things like that. So I'm the lead for the IRT. How many have heard General Holm's State this morning about the end user experience? How many have heard about General Skinner? What's happening about the end user experience? Well, I'm neat even that. I was the email PRT lead. I work in Africa. I work with Scott Hightman. So, if, if, Justin, can you go down? Because you guys are on my PRT. IRT, right? PRT. There we go. Use-afi latency troubleshooting. So, the 30-HC-IG AFNIC, Use-afi A6 and many other 691st, 83rd, 26th. Everybody's been working a lot of this. So if you go to the files through our troubleshooting, we talk about one of the most disadvantaged sites, Interluk Turkey, in probably the Use-afi AOR, we found problems trying to share packet captures. I had a solution. I did talk to Justin a little bit, but I got a little aggressive sharing with a lot of the teams. So you can see a lot of the packet captures and all these sources of information, although Interluk's email wasn't working very well, we're downloading files to teams and it's working just fine. So, the team around the world, literally, this was done a lot of it. We had packet capture going on at 1 o'clock this morning. I got a couple hours this late. But, and everybody's dumping them in the team so that the folks at the 38th at Panker can review the packet captures. So, folks at Use-afi, the 83rd, so everybody's using teams for truly a collaborative space. And it's working, working well. Probably not the most organized, but I'm learning. I love SharePoint, I love Justin, but I'm not as good as Justin at SharePoint, so I'm learning. But it is, it is critical to sharing information with your mission partner. To my 38th brethren back here, does it help? Has it helped? I know, I know that they have a Netlaw team at Interluk, to get the Netlaw mission. We are here for Interluk and they've been doing a great job loading this stuff up, so truly a mission need was solved by using this. That's awesome. Thank you guys. No, thank you, that's awesome. Do you want to leave the parting story? I also want to show the last screen of the slide to where they can go and get more information. So, who's interested in finding out more about teams and being able to use it? Oh yeah, that's what I'm talking about. Okay, there we go. Okay. So, if you want to find out more, here's my recommendation. Take a picture. So I'm sure all of you guys have a mobile phone, right? Take a picture of the slide so that you have the URLs that you can go visit it and find out more about teams. We have weekly learning events. Did you want to talk about Tile? Yeah, so part of the rollout of this event towards the end of September and leading up until it, we're going to be running weekly learning events with all of the users who find their way into this service. We're going to be opening up and doing engagement events at the bases, running public fairs articles. We're also going to be running AMAs, Ask Me Anything through these learning events so that you can dial in if you've got a question about this or you want to know how to use it better or what we've learned, some lessons learned for you. Please dial in and join us. Yeah, and the contact down there below is one of our colleagues who's helping to run the events and that way Justin also doesn't get overloaded because he's leading this, so you want to make sure that he's got time to... You can send me a message in Teams, but don't be mad at me. Beautiful, love it. Thank you, yes. So do we have any questions? Yes. All of their contributions remain, their access to those contributions gets removed. So we have more Q&A time at the Microsoft booth right after the session for an hour and we also have some Power BI Q&A if you guys are interested in that. So please follow us to the booth if you guys want to talk more about Teams. We're happy to share. Thank you. Thank you.