Gaurav

My feedback

  1. 530 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

    77 comments  ·  Public » IT Pro  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav supported this idea  · 
  2. 2 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

    0 comments  ·  Public » Notifications  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav shared this idea  · 
  3. 1,715 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

    142 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Gaurav commented  · 

    As of Dec 15, 2020 when a chat is between a user on either latest Chrome or latest Edge (Chromium) Browser and another desktop Teams user, the screen sharing option does not appear on the browser user in 1:1 chat, but does appear on the Desktop client. Both users are on Windows 10.

  4. 1 vote

    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

    0 comments  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav shared this idea  · 
  5. 31 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

    1 comment  ·  Public » Bots  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav supported this idea  · 
  6. 1 vote

    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

    0 comments  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav shared this idea  · 
  7. 17 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

    Gaurav supported this idea  · 
  8. 1 vote

    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

    0 comments  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav shared this idea  · 
  9. 171 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

    30 comments  ·  Public » People  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav supported this idea  · 
    An error occurred while saving the comment
    Gaurav commented  · 

    A recent (Jan 2020 first week) fix has enabled display of external user Friendly names but apparently only if the external user is a Teams/Office 365 user. The Teams client (and the latest SfB client) can detect that the remote user across Federation is a Teams users, and also show their Friendly name.

    However, the problem still exists if the external user is a pure Skype for Business user or Trusted Application reachable across federation. In this case, only the SIP URI (email style) shows, and not the Display Name.

    So: If remote user is Teams user, friendly name will show. If remote user is SfB On-premise user, friendly name does not show (as of Jan 14, 2020)

  10. 1,032 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

    165 comments  ·  Public » People  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav supported this idea  · 
  11. 4 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

    0 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav shared this idea  · 
  12. 8 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

    1 comment  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav shared this idea  · 
  13. 402 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

    55 comments  ·  Public » Bots  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav supported this idea  · 
  14. 2,497 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

    156 comments  ·  Public » Calling  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Gaurav commented  · 

    Feature parity with SfB can only be claimed if a replacement for UCMA, or at the very least the Lync SDK (client SDK) is provided.

    The Bot Framework plus Graph/Calling API is a clumsy solution.

    Unlike UCMA or Slack, a bot can not listen into a conversation without being @mentioned which defeats the essence of cognitive assistance bots as well as other sentiment analysis or assistive productivity applications. Microsoft has substituted its notion of privacy controls in this implementation for what a company ought to be able to decide for its own tenant.

    The HTTP based architecture is perceptibly slow compared to the socket based architecture of UCMA and the local inter process communication based architecture of the Lync client SDK. It has many moving parts ( Teams client <> Teams/O365 <> Bot Framework <> Bot), each a http based connection with associated connections set up/tear down to deliver a basic message.

    Finally, presence updates are atrociously slow which is a deal breaker for contact center apps that rely on agent presence/availability.

    Gaurav supported this idea  · 
  15. 308 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

    36 comments  ·  Public » People  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav supported this idea  · 
  16. 62 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

    2 comments  ·  Public » Bots  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav supported this idea  · 
  17. 15 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

    0 comments  ·  Microsoft Teams free  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav shared this idea  · 
  18. 26 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

    1 comment  ·  Public » Bots  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav supported this idea  · 
  19. 250 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

    30 comments  ·  Public » Bots  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav supported this idea  · 
  20. 6 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

    0 comments  ·  Public » Developer Platform  ·  Flag idea as inappropriate…  ·  Admin →
    Gaurav shared this idea  · 

Feedback and Knowledge Base