They often show up if you are using Edge Chromium as your browser and, from the Microsoft Teams client, open a file in “Files”or if you try to open the Team SharePoint site. (and also sometimes when You open a tab that shows a file).
I would like to start by telling you how i went from Lotus Notes, via SharePoint to Microsoft Teams.
Since 1997 I have been working on building systems for “collaboration”. The first few years I worked as a Lotus Notes-developer. Lotus Notes was at that time, in my personal opinion, the most effective platform for building good collaboration solutions. With Lotus Notes, i built document management solutions, good process support with automated workflows, ordering and booking systems, intranets and HR solutions. You could basically build most of it.
Best of all was that once you had built a good solution you could save it as a template. This template could then be used to quickly build the same, or similar solution elsewhere.
The replication in Lotus Notes means that you can distribute the load over different servers and you as a user can also replicate the databases so that you can work offline on your local computer when you do not have access to the Internet (this was during the time you did not always have access to fast internet everywhere and all the time).
Files were attached to Notes documents and you could use the email to attach links to the Notes documents which in turn contained those files. That’s how you (or at least i) did it “at that time”…
Many of you may have read some of my posts on “How to use Microsoft Teams to simplify O365 Governance” and the simple concept I have developed to make everyday life easier for those who have some form of service responsibilities in governance for Office 365.
Did you miss my “How to use Microsoft Teams to simplify O365 Governance” session at the Oktoberfest virtual summit, a.k.a. “TeamsFest”, hosted by European Teams User Group? Below you can see and download what you may have missed and that interests you.
Let me start by saying that I love new functionality that creates opportunities and solves concrete needs, BUT: Having a holistic perspective when managing your organization’s productivity platform is a puzzle with many pieces. In my opinion, there are mainly three pieces you need to fit together as soon as possible if you are to succeed in introducing new functionality into an organization. These pieces are: Continue reading “Things to Know Before Your Organization Opens Up to Use Private Channels in Microsoft Teams”→
As you probably already know, in Microsoft Teams, any user in the organization can sign up for Public Teams while Private teams require the owner of the team to invite members to the team. Unless users know which private teams already exist, the risk of unnecessarily establishing new teams, with the same purpose and similar content, increases. Continue reading “How to reduce teams sprawl by making the existence of Private Teams visible for all users”→
Private channels in Microsoft Teams are now launched and rolled out to your tenant. You can create private channels for a specific group of team members in a team. Only those people that are added to the private channel will be able to see and write messages in it.
Have you informed your users about your guidelines for using this Private channels? If you haven’t done so, now is the time to do it. In the meantime, you can (read: should) disable Private Channels for a time until everyone knows how it works and how to use it.
Now you have the opportunity to create “Private channels” in your tenant, but have you informed all your users about how private channels work and how and when to use this functionality? If not, NOW is the time to communicate the guidelines you have for using private channels. (Surely you have developed guidelines?)
“I have a feeling that most of you have not prepared yourself for this rollout and now you stand there with the “Smörgåsbord” popped up and your users storm in, enjoy the goodies and leaves a very messy table behind.”
On this personal blog I would like to share some findings, insights and stories all around my daily work as a Microsoft 365 Dev architect and consultant.