List - Conditional formatting for blank text field
I'm using Lists via Teams (Office 365). I've got a list with a "single line text" column. I'd like to add some conditional formatting if the column contents are not blank. The only options I see in the conditional formatting dialog are "is equal to" and "is not equal to", so I picked "is not equal to", but it won't accept an empty value in the "choose a type or value" box (which is a plain text field, it's not a dropdown). I tried empty single quotes and empty double quotes but that didn't work. How do I do this? Thanks!!
Delete MS Teams but SharePoint site remain active
When a site owner deletes MS Teams, the SharePoint site remains active because we have a retention policy enabled for SharePoint sites. I ran a report from Teams and SharePoint via the admin center, usage report, and PowerShell to list out the deleted Teams. However, the report in Teams only shows deleted Teams but no associated SharePoint URL or name. The SharePoint reports, show the sites are still connected to Teams. Microsoft says this is by design (BS). Needs help to get a report on the SharePoint sites that were associated with deleted Teams.
The issue with channel sites (private and shared channels in Teams)
Hi, I'd like to know of your opinions, experiences, practices, decisions you've made concerning private and shared channels in teams. In my company, we are progressively migrating to Teams from Webex. Users have started creating private and shared channels. My own practice and recommendation to users has been to get a new team created when a different list of users need private access to conversations or documents, instead of a private or shared channel. My reasons are as follow: Rigidity: The SharePoint channel site created cannot follow its own direction if needs arise. It is locked with the parent site. Say we want to reorganize teams and work units, and we want to join a SharePoint channel site with a another hub − we can't, at least not easily. And now the rigidity of subsites is brought back! And anyway, the conversations are also locked with the parent team! It can't be made independent. Lack of control: Control is removed once again from us, the admins − Microsoft loves to allow users to do everything they want and foster chaotic environments. We have disabled group creation and sites creation for all but a few in order to manage the information environment, try to restrict the scattering of important documents, and make things clearer for users. But with private and shared channels, end users can now create new SharePoint sites. As the documents management specialist, I can't easily see where documents end up. And when I export the list of sites to Excel, the channel sites don't appear! So I can't really see which sites take a lot of storage space. Lack of features: Let's say the management team of a department created a private channel for management topics in the department team, and after several months of active use, they now decide they'd like to manage tasks in Planner − tasks that should be private to the management team. They can't, should have created a M365 group for that! Once again, it is rigid. Troubles for the admin: I want to apply a change to all SharePoint sites − so I type a PowerShell command that will apply to all sites. But it won't apply to all sites: not the channel sites. Also, ShareGate can't seem to get the access matrix of channel sites − it returns errors for them. However, when I turn to the Web for advice with this issue, I only find appreciation for private and shared channels, and none of my concerns addressed. Apparently, they allow to avoid the multiplication of teams. However, I'm not sure how multiplying channels is better than multiplying teams. With both teams and channels, users can hide or show them, and as a team always have a channel, they can disable notifications. Maybe I should just deal with and accept the rigidity, lack of M365 features and troubles for the admin. Maybe I should approach the control of the information architecture and documents differently. What is your view on that? Did you have any issues with channel sites, and if yes, how do you deal with them? Did you discourage or prevent the creation of private and shared channels? Have you reconsidered your decision? Do you see private and shared channels as a very useful feature, and if so, why? I'm interested in all experiences on this topic and I'm thankful for all answers.
Sharpoint Connection
For my job, we want ot create a sharepoint that other departments, and outside people have access to. We want to be able to have content (recorded videos, PDF flyers, and other resources) available for all the other stakeholders to access. We have a few teams that have that different resources in them, one for PD, one for our whole team, and its not all consolidated and our team does not want to consolidate them. Is there a way that I can upload the information to a sharepoint without having to individually upload the content one file at a time, or if there was a way to link them together?Linking Teams to a Communication site?
When you create a new Teams channel, by default it will deploy a linked team site in SharePoint for the files to be stored in. However, we need to create a Teams channel that links to a communication site, not a team site. I know you can add an extra tab in Teams and link any document library from any site, but this is not what we want. We need the actual 'files' tab in Teams to be directly linked to a communication site. However, when creating a Teams channel there is no option to choose a comms site, it just defaults to a team site. Is there any way I can do this?
Teams and sharepoint for project collaboration
Hi, We are trying to figure out how to combine teams and sharepoint for better project collaboration and always found some incovenients to solve the whole puzzle. The bussiness case is very common: Departments work in projects with other departments or/and external people. People from the same department needs read access to their department projects documents even if they didn't participate (in order to share knowledge) and 1..N externals can potentially access to project data. With old way (sharing folders) all looked like more easy and now with a set of tools made to collaborate it seems too difficult to find a way We have tested several scenarios but none works. One team for project has some cons; lot of teams and in order to allow access to information to non project members IT has to go to every project site to share with departmental groups. IT support needed in order to create teams as we have restricted policy Team with private channel has the cons; only 30 channels permitted, you have to be very carefully adding members teams and then carefully adding members to channels Departmental Team with shared channels has been the best approach as you can share the channel with a kind of master departmental teams and brings a consolidate visibility on all department project, but it has a mega big cons, only MS Orgs are allowed as externals (???) and it makes it practically useless Now we are thinking in other approaches like having a sharepoint site for all departmental projects or a site for all projects and playing with the permissions leaving teams only for easy and fast collaboration. This approach has the cons we have to think carefully on folder/sites architecture, limits and permissions and a major Administration effort Is there any MS best practice or recommendation for these scenarios? SusanHanley your insights are very welcome ThanksNew SharePoint site created not inherit external sharing from tenant level
Dear All, Recently I found that when we create a new spo site for teams, the sharing capability always showing as ExternalUserSharingOnly. I look found an article mentioning for teams group connected sites the default site sharing settings will be ExternalUserSharingOnly I try setting tenant level to ExternalUserAndGuestSharing; it will not apply. we have to manually update all teams site using powershell or manually. Is there any way when creating teams site, it will always inherit SPOtenant setting instead of default one.Team Sharepoint site not connecting
Dear all, Lately I've come across an annoying issue for one of my clients: Whenever there is a Team (in Teams) created, naturally a Sharepoint-site is created and should be connected properly, as indicated by the following icon in the SharePoint admin center. What we notice lately is that both Sharepoint and Team are created correctly, but they do not seem connected as this icon is not showing. When trying to reach the Sharepoint-site from Teams I am receiving the following error (even after 2 days worth of "later"). The icon reappears when the Teams get deleted and restored but functionality does not. This, however, all seems to be solved by manually deleting the Sharepoint-site from the Sharepoint admin Center and restoring it from the 'Deleted sites'. After this (and the proper waiting time to sync), the icon appears and connection is made correctly. This workaround does works but I don't believe this should be necessary. Is there anyone who can provide a definitive solution for this? Thanks in advance, Kind regards, Adrian
