In the ever-evolving world of Microsoft Teams, it’s essential to stay updated with how certain features, especially bots, are managed and accessed. Recently (as of early December 2023), there have been notable shifts in how bots are accessed in Teams, particularly in relation to direct links and custom app policies. Let’s delve into these changes and the steps you can take to ensure smooth bot interactions in your Teams environment.
Understanding the Access Issue
The Core of the Issue
The primary issue arises when a bot is accessed through a direct link instead of an installed Teams app. This practice may lead to problems, particularly in certain configurations of the Teams App Setup policy.
Teams App Setup Policy and Sideloading
If your organization’s Teams App Setup policy is configured to block the sideloading of custom apps, users might encounter difficulties in accessing bots. Sideloading refers to the process of adding custom apps to Teams that are not part of the official Teams app store.
Teams Clients’ Behavior
The new Teams client adheres to this policy strictly, denying bot access through direct links if sideloading is disabled. In contrast, the Teams Classic client might have allowed such access in the past. However, updates are bringing the Classic client in line with the New Teams client policy.
Solutions to Unblock Your Bot
1. Adjusting the Teams App Setup Policy
- Allow Custom Apps: Modify the Teams App Setup policy to allow custom apps. This change might be tested with a select group of users initially.
- Policy Details and Management: For detailed guidance on managing app setup policies, visit Microsoft’s documentation here.
2. Publishing via Developer Portal
- Create and Connect to Azure Bot: Develop a new Teams app connected to your Azure Bot using the Developer Portal. This approach is particularly advisable for bots in production environments.
- Publish to Teams App Catalog: Once developed, publish the app to the Teams app catalog for your tenant.
- App Permission Policies: Ensure the new app is permitted for user installation under the App Permission policies. For more information on editing app permission policies, check out the official guide.
Important Considerations
Policy Replication Time
Be aware that policy changes “might” take up to 48 hours to take effect for all users.
Testing post-configuration
For testing:
- Use the Teams web client in an incognito or “inPrivate” browser session to avoid caching issues.
- Alternatively, sign out of the Teams client, quit the application, and sign in again for a fresh start.
Recommended Usage
Direct link access to bot chats is not recommended for bots in production. It should be primarily used for testing purposes. For more insights, refer to Microsoft’s guidance on connecting bots in Teams.
Key Takeaway: The Importance of “Upload Custom Apps” Setting
An essential aspect to highlight is that for a user to access an app via a direct link, the “Upload custom apps” option must be enabled for that user. This setting is pivotal in determining access to custom apps and bots within Teams.
Conclusion
As Microsoft Teams continues to evolve, staying informed and adapting to these changes is crucial for seamless operation and utilization of its features. By understanding the intricacies of app setup policies and the right approach to publishing bots, you can ensure efficient and compliant use of bots within your Teams environment.
