Forum Discussion

obetheduck's avatar
obetheduck
Copper Contributor
Jan 15, 2025
Solved

Team not visible in Teams admin centre or from get-Team powershell by owner and global admin.

In my organization we currently have 16 teams.  However in teams admin->manage teams I only see 14.  Two of them do not show up.  All were create a couple years ago and for the most part have been fine.  I also think they may have shown up in the past but no long but my memory is not 100% on that.  

The 2 team with issue I am able to fully use the team but unable to manage them from an admin point of view.  I recently as asked to add some member to private channels in these teams.  However I am able to do so.

 

I am both owner of the team and my account has global admin role.

I have also run powershell get-Team and only list 14 teams with the 2 in question being missing.

Under https://portal.office.com/adminportal/home#/groups > "Active teams and groups" I can see all 16 groups however the 2 in teams question don't have the "Teams" icon under "team status".

From this groups window if I click "Add Teams" it tries and comes back with "We couldn't create a team for this group. Please try again."

All 16 teams show under "Sharepoint admin center">active sites  with "Teams" icon showing share point being connected to the team.

 

Is there a way to reconnect these teams back to there groups?

 

Thanks

  • obetheduck's avatar
    obetheduck
    Mar 17, 2025

    I have been working with microsoft to resolve this issue since it was posted and now have a resolution.  We were able to MS Graph to make a API call to Reconnect the Team to the Group.  

     

    URL-> https://developer.microsoft.com/en-us/graph/graph-explorer

     

    groupid below replaced from the Admin->Identify -> Group ->All Groups-> (Group disconnected from Team)-> GroupID that matches the team or ExternalDirectoryObjectId from exchangeonline of the team email address.

    API Rest Call PATCH https://graph.microsoft.com/v1.0/groups/{groupid}   

    Request Body
    {"resourceProvisioningOptions": ["Team"]}

     

    Please use this at your on risk.  I did this under supervision of microsoft support and engineering after weeks of research.

6 Replies

  • You can also gather the team/group id and replace it in the management URL

     

    https://admin.teams.microsoft.com/teams/manage/73dcb149-df26-4618-bc24-fa91ca4b4c55

     

    replace the id and insert that in the browser

     

    check if it opens

    • obetheduck's avatar
      obetheduck
      Copper Contributor

      Ok that is an insiteful workaround that works like a champ.

  • obetheduck's avatar
    obetheduck
    Copper Contributor

    You are correct.  I finally found an similar article recommending the same after creating this discussion.  I had search many articles before posting this but the critically search term was 365 group not syncing to teams.  I have already created an open ticket with microsoft and received a call back from them to document the issue.  I will mark this as the solution if the ticket does indeed fix it.  Thanks

  • Looks like something went wrong on the backend... best open a support case with Microsoft, hopefully they have a way to "resync" it. Otherwise you'll have to recreate them, I suppose.

    • obetheduck's avatar
      obetheduck
      Copper Contributor

      I have been working with microsoft to resolve this issue since it was posted and now have a resolution.  We were able to MS Graph to make a API call to Reconnect the Team to the Group.  

       

      URL-> https://developer.microsoft.com/en-us/graph/graph-explorer

       

      groupid below replaced from the Admin->Identify -> Group ->All Groups-> (Group disconnected from Team)-> GroupID that matches the team or ExternalDirectoryObjectId from exchangeonline of the team email address.

      API Rest Call PATCH https://graph.microsoft.com/v1.0/groups/{groupid}   

      Request Body
      {"resourceProvisioningOptions": ["Team"]}

       

      Please use this at your on risk.  I did this under supervision of microsoft support and engineering after weeks of research.

      • Nigel Clark's avatar
        Nigel Clark
        Copper Contributor

        Seeing the same issue. Am trying to run the patch request to see if it will resolve, however it's unclear what permissions scope is needed for the call. At present we are seeing:

         

            "error": {

                "code": "Authorization_RequestDenied",

                "message": "Insufficient privileges to complete the operation.",

         

        Can you share the permissions scope you used?

Resources