Feedback by UserVoice

Anonymous

My feedback

  1. 500 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    24 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  2. 539 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  Office 365 Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 2,038 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    93 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    We have a mix of Seat licenced Office 2019 Pro Plus on E1 and F1 users, and E3 licenced users licenced to Office 365 PRo Plus. We are planning a new Citrix platform based on Server 2019, but are unable to deliver due to this marketing driven requirement.
    Only supported platform for Office 365 Pro Plus users is Windows Server 2016
    Only supported platform for Office 2019 Pro Plus users is Windows Server 2019
    Result is that we are forced to maintain two different server platforms on our Citrix platform.
    This drives cost, and are higly ineffeicient and not logic.
    Either support Office 2019 on Server 2016 or Support Office 365 Pro Plus on Server 2019!

    Anonymous supported this idea  · 
  4. 691 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. 297 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    25 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  6. 29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Office 365 Admin » Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  7. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  8. 161 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Also consider allowing for 3 first letters of attribute already supported, %3[Department] - Similar to he old exchange recipient policies.

    Anonymous supported this idea  · 
  9. 42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    An error occurred while saving the comment
    Anonymous commented  · 

    Yes, default behaviour should be similar to ADFS, where Office activation is seamless, and Office365 account is added to OfficeProPlus autmatically.

  10. 1,490 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    56 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →

Feedback and Knowledge Base