./cb

My feedback

  1. 4,128 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    838 comments  ·  Public » Devices (Headphones, Cameras)  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    ./cb commented  · 

    Teams shoot self foot

    ./cb supported this idea  · 
  2. 1,059 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    161 comments  ·  Public » Wiki  ·  Flag idea as inappropriate…  ·  Admin →
    ./cb supported this idea  · 
    An error occurred while saving the comment
    ./cb commented  · 

    Jeff's method works. Thanks mate.

    .. >> Jeff Poblocki commented · March 31, 2020 11:52
    Longer version of the the same thing attached as a rtf file.

    I did a bunch of other testing and also locked out 'files' so that I could put company policy information in there.

    @anonymous.. perms at 'Teams Wiki Data' just don't apply.. I guess they're overridden by the hidden guid.blah.blah@thread.tacv2.wiki (or similar 'odd name') and you must block inheritance before setting the perms there. Again, not my work, I hate trying to fathom the sharepoint permissions nightmare. This is all based on Jeff's comment further down.

    ( can't imagine why that isn't surfaced as a simple perms dialogue in Teams itself, also can't imagine why all these perms are structured in such a complicated and contradictory way when the Active Directory perms structure already exists in the MS Cloud and is both robust and simple /rant).

Feedback and Knowledge Base