Anonymous

My feedback

  1. 27 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 →
    Anonymous supported this idea  · 
  2. 10 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 » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    Extend the questions to factor that Sharepoint is now a backing store for Teams and Yammer O365 groups resources mutually exclusively.

    It might be appropriate to converge conceptual group management focus into O365 admin panel > Resources > Sites to add Teams and Yammer as mere settings to converge management to somewhere (anywhere would be nice!). Both Teams and Yammer prescribe Team 'Sites', afterall.

    Left as is, Teams tabs and Yammer links to site resources are toys that need to be firmed up as bone fide settings (at least templates).

    Dynamics 365 Document Management maintains locations whilst still allowing ad hoc retargeting to other locations (at far lower granularity). Good enough for Dynamics, good enough for Teams and Yammer?

    Anonymous shared this idea  · 
  3. 32 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  4. 10 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 » IT Pro - Controls and Knobs  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  5. 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 » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  6. 11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  7. 60 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 » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  8. 6,787 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    582 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.

    ~Alex

    Anonymous commented  · 

    If I get back 230mb PLUS turning off Giphy altogether will help reduce the burn even moreso, then this is good news indeed. Keep up the great work.

    Anonymous commented  · 

    "There was a glitch and we are recovering." says the Teams splash dialog after it crashed. Desktop experience of using the PDF tab integration using a file in Sharepoint, is that the file is being pulled into the main Teams process causing the app to receive a very high priority with memory consumption ramping and ramping with the op and the rest of the Windows 10 OS suffers slow or no interactivity options! It goes back to normal after the file is copied to where that integration puts it - or after the app crashes. Running the same test twice doesn't improve the experience suggesting no caching strategy is in place for this app yet. Teams Desktopc rashes every time I open this PDF tab now and stopped showing the recovery splash and stays dead until I reopen the app. It's not just a create time design issue but normal usage issue.

    Anonymous supported this idea  · 
  9. 22 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 » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    Anonymous commented  · 

    I have a comment from a customer GM today;

    "each of O365 Groups, Teams Sharepoint integration, Yammer Sharepoint integration, Sharepoint direct, and Dynamics integration with Sharepoint all solve 80 percent of their own problem but create a separate different 20 percent solved by none of them to each other."

    I reckon he might be talking about the fact that there is no convergence across the mentioned products with Sharepoint as a holy grail collaborative content backing store (for Yammer and Teams as just ways to conventionally share through a tool in the context at hand be that private or public).

    I also see it that remediation of modelling (design) mistakes could be easier with tools made available to retarget (or at least workaround) siloing issues that challenge convention, cohabitaton, and sharing such as for Yammer and Teams and Sharepoint currently.

    In another post elsewhere, I mentioned 'Publishing' items from site-to-site for comms and docs may be an option. i.e. to the 'outer loop' as Nicklas put it. That probably means having an option at the user level and at the admin level.

  10. 8 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 » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    I think this is only half the story and it gets worse.

    Sharepoint site resource is auto-provisioned for each group and group email addresses overload on name (because its allowed) leaving them so hideously deformed and prolific to the extent that users don't know what is authoritative anymore.

    I wonder if the philosopy of Yammer 'freedom', and O365 groups 'freedom' is undermining the MS Teams effort?

    I understand that arbitrary Yammer groups can be set to notify into Teams via connection per channel, but I can't get past that the Sharepoint backing store is so siloed (or fragmented?) causing equally large woes to the mentioned email address situation.

    If intention has it that Yammer is to be a kind of 'Public face' and Teams be a kind of 'Private huddle' then show me how Guest access to Teams improves the situation.

    It almost feels like it needs to be the other way around; there needs to be a Share on Yammer feature in Teams to get something that's happening inTeams out to Yammer and publish something out to it's Sharepoint silo. i.e. Teams holds the focus for staging and Yammer is the release environment as appropriate. Yammer's and Outlooks freedom to proliferate complicates any prospect of convention as a sensible means to map between the environments.

  11. 30 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Public » Calling  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  12. 354 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    67 comments  ·  Public » Calling  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback. Two updates on this:
    1) Audio 1:1 call recording feature is on the backlog. We’ll update when we have more details to share.

    2) Compliance recording is being worked on, partnering with 3rd party providers. Please see the posting below:

    https://www.microsoft.com/en-us/microsoft-365/blog/2019/07/11/microsoft-teams-reaches-13-million-daily-active-users-introduces-4-new-ways-for-teams-to-work-better-together/

    Anonymous supported this idea  · 
  13. 29 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 » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  14. 40 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 » Calling  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  15. 18 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 » Calling  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  16. 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 » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  17. 54 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  18. 5 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 » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  19. 9 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 » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  20. 290 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  19 comments  ·  Public » Planner  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
← Previous 1

Feedback and Knowledge Base



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.