I store sensitive data in Box. Will that be accessible in MS Teams?
No. No personally identifiable or sensitive content is ever stored in Teams. Teams has access only to shared links and file metadata (thumbnail, file name, author, and version, and uploaded timestamp).
Can I use Box as the default file storage system for Teams?
No. If you use the paper clip icon, or if you drag and drop a file in your Teams interface, the content you share is stored in Microsoft SharePoint or OneDrive.
In the below image of a Teams interface, files you share or drag and drop using the files icon in the lefthand navigation, the files tab on the top navigation, or the paper clip icon in the bottom application tray (all bordered in red) are stored in SharePoint or OneDrive. Files you share using the Box Files tab in the top navigation or the Box app in the bottom application tray are stored in Box:
Can I move content in an existing Box folder to a channel folder?
Yes. But keep in mind that when you use the Box Web app to move a Box file into a Teams Channel folder manually (that is, by dragging and dropping it), you also transfer ownership of this file to whoever owns the destination folder.
I need my Microsoft Tenant ID. How do I find it?
- Log in to the Azure portal as a global or user management admin
- Go to Azure Active Directory
- Under Manage, click Properties. Look in the Directory ID box to view your tenant ID.
What happens if I use Teams to share a Box link with someone who hasn’t enabled the integration?
When one channel member installs and enables Box for Teams, everyone in the channel has access to it. If you're using the integration for the first time, you must first sign in to Box.
What happens if I share a link with someone who doesn’t have a Box account?
If you share a link with someone who does not have a Box account, they can see the file name, file type, and thumbnail (if enabled by your Box Admin). But to access the file itself they must sign up to get an account (or ask their organization’s Box admin to provision an account for them).
What happens to the content in Box if a Team or Channel is deleted?
Members of that Team or Channel are collaborators on this content. They can use the Box Web app to access it.
What do I do if I deleted the Box Files tab?
Add the tab back in. To do this, at the top of your Teams application, click the + button and follow the prompts.
Can I use an existing folder with a Teams Channel or chat instead of the automatically created folder?
Yes. You can manually map the Box folder of your choice to a Teams Channel or to a Teams chat.
Can I use an existing folder with a Teams channel instead of the automatically created folder?
Yes. You can manually map a Box folder to a Teams Channel.
Can I search through my Box content from my Teams interface?
No. Files managed in Box do not display in Teams' native search functionality, nor in the activity feed. That’s because Box files are treated as links, not actual files, and they do not surface in file-specific features (that is, you cannot surface Box files either in Teams’ native search or in your Recents list).
I was using an earlier Box for Teams integration. What’s the difference?
This second version of the Box for Teams integration improves on the earlier version, which was limited in scope and functionality and did not allow Box as a default file storage location for Channel files. We strongly recommend moving to this updated integration.
Do I have to uninstall the earlier version of the integration before I can install this updated version?
No, but using both simultaneously can create issues. We recommend uninstalling the earlier integration before installing and using version two.
Can I edit my Box File in Teams?
No. That is not part of the current integration. However, Teams redirects you to the Box Web app. From there you can edit the file using the document editor of your choice.
Is the owner of a Teams Channel automatically a co-owner of a Box file or folder that's been associated to that channel?
Not yet; Channel owners are equivalent to other members added as collaborators. In turn, that means that from within Box anyone can delete the Teams channel folder.
Does Box for Teams work in private Teams channels?
|For this Team...||...and these Channels...||...is Box for Teams available?|
|Private Team||Private Channels||No|
|Private Team||Public Channels||Yes|
|Public Team||Public Channels||Yes|
|Public Team||Private Channels||No|
Do I deploy Box for Microsoft Teams centrally, company-wide?
The short answer is, no. After you enable Box for Teams for your organization, it actually installs on a team-by-team basis. You only need one member of a team to install the integration – it can be any team member – at which point the integration becomes available for every member of that team. But you cannot install it for more than one team at a time.
The system displays a message that indicates Box for Teams isn’t available. But I deployed it. Why are my people getting this message?
This message applies only to ad hoc or one-off chats – that is, chat exchanges that take place outside of a Teams Channel. Essentially, this message displays because of a conflict between the default Teams chat folder creation and a setting in the Box Admin Console.
It’s not unusual for a Box admin to restrict content creation by checking Only admins can create and delete first-level folders, files, and bookmarks.
There are various reasons for this, mostly having to do with a company’s security requirements. But if the Box Admin enables this setting, it prohibits any non-Admin from creating a folder at the top level – that is, the All Files level. And that prohibition extends to any systematic attempt to create a folder at that level automatically, as the Box for Teams integration attempts to do. As a result, there is no default catch-all folder to store all content shared within ad hoc chats. And without that default folder, people in ad hoc chats cannot access Box for Teams. (They can continue to access it within their Channels.)
We are working on a way to allow Box for Teams to create a default folder even when this setting is enabled.