Following SharePoint sites through Viva Connections app via Teams mobile app
Hello, Is there a way for users to follow a SharePoint site when accessing a site through the Viva Connections app via the Teams mobile app? I know that you can follow a SharePoint site when accessing a site through the SharePoint mobile app, but this is not the experience my organization wants for end users. We do not want end users to have to download another app and leave the Teams mobile app for one task. In addition, the majority of our end users access SharePoint through Viva Connections via the Teams mobile app and do not have access to a PC.
Sharepoint app in Microsoft teams doesn't open files in subfolders
Hello, We have an app for Sharepoint created using viva connections in Teams. It appears as an icon in Teams navigation. When we open it it shows us our Sharepoint homepage(hub site) and we navigate to different sitecollections using top navigation with in teams app. We have encountered an issue with opening a link added over quick links on one of our site collections page. If the link in quick links webpart is just an excel or an other office app or even pdf it works fine. But the link in quick links webpart points to a folder inside Shared documents library in the same site collection. Link looks like this: https://org.sharepoint.com/sites/sitecollection1/Shared%20Documents/Forms/all Attached is the error message. It works fine in Sharepoint when accessed through browser. Can someone kindly help me understand what could be the issue in such scenarios? Regards, Sush410
Some SharePoint standard links are opened in browser when clicked in Teams using Viva Connections
We load a SharePoint modern site in Teams using Viva Connections (but the same issue also happens when adding the site as a tab in a team). Some links are working correctly inside Teams but others like the "Site contents" link in the left navigation or the "See all" link from a modern list webpart open a browser to load it. If I use Teams in the browser the same links are also opened in a new browser tab instead of the same where Teams is running. Why is this happening and is there a way to overcome this behavior?
