![\"\"](\"https:\/\/regroove.ca\/stellark\/wp-content\/uploads\/sites\/3\/2019\/06\/teams-manage-features-in-office365-image2.png\")
<\/figure>\n\n\n\nMicrosoft defines “Sideloading of External Apps”<\/p>\n\n\n\n
\nIf you want to turn on some external apps and turn off others , turn off this setting, and then in the list of external apps, turn off the apps that you don’t want users to access. When this setting is turned on, team owners and members who are granted permission can sideload apps to Teams<\/p>\n<\/blockquote>\n\n\n\n
But more to the point…<\/p>\n\n\n\n
\nSideloading of Apps is the process of adding apps to Microsoft Teams by uploading a zip file directly to a team. It’s useful because it allows users to test an app as it’s being developed. Sideloading also lets you build an app for internal use only, so you can share it with your team without submitting it to the Teams app catalog.<\/p>\n<\/blockquote>\n\n\n\n
Now What?<\/p>\n\n\n\n
We wanted our new “Teams App” feature in the new Teams Admin portal so we decided to disable the “Allow Sideloading of External Apps”. This however, did not work. While the “Teams Apps” feature has been rolled out to General Availability the other feature “Teams App Permissions” has not been. Because the “Sideloading of external apps” was enabled it prevented the migration of the “Teams Apps” feature which won’t be available to us until the “Teams App Permissions” feature is rolled out. <\/p>\n\n\n\n
This was a serious head scratcher and now we wait til “Teams App Permissions” is rolled out, fingers crossed both features show up!<\/p>\n","protected":false},"excerpt":{"rendered":"