MS Teams "We couldn’t get the email address of this channel. Please try again later" + We're still setting up your team, you can change your picture when we're done.

Anonymous
2018-06-05T18:40:14+00:00

Hi,

2 errors that appear to be related to a new team/channel being created.

When creating a new team, we can no longer get the email address nor change the picture. 

No issues with previously created teams/channels. 

Confirmed: 

  • Waited for 3 days
  • Error occurs on App and Web versions
  • App is on latest version
  • Error occurs on both Windows and Mac
Microsoft Teams | Microsoft Teams for business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

57 answers

Sort by: Most helpful
  1. Anonymous
    2019-02-27T01:26:57+00:00

    OK. Your suggestion didn't work as, clicking on files generated the following error in the client and web page.

    Show details has the following error:

    Exception encountered from Sharepoint for requestId f3eac39e-8038-8000-e642-900ecfd7e538 Scenario ID: 351

    I have set the team from private to public, waited several hours and confirmed it in the client, and set it back. This did nothing.

    This team was generated from a SharePoint site, which exists and, both the site and team, have been around for well over 12 months now, as has the issue of not being able to "Get email address" for any of the channels. The only thing to note is that the user who created the site and team are no longer employed here. 30 teams that I created this morning have no problems.

    As a global admin, I can see the email associated with the distribution list.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-01-17T02:35:38+00:00

    The workaround of going to the affected channel to upload files to the channel doesn't solve the "couldn't get the email address of this channel" issue.

    Was this answer helpful?

    0 comments No comments