The home site app for Microsoft Teams

Published Sep 25 2020 12:12 PM 116K Views
Microsoft

During Microsoft Ignite 2020 we announced the new home site app for Microsoft Teams. The app gives employees a gateway to your organization, starting with the app’s name and icon, which you can customize to reflect the identity of your organization or your intranet. The app’s multi-level navigation lets people find sites across the organization, including portals, teams, communities and applications.

 

This blog gives you a great first look at the app, an on-demand video session packed with demos and a set of common questions and answers below.

 

The home site app for Teams brings the power of your SharePoint-based intranet home site seamlessly into Microsoft Teams.The home site app for Teams brings the power of your SharePoint-based intranet home site seamlessly into Microsoft Teams.

Bring the power of your SharePoint-based intranet home site directly into Microsoft Teams—seamlessly. The home site app in Teams gives your users global navigation across sites, communities, and teams; quick access to sites they use regularly; and a personalized news feed.

 

We are happy to see the excitement for this in the community and with our customers. Many of you have asked for additional information. As part of Ignite, we produced an on-demand video focused on the new home site app in Teams - showcasing how it work and the value of empowering users to discover, consume and collaborate on content like never before. 

"Living in Teams? Now, so does your intranet!" video by @Tejas Mehta and @Prateek Dudeja:

 

 

Home site app in Teams - frequently asked questions (FAQ)

 

Q: Can any site be pinned as a Home site app in Teams? 

A: Communication sites designated as Home Sites are eligible for pinning in Teams as the Home site app using our default configuration flow. 

 

Q: Where are global navigation links curated? 

A: Links for global navigation are managed through the home site, by home site owners, freeing global admins from having to play the role of curator 

 

Q: Can my classic site be pinned in Teams ? 

A: Only home sites are eligible to be pinned as the home site app in Teams with our default configuration flow.  Home sites must be modern SharePoint communication sites. 

 

Q: What is difference between Home site app and Home page pinned as tab? 

A: The home site app provides organizations to pin company branded entry point to their intranet as a top level app in Teams.  It provides an immersive site consumption experience, complete with navigation, mega-menus and support for tenant wide search.  It also provides quick access to company curated resources, important sites and news similar to those provided by the SharePoint App Bar in the web.  Home pages (or any other SharePoint pages) pinned as tabs in Channels provide ways to bring content directly into Team collaboration scenarios, and these pages have navigation and search elements removed to facilitate focus on the page content itself. 

 

Q: Do I need a Home site app for the Global navigation to show up in Teams? 

A: Yes, the global navigation links are stored in the home site of a tenant, and is required in order for the navigation panel to appear in the home site app in Teams 

 

Q: Can a SharePoint team site be a Home site? 

A: No. Only communication sites can be made a Home site in a tenant. 

 

We are humbled and honored by the reaction to this upcoming feature and appreciate all the engagement with us. Please, keep your feedback and questions coming.

 

Thanks,

Tejas Mehta, principal program manager - Microsoft

51 Comments
Contributor

Great idea and a nice way of bringing it all together. Only thing, I want it now to our tenant :)

Regular Contributor

Any estimate on general availability for the Home site Microsoft Teams app?

Good stuff. Looking forward to this. Now we just need session state when navigating away to a chat and back to where we left off ;). 

New Contributor

As long as we still can't change the registered company tenant domain of our O365 subscription expansion on the entire platform, including Teams, is completely useless.  I realize a tenant-to-tenant transfer is possible, it's a risky process involving 3rd party utilities like BitTitan.  Data loss almost always results.  Microsoft seems to think companies never change ownership, their name or reincorporate so everyone's forced to use irrelevant domain namespace or start all over, including moving everything on One Drive.  As a result when our new parent company asked if we want to stay on O365 or move to GSuite with them.... As long as we're starting over, GSuite it is!  Way to stick to your technical limitations and/or subscription policies and lose customers Microsoft.  You made our decision to leave easy.

Established Member

