I got back on the circuit this week: aMS Germany and Power Platform French Summit bookending a delivery of Microsoft 365 Fundamentals: so all in all I've had little time to really sit down and think about what to write - but then every once in a while a good turn of fortune occurs, and this week I found out that Lists now supports tel: which is something I have wanted to see ever since I wrote about hyperlinked email addresses. You see, launching a PSTN call from a list makes a lot of sense: namely because people and lists go hand in hand. A list of staff members. A list of potential recruits. A list of vendors. And the thing is, Teams as we know it has never really had a proper communal phone book has it? One that all members of staff can share. You know, I am not talking about some all singing, all dancing, aesthetically mind-blowing app. I am talking about basic no frills does what it says on the tin. I want a list of people, to be able to be searched by a team, and then can call on the spot. One or two clicks then go. Well, now we can all because Lists supports tel://.
So Build is done. It's in the books. I just finished up my last session moderating which was one of those sessions at the back end of the conference. You know the ones. Less attendees, but every one of those attendees die-hards still asking awesome questions to get every last ounce of value out of the event. I remember the first time I was out in Vegas at Inspire. I was still there at the Mandalay doing sessions on the Friday morning when others were still in bed conferenced out or were checking in at the airport to go home. And you have to hand it to the speakers who still show so much passion at the end probably having just done the last few days on about 4 hours sleep a night. So signing out of Build, I wanted to complete a trio of blogs on the new Power Apps for Microsoft Teams which were announced at the conference. The first blog was on Perspectives. The second was on Boards. This one is on Profile+
Day two of Build. It's a good one. And I have the opportunity of following up yesterday's blog on Perspectives with one on Boards. This is the second of three blogs on the three new Power Apps Solutions introduced at Build, and which I think are really building (excuse the pun) on the success of others released over the past six months. I am talking about Bulletins, Milestones, Employee Ideas, Inspection and Issue Reporting. If you haven't used them yet, they are Power Apps within the Teams App store which you can install and which are deployed in Dataverse for Teams. The great thing about these apps is that you can go on and extend their functionality, you can widen their use in broad distribution scenarios, but what is also really cool is that they are straightforward and you can simply use them straight out of the box. They are designed for a specific purpose. So let's get to it for today
Today at Microsoft Build it was great to run a Table Talk with Vesku Nopanen, Reza Dorrani, Mar Llambi, Karoliina Kettukari and April Dunnum. Lots of people showed up. I think - and I say think - we answered most questions. The chat was moving so fast that Reza, Mar and I were leapfrogging each other trying to answer them in time. There's a lot of interest about Dataverse for Microsoft Teams - particularly the apps which can be installed in them and extended with by Fusion Teams - Teams which are mixes of citizen and professional developers. Now some of these apps you may already know and used, and some of them I have already written about: Bulletins and Employee Ideas. There's Milestones too and a few others. Today, at Microsoft Build, three more were announced. Profile Plus, Perspectives and Boards. Over the next few days I am going to write about all three and all three are available in preview. Today I am going to cover Perspectives.
Last month I wrote a bit about the new Power Apps Templates in Teams - Bulletins and Employee Ideas, and last week I discussed Applying DLP policies to the environments these apps are housed in. Now It feels pretty natural to continue this conversation about data and discuss Table Permissions within the apps themselves. This is because it's these permissions which determine how users inside and outside the team - and guests - can work with the apps and the data that they contain. Firstly, it's important from a usability perspective that we can granulate access. Think of the following scenario - one team member needs full access over one app in the environment because they are managing it whereas that same user may only need read access over another because they don't need to touch any data within it or add any data to it. You may also want team members to be able to modify data with a specific part of the app - for example links in Bulletins, and not in others. This is all possible with table permissions. Secondly, it's also important from a security and compliance perspective. We want the users we need using the app in the way we specifically need them to use it. Circling back to the DLP conversation last week whilst we want to trust that others will handle the apps and the data within them in the right way, having carte blanche in terms of permissions, or even having permissions for certain users, or guests, at all opens things up to all sorts of risks including insider threats. Like DLP, this is certainly something we want to think about when we deploy, or when we are sharing it outside the Team