Yogesh Kumar

My feedback

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

    We’ll send you updates on this idea

    0 comments  ·  Public » Search  ·  Flag idea as inappropriate…  ·  Admin →
    Yogesh Kumar shared this idea  · 
  2. 38 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Public » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    Yogesh Kumar supported this idea  · 
  3. 53 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Public » IT Pro  ·  Flag idea as inappropriate…  ·  Admin →
    Yogesh Kumar supported this idea  · 
  4. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Bots  ·  Flag idea as inappropriate…  ·  Admin →
    Yogesh Kumar supported this idea  · 
  5. 280 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    27 comments  ·  Public » Guest Access  ·  Flag idea as inappropriate…  ·  Admin →
    Yogesh Kumar supported this idea  · 
  6. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Yogesh Kumar shared this idea  · 
  7. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Yogesh Kumar shared this idea  · 
  8. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Yogesh Kumar supported this idea  · 
    An error occurred while saving the comment
    Yogesh Kumar commented  · 

    https://github.com/MicrosoftDocs/office-docs-powershell/issues/2182

    Specifying the team by GroupId is cumbersome. We need to be able to specify by alias.

  9. 42 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Yogesh Kumar supported this idea  · 
    An error occurred while saving the comment
    Yogesh Kumar commented  · 

    https://github.com/MicrosoftDocs/office-docs-powershell/issues/2399
    normally, when a new channel in a team is created, a folder with exactly the same name as the channel is also directly created in the document library of the team's Sharepoint site. When I add a channel manually in Teams itself, everything works correctly. 6 weeks ago, the same result could also be achieved with the command "New-TeamChannel" - right after the team channel was created, a folder with the channel's name was available in Sharepoint.

    However, the behavior of "New-TeamChannel" seemingly changed in the meantime. Now, the folder in the SP document library is not immediately created anymore, but only when the tab "Files" is clicked in the channel in Teams. As long as the "Files" tab is not clicked, no folder will be created in SP. It seems that only clicking the tab serves as a trigger to create the SP folder.

    This is an issue in our use case where we want to copy files to that folder right after we create the channel, and we rely on the existence of that folder. As already said, it worked perfectly in November 2018. But now, since no folder is there WITHOUT clicking the "Files" tab in Teams, the path of the SP folder can't be found and we get an error message.

Feedback and Knowledge Base