SharePoint Team Not Showing in Teams: Complete Fixing Guide (2025)

Mack John ~ Published: July 24th, 2025 ~ SharePoint ~ 6 Minutes Reading

If your SharePoint team not showing in Teams, it’s likely due to a missing Microsoft 365 Group link, site type mismatch, or permission issue. Recently, I’ve dealt with this problem myself. That’s why I researched and found the root causes behind the issue and how to fix them step by step. 

Now, I will explain to you:

Why Your SharePoint Team Isn’t Appearing in Microsoft Teams

Knowing the reasons behind this issue will help us to prevent it in future. So, go through these root causes first, which I found out:

  1. No Microsoft Teams has been created for the SharePoint site yet.
  2. The SharePoint site wasn’t created through Teams.
  3. You’re not a member or owner of the Microsoft 365 group.
  4. The SharePoint site is a Communication Site, not a Team Site.
  5. Teams admin settings or policies are preventing visibility.
  6. Microsoft 365 services haven’t fully synced yet.

So, these are the six main causes, and in the next sections, I will explain to you how to resolve each one in seconds.

Troubleshooting SharePoint Team Not Showing in Teams Step by Step

Resolving this query is quite simple; just follow the flowchart below, which explains how to fix it quickly:

SharePoint team not showing in Teams

Here is the detailed explanation of the troubleshooting steps:

#Step 1. Check If a Microsoft Team Exists for the SharePoint Site

Check whether a Microsoft Team has ever been created for the SharePoint site:

  • Open the SharePoint site in a browser.
  • Look for a Go to Teams icon or link.
  • If that link is missing, then a Team wasn’t created.

Since not all SharePoint sites are automatically linked to Teams, that’s why it is necessary to check and manually link the site to Team. Next, we will learn the same. 

#Step 2. Create a Team from the Existing SharePoint Site

If you find there was no Team linked, then use Microsoft Teams to create one based on the existing SharePoint site’s Microsoft 365 group:

  1. Open Microsoft Teams.
  2. Click Join or create a team at the bottom.
  3. Select Create a team from an existing Microsoft 365 group.
  4. Choose the group that had the same name as the SharePoint site.

This immediately created a new Team and linked it with the SharePoint site. After a few minutes, the SharePoint team not showing in Teams error is resolved. However, if your SharePoint site wasn’t created through Teams originally, then read how to create a SharePoint site in Teams guide.

#Step 3. Check Permissions for the Microsoft 365 Group

One time, I couldn’t see the SharePoint site in Teams because I wasn’t a member of the related Microsoft 365 group. So, I verified some things, which are:

  • I signed in to the Microsoft 365 admin center.
  • Navigated to Groups > Active Groups.
  • Searched for the SharePoint site name.
  • Checked if my user account was listed under members or owners.

According to Microsoft’s overview of Microsoft 365 Groups, Teams, and SharePoint rely on the same group. If you’re not part of the group, the associated Team won’t show up for you in Teams. 

#Step 4. Confirm the Site Type to Resolve SharePoint Team Not Showing in Teams

SharePoint sites can be of two types: Team sites and Communication sites. Only Team sites are group-connected and able to link with Microsoft Teams. If you are using Communication Site, you won’t fix the issue. So, identifying the site type is essential:

  • Open the SharePoint Site settings from the home page. 
  • Now, see the site type:
    • Communication sites have a wide layout and no Group options.
    • Team sites show a Members list and Site permissions tied to a group.

If the site were a Communication site, then you need to recreate the content in a Team site or migrate SharePoint site to another site to use it in Teams.

#Step 5. Fix SharePoint Team Not Showing in Teams by Reviewing Teams Admin Settings & Policies

There were cases where everything was correctly configured, but Teams policies were blocking access. So I logged into the Teams Admin Center and checked the settings:

  • Under Teams > Teams settings, ensure Team creation is allowed.
  • Now, under Users > Policies, confirm that Teams apps are not restricted.
  • Verify whether Teams client has any pinned or hidden apps affecting visibility.

If the settings are too restrictive, it creates a hassle and does not show up for the user.

#Step 6. Allow Time for Microsoft 365 Sync

Sometimes it took up to 30–60 minutes for Microsoft 365 services to sync the change across SharePoint, Teams, and Outlook.

So if you just created or linked something, give it a little time. Additionally, if you’re experiencing broken links or access issues alongside Teams visibility problems, this guide on why is my SharePoint link not working can help.

Use PowerShell to Verify Group and Team Links

In more advanced cases, I used PowerShell to check if a Microsoft 365 group had an associated Team. Here’s the script mentioned in Microsoft Teams’ official PowerShell documentation used to troubleshoot SharePoint team not showing in Teams:

# Connect to Teams

Connect-MicrosoftTeams

# Search for the group

Search for the group

If nothing returned, I confirmed that the group had no linked Team. I could create one like this:

New-Team -GroupId GroupID

This helped in situations where the Teams UI didn’t provide enough clarity.

Quick Steps to Troubleshoot the Issue

Here is the quick recap of the steps we discussed:

  1. Verify whether a Team was ever created from the SharePoint site.
  2. If not, create one from the existing group via Teams.
  3. Make sure you’re a member or owner of the related Microsoft 365 group.
  4. Confirm that the site is a Team Site, not a Communication Site.
  5. Review Teams admin settings to make sure nothing is blocked.
  6. Wait for full sync if recent changes were made.

Author’s Verdict

If your SharePoint team not showing in Teams whether due to a missing Team connection, permissions, or site type. Following the mentioned steps will easily troubleshoot this error in seconds.