Sounds like a good plan, but even better would be an option for the owner to set the opening tab (not Posts as the current default), so we can choose the platform /content that greets people in each channel.

New Contributor

It is what we need today! Can you pease tell us when it will be available?

Senior Member

When can we expect this to land in tenants?

Regular Contributor

Mars 2021,

 

https://www.microsoft.com/sv-se/microsoft-365/roadmap?filters=SharePoint%2CNew Last Week%2CChanged Last Week%2CIn development&searchterms=Home%2Csite

Senior Member

Looks really promising!

How will this work in the Teams mobile app? For instance, would it be possible to receive a Teams notification if a news is posted on the Home site?

New Contributor

Hi @JohanFiske , Teams notification exists already by using connector in Teams.

New Contributor

@ArefHalmstrand 

 

Looks like the roadmap says March 2021 for the Home Site app for Teams.

 

Click here to review the Microsoft 365 roadmap.

Senior Member

Will this feature also be available in the mobile app? This would offer really big benefits, cause the mobile worker could use the intranet without changing the app. :)

Frequent Visitor

Integration into Teams is a great news

New Contributor

Home site app for Teams: what about multilingual support?

 

1) Can contents that appear on the app panel (global nav item menu, labels like "Recommended news", ...) be translated? If yes, which language they follow (the language I choose in my User profile or in my Teams settings or ...)?

2) My home site has modern mutlilingual feature active. Is the language selector visible inside Teams app? Does it behave consistently as it does in browser?

 

Thank you!

New Contributor

I Installed the home site app.

1.  No Hub menu.
2. The phone app is sort useless as you can navigate back and need to navigate to SharePoint to open a file.
So why bother going to Teams? Look like a nice idea but useless for mobile users. 

New Contributor

Any ideas on the roadmap ID and when we can see this rolled out?

Contributor

Home site is too limited.  While in most organizations there is one portal, in many organizations there are multiple portals.  Large public sector organizations work more at a Department/Division level than the "corporate" level.  The ability to have a Home for that sub-entity would be far more useful for those organizations, driving people to the content they need and use the most. 

Occasional Contributor

Any updates on this? Or, where would we expect to SEE updates on the rollout?

Regular Visitor

Will the Home Site work with on-Prem Sharepoint?

Occasional Visitor

The company I currently work for has multiple banners which are in someways run separately. Is it possible to have different homesites based on a hierarchy or groups?

Senior Member

how many Home Sites can there be in one tenant?

Frequent Contributor

As usual, poorly thought through and not well explained in this presentation. Looks like you're just iframing a site within Teams so why is that a big deal? I could see a benefit if this allowed users to access SP content on a mobile device rather than using the pathetic SP mobile app, but that isn't addressed in this lame video. Once again, Msft is being guided by what their engineers CAN do rather than by what users actually WANT. And by not starting with a clear purpose,  the presentation reflects that muddled, confused thinking.

Also as others have asked, WHEN is this going to be available?  I see March 2021 on the roadmap so that probably means sometime in 2022. Why so long?

Occasional Visitor

We have recently setup a new Intranet however I had to use the powershell command to make a Comm site our root site.

 

Will this feature work on a site that has been switched out like this? 

New Contributor

Any updates on the availability of the Home Site App?

Super Contributor

Any updates about this at all??? It showed up in the Viva presentations, which is another set of branded vapor-ware. It's getting old, continuous pumping of features that are over-promised and under-delivered. A barrage of features to learn and understand only to find out that they're not available. Sigh.

Senior Member

If my home site page have custom SPFx web parts and extensions, can I still connect that home site as home site app in Teams? or the home site with custom SFPx are not supported?

Occasional Visitor

Has Microsoft considered how this will work for Universities and other Education users where the staff and customers (students) exist in the same tenancy?  Are we going to be able to assign a home site through policy / groups? As always thank you for the video / insight into the future but can we have an update on progress please @Tejas Mehta  

Super Contributor

