Bo is a Principal Consultant for ThreeWill. He has 18 years of full lifecycle software development experience.
Tommy serves as the President at ThreeWill. In this role, he works with his leadership team to hire the best people, find the right business opportunities, and ensure that ThreeWill delivers for our clients on projects.
Danny serves as Vice President of Client Development at ThreeWill. His primary responsibilities are to make sure that we are building partnerships with the right clients and getting out the message about how we can help clients.
In this Podcast, Guest Access Across Multiple Microsoft 365 Tenants: Productivity, we discuss…
| Min | Topic |
| 2:25 | Guest User Access Vs. Tenant Based Users Access in SharePoint |
| 3:40 | Licensing |
| 5:40 | Power Apps |
| 10:10 | Azure AD Groups |
| 13:20 | Admin’s Ability to Open Up Sharing |
| 16:50 | Guest User in Microsoft Forms |
| 18:14 | Microsoft Teams Wall |
| Learn More About Tenant Consolidations | |
| Guest Access Across Multiple Microsoft 365 Tenants: Overview | |
| Guest User Experience Spreadsheet – Coming soon |
Transcript
| Danny Ryan: | It’s Monday, January 6th, 2020 and today Tommy and I talk with Bo George about productivity as it relates to giving users guests access to Microsoft 365. I hope you enjoy this.
|
| Hi and welcome to the Work Together Better Podcast. This is your host, Danny Ryan. This is ThreeWill’s official podcast about enterprise collaboration, how people process and technology combine to help organizations, departments, and teams work together better.
| |
| Hello and welcome to the Work Together Better podcast. I’m here today with Bo George. Hey Bo.
| |
| Bo George: | Hey. Hey Danny. Hey Tommy
|
| Danny Ryan: | And Tommy Ryan. Hey Tom.
|
| Tommy Ryan: | Howdy Danny.
|
| Danny Ryan: | Welcome back. We’re just coming back from the holidays and started up a new year here and this is a actually a follow up podcast on Microsoft 365 and giving guests access. I think what Tommy and I recognize was that maybe it would be good to pull in a couple of ThreeWill experts to this particular topic. And so from the productivity side of things, we’re pulling in Bo George for some more details around things and Bo, we’ll probably end up do this more often this year as Tommy and I have fewer answers to the questions. Just pull you guys in as we need if that’s okay?
|
| Bo George: | That’s cool with me, yeah.
|
| Danny Ryan: | Excellent. Excellent. So the follow-up to the conversation where we were talking about sort of what we’ve been doing a lot on projects with regards to giving guests access and wanted you to find out from you sort of some of the things that are the important topics from the standpoint of productivity. Can you sort of get us kicked off with what some things maybe that you’ve seen going on in projects, and what, as it relates to productivity?
|
| Bo George: | Sure. So guest access, there’s a lot to it, but in terms of SharePoint productivity, specifically in SharePoint, productivity and guest users access versus a tenant based users access is almost exactly the same. I mean, if you give a guest user access to your site to be an owner, a contributor, or a visitor, it’s going to be the same as a tenant user, which is great inside of SharePoint Proper. And then teams, similar experience. Guest users are really pretty much first class citizens in a team and can do all the normal stuff other members of that team can do. I think when you get into some of the other products is where the water gets a little bit more muddy in terms of stuff like the Power platform and Stream and some of those things that get layered into those products. But SharePoint Proper, it’s been awesome in terms of being able to collaborate with people as a guest user.
|
| Danny Ryan: | So it’s pretty straight forward from a SharePoint standpoint, but then when you start looking … so they nailed that, but there’s some other things that we’ll probably have to take a look at as we’re starting, using other products from Microsoft?
|
| Bo George: | Yeah, it’s the historical Microsoft and licensing conundrum that hits everybody and being a guest in somebody else’s tenant only exacerbates that conundrum.
|
| Danny Ryan: | Okay, cool. Well, tell me a little bit more about what are the concerns with regards to licensing?
|
| Bo George: | So SharePoint itself is really good as a collaboration platform and with a lot of our customers, we’ve built a lot of intranets and obviously, as soon as you start building an intranet, in today’s world, you’re going to probably want video.
|
| Danny Ryan: | Mm-hmm (affirmative).
|
| Bo George: | And so with customers, we’ve had that video conversation. If everybody that’s going to your intranet is a part of your tenant, video seems a pretty simple thing. If you have Stream licensed, put them in Stream, then they’re secured to your tenant and people show them. But if you’re an organization where maybe you have guests users, maybe you’re a multi-tenant organization and you have users in another tenant, that question gets a little bit more slippery. And so a lot of those customers, it may be that you continue to do videos in YouTube or private channels or Vimeo where there’s sort of a very complex link that’s not easily discoverable. A lot of companies have been doing that for their corporate communication portals and so that all still works in SharePoint and that’s a like a stop gap for Stream licensing in that case.
|
| Danny Ryan: | Okay.
|
| Bo George: | We did … Will Holland, have to give him a shout out, when we were at Ignite this past November, we went to the Stream team with that question and they did tell us that next year, well now it’s this year, they were going to be adding like anonymous links for Streams so that it could be opened up and stuff like that. So I know that Microsoft has heard the guest’s challenge with Stream and I think they’re working towards it to making that better.
|
| Danny Ryan: | Excellent. Excellent. What other apps are you noticing things that you had to work around?
|
| Bo George: | The Power platform’s another big one. Some things will work for people in the Power platform, like as a user, as a guest user, I can run flows. If I add a list item and a flow has to run behind that, then that should work fine. But say you have a Power app that you built as a canvas app, that won’t work for guest users because of the licensing. So regardless of in my tenant that I have access to the Power platform, I go into it in somebody else’s and then I can’t use it. So that’s a challenge.
|
| Now Microsoft is addressing that for … there’s sort of two types of Power apps. There’s the ones that are your canvas app. They’re sort of a full blown, and then there’s the ones where you’ve customized a SharePoint list form and that happens quite a bit. And the scenario where you customize a SharePoint list for him is one that they’re working to support it. I don’t know. It’s coming out pretty soon, but that one would be like if you have a SharePoint list and you’ve put a really fancy form on top of that list entry, then that will work for guests soon, if not already. I had to look at the roadmap for that one.
| |
| Danny Ryan: | Awesome.
|
| Bo George: | But that’s another biggie that seems to come up. That was a … I tripped over that one like a year and a half ago for a customer where I built a Power app and then they said, “Hey, we have a bunch of guests users.” And I was like, “Uh-oh.”
|
| Danny Ryan: | And it looks like, I guess from project work as well, you’ve got, you guys have sort of picked up this your … Will’s created a spreadsheet, sort of like the different features that are out there. And boy, this sounds like something maybe we could … I know Will’s been putting some blog posts out, but this might be a good little downloadable off of our site, but tell me more about what that is.
|
| Bo George: | Yeah, Will, for one of our customer’s who’s a multi-tenant, Will invested in a good bit of time using his developer tenant and then his ThreeWill account accessing that as a guest to really get to the meat of what happens when you’re a guest using applications in somebody else’s tenant and what’s that experience like, what are the potholes and all that sort of stuff. So that spreadsheet he did was, it was really awesome and I look back at it quite a bit. Sometimes it’s licensing will change in effect it, but it’s really robust for, “Hey, I’m a guest user. I’m opening an Excel document that’s over in my customer’s tenant. What does that mean?” And it’s going to actually use my Office apps permissions or my Outlook or I mean, not my Outlook, but say my Excel or Word clients, it’s going to open in mine. So I might get prompted to log in again or whatever.
|
| So there’s certain things with Office apps that will use your license within your tenant and your products. And then there’s things like the Power apps and then there’s just normal SharePoint stuff or the admin center. We are oftentimes a SharePoint administrator in our customer’s tenant. So he vetted that stuff to see, “Well, what’s that like?” And then obviously we talked about Stream. He even went so far as to about Kaizala, which really doesn’t seem to have a guest component to it. And I think maybe one day that’ll just get rolled into teams. And then, of course, teams is another one. Probably that might be the most common guest user experience that people encounter because as soon as somebody sets up a team they want to collaborate with somebody external. Works great for us.
| |
| So he looked at all those features and all the things that get layered on top of a team, a planner board and things like that. And so you can be assigned tasks as a guest in somebody’s tenant in the planner board and edit those and things like that. So that spreadsheet’s pretty robust, well thought through, and a really great job from Will putting that together.
| |
| Danny Ryan: | I’ll have to … That just reminded me. I’ll have to follow up with him and see if maybe that’s a downloadable resource for us. Sounds like it could be really helpful and, but it’s probably something we need to keep up to date as well.
|
| Bo George: | Yeah, yeah. The licensing roadmap will continue to evolve.
|
| Tommy Ryan: | Yeah. You almost want to wrap that with a blog post and say, “Put comments below if you see anything that, ‘Hey, we want to keep it up to date.'”
|
| Bo George: | Yeah.
|
| Danny Ryan: | Yep. That’s a great point. That’s a great point. Tell me a little bit … I know we’re not really focusing in on security, but tell me a little bit about Azure AD Groups and how that plays into this.
|
| Bo George: | Yeah. That one was really top of mind with guest access because I was thinking about multi-tenants.
|
| Danny Ryan: | Uh-huh (affirmative).
|
| Bo George: | And in particular coming from the mindset that you’re building an intranet or a digital workplace on Microsoft 365 in SharePoint and where Office, or excuse me, where Azure AD Groups are really valuable are that it gives you sort of that single point of control. So with my team who manages Azure AD, I could create an Azure AD Group and call it employees, right? And that could actually literally represent people in multiple tenants, if we’re in a sort of a converging multi-tenant scenario and everybody’s not in the same tenant yet.
|
| Danny Ryan: | Uh-huh (affirmative).
|
| Bo George: | And so you can have guests users in there and they can be in your Azure AD Groups and Microsoft 365 Groups in there, security or Microsoft 365 Groups. And you can also have your tenant users. And what I like about that is then when I’m securing, say I’m securing the leadership site and in that site, I want to give access to leaders who are a member of multiple tenants. Maybe some are from one and some are for the other. Well, I can rely on that Azure AD group for the security and I’m not adding a bo@companyone.com and bob@acme.com and all that sort of stuff. It centralizes your control around security, which is the ideal scenario for that sort of stuff.
|
| So Azure AD Groups are a great way to bridge that gap and manage your users in a centralized place. And then use those groups inside of SharePoint. And what’s really awesome about those is features that really started rolling out towards the end of the third quarter, fourth quarter, audience targeting. I think everybody has it now. Well, those can be used for that as well. So with that same mindset of the employees group, say you have a contractors and an employees and those span multiple tenants. Well, then I could target content to employees by using the employee Azure AD Security Group. And that means employee at company A, B or C, tenant A, B or C, would see content that may be contractor at A, B or C wouldn’t see. So another great reason to leverage Azure AD Groups.
| |
| Danny Ryan: | Yeah, that sounds like it not only helps with onboarding new people but also with off boarding people as well.
|
| Bo George: | Right.
|
| Danny Ryan: | Doing some of the cleanup. If it’s all in there and Azure AD, then you’re getting them out, you can point to one place for them. And then if you’re not making user accounts across a bunch of different places and sort of have one place to go to keep everything up to date, which is definitely probably easier to maintain security that way. What other sort of like guest considerations that are out there?
|
| Bo George: | Well, this tiptoes into security a little bit, but-
|
| Danny Ryan: | That’s fine. You can step on Pete’s toes. I’m fine. I’m sure-
|
| Bo George: | [crosstalk 00:13:18] Pete’ll have to find something else to talk about. But in thinking about, putting myself in the shoes of sort of a SharePoint administrator or even an Azure AD administrator, one of their concerns is how far do I open up sharing, right? And there’s four knobs that Microsoft gives you at a tenant level. So you can say, “Well, you can share with anyone.” And that could be like a Gmail account, a Hotmail account, or you can say, “Well, new and existing people …”
|
| Danny Ryan: | Okay.
|
| Bo George: | Or excuse me, anyone would even be like an anonymous link. But new and existing means, “Hey, even if this person isn’t a guest in my tenant yet, I could share with them. They could accept it.” And then it sort of creates a guest account in the tenant. So there’s that new and existing. And then there’s existing only that says, “Hey, they have to exist in our tenant as a guest before you can share with them.” And then our org only. So those four knobs are really important when you consider the impacts on things like SharePoint and teams, where customers we’ve worked with, they typically end up in the new and existing scenario because teams, because if you don’t do that, then every time you have a team and you want to invite a guest, you’ve got to go to your IT organization to say, “Add Bo’s ThreeWill account so that he can be invited to this team” and that becomes a hassle, right? So that’s why people typically end up in the new and existing scenario.
|
| But that’s at a tenant level. And customers have kind of settled there often for teams and the openness of collaboration there. Now if you layer that down to a site level inside of SharePoint, you’re going to have an intranet, typically if used for communication. So what you can still do at your site level is you can ratchet that back a little bit and say, “Oh, actually for my intranet, I want it to be org only.” So you can’t invite guests to these intranet sites. Or if you’re a multi-tenant, you might say, “Well, existing only.” And in that scenario, you’re a little bit tighter secured on your intranet sites, then your tenant is, because maybe your intranet sites probably are going to have a little bit more sensitive information than a team, right? Or at least information that you don’t want to leak. So existing only would then allow you to control it to say, “Well, if I want to invite Bo to this particular intranet site, he has to exist in my directory already. And if he doesn’t, then that can’t happen.”
| |
| There’s still some leakage potentially there because you invited somebody to teams. They ended up in your tenant and you’ve got to worry about that scenario. And that’s where sort of my thought is the third prong of that approach is to leverage the Security and Compliance Center and have alerts for when sharing to guest is done, specifically for the sites that you’re most concerned about. So you could ignore the sites that are backing your teams maybe because you’re all right with those being open. But maybe your intranet sites or specific intranet sites, you can say, “Make sure this isn’t shared with anybody that doesn’t end with these domains.” And you can have PowerShell and Jobs to kind of monitor that because you do, you get stuck in a open, risky situation just by the nature of those, having those two sets of four levels granularity a little bit. So you have to be aware of it and careful with it.
| |
| Danny Ryan: | Good deal. What else? What else do we need to consider as we look at this?
|
| Bo George: | Well, some areas of concern that customers have had when we were talking about multi-tenants were oftentimes it was audiences. Can people access the content? Which, I think, inside of SharePoint, like I’ve never been happier that SharePoint does stuff better than other products inside of Microsoft. The licensing doesn’t seem to come in play there. So what I think is awesome about that is I can be a guest in a customer’s tenant, they can make me a SharePoint admin, and I can help them manage their farm or they can just make me maybe a site collection admin or a site owner so the permissions are great there. So I think it’s a good story for intranets and I hope stuff like Stream and Power apps and stuff like that come along.
|
| Microsoft Forms, thinking of another product, that one’s pretty wide open. You can already share Microsoft Forms with anyone outside of your tenant even. So those are a good way to layer in stuff like surveys or questions. We have a customer we’re working with now that uses a lot of Microsoft forms combined with float of, fill out maybe an event request or things like that and then have it feed into a SharePoint list.
| |
| Danny Ryan: | Got you. So … [crosstalk 00:18:17] Go ahead, Tommy.
|
| Tommy Ryan: | I was going to say, yeah, I was going through your notes, Bo, and you had commented around team walls. What’s this teams walls all about?
|
| Bo George: | I knew that one would stir you. So this is not as fresh in my memory, but it’s kind of the inverse of it. It’s … So at Ignite, I saw it at least twice or maybe I heard it once and then saw it once. But a team wall, if that’s the right term for what they’re calling it, is say you’re in a highly … what’s the right word? Highly sensitive environment. I haven’t worked in those, so I don’t know. But the scenario they said was say you’re like a stock company or whatever and you don’t want two traders to talk because maybe it actually opens you up to risk to insider trading or something like that, right? And you actually want to create a virtual wall between the two so that they can’t use your technology to talk.
|
| Now obviously, if they wander by the water cooler and talk, you can’t really stop that. But at least your technology and teams, you can make it where they can’t talk. And so what they showed is you could set up these boundaries and say, “Hey, Bo’s in bucket A and bucket A is not allowed to talk to bucket B and Tommy’s in bucket B.” And then inside of teams, when I tried to chat with Tommy, it actually acts like he doesn’t even exist and I can’t talk to him. And I thought that was kind of an interesting scenario to say, I haven’t been in those banking or maybe securities and exchange kind of things, but it makes a lot of sense. And that way, as a company, you can say, “Hey, we put up the wall where these two couldn’t talk. So if some of this has gone on, it’s those that guys outside of work or whatever. We haven’t enabled it. We’ve actually disabled it.”
| |
| Tommy Ryan: | That’s interesting. I know Coca-Cola, I believe, acquired Dr. Pepper and they were trying to keep their information separate. So there’s value in if they spun off Dr. Pepper, people would know that information with the secret sauce of that product line was never seen by Coke. It’s just owned by Coke. I don’t know if it’s a lot of scenarios like that, but it allows you to maybe keep this organization that maybe you’re temporarily holding and treat it as though it’s a separate company and create some barriers to not allow information to leak.
|
| Bo George: | Yeah. Hearing it, it was … I think the reason it stuck in my head is because everything with collaboration tends to be openness and conversation with each other and all that sort of stuff. So to see Microsoft demonstrate it Ignite and talk about it Ignite, a way to put up walls to collaboration means that somebody cares about it enough that Microsoft developed it for teams. And maybe they’re exploring it further, but it is weird because it is that it’s the antithesis of collaboration.
|
| Danny Ryan: | Yeah. You’ve got, I think, the company, one of the companies that we work with, there’s a parent company and then a bunch of companies underneath that, and some of those companies compete with each other. So you’ve got to, even though you have a central IT, you can’t have them sharing information across companies. So and probably in some of these highly regulated industries, you run into scenarios like that as well. So it’s good to … It’s interesting, yeah, that they end up include this as one of the features that they’re focusing in on that. That’s great to see.
|
| Bo George: | Well, I don’t know why, but the visual, it puts in my head as like a horse, where they put those blinders on both sides so they can only see forward to run forward. They don’t know who’s beside them or whatever’s going on, just go forward. That’s all you need to worry about.
|
| Danny Ryan: | I’ve got one last question here and Tommy, I’ll go check with you to see if you have anything to follow up. What are we seeing? So we’re talking in this case about giving guests access and so when I start thinking about that, I start thinking of a high-level, what are a lot of our clients doing with that? Are they giving guests access to partners, to vendors, to customers, to like what do we see? Is there anything that we’re seeing sort of trend wise with regards to how people are using this?
|
| And right away I start thinking like as soon as I am giving somebody access outside of my company, I start thinking, “Oh, we’re moving from an intranet to an extranet type of thing. And it sounds like nowadays it’s like there isn’t such a clear distinguishing like your intranet. People are sort of melding the two together and I might be wrong with that, but it’s just sort of sounds like that’s how things are going. You’re not … You’re intranet, you might have portions of it that where you do give access to people outside your organization. Anything you’re seeing as far as like who are people are starting to provide, to access? Are we sort of seeing as it starting with customers? Is it starting with partners, with vendors? Are we seeing anything there as far as trends?
| |
| Bo George: | So yeah. I think the lines between an intranet and an extranet are for sure blurring.
|
| Danny Ryan: | Okay.
|
| Bo George: | And Microsoft, also with guest access, one thing that I didn’t mention at all is they call it B2C and B2B.
|
| Danny Ryan: | Okay.
|
| Bo George: | And I would certainly say, especially with teams, at least in our experience, but I am seeing it with others, that B2B sort of scenarios where us in our ThreeWill tenant are collaborating with customers in their Azure tenants. That’s like a very common thing. And I think it’s led by teams, which teams are backed by a SharePoint site. So there’s aspects of that. And then in terms of actual what I call “intranets,” which that’s running in SharePoint typically, which has also the backing side of teams and that whole thing. But intranets, there are some extranet parts of that, but it tends to probably be specific site collections and maybe not holistically the entirety of the intranet.
|
| Danny Ryan: | Okay.
|
| Bo George: | Which that feeds into another feature coming from Microsoft that I think is important, which is I mentioned audience targeting earlier and currently that’s available for news articles and site pages and things like that, where you can say, “Hey, this content is targeted to these people.” And soon, I think this quarter, they’re going to have that for navigation. And that’s good because you’re going to have stuff like hub navigation that spans sites and if you have a guest in there, then they’re going to see what’s all out there for them to access in that navigation. They’re going to click on it, get access denied likely. And so the audiences stuff can help that as well. So that’s just another reason for Azure AD Groups because then you could use them in your navigation so that Bo is a guest. Maybe I only see five things in the navigation, but as a tenant user, maybe I see 50 or whatever. And so audiences will help with that sort of stuff too to prevent prying eyes poking around from your navigation.
|
| Danny Ryan: | So the menus are like security trimmed, so if you don’t have access to it, you don’t see it.
|
| Bo George: | Yeah. Well the nav will be security trimmed for the stuff on the site you’re on.
|
| Danny Ryan: | Okay.
|
| Bo George: | But with hub navigation, you’re typically linking, I call it building bridges. So you’re building a bridge from one site collection to another, to another, and all that. And when you build those bridges, people know the bridges exist right now. So even though I don’t have access to the leadership side, if that’s in the navigation and it’s another site, then I might be tempted to click on it and then I’ll find out I don’t have access. And so audiences will be our way to help trim that down to say, “Oh yeah. Let’s only show this link to this AD Group.” And we know that that AD Group is what’s securing that site to.
|
| Tommy Ryan: | Yeah. It seems like if you go outside of your hub, you can’t security trim. When you hop over to another hub, you’re actually almost creating a link that doesn’t pay attention to security. It’s kind of a hard coded link and the audience is saying, “Which hard coded links do I want to hide?” So yeah. They don’t go to it because they don’t have access to it. And I guess it would be nice if the links going across hubs would be security trimmed and that way you wouldn’t even have to use audiences if you want to keep them out of things that see.
|
| Bo George: | Yeah. Yeah, I agree that’s something that in the history of SharePoint has always been bad is cross site collection linking and having that security trimmed. It’s been really good about, “Hey, I’m linking to something within my site and you don’t have access to that,” which, back in the day, we used to have sites and sub sites and all that sort of stuff. So that was really advantageous because if I didn’t have access to a sub site, then I didn’t see the link to it. But now that the world is flat and we’re more often than ever linking across site collections, I think that audience targeting stuff is more important. It would be awesome if it would trim a link if it knew it was a link within this tenant and you don’t have permission to the destination it trimmed it. But I think that that’s probably a very expensive operation for SharePoint people to do in the background, which is why they’ve punted.
|
| Tommy Ryan: | Mm-hmm (affirmative).
|
| Bo George: | Put the onus back on us now to say, “You’ve got to create an audience for it and secure it yourself.”
|
| Danny Ryan: | Mm-hmm (affirmative). So it’s interesting. It’s just sort of going back to the, it’s nice to see … So people have their intranet, more formal intranets, where it’s more of like read only. You’re providing, someone’s providing access where people can get what’s going on within the company. And what you’re saying here with teams, is that’s the place where maybe you’re working together in a team that’s trying to go get something done and you have an outside, someone you need to work with outside the company. You’re seeing that sort of as teams is taking off, that’s more of the place where people are getting external access to work with the people outside the company. And that’s sort of helping to provide a way for people outside your organization to work with you.
|
| So it’s not, maybe not so much an extranet that they’re going to access, but they’re getting access to a team within your organization, sort of like what, and I think we’re what we do with clients as well, set up a team with them and we collaborate with them. They are, it sounds like that’s sort of the extranet somewhat being replaced by teams. It’s sort of like the extranet is teams. It’s you give the access there, you work with the people there, but there’s not like a formal, like you would have with an intranet that’s a homepage, but more of like your teams that you’re trying to get work done. Is that kind of summarize what you were saying or any subtleties you would make with that?
| |
| Bo George: | I think everything you said is fair. Teams is probably the largest conduit of an extranet collaboration scenario that we’ve known and done before.
|
| Danny Ryan: | Okay.
|
| Bo George: | I think the exception is if you have an intranet that you feel needs to be guest facing and the scenario that probably comes to mind most somebody who’s a multi-tenant sort of company, where they have an intranet and they already have companies that are already in other tenants. Then that might be the scenario where guest access to your “intranet” outside of teams, which theoretically means it’s an extranet, right? Because it’s, you’re exposing it, but you’re really exposing it to just tenants that are kind of well known to you. But the idea of an extranet that’s sort of wide open to all your partners and all that kind of stuff is probably lessened because it’s more specific to a team, where you’re going to collaborate with partner A and team A and you’re going to collaborate with partner B and team B and it’s not like this wide open intranet to those sort of scenarios. Probably.
|
| Danny Ryan: | Cool. I could probably pick your brain. You were talking about anonymous access earlier. I have some questions about that, but let’s just wrap it up with that. I think this is great information. I think this is a great subject. I think what’s exciting to hear more about with this is with the whole concept of work together better. It really gets exciting when you see clients not just work inside their organization, but also outside the organization and it’s a lot. I mean, that’s … Nowadays that’s the way that work gets done and so enabling this through teams and enable, once we give them this access to work together, then we get to do all the fun stuff around workflows and all the building apps with them that they’re getting access to all this great stuff that we can do on top of Microsoft 365 sort of starts with this and we’re no longer talking about just staying inside the organization. I think that’s the exciting thing for us in this upcoming year.
|
| Bo George: | I started smiling because for some reason, the way you said that made me think my developer plug would be, if we build it in a SharePoint framework solution, then it’s going to respect the SharePoint permissions and then we don’t have to worry about this whole guest thing or not. We just have to worry about do you have SharePoint permission. That’s just … yeah.
|
| Danny Ryan: | That’s good. That’s good, right. I mean, we’ve had it before in the past where it was somebody didn’t think through this and therefore, we had to code to some use cases that somebody didn’t think about. It sounds like it’s pretty, they’ve done a good job with that. The team has put together something well there. So that’s great to hear.
|
| Bo George: | Yeah. Well and that’s actually what I had to do for the customer where I built the Power app and then they said, “Oh yeah. We’re going to have 300 people that are guests accessing this.” And I was like, “Okay. Well, I guess I have to do this as a SharePoint framework solution.” I cried a little bit, but I was more happy.
|
| Danny Ryan: | Got you. Anything else, Tommy, before we wrap up?
|
| Tommy Ryan: | Nope. It sounds good. Enjoy [crosstalk 00:32:28] some tech stuff from Bo. Makes me happy.
|
| Bo George: | Thanks.
|
| Danny Ryan: | This was great, Bo. Thank you for taking the time to do this and we really appreciate that. We’d love pull, we’ll pull you in later on this year as we get in over our heads and find some different subjects where we feel like you could help out. But thank you for all the hard work that you put on projects. I think it’s an exciting year. It’s a good time to be at ThreeWill. It’s a good time. I think just where some of the projects we’re taking on are pretty awesome and we love having what you’re doing and finding out what you’re doing on these projects. So thanks. Thanks for all that you do, Bo.
|
| Bo George: | No problem. Thanks.
|
| Danny Ryan: | Awesome. Thanks so much for listening and have a wonderful day. Bye-bye.
|
| Thank you for listening to the Work Together Better podcast. We’re available on SoundCloud, iTunes, Stitcher, and TuneIn. If you’re looking for a partner to help you craft a modern digital workplace on the Microsoft Cloud, please come by and see us at threewill.com. That’s the number three spelled out, W-I-L-L.
|
[/vc_column_text][/vc_column][/vc_row]
