Many years ago - when I was a secondary school teacher, I always used to see great stuff on websites or articles in books which I thought could benefit other members of the team. With websites it was always slow and cumbersome having to copy and paste the URL of the site, stick that in an email then add the other members of the team one by one from the address book. With articles in books it was even more hassle and usually involved a photocopier or a scanner - often to much expense. Ultimately, I wanted something quick, cheap and easy to get that information to them that took zero time without having to think about it too much. This is what I love about Microsoft apps - how they work together to make things easy to do. I like advanced - I do - but I will be honest with you, I love real simple stuff which is intuitive and saves time and money. On IoS, between the EDGE app, the OneDrive App and Teams we can get websites and articles from books or slide decks to the Team in seconds and minutes. So the next time you are reading something interesting - a Tech Community article or a Blog - or at a conference and see that killer slide, or reading a book and want to share it with the team, remember it doesn't take a lot to get that into a channel where the whole Team can benefit from it
Why would we want to know how the Team accesses Teams and from where? Firstly, it can tell us more about the Team - do they prefer to use their apps online as opposed to the desktop? If they use Teams like this maybe they use Office like this? It may determine the device which is ideal for them in the future. It could help us with licencing too. If they don't use desktop apps then maybe they would be better suited to an F1 licence rather than something like an E3. That's good for our business and its the whole point about Microsoft 365 - it facilitates how users want to work. Secondly, it may be important in terms of security: for example, who is accessing Teams outside of work hours and where? We could be considering a conditional access policy and want to see the typical locations that users are accessing it from before applying it.