Any updates? Has anyone seen this in the wild?

Senior Member

@Rob O'Keefe 

I'm from the Asia Pacific region (New Zealand) and haven't sited it yet on multiple 365 tenants. 

New Contributor

Haven't heard any additional updates on this whatsoever - looks like Microsoft may be rolling this into the broader "Viva" initiative... I'm not holding my breath, as we haven't seen any roadmap updates on the Home Site app for Microsoft Teams since October of last year.  I was hopeful and had our existing intranet mapped as our home site, in preparation for being able to bring the 'corporate intranet' into Teams.  This would have been a great way to integrate the site, as controlling homepages for a multitude of various browsers is far from practical - instead linking the corporate intranet within the Teams console as a dedicated primary feature for all of our users would've been vastly preferable.

Contributor

As far as I can understand the Home Site app is going to be Viva Connections. And should be in some kind off preview/release from April and moving forward.

Microsoft

Hello @Steven Jordan@nlundqvist and others - yes as you may have surmised, the Home site app is now part of the Viva Connections offering and is the desktop component for it.  All of the prep you've done with your home sites, including setup of global navigation will flow through once you configure and deploy the desktop app via Teams Admin Center. The final bits are expected to be available at the end of the month.  Steps and pre-reqs are outlined on this docs page: https://docs.microsoft.com/en-us/SharePoint/viva-connections#step-by-step-guide-to-setting-up-viva-c... and will include a hyperlink to the download on March 31st.

Regular Contributor

Thank you @Tejas Mehta ! :)

Contributor

Got it yesterday, sadly not working...when trying to use it (after activation) I get the "ask for permissions page". Anyone else having this and/or have an idea of a solution?

Contributor

Clarification - we've got the Sharepoint global navigation app in our tenant and that is the one not working.

Microsoft

Hi @nlundqvist, can you provide a few more details about what's not working? Also have you ensured the home site is shared broadly so that everyone has access to the links in the global nav?

Super Contributor

Ok, we have ours working. I am having a tough time seeing the value so far. I'm working in teams and I want to go to our intranet, how is a web page embedded in Teams better? We often use search, and search from Teams takes you to a browser - I guess that saves you a step. I will try it for a while and see, this is the minimum viable product, idk.

 
 
New Contributor

OK, this is frustrating.  I'm a Global Admin and I still do not see the SharePoint App Bar.  The home page is set as a Home Site and is using the communications template. My tenant has been on first release for a couple yrs now.  According to the timeline, this should have been rolled out to my tenant by now.  

Anybody else having an issue with the SharePoint App Bar?

New Contributor

Hey there, @JOEL L. ROLLINS , Are you specifically having trouble with the SharePoint App Bar as a nav element or are you having challenges with the larger instruction set of the overall Powershell configuration requirements associated with generating the custom Teams App zip file?

I followed the instructions shared by Microsoft that pointed to: https://docs.microsoft.com/en-us/SharePoint/viva-connections#step-by-step-guide-to-setting-up-viva-c... and didn't have any issues once we downloaded the required powershell script  (.ps1) from here. https://www.microsoft.com/en-us/download/confirmation.aspx?id=102888 


