Teams not linking to document library
When creating a new teams you also create an associated SharePoint site that serves as its document library. This library then gets linked under the files tab in the general channel. At least this is how it is supposed to be. Lately however this does not seem to work correctly anymore The teams and general channel are created correctly, the SharePoint site is also create correctly. The files tab however does no longer link to the correct sub-site on our SharePoint but to the general site who obviously is not a document library, We are temporarily using the work around with creating a new tab and linking to the correct library but this is not a good solution in the long run. I've tested this on different devices, in app and in browser in anonymous browser windows to exclude any client side errors. On the old teams who are working properly clicking on the files tabs send out a get request to the following url <organisation>.sharepoint.com/sites/<teamname>/_layouts/15/filebrowser.aspx?<querystring> On the newly created sited I am not longer getting a reference to which site it should go and we see a url like <organisation>.sharepoint.com/_layouts/15/filebrowser.aspx?<querystring> This doesn't seem to be a fluke as we have tried it on different days, different machines with different accounts. The only thing we have in common is that the Teams admin role is managed trough PIM and has been requested just in time. Any help would be appreciated. The domain or root sharepoint have not been changed since it's creation many years ago
Recording Failed to Upload to SharePoint
Hi there, I have been recording files since the first day of my class. However, today, after stopping the recording, it shows 'recording failed to upload' prior to some AMS Document Generation error. I come from a non CS background and I don't know how to fix this. I did not find the recording even on SharePoint. And actually, while trying to share a totally unrelated file on SharePoint, even there it says 'Something went wrong'. It was my last class today and the lecture is extremely urgent to get. Please help. Earnest request. Pernille-Eskebo @sharepoint
Pinned items in Sharepoint not showing in Teams
Our tenant just received the update for new Sharepoint Files experience in Microsoft Teams. It's now possible to "Pin to top", which brings a thumbnail view of the selected item to the top of the library view, as expected. However, leaving the Files tab and returning to it, the pinned items are no longer visible on top. Opening the library in Sharepoint shows the pinned items correctly there. Alternatively, pinning an item in Sharepoint, does not reflect in Teams. So it seems the new Teams Files experience is not displaying existing pinned items, it can only display new ones when submitting.
Restrict user group from viewing public teams
My org is in the middle of migrating from Dropbox to SharePoint, with project teams accessing SharePoint primarily via MS Teams. We are making most of our Teams public so that our users can easily discover and use them, however there is a large pool of contractors who have O365 accounts that I would like to restrict from discovering or joining these teams. The main concern is their ability to view files in SharePoint, rather than conversations, etc in Teams. Is anybody aware of a way in O365 to restrict a specific user group from joining or viewing public Teams or SharePoint sites?Files are duplicated when posting in a secure Teams channel
A couple of weeks ago my client's Teams started duplicating every file that I posted in a secure channel. That is, I'd write a post, attach a document that was already saved in a Teams folder (via the paperclip icon) and two things happen: 1. The file takes a while to attach as seen by a progress bar, as if it's uploading; and 2. It immediately creates a duplicate of the document into the parent SharePoint folder (that is, the top level secure channel folder). From there, I'll end up working in the original document I had saved in the sub-folder and everyone else who accesses the document via the Post, is using the new version in the parent-level folder. Ok, so I logged a ticket with my client's IT as they do have a very unusual set up for their whole Microsoft environment and to all of us this is a very new issue none of us has heard of before, so they logged a ticket with Microsoft. However, today I tested it in my tenant - and got exactly the same result! This is not a standalone issue - my tenant is set up completely differently to my client's and I suspect we are not even on the same type of business licence (they'd be on enterprise and I'm just a small business). Not only is this weird but we are going insane trying to keep track of the correct versions and archiving all the duplicates. Has anyone seen this? Any ideas on whether there is a new default setting or something happening on microsoft's end? And importantly, any idea how to fix this?
Teams Private/Shared Channel connected site don't inherit Site Sharing Permissions from Parent site?
We recently started using Sensitivity Labels for Containers so that we could apply a Highly Confidential or Confidential label to a Microsoft Team. Since Sensitivity labels don't include any way to configure the "Site Sharing" permissions for the connected site, we need to first create the team and assign the label. Then we need to go to the Site Permissions of the connected team site and change "Site Sharing" to "Only site owners can share files, folders, and the site". That assures that the team owner remains in control of whether folders or files are shared outside the team. Great, right? (Not quite). What we noticed is that the Site Sharing setting holds for any Standard Channels that are created. But as soon as the team owner creates a Private Channel, the new site that gets created as a result, does not inherit the same Site Sharing setting as the parent. The same is true if they create a Shared Channel. Those new sites revert back to Microsoft's default of "Site owners, members, and people with Edit permissions can share files and folders." So, the end result here is that team members are restricted from sharing folders/files from any of the Standard Channels, but channel members can share folders/files from within any Private or Shared Channels! I would have figured that Private and Shared Channels would have inherited that setting from the Parent site, so it doesn't have to be set for every Private or Shared Channel that is created thereafter. Or I would have figured, there was a way to change the default for Site Sharing...but I don't see that anywhere either. This appears to be a pretty serious gap to me. I would be willing to bet most team owners don't realize how easy it is for members to share folders/files from a team they're responsible for...without them even knowing...since the "Access Control" you can enable within the Site Sharing permissions only works if trying to share the site...that doesn't work for folders or files. Am I missing something here? Am I going about this all wrong? Is there a better way to accomplish that? Thanks 🙂
