Micael

My feedback

  1. 149 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    12 comments  ·  Microsoft Teams free  ·  Flag idea as inappropriate…  ·  Admin →
    Micael supported this idea  · 
  2. 294 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    42 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Micael supported this idea  · 
  3. 1,090 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    83 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Micael supported this idea  · 
  4. 17 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Public » Guest Access  ·  Flag idea as inappropriate…  ·  Admin →
    Micael supported this idea  · 
    An error occurred while saving the comment
    Micael commented  · 

    This is a major bug. As we diagnosticated, here's what seems to happen : Teams has its own database and is synched with O365 groups. But if you invite a guest in your O365 group, and he has not yet accepted Azure invite (so pending in AzureAD), the sync does not happen and he will never be able to access Teams. So, all apis will fail ( Powershell, Flow) that uses Teams api with add-teamUser, since it uses O365 group adding in reality and not the internal Teams add user! Confusing as F***, and also, useless since you can only add guest by Teams interface!

Feedback and Knowledge Base