I can confirm that once the link went 'hot' on March 31st, we were able to follow the contained instructions with generating the app zip file, loading as a custom Teams app, and then deploying the rollout via Teams Setup Policies (which only sucked, because it wouldn't let us deploy by group, only batch...which is a pain, so I manually assigned 200+ users - Worth it though).

 

In our case, we are exclusively using internal site navigation within the actual SharePoint site pages themselves that we had manually added in to our SharePoint intranet instance.  So it exists on the page itself and not as a slide-in bar from the left.  I think that for us, that is because our SharePoint environment having originally existed well-before Modern Sites, and subsequently, any true shot at creating a new Hub-site model that enables global nav via the SharePoint App Bar was long since not applicable to us based on site design that would be crippled if we tried to truly convert our structure to a new root domain.


Microsoft

Agree with what @Steven Jordan mentioned about. please follow up the Add Viva Connections for Microsoft Teams desktop to download the PowerShell script to create the MS Teams app zip. once you upload it to your MS Teams admin, you should be able to leverage MS Teams App policy to deploy that and pin in for the end users. Behind the scene, the PS will generate the URL to embed your site collection to the MS Teams. the following is what I got which will display your site collection as immersive mode. there is also an option to configure the app as full screen mode. 

  "staticTabs": [
        {
            "entityId": "sharepointportal_84cdd192-4fca-422e-9a98-f994ecea9988",
            "name": "Portals-Contoso",
            "contentUrl": "https://[tenantname].sharepoint.com/_layouts/15/teamslogon.aspx?spfx=true&dest=[your-sc-url]?app=portals",
            "websiteUrl": "[your-sc-url]",
            "searchUrl": "[your-sc-url]/_layouts/15/search.aspx?q={searchQuery}",
            "scopes": ["personal"],
            "supportedPlatform" : ["desktop"]
        }
    ],

Again, it recommended to use Home Site which you can configure it, but it doesn't really matter that. as long as you provide a site collection, the ps will generate the manifest and create the zip file for you. 

 

Contributor

I'm having the same issue as @JOEL L. ROLLINS in that we still don't have the App Bar.  I'm a global admin and we're on early release.  No app bar, no global navigation.  We have a home site set and it's the root site.  It's also a modern communication site.  I am able to generate the zip though but have not been able to add Viva Connect to Teams as of yet.

New Contributor

Thanks @Steven Jordan@FrankChenMS for the responses. I'm specifically having an issue with the SharePoint App Bar.  I can create the Home Site app just fine and add it to Teams.  That part actually works great.

I've confirmed that the feature is enabled using the PowerShell script (Get-SPOTemporarilyDisableAppBar), but the new navigation elements do not appear.   Additionally, the Global navigation option does not appear in my Settings menu.

 

Global2.png

 

Microsoft

@JOEL L. ROLLINS The SharePoint app bar is still in the process of rolling out. The 'Global navigation' settings entry point is missing because the app bar hasn't reached your tenant yet. The PowerShell commandlet doesn't show whether the feature is available in your tenant, it just allows you to control whether you want to have it enabled once its been rolled out to you. Hope this clarification helps. 

Contributor

I am having an impossible time determining whether homesites are available for the GCC tenant yet. I cannot even see it anywhere on the roadmap anymore. Anyone have any idea?

 

Microsoft

@JOEL L. ROLLINS / @melkinsco , agreed with what @Melissa Torres mentioned, Rolling out SPO App Bar is still in process. Even though the roadmap indicated this feature was rolling out at the end of March, a few of my test tenant still don't have this feature available yet. If you want, you can create a MS support ticket to ask the status.  

Contributor

@FrankChenMS  yep.  I have Viva Connections installed with no issues at the moment. 

Occasional Visitor

Is there a way to undo the linking of sharepoint site to the Teams?

Microsoft

@AimzE if you are talking about the SPO site collection URL referenced from Viva Connection MS Teams App, you can update "contentUrl" property from the generated App's manifest file to a new site collection URL which you want. I hope that helps

Hi Team,
I am facing one issue after the implementation (integrating the site to Teams).
I have Spfx Extension enabled on this home site showing the mega menu, sometimes these mega menu links in MS Team are not opening in the app. They are opening in the browser.

Please, can any one help me in resolving this issue.

Thank You!

Microsoft

@SivaPrasad2007 , if your extension redirect to other URLs, have you tried to include those domains to your MS Teams manifest file-> validDomains property listed below? 

{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.9/MicrosoftTeams.schema.json",
  "manifestVersion": "1.9",
  "version": "1.0",
  "id": "[your app id]",
   ....
  "validDomains": [
   "[your-domain]"
   ....
  ],
}
Version history
Last update:
‎Oct 21 2020 02:15 PM
Updated by: