Roland

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

    2 comments  ·  Public » Guest Access  ·  Flag idea as inappropriate…  ·  Admin →
    Roland commented  · 

    +1 for this suggestion. Would be a nice addition.

  2. 13 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 →
    Roland commented  · 

    Here is what I wrote earlier:

    "Allow Teams to use external Premium/Essential license to connect on 1 domain

    Instead of having a domain owner assign Premium/Essential licenses to external users for the sake of allowing them to work under their domain in Teams, allow external Premium/Essential licenses to be registered under that domain and have these users purchase and use their own copy to do so.

    Example:

    We want to use Microsoft Teams to work on projects. Our user group consists of independent external colleagues. Teams is using the company domain. The users have an existing domain e-mail address. They wish to purchase their own O365 Premium or Essential license and connect that with an existing Teams environment. This is not possible today.

    Either: a user is assigned a license from within Teams and automatically gets domain credentials. This means that the domain owner is paying for all licenses for all users.

    Or: a user gets its own license, with its own domain and then applies for access. This means the user pays for the license, but also gets their own Teams domain.

    The alternative is (limited) guest accounts.

    We want users to register their existing e-mail addresses from one domain as credentials for the purchase of their own license and then connect to Teams."

    And, after speaking with support, I added the following:

    "Just learned that applying for a Business Premium subscription includes an implicit request for the creation of a tenant/domain for that one account. My suggestion would be to have a choice when signing up between activation of that single new tenant/domain or joining an existing tenant/domain. If the latter, the owner of the existing tenant/domain would need to accept the application or actively drive such application. "

  3. 55 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Roland commented  · 

    +1 for this suggestion. Would be a very good addition!

  4. 36 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 →
    Roland commented  · 

    Totally agree: I am trying to delete an automated message from a bot (connected service). Being the owner of the Team/Channel, I would expect to be able to moderate the chat thread. It is weird that I can't delete chat messages as owner. And while the workaround to ask team members to delete one of their chats messages is tedious but an option, this is not possible for automated non-member messages.

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

    We’ll send you updates on this idea

    280 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    try this instead  ·  Suphatra responded

    Hey everyone! We have this already. Just click the ellipses next to the thread name and select “Hide”.

    Note that we cannot provide a “hard delete” due to eDiscovery and other legal reasons.

    Thanks,
    Suphatra

    Roland commented  · 

    +1 for this. I would argue that Team owners should be able to delete any and all messages if so required. This applies to public and private messages, and certainly the automated bot messages in conversations.

  6. 4,235 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    141 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Suphatra responded

    Sorry for the delay on an update on this one! I’m hunting down the status for you and will update once I have it.

    Also, if you are interested in participating in testing or surveys for this, just tweet me at @skprufo.

    Suphatra

    Roland supported this idea  · 

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.