Sherman, set the WABAC machine for 2015!
- History & Background (you are here)
- Part 1: Application Authentication — Azure AD Application Registrations
- Part 2: Request Storage — SharePoint
- Part 3: Request Process Automation — Microsoft Power Automate & Microsoft Graph
- Part 4: Enhanced User Interface — PowerApps
- Part 5: Next Steps — Security
How Did We Get Here?
Office 365 Groups is a service providing a single identity for teams across different applications within Office 365. Office 365 applications that use Office 365 Groups for managing access and membership include Microsoft Teams and the various other services like SharePoint, OneDrive, etc.
Office 365 Groups have been around for a few years, but they didn’t really get “proper” Guest Access until around last year.
Let me in! I need to collaborate with my team!
Normal day-to-day businesses work with all sorts of people as part of ongoing projects. Businesses need to work with these people, independent as to what “type” of person they are. So, it’s only natural that these business want to engage with people both internal and external to their enterprise.
This type of engagement offers many challenges in existing enterprises. Usually, IT controls this level of access, but they are historically so busy, or there’s a lack of understanding as to the features/capabilities that can support this scenario. Some may also struggle to keep up with the pace of innovation that is the cloud, and are just so fatigued at that point that they just concentrate on other, more easier requests. When you throw security into the mix, the knee-jerk reaction is usually like “you want to do *what*?”
Luckily there are controls available to let us accommodate what businesses are asking for. While the existing interface allows us to “flip the switch” and turn on the ability to collaborate with guests, it’s a big switch, meaning that it’s open for everybody in the tenant. What happens when we want to get more granular? Luckily, we have additional controls that let us provide this capability.
We have a pretty wide range of services in Office 365 that allow us to get a little bit more granular with what we’re looking to do. Because the guest access control is available at the specific group level, we can use the Microsoft Graph to set it to the relevant value (on/off). This allows us to control guests in, or not in, for a specific group. Couple this with using a Flow in Power Automate, we can also provide a mechanism to create a Team and then set it to allow guests in or not. Now, put all of those requests into a SharePoint list and we can start working with a consistent request process, that starts with a request being submitted, moves through an approval process, and then ends up with a Team properly configured. That’s what this solution is:
- Enter a request for a Microsoft Team, asking for Guest Access on or off
- Flow in Power Automate picks up the request, and sends it through an approval process
- Microsoft Graph in Flow provisions the Team
About the Author:
Michael Mukalian is the Modern Workplace Technical Architect at the Microsoft Technology Center in Philadelphia (Malvern), PA. covering Office 365. He is co-owner of the Tri-State Office 365 User Group (https://www.meetup.com/TSSPUG/), was a contributing author on the SharePoint 2010 Administrator’s Pocket Consultant, speaks at a number of SharePoint Saturdays and Code Camps around the country and was awarded Microsoft’s MVP award in CY2010 for SharePoint Services. With over 25 years of IT experience and certifications in SharePoint and Office 365, Michael has architected and developed solutions for enterprises of all sizes.
Mukalian, M. (2019). Automating the Provisioning of Selective Teams with Guest Access: History & Background. Available at: https://firstname.lastname@example.org/automating-the-provisioning-of-selective-teams-with-guest-access-history-background-fb6776a9260e [Accessed: 18th February 2020].
Check out more great Microsoft Teams content here or join our mailing list to stay up to date.