Mike G

My feedback

  1. 16 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 →
    Mike G supported this idea  · 
  2. 346 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    58 comments  ·  Public » Presence  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G commented  · 

    It's baffling to see this kind of high-visibility low-hanging fruit go unresolved and, in this case, even unacknowledged for almost three years now. Even "Planned: targeted for fall 2025" would be better than no response at all. This seems like a management failure.

    Mike G supported this idea  · 
  3. 1,204 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  102 comments  ·  Public » People  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G commented  · 

    Although, as people are mentioning, a partial workaround exists (backspacing over the last name), having to do this extra manual step for every name you @mention is annoying. This would seem to be high-visibility, low hanging fruit, but I may be underestimating the effort involved.

    I agree with those who prefer being able to use an alias because even the full first name often sounds inappropriately formal. Ideally, this would be a setting in Teams that the team owner or user themselves could set (the latter being best for delegation of control, but subject to abuse). Even pulling from AD alias would be far better than nothing even though it could mean more work for admins.

    Mike G supported this idea  · 
  4. 114 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 » Tabs  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G commented  · 

    As stated, OneNote Navigation Pane View defaults to Hide All in Teams. But if the purpose of OneNote is to manage hundreds or even thousands of notes organized in various sections, it makes no sense to default to a single note that happens to be at the top of one section. It's not even the most recent note you worked on (unless you manually move it to the top)! Yet, when you set a View option, Teams overrides it and goes back to showing a single page. 🙄

    New users often fail to notice the little arrow for expanding and seasoned users grow weary of having to manually expand over and over and over. PLEASE make Teams retain the user's OneNote Navigation Pane setting or, at the very least, default to the more sensible Show Sections and Pages view.

    Mike G supported this idea  · 
  5. 20 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 » Settings  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G commented  · 

    I agree totally with the other comments here. This behavior not only hurts adoption by new users, but is also a real annoyance for experienced users who get tired of expending the panes over and over and over. The power of OneNote is in quickly creating, organizing and navigating hundreds or thousands of pages, so it makes no sense for the default view in Teams to always open inside of one singe page!

    Mike G supported this idea  · 
  6. 1,588 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    265 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G commented  · 

    At the very least, there should be an option in the admin portal to make notification for all new messages an org-wide default (useful for very small orgs) and allow owners to set a team and/or channel default for all users (instead of having to keep asking everyone to please turn this on).

    While the Microsoft group in charge of Teams is taking it's sweet time discussing this (>1 year is bordering on outrageous), a lot of your customer base is frustrated and Teams engagement is being impeded in a major way.

    Mike G supported this idea  · 
  7. 2,791 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    77 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →

    As the last status states, we have been testing for several months.  Although many people have asked for this feature, we received a similar amount of feedback from other users that they prefer the Teams notifications and don’t want them changed.  We are currently testing a feature for users to choose between Teams notifications & Windows notifications.

    We will update you as work progresses.

    Mike G supported this idea  · 
  8. 106 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    29 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G commented  · 

    Ankit Jadia is the hero here. For convenience, here's the workaround he posted earlier in the comments. I don't know why Microsoft can't at least include this workaround with their disappointing error msg.

    ---------------------------------
    Ankit Jadia commented · October 16, 2019 05:38
    Just try sending a simple "Hi" first and then paste your long message and send it. It will work. :)
    ----------
    A small explanation about why this works. Skype for Business usually sends messages as thread bubbles in groups. So when first message is being sent from your side to other party it cannot be very long. Once you send a small message like "Hi" or something and then if you send the long one it gets clubbed in a group and you won't face any problem.

    Mike G supported this idea  · 
  9. 371 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Public » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G supported this idea  · 
  10. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mike G supported this idea  · 
  11. 13 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 →
    Mike G supported this idea  · 
  12. 771 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mike G supported this idea  · 
  13. 10,774 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    686 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G supported this idea  · 
  14. 184 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    50 comments  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G commented  · 

    I think Teams chat is trying to mimic mobile messaging apps like Android Messenger. As others have stated, Shift+Enter or Tab+Enter (full Compose mode) are intended for longer messages. However, discoverability of these key combinations is poor. New users in particular get frustrated by this default behavior.

    For these reasons, I agree with most here that Enter should never send by default. At the very least, this behavior should be globally configurable by owners/admins to make the user experience more consistent. In that case, this should also be user-configurable in case some users prefer a mobile messaging experience.

    Mike G supported this idea  · 
  15. 6,936 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    651 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →

    if you have an existing post that you want to show in a different channel, you can edit the message and cross-post. This will add the top-level post to the different channel, but will not include the full set of replies. We will keep this request in mind as we evolve the cross-posting feature in the future and update if the status changes.

    Details on cross posting can be found here: https://support.office.com/article/cross-post-a-channel-conversation-in-teams-9c1252a3-67ef-498e-a7c1-dd7147b3d295.

    Mike G commented  · 

    Thanks for working diligently on this feature. Without it, important conversations get stranded, orphaned or completely lost as teams and channels evolve.

    Mike G supported this idea  · 
  16. 24 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 » Tabs  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G commented  · 

    Came here to post the same request. Could not have articulated it more clearly and succinctly myself.
    Choosing a specific section during OneNote tab creation always opens that tab inside the first page in the section.

    Adding an option to Open in: Section View (instead of Page View) could also reduce hand holding and training needs for users who are new to OneNote navigation as well as reducing frustration for those of us who immediately click back to the broader section view virtually every time we open the tab.

    As a workaround, I've resorted to manually creating a table of contents for the pages in each section and positioning it as the first page. However, as you can imagine, this is very labor intensive. Losing the Onetastic table of contents add-on in the UWP version of OneNote is another shortcoming, but defaulting to section view would mitigate that.

    Mike G supported this idea  · 
  17. 6,180 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    457 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G supported this idea  · 
  18. 1,515 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    151 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Warren responded

    This feature request is still in the works. No additional updates are available at this time. I’ll keep you posted as I hear more.

    -Warren

    Mike G supported this idea  · 
  19. 2,351 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    286 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →

    Once support for Windows 10 native notifications is released, users who choose to use Windows notifications will be able to utilize Windows OS specific settings for the length of time to display notifications. Mac does not have an OS specific setting, so will not have the support.

    Mike G supported this idea  · 
  20. 1,964 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    73 comments  ·  Public » PowerBar  ·  Flag idea as inappropriate…  ·  Admin →
    Mike G